Skip to main content

Mapping OPD Notes and Prescriptions to FHIR: A Practical Guide for Indian Clinics

Mapping an OPD note to FHIR means preserving the clinical meaning, authorship, dates and relationships of its contents, not simply placing six text fields in JSON. Use the agreed ABDM implementation-guide version, distinguish reported medicine use from a prescription and validate the resulting document. A valid export still does not prove successful consented exchange or clinical correctness.

By Bractis · Updated · 10 min read

Indian clinic owners, doctors and implementation teams discussing record portability, ABDM integration and consultation exports with software vendors.

Separate a readable note, a structured document and a working exchange

A readable consultation note answers what happened in the encounter. A structured exchange document represents that information in a defined technical form. A working exchange also needs the intended recipient, permissions, transport and acknowledgement. These are related deliverables, but evidence for one does not establish the others.

A vendor may show a downloadable PDF and call it interoperability. The PDF may be useful, yet another system might still be unable to identify the individual observations or medicine instructions. Conversely, a machine-readable export may be difficult for a clinician to understand if its narrative is missing or inconsistent.

Start with the receiving use case: another doctor reading the encounter, a patient carrying a record, or a specified health-information exchange. Agree what information must survive and how the receiving system will use it. Do not begin by forcing the clinic into a technical format without defining the care task.

In a demonstration, keep the three questions separate: is the clinical record complete for its purpose, does the export conform to the agreed specification, and can the recipient receive and interpret it through the intended workflow? Record separate evidence and limitations for each.

Name the exact guide and profile version being implemented

The inspected NRCeS PrescriptionRecord page identifies the published ABDM implementation guide as v6.5.0, based on FHIR R4. Preview pages for another version should not be assumed to be the target required by a receiving system. Verify the package and version actually agreed for the integration.

Ask the vendor to identify the relevant document profile, terminology dependencies and validation tooling. “FHIR ready” is too broad to explain which constraints an export satisfies. A system can use FHIR-shaped data internally without producing the document required by a particular exchange.

HL7’s R4 document model uses a document Bundle beginning with a Composition, together with referenced content. This gives the document context and structure. It is different from a folder containing unrelated JSON files or a PDF with a FHIR label added to its name.

Use these technical details only to frame acceptance questions. The clinic does not need to inspect every field manually, but it should receive an understandable conformance report and an explanation of any omitted, unsupported or locally extended content.

Source: NRCeS: ABDM PrescriptionRecord profile, v6.5.0

Source: HL7 FHIR R4: Documents

Map meaning before mapping fields

An OPD form may have six convenient sections, but a single section can contain several different clinical concepts. A medicine mentioned in the history is not necessarily a new order; a possible diagnosis should not become confirmed simply because a destination field requires a code.

The original mapping table below is conceptual. It is not a complete profile specification or a validated sample payload. The implementation team must apply the actual profile constraints and preserve uncertainty rather than inventing content to satisfy them.

On a narrow screen, scroll the table horizontally to read all columns.

A consultation section can contain more than one kind of information
Clinical contentMeaning to preserveMapping question
Patient, encounter and authorWho the record concerns and who documented itDo all references resolve to the correct person, visit and practitioner?
History and reported medicine useAttributed reports, time and uncertaintyIs reported use kept distinct from a newly requested medicine?
Examination and measurementsWhat was actually assessed, when and in which unitsAre structured observations supported by source evidence?
AssessmentClinical conclusion and its certaintyDoes narrative and coded representation preserve the same meaning?
PrescriptionThe clinician’s authorised medicine instructionsAre request intent, status, prescriber and dosage meaning accurate?
Investigations and follow-upRequested work versus completed results or reviewCan the recipient distinguish a plan from an event that already happened?

Source: NRCeS: ABDM OPConsultRecord profile, published guide v6.5.0

Source: HL7 FHIR R4: MedicationRequest

Source: HL7 FHIR R4: MedicationStatement

Walk through one fictional encounter without inventing missing data

Consider a fictional consultation in which the patient reports taking a medicine prescribed elsewhere, brings a laboratory report collected the previous week and receives advice without a new prescription. The note contains medicine text and a test value, but neither establishes that this clinic issued the old medicine or measured the value today.

The export should preserve the reported-use meaning and the outside result’s source and date. It should not create a fresh active order just because a medicine name is present in the history. The responsible clinician’s actual plan belongs in the appropriate narrative and structured representation supported by the target profile.

If a medicine name or strength is uncertain, retain the uncertainty and arrange review. Selecting the closest catalogue entry can turn a transcription limitation into a specific clinical assertion. The same applies to missing units, unclear report dates and incomplete identifiers.

Now add a later authorised prescription after further assessment. That later decision needs its own accurate authorship, time and relationship to the encounter. Exporting the current state must not silently make it appear that the original no-new-prescription visit already contained that order.

Compare the human-readable document with the structured values

A recipient may read the narrative while software uses structured fields for display, trend charts or alerts. Contradictions between the two are therefore consequential. A note saying a medicine was stopped should not coexist unexplained with an active new request for the same treatment.

Compare dates with their meanings. Encounter time, observation time, report issue time and export-generation time are different. A technically valid timestamp does not prove that it represents the correct event. A value imported today may describe a sample collected much earlier.

Check identifiers and references using fictional similar-name patients. An export can be syntactically valid while linking a report to the wrong patient or a prescription to the wrong encounter. Validation must include relational checks and a clinical review of the assembled document.

