Healthcare Interoperability Stack on AWS
Publication date: January 31, 2023 (Diagram history)
With this architecture, you can build a modular interoperability platform to ingest, parse, and store healthcare data of any shape, size, and format. The solution uses connectors with syntactic and semantic parsers to convert and standardize both standard and non-standard data into Health Level Seven Fast Healthcare Interoperability Resources (HL7 FHIR) format.
Healthcare interoperability stack diagram
The following steps describe the data flow and processing pipeline for this architecture:
-
Establish on-premises connectivity for data ingestion. Use a private channel such as AWS Site-to-Site VPN, AWS Direct Connect, or HTTPS connectivity.
-
Use different connectors depending on the incoming message type. For public-facing Amazon API Gateway instances, configure AWS WAF as a web application firewall. Use AWS Transfer Family, AWS Database Migration Service, or Elastic Load Balancing depending on your data source.
-
Use Amazon EventBridge to handle data processing pipeline orchestration. Store intermediate data in Amazon Simple Storage Service. Use Amazon Textract to extract text from files where required, such as PDFs.
-
Use a data classifier to determine the incoming message type and route information to the appropriate parser by using event rules.
-
Use a set of configurable templates in the syntactic parser to transform incoming data formats into HL7 FHIR if required.
-
Use the semantic parser to standardize data values into common ontologies.
-
Use the distribution module to fan out converted messages to appropriate destinations by using Amazon Simple Queue Service and Amazon Simple Notification Service.
-
Bring your own identity solutions to normalize resources such as patients and providers.
-
Use Amazon HealthLake as a durable storage destination for messages transformed into HL7 FHIR. Use Amazon S3 to store other resources.
-
Benefit from standardized data to gain insights and to improve care.
Further reading
For additional information, see the following resources:
Diagram history
To receive updates about this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Initial publication | Reference architecture diagram first published. | January 31, 2023 |
RSS subscription requirement
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.
