Quick answer: HIP (Health Information Provider) generates and shares health records — like a hospital or lab. HIU (Health Information User) requests and consumes those records — like an insurer or a referral doctor. HRP (Health Repository Provider) stores a patient's longitudinal health records on their behalf. A single facility can hold more than one role.

Why These Three Roles Matter

ABDM's entire consent-based data exchange model is built around clearly defined roles. Once you understand HIP, HIU and HRP, the rest of ABDM's architecture — Consent Manager flows, FHIR record formats, registration requirements — becomes much easier to reason about.

HIP: Health Information Provider

A Health Information Provider is any facility that creates health records as part of patient care. This includes:

  • Hospitals recording OPD/IPD visits, discharge summaries and procedures.
  • Diagnostic labs generating pathology and radiology reports.
  • Pharmacies recording dispensed prescriptions.
  • Clinics documenting consultations.

To act as a HIP, a facility must register on the Health Facility Registry (HFR), integrate with the ABDM gateway, and format records to the FHIR R4 standard — exactly what an ABDM connector handles automatically.

HIU: Health Information User

A Health Information User is any system that requests a patient's existing health records, with consent, to make a decision or provide care. Examples include:

  • An insurer reviewing a patient's medical history to process a claim.
  • A specialist requesting a referred patient's prior records before a consultation.
  • A second-opinion platform pulling lab results and prescriptions.

Every HIU request must go through the Consent Manager — the HIU cannot simply query for data without the patient explicitly approving that specific request.

HRP: Health Repository Provider

A Health Repository Provider stores a patient's health records over time on their behalf, typically as a longitudinal record store. Some HIPs also act as an HRP if they retain patient data long-term, though many facilities generate records without retaining an HRP role themselves.

Can One Facility Be More Than One Role?

Yes — and it's common. A hospital that both generates records (HIP) and requests a referred patient's history from another facility (HIU) holds both roles simultaneously. A large hospital group that also stores longitudinal patient data across branches may function as an HRP too.

RoleWhat It DoesTypical Example
HIPGenerates & shares health recordsHospital, lab, pharmacy
HIURequests & consumes health recordsInsurer, referral specialist
HRPStores longitudinal records on patient's behalfHospital chain, health record platform

How This Affects Your Integration

Knowing which role(s) your facility needs determines what your ABDM integration should prioritise. Most clinics and single-service labs only need HIP capability. Hospital groups and insurers typically need both HIP and HIU flows enabled from day one.

Key Takeaways

  • HIP creates records, HIU consumes them, HRP stores them long-term.
  • A facility can hold multiple roles at once.
  • Every HIU data request is gated by patient consent through the Consent Manager.
  • An ABDM connector pre-builds support for all three roles so you don't need to implement them individually.