Product + Architecture Narrative
Race Track FHIR Pipeline: One Journey, Three Views
Patients "drive" through one canonical workflow while their data moves through FHIR, Kafka, services, and Redis. Switch tabs to compare non-technical, mixed, and technical explanations without changing the underlying flow.
Built from real-world HIE operating patterns (Healthix, HealthInfoNet) and modern identity strategy (Verato) to remove custom-interface bottlenecks and activate FHIR-native, event-driven workflows.
Canonical Journey (Same Across All Tabs)
1
Patient Event Created
2
Data Ingested
3
Kafka Stream Routed
4
Service Processing
5
Redis Context Lookup
6
Care Rule Evaluation (1 Patient → N Measures)
7
Action Generated
8
Consumer Delivery
9
Outcome + Audit
Track laneData laneKafka laneRedis laneOutcome lane
Story-First View (Fully Illustrative)
Track Lane
Race Start
Patient event created in customer systems
Pit Stop A
Customer FHIR + CDR provide source data
Pit Stop B
Standards-based processing routes events
Pit Stop C
Care decision checkpoint applies context
Finish
Action delivered and outcome tracked
Audience Language
FHIR standards integration
Plug in to existing customer systems
Events move in real time
No custom one-off interfaces
Clinical context applied
Data is interpreted before action
Standard actions back
Care teams get tasks and guidance
Key takeaway: Patients follow one continuous workflow. Data moves with them end-to-end, so onboarding does not require custom interfaces.
Explore More
See the validation evidence or return to resources.