How to convert HL7v2 to FHIR in AWS

0

Is there a reference implementation / architecture for converting HL7 v2 messages to FHIR json format ? I came across this FHIR works on AWS, https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-fhir-works-on-aws/, but not sure if that would address my needs.

Just to add some details, I found https://github.com/aws-samples/fhir-hl7v2-integration-transform which is part of fhir works which seems to do the hl7 to fhir transformation using some python libraries. But was looking for an AWS equivalent of https://github.com/microsoft/FHIR-Converter

asked 2 years ago1246 views
2 Answers
1

Hello,

Tim here with the Serverless Support Team and came across your question. There is not currently a reference implementation/architecture for converting HL7v2 messages to FHIR json format that I could recommend myself, however it does appear that the link you had shared, https://github.com/aws-samples/fhir-hl7v2-integration-transform , is an excellent starting position. You could raise a GitHub issue on that repository here, https://github.com/aws-samples/fhir-hl7v2-integration-transform/issues, but it looks for implementing it would mainly just be running the CDK and determining how to integrate the two.

As I'm not familiar with the solution I can only advise on an as-is best effort basis myself, but perhaps simply merging the API resources/methods between the two solutions, and keeping the backend for the HL7v2 for a specific endpoint would suffice? I could not say for sure, but I think generally it's going to be specific to your own unique needs, so looking over the solutions and designing your own system referencing these may be good. I have found that launching solutions and scaffolding my own custom engineered solution via adding CloudFormation or CDK code is one of the best strategies since most everyone’s solutions would be custom with their own features and design constraints.

AWS
SUPPORT ENGINEER
Tim_P
answered 2 years ago
  • TIm is correct: you can use FHIR to HL7v2 transform code as a starting point (we tried to show the art of possible). Due to the differences in implementation between different vendors and customers, there is always a need to have somewhat custom mappings of HL7v2 messages to FHIR resources. We have partners that help with such transformations, several of them can be found on the following page: https://aws.amazon.com/healthlake/partners/

0

Thanks for the insights, we have tons of custom mappings that are internal to our product. This seems to be a good place for me to start. We'll reach out if we plan to write a generic framework for transformation in our company. I'm not sure if healthlake partners will help at this point, but will be sure to evaluate for future needs. Though medical comprehend looks interesting, and wonder if I can use that to infer hl7v2 data and build a fhir wrapper on top of it.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions