The short answer
Most hospitals start as a Health Information Provider (HIP) because they already hold records that patients may want to access. A Health Information User (HIU) is for organisations that need to request records from others, such as a hospital that wants a patient's earlier history, an insurer or a digital-health app.
What a HIP does
- ✓Registers its facility and links patient care contexts to ABHA.
- ✓Responds to discovery and linking requests routed through the gateway.
- ✓On consent, prepares records as FHIR bundles and sends them securely to the requester.
- ✓Keeps an audit trail of what was shared, with whom and when.
What a HIU does
- ✓Raises a consent request describing the purpose, record types and date range.
- ✓Receives and decrypts the data after the patient approves.
- ✓Stores or displays the data only for the approved purpose and period, then deletes or expires it as required.
How to decide
- 1.Do patients ask for their records? Build the HIP role first.
- 2.Do your clinicians struggle without prior history from other providers? Plan the HIU role next.
- 3.Do you operate both a provider and a service that consumes data? You will likely need both, with clearly separated consent and storage rules.
Engineering differences that matter
A HIP is mostly an export problem: turning your internal data into correct FHIR. A HIU is mostly a storage and presentation problem: handling data you did not create, for a limited purpose. Both need strong consent handling and audit logging. Read the overview of ABDM integration and the milestone checklist to see where each role fits.
To understand the data format you will produce or consume, see FHIR R4 resources for hospital integration.
Frequently asked questions
Can a hospital be both a HIP and a HIU?
Yes. Many hospitals eventually do both, but they are usually built and certified as separate capabilities.
Does a HIU need patient consent every time?
Yes. Access to a patient's records requires the patient's consent for a stated purpose and time period.
Which role is faster to build?
Often the HIP role is the first deliverable because the data already exists in your HIS, though data quality can make it slower than expected.
Need help with this in your hospital?
Tell us your systems and your goal. We'll map it to a scoped plan.
Talk to our team →This guide is general information for engineering and planning purposes. It is not legal advice, and regulations and specifications change; confirm current requirements with the relevant authority or qualified counsel.
