Both bridged race and ethnicity required by the coded race profile

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Birth and Fetal Death Reporting (FHIR)
    • 0.1.0 [deprecated]
    • Public Health
    • Composition - Coded Race and Ethnicity
    • Hide
      • Provider Compositions: the edit specification for both Race and Ethnicity states that if there is no response, type or print "Unknown" - update both Provider Compositions to with guidance on how to use the data-absent-reason extension when data is unknown
      • Coded Race and Ethnicity Composition
        • Update title of Composition from "Composition - Coded Race" to "Composition - Coded Race and Ethnicity" (there was a typo)
        • Rename "Bridged Race" to "Race" as this term is being retired.
        • Point to single race value set in PhinVads instead of bridged race value set
        • Keep 1..1 cardinality on slices mentioned in comment
        • update with guidance on how to use the data-absent reason extension when the data is unknown

      See also FHIR-30921

      Show
      Provider Compositions: the edit specification for both Race and Ethnicity states that if there is no response, type or print "Unknown" - update both Provider Compositions to with guidance on how to use the data-absent-reason extension when data is unknown Coded Race and Ethnicity Composition Update title of Composition from "Composition - Coded Race" to "Composition - Coded Race and Ethnicity" (there was a typo) Rename "Bridged Race" to "Race" as this term is being retired. Point to single race value set in PhinVads instead of bridged race value set Keep 1..1 cardinality on slices mentioned in comment update with guidance on how to use the data-absent reason extension when the data is unknown See also FHIR-30921
    • Sarah Gaunt / Cindy Bush : 25-0-0
    • Correction
    • Non-substantive

      It looks like the coded race and ethnicity profile requires that both the bridged race and tabulated ethnicity are required (their slices are 1..1) but what happens if the jurisdiction reports to NCHS don't contain data on either race or ethnicity (or on neither)? Neither value set seems to have an options for "unknown" (although data absent reason presumably could be used). Is 1..1 the best cardinality for these slices? If so, should section.entry have a cardinality of 2..* or 2..2?

            Assignee:
            Sarah Gaunt
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: