Is AJ Commons software free to use?

Yes. All AJ Commons components are licensed under the Apache License 2.0 — free to use, modify, and distribute with no usage fees, no call-home telemetry, and no proprietary lock-in. You can self-host on your own infrastructure or air-gapped government cloud.

AJBridge is an open-source HL7v2 to FHIR R4/R5 integration gateway. It receives ADT, ORU, ORM, OML, and MDM messages via MLLP and converts them to FHIR resources. It includes ATNA audit, consent enforcement, and SMART token validation. It is a drop-in OpenHIM-compatible replacement.

What is a Master Patient Index and does AJ Commons have one?

A Master Patient Index (MPI) is a system that uniquely identifies patients across multiple healthcare facilities, eliminating duplicate records. AJMPI is AJ Commons' open-source MPI with probabilistic matching, golden record management, and IHE PDQm, PIXm, and PMIR conformance.

Which programming language and runtime does AJ Commons use?

All AJ Commons components are built on Java 21 (OpenJDK) and Spring Boot 3, using HAPI FHIR JPA v7.4.5 as the FHIR server. All dependencies are open source under Apache 2.0 or compatible licences. Components can be deployed via Docker Compose on any POSIX OS or cloud environment.

Does AJ Commons support ABDM — Ayushman Bharat Digital Mission?

Yes. AJ Commons components align with ABDM Health Data Management Policy and ABDM FHIR profiles. AJConsent implements the consent framework required by ABDM. AJBridge supports HL7v2 to FHIR conversion aligned with ABDM's interoperability requirements. AJMPI supports the patient identity resolution patterns used in ABDM's Health ID system.

AJ Commons — Open Source FHIR Health Infrastructure Foundation

Q: Are AJ Commons projects Digital Public Goods?

AJ Commons components are being submitted to the Digital Public Goods Alliance (DPGA) as Digital Public Goods under SDG 3 — Good Health and Well-Being. All components are Apache 2.0 licensed. Stewarded by Dr. Akriti Jamwal Foundation — a registered Section 8 not-for-profit company in India (CIN: U88900BR2026NPL086460, incorporated under the Companies Act, 2013). This provides permanent, independent, non-commercial governance over all AJ Commons IP.

Our story

Built from the gaps a clinician sees every day

AJ Commons was founded by Dr. Akriti Jamwal, a dentist with an MBA in Health Informatics who saw the data fragmentation problem from both sides of the stethoscope. A clinician who became Co-Founder and CEO of dChikitsa — a digital health platform serving hospitals and clinics across India — she built firsthand knowledge of what EMR interoperability and health information exchange look like on the ground, not in a whitepaper.

The tools to fix this existed — HL7 FHIR, SMART App Launch, IHE profiles — but the open, deployable implementations that low-resource health systems could actually use did not. AJ Commons builds them.

Every component is built to run in a district hospital in Bihar as reliably as it runs in a teaching hospital in Colombo. No proprietary lock-in. No usage fees. No cloud dependency. Just open infrastructure that works.

Founder

Dr. Akriti Jamwal

Dentist · MBA in Health Informatics · Co-Founder & CEO, dChikitsa · Co-Founder, Akhester Technologies · HL7 FHIR · openEHR

LinkedIn ↗

Mission

To build and steward open FHIR health data infrastructure that any government, hospital, or implementer can deploy freely — advancing universal health coverage through shared public digital goods.

Model

Open core — AJ Commons components are free forever. The commercial Jam Platform (built on these components) sustains ongoing development. Same model as OpenMRS, OpenFn, and DHIS2.

Health data should flow as freely as health itself — across facilities, across systems, across borders — with the patient's consent and under open governance.

Open by default

Every component Apache 2.0 licensed. No proprietary lock-in, no call-home telemetry, no usage fees. Deploy on your own infrastructure or air-gapped government cloud.

Standards first

Built entirely on HL7 FHIR R4/R5, SMART App Launch v2.2, IHE profiles, and WHO SMART Guidelines. No proprietary protocols — interoperable with every standards-compliant system.

Built for LMIC scale

Designed for national digital health deployments in low- and middle-income countries — low resource requirements, DHIS2 integration, offline-capable nodes, PEPFAR reporting built in.

Openly governed

Stewarded by Dr. Akriti Jamwal Foundation — a registered Section 8 not-for-profit company (India, CIN U88900BR2026NPL086460). Community Code of Conduct, public roadmap, open contribution process. Pursuing Digital Public Goods certification under the DPGA Standard.

Components

Nine independently deployable components

Use what you need. Replace what you have. Every component works alone or as part of the full AJ Commons stack.

Component

Function

Status

Links

AJBridgeHL7v2 → FHIR Gateway

Connects your hospital HIS to the FHIR ecosystemMLLP reception for ADT, ORU, ORM, OML, MDM messages. Converts HL7v2 to FHIR R4/R5. ATNA audit, consent enforcement, SMART token validation. Drop-in OpenHIM-compatible replacement.

Coming soon

GitHub

AJMPIMaster Patient Index

Resolves patient identity across every connected facilityProbabilistic matching, golden record management, IHE PDQm / PIXm / PMIR conformant. Eliminates duplicate patient records at national scale.

Coming soon

GitHub

AJConsentConsent Manager

Patient-controlled data access with GDPR · HIPAA · DISHA complianceFHIR R4/R5 Consent resource lifecycle. Patient self-service portal. Deny-by-default enforcement. IHE ATNA audit trail. 181 tests.

Stable v1.0.0

Docs GitHub

AJHFRHealth Facility Registry

The authoritative directory of every hospital and clinic in your networkmCSD-conformant IHE ITI-90 search. Admin portal. Auto-provisioning from HL7v2 MSH-4 facility codes. Used to route HL7 messages and resolve facility identifiers across the HIE.

Coming soon

GitHub

AJGuardCross-Facility Safety

Catches what no single hospital can see aloneDrug interaction and allergy checks across all connected facilities. CDS Hooks integration fires at point of prescribing. Cross-facility medication history. Population safety surveillance for MoH reporting.

Coming soon

GitHub

AJAuthSMART Auth Server

Complete SMART App Launch v2.2 authorisation serverPKCE S256 enforced. Atomic launch tokens. RS256 JWT with JWKS. Azure AD · Okta · Epic IdP federation. 90 tests. Production-ready alternative to Keycloak SMART extensions.

Stable v0.2.3

Docs GitHub

AJConnectCDS Hooks Engine

Clinical decision support at the moment of careCDS Hooks 2.0 service orchestrator. Aggregates hooks from multiple CDS providers. Feeds AJGuard safety alerts to any SMART-enabled EHR at point of prescribing or ordering.

Coming soon

GitHub

AJImmuniseVaccination App

WHO-schedule vaccination management with digital certificatesSMART on FHIR vaccination history. WHO schedule forecasting. Printable WHO VDS-NC digital certificates with QR codes. Aligned with GAVI and NIP reporting requirements. 28 tests.

Stable v1.0.0

Docs GitHub

AJReferralCross-Facility Referral

Tracks patients across facility boundaries, from referral to receiptFHIR R4/R5 ServiceRequest + Task state machine. IHE MHD document exchange. Real-time status notifications. Prevents patients from being lost between facilities.

Stable v1.0.0

Docs GitHub

Full technical documentation at docs.ajcommons.org · All components Java 21 · Spring Boot 3 · Apache 2.0

National HIE — how data flows through AJ Commons From hospital HIS to population health

AJImmunise and AJReferral operate independently or alongside the full stack. Technical documentation: docs.ajcommons.org/architecture

Standards alignment

Built on open standards, not proprietary protocols

Every component implements published international standards. No vendor lock-in. Interoperable with any conformant system.

HL7 International

FHIR® · SMART® · CDS Hooks · HL7v2 · IPS

FHIR® R4 FHIR® R5 SMART® App Launch v2.2 CDS Hooks 2.0 IPS — Patient/$summary FHIR Bulk Data $export FHIR Subscriptions (rest-hook) HL7v2 ADT · ORU · ORM · OML · MDM · RDE · SIU MLLP — 7 ports / 7 message types QBP Q22 / RSP K22 (PDQ v2)

FHIR R4 and R5 resource types across all components. SMART App Launch v2.2 with PKCE S256 enforced. CDS Hooks 2.0 for real-time clinical decision support (AJGuard fires on medication-prescribe, patient-view, encounter-discharge, order-sign). IPS Patient/$summary with 10-section parallel assembly and Redis cache. FHIR Bulk Data $export for population-level reporting. Full FHIR rest-hook subscription engine (13 criteria types). HL7v2 MLLP on 7 dedicated ports — ADT A01-A40, ORU R01, ORM O01/OML O21, MDM T02, QBP Q22, RDE O11, SIU S12-S17.

IHE — Integrating the Healthcare Enterprise

ITI · RAD · BALP — 16 transactions

ITI · ATNA (ITI-8, ITI-20) ITI · BALP (FHIR AuditEvent) ITI · PDQm (ITI-78) ITI · PIXm (ITI-83) ITI · PMIR (ITI-93, ITI-94) ITI · MHD (ITI-65, 66, 67, 68) ITI · MHD (ITI-105, ITI-106) ITI · mCSD (ITI-90) ITI · IUA (Internet User Auth) ITI · XDS.b RAD · DICOM DIMSE

Full IHE ITI profile implementation. ATNA audit on 138 sites across all services — RFC 5425 TLS syslog (ITI-20) to syslog-ng plus FHIR R4 AuditEvent POST (IHE BALP) to HAPI. MHD v4.2.3 complete — all six transactions including ITI-105 Simplified Publish and ITI-106 Generate Metadata from CDA. PMIR ITI-93/94 with async fan-out to downstream subscribers. IUA wraps SMART on FHIR token validation. mCSD ITI-90 with 6-hour facility cache. XDS.b document sharing. DICOM DIMSE for radiology. OpenHIM mediator-compatible via self-registration protocol.

Clinical Terminology

SNOMED CT · LOINC · ICD · RxNorm

SNOMED CT (Snowstorm) LOINC ICD-10 / ICD-11 RxNorm (NLM API) UCUM FHIR $expand · $translate · $validate-code

Snowstorm SNOMED CT server with ECL queries and subsumption. LOINC code binding on FHIR ValueSets with local lab code overlay (28 Sri Lanka codes). ICD-10 ↔ SNOMED CT cross-maps. RxNorm NDC normalisation via NLM API — used by AJGuard for cross-facility drug-drug interaction checking. UCUM units on all Observation resources. Federated terminology federation: local → Snowstorm → NLM.

Infrastructure · openEHR · Security

Apache Camel · openEHR · mTLS · Redis

Apache Camel (routing) openEHR RM / EHRBase / AQL DICOM DIMSE + STOW-RS mTLS (client cert) OAuth 2.0 / PKCE S256 RS256 JWT / JWKS rotation Redis (IPS cache) Prometheus · Grafana

Apache Camel drives all 7 MLLP routes and FHIR gateway routing in AJBridge. openEHR archetypes and operational templates via EHRBase with AQL. DICOM DIMSE for PACS and STOW-RS for web-based imaging. mTLS for high-security hospital integrations. Redis-backed IPS cache (<100ms warm). 20+ Prometheus counters per service, 4 Grafana dashboards, 11 Alertmanager rules.

National · WHO · DPG · Observability

NDHB · WHO · DHIS2 · Apache 2.0

India NDHB 2019 WHO SMART Guidelines WHO VDS-NC (vaccination) DHIS2 direct integration ONC HTI-1 / Inferno PEPFAR reporting DPG Standard v1.1.6 Country-agnostic OID config Apache 2.0

India NDHB 2019 aligned. WHO SMART Guidelines for computable clinical guidance. WHO VDS-NC vaccination certificates with QR codes. DHIS2 direct integration via Dhis2SurveillanceMediator — 5 notifiable diseases configured, LOINC→DHIS2 data element mapping. Country-agnostic deployment: all OIDs, MRN systems, national ID systems, and clinical thresholds configured via deployment.yml — same binary, different config for Sri Lanka, Kenya, Nepal, Bangladesh.

Governance

Open governance, not corporate control

AJ Commons projects are independently stewarded. The code is not at the mercy of any single organisation's commercial decisions.

Who stewards AJ Commons

AJ Commons is stewarded by Dr. Akriti Jamwal Foundation — a registered Section 8 not-for-profit company under the Companies Act, 2013 (India). As a non-profit, the foundation cannot distribute profits or be acquired; its sole mandate is the long-term public-interest stewardship of AJ Commons. All projects are licensed under Apache 2.0 — meaning no single entity controls the code's future. Any conformant implementer may fork, deploy, or build on the work.

📋 Foundation Registration Details

