ABDM M2 - harikrushnav/fhir_document GitHub Wiki
Here is a list of Health Records, based on FHIR’s specifications:
| Name | Definition |
|---|---|
| Diagnostic Report Record | The Clinical Artifact represents diagnostic reports including Radiology and Laboratory reports that can be shared across the health ecosystem. |
| Discharge Summary Record | Clinical document used to represent the discharge summary record for ABDM HDE data set. |
| Health Document Record | The Clinical Artifact represents the unstructured historical health records as a single of multiple Health Record Documents generally uploaded by the patients through the Health Locker and can be shared across the health ecosystem. |
| Immunization Record | The Clinical Artifact represents the Immunization records with any additional documents such as vaccine certificate, the next immunization recommendations, etc. This can be further shared across the health ecosystem. |
| OP Consult Record | The Clinical Artifact represents the outpatient visit consultation note which may include clinical information on any OP examinations, procedures along with medication administered, and advice that can be shared across the health ecosystem. |
| Prescription Record | The Clinical Artifact represents the medication advice to the patient in compliance with the Pharmacy Council of India (PCI) guidelines, which can be shared across the health ecosystem. |
| Wellness Record | The Clinical Artifact represents regular wellness information of patients typically through the Patient Health Record (PHR) application covering clinical information such as vitals, physical examination, general wellness, women wellness, etc., that can be shared across the health ecosystem. |
| Invoice Record | This billing HI type comprises of invoice details such as pharmacy invoice, consultation invoice etc. |
ABDM design is aligned with India’s Personal Data Protection Bill, that is the exchange of health data can only happen with the consent of the User.
The entity requesting access to the data (HIU), needs to provide the following information:
The purpose for which they want access to data
The historical time period of health data
The type of health records
How long they wish to keep the copy of the data
ABDM uses an electronic consent artefact based on MEITY’s electronic consent framework to allow HIUs to specify their consent request.
Users can modify any of the request consent parameters, and provide a consent approval that suits them.
Users have the option to revoke the consent they have provided to the HIU, at any time. The HIU must remove any copy of the user’s data when the consent is revoked.
All HIPs who are holding any data associated with this consent are notified. They must save a copy of the consent artefact in their system.
Data can be shared against this consent any number of times till the consent expires / is revoked by the user.
FHIR Documents
- As explained in the APIs and Standards section, the following are the Health Information (HI) Types that are currently supported. The document type codes must be specfied as per the defined SNOMED-CT codes specified below. Please check the “Main Envelope” section to see example.
| Code | Display | SNOMED-CT code |
|---|---|---|
| Prescription | Prescription | 440545006 |
| DiagnosticReport | Diagnostic Report | 721981007 |
| OPConsultation | OP Consultation | 371530004 |
| DischargeSummary | Discharge Summary | 373942005 |
| ImmunizationRecord | Immunization Record | 41000179103 |
| HealthDocumentRecord | Record artifact | 419891008 |
| WellnessRecord | Wellness Record | N/A (Should match exact text Wellness record) |
ABDM FHIR https://nrces.in/ndhm/fhir/r4/index.html