A prescription only works if the person holding it understands it. That sounds too obvious to state, and yet the standard Pakistani prescription asks a patient to act on instructions written in a language they may read haltingly, in handwriting they cannot parse, abbreviated in Latin.
"T. Augmentin 625mg BD x 5/7" is perfectly clear to a pharmacist and close to meaningless to a labourer in Gujranwala. The gap between those two readings is where medication errors live — not in the prescribing, but in the hour after the patient leaves your room.
This article covers why Roman Urdu is the right format for dosage instructions, what prescription software has to get right to support it, where it genuinely helps, and where it does nothing at all.
Why Roman Urdu rather than Urdu script
The instinctive answer, when you decide English is not working, is to print in Urdu. In practice Roman Urdu — Urdu written in Latin characters, the way people type on WhatsApp — works better for dosage instructions, for four reasons.
Reading fluency
Many patients who speak Urdu fluently read Urdu script slowly. Formal literacy in Nastaliq is not universal, and a patient who reads it at the pace of a schoolchild will not reliably extract a dosing schedule from it under stress.
Almost everyone with a phone, by contrast, reads Roman Urdu at conversational speed, because that is the register they already use for messaging. You are not teaching the patient a new format. You are writing in the one they use every day.
Rendering and printing
Urdu script is cursive and context-sensitive: letterforms change depending on their neighbours. It renders poorly on cheap thermal printers, inconsistently across devices, and badly in any system whose font handling was not designed for it.
Latin characters survive all of that. A Roman Urdu instruction prints identically on a thermal roll, a laser printer and a WhatsApp message, which matters because those are the three places your prescription ends up.
Mixed content without a script change
A prescription is inherently bilingual. The medicine name stays in English — that is what the pharmacy stocks, what the box says, and what the pharmacist recognises. Only the instruction needs translating.
Roman Urdu sits beside English on the same line without a script direction change. Urdu script does not: you get a right-to-left run embedded in a left-to-right line, which is where layouts break and characters reverse.
It matches how the instruction is spoken
When you explain a dose verbally, you say "khana ke baad". Writing it the same way means the printed instruction matches what the patient heard, which is a surprisingly large part of whether it is followed.
What this looks like in practice
The difference is easiest to see across three versions of the same prescription line.
| Written as | What the patient takes from it | Likely outcome |
|---|---|---|
| T. Augmentin 625mg BD x 5/7 | Almost nothing | Asks the pharmacist, or guesses |
| Augmentin 625mg, twice daily, 5 days | Partially — often misses food timing | Takes it, but not with food |
| Augmentin 625mg — khana ke baad, din mein do baar, 5 din poora karein | All of it | Takes it correctly, finishes the course |
The third version takes no longer to produce than the first, provided the software carries a dosage library. The doctor selects "khana ke baad, din mein do baar" from a list rather than typing it, and the prescription prints with the medicine in English and the instruction in Roman Urdu.
The goal is not to translate the prescription. It is to translate the instructions. Medicine name, strength and form stay exactly as the pharmacist expects. What changes is only the part the patient has to act on alone, at home, without you.
What to look for in the prescription module
A dosage library you can edit
The phrases that matter are few. Before food, after food, empty stomach, once daily, twice daily, three times daily, at bedtime, as needed, finish the full course, stop if rash appears. Twenty or so entries cover the vast majority of what you write.
If the software ships these in Roman Urdu and lets you edit the wording to match how you actually speak to patients, the feature works. If you have to type the instruction every time, it will quietly stop being used by week three — not through disagreement, but because a seven-minute consultation has no room for optional typing.
Mixed script that does not fight you
The medicine field should stay English while the instruction field accepts Roman Urdu, with no mode switch and no keyboard change. Any system where you toggle language mid-prescription adds friction at precisely the moment you are trying to move faster.
Test this specifically in the demo: write one prescription with four medicines, each with a different instruction. If it takes longer than writing it by hand, the implementation is wrong regardless of what the feature list says.
What prints is what you saw
Whatever appears on screen must be what prints, and what arrives on the patient's WhatsApp. If the pad looks right but the printed copy drops characters or the WhatsApp version arrives mangled, you have a cosmetic feature rather than a working one.
Test this on your own printer before you commit, not the vendor's. Thermal printers vary, and character handling is exactly the kind of thing that works in a demo environment and fails on a four-year-old receipt printer in Faisalabad.
Translation that fails safely
Some systems offer automatic translation from English into Roman Urdu. It is genuinely useful and it must never be silent.
Automatic translation of clinical instructions should show the doctor what it produced before printing, so an odd rendering gets caught in the consulting room rather than at the patient's home. A system that translates invisibly is one bad translation away from a patient taking a drug the wrong way, with your name on the prescription.
Any automated translation of a dosage instruction should be visible to the prescriber before it prints. Silent translation of clinical text is a patient-safety problem wearing a convenience feature's clothes.
It carries through to the pharmacy label
If you dispense, check that the Roman Urdu instruction reaches the dispensing label too, not just the prescription. A patient who receives a correctly worded prescription and a box labelled only in English has gained half the benefit.
A starter library you can copy
If you are building the list from scratch, these cover most of what a general practice writes in a week. Edit the wording to match how you speak.
| English | Roman Urdu |
|---|---|
| Once daily | Din mein ek baar |
| Twice daily | Din mein do baar |
| Three times daily | Din mein teen baar |
| After food | Khana ke baad |
| Before food | Khana se pehle |
| Empty stomach | Khali pait |
| At bedtime | Sone se pehle |
| Only if needed | Sirf zaroorat par |
| Finish the full course | Poora course khatam karein |
| Stop and call us if a rash appears | Rash ho to band karein aur hamein batayein |
What it actually changes
The honest claim is modest and worth having.
- Fewer questions at the pharmacy counter, because the instruction does not need interpreting.
- Fewer follow-up calls asking how to take something, which is time your reception desk gets back.
- Better adherence on courses that must be finished — antibiotics above all.
- Faster confirmation in the room: you can ask the patient to read the instruction back in ten seconds.
That last one is underrated. When the instruction is printed in a form the patient can read aloud, confirming understanding takes a moment rather than a repeated explanation in two languages. It also surfaces the patients who cannot read at all, which is information you want before they leave rather than after.
The antibiotic case specifically
The difference between a patient stopping at day three because they feel better and finishing a five-day course is partly a function of whether "5 din poora karein" was legible and unambiguous.
No prescription format fixes antimicrobial resistance. But incomplete courses driven by misread instructions are a contributing cause that is unusually cheap to address, and it is addressed at the point of printing rather than through patient education campaigns.
Where Roman Urdu does not help
Overstating this would be a disservice, so here is the honest boundary.
It does not fix a prescription that is clinically wrong. A correct instruction for the wrong drug is still the wrong drug, and legibility makes an error easier to follow rather than less likely.
It does not replace explaining a complicated regimen. A patient on five medicines with staggered timings, some with food and some without, needs a conversation and a written schedule — not a cleverer prescription format. For that group, a printed daily timetable is worth more than any dosage library.
And it does not help a patient who cannot read at all, which in parts of rural Pakistan is a meaningful proportion. For them the answer is a pictorial dosage chart, a family member briefed at the counter, or both. Software does not substitute for either.
Getting it into your clinic
If you already run clinic software
Check whether the prescription module already has a Roman Urdu dosage library before assuming it does not. A surprising number of systems ship one that nobody ever enabled, because it sits behind a settings page the clinic never opened.
If it exists, spend an hour editing the default phrases into your own wording. The library is far more likely to be used if it sounds like you.
If you are choosing a system
Put it on the demo checklist. Ask the vendor to write a live prescription with Roman Urdu instructions, print it on your printer, and send it to your WhatsApp while you watch. Three minutes of demo answers what a feature list cannot.
The wider evaluation framework is in the 2026 buying guide, which covers the other four Pakistan-specific requirements imported software tends to miss.
Rolling it out
Configure it in the second week of your rollout rather than later — establishing it as the default from the start is far easier than retrofitting it onto an existing habit. The sequence is in how to set up a clinic management system.
For the broader case against handwritten pads, see digital prescriptions versus handwritten scripts. Urdu-speaking readers may prefer our Roman Urdu walkthrough of the same topic.
Templates and prescription format
Most of the speed gain in Roman Urdu prescribing comes from not typing the same instruction again. A reusable Urdu prescription template — a saved set of the twenty or thirty dosage lines you actually use — turns a typing task into a selection task, and selection is both faster and less error-prone.
The clinic prescription format in Pakistan is not standardised, but a workable one puts the clinic name, doctor name and PMDC registration at the top, the patient's name, age and date below it, medicines with strength and quantity in English, the dosage instruction in Roman Urdu, and the follow-up date at the bottom.
Keep the template editable
A template that cannot be adjusted in the moment becomes a constraint rather than a help. The doctor should be able to pick the standard line and then change the duration without leaving the prescription.
Frequently asked questions
- What is Roman Urdu prescription software?
- It is prescription software that lets the doctor write dosage instructions in Roman Urdu — Urdu written in Latin characters, the way people type on WhatsApp — while keeping the medicine name, strength and form in English. The pharmacist still reads a familiar English drug name; the patient reads an instruction like "khana ke baad, din mein do baar" in a script they parse at conversational speed.
- Why not just print prescriptions in Urdu script instead?
- Three practical reasons. Many patients who speak Urdu fluently read Nastaliq slowly. Urdu script renders poorly on cheap thermal printers and inconsistently across devices. And a prescription is bilingual by nature — the medicine name must stay in English — so Urdu script forces a right-to-left run inside a left-to-right line, which is where layouts break. Roman Urdu avoids all three.
- Does writing prescriptions in Roman Urdu take longer?
- Not if the software has an editable dosage library. The doctor selects a phrase rather than typing it, so a prescription takes about the same time as a handwritten one and often less. If your system requires typing the instruction each time, it will stop being used within a few weeks — that is an implementation problem, not a language one.
- Can prescription software translate English instructions automatically?
- Some systems do, and it is useful, but it must show the doctor the result before printing. Silent automatic translation of clinical instructions is a patient-safety risk: an odd rendering should be caught in the consulting room, not discovered at the patient's home. Treat visible review as a requirement rather than a preference.
- Does Roman Urdu actually improve whether patients take medicines correctly?
- It helps most with instructions patients otherwise misread — food timing, frequency, and finishing a full course. The clearest case is antibiotics, where stopping early because symptoms improve is common and partly driven by unclear instructions. It does not help patients who cannot read at all; those need a pictorial chart or a family member briefed at the counter.
- How do I write prescriptions in Roman Urdu for patients?
- Write the medicine name and strength in English, because that is what the pharmacist dispenses from, and the dosage instruction in Roman Urdu, because that is what the patient reads at home. 'Subah aur shaam khanay ke baad, 5 din' is understood by a patient who cannot read English and cannot read Urdu script. Keeping a reusable set of common instructions means it is selected rather than typed each time.
- What prescription software supports Urdu and Roman Urdu?
- Check three things rather than the claim: whether Roman Urdu instructions can be saved and reused rather than retyped, whether they print correctly on your actual printer without font substitution turning the text into boxes, and whether the medicine name stays in English while the instruction is in Roman Urdu. Many systems accept the characters and then break at the printer, which you only discover in front of a patient.
- Prescriptions
- Roman Urdu
- E-Prescribing
- Patient safety
- Adherence
SehatDoc in your city
Local pages with the practice context for each city.