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

DataAbsentReason -> NullFlavor Map

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US C-CDA on FHIR (FHIR)
    • 1.2.0-ballot
    • Cross-Group Projects
    • STU
    • FHIR Data Absent Reason to C-CDA NullFlavor
    • Hide

      error -> NAV
      Add a comment explaining why UNK <> unk.
      And explicitly "not the R4 map"

      Show
      error -> NAV Add a comment explaining why UNK <> unk. And explicitly "not the R4 map"
    • Jay Lyle/John D'Amore: 18-0-6
    • Clarification
    • Non-substantive

    Description

      I know there's generic recommendation to use FHIR's "unknown" in the absence of otherwise required information, but it feels completely wrong that FHIR's "unknown" would not just directly map to CDA's "UNK" nullFlavor.

       

      Other mappings I'd suggest additional discussion on:

      • unsupported - seems more like "not applicable" than "no information"
      • not-permitted - also seems like "not applicable"
      • error - does not seem like it should map to anything; though perhaps NAV or UNK

      Attachments

        Activity

          People

            Unassigned Unassigned
            benjamin Benjamin Flessner
            Benjamin Flessner
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: