JamConnect
v0.2 · Spring Boot · Commercial · Port 8091
JamConnect is the clinical intelligence facade. It is the single API that JamBridge calls for consent checks and POST_WRITE events, decoupling the integration pipeline from the details of each registry service.
Consent check
POST /jamconnect/consent/check
{
"patientRef": "Patient/GOLDEN-00441",
"actorRef": "Organization/org-br01-001",
"resourceType": "Patient",
"action": "write",
"purpose": "TREAT"
}
JamConnect calls AJ Consent Manager and returns the decision to JamBridge. Caching: consent decisions are cached for 30 seconds per (patient, actor, resource, action, purpose) tuple.
POST_WRITE event routing
After every successful FHIR write, JamBridge fires a POST_WRITE event. JamConnect evaluates its rule engine — 5 rules per event, running in virtual threads:
| Rule | Trigger | Action |
|---|---|---|
| IPS invalidation | Any write | Invalidate JamSHR IPS cache |
| CDS Hooks dispatch | MedicationRequest write | Send card to clinician portal |
| Critical value alert | OBX-8 = H or L | Alert prescriber + admin |
| Escalation timer | Critical alert unacknowledged 30min | Escalate to branch admin |
| DHIS2 trigger | Notifiable LOINC code | Push to JamDHIW surveillance |
CDS Hooks
JamConnect dispatches CDS Hooks cards when a MedicationRequest or ServiceRequest is written:
POST https://cds-hooks.branch.internal/cds-services/lipid-risk
{
"hook": "order-sign",
"context": {"patientId": "GOLDEN-00441", "draftOrders": {...}}
}
The CDS service returns cards that are displayed in the clinician portal at the point of care.