Uploaded image for project: 'CDA Specification Feedback'
  1. CDA Specification Feedback
  2. CDA-20891

Should this design narrow the relevant data absent reasons allowed?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • C-CDA Templates Clinical Notes (CDA)
    • 3.0.0-ballot
    • Structured Documents
    • STU
    • Care Experience Preference
    • Hide

      We are restricted to using the NullFlavor codes that are specified by the version of RIM and v3 Vocabulary that CDA uses.  We are unable to change those at this time.

      Show
      We are restricted to using the NullFlavor codes that are specified by the version of RIM and v3 Vocabulary that CDA uses.  We are unable to change those at this time.
    • Jean Duteau / Brett Marquard: 16-0-1

    Description

      Should this design narrow the relevant data absent reasons allowed?

      What would be the best way to align these designs?

      When shaping the code in an observation, it seems to make more sense to keep the nullFlavor attribute as an allowed structure, but constrain it to use the same Data Absent Reason VS and used in the DataAbsentReason element of the FHIR profile.

      Seems like we could make a better alignment choice here, and then create a design principle which could be applied elsewhere.

      Attachments

        Activity

          People

            Unassigned Unassigned
            LisaRNelson Lisa R. Nelson
            Lisa R. Nelson
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: