Shared Family Phone Numbers: Keep Each Patient Record Separate
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
ABHA is a person’s digital health identifier within ABDM, India’s digital health ecosystem. Recording an ABHA number, linking records and exchanging information with consent are different capabilities. A private clinic should establish which steps its software actually supports, what setup is required and how received records are matched and reviewed. Keep a usable local registration path when a patient does not provide ABHA or an exchange cannot be completed.
For private clinic owners and doctors evaluating ABHA-related registration and ABDM health-record exchange.
The Ministry of Health and Family Welfare describes ABHA as a 14-digit digital health identifier and states that its creation is voluntary. ABDM is the wider ecosystem through which digital health participants and services can work together. These terms are related, but they do not describe the same object.
The Ministry’s May 2026 update describes consent-based health-information exchange and identifies building blocks including ABHA, the Healthcare Professionals Registry, the Health Facility Registry and the Health Information Exchange and Consent Manager. A clinic’s practical question is which relevant capabilities its product and configuration support.
An identifier does not contain the full clinical history on its own. A number shown in a patient profile does not establish that the clinic has received records, that those records are complete, or that a doctor has reviewed them. Evaluate these stages independently.
Source: MoHFW: Update on Ayushman Bharat Digital Mission, 6 February 2024
Source: MoHFW: ABHA-linked records and consent-based exchange, 22 May 2026
Ask the demonstrator to name the action being shown and the evidence that it succeeded. The table below is an evaluation framework, not a technical description of every ABDM API or a certification checklist. It prevents a successful early step from being mistaken for a complete clinical workflow.
For every stage, identify what happens when it is incomplete. An exchange request may be pending while the consultation continues with information already available through the clinic’s appropriate process. The screen should not imply that absent information was received or reviewed.
On a narrow screen, scroll the table horizontally to read all columns.
| Stage | Evidence to inspect | What it does not establish |
|---|---|---|
| Local patient matching | The correct existing clinic chart is selected using the clinic’s identity process. | A shared phone number alone does not identify a unique patient. |
| Identifier handling | The demonstrated capture, verification or linking capability and its actual result. | An ABHA field does not prove record exchange. |
| Consent process | The purpose, scope and status of the consent-related step supported by the connection. | A request displayed on screen is not evidence of completed sharing. |
| Record receipt | Supported records arrive with source, date and patient context. | Successful receipt does not establish a complete longitudinal history. |
| Clinical review | The responsible clinician reviews relevant received information and records the outcome. | A downloaded document is not automatically a clinical conclusion. |
The NRCeS FHIR Implementation Guide for ABDM distinguishes a Health Information Provider, or HIP, that creates health information for digital sharing, from a Health Information User, or HIU, that intends to view a person’s records with informed consent. These describe roles in information exchange. Ask which role the proposed clinic workflow supports; seeing one direction demonstrated does not establish the other.
For a sharing workflow, inspect which completed clinic records can be made available, how the correct patient is linked and how corrected documents are represented. For a receiving workflow, inspect the request, actual received material, source, patient match and clinician review. A clinic evaluating both directions needs a demonstration of both, with the appropriate permissions and supported configuration.
Keep registry participation and exchange capability distinct. Professional and facility identifiers help identify participants, but a registry screen does not show whether this clinic’s EMR can complete the required information flow. Record the actual enabled capability and the party responsible for unresolved setup, rather than reducing the buying decision to an “ABDM-ready” badge.
Source: NRCeS: FHIR Implementation Guide for ABDM—actors and scope
A test environment is useful for rehearsing identity and exchange with fictional data. Label it clearly in the evidence record. A successful sandbox demonstration shows what happened in that environment; it does not by itself prove that the clinic’s production connection, organisation, users and supported record types are configured. Ask for the route from the demonstrated state to the contracted service.
Capture the product version, environment, enabled direction of exchange, participating endpoints and the record types actually tested. Ask who owns onboarding, ongoing support and failures outside the EMR. If a dependency is still being arranged, retain it as an explicit precondition for adopting that workflow rather than treating a future integration as available today.
Use the same discipline for registration conveniences. A successful QR registration or token workflow should be evaluated for its registration purpose. Do not treat it as evidence that clinical documents have been requested, shared or reviewed. The clinic needs separate observations for those actions, even when the software presents them within one patient journey.
On a narrow screen, scroll the table horizontally to read all columns.
| Claim shown in a demo | Evidence still needed | Decision to record |
|---|---|---|
| An ABHA identifier appears on a profile | The actual capture, verification or linking result and the local chart match | Which identity task is supported and which remains outside scope. |
| A fictional record moves in a sandbox | Configuration and acceptance steps for the clinic’s intended environment | Who completes setup and what must be demonstrated before use. |
| The clinic can share a document | A separate receiving demonstration if retrieval is required | Whether the contracted workflow covers sharing, receiving or both. |
| A registry or integration status is displayed | The exact meaning, evidence date and workflow it covers | No broader certification or interoperability claim inferred from the label. |
A clinic already needs a reliable way to distinguish people with similar names or shared contact numbers. Adding another identifier should strengthen that process rather than bypass it. Confirm the intended local chart before linking identity or importing information.
Consider a patient who first visits without ABHA and provides it later. The desired outcome is an appropriate link to the established chart, not a second chart that hides the earlier encounter. Test how the software identifies a possible existing record and who can resolve an uncertain match.
Do not let reception merge records simply to remove a duplicate warning. A merge can affect prescriptions, attachments and billing history. The clinic needs an authorized correction path with enough history to explain what changed. Identifier linking and record merging are distinct operations.
For a family sharing a phone, evaluate each person separately. Neither the shared number nor the accompanying relative should cause records from different people to be combined. Use fictional family records in the demonstration to expose this failure mode.
The ecosystem’s consent-based exchange model does not remove the need to understand what a particular request covers. Ask the vendor to show the supported purpose, record scope, time scope and status information in the configured workflow. Avoid treating a broad consent label as an explanation of all data handling.
Then inspect what actually arrives. Check the patient, originating provider, document or encounter date and any information needed to understand the record. A receipt containing only some requested documents should remain distinguishable from an expectation of a complete set.
The clinician still decides how the information relates to the current encounter. An old prescription may describe a previous treatment rather than current medicines. An external laboratory value needs its source and relevant units or context. Exchange supplies information; it does not resolve every interpretation question.
Ask how a denied, expired or otherwise unusable consent state affects pending work, and how the product displays the limits of its current capability. Do not infer a universal deletion or retention rule from a single consent status; document the actual system behaviour and the clinic’s responsibilities.
In this fictional reception-and-doctor rehearsal, the team tracks eight distinct requests. Two patients decline the requested sharing, one request expires without approval, one is still awaiting a response and four receive permission for the specified scope. These are plain-language evaluation outcomes, not an exhaustive list of ABDM API status codes. A declined request is a patient choice, not a technical failure to be overcome.
Of the four permitted exchanges, two deliver all documents expected in the test fixture, one delivers only part of the expected material and one has a transfer failure. That leaves two complete fixture receipts out of eight initial requests, or two out of four permitted exchanges. The denominators answer different questions. Neither ratio measures real-world ABDM reliability, and neither establishes that a patient’s lifetime history is complete.
On a narrow screen, scroll the table horizontally to read all columns.
| Requests | Observed permission state | Receipt and follow-up |
|---|---|---|
| R1–R2: 2 requests | Declined | Respect the decision; continue with the clinic’s appropriate information and care process. |
| R3: 1 request | Expired without approval | Do not label records received. Review whether another appropriately explained request is needed. |
| R4: 1 request | Awaiting response | Retain a visible pending task with an owner; no receipt is assumed. |
| R5–R6: 2 requests | Permission recorded for the test scope | Expected fixture documents received; clinician review remains a separate step. |
| R7: 1 request | Permission recorded for the test scope | Partial receipt; identify the particular expected document still missing. |
| R8: 1 request | Permission recorded for the test scope | Transfer failed; follow the supported investigation or retry process. |
The receptionist and doctor need different explanations because they are doing different work. During registration, explain the identifier-related action actually being offered and retain the ordinary registration path. Before an exchange, explain what information is being requested, for what purpose and through the supported consent process. Avoid promising that entering a number reveals every medical record.
A useful locally adapted explanation might be: “We have recorded the identifier against the chart we checked with you. We have not yet received records from another provider. If a record request is appropriate, we will explain that step separately.” After a partial receipt, name the gap: “The earlier consultation document arrived; the test report we expected has not arrived yet.” These are original example scripts, not official consent wording.
When a family shares a phone, establish whose chart and whose requested records are involved before proceeding. A relative helping with a device should not cause the software or staff to silently switch the patient context. Route questions about representation, authority or disputed identity through the clinic’s appropriate process; do not improvise permission based only on possession of a phone.
A useful scope statement names the product, environment, supported workflow and record types, together with prerequisites. It separates what is working now from what requires registration, configuration, another provider or future development. A logo, broad integration phrase or roadmap entry cannot answer those questions.
Identify who is responsible for the clinic’s applicable setup, credentials, staff access, support and ongoing maintenance. Ask what evidence is available for the claimed integration status and whether it applies to the version being sold. Do not convert an ecosystem participation claim into a certification claim that has not been established.
Include commercial dependencies: setup fees, recurring charges, any provider costs and support exclusions. The most expensive misunderstanding may be operational rather than monetary—for example, assuming reception can complete a workflow that still requires an unassigned external setup step.
Keep a registration path for patients who do not provide ABHA. The Ministry’s statement that creation is voluntary should not be turned into a software dead end. Check any specific programme requirements separately rather than assuming that every private-clinic encounter must use the same process.
If a connection fails, distinguish a pending exchange from a missing patient chart. The clinic should be able to identify which local information is available and which requested external information has not arrived. The clinician decides how to proceed with the information and limitations of the encounter.
Recovery also needs patient matching. A later successful exchange should connect to the intended chart without creating another encounter or duplicating an already received document unnecessarily. Test retry behaviour and the visibility of unresolved work in the supported environment.
Source: MoHFW: Update on Ayushman Bharat Digital Mission, 6 February 2024
A record may arrive after the patient has left reception or after the consultation note has been completed. Decide who sees that arrival and how it reaches the responsible clinician. Reception can investigate delivery status, but should not infer that an old prescription remains current or reconcile conflicting treatment information merely to close a task.
In the eight-request example, R7 needs a named missing-document task and R8 needs technical follow-up. R5 and R6 still need the intended clinical review, even though their fixture receipts are complete. A shift handover should distinguish those responsibilities and preserve the source and dates of received documents. Copying content into a new note without that context can obscure where the information came from.
Close a task against the outcome it was created to achieve. Technical receipt can close a delivery investigation; it cannot close a clinician’s review task automatically. If the clinician later corrects or adds to the local record, use the established amendment process and preserve chronology rather than making the newly received information appear available at the original consultation time.
Moving a clinic from an old EMR to a new one involves its patient list, encounters, attachments, prescriptions and other agreed data. Consent-based exchange is a different workflow. Do not assume that connecting to ABDM automatically recovers every legacy record or preserves every field needed for clinic operations.
Inventory the old data and agree export, mapping, import validation, exceptions and access to retained originals. Separately evaluate any supported exchange capabilities. A clinic may need both projects, with different acceptance evidence and responsibilities.
Bractis’s interoperability page is first-party product context. Use it to frame questions, then inspect the current connection scope and configuration. This guide does not certify Bractis or any other product as satisfying a particular integration programme.
In a fictional demonstration, the clinic finds an existing patient chart and observes the supported ABHA identifier step. A subsequent exchange request remains pending, so no external report is presented as received. The clinic records identity handling as demonstrated and exchange completion as unresolved. When the request later succeeds in the demonstration environment, staff verify the source and patient match before the clinician reviews the information. Each result has its own evidence; an early success does not fill the later gaps.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Permission and receipt are different stages. Check the requested scope, the material actually available from the source and the transfer outcome. Keep partial or failed receipt visible, assign follow-up and avoid telling the clinician that an incomplete record set is complete.
It establishes the observed test-environment result. Verify the proposed clinic configuration, enabled sharing or receiving roles, supported record types, setup responsibilities and acceptance evidence separately before relying on the workflow.
The Ministry of Health and Family Welfare’s February 2024 update describes creation as voluntary. Keep a usable clinic registration path and check specific programme requirements separately.
No. Establish the exact capability, configured environment, supported records and evidence of consented exchange. Recording an identifier is only one possible step.
Do not assume that. Vendor migration requires its own data inventory, export, mapping and validation. Evaluate record exchange as a separate capability.
No. Review the scope and actual records received, their source and date, and any missing information relevant to the consultation.
Match the established local chart before linking the identifier. Test the software’s handling of uncertain matches and avoid creating a second chart solely because the identifier is new.
Updated on . Official sources establish the ecosystem facts cited above. The evaluation framework is original operational guidance and makes no product certification or universal programme-eligibility claim. No independent clinical or legal review is claimed.
Primary source for the 14-digit identifier and voluntary creation, checked 25 October 2026.
Primary description of the ecosystem and its building blocks, checked 25 October 2026. It does not establish the scope of a particular vendor.
Primary definitions of HIP and HIU and the scope of the health-data interchange guide, checked 25 October 2026. The procurement questions and eight-request ledger are original examples, not protocol status definitions or vendor certification.
First-party product context; verify the current connection and setup in a demonstration.
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
Specify an EMR export manifest, preserve clinical meaning, test FHIR claims and reconcile attachment defects before accepting clinic data portability.
Use 20 demo questions, a clinic brief, supplier evidence and a worked scoring model to compare EMRs for Indian OPDs.
Ask us to identify the current ABDM scope and prerequisites, then trace a fictional patient from local matching to the supported exchange result and an unavailable-connection fallback.
Request a clinic demo