Skip to main content

ABDM Consent and Health Record Exchange: A Clinic Workflow

Track a record exchange under the Ayushman Bharat Digital Mission (ABDM) as separate decisions and events: identify the patient, define the needed records, obtain the applicable consent, receive the information and have the clinician review it. A consent request is not an approval; approval is not receipt; receipt is not clinical reconciliation. Keep unavailable records and expired or withdrawn permissions visible, with a responsible owner and a fallback for the consultation.

By Bractis · Updated · 15 min read

Indian clinics evaluating consented record retrieval or sharing through an ABDM-connected product.

Begin with the clinical information needed, not “fetch everything”

A doctor may need the report from a particular investigation, the discharge summary from a recent admission or earlier prescriptions to understand a treatment history. These are more precise requests than an indefinite request for every record the system can find.

Record the intended purpose, relevant period and document types through the supported process. The clinic’s requester and the patient should be able to understand the scope. If the request is too broad or ambiguous, revise it before treating an approval as a meaningful decision.

The Ministry of Health and Family Welfare states that exchange under ABDM takes place after patient consent. The published Health Data Management Policy describes purpose-specific, informed consent that can be withdrawn. These establish the general framework; the workflow below is an operational interpretation for evaluating a clinic implementation.

Use the patient’s actual chart and current encounter as the context for the request. A shared family contact, an old browser tab or a recently changed phone number should not determine whose records are requested without a patient-matching check.

Source: MoHFW: Steps taken for cyber security under ABDM

Source: NHA: published Health Data Management Policy, 2020

Know who is requesting, supplying and reviewing the information

In an exchange discussion, a health information provider supplies records and a health information user receives information for the relevant use. Your clinic may participate in different roles in different transactions. Ask the vendor to explain the configured role in ordinary language rather than relying on an acronym beside a logo.

The patient’s consent-management experience is another part of the journey. The receptionist initiating a request may not be the person able to approve it. Staff should help explain the process without taking over a patient’s private credentials or representing an unanswered request as agreement.

Assign clinic responsibility for retrieval and for clinical review separately. A receptionist may monitor whether an expected report arrived, while the doctor decides how it affects the current assessment. Neither role should assume the other has completed its part simply because a status changed.

Use a state record that explains what actually happened

The following states are a clinic review model, not a promise about the exact labels in every product. Map the actual software states to their meaning, evidence and next action. Preserve references that connect a request to the consent and received material.

A single green indicator called “connected” hides too much. A clinic should be able to distinguish the successful connection from an unresolved request, and a completed transfer from a document nobody has opened.

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

Evidence at each stage of a consented record exchange
Observed stageEvidence neededStill unresolved
Request submittedCorrect patient, purpose, requested scope and request referenceWhether the patient approves
Permission granted for a scopeCurrent applicable authorization and its limitsWhether any records have arrived
Information receivedActual documents, source, dates and transfer resultWhether the expected information is complete and usable
Clinical review recordedClinician’s review and handling of relevant discrepanciesAny new action arising from that review
Denied, expired or withdrawnCurrent status and the affected request or permissionRequired follow-through and the consultation fallback
Partial or failed transferKnown received items and a specific missing or failed partRecovery without duplicating already received material

Separate the record period from permission and retrieval time

Three date concepts can appear in one exchange: the period of care covered by the requested records, the permission’s applicable time limits, and the time information was actually received. They should not be substituted for each other.

For a fictional example, a request made in October concerns an investigation from July. An October receipt date does not make the investigation current. A document’s original date and source need to remain visible when the doctor reads it or when an automated summary uses it.

Similarly, an authorization that was usable when a request started may require a new check before later access. Have the provider show how status changes reach pending or repeated operations. Do not infer the allowed access period from the historical date range printed on the request.

Record unfamiliar date fields and ask for their meaning in the deployed version. A technical timestamp labelled only “expiry” is not enough to determine which permission, request or stored copy it governs.

Inspect the received package before using its contents

Start with patient identity and source. Then inspect document dates, page completeness, readability and relevant units or version information. A transfer can be technically successful while the attached scan is incomplete or the expected report is absent.

Keep outside information attributable. An old prescription should remain an outside prescription from its actual date until the clinician determines its current relevance. Importing it should not automatically add all medicines to the active medication list.

Document a conflict rather than silently resolving it through the import order. A current patient account may disagree with an earlier record; both can be useful evidence, but the clinician needs to establish what applies now. The most recently received file is not necessarily the most recent clinical fact.

Where the same document arrives twice, compare source and identity before treating it as a second investigation. Preserve meaningful amendments. Two files with similar titles may be a true duplicate, a corrected version or separate events that should remain distinct.

Worked package: four received files, three expected documents, one ready for review

In fictional case E-24, an October consultation needs three specified outside documents: July report J-01 with two pages, August discharge summary A-02 with four pages, and September prescription S-03 with one page. The expected page counts are known from the test source inventory. They are not guessed from a filename or assumed to be available in every live exchange.

At 11:00, the clinic receives four files. The July report is complete and a retry delivers an identical copy of that same version. The discharge file contains pages 1, 2 and 4; page 3 is absent. The prescription file contains one page, but its contents cannot be read. A green receipt indicator can be accurate about delivery while still being inadequate evidence for clinical use.

The receptionist’s receipt check establishes identity, source, visible page coverage and readability. “Ready for review” below means ready for the doctor to inspect, not that the document is correct, relevant or clinically accepted. Even a complete outside report may contain a discrepancy that only clinical reconciliation can resolve.

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

Fictional E-24 receipt inventory at 11:00
Received fileEvidence at the deskHandling before clinical use
J-01, original deliveryTwo expected pages present and readable; source and document identity match the request.One document ready for clinician review; preserve its July date.
J-01, retry deliverySame source, document, version and two-page contents confirmed in this test.Record a repeated delivery of J-01; do not count a second investigation or overwrite a later amendment.
A-02, discharge summaryPages 1, 2 and 4 received against four expected pages.Incomplete document; identify page 3 as missing and assign follow-through. No claim that the unseen page contains no relevant information.
S-03, prescriptionOne page delivered, but text is unreadable.Receipt is established; medicine content is not. Obtain a usable source through an authorized route rather than infer entries.

Count document readiness separately from files and pages

E-24 has four delivered files representing three expected document identities. Only one of those three documents is complete and readable at 11:00. The received files contain eight page images: two plus two plus three plus one. After excluding the confirmed repeated two-page delivery, six distinct page positions are present against seven expected. Five are readable; one is unreadable and one is missing. Each count answers a different question.

Use the exception to choose the next action. A missing page calls for the missing part or a verified complete replacement. An unreadable page calls for a usable representation. An unconfirmed duplicate calls for comparison of source, document and version. Downloading everything again without a plan can increase the file count while leaving the same clinical gap.

If a replacement A-02 later arrives with all four pages, confirm whether it is the same document version or an amendment, link the receipt history and recheck the complete set. Do not blindly combine page 3 from one version with pages 1, 2 and 4 from another. Where the source cannot establish the relationship, keep that uncertainty visible to the clinician.

Do not convert “nothing returned” into “no history”. A source may have no linked document, a request may have the wrong period, permission may be unresolved, or delivery may have failed. Record the observed state and the specific information still needed. The doctor decides the consultation plan with those limits; the software should not fill the gap with a normal result or an empty active-medicine history.

Give the clinician a usable partial-record handover

For E-24, a useful handover states that the July report is available, the August discharge summary is incomplete and the September prescription is unreadable. It identifies the current request reference and the person pursuing each exception. “ABDM completed” says none of that and encourages the next person to rely on information the clinic does not have.

The doctor’s review should distinguish the outside source from today’s assessment. For example, “July report reviewed; missing discharge page limits reconciliation of the admission history” describes available evidence and its limitation. It is not a diagnosis or a substitute for the clinician’s actual findings. Do not paste an example review sentence into a real chart unless it accurately describes the review performed.

When the patient asks why another document is needed, explain the gap specifically: one requested page is missing or the received prescription cannot be read. Do not imply that the patient refused sharing when permission was granted and the failure occurred during receipt. Record any alternative source with its own provenance rather than presenting a photographed paper copy as if it arrived in the earlier exchange.

Treat withdrawal and retention as explicit operational work

When permission expires or is withdrawn, stop relying on it for further access and follow the applicable exchange requirements. The policy describes notification of revocation and separately addresses storage limitation, with applicable-law considerations. Do not turn that into either blanket permission to keep every received copy or a claim that one button physically recalls every copy.

Ask the provider to explain what happens to pending transfers, cached documents, exports and downstream processing under the supported arrangement. The clinic needs an actionable procedure and a responsible person for any remaining obligations, not just a status badge.

Separate externally received material from records created by the clinic during its own care. Resolve the relevant retention and access duties with the responsible adviser and provider. Staff should not improvise bulk destruction of the clinic’s original records from an unexplained consent status.

Use a fictional withdrawal test to verify the visible result and the handling of a later access attempt. Record any unsupported case or delayed status propagation. This is stronger evidence than a verbal assurance that all consent changes are automatic.

Source: NHA: published Health Data Management Policy, 2020

Test a permission change while a transfer is still in flight

A controlled test should include more than clicking Withdraw after every transfer has finished. In a separate fictional timeline, an access attempt starts at 11:01, withdrawal is recorded at 11:02, and a delayed response reaches the receiving system at 11:03. The order of events raises a question; the response’s arrival does not by itself answer whether it may now be used.

Have the responsible technical owner trace the linked request, permission, status notification, access check and response. Establish the actual timestamps and the deployed service’s requirements. Stop further reliance on the withdrawn permission and keep the late response from silently becoming accepted clinical input while its authorized handling is unresolved. Do not mark a local timestamp or a cached approval badge as sufficient proof.

The published Health Data Management Policy addresses revocation notification in clause 11.3 and storage limitation in clause 26.6, with applicable-law qualifications. Those clauses do not specify every race condition in a deployed product. The clinic needs an explained, tested disposition for pending work and received copies, including any lawful retention duties, without treating revocation as either permission for unlimited reuse or a mechanism that recalls every exported file.

Close the test with an outcome for each affected object: future request, pending response, received document and any separate clinic-created record. Name the owner of unresolved copy handling and preserve the relevant audit evidence under the approved process. This is an acceptance exercise, not an instruction to delete a patient chart or an assertion that a particular platform enforces these controls.

Source: NHA: published Health Data Management Policy, 2020

Rehearse a partial exchange and an unavailable patient approval

A useful demonstration includes one completed request and one exception. For the completed request, inspect a specific report and its original date. For the exception, make one item unavailable or leave approval unresolved, then follow the clinic’s task ownership and fallback.

If an external record cannot be obtained, the doctor decides how to proceed with the available information and its limitations. The system should not create a fictitious normal result or a “reviewed” status to let the user move forward.

Bractis’s interoperability page provides the product discussion starting point. Obtain the exact supported environment, record types, prerequisites and limitations before treating the demonstration as evidence for your clinic. A sandbox exercise and a live connection are different pieces of evidence.

Source: Bractis ABDM and interoperability scope

Two requested documents, one received report

A fictional clinic requests a July laboratory report and an August discharge summary for an October visit. Permission is granted, but only the July report arrives. Reception records the missing summary as unresolved. The doctor sees the report’s July date and reviews it in the current context. The clinic does not mark the full history received, list the July value as an October observation or record the absent discharge medicines as current.

Consented Record Exchange Review Sheet

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

Purpose and identity
Confirm the chart and state the specific information needed for this request.
State and dates
Distinguish request, permission, receipt and review, including the meaning of each date.
Received evidence
Check original source, patient, dates, readable content, versions and missing documents.
Changed permission
Test a supported exception and document access, copy handling, fallback and responsibility.

Questions doctors ask

Can four received files still represent an incomplete ABDM record exchange?

Yes. A repeated delivery can increase file counts while another document is missing pages or unreadable. Reconcile document identities, versions, expected coverage and usability before reporting completion; receipt still needs separate clinical review.

What if a record response arrives after consent was withdrawn?

Do not infer permission from delivery. Trace the linked request, withdrawal and access checks with the responsible provider, stop further reliance on the withdrawn permission, and resolve handling of the delayed response under the applicable requirements before accepting it for use.

Does an approved ABDM consent mean the clinic has received the records?

No. Confirm actual receipt, document scope and usability separately, then record the clinician’s relevant review.

Which date should a received outside report retain?

Keep its original clinical date and source distinct from the date the clinic received or imported it.

Can imported prescriptions automatically become current medicines?

The clinician needs to reconcile their present relevance. An earlier prescription is evidence of an earlier record, not automatic confirmation of current use.

What should happen when sharing permission is withdrawn?

Stop relying on that permission for further access and follow the applicable exchange and copy-handling requirements. Confirm pending work and retention responsibilities rather than treating a changed badge as the whole process.

What if only part of the requested history arrives?

Identify the received and missing material, assign follow-through and let the doctor assess the current encounter with the documented information limits.

Sources and scope

Updated on . The state table is an original clinic evaluation aid, not an API specification or certification. Exact access, deletion and retention responsibilities depend on the applicable requirements and configured service. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Trace a fictional request through permission, partial receipt and clinician review, then inspect an expired or withdrawn permission and its operational follow-through.

Request a clinic demo