Patient records.
Connected with consent.
Bring identity, consent, and record exchange into one traceable workflow. Keep the source, version, and review state visible as information moves between care settings.
Talk to us about your clinic.
Connect the record
with the patient’s permission.
Start with the right identity, explain the exchange, and follow the record through confirmation and review.
See the permission
and the exchange state.
Keep the care context, consent, and provider confirmation connected. Show the difference between a request, a completed exchange, and information awaiting reconciliation.
Consent and exchange
The record tells you what happened
Aarav Sharma · care context 004128
Purpose
Share this visit summary with the patient-selected health record.
Data
Encounter, prescription, and patient-facing instructions.
Alternative
Continue care without ABHA or exchange consent.
Illustrative record-exchange workflow with sample data. No health record is exchanged.
- Optional ABHA and identity flows with duplicate controls
- Care-context creation and consent lifecycle
- FHIR mapping with source/version provenance
- Exchange status, retry, reconciliation, and accessible alternatives
Match the patient.
Keep access to care open.
Support optional ABHA and identity flows with duplicate controls. A missing identifier must not block care or force an unrelated consent decision.
Keep identity matching explicit so records are connected to the intended person.
Explore patient registration- 01Find or create the patient record
- 02Review possible duplicates
- 03Keep an accessible path without ABHA
- 01Purpose and information requested
- 02Recipient and duration
- 03Withdrawal and its consequences
Make the sharing decision
understandable.
Explain what information is requested, why it is needed, who receives it, and for how long. Keep withdrawal and its consequences clear.
Consent for record exchange stays separate from unrelated clinic actions and optional services.
Keep the source
with the clinical information.
FHIR mapping and imported records need source and version information. Keep external information distinguishable while it is awaiting review.
When identity, content, or exchange outcomes do not match, make reconciliation visible before treating the record as resolved.
Read the record portability guide- 01Origin and version of the record
- 02Requested and confirmed exchange states
- 03Review and reconciliation status
Evaluate the connection
with its boundaries in view.
Patients need understandable choices. Clinic administrators need exchange status and unresolved work. Procurement teams need evidence for interoperability claims.
Patient
Choose whether and where a record is shared with understandable consent.
Clinic admin
See exchange status, provider boundaries, and unresolved reconciliation.
Procurement
Review staged interoperability claims against evidence and release gates.
ABHA is optional for care access
Consent is separate from unrelated clinic actions
FHIR output keeps source, version, and reconciliation state visible
Review interoperability scope and availability
Bractis is preparing for launch. Current evaluation status: planned. Last reviewed: 2026-08-12.
Pilot scope: this page describes the intended workflow and safe demonstration states, not a live patient record.
ABDM and FHIR claims remain staged until certification, consent, exchange, and reconciliation gates pass.
Connect records
to continued care.
Explore all capabilitiesQuestions about
connected health records.
How patient choice, record sources, and exchange status fit together.
Is ABHA required to receive care?
No. ABHA is optional for care access. The workflow must retain an accessible path when an identifier is unavailable.
What should patients see before consenting?
The purpose, information requested, recipient, duration, withdrawal path, and consequences should be explained in understandable language.
Are imported records automatically treated as reviewed?
No. Source, version, and reconciliation state remain visible. Imported information needs the appropriate review before clinical use.
Is Bractis certified for ABDM exchange today?
This page makes no certification claim. ABDM and FHIR capabilities remain staged until certification, consent, exchange, and reconciliation gates pass.
Can we discuss our integration requirements?
Yes. Contact Bractis with your record types, exchange needs, and provider requirements. The product is preparing for launch.
Tell us which records
your clinic needs to connect.
Let’s discuss patient identity, consent, and the information your team exchanges.
Talk to Bractis