FHIR R4 · Early Access

Healthcare data,
made interoperable.

Reli converts messy clinical data — CSV, JSON, HL7 — into ABDM-compliant FHIR R4 records. All the ABDM compliance, none of the pain.

Get API Access → See how it works

from reli import ReliBridge
 
# Initialize with your Reli API key
bridge = ReliBridge(
    api_key="reli_live_sk_xxxxxxxxxxxx",
)
 
# Ingest CSV, map to FHIR R4, link to ABHA
result = bridge.ingest(
    source  = "lab_reports_q1.csv",
    hi_type = "DiagnosticReport",
    abha    = "john.doe@abdm",
)
 
✓  records mapped to FHIR R4 (NRCeS profiles)
✓  care contexts linked to ABHA
✓  HIP registered with NHA gateway
        

Process

From raw data to ABDM-ready
in four steps

No ABDM expertise needed on your end. Reli’s pipeline handles the entire clinical data lifecycle — from ingestion to compliant API exposure.

01 · INGEST

Ingest

Accept clinical data in any format: CSV exports from LIS, JSON from EMRs, HL7 v2.x messages from legacy HIS. No format is too messy — we’ve seen them all.

02 · MAP

Map

Our NRCeS-aware mapping engine transforms data into FHIR R4 resources — DiagnosticReport, Observation, Patient, Condition — with full SNOMED CT and LOINC coding.

03 · LINK

Link

Associate records with ABHA IDs, create care contexts on the NHA gateway, and manage ABDM consent artefacts — all from a single API call.

04 · EXPOSE

Expose

Serve FHIR bundles through ABDM-compliant HIP and HIU APIs. Your system joins India’s national health data network — instantly.

Capabilities

Everything ABDM integration requires

We built Reli while working through ABDM integration ourselves. This is the tool we wished existed.

FHIR R4 / NRCeS Aligned

Full FHIR R4 implementation aligned with NRCeS (National Resource Centre for EHR Standards). Every resource is validated against India’s national health data profile before it leaves the pipeline.

fhir-r4 · nrces

HIP + HIU Ready

Reli is designed to support both HIP and HIU roles on the ABDM network. We handle the gateway integration layer so you can focus on your product.

hip · hiu · abdm

Consent Flows

Consent artefact creation, management, and revocation built into the pipeline. Patients stay in control of their health data; your product handles it correctly.

consent · artefacts

Smart Mapping Engine

Declarative YAML mapping configs with conflict resolution, custom field transformers, and partial-record handling. Auto-map 90% of fields; tune the rest with a low-code editor.

mapping · transformers

Security & DPDP Act

End-to-end encryption, immutable audit trails, and data processing aligned with India’s Digital Personal Data Protection Act 2023.

dpdp · encrypted · audit

Developer-First API

Clean REST API with full OpenAPI spec, webhook support, and a sandboxed ABDM environment for safe end-to-end testing before you go live. Python SDK in development.

rest · webhooks · sandbox

Who it’s for

Built for India’s health data ecosystem

Whether you’re onboarding ABDM for the first time or scaling an existing HIP integration, Reli fits your stack without replacing it.

Diagnostic Labs

Ingest LIS exports, map them to DiagnosticReport and Observation resources, and link patient ABHA IDs — without touching your existing LIS workflow or vendor contract.

CSV → FHIR R4 · ABHA link · HIP reg

Clinic Chains

Build toward ABDM integration across every branch without rewriting your EMR. Reli sits as a thin translation layer between your existing systems and the NHA gateway, with non-invasive integration.

EMR bridge · multi-branch · non-invasive

Healthtech Startups

Skip six months of ABDM documentation and compliance work. Ship your product’s core value, not FHIR plumbing. Dramatically reduce your ABDM integration timeline. Integrate with Reli’s API in days — ABDM certification supported.

API-first · days to live · sandbox env

Health AI Companies

Access structured, standardized FHIR data streams for model training and inference pipelines. Clean, coded data in — better models out. No custom preprocessing required.

FHIR streams · coded data · LOINC / SNOMED

Healthcare data,made interoperable.

From raw data to ABDM-readyin four steps