Brand and Generic Medicine Search: A Guide for Indian Clinics
Compare brand and generic medicine candidates, resolve incomplete pack details and review inherited instructions with worked examples for Indian clinics.
A shared clinic formulary is a reviewed list of medicine entries with a defined scope, owner and change process. It is different from stock on the shelf, a doctor’s favourites and a list of medicines suitable for every patient. Start with a manageable catalogue, preserve complete product identity, and control how additions, withdrawals and corrections reach saved sets and new prescriptions.
Indian clinic owners, doctors and authorized pharmacy teams moving from separate medicine favourites to a maintained shared catalogue.
A clinic can have a searchable catalogue, a locally reviewed formulary, current inventory and personal favourites at the same time. Confusion begins when all four are called the “medicine list”. A stock purchase can then make a medicine appear clinically preferred, or a favourite can keep an item selectable after the clinic has withdrawn it from routine use.
Define the formulary’s purpose before cleaning the database. A single-specialty clinic may need a tightly scoped list of reviewed entries; a group practice may need specialty-specific views. Neither arrangement means that every listed medicine is suitable for every patient or that prescribing outside the list is automatically inappropriate. Decide how exceptions reach the responsible clinician.
ASHP’s published guidance on electronic order entry discusses maintaining medication content and the risks associated with defaults. Its hospital context is different from a small Indian OPD. The lifecycle and change-impact process here are original proposals for a clinic, not an assertion that that guidance creates an Indian legal requirement.
On a narrow screen, scroll the table horizontally to read all columns.
| List | Question it answers | What it cannot establish |
|---|---|---|
| Medicine catalogue | What identifiable entries can the system represent? | That every entry is locally reviewed or available |
| Clinic formulary | Which entries are reviewed for a defined local scope? | That an entry suits this particular patient |
| Inventory | Which batches and quantities are physically available? | That an available product should replace another |
| Personal favourites | Which entries does this clinician want to find quickly? | That an old selection remains current or approved |
Collect the medicine entries currently used by the participating doctors and, where applicable, the dispensary. Use this material to discover duplicate spellings, missing strengths and different formulations hidden under one name. Frequency helps prioritize review; it is not evidence that the item is clinically appropriate.
For each proposed entry, confirm ingredients, strength and units, dosage form, relevant release details and a reliable product-information source. For combinations, retain the component-level information. Keep an unresolved queue for entries that cannot be verified. Deleting uncertainty from the spreadsheet by filling a likely value merely moves the risk into the prescription screen.
Choose a first scope that someone can maintain. For example, a fictional three-doctor clinic can start with the entries needed for its existing consultation workflows and leave additional proposals pending. Announce the scope clearly so a missing item is understood as “not yet reviewed for this catalogue”, rather than “clinically forbidden”.
In a fictional three-doctor OPD, staff combine favourites into 14 proposed rows. The reviewer finds eight distinct entries with verified identity and approved local scope, three duplicate rows referring to those eight, two incompletely identified products and one fully identified product whose proposed use falls outside the first release’s reviewed scope. These are four different outcomes. A bulk import that turns every row green would hide the actual work still required.
Resolve duplicates using the complete product identity, not just an ingredient or matching brand prefix. Different strengths or release descriptions must not be merged merely to reduce the row count. When two records truly represent the same reviewed entry, retain the mapping from their old identifiers and aliases to the maintained identity. Review the downstream effect of that mapping before replacing active shortcuts.
The resulting first release contains eight approved entries. The three duplicate proposals add no new identity; the other three proposals remain unresolved for different reasons. Two need product evidence, while one needs a decision about clinical scope. Keeping those queues distinct lets an administrator request a complete label without accidentally claiming authority to approve the proposed clinical use.
On a narrow screen, scroll the table horizontally to read all columns.
| Proposal outcome | Rows | First-release treatment | Evidence needed to close the proposal |
|---|---|---|---|
| Verified identity and approved local scope | 8 | Eight maintained entries available for the stated scope | Source identity, clinical decision and accountable owner |
| Duplicates of those verified entries | 3 | No additional active identity; preserve reviewed mappings | Full identity comparison and check of dependent references |
| Incomplete product identity | 2 | Pending verification; no guessed strength or formulation | Reliable missing product information and reviewer acceptance |
| Identity verified; local scope undecided | 1 | Pending clinical decision rather than a data-entry correction | Clinical owner’s inclusion, restriction or rejection decision |
Appoint a clinical owner for the formulary and a person responsible for catalogue administration. Those roles may overlap in a small clinic, but they involve different decisions. Administrative staff can enter verified information; clinical inclusion, restrictions and prescribing decisions need appropriately qualified responsibility.
When proposing an addition, record why it is needed, which patients or service it concerns and what supporting information the reviewer considered. A supplier’s promotion, a purchasing discount or a frequent search miss can trigger a proposal, but should not silently settle the clinical decision. Keep commercial availability separate from the review outcome.
Use a short decision vocabulary: proposed, needs information, approved for the stated scope, restricted, retired. “Approved” should identify who approved what, and when. Without that scope, staff may interpret a data-quality check as clinical endorsement or mistake a local choice for national guidance.
Give each medicine identity a stable identifier, and record the version of the formulary in which it becomes available. Correcting a harmless display spelling may not require a new medicine identity. Changing an ingredient, strength or formulation does require careful review of whether the old and new entries represent different things.
Do not overwrite an issued prescription merely because a catalogue entry was edited. The historical record needs to show what was selected and issued at the time. If that historical selection was wrong, use the clinic’s prescription-correction process and assess the affected patient records; a quiet catalogue rename is not an adequate correction.
Retirement also needs a reason and an effective date. A duplicate entry retired after mapping to a verified replacement is different from an item placed under review because its information is uncertain. Keep the old identity available for historical interpretation while controlling new use according to the decision.
In a fictional clinic, entry M-014 is found to have an incorrectly recorded formulation. It appears in three saved prescription sets and eight personal favourites. That creates 11 configuration references to inspect; it does not mean 11 patients were affected. Issued prescriptions and open drafts are separate populations that need their own search and review.
The clinical owner decides how to handle the erroneous entry and any affected records. The catalogue administrator updates or disables the relevant references and records the outcome. A saved set that still contains the old identifier must not bypass the change simply because the doctor opens it from a shortcut.
For open drafts, show that source content has changed and require review of the affected medicine and instructions. Do not silently replace one formulation with another. For issued records, preserve the original and use an explicit clinical correction and communication workflow if indicated.
Continue the fictional M-014 formulation correction. A search of the defined clinic workspace finds three saved sets, eight personal favourites, four open drafts and six issued prescriptions containing the affected identity. The six issued prescriptions belong to five distinct fictional patients because one patient has two records. The figures describe discovered references; they do not prove exposure, ingestion, injury or even that every selected draft item was issued.
Record how the search was performed and what it covered. A report limited to shared sets will miss personal copies. A search of current catalogue labels may miss the old wording on an issued document. Use the previous identifier and known aliases where supported, and note exports, archived records or branches outside the search. “No more matches” means no more within that coverage, not a guarantee that every historical use has been found.
The ledger below is a hypothetical checkpoint after initial work, not a clinical incident report. Configuration containment and record review proceed on their own tracks. Two blocked favourites can prevent routine new selection while their owners review them; that does not close the remaining open draft or decide the response to issued prescriptions. The clinical owner should determine the urgency of those reviews from the actual error and context.
On a narrow screen, scroll the table horizontally to read all columns.
| Population found | Count | Checkpoint in the exercise | What remains unresolved |
|---|---|---|---|
| Saved prescription sets | 3 | 2 reviewed versions released; 1 set paused | Owner must approve or retire the paused set |
| Personal favourites | 8 | 6 verified references repaired; 2 blocked for routine new selection | Two owners still need to review their shortcuts |
| Open prescription drafts | 4 | 2 clinically adapted; 1 duplicate draft explicitly discarded; 1 awaiting review | One draft remains assigned to the responsible doctor |
| Issued prescriptions | 6 records / 5 distinct patients | Historical output preserved; clinical review assigned separately | Record-specific decisions and any indicated patient follow-through |
A catalogue administrator can confirm that a corrected field appears in the master list. That is only one acceptance check. A doctor should then try a normal search, a personal favourite and each affected shared set in fictional encounters. Include a saved draft created before the change. An old reference that still opens silently is a different failure from a new search showing the wrong label.
Use a named decision for each unresolved route: pause the set, block routine selection of a shortcut, or keep an existing draft visibly awaiting review. Explain the available alternative workflow so a clinician is not forced to bypass the control to finish a consultation. Administrative containment does not authorize replacing a patient’s medicine, and a successful software check does not approve treatment.
If the change has to be reversed because the catalogue build is wrong, restore the last verified configuration or pause the affected routes under the clinical owner’s direction. Do not restore the known erroneous identity merely because it was the previous version. Keep the failed release and reversal history, and review anything created while it was available. A rollback of configuration cannot recall documents already issued.
An out-of-stock label describes availability. It does not establish that a nearby item is a suitable substitute. If the clinic dispenses, the authorized team should route a proposed alternative through the applicable clinical and dispensing process. Reception staff should not change a prescription merely to match what is on the shelf.
Keep temporary shortage separate from formulary retirement. A product may remain a valid catalogue entry while being unavailable from the clinic’s supplier. Conversely, plentiful stock does not justify leaving an entry active when the clinical owner has restricted it or an applicable recall affects it.
Record the actual product supplied, where supply occurs within the clinic’s authorized scope, and retain the relationship to the prescribed item. This makes later reconciliation possible without pretending that prescription identity, local stock identity and patient-reported use are always identical.
A visiting consultant may want a shorter favourites list than the resident doctor. A second branch may stock different packs. Those differences do not require each team to maintain an unrelated copy of the same medicine identity. Where the system supports it, keep shared verified identity underneath personal or branch-specific views, with separate ownership for stock and clinical scope.
Distinguish a view from a copied record during the demonstration. If the consultant’s favourite points to the maintained identity, a status change can remain visible. If it is a detached text copy, updating the shared entry may have no effect. Ask the consultant to open a previously saved favourite after a fictional change and show how the change reaches them. Document a manual review route where that link does not exist.
At owner handover, pass on unresolved proposals, pending clinical decisions, paused sets and the location of supporting evidence. A departing doctor’s name in an approval column is historical attribution, not continuing availability to review new requests. Assign the next responsible person explicitly and preserve the earlier decisions. The practical test of a maintained formulary is whether another clinician can explain its limits and open issues without guessing.
Before release, let each participating doctor walk through a few fictional searches and current templates. Include a combination, more than one strength, a retired entry and an item outside the initial scope. Ask staff to show how they request a correction rather than encouraging private workarounds in free text.
After release, review unresolved requests and the reasons clinicians bypass the shared list. Repeated missing-item requests may reveal an incomplete scope; repeated ambiguous matches may reveal poor identity data. Those problems require different changes. A target of zero exceptions can encourage staff to choose the wrong entry just to finish a form.
Measure what the clinic can inspect: proposals awaiting review, active entries lacking verified identity details, and changed entries whose dependent sets remain unresolved. Do not call a large catalogue “complete” or a high adoption percentage “safe”. The purpose is a maintained decision aid whose limits are visible.
Choose a periodic review cadence that the named owner can actually sustain, and add event-triggered review for important product information changes, safety notices and observed errors. Record the next review owner when someone leaves the clinic; an abandoned shared list can become less reliable than a smaller actively maintained one.
A fictional formulation correction affects three saved sets and eight favourites. The clinic repairs those 11 configuration references, then separately investigates open drafts and issued records. This avoids both understating the impact as a simple spelling change and overstating it as 11 patient incidents. Each category has its own owner and evidence of completion.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
No. They count configuration references. Review open drafts and issued prescriptions separately, then identify distinct patients within the relevant records. In the fictional example, 6 issued prescriptions concern 5 patients; neither figure establishes injury or medicine ingestion.
Yes. Product identity can be complete while clinical inclusion or scope is undecided. Keep evidence collection and clinical approval as separate decisions so a data-entry correction does not become an unintended prescribing endorsement.
No. A formulary records reviewed entries and their scope. Inventory records available batches and quantities. Availability alone does not establish clinical suitability.
Use named clinical responsibility for inclusion and scope, with administrative entry based on verified information. Separate a data-entry task from a prescribing or formulary decision.
Yes, if favourites reference maintained identities and expose changes or restrictions. A favourite should not preserve an obsolete entry as an invisible exception.
Do not silently rewrite issued records. Preserve their historical content and investigate affected prescriptions through an explicit correction process where needed.
An unlisted item may simply fall outside the reviewed catalogue scope. Use the clinic’s clinical exception and verification process; do not infer a universal prescribing rule from a local list.
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 2011; publisher text checked 28 October 2026, particularly medication-orderable design and build considerations. Hospital pharmacy guidance supplies limited context on formularies, defaults and maintenance. The 14-row intake, M-014 ledger and small-clinic handover are original examples, not an Indian legal standard or independently reviewed clinical protocol.
Compare brand and generic medicine candidates, resolve incomplete pack details and review inherited instructions with worked examples for Indian clinics.
Review saved prescription sets with worked draft-merging, interruption and version-change examples, plus output checks for doctors in Indian clinics.
Respond to medicine batch alerts with notice matching, return reconciliation and patient-level contact records, including shared phones and uncertain links.
Trace issued prescription corrections through version history, translated copies, queued outputs and recipient-specific communication.
Discuss a fictional formulary change that affects a favourite, a saved set and an existing prescription, and inspect how each is represented in the available Bractis workflow.
Request a clinic demo