Skip to main content
JamConnect v0.2 · Commercial · Port 8091

Clinical intelligence.
One API for the whole platform.

JamConnect is the clinical intelligence facade. JamBridge calls one endpoint. JamConnect coordinates identity resolution, consent enforcement, facility lookup, CDS Hooks, and POST_WRITE event routing — in sequence, without tight coupling.

JAMBRIDGE → JAMCONNECT → PLATFORMJamBridgeJamConnect:8091AJ MPI — $matchAJ Consent — checkJamFR — facilityCDS Hooks — fireJamSHR — invalidate

What JamConnect coordinates

🔍
Identity resolution
Calls AJ MPI $match on every message. Returns the golden patient ID before consent checks or FHIR writes.
⚖️
Consent enforcement
Checks AJ Consent Manager before every FHIR write. Returns PERMIT or DENY with the matching provision clause.
🏥
Facility lookup
Resolves HL7v2 MSH-4 facility codes against AJ FR. Returns the FHIR Organization reference for the sending facility.
🔔
CDS Hooks dispatch
Fires CDS Hooks after each POST_WRITE — medication-prescribe, order-review. Returns cards to JamBridge for prescriber alerting.
♻️
Cache invalidation
Sends POST_WRITE events to JamSHR after every successful write. JamSHR invalidates the IPS cache for the golden patient.
🔌
Decoupling
JamBridge calls one JamConnect endpoint. No direct dependencies on AJ MPI, AJ Consent, JamFR, or JamSHR. Platform changes without pipeline changes.

One call. Seven services. Zero coupling.

JamConnect is how JamBridge stays simple while the platform grows.

Read the docs →Book a call