USCDI v5 to FHIR R4B Mapping in OpenMRS – Approaches for Extensions and Interoperability

Hi,

We are exploring how to map USCDI v5 data elements to FHIR R4B resources using OpenMRS. The goal is to enable seamless interoperability where OpenMRS systems can expose US Core-compliant FHIR resources.

Here’s what we’ve done so far:

In the context of mapping OpenMRS data to FHIR R4 resources, We’re exploring approaches for handling fields that are not natively supported in the OpenMRS core data model (e.g., Race, Ethnicity). Since these elements exist in US Core FHIR as extensions (like us-core-race, us-core-ethnicity), what are the recommended strategies for exposing them via the FHIR2 module?

We’d like to hear from others who may have:

Worked on extending FHIR resources with OpenMRS data Tackled mappings of custom attributes (e.g., Race, Ethnicity) to standardized FHIR extensions General recommendations for building reusable mappings for different implementations

Any insights, examples, or pointers to existing discussions/codebases would be incredibly helpful.

Thank you!

1 Like