Prescription Format in India: NMC Rules and Sample Layout
Review NMC prescription provisions, an annotated OPD format, a two-doctor document audit and reprint checks that preserve the original issued copy.
A clinic medicine search should help a doctor find a familiar brand while keeping the selected ingredients, strength, dosage form and release characteristics visible. A matching name is a search result, not proof that two products are interchangeable. Resolve an uncertain formulation before issuing the prescription, and retain the identity actually selected in the encounter record.
Indian doctors and clinic managers organizing brand and generic medicine searches, shared favourites and prescription catalogues.
During a busy OPD, a doctor may remember a brand, a patient may bring a partly used strip, and the clinic catalogue may organize medicines under ingredients. These are three entry points into the same conversation. Search can connect them, but the connection needs enough information to establish which product is being discussed.
Treat the typed phrase as an alias: a route to possible matches. Treat the complete medicine entry as an identity: ingredients, strength, form and relevant release details. Treat suitability or substitution as a clinical decision. When these layers collapse into one autocomplete action, an almost-correct name can silently become a different prescription.
WHO describes look-alike and sound-alike confusion involving medicine names. This supports making similar candidates distinguishable; it does not establish that every product with the same ingredient is interchangeable. The workflow below is an original catalogue-management proposal, not a list of equivalent Indian brands.
Source: WHO: Medication safety for look-alike, sound-alike medicines
Display the information that can change the selection without requiring the doctor to open several detail screens. A long brand name with a strength hidden beyond a narrow dropdown is a poor match for the actual decision. On phones, allow the candidate to wrap rather than remove the distinguishing ending.
For a combination, preserve each component and its associated strength. A single total-strength field cannot explain which ingredient contributes which amount. Where source information is incomplete, show the unresolved field explicitly. Do not display an apparently complete entry assembled from assumptions about the most commonly sold pack.
On a narrow screen, scroll the table horizontally to read all columns.
| Visible detail | What it resolves | If it is missing |
|---|---|---|
| Brand and generic identity | Whether the searched name maps to the intended ingredient or combination | Keep it as an unresolved candidate |
| Strength with units and basis | Amount per tablet, capsule or stated liquid volume | Do not borrow a strength from another result |
| Dosage form and release qualifier | Distinctions such as liquid versus tablet or a specified release form | Ask the clinician to resolve the formulation |
| Manufacturer or product source when needed | Which labelled product supports the catalogue entry | Check reliable product information |
| Catalogue status and verification date | Whether the item is active, under review or retired | Prevent an old favourite bypassing review |
Consider a fictional training catalogue, not real medicines: the alias “Luma” returns Ingredient Q 100 mg tablet, Ingredient Q 200 mg tablet and Ingredient Q 100 mg modified-release tablet. An additional “Luma Plus” result contains Q together with Ingredient R. The first letters are useful for finding the family, but none of the four results can stand in for the others on the basis of the alias alone.
The doctor intending the first entry should see why it differs from the other three before selecting it. A keyboard shortcut that accepts the first row merely because it is popular creates an accidental default. A safer interaction leaves the candidate list visible until the doctor makes a deliberate selection and then shows the complete identity in the prescription draft.
Now change the example: a patient reports “Luma, the small white one” without a strip. Record the reported name and uncertainty in medication history. Do not force that statement into the first available catalogue item. Finding a plausible result is not confirmation of what the patient has actually taken.
The following is a fictional catalogue exercise. L-101 to L-104 are invented identifiers, Q and R are invented ingredients, and the amounts describe product identity only; they are not treatment recommendations. Assume the catalogue reviewer has checked a complete source label for each entry. In an actual clinic, a partial or unverified label would not justify marking those fields confirmed.
The same typed alias returns four candidates. Preserve the relationship between each ingredient, its strength and the basis of that strength. A generic-name search for Q can legitimately return the combination as a candidate, provided the additional ingredient remains prominent. Returning that row is different from selecting it. A combination must not look like the single-ingredient entry simply because both contain Q.
When a brand is written in a local script or transliterated into English, the search alias can help locate this same candidate list. The spelling variant should not create another medicine identity or imply that an uncertain sound matches one particular product. Keep the original reported spelling alongside any proposed catalogue match until the source is resolved.
On a narrow screen, scroll the table horizontally to read all columns.
| Catalogue candidate | Source-supported identity | Distinction to keep visible | Selection boundary |
|---|---|---|---|
| L-101 — Luma | Q 100 mg per tablet; tablet; no modified-release designation in the exercise source | The complete source description, not just Q 100 | A name match does not decide patient suitability |
| L-102 — Luma | Q 200 mg per tablet; tablet | Different strength from L-101 | Do not carry L-101 instructions into this choice without review |
| L-103 — Luma | Q 100 mg per tablet; modified-release tablet | Release qualifier distinguishes it from L-101 | Do not collapse the two entries because ingredient and number match |
| L-104 — Luma Plus | Q 100 mg and R 10 mg per tablet; combination tablet | Both components and both strengths | Searching Q does not authorize adding R to a prescription |
Start with the known source: a clinician-selected medicine, a labelled pack or a previous prescription that still needs current-use reconciliation. Search by the known name, then compare the identifying fields. Only after identity is resolved should the doctor set patient-specific instructions and approve the issued output.
Keep selection separate from carry-forward. A medicine found on an old prescription may explain past treatment without belonging in the current prescription. Similarly, a search used to record an allergy-related history should not create a new order. The destination field is part of the decision.
After changing a candidate, inspect associated fields. A system may retain an old liquid volume, frequency or instruction from the previous selection. Those values require fresh clinician review; a correct replacement name does not make the inherited instructions correct.
An unlisted item needs a controlled route. The clinician may document the supplied information as free text with an unresolved-catalogue marker, or request a new reviewed entry, depending on the system and the intended use. The workflow must distinguish an incomplete historical report from an issued prescription whose details need to be sufficiently clear.
Assign catalogue creation to a named reviewer rather than allowing every search failure to create a new shared item. Capture the source label or authoritative product information, who checked it and which fields were confirmed. A cropped pack photograph may establish a brand name while omitting the formulation; mark that limitation instead of treating the image as complete evidence.
Reception staff can collect a legible source and route the request. They should not decide that an unavailable catalogue product is clinically equivalent to another. If urgent clinical work cannot wait for catalogue administration, the doctor must retain a clear prescribing and documentation route within the clinic’s established process.
Suppose a patient brings a cropped photograph showing “Luma” and part of a number. The form and release description are outside the image. The receptionist can attach the source to the appropriate record under the clinic’s privacy process and note what is visible. Assigning L-101 because it is the most frequently used result would turn a guess into apparently verified history.
A useful handover states which fact is missing and who can resolve it. “Please add medicine” is too vague: an administrator might create a duplicate catalogue item, while a doctor might assume the identity has already been checked. Request a complete legible label or other reliable product information and identify the clinician who will reconcile the history. A patient recalling a different name later is new information to assess, not a reason to erase the earlier report.
The completed example below concerns historical identification. It does not postpone necessary clinical assessment or authorize an incomplete prescription. If the doctor needs to prescribe during the consultation, that is a separate decision with its own complete identity and instructions. Recording what was reported and deciding what to prescribe should remain distinguishable in the chart.
In a fictional draft, the doctor selects L-101 and begins entering instructions, then realizes the intended catalogue candidate was L-103. The identity change is visible, but the old directions may still look complete. A successful search has only corrected the selected product; it has not reviewed the content that followed the earlier selection.
Ask the software demonstrator to show the actual behaviour. Does the change clear dependent fields, retain them with an explicit review state, or silently preserve them as ready to issue? The first two approaches still need a workable clinician review; clearing everything without explanation can also cause omissions. The key evidence is whether the doctor can see what came from the prior selection and approve the current output deliberately.
Rehearse the reverse journey as well: leave the draft, reopen it and inspect the printed or downloaded representation. The selected identifier, visible medicine description and clinician-approved directions should describe the same decision. A reassuring detail panel is insufficient if the final PDF drops the release qualifier. Record an unresolved mismatch as a failed rehearsal even if the search result itself was correct.
On a narrow screen, scroll the table horizontally to read all columns.
| Draft element | Before replacement | Review after replacement | Evidence at issuing |
|---|---|---|---|
| Medicine identity | L-101, Q 100 mg tablet | Doctor explicitly selects L-103, Q 100 mg modified-release tablet | Final visible identity agrees with the selected entry |
| Dose, route, frequency and duration | Values entered for the earlier selection | Clinician determines the appropriate instructions; no transfer presumed valid | Only the reviewed instructions appear |
| Advice and free text | May mention the earlier formulation | Read for stale wording or contradictions | No abandoned-product wording remains in the approved output |
| Review status and history | Earlier selection was reviewed or partly edited | New selection cannot inherit proof of completed review | Preserve what changed and the actual approving action |
Use a stable internal identifier for each reviewed entry. Search aliases can include a verified brand spelling, an accepted abbreviation or a documented transliteration, but each alias should point to a reviewable candidate set. An ambiguous shortcut should return choices rather than conceal its ambiguity.
Keep a record of catalogue changes. Correcting a spelling in the search index is different from discovering that an entry had the wrong ingredient. The latter requires an impact review of favourites, saved sets and affected records. Do not simply rename the underlying item and make old issued prescriptions appear to have contained the new information all along.
A retired entry should remain interpretable in historical records while being unavailable for routine new selection. The retirement reason matters: duplicate catalogue entry, product-information correction, local formulary decision and a product safety notice call for different follow-up. One generic “inactive” flag cannot explain all four.
Try a small, reviewed set of fictional searches representing the clinic’s work: exact brand, ingredient, combination, misspelling, similar name, multiple strengths and an intentionally unlisted item. Record whether the intended candidate was found, whether it was distinguishable and whether any detail changed on issuing. Search speed alone misses the most consequential failures.
For example, finding all 12 intended items in a 12-case exercise is a retrieval result. If two searches select the wrong formulation, the exercise has only 10 correct final selections. Report both observations and the nature of the errors. This local exercise does not establish a general safety rate.
Keep three denominators in the exercise log: intended candidates found, intended candidates selected and complete identities preserved in issued output. If the two incorrect selections are both formulation errors, describe them as such; do not spread them across unrelated fields to produce a more flattering percentage. An intentionally unlisted case should be assessed on whether uncertainty was preserved, rather than counted as a retrieval failure that staff must “fix” by choosing something.
Use the failures to improve the display, alias mapping or review workflow. Avoid solving every problem by moving a popular result to the top: ranking may help one doctor and increase mistaken selection for another. Recheck shared favourites after a meaningful catalogue update.
A search-index correction can affect several entry routes: typing a full brand, using a shorthand, choosing a favourite and importing a saved set. For the Luma exercise, write down which candidate identifiers each route should expose. Repeating the same full-name search four times does not test the other routes. Include a misspelling and the local transliteration actually used by staff, without treating fuzzy matching as product verification.
Keep a before-and-after example for the changed alias, the reviewed catalogue version and the person accepting the change. Test on a narrow screen where distinguishing endings may be truncated, and with the keyboard shortcut doctors use during OPD. The outcome should be a visible, deliberate selection rather than a surprise first-result acceptance. If a stale favourite still opens the old identity, the correction is incomplete for that route.
This exercise helps the clinic ask concrete questions in a vendor demonstration. It does not establish that Bractis or any other product currently supports every proposed control. Ask to see the available workflow, its gaps and the responsible manual step for each gap before relying on it in patient care.
In a fictional two-doctor clinic, “Luma” initially opens one preferred tablet automatically. The clinic changes it to a search alias returning four fully labelled candidates. Doctors still reach the familiar name quickly, but each selection preserves its own strength and formulation. A patient-reported “Luma” without a pack remains an uncertain history item until clarified; the search does not manufacture confirmation.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
A verified transliteration can help retrieve candidates. It does not resolve missing strength, ingredients, form or release details. Retain the patient’s reported name and source uncertainty until a qualified reviewer confirms the identity.
The doctor must review instructions that depended on the earlier selection. They may be cleared or retained visibly for review, but should not silently inherit approval. Check the complete final prescription, including formulation and free-text advice.
Yes. A verified brand can be an alias that returns a complete ingredient-based identity with strength and formulation. The alias should not hide combinations or automatically choose among different products.
No. Strength, dosage form, release characteristics and patient-specific considerations can matter. Search grouping is not authorization to substitute.
Keep the supplied information and uncertainty visible, obtain reliable product details and use a controlled catalogue review. Do not select the nearest-looking item to satisfy a required field.
No. A favourite is a convenience reference. It should expose the current entry status and require review when the underlying identity or availability has changed.
No. Search design and prescription requirements are different questions. Review applicable prescribing provisions and the final output; the linked Indian prescription-format guide explains the published NMC context.
Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.
Published 20 October 2023; publication overview checked 28 October 2026 for brand/brand, brand/generic and generic/generic name-confusion context. The fictional identities, source card, replacement matrix and rehearsal are original operational analysis, not WHO-endorsed treatment or substitution guidance.
Review NMC prescription provisions, an annotated OPD format, a two-doctor document audit and reprint checks that preserve the original issued copy.
Build a shared clinic formulary using a worked intake review, change-impact ledger and handover for favourites, saved sets, drafts and issued prescriptions.
Compare medicine strips, discharge papers and reported use with a three-source case, Hindi intake question and discrepancy handover.
Assess AI medicine recognition with mapping cases and a worked twenty-entry comparison across generation, clinician correction and final prescription rendering.
Use a fictional brand alias with several strengths and a deliberately unlisted item to discuss how medicine identity, favourites and final prescription output behave in the available Bractis workflow.
Request a clinic demo