MindFlow is designed to operate as both a Health Information Provider (HIP) and Health Information User (HIU) within India's ABDM (Ayushman Bharat Digital Mission) ecosystem. All health record sharing is patient-initiated and consent-gated, records are never shared automatically.
Patients or staff can initiate creation of a new 14-digit ABHA number from within the clinic or from the patient portal. The verification flow follows the official NHA ABDM v3 specification, OTP-based identity verification via mobile or Aadhaar. No third-party intermediaries are involved.
Patients who already have an ABHA number can link it to their clinic record. The link is verified through the same OTP flow and is stored against the patient for all subsequent ABDM interactions.
The ABDM verification flow is multi-step. The system maintains the in-progress state of each verification session securely on the server, the patient does not need to restart if they switch screens between OTP steps.
Every call made to the ABDM API on behalf of a patient, including the transaction ID, action, ABHA address, and timestamp, is logged. Clinic admins can review this log for compliance purposes.
Consent artefacts, including the consent ID, purpose, date range, types of data consented, and expiry, are stored per patient. Revoking consent immediately stops any further data sharing. Every consent grant and revocation is logged immutably.
When a patient grants consent to pull their records from another health facility, the system fetches the relevant FHIR bundles from the PHR (Personal Health Records) system and makes them available in the patient's record in the clinic application. The clinician sees records from other facilities alongside their own notes.
When a patient consents to share their records from this clinic to another facility, the system constructs a FHIR Bundle of the relevant clinical records and transmits it through the ABDM PHR system. The receiving facility receives standard FHIR resources, not proprietary formats.
The integration handles ABDM v3 callback events, Discovery, LinkConfirm, and NotifyOnAddContexts, separately from the earlier v1/v2 flow, as required by the NHA's updated specifications. A local webhook receiver is available for testing in the ABDM sandbox environment.
ABDM requires inbound callback events to be acknowledged within 7 seconds. The system is designed to return an acknowledgement immediately and process the event asynchronously, ensuring compliance with the strict response-time requirement.
FHIR R4 (version 4.0.1), the version required by the ABDM HL7 FHIR Implementation Guide for India and the version supported by the NHA PHR system.
The system can generate the following FHIR R4 resources from clinical data: Patient, Practitioner, Organization, Encounter, Condition (with ICD-11 coding), Observation (vitals and assessment scores), MedicationRequest, DiagnosticReport (lab results), AllergyIntolerance, and Bundle. Records can be downloaded as a FHIR Bundle JSON from the admin interface.
Diagnoses stored with WHO ICD-11 codes are exported as FHIR Condition resources with the coding system set to the official WHO linearisation URI, as required by the ABDM Implementation Guide. This ensures interoperability with all ABDM-compliant receiving systems.
The facility's HIP certificate and private key (issued by NHA) are stored encrypted at rest. They are loaded at runtime only when needed to sign ABDM API calls. Key rotation can be performed from the admin interface without system downtime.
The integration supports a clean switch between the ABDM sandbox testing environment and the production environment via a single configuration setting, no code changes required to promote from testing to live.
The demo comes pre-loaded with real sample data, so you can click through actual appointments, patients and prescriptions.