--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hapi-fhir/9fa3440d-53d0-4e9c-a4e2-a0699e3f9f6bn%40googlegroups.com.
Hi Azhar,
Below illustrates how we successfully migrated a large set of HAPI-FHIR JPA DSTU2 resource to R4 format for a client of ours.
Regarding FHIR DSTU2 to R4 structure conversion, we leveraged NextGen’s Mirth Connect integration engine as a platform to execute a blend of JSON text inspection / modification and Java based HL7 FHIR model-to-model version convertors. See: https://hapifhir.io/hapi-fhir/docs/model/converter.html. Inside the Mirth Connect engine, we constructed a set of FHIR DSTU2 to R4 resource specific conversion channels as illustrated below. These channels worked together to create an DSTU2 to R4 workflow.
Other technologies than Mirth Connect could have been used to encapsulate the resource convertors created. The main benefits of Mirth Connect is that it has an internal data bus.. this feature gave the operation staff eye-ball visibility into conversion detail for each and every FHIR resource… along with ability to interactively fix and/or replay any failures.
Hope the above helps your efforts.
Chuck
--
--