How do we use HealthAPIX proxies if th backend EMR is not FHIR compliant?

How do we use HealthAPIX proxies if th backend EMR is not FHIR compliant?

Solved Solved
1 4 255
1 ACCEPTED SOLUTION

The HealthAPIx proxies are meant to bridge that gap. By configuring these proxies, you can integrate with your legacy (non-FHIR) EMR systems. The logic of mapping services & data will go as part of these proxy implementation itself.

View solution in original post

4 REPLIES 4

The HealthAPIx proxies are meant to bridge that gap. By configuring these proxies, you can integrate with your legacy (non-FHIR) EMR systems. The logic of mapping services & data will go as part of these proxy implementation itself.

Sudhee, is this done via the FHIR adapters I have heard about?

Thanks @sudheendra1 and @Dino . Guess I will have to use the XSLT Transform policy for this mapping. And all this logic goes in fhir-connector-hapi-dstu2 proxy in the reference implementation. Let us know if there are any better/alternative approaches, please.

Just wondering, do we have any Apigee reference implementation for the EMR which is not FHIR Compliant.