Do not hide unsupported information in a generic narrative merely to obtain a validation pass. State what can be represented reliably, what remains in the source document and what needs further work. An honest limitation is more useful to a receiving clinician than a complete-looking but misleading data structure.

Ask for four layers of acceptance evidence

First, inspect the source encounter and define the facts that must survive. Second, review the export against the agreed profile and terminology requirements. Third, view it in the intended receiving application or an appropriate test viewer. Fourth, test the actual exchange workflow separately with fictional or approved test data.

A validator’s success answers a bounded structural question. It does not establish that the doctor’s reasoning is correct, that the patient authorised the exchange or that the receiving clinician saw the intended version. Keep those claims separate in the evidence record.

The outline below helps a clinic request useful evidence without becoming responsible for writing the integration itself.

Maintain the mapping when clinical forms or profiles change

A new field in the clinic form can change the export even if the integration code is untouched. For example, adding a patient-reported medicine section creates a risk if the old mapper treats every medicine row as a prescription. Review the mapping whenever the clinical data contract changes.

Likewise, a profile upgrade should have a defined migration and regression plan. Retain a set of fictional encounters that includes no new medicine, uncertain history, outside results, corrected documents and multiple authors. These cases expose semantic problems that a simple successful example may not reveal.

NRCeS’s EHR standards describe preserving original information and traceable changes. Apply that distinction when reviewing exports and amendments: a later version should have an understandable relationship to the earlier issued record rather than replacing its history without explanation.

Document which integrations and versions were actually demonstrated. A structured export is useful progress, but it should not be marketed as completed ABDM exchange, insurance readiness or universal interoperability unless those separate capabilities have been established.

Source: NRCeS: EHR Standards for India

Worked example: a medicine history becomes an unintended order

A fictional clinic imports an old prescription into the history section. Its export mapper places every medicine row into the new-prescription pathway, so the receiving view shows a current order that the doctor never issued. The team compares the source note with the receiving document, isolates the mapping error and adds a reported-use case to the acceptance set. The fix is a semantic distinction between history and authorisation, not merely changing a JSON field name.

OPD-to-FHIR Mapping and Acceptance Worksheet

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Target agreement
Record the receiving use case, exact implementation-guide version and profile. What does the vendor mean by “FHIR ready”?
Meaning preservation
Choose a fictional encounter with an old medicine, outside result and uncertain history. State what must not become a new clinical assertion.
Receiving view
Compare narrative and structured content in the receiving application, including dates, units, identity and medicine intent.
Separate evidence
List conformance, clinical meaning and exchange evidence separately. Identify which claims have not yet been demonstrated.

Questions doctors ask

Does a six-field OPD note automatically map cleanly to FHIR?

No. A form section can contain several concepts with different meanings, sources and statuses. The mapping must preserve those distinctions and meet the target profile. Populated text fields alone do not prove a conformant or clinically faithful export.

Is a PDF prescription the same as a structured FHIR prescription?

A PDF can be a useful human-readable document, but it does not by itself provide the structured relationships and constraints of the target FHIR representation. Ask what the recipient can read and process, and how the source document remains connected.

Which ABDM FHIR version should a clinic ask a vendor to support?

Ask for the package and profile version agreed with the actual receiving workflow. The published page inspected for this guide identifies v6.5.0 on FHIR R4; preview releases and future changes need separate verification before adoption.

Does passing a FHIR validator prove the record is correct?

It provides bounded technical evidence, not proof of the clinical facts, patient matching, authorisation or successful exchange. Compare the source and receiving views and test the relevant workflow as separate acceptance steps.

Should every medicine mentioned in a consultation become a prescription resource?

No. Reported use, historical treatment, a suggestion and a new authorised request have different meanings. The implementation must preserve intent and status under the chosen profile rather than convert every medicine mention into an active order.

Sources and scope

Updated on . Conceptual implementation and procurement guidance. No sample payload is represented as validated, and no ABDM integration, regulatory conformance or clinical correctness is certified. No independent clinical or legal review is claimed.

  • NRCeS: ABDM PrescriptionRecord profile, v6.5.0

    The inspected page identifies published guide v6.5.0 based on FHIR R4. A profile description does not prove that a vendor exports conformant data or has completed ABDM exchange integration.

  • NRCeS: ABDM OPConsultRecord profile, published guide v6.5.0

    Published-profile reference checked against official indexed content. Confirm the implementation-guide package and version agreed with the receiving system; a preview release is not assumed to be the required target.

  • HL7 FHIR R4: Documents

    Versioned R4 specification for document bundles and Composition. Used because the inspected ABDM published guide is R4-based, not because R4 is the newest FHIR release.

  • HL7 FHIR R4: MedicationRequest

    Describes medication requests and orders. Interpret status and intent with the actual profile and workflow; merely serialising a resource must not create an unintended authorisation.

  • HL7 FHIR R4: MedicationStatement

    Describes an assertion about medication use, distinct from a new prescription. Mapping must preserve source and meaning rather than turn every medicine mention into an order.

  • NRCeS: EHR Standards for India

    Indian standards context, including original data and traceable changes. The mapping and review methods here do not establish legal compliance, retention periods or product certification.

Try the workflow
with Bractis.

Bring a fictional no-new-prescription encounter with an outside report to a Bractis demo. Ask which export and exchange capabilities are currently supported, then inspect profile/version evidence and the receiving view for the demonstrated scope.

Request a clinic demo