Systems
Government & Regulatory
The national rails and registries, reached over the one governed outbound path.
What this class of system is
These are India’s national health-data rails and registries: ABDM, GST, and the IRDAI / NHCX claims exchange.
Pensieve speaks FHIR R4 (ABDM and NHCX) and the GST API over the governed outbound path. Out: ABHA linkage, claims, and e-invoices; in: registry context. Gate, Vault, Nexus, and Cirith consume and produce the data.
Everything above rides one path. The on-prem orophin agent speaks the protocol on the hospital's own network and opens a single outbound mutually authenticated link to the Pensieve backend. Your network team approves egress.
On the wire
What it emits, and what carries it
The traffic
A national rail is an identity problem before it is a data problem. The facility is registered on the HFR, clinicians on the HPR, and the patient carries an ABHA that Gate creates or links at registration. Records are published to that ABHA as FHIR R4 under a consent artefact issued by the HIE-CM, and claims leave over NHCX in the same resource vocabulary.
What breaks here
Linkage is voluntary for the patient and a refusal cannot obstruct treatment, so ABHA can never be a required field in a registration flow. Gate treats it as an optional identity that unlocks publication when present and changes nothing when absent. Milestone alignment is an implementation target here, and this page says so rather than printing a badge.
Protocols
The standards this class speaks
Each one is described in full on the standards register, at the anchor named here.
- FHIR R4Modern REST / JSON resources: Patient, Encounter, Observation, ServiceRequest, DiagnosticReport, Claim, Coverage. Pensieve speaks FHIR R4 for record exchange, ABDM linkage, and NHCX claims.
- CSV / flat fileThe fallback for a system with no live interface. orophin watches a drop folder for scheduled exports and reads each file once.
- mTLS WebSocket bridgeThe single outbound, mutually authenticated link orophin opens to the Pensieve backend. Both ends verify a certificate, nothing listens on the hospital side, and every row in this register rides it.
- OIDC SSOOpenID Connect sign-in for a hospital identity provider.
- ABDM (ABHA / HIE-CM)India’s national health-data rails: FHIR-R4 ABHA linkage and consent-driven sharing through the Health Information Exchange and Consent Manager.
- HFR / HPR registriesThe ABDM Health Facility Registry and Healthcare Professionals Registry. Facility and professional context is held in Nexus, beside orgs, sites, users and roles.
- NHCX claimsThe FHIR-based National Health Claims Exchange, built jointly by the National Health Authority and IRDAI. Vault packages pre-auth and claims to it.
- GST e-invoicing APIIndia’s e-invoicing rails. Vault produces GST-correct invoices for the Invoice Registration Portal, with the tax treatment carried as an attribute of the charge rather than applied at the end.
Members
Systems in this class
14 entries on the register, each at its own anchor.
- ABHA creationABDM FHIR R4. Out: create or link an ABHA at Gate registration.
- HIE-CM (consent manager)ABDM FHIR R4 / consent. In/out: consent-driven record sharing.
- HFR (facility registry)ABDM HFR API. In: facility registration context held in Nexus.
- HPR (professional registry)ABDM HPR API. In: HPR-linked professional context for clinicians.
- Health Records linkingABDM FHIR R4. Out: publish records to the patient ABHA with consent.
- Scan & ShareABDM API / QR token. In: token-based OPD registration from a scanned QR.
- ABDM Milestone M1/M2/M3ABDM sandbox conformance. Built to the ABDM M1/M2/M3 milestone framework, an alignment target rather than a certification.
- NDHM sandboxABDM sandbox. In/out: a test endpoint for exercising ABDM integration.
- PMJAY / Ayushman BharatFHIR R4 / REST (PMJAY). Out: scheme claims. In: eligibility and approval.
- ECHSREST API / CSV. Out: scheme claims. In: approval.
- CGHSREST API / CSV. Out: scheme claims. In: approval.
- IRDAI e-claimFHIR R4 / REST API. Out: standardised claim submission.
- GST IRP portalGST e-invoicing API. Out: e-invoices to the Invoice Registration Portal.
- NHCXFHIR R4 (NHCX). Out: pre-auth and claims. In: adjudication and settlement.
What a name in this register means
Compatibility only. Pensieve connects to systems in this class over the protocol they speak. Naming a system describes the connection Pensieve is built to make; it implies no partnership, no certification, and no existing deployment.