Translate care into records a health system can use
A standards-led exchange layer for record generation, consent boundaries and country-specific national adapters—starting with India’s ABDM.
FHIR-oriented record generation
Krama Core provides an open Python foundation for producing structured health-record bundles from clinical context. Current interfaces and support are documented in the repository.
- FHIR-oriented document-bundle foundation
- Patient, practitioner and clinical context kept together
- Inspectable implementation rather than opaque payloads
- Apache 2.0 licensed Krama Core
ABDM integration
The India adapter is designed around ABDM’s identity, care-context linking and consented exchange responsibilities.
- Identity and ABHA-aware registration context
- Care-context and record-linking workflows
- Consent-aware exchange architecture
- Sandbox-first implementation discipline
Consent and security
Consent, facility boundaries and auditability are treated as part of the exchange route—not as a disclaimer added after the workflow.
- Consent state remains visible in the workflow
- Audit events attach to record movement
- Facility boundaries shape data access
- Security controls documented by implementation stage
Multi-country by design
The shared core separates clinical and patient workflows from the rules of a national exchange. India is the active product focus; Australia and the United States are architecture contexts, not launch commitments.
- Country adapter layer — swap the exchange, keep the product
- India · ABDM — active product focus
- Australia · My Health Record — system context
- United States · interoperable networks — system context
Start with one care journey.
Define what a pilot should prove in your facility or health system.