05 · HealthTech · Interoperability · Library
Nexus
Hospital interoperability work: HL7 v2 to FHIR R4 backbone, described on the prior personal site as a multi-channel integration programme.
- Role
- Architecture & programme
- Domain
- HealthTech
- ROLE · Architecture & programme
- EVIDENCE · Prior personal site
- SCALE · Hospital integration estate
Scroll down ↓HealthTech
01 · Problem
Legacy HL7 v2 estates do not speak FHIR without a governed translation layer.
02 · Approach
Integration-engine channels across HL7 families, with FHIR as the modern contract. Specific budget and audit figures from the prior site are not restated as independently verified outcomes.
03 · System
HL7 v2 families → FHIR R4 resources; clinical NLP as an optional de-identification path.
04 · Outcome
Documented as a completed interoperability programme on the prior personal site. Treat quantitative claims there as self-reported until independently evidenced.