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

Better handling of dataAbsentReason

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest

    Description

      component.value[x] is 1..1. This suggests that a value for a component is always required. If so, suggest constraining dataAbsentReason 0..0. However, I think a better approach would be to allow (require?) either a value or dataAbsentReason.

      (Comment 38 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            minigrrl Sarah Gaunt
            esilver Elliot Silver
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: