Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement Request - Handle US Core STU5+ OMB Race Category value (2131-1) #784

Open
AGABB opened this issue Aug 21, 2024 · 3 comments
Open

Comments

@AGABB
Copy link

AGABB commented Aug 21, 2024

Situation
FHIR Version 4 is the version of FHIR that is compatible with the App. When it comes to the raceCode element, the app looks for the omb-race-category url extension and pulls the associated race code into the eICR. In both eICR 1.1 and 3.1, there are five allowed values that do not include 2131-1 (other race). This aligns with the omb-race-category value set in FHIR version 4, so everything works great.
image

In FHIR STU5 and up, the 2131-1 code is included as a valid value in the valueSet:
image
For any vendors who have advanced their FHIR server to this version, a situation is now possible where their server can emit a valid value per the FHIR Spec, but result in an invalid value being included in the eICR.

This will cause Schematron errors in the DQ Monitoring Report that is used for data quality validation by the onboarding team and PHAs.

Approach
One solution, of course, is for the FHIR Server to revert back to the version 4 valueSet and not allow 2131-1. This does however feel like potentially a step in the wrong direction. FHIR R6 will eventually be required and this would have to be switched back.

Another solution is to handle this in the app code - the app could, for instance, add a check in CdaHeaderGenerator.java such as:

    if (race != null && race.hasCode()) {
		if (race.getCode().equals(OTHER_RACE_code)) {
			patientDetails.append(
            CdaGeneratorUtils.getXmlForNullCD(
                CdaGeneratorConstants.RACE_CODE_EL_NAME, race.getCode()));
        else if (!isCodingNullFlavor(race)) {
        patientDetails.append(
            CdaGeneratorUtils.getXmlForCD(
                CdaGeneratorConstants.RACE_CODE_EL_NAME,
                race.getCode(),
                CdaGeneratorConstants.RACE_CODE_SYSTEM,
                CdaGeneratorConstants.RACE_CODE_SYSTEM_NAME,
                race.getDisplay()));

Submitting this request for eCR Now Team's input and review on behalf of McKesson Ontada

@nbashyam
Copy link
Collaborator

Make modification to allow OTHER Value as a mapping element to nullFLAVOR=OTH as shown below.

. Other

@nbashyam
Copy link
Collaborator

   <originalText>..
</raceCode> ```

@mmatiasalt
Copy link

@nbashyam as per Sarah, as per Chuck- they do sometimes get that code (2131-1 Other Race), so I think that the code change that you suggested would be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants