Milestone 2 — HIP Data Sharing

Implement the HIP role, link care contexts, and share encrypted FHIR records after patient consent.

Milestone 2 makes your system a Health Information Provider (HIP). Create patient records, link them to an ABHA, and share them after consent.

Scope

Act as the HIP for each registered facility.

Create health records in ABDM FHIR R4 format.
Group records into clear care contexts.
Link each care context to the patient's ABHA.
Support user-initiated Discovery & Link.
Accept health information requests after consent.
Encrypt FHIR bundles and push them to the HIU.
Send status notifications to HIE-CM.

Prerequisites

Before you start Milestone 2, complete these tasks.

Prerequisite	Why it matters
Facility ID	HIE-CM routes HIP calls to this facility.
HIP role registration	ABDM authorizes the bridge to link and share records.
Bridge callback URL	HIE-CM sends discovery, link, consent, and data requests to this URL.
Gateway access token	Your HIP calls HIE-CM APIs with this bearer token.
FHIR bundle generator	The HIP must build NRCeS-conformant FHIR R4 documents.
Encryption implementation	The HIP must encrypt each health data payload for the HIU.

Health record formats

The source states that HRP/HIP systems can link only these health records. All health records must use the NRCeS ABDM FHIR R4 profiles.

Health record type	Use
Diagnostic Report Record	Share laboratory and radiology reports.
Discharge Summary Record	Share a discharge summary for an inpatient admission.
Health Document Record	Share unstructured documents, scans, or PDFs.
Immunization Record	Share vaccines, certificates, and next-dose advice.
OP Consult Record	Share outpatient notes, examinations, medicines, and advice.
Prescription Record	Share medication advice that follows PCI guidance.
Wellness Record	Share vitals, examination data, and wellness data.
Invoice Record	Share billing details, pharmacy invoices, and consultation invoices.

HMIS HI types

The source states that HMIS implementations must implement all listed HI types. Confirm your declared HI types during ABDM certification.

Care contexts

A care context is a reference to a logical group of records. Use one care context per OPD visit or IPD admission.

HIE-CM remains data-blind. It stores only identifiers and metadata for each care context. It does not store the clinical record.

Component	Rule
Reference ID	Use a unique ID from the HIP system.
Display name	Use a clear label that helps the patient select records.
Sensitive data	Do not include diagnoses, results, or confidential data.

Care context shape

{
  "patient": {
    "referenceNumber": "TMH-PUID-001",
    "display": "TMH records for Kiran Kumar",
    "careContexts": [
      {
        "referenceNumber": "VISIT-2375639",
        "display": "OPD records for 03 Oct 2022"
      }
    ]
  }
}

Milestone 2 implementation guides

HIP-initiated linking

Link records to ABHA after the patient shares an ABHA at the facility.

Discovery & Link

Let a patient discover and link records from a PHR app.

Data transfer

Handle consent, package FHIR bundles, encrypt data, and push to an HIU.

Certification scenarios

Prepare these scenarios before Milestone 2 certification.

Link a new care context with a valid link token.
Reject a link request when the link token is invalid or expired.
Return only unlinked records during Discovery & Link.
Complete link init and link confirm with OTP validation.
Receive a granted consent artefact and acknowledge it.
Reject data requests outside the consent date range.
Build valid FHIR bundles for each declared HI type.
Encrypt each bundle and push it to the HIU data push URL.
Send transfer notifications with success and failure states.

Sources

ABDM Proposed Simplified Milestone 2 (DOCX→MD, 2026-08)

PreviousM1 · Benefit Programs Next M2 · HIP-Initiated Linking