Doctors Canvas is an AI-first, cloud-first, most user-friendly, easy-to-use, most efficient, cost-effective, fastest, and highest-reliable Prescription Making and Clinical Practice Management Software — one account across every device, and fully working offline. The patient record is the part that is worthless on day one and indispensable by month three.
Key takeaways
- A patient management system is judged on the second visit — the first one only puts data in.
- Identity is the foundation: mobile number plus DGHS Health ID, so a changed SIM does not create a duplicate patient.
- The record has to hold the visit timeline, vitals trends and the complete prescription history, not a folder of documents.
- Structured prescriptions are what make allergy and interaction checking possible at all.
- One record across all chambers, or a multi-location doctor accumulates partial histories.
- Cloud-first, offline-proof storage, because a record you cannot open during load shedding is not available when you need it.
Identity is the whole foundation
Every other property of a patient management system rests on one question: when this person comes back in four months, will the software know they are the same person? Get that wrong and the timeline fragments, the vitals trend restarts, and the prescription history is split across records that nobody will ever reconcile.
Mobile number is the obvious handle and an unreliable one on its own, because numbers change and families share them. The DGHS Health ID is the stable identifier, which is why it belongs on the record from the first visit rather than being added when somebody remembers. Capturing both gives you two ways to find the same person and a way to notice when they have become two.
In a clinic with several consulting doctors this matters even more, because a patient referred internally should arrive at the second doctor with their history rather than as a new registration. Per-doctor record silos are the path of least resistance for a vendor to build and the most expensive thing for a polyclinic to live with.
What the record has to hold
Six things, all of which have to be queryable rather than merely stored.
The visit timeline
Every consultation in order, with its date and diagnosis, so the history reads as a sequence rather than a pile.
Vitals trends
Blood pressure, temperature and blood glucose across visits. A single reading is a number; a trend is information.
Prescription history
What was prescribed, at what dose, for how long, and when — as structured drugs rather than an attached document.
Recorded allergies
The thing the pre-save allergy check checks against. It can only protect against what it has been told.
Identity
Mobile number and DGHS Health ID, so the same person resolves to the same record across visits and chambers.
Chamber context
Which location a visit happened at, as an attribute of the visit rather than a separate universe.
Device independence
The record belongs to the account, not to the machine it was typed on. Signing in elsewhere shows the same history — which is what makes a phone usable for a ward round without creating a second version of the patient.
Why a document store is not a patient record
Plenty of systems satisfy the letter of the requirement by attaching a PDF of each prescription to the patient. It looks complete and it is nearly useless, because a document is opaque to the software that holds it. It cannot tell you what the patient has been prescribed over the past year, cannot check a new prescription against an old one, and cannot surface an allergy at the moment it matters.
The test is simple. Open a patient with several visits and ask the system a question — what have I prescribed this person, what has their blood pressure done, when did they last come in. If those are answers rather than a reading exercise, the record is structured. If you are opening attachments one at a time, it is a filing cabinet with a search box.
This is also why prescribing and record-keeping should not be separate products joined by a patient name. The interaction and allergy checks that make prescribing safer are only possible because the prescription is structured data on the same record that holds the allergies.
The offline requirement applies to records too
It is easy to think of offline capability as a prescribing concern — can I write and print during load shedding. It applies just as strongly to the record, and arguably more so: a patient history you cannot open is not a history, and the moment you most want it is the moment you are consulting, which is precisely when a connection failure stops you.
Cloud-first, offline-proof on IndexedDB means the patient database lives on the device and syncs automatically when connectivity returns. Opening a patient, reading their timeline, checking their vitals trend and reviewing what you prescribed last time all happen locally.
The security posture that sits over it matters as much: AES-256 encryption at rest, TLS in transit, role-based access control, and daily automated backups. On-device data without encryption at rest would be a different and worse trade.
Who should see what
A clinic patient record is read by more people than the doctor who wrote it, and the access question is where most clinic systems are either too coarse or too restrictive. Too coarse and your receptionist can read clinical notes. Too restrictive and they cannot register a patient or record vitals, so the intake half of the workflow stays on paper.
The workable split is role-based: staff and attendant profiles handle serial, schedule and patient management, while clinical notes sit outside that scope. That is what lets you delegate registration and vitals capture without a privacy concern, which is in turn what makes the parallel front-desk workflow possible.
Ask to see this rather than take it on trust. Log in as the receptionist during an evaluation and look at what is on the screen — it is a two-minute check that settles a question most demonstrations never raise.
What good record hygiene looks like in practice
A patient management system will faithfully record whatever habits the chamber has, including bad ones. Three habits do most of the work, and none of them require anyone to be conscientious in the moment — they work because they are part of the intake routine rather than a decision.
Capture the DGHS Health ID at registration every time, not only when it seems relevant. Record vitals on every patient rather than only on the ones who prompted concern, because a vitals trend only exists if the readings were taken when nothing appeared to be wrong. And record allergies as they are mentioned, since the pre-save allergy check is only as good as what it has been told, and the visit where it matters will be one where nobody thinks to raise it.
All three belong at the front desk rather than in the consultation, which is the argument for getting staff accounts running early. Habits that depend on the doctor remembering during a hundred-patient evening are habits that will not survive the evening.
The one field worth being strict about
The DGHS Health ID. It costs seconds at registration and it is the only thing standing between you and a duplicate record when a patient changes their phone number — which is the single most common way a carefully kept history quietly splits in two.
Frequently asked questions
Do I have to enter my existing paper records?
No. History builds forward from the first digital visit, and becomes genuinely useful within a couple of months of routine use. Back-entry is a large cost with a small return, because most of the value is in recent history.
What if a patient changes their phone number?
This is the usual cause of duplicate records. Searching by DGHS Health ID resolves it, which is why the Health ID is captured and stored on every patient record from the first visit.
Is the record shared across my chambers?
Yes. Chambers are unlimited with independent schedules under one login, and the patient record is shared across all of them, so a patient seen at one location is not a stranger at the next.
Can patients see their own records?
Patients can book and manage their own appointments through the patient portal today. Full prescription and medical-history access inside that portal is in development rather than available.
How is the data protected?
AES-256 encryption at rest, TLS in transit, role-based access control, and daily automated backups.
What happens to records during load shedding?
They stay available. The patient database is on-device in IndexedDB and syncs when connectivity returns, so you can open and read a patient history with no connection at all.
How do I tell whether a system stores records or just files?
Open a patient with several visits and ask the system a question — what have I prescribed this person, what has their blood pressure done, when did they last attend. If those come back as answers, the record is structured. If you are opening attachments one at a time, it is a filing cabinet with a search box, and none of the checking or trending that makes a record clinically useful is possible on top of it.
Should reception be able to create patient records?
Yes, and the workflow depends on it. Registration and vitals capture at check-in are what let a consultation start with the record already open and the numbers already on screen. Role-based access makes the delegation safe: staff profiles cover serial, schedule and patient management, and clinical notes sit outside that scope.
Start the record now, use it in month three
The history only accumulates once you begin. Free tier available, BDT pricing published.