Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-34694

Validation of race and ethnicity Observation components

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US SDOH Clinical Care (FHIR)
    • 1.1.0
    • Patient Care
    • SDOHCC Observation Ethnicity OMB
      SDOHCC Observation Race OMB
    • Draft Specifications for Personal Characteristics
    • Hide

      The same LOINC code is used for all three components in this draft profile.  If the profile is adopted as part of the US Core standard, new LOINC codes (possibly a panel) will be needed to represent the components (e.g., a new LOINC code for detailed race and for text description of race).

      Show
      The same LOINC code is used for all three components in this draft profile.  If the profile is adopted as part of the US Core standard, new LOINC codes (possibly a panel) will be needed to represent the components (e.g., a new LOINC code for detailed race and for text description of race).
    • Bob Dieterle / Laura Heerman-Langford : 7-1-0
    • Clarification
    • Non-substantive

    Description

      It seems odd that all of the slices on Observation.component for the race and ethnicity profiles use the same LOINC code for each of the 3 slices. Is this expected to problematic in terms of validating the data for a system using the resource? While the value sets for the rolled up OMB codes and the detailed codes are mutually exclusive, it seems like the using system will need to validation each coded component against both value sets to determine that the value is valid. Is it not possible to have unique LOINC codes for each concept? If unique codes are not possible, narrative on the Draft Specification for Race and Ethnicity page on the implications of using the same code for all components may be helpful to implementers.

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: