Modern target state, legacy ingress
Healthcare modernization on AWS usually starts in the middle of history, not at a clean slate. Orders, ADTs, results, and scheduling traffic still arrive from legacy systems while downstream applications increasingly expect FHIR APIs and domain-specific managed services.
That is why AWS Well-Architected healthcare patterns still show HL7 v2 integration tiers, transformation layers, and event-driven handoff into FHIR-centric systems. The lesson is not that legacy protocols win. The lesson is that migration paths must respect how the source estate actually behaves.
Representative AWS interoperability ingress path
Loading diagram...
The simplified message-flow above explains the migration logic. This official AWS figure then shows what that logic becomes in a concrete FHIR implementation, with identity, storage, search, encryption, and API mediation all made explicit.
AWS interoperability reference architecture
Well-Architected healthcare guidance showing representative HL7 v2 and FHIR integration patterns.
Read the reference architectureFHIR normalization creates a durable contract, not a universal datastore
Once data crosses the transformation boundary, FHIR gives AWS-native applications a standards-based contract for patient, observation, encounter, and many other resources. That helps with APIs, app launches, analytics, and longitudinal patient context.
Transformed clinical bundle example
Simplified FHIR bundle showing how legacy identity and result content becomes durable, linked resources.
Click on an annotation to highlight it in the JSON
Normalization is not modality collapse
FHIR is a powerful exchange and storage contract for clinical resources, but it does not replace imaging or omics-specific operational stores.
What is AWS HealthLake?
Official HealthLake guide covering the managed FHIR R4 service and its application-facing contract.
Review HealthLake capabilitiesA modern patient-data strategy is multimodal by design
AWS Prescriptive Guidance now describes a modern health-data strategy with separate domain products. Clinical records land in HealthLake, medical imaging lands in HealthImaging, and genomics pipelines plus derived stores land in HealthOmics. The shared patient story happens across those domains, not by pretending they are one operational schema.
Multimodal health-data strategy on AWS
Loading diagram...
Modern health-data strategy example
AWS Prescriptive Guidance describing HealthLake, HealthImaging, and HealthOmics as domain-aligned data products.
Read the multimodal strategy guidanceKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.