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

If code element carries a nullFlavor, then the value element should not be present.

    XMLWordPrintableJSON

Details

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

    • Change Request CDA-20943 Add 0..0 @nullFlavor for @code bindings

    Description

      If code element carries a nullFlavor, should the value element not be present? Seems like there needs to some smarts built into the validator to address this situation where you permit data to be absent for a reason, but also require that information to be coded and included when the data is not absent. 

       

      Is there something we can do with constraint language or which the way the FHIR Validator works to make this "commonsense" situation supported without having to add a bunch of work-around constraints?  Or do we just need to add some additional constraints?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated: