Appendix FGlossary
The words as this manual uses them, each with the chapter that explains it.
F.1 The program and the computers
| Term | Meaning | See |
|---|---|---|
| Server | The computer that holds the laboratory's database, on which the program always runs | 4.1 What runs on the server |
| Member computer | A computer of the branch that runs the program without a database, taking everything from the server | Chapter 5: Network, branches and Clarus Link |
| Station | The part of the program on every computer that prints on its printers and serves the analysers cabled to it | 7.1 How the program prints |
| Branch | A site of the laboratory with its own server or computers, within one laboratory or a chain | Chapter 5: Network, branches and Clarus Link |
| Program folder | Where the program's files are. It is replaced at every update | B.2 Inside the program's folder |
| Data folder | Where the database, the encryption keys and the logs are. Updates never touch it | B.3 Inside the data folder |
| Service | A program Windows starts with the computer. Only the database is a service | C.1 Services |
| Scheduled task | What Windows' Task Scheduler runs. The program itself is a task that starts at sign-in | C.2 Scheduled tasks |
| Private and Public network | How Windows classes a network. The program never opens its ports on a Public one | A.4 Firewall rules |
F.2 Printing and devices
| Term | Meaning | See |
|---|---|---|
| Printer role | The label, the receipt or the report. Each role has its printer on each station | 7.2 Binding printers to their roles |
| Silent printing | Printing straight to the role's printer, with no window | 7.1 How the program prints |
| Command language | What the printer understands: ZPL, TSPL or ESC/POS, or drawing through the Windows driver | 7.2 Binding printers to their roles |
| Resolution | The label printer's dots per inch, most often 203 or 300 | 7.3 Printing settings |
| Link file | An analyser's settings and codes in one file, from the Clarus library or another laboratory | 6.4 Mapping the analyser's codes to tests |
| Code mapping | Joining a code the analyser sends to a test of the catalogue. Without it no result is filed | 6.4 Mapping the analyser's codes to tests |
| Held messages | What the analyser sent that was not filed, with the reason, until it is processed again | 6.5 Checking the link |
| Work orders | What to run on each tube, sent by the program to the analyser or asked for by the analyser | 6.7 Both directions: work orders |
| ASTM, HL7 and POCT1-A | The languages analysers and the program talk in. MLLP is HL7's message envelope | 6.1 How results arrive |
F.3 Data and security
| Term | Meaning | See |
|---|---|---|
| Backup | A signed, complete copy of the laboratory's data, to restore from | Chapter 8: Backup and restore |
| Restore drill | A trial restore of a backup in a separate place, proving it really restores | 8.4.2 The restore drill |
| Migration | Carrying a laboratory's history from the RealLab program into the program | 10.2 The steps of a migration |
| Acceptance report | What the program shows after a migration: what moved and what did not, with a balance of numbers | 10.4 The acceptance report |
| Recovery code | A code for each administrator, to set a new password on the server if they forget theirs | 11.5 The administrator's recovery code |
| Emergency sheet | A printed sheet with the recovery code, the installation number, the support number and the cloud backup code | 11.5 The administrator's recovery code |
| Encryption key | The file field_vault.key that reads the sensitive fields in the database | B.3 Inside the data folder |
F.4 Licence and updates
| Term | Meaning | See |
|---|---|---|
| Trial | 14 days with everything in the program before activation | 3.2 The trial |
| Computer fingerprint | What binds the licence to the computer from its parts, tolerating some of them changing | 3.3 Activating the licence |
| Installation code | The number that identifies the laboratory's installation to the supplier and support | 3.3 Activating the licence |
| Hand-back code | What the program gives when the licence leaves a computer, proving it was handed back | 3.4 Moving the licence to another computer |
| Required update | An update with a deadline. When it passes, new work is refused until the update, and reading, printing and delivering verified results stay open | 9.1.1 A required update |
| Language pack | A signed file with a whole language's texts for the screens, the papers and the test names | 12.1 What a language pack is |
| Status report | A summary of the program's state sent to support, with no patient data at all | 13.3 The status report to support |
| Remote support session | Clarus support entering the laboratory's copy with its agreement, for a time it chooses | 13.4 A remote support session |