Building a Shared Clinic Formulary: Ownership, Versions and Changes
Build a shared clinic formulary using a worked intake review, change-impact ledger and handover for favourites, saved sets, drafts and issued prescriptions.
A doctor’s medicine favourites should make a verified product easier to find without making a prescribing decision for the next patient. Keep medicine identity separate from optional saved directions, identify the owner and source of each shortcut, and review outdated or ambiguous entries. There is no ideal “top 50” list for every Indian clinic. A small, maintained collection that preserves patient-specific review is more useful than a long menu of copied doses and durations.
Indian doctors building personal medicine shortcuts within a clinic formulary or prescription system.
A personal favourite records a doctor’s preferred way to locate an item. A clinic formulary is a governed shared catalogue. A stock list describes what is physically available. These sets can overlap, but membership in one does not establish membership or suitability in another.
A frequently prescribed medicine can be out of stock, and an available product may be inappropriate for the patient. Do not let a favourite badge imply either availability or a clinical recommendation. Show which information comes from the catalogue and which belongs to the doctor’s shortcut.
For a locum or new colleague, keep ownership explicit. Opening another doctor’s favourites may be useful for orientation, but should not silently copy their default amounts or become evidence that the new prescriber has reviewed those defaults.
A useful favourite identifies the intended ingredient or product, strength, dosage form, release characteristics and route as applicable. A nickname such as “usual pain tablet” is too weak to distinguish similar products or combination formulations.
If a catalogue contains several entries for the same brand family, display the distinguishing details at selection. Saving only the brand prefix can place the doctor one click away from an unintended strength or formulation. Where identity remains uncertain, leave the shortcut unavailable for routine reuse until clarified.
Retain the catalogue source and review context. A favourite is a pointer to verified information, not independent evidence that the product is currently authorised, available or clinically appropriate. Changes in the source catalogue need an identifiable path to the shortcut owner.
Saving a medicine and saving a regimen are different actions. A doctor may reasonably want fast access to an item while entering the amount, frequency and duration afresh. If directions are saved, make them visible as proposed defaults that require review in the encounter.
The following model is an original configuration aid. It does not prescribe a medicine or establish which defaults a particular clinic should allow. The key question is what could become wrong when the next patient differs from the one used to create the shortcut.
On a narrow screen, scroll the table horizontally to read all columns.
| Information | Reason to preserve it | Review boundary |
|---|---|---|
| Verified identity | Find the intended item consistently | Recheck when catalogue identity or formulation changes |
| Search alias | Recognise a familiar local term | Alias must not hide ingredients or strength |
| Route or device context | Distinguish materially different administration forms | Confirm against the selected product and patient |
| Suggested directions | Reduce repeated typing where locally appropriate | Remain visible and patient-specific before approval |
| Duration or review text | Offer an editable communication starting point | Never imply a universal course or automatic repeat |
| Owner and version | Resolve questions and trace later changes | Updates must not rewrite issued prescriptions |
The patient may already be taking the same ingredient under another brand, may have stopped a previous course, or may have received a new specialist plan. A familiar favourite should not bypass medication reconciliation or make yesterday’s regimen look current.
WHO’s Five Moments for Medication Safety treats starting, taking, adding, reviewing and stopping medicines as opportunities for patient engagement. The operational implication here is that a convenient selection tool must still leave space for the patient’s actual medicine story and the doctor’s current decision.
Review relevant patient factors through the clinic’s clinical process. A personal default cannot determine whether pregnancy, renal function, allergy history or another circumstance changes the plan. The shortcut should reduce navigation, not silently supply missing assessment.
Source: WHO: Five Moments for Medication Safety, 2019
Source: WHO Quality Toolkit: Five Moments for Medication Safety
Start with a manageable set of items the doctor can maintain. Review duplicates and confusing aliases before adding more. A long list ordered by historic frequency can bury less common but important alternatives and make a recently changed formulation hard to distinguish.
If the system suggests favourites from past prescriptions, inspect whether those records belong to the same clinician and setting. A medicine used during a temporary assignment should not automatically become a permanent personal default. Historical use is a discovery signal, not proof of continuing preference.
Organise the list by a method the doctor can explain, such as consistent names or clearly labelled groups. Avoid a sponsor-influenced position being mistaken for a clinical ranking. The clinic should know who can alter ordering, labels and suggested directions.
Useful triggers include a changed catalogue entry, an amended source instruction, repeated selection errors or the owner deciding that a saved direction is too specific for reuse. A periodic review can catch neglected items, but a known problem should not wait for the next calendar review.
Retire or replace the shortcut while retaining historical references. A prescription issued last month should continue to show the product and directions actually approved then. Changing today’s favourite must not recalculate or relabel that earlier document.
This fictional maintenance case is separate from the ten-shortcut audit below. Dr Sen owns personal favourite F7, version 1. It points to verified catalogue identity M17, revision 4, and includes the alias “usual evening item” plus saved timing and duration text. M17 is a teaching identifier standing for the complete product identity, including ingredient, strength, form, release characteristics and route where relevant. Neither M17 nor any other token in this case is a medicine name suitable for an actual prescription.
During review on 28 October 2026, Dr Sen finds that the alias hides the distinction between M17 and a different-release entry M18. The underlying F7 pointer still identifies M17 correctly. The saved regimen text also originated in an earlier clinical context and is no longer wanted as a personal default. These are two maintenance findings, not evidence that M17 changed formulation or that every prior prescription was wrong. Product verification and patient-specific prescribing remain separate decisions.
At 11:00, Dr Sen publishes F7 version 2 with a clear identity label and no saved timing or duration. Catalogue identity M17, revision 4, is unchanged. The clinic uses English and transliterated Hindi search aliases: familiar wording may remain useful for finding the entry, but the selection display must expose the verified identity. An alias must not silently substitute M18, or supply patient instructions merely because its nickname mentions a time of day.
Two other records need separate treatment. S4 is the clinic’s shared identity-only entry for M17; its owner confirms that it contains no regimen default. L9 is a locum’s independent copy of F7 version 1, created the previous day. Changing Dr Sen’s personal favourite does not establish that L9 changed too. The locum agrees to suspend further use of L9 pending review, while existing drafts retain their contents for assessment. This is a proposed workflow to evaluate locally, not a claim about automatic Bractis synchronisation.
On a narrow screen, scroll the table horizontally to read all columns.
| Record | Confirmed decision in this example | What that decision does not establish |
|---|---|---|
| M17, catalogue revision 4 | Verified product identity retained; M18 remains a distinct entry | No product replacement, stock confirmation or patient-specific suitability decision |
| F7, Dr Sen’s personal favourite | Version 2 replaces the ambiguous display label and removes saved timing and duration | No automatic rewrite of existing encounter copies |
| S4, shared clinic entry | Shared owner confirms identity-only content; no change made | Dr Sen’s personal decision is not a clinic-wide prescribing policy |
| L9, locum’s independent copy | Old default origin identified; locum accepts review and suspends further reuse | Existing drafts are not cleared and completed review is not yet recorded |
Suppose a favourite is corrected while a consultation draft is open. The system needs a clear policy: notify the prescriber of the changed source or require reselection where appropriate, while preserving the doctor’s visible work. Silently rewriting the draft can remove patient-specific adjustments.
An issued prescription needs the clinic’s correction process if its content was wrong. Editing a favourite is not a recall mechanism for PDFs already supplied. Identify affected prescriptions through evidence rather than assuming every use of the shortcut needs the same response.
A useful change notice explains what changed: the catalogue identity, suggested wording or merely the display alias. These changes have different implications. “Favourite updated” is too vague when the prescriber must decide whether a draft needs attention.
For fictional F-84, inspect the six records below at a cutoff of 11:30 on 28 October. The review records which shortcut version supplied each encounter, then inspects the actual product and directions present in that encounter. A link to an old favourite identifies where to look; it does not establish that unchanged defaults reached the patient. D42, for example, already contains deliberate patient-specific edits that must not be removed by a bulk cleanup.
I52 exposes a different boundary. Its tab loaded F7 version 1 at 10:50 and the prescription was issued at 11:06, after version 2 was published. The case assumes this stale-copy behaviour was observed during a fictional local exercise; it is not an asserted feature of any product. Searching only prescriptions issued before 11:00 would miss I52. Searching only current F7 links would also miss D43 because it originated from independently copied L9.
The table contains four drafts and two issued prescriptions: 4 + 2 = 6 records. Five records trace to the old default’s origin, directly through F7 version 1 or through L9; D44 alone uses version 2. That is five candidates for content inspection, not five prescribing errors. The actual directions in each record, relevant patient circumstances and prescriber decisions determine whether further action is necessary. The records do not prove dispensing or medicine use.
HL7 FHIR R4 MedicationRequest represents the medication and administration instructions separately and distinguishes a request from records of dispensing or administration. This is useful technical context for the separation above. It does not define this favourites workflow, guarantee historical snapshots or establish that a software product implements any particular change behaviour.
On a narrow screen, scroll the table horizontally to read all columns.
| Record and source event | State at cutoff | Specific review or preservation task |
|---|---|---|
| D41: selected F7 version 1 at 08:30 | Open draft; inherited directions still present | Prescriber reviews those directions for this patient before approval; do not treat removal from F7 as a completed review |
| D42: selected F7 version 1 at 08:50 | Open draft; prescriber has edited the directions | Compare the retained patient-specific text with the change finding; preserve the edits while the clinician decides |
| D43: selected L9 at 09:10 | Open locum draft from an independent copy of version 1 | Locum inspects the encounter and copy separately; suspending L9 does not empty this draft |
| I51: issued from F7 version 1 at 09:40 | Issued document; approved contents remain unchanged | Inspect what was actually issued; clinician determines whether correction or patient communication is needed |
| I52: tab loaded version 1 at 10:50; issued at 11:06 | Issued document from a stale pre-change selection | Include despite its post-change issue time; review actual contents and any copies already supplied |
| D44: selected F7 version 2 at 11:12 | Open draft; identity M17 present and directions not yet entered | Prescriber must still decide and document the current plan; a new version is not clinical approval |
A useful notice states both the maintenance decision and the work it leaves for others. In F-84, “medicine changed” would be misleading because M17 is unchanged; “defaults removed everywhere” would also be false because encounter copies and L9 remain. Describe the changed fields, affected source versions and observed copy behaviour in ordinary language. Keep the notice linked to the evidence used to identify the six records.
At 11:30, Dr Sen has accepted review of D41, D42, I51 and I52. The locum has accepted D43 and L9 review. Those are assignments, not completed clinical conclusions. D44 remains an ordinary unfinished prescription draft with its own patient-specific decision outstanding. The shared entry’s owner has confirmed S4 contains no default; this establishes the scope of that shared-entry check only.
For an issued prescription, retain what was approved and any later correction as distinguishable records. If the responsible clinician identifies a correction or communication need, track the destination and outcome of that action separately. A patient may have a printed copy or a PDF shared with an outside pharmacy; editing a personal shortcut does not reach those copies. Do not infer the patient obtained or took a medicine merely because the document was issued.
In a local pilot, observe a standard selection, two similar formulations, a patient-specific edit and an outdated shortcut. Record whether the doctor selected the intended item and noticed inherited directions. A faster click sequence alone is not enough to judge the design.
Review mis-selections, abandoned favourites, unclear aliases and edits undone by subsequent selection. Keep counts tied to the observed sample. Do not infer prescribing quality from how often a favourite was used or claim that a certain list size guarantees a faster OPD.
Fictional maintenance review: a doctor examines ten favourites. Six retain verified identities and appropriate editable defaults, two are duplicate aliases, one points to a superseded catalogue entry and one has an unresolved formulation. The categories total ten. The doctor keeps the six, resolves the aliases through the catalogue process, retires the obsolete shortcut and holds the unclear item for verification. This is a local list-maintenance example, not evidence that 40% of prescribing was wrong. Historical prescriptions retain the identity and directions originally issued.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
There is no universal ideal number. Use a manageable collection that the doctor can verify and maintain, with clear identities and visible defaults. A larger list can add ambiguity rather than save time.
Saving identity and saving a regimen are separate choices. Any proposed directions should be visible and reviewed for the current patient, with missing clinical decisions left for the prescriber.
No. Preference, formulary membership and actual stock are distinct. Availability needs its own current evidence and must not determine clinical suitability by itself.
Old issued documents should preserve what was actually approved. If an earlier prescription was wrong, use a traceable correction and communication process; changing a shortcut alone does not correct copies already supplied.
It can if an earlier selection or loaded draft retains them; verify the actual software behaviour. Inspect the source version and issued content, not just the issue time. In fictional F-84, I52 loads the old version before the update and is issued afterwards. That makes it a review candidate, not proof of a prescribing error.
No. Product identity, reusable directions and the current patient’s plan are separate decisions. In F-84, M17 stays unchanged while F7 becomes identity-only. The clinician still reviews each relevant encounter; staff must not substitute another formulation or erase patient-specific directions simply to match the revised shortcut.
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.
Official publication overview opened 28 October 2026. It describes a patient-engagement tool used with health professionals. The linked booklet download returned HTTP 403, so no full-booklet review is claimed. The favourites model and fictional maintenance cases are original analysis, not WHO-approved software designs.
Official HTML entry opened 28 October 2026. It directly identifies the five moments as starting, taking, adding, reviewing and stopping medication. This supports the patient-engagement context, not a regimen, an Indian prescribing rule or a favourites configuration.
Version 4.0.1 documentation opened 28 October 2026. Supports the distinct medication and dosage-instruction fields and the boundaries between requests, dispensing and administration. It does not prescribe shortcut versioning, establish clinical suitability or demonstrate Bractis behaviour. F-84 is a fictional local evaluation case.
Build a shared clinic formulary using a worked intake review, change-impact ledger and handover for favourites, saved sets, drafts and issued prescriptions.
Review saved prescription sets with worked draft-merging, interruption and version-change examples, plus output checks for doctors in Indian clinics.
Verify unlisted medicines with a worked evidence trail for pack details, conflicting formulations, clinical review and catalogue decisions.
Build a fictional personal favourite, edit its directions for one patient and revise the source entry while an earlier draft remains open.
Request a clinic demo