Legal Name	Dr. Akriti Jamwal Foundation
Entity Type	Section 8 Company (Not-for-Profit) · Companies Act, 2013
CIN	U88900BR2026NPL086460
Issuing Authority	Central Registration Centre, Ministry of Corporate Affairs, Govt. of India

The commercial Jam platform — built on these open components — is maintained by Akhester Technologies, a founding sponsor of the foundation. Commercial revenue sustains open source development. This is the open-core model that powers OpenMRS, OpenFn, and DHIS2.

Governance commitments

Apache 2.0 licence — permanent, irrevocable, on every repository

Public CODE_OF_CONDUCT.md and CONTRIBUTING.md in every repo

Public roadmap — decisions made openly via GitHub Discussions

No call-home telemetry, no usage metering, no licence keys in OSS components

DPG Standard compliance — applications submitted to DPGA for each component

Digital Public Goods

Open infrastructure for the public interest

AJ Commons components are being submitted to the Digital Public Goods Alliance as Digital Public Goods under SDG 3 — Good Health and Well-Being. This page is the publicly accessible ownership and licence evidence referenced in each DPGA application (ajcommons.org/#dpg).

Legal Owner

All AJ Commons projects are owned and stewarded by Dr. Akriti Jamwal Foundation — a registered Section 8 not-for-profit company under the Companies Act, 2013 (India), CIN U88900BR2026NPL086460.

As a Section 8 entity the foundation is legally prohibited from distributing profits — its sole mandate is the long-term public-interest stewardship of AJ Commons.

Verify at mca.gov.in · Enquiries: dpg@ajcommons.org

Licence

Every AJ Commons component is released under the Apache License 2.0 (OSI-approved) — free to use, modify, and deploy in any context with attribution. No component uses a more restrictive licence.

Source: github.com/ajcommons

SDG Alignment

Directly advances SDG 3 — Good Health and Well-Being by providing open digital infrastructure for health data exchange, patient identity, and clinical decision support in low- and middle-income countries.

SDG 3.8 — Universal Health Coverage SDG 3.4 — Non-Communicable Diseases SDG 3.b — Medicines & Vaccines SDG 3.d — Health Security

DPG Compliance

AJ Commons is designed to meet all nine indicators of the DPG Standard v1.1.6. DPGA applications reference this page as the primary ownership and compliance evidence URL.

DPG Indicator

Status

1 — SDG Relevance

✓ Met

2 — Open Licensing (Apache 2.0)

✓ Met

3 — Clear Ownership

✓ Met

4 — Platform Independence

✓ Met

5 — Documentation

✓ Met

6 — Non-PII Data Extraction

✓ Met

7 — Privacy & Applicable Laws

In prep

8 — Open Standards

✓ Met

9 — Do No Harm

✓ Met

DPGA Reviewer Contact

All evidence for DPGA review: dpg@ajcommons.org · Security: security@ajcommons.org

DPG Standard v1.1.6 · digitalpublicgoods.net · Enquiries: dpg@ajcommons.org

Get in touch

We'd like to hear from you

Whether you're deploying in a hospital network, advising a Ministry of Health, or contributing code — reach out through the right channel.

Government & national health programmes

Deploying a national HIE? Evaluating AJ Commons for a Ministry of Health implementation? We support government technical teams directly.

gov@ajcommons.org →

Developers & implementers

Building on AJ Commons, contributing code, or deploying components? Start with the documentation or open a GitHub issue.

Documentation →

DPG, research & partnerships

DPGA reviewers, WHO technical teams, bilateral health funders, or research institutions — contact us about governance and partnership.

dpg@ajcommons.org →

Security vulnerabilities

Responsible disclosure of security issues in any AJ Commons component. We respond within 48 hours and publish CVEs after patching.

security@ajcommons.org →

Code of Conduct reports

Harassment, abuse, or conduct concerns in any AJ Commons space — GitHub, discussions, or events. Confidential. Maintainers respond within 72 hours.

conduct@ajcommons.org →

Open infrastructure for health systems that serve everyone

Built from the gaps a clinician sees every day

Nine independently deployable components

Built on open standards, not proprietary protocols

Open governance, not corporate control

Who stewards AJ Commons

Governance commitments

Open infrastructure for the public interest

We'd like to hear from you

Government & national health programmes

Developers & implementers

DPG, research & partnerships

Security vulnerabilities

Code of Conduct reports