JamReferral v1.0 · Apache 2.0 · Port 8093
Cross-branch referrals.
FHIR ServiceRequest + Task.
JamReferral manages cross-branch referrals with a 5-state FHIR workflow engine — ServiceRequest holds the clinical order, Task tracks the workflow. 48-hour accept timeout. Automatic DECLINED on expiry.
Referral state machine
DECLINED ← (on rejection or timeout)
What JamReferral provides
📋
ServiceRequest + Task
ServiceRequest holds the clinical referral order (specialty, priority, reason). Task tracks the workflow state. Standard FHIR R4 — works with any SMART-enabled EHR.
⏰
48-hour timeout
ACCEPTED state has a 48-hour window. If the receiving facility does not start the appointment, the Task transitions to DECLINED automatically.
🔔
Event-driven notifications
Every state transition fires a notification via JamConnect POST_WRITE — referral accepted, declined, or completed. Drives EHR task panels and SMS alerts.
🏥
Cross-branch routing
JamFR resolves the sending and receiving facility from HL7v2 MSH-4. JamMPI resolves the patient golden ID. No manual facility configuration.
📊
Referral analytics
All referral TaskHistory resources queryable via FHIR search. Average accept time, decline rates, specialty volumes — available in JamDHIW dashboards.
🔐
Consent-enforced
AJ Consent Manager checks the patient's consent before creating or updating a referral. DENY = ServiceRequest blocked before creation.
Referrals that close the loop.
From ServiceRequest to COMPLETED — across every branch in your network.