AWS Step Functions Callback Pattern

• healthlake-export-manager

  2 3 5.2 Go

  Sample and working repos to demonstrate exporting data from AWS HealthLake to trigger downstream operations

This has been a deep dive into several concepts. The genesis for the article was built upon AWS Step Functions Callback Pattern, but to do that we needed HealthLake's export capabilities and the recently released Distributed Map capability in Step Functions. I've tried to not over-code the article but there is an accompanying repository that is fully working and deployable. Be careful, however, HealthLake can be a bit pricey to run so watch how long you leave the stack up.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• fhir

  9 529 9.7 HTML

  Official source for the HL7 FHIR Specification

  

I skipped over the prepare change function that is at the beginning of the sub-map flow because it's outside of the scope of this article. But when you choose AWS HealthLake you are signing up for a FHIR compliant datastore. FHIR stands for Fast Healthcare Interoperable Resource and it's the go-to and preferred format for exchanging Patient and other Healthcare data between domain boundaries externally. The prepare function breaks the NDJSON up and makes little FHIR payloads to be sent downstream into the ecosystem.

Suggest a related project