Managed Health Information Exchange

Your national HIE.
Zero servers.
Live in weeks.

Connect your hospitals to MLLP endpoints we host. Patient identity, shared records, consent enforcement, and analytics — all running on infrastructure we operate under a 99.9% SLA. No servers to deploy. No FHIR expertise required at the facility.

Talk to us See how it works
Built on FHIR R4/R5 Apache 2.0 core IHE ATNA SMART v2.2 HAPI FHIR 7
cloud.akhester.com — Control Plane
All systems operational
Connected
14
hospitals active
Uptime (30d)
99.97%
SLA: 99.9%
Msg today
48,291
HL7v2 processed
MPI records
2.4M
golden identities
Live event feed
ADT^A01 — KNH001 — Patient enrolled 0.3s ago
ORU^R01 — MGH003 — Lab result written 1.1s ago
MPI match — golden_id:GLD-29481 resolved 1.4s ago
DHIS2 sync — 1,204 indicators pushed 3m ago
IHE ATNA audit: 1.2M events today ↑ 99.97% uptime
10+
Jam products included
7
HL7v2 message types
0
Servers to deploy
99.9%
Uptime SLA
How it works

From legacy HIS to live HIE
in three steps

Your hospitals keep their existing systems. You make one network routing change. We run everything else.

01
Point your HL7v2 feed at our endpoint
We provision a dedicated MLLP endpoint for each facility. Your HIS team adds a routing destination — no middleware, no FHIR expertise required at the facility. We receive ADT, ORU, ORM, OML, MDM, RDE, and SIU messages immediately. Facilities with native FHIR can POST directly to our JamConnect API instead.
HL7v2 MLLPFHIR R4 directTLS 1.3
02
Patient identity resolves. Records flow.
JamBridge translates every message to FHIR R4/R5. AJ MPI resolves patient identity across all facilities — the same patient at five hospitals becomes one golden record. JamConnect enforces consent before any data is written or read. Every action generates a FHIR AuditEvent. No code written by your team.
Golden recordsIHE PDQm/PIXmConsent enforced
03
The full platform activates
Clinicians pull IPS summaries across facilities via JamSHR. Patients access records via JamPHR. JamDHIW exports to DHIS2 and generates PEPFAR MER indicators nightly. JamGuard monitors cross-facility drug safety. All on infrastructure we operate — patched, scaled, and monitored around the clock.
IPS summariesDHIS2 nightly24/7 ops
What's included

Every Jam product.
One subscription.

No per-module pricing. Every connected facility gets the full stack — integration, identity, shared records, analytics, and terminology. All included in the annual per-facility fee.

No lock-in
The identity, consent, auth, and registry components are Apache 2.0 open source on GitHub. If you ever need to self-host, we provide a full FHIR bulk export in standard NDJSON. Your data is portable by design — this is a contractual commitment.
Integration & Coordination2 products
JamBridgeIncluded

HL7v2-to-FHIR engine. Receives MLLP feeds on 7 message types, enriches with MPI-resolved patient identity, writes to HAPI FHIR R4/R5. IHE ATNA audit on every message. Replaces OpenHIM and proprietary integration engines.

ADT·ORU·ORM·OML·MDM·RDE·SIUIHE ATNA
JamConnectIncluded

Clinical coordination API. Every read and write in the HIE passes through JamConnect — identity resolution, consent enforcement, facility lookup, CDS Hooks dispatch, and cross-facility event routing.

Consent enforcementCDS HooksEvent routing
Identity & Registry — Apache 2.03 components
AJ MPIApache 2.0

Master Patient Index. Probabilistic matching with golden record management across all facilities. IHE PDQm, PIXm, and PMIR. Every HL7v2 message enriched with a golden patient ID before the FHIR write.

IHE PDQm/PIXmProbabilistic match
AJ FRApache 2.0

Facility Registry. mCSD-conformant ITI-90 hospital and clinic directory. Auto-provisioned from HL7v2 MSH-4 — a new facility connecting via JamBridge registers automatically. No manual directory maintenance.

IHE mCSDITI-90
AJ FHIR Auth ServerApache 2.0

SMART App Launch v2.2. PKCE S256, RS256 id_token, IdP federation to Azure AD, Okta, or any OIDC provider. Clinicians use hospital credentials — no new identity store required.

SMART v2.2PKCE S256IdP federation
Clinical Data & Patient Access3 products
JamSHRIncluded

Shared Health Record. IPS patient summaries across all connected facilities — medications, allergies, conditions, immunisations, results. IHE MHD (ITI-65/66/67/68). FHIR $summary operation.

IPSIHE MHD$summary
JamPHRIncluded

Patient-facing health record portal. Full IPS view of the cross-facility record. SMART on FHIR launch. Patients grant and revoke consent. VDS-NC vaccination certificates with QR codes.

Patient portalConsent UIVDS-NC
AJ FHIR Consent ManagerApache 2.0

FHIR R4/R5 Consent lifecycle. Deny-by-default — no data moves without a valid consent resource. JamConnect checks it on every call. GDPR, HIPAA, and DISHA/ABDM aligned. Full patient audit trail.

Deny-by-defaultGDPR/HIPAA
Analytics & Terminology2 products
JamDHIWIncluded

Analytics warehouse. FHIR bulk export, DHIS2 dataValueSet sync, PEPFAR MER indicators (TX_CURR, TX_NEW, HTS_TST, HTS_POS), and population health dashboards. Nightly ETL or manual trigger. HMIS CSV fallback.

DHIS2 v2.36+PEPFAR MERFHIR bulk
JamTSIncluded

Terminology Service. LOINC, SNOMED CT, and ICD-10 translation. Local code system mappings for country-specific lab codes. Snowstorm federation for full SNOMED CT. Cross-facility analytics requires normalised codes — JamTS handles it automatically.

LOINC/SNOMEDICD-10Snowstorm
Rolling out 2025–2026
JamGuard — cross-facility drug safety
JamCare — chronic care management
JamLM — FHIR-powered LLM summaries
JamEMR — managed EMR for JamCloud facilities
Solutions

Built for three buyer profiles

JamCloud is the right choice when the clinical need is real but operating FHIR infrastructure is not your core competency.

🏛️
Government
Ministry of Health or national HIE programme
You are mandating FHIR interoperability across public hospitals. You need a national HIE that connects to existing HIS systems without a technology upgrade at each facility — and without deploying infrastructure everywhere.
National-scale patient identity across hundreds of facilities
DHIS2 national reporting already in use
In-country data residency required
Government procurement — BAA, DPA, audit reports needed
🏥
Healthcare group
Private hospital network (5–50 facilities)
You run multiple hospitals, each with its own HIS. Clinicians cannot see the patient's record from another facility. You want shared health records, unified identity, and group-wide analytics — without a large IT project.
No DevOps capacity — want someone else to run it
Mix of HIS vendors — all send HL7v2
Insurance revenue cycle across facilities
Clinicians need patient history before the patient arrives
🌍
Development partner
NGO, PEPFAR implementer, or global health programme
You implement health IT across multiple countries and need a predictable, compliant HIE substrate — with PEPFAR DATIM reporting, WHO EPI, and DHIS2 — that you do not have to build and operate yourself.
PEPFAR MER indicators (TX_CURR, TX_NEW, HTS_TST, HTS_POS)
DHIS2 integration mandatory for ministry sign-off
HIV/ART programme tracking across facilities
Multi-country, consistent platform
Division of work

Your team does three things.
We do everything else.

Your side
Your HIS and clinical workflow
  • Configure your HIS to send HL7v2 to the MLLP endpoint we provision — one network routing change per facility
  • Manage clinical users and roles in your existing HIS
  • Configure DHIS2 data element UIDs for your national indicators
  • Patient consent capture in your facility registration workflow
Akhester's side
The entire HIE infrastructure
  • Host and operate JamBridge, JamConnect, AJ MPI, AJ FR, JamSHR, JamPHR, JamDHIW, JamTS, and all AJ FHIR OSS components
  • HAPI FHIR server, PostgreSQL, and all cloud infrastructure — zero servers on your side
  • Security patches deployed within 24 hours on Enterprise and National tiers
  • IHE ATNA immutable audit trail — FHIR AuditEvent log for every action
  • HIPAA BAA and GDPR DPA for regulated deployments
  • Data residency — in-country hosting in India, UK, or US on request
  • Backup, disaster recovery, and 99.9% uptime SLA with monthly reporting
Compliance & standards

Built for regulated environments

Every compliance property of the self-hosted Jam Platform carries directly into the managed service.

SMART App Launch v2.2LIVE

ONC HTI-1 mandated. PKCE S256, RS256 JWT. EHR + standalone launch. Epic and Cerner tested.

FHIR R4 / R5LIVE

All major EHR vendors. HAPI FHIR 7.4 upstream tracked. No proprietary schema at any layer.

IHE ATNALIVE

Non-repudiation audit on every JamBridge message and JamConnect call. FHIR AuditEvent + PostgreSQL.

IHE MHDLIVE

Mobile Access to Health Documents via JamSHR. ITI-65/66/67/68 — submit, find, retrieve documents.

IHE PDQm / PIXmLIVE

Patient identity cross-referencing and demographics query. IHE PMIR. Powered by AJ MPI.

IHE mCSDLIVE

Mobile Care Services Discovery. ITI-90 facility lookup. Powered by AJ FR, auto-provisioned.

HIPAA BAAAVAILABLE

Business Associate Agreement for all JamCloud contracts. Standard template ready on request.

GDPR / EHDSAVAILABLE

Data Processing Agreement available. Consent lifecycle, right to erasure, DPA documentation.

DISHA / ABDMSUPPORTED

Indian Digital Health Mission via AJ FHIR Consent Manager. Consent artefact and health ID aligned.

TEFCASUPPORTED

Consent enforcement and ATNA audit structured for QHIN-adjacent US health network deployments.

Open source means compliance is verifiable, not just claimed
Every consent enforcement decision and patient identity algorithm runs on Apache 2.0 open source code on GitHub. Read the code, run the tests, verify the behaviour — independently of what we tell you. There are no black-box compliance claims in JamCloud.
Pricing

Per-facility annual subscription

Every Jam product included. Price scales with connected facilities, not features. Volume discounts for national deployments of 10 or more facilities. All tiers are annual contracts.

What determines the price
Connected facilitiesPrimary unit
Message volumeTiered above threshold
Data residency regionIncluded / optional upgrade
Support tierStandard / Priority / 24×7
JamCare (when live)Per-patient add-on
Hospital network
Starter
2–9 connected facilities
  • ✓All Jam products included
  • ✓HL7v2 MLLP per facility
  • ✓Shared HAPI FHIR instance
  • ✓Standard support — 2-day SLA
  • ✓HIPAA BAA available
  • ✓Shared hosting (India region)
Get a quote →
MOST COMMON
Network / Government programme
Scale
10–49 facilities · volume discount
  • ✓All Jam products included
  • ✓Dedicated HAPI FHIR instance
  • ✓Priority support — 4-hour SLA
  • ✓HIPAA BAA + GDPR DPA
  • ✓Data residency choice (IN/UK/US)
  • ✓DHIS2 + PEPFAR MER configured
  • ✓Technical onboarding included
Get a quote →
National programme
National
50+ facilities · government pricing
  • ✓Everything in Scale
  • ✓Dedicated per-country infrastructure
  • ✓24/7 support — custom SLA
  • ✓In-country hosting mandatory option
  • ✓Procurement documentation
  • ✓National IT team training
Get a quote →

Contact us with your facility count and HIS vendor list — we quote within 48 hours.

FAQ

Questions from evaluators

We already have a FHIR server. Do we still need JamBridge? ↓
No. If your HIS speaks FHIR R4, you can POST resources directly to JamConnect's FHIR endpoint — JamBridge handles HL7v2 MLLP feeds only. Both connection types coexist in a single deployment. Facilities migrating from HL7v2 over time can switch without any HIE reconfiguration.
Where does our patient data live? ↓
Default region is India (AWS ap-south-1). In-country hosting in the UK (eu-west-2) and US (us-east-1) is standard on Scale and National tiers. Government customers requiring data within their country's borders can request a dedicated in-country deployment. We provide written Data Residency Confirmation as part of the contract.
What happens to our data if we exit JamCloud? ↓
Because JamCloud runs on standard HAPI FHIR JPA storage, your data is fully portable. We provide a complete FHIR bulk export in standard NDJSON at any point during or at the end of the contract. Load it into any HAPI FHIR server you operate. No proprietary schema, no migration work, no lock-in — this is a contractual commitment.
How long does onboarding take? ↓
Single-facility pilot: 1–2 weeks. We provision the MLLP endpoint on day one; your HIS team makes the routing change. National deployments across 50+ facilities typically take 8–16 weeks — mostly driven by the pace of HIS reconfiguration at each site, not by the JamCloud setup.
Our hospitals use different HIS vendors. Does that work? ↓
Yes. JamBridge connects to any system that sends HL7v2 over MLLP — it is vendor-agnostic. Epic and Cerner can also connect via SMART on FHIR through the AJ FHIR Auth Server. AJ MPI resolves identity across all facilities regardless of connection method. A mixed-vendor deployment is the normal case, not an edge case.
Is the platform really open source? ↓
The core components — AJ FHIR Auth Server, Consent Manager, SMART Client, HAPI Plugin, AJ MPI, and AJ FR — are Apache 2.0 open source on GitHub (vedpr625 account). Read every line of the consent enforcement code and patient matching algorithm. The Jam commercial products are built on top of this open stack. JamCloud runs the complete platform.
Do you support DHIS2 national HMIS reporting? ↓
Yes — JamDHIW is included in every tier. It runs a nightly ETL aggregating FHIR resources into indicator values — OPD, malaria (ICD-10 B50–B54), TB (A15–A19), EPI vaccine doses, and PEPFAR HIV indicators — and POSTs a dataValueSet to your DHIS2 instance. Supply your facility UID and indicator UIDs once. HMIS CSV fallback available.
Can one facility see another facility's raw data? ↓
No. Facility-level data isolation is enforced at the JamConnect API layer. A clinician at Facility A can query a shared patient summary via JamSHR only if a valid consent resource exists for that access. Raw clinical data from another facility is never accessible without explicit consent. Every cross-facility access attempt is logged as a FHIR AuditEvent.
Get started

Start with a scoping call.
Quote in 48 hours.

Tell us your facility count, your HIS vendors, and your compliance requirements. We come back with a concrete architecture and a price.

Email support@akhester.com See the Jam Platform →
Or reach us at support@akhester.com