How to use Klinira
Every screen in the application, what it is for, and the steps to work through it — with a picture of each one. Written for the people who will actually use it: the counter, the nurse, the pharmacist, the doctor and whoever runs the clinic.
This guide covers the whole application, screen by screen. Each chapter stands on its own, so you can open the one you need without reading the others first.
Download the whole guide
Print it and keep it at the counter. It is this same guide printed — every chapter, every picture — not a shorter version of it.
Where to start
| If you are | Read these first |
|---|---|
| Opening it for the very first time | One patient, from the door to the payment |
| Installing Klinira for the first time | Installation · Your first week · Signing in · Staff accounts · Roles |
| On the counter | Today · Patients · Appointments · Queue · Billing |
| A doctor or dentist | The consultation · Prescribing · Certificates and letters · Laboratory results · Dental charting |
| In the pharmacy | Dispensing · Stock · The statutory registers |
| Running the clinic | Reports · Backup · Licence · Working offline |
| Stuck, and it is nine on a Tuesday | When something goes wrong · Help inside the application |
Every screen, chapter by chapter
Installing Klinira and setting up the clinic
One computer in the clinic holds the records and every other computer talks to it. The setup wizard runs once, on that computer, and it is the only part of Klinira that must be done in order.
Chapter 2Your first week
The installation finishes on one afternoon. The clinic finishes some days later, when the paper day-book goes into a drawer and does not come out again. Ten things sit between the two, and the system keeps the list for you.
Chapter 3One patient, from the door to the payment
Every other chapter is about one screen. This one is about one patient walking through the whole clinic, and who touches what along the way. If you read only one chapter before your first morning, read this one.
Chapter 4Signing in, the Quick PIN, and locking the screen
Everybody who uses Klinira signs in as themselves. It is not an administrative nicety: every note, every dispensing entry and every payment is recorded against whoever was signed in, and a shared account makes all of that say the same name.
Chapter 5The Today screen
The screen the clinic opens on. It answers the four questions somebody arriving at eight in the morning actually has, and it is the only screen designed to be looked at rather than worked in.
Chapter 6Patients: finding, registering and the record
Everything in Klinira hangs off a patient record, so the two things that matter most here are finding the right one and not creating a second one for a person who already exists.
Chapter 7Appointments and online booking
The calendar your staff work in, and the booking page a patient reaches from their own phone. The two are joined, but nothing a patient does writes into your calendar without somebody at the counter accepting it.
Chapter 8The queue, QR check-in and the waiting room screen
One queue, three ways into it: the counter puts somebody in it, a patient scans the QR at the door, or an appointment arrives. Everything downstream — the consultation, the pharmacy, the payment desk — reads the same list.
Chapter 9Messages to patients
One list of everything the clinic has written to a patient and not yet sent. Four things put messages on it, you press send in WhatsApp, and nothing goes out on its own.
Chapter 10The consultation
One screen holds the whole visit: what the patient says, what you find, what you diagnose, what you prescribe. It keeps working with the network cable out, and nothing you type is lost if the machine is switched off mid-sentence.
Chapter 11Prescribing
Write the prescription once. The pharmacy sees it, the bill picks it up, the label prints from it, and the statutory register entry is made from it.
Chapter 12Medical certificates and referral letters
The MC a clinic writes every day it opens, and the letter that sends a patient to a hospital. Both are numbered, both are kept on a register, and neither is ever edited after it is issued.
Chapter 13Dental charting and the gum chart
The chart is a record, not a picture of today. Every visit adds a layer, nothing is overwritten, and you can see the mouth as it was on any past date.
Chapter 14The chronic disease register
The list of patients you have undertaken to see again, and how often. Mostly diabetes and blood pressure — and the point of it is the other list it produces: who has stopped coming.
Chapter 15Immunisation
A child's vaccination record, the National Immunisation Programme schedule worked out from their own date of birth, and the list of who has not come for their injection.
Chapter 16Laboratory results
The report that comes back from Pathlab, filed against the patient with its numbers in — and the list of results nobody has read yet, which is the part that matters.
Chapter 17JPJ, food handler and other examinations
The four examinations a clinic does for somebody who is not the patient — a licensing authority, an employer, an insurer. Filled in on screen, numbered, registered, and printed on the clinic's letterhead.
Chapter 18FOMEMA — foreign worker examinations
The board that tells a screening clinic which of its open cases is waiting on them. Klinira holds the clinic's side of a FOMEMA case; the findings are still keyed into FOMEMA's own portal, because it has no connection for other software.
Chapter 19Dispensing
The pharmacy screen takes a prescription, picks the batch, prints the label, moves the stock and writes the statutory register entry — in one action, so none of those can be done and another forgotten.
Chapter 20The statutory registers
The Prescription Book and the psychotropic register. Klinira writes them as a side effect of dispensing, so they are complete without anybody keeping them up.
Chapter 21Medicines, stock and purchasing
What each medicine is, what is on the shelf by batch and expiry, and how it gets there. Dispensing moves stock by itself, so the work here is checking your medicines, receiving, counting and watching what is about to expire.
Chapter 22Billing, payment and the till
The bill builds itself from the visit — the consultation, what was dispensed, what was done — and the counter checks it rather than typing it.
Chapter 23Panels and claims
Klinira does not send anything to a panel — nobody's software can. What it does is tell you what each panel owes you right now, and find the claims their statement quietly left out.
Chapter 24Reports
Twenty-six reports, grouped by what they answer. Every one runs on the clinic's own data, prints, and exports to CSV.
Chapter 25Staff accounts and clinic settings
Everybody who works in the clinic gets their own login. That is what makes the audit trail mean anything, and it is what a shared account destroys.
Chapter 26Roles and permissions
The seven roles Klinira supplies are starting points, not rules. Change what any of them may do, or make one that fits a job in your clinic.
Chapter 27Backup, restore and getting your data out
Backups run by themselves. The part that needs a person is proving one works, and it is the only item on the getting-started list that really matters.
Chapter 28The licence
What you are entitled to, how long it runs, and what happens if it lapses. Nothing here ever takes your records away from you.
Chapter 29Working when the internet is down
Almost everything carries on. The exceptions are two, they are deliberate, and Klinira says which one you have hit rather than showing a general failure.
Chapter 30When something goes wrong
The things that actually happen in a clinic, and what to do about each one. Nothing here needs a technical person, and none of it needs us to be awake.
Chapter 31Help inside the application
Every message Klinira shows carries a code, and every code has exactly one help topic explaining what happened and what to do about it.
Take a place in the first installs
Klinira is being built now. Leave your details and you will hear what is finished, be asked what your clinic actually needs, and get the first install dates when it is ready.