Why section emptyReason but not nullFlavor on data elements? - 2016-09 ccda #67

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - Question answered
    • Priority: Medium
    • US C-CDA on FHIR (FHIR)
    • DSTU2
    • Structured Documents
    • Composition [deprecated]
    • (profiles) [deprecated]
    • D.4.1.1
    • Hide

      C-CDA on FHIR did not add section.emptyReason. This is a core property of the Composition resource. The emptyReason property is present because Composition.section is modeled after the List resource.

      The absense of nullFlavors in general is a core FHIR issue. Suggest taking this up with FHIR-I.

      Show
      C-CDA on FHIR did not add section.emptyReason. This is a core property of the Composition resource. The emptyReason property is present because Composition.section is modeled after the List resource. The absense of nullFlavors in general is a core FHIR issue. Suggest taking this up with FHIR-I.
    • Sarah Gaunt/Lisa Nelson: 9-0-0
    • Clarification

      Existing Wording: emptyReason

      Comment:

      Why is there a section emptyReason, which is essentially like a nullFlavor, but yet the decision was made to avoid nullFlavors at the data element level? Aside from the difference in the number of instances, they seem to be the same in principle, so the decisions seem inconsistent

      Summary:

      Why section emptyReason but not nullFlavor on data elements?

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: