SCRIMED CODE pt. 4
Patient Context Gateway
SCRIMED Patient Context Gateway uses no-PHI demo data only. It models patient story continuity, provenance, consent, HIE/FHIR abstractions, and complex-care review without EHR writeback, live patient data, diagnosis, treatment, prescribing, or patient outreach.
Synthetic Scenario
synthetic-elderly-complex-care-continuity-001
Elderly complex-care continuity scenario with medication reconciliation, referral follow-up, transportation barrier, and caregiver handoff metadata.
Longitudinal synthetic story made of encounters, medications, social factors, care gaps, referrals, and reviewer notes.
Audit hash: scrimed-intel-11e6d4d1
Controls
Context assembly stays consent-aware, provenance-required, and FHIR-ready.
required
no PHI demo data only
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
patient story continuity model
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
source provenance required
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
HIE interoperability concept
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
FHIR-ready abstraction
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
consent-required flag
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
elderly/complex-care continuity scenario
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan
required
no EHR writeback
Protected patient-context capability remains synthetic until external approvals and live-data controls exist.
FHIR abstraction
Patient, Encounter, Condition, MedicationStatement, Observation, CarePlan