Medication Reconciliation for Indian Clinics: Patient-Reported Use, Discharge Lists, and Clinician Review

Before designing a form, distinguish the information the clinic is handling.

Keep these distinctions visible in the record.

For example, a medicine can appear on an old prescription while the patient reports that it was discontinued elsewhere. That is information requiring review, not permission for reception staff to remove the medicine or renew it.

Likewise, a dispensing transaction establishes a supply event. It does not establish actual use.

A useful documentation rule is to label the source before recording a conclusion.

Medication reconciliation and medication review are related, but they are not interchangeable.

Reconciliation establishes an accurate medicine list, compares available information, and addresses discrepancies. A clinical medication review considers whether treatment remains appropriate for the individual patient. WHO discusses both processes and their different purposes. WHO technical report.

For the clinic’s operating procedure, describe three separate responsibilities:

• Gathering information.
• Checking and explaining differences.
• Making and communicating clinical decisions.

Qualified professionals should perform the activities appropriate to their competence and responsibilities. Decisions to prescribe, discontinue, substitute, or change treatment must remain with the appropriately authorised clinician.

Do not label a record “clinically reviewed” merely because someone completed the intake fields. A form can be administratively complete while its central question remains unanswered.

A clinic should have a deliberate way to identify encounters that need reconciliation.

Possible prompts for the clinical team include:

• A visit following hospital discharge.
• A new specialist’s prescription.
• A patient reporting an outside treatment change.
• Different instructions appearing on available documents.
• Uncertainty about which medicines are currently being used.

These are suggested workflow prompts, not a universal schedule or legal requirement.

The responsible clinician should determine the urgency and scope of review. A concern affecting immediate care should follow the clinic’s clinical escalation process, rather than wait for an administrative callback.

Reception can flag that a discharge document or changed prescription has arrived. It should not decide which instruction takes precedence.

Record the reason for opening the review in plain language: “Patient reports changes after discharge; current use not yet confirmed” is more informative than “medicine update.”

Patients may describe medicines by brand, packaging, colour, purpose, or the time they take them. Build an intake process that allows uncertainty instead of demanding confident answers.

AHRQ’s medicine-review guidance recommends asking patients to bring their medicines and discussing what they actually use. It includes prescription products, non-prescription medicines, supplements, herbal products, and non-tablet preparations. AHRQ: Conduct Brown Bag Medicine Reviews.

An appointment preparation message could say:

Please bring your current medicine packets or containers, recent prescriptions, and any discharge medicine list. If something is missing or you are unsure about it, tell the clinical team.

Do not suggest that patients delay necessary care because documents are unavailable.

Record who supplied the information

Distinguish the patient’s account from information supplied by a caregiver or another provider.

If a caregiver manages the medicines, record their involvement through the clinic’s established identity and permission process. Do not assume that a shared phone number makes someone the authorised contact.

Where a name or instruction is unclear, document that limitation. Guessing creates apparent certainty that the clinician must later undo.

A comparison record should help the clinician locate the disagreement quickly.

Useful information includes the medicine name, strength, formulation, recorded directions, and the source of each account. NICE’s medicines-optimisation guidance describes these kinds of medicine details and recognises prescribed, non-prescription, and complementary medicines. It is UK guidance, not an Indian statutory requirement. NICE: Medicines optimisation.

For a clinic-designed worksheet, consider these additional documentation fields:

• Patient and encounter reference.
• Document date.
• Date the clinic received the information.
• Person who recorded it.
• Exact uncertainty requiring review.
• Responsible reviewer.
• Decision or next action, once available.

Keep document date and receipt date separate. A discharge summary received today may describe treatment from several weeks earlier.

Avoid using a single “last updated” date for the whole history. It can make an old source look newly verified.

The worksheet should support the clinical record, not become an uncontrolled spreadsheet containing a second, competing version of the patient’s treatment.

The purpose of comparison is to expose questions.

A medicine might appear in one source but not another. The name may be similar while the strength or formulation differs. A patient may describe instructions that do not match the available document.

Use neutral descriptions:

• “Present on previous clinic prescription; absent from supplied discharge list.”
• “Patient reports a change; supporting document unavailable.”
• “Directions differ between sources.”
• “Product identity requires confirmation.”

Avoid automatically labelling every difference a prescribing error. A change may have been intentional, and the available information may be incomplete.

Do not use formatting as a clinical shortcut

Alphabetising lists or standardising spelling can improve readability. Neither establishes that two entries describe the same product.

If software suggests a match, the reviewer should still see the original text and source. A confident-looking medicine catalogue entry should not conceal an uncertain transcription.

Similarly, do not convert an unreadable strength into a plausible value merely to satisfy a mandatory field.

An explicit “not confirmed” is more useful than an invented answer.

A reconciliation process needs somewhere for unanswered questions to go.

A suggested coordination record could contain:

• The specific question.
• The person responsible for obtaining clarification.
• The clinician responsible for the treatment decision.
• The approved contact route.
• Contact attempts and responses.
• The clinician-defined review time.
• The current status.

Do not use “message sent” as a synonym for “resolved.”

Suppose the clinic asks another provider whether an omission from a discharge list was intentional. An outgoing message records an attempt. A reply records information received. The responsible clinician’s assessment records what that information means for this patient.

Those are three different events.

Where clarification cannot be obtained, document the limitation and the clinician’s resulting plan. Do not close the question by assuming that silence confirms either list.

For broader coordination principles, see the patient referral tracking guide.

Once the responsible clinician reviews the available information, the record should explain the result.

The clinic’s documentation format should make it possible to identify:

• Which information was considered.
• Which differences were clarified.
• What remains uncertain.
• What the clinician decided.
• Who made the decision and when.
• What was communicated to the patient.
• Whether further clarification or follow-up is required.

Keep the historical prescription and external document available as historical evidence.

Do not rewrite an earlier consultation so it appears that today’s information was known at the time.

If the new review reveals an actual documentation error, use the clinic’s correction process. If it records a genuine change in treatment, document the new decision as a new event.

The medical-record correction guide explains that distinction in more detail.

An updated list should make the present position easier to understand without making the past impossible to reconstruct.

A completed review is not useful if the patient leaves unsure which instructions apply.

The responsible clinical professional should explain the approved plan and address uncertainty using language the patient understands.

AHRQ describes teach-back as asking patients to explain information in their own words to check how clearly it was communicated. It is not a test of the patient’s intelligence or memory. AHRQ: Use the Teach-Back Method.

A suitable communication prompt is:

To check that I explained this clearly, please tell me which medicine instructions you will follow when you get home.

Record the explanation and any remaining questions. A delivery receipt alone does not establish understanding.

Where another person helps manage the medicines, include them appropriately without bypassing the patient’s preferences or the clinic’s confidentiality process.

Keep the clinician-approved prescription and any explanatory document consistent. If a corrected version is issued, make clear which document supersedes the earlier one.

Before introducing the workflow, rehearse a case using fictional information.

Create a test patient with:

• An earlier clinic prescription containing Medicine A and Medicine B.
• A discharge document containing Medicine A and Medicine C.
• A patient-reported list that includes all three.
• One medicine packet with an unclear label.

These placeholders are a documentation exercise, not a treatment example.

What the team should demonstrate

First, reception links the discharge document to the correct patient and flags it for clinical review. It does not alter the prescription.

Next, the authorised person gathering the history records each source separately. The unclear label remains unresolved rather than becoming an assumed catalogue match.

The clinician then reviews the differences. The exercise does not prescribe what that decision should be; it tests whether the decision and its supporting information can be recorded clearly.

Finally, the team demonstrates how it records the patient explanation and any outstanding clarification.

Add a late-arriving document

After the simulated encounter is completed, introduce another external document.

Can the team record when it arrived, route it for review, and preserve the earlier information? Or does uploading a file silently replace the list everyone had previously seen?

This second step tests the process more effectively than a demonstration in which every source agrees from the beginning.

A polished medicine table is not enough. Ask the software provider to demonstrate these questions:

1. Can a reported medicine be recorded without issuing a prescription?
2. Can the original source and its date remain visible?
3. Can staff record an uncertain name or instruction without guessing?
4. Can a clinician compare historical prescriptions with external documents?
5. Can a discrepancy remain open without being represented as an approved treatment change?
6. Can the reviewer record the decision and its timing?
7. Can another authorised clinician understand the unresolved work?
8. Can the clinic retrieve the patient-facing document that was actually issued?
9. Do permissions separate preparation from clinical approval?
10. Can the relevant history be exported intelligibly?

Ask which steps are supported directly, which require configuration, and which remain manual.

Do not treat automatic extraction as verification. A system may correctly transcribe a document while still being unable to establish whether the patient follows it or whether a later instruction exists.

For prescription-authoring requirements, use the separate digital prescription software checklist.

CliniKite’s current feature descriptions include longitudinal patient history, previous notes and medicines, consultation-linked prescriptions, doctor-reviewed drafts, and pharmacy dispensing from the saved prescription. These provide relevant context for medicine-history work. CliniKite features.

They do not, by themselves, establish that CliniKite offers a dedicated medication-reconciliation module, a consolidated external-provider medicine feed, or automatic resolution of conflicting instructions.

Bring the fictional scenario above to a CliniKite demonstration. Ask the team to show exactly where patient-reported information, external documents, unresolved questions, and clinician decisions would be recorded.

Confirm the access, export, and connected-service arrangements for the selected deployment using the security and data information.

If part of the process remains manual, document that responsibility explicitly. An honest, understood handoff is preferable to assuming that a feature name covers the whole workflow.

Medication reconciliation for clinics is not simply copying the latest prescription into a new visit.

A useful process distinguishes historical instructions, patient-reported use, external information, and the clinician’s current decision. It preserves uncertainty until it can be assessed, assigns unresolved questions, and records what the patient was told.

Start with one fictional case containing conflicting sources. The clinic should be able to explain what was known, what required clarification, who made the decision, and what happened next—without relying on staff memory.