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

CommunicationNotDone code requires change in cardinality and modeling

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US QI Core (FHIR)
    • 2.0 [deprecated]
    • Clinical Quality Information
    • QICore Communication
    • D.4.1 StructureDefinition-qicore-communicationnotdone
    • Hide

      Create an invariant with at least one code or a value set reference:
      CommunicationNotDone.code cardinality 1..1
      CommunicationNotDone.code.coding cardinality 1..1
      Invariant - ((coding.code and coding.system) xor valueset-reference extension)
      In these cases can only have 1 code (1..1)
      We would like coding to be 1..* but that means the NotDone value set is ambiguous, so will submit a base FHIR Tracker to expand the context of use for the value set reference extension to support use on the Codeable Concept

      Show
      Create an invariant with at least one code or a value set reference: CommunicationNotDone.code cardinality 1..1 CommunicationNotDone.code.coding cardinality 1..1 Invariant - ((coding.code and coding.system) xor valueset-reference extension) In these cases can only have 1 code (1..1) We would like coding to be 1..* but that means the NotDone value set is ambiguous, so will submit a base FHIR Tracker to expand the context of use for the value set reference extension to support use on the Codeable Concept
    • Anne Smith/Linda Michaelsen:18-0-0
    • Enhancement
    • Non-compatible

    Description

      The current modeling for many QI-Core NotDone profile code elements is confusing to implementers and considered potentially ambiguous. Other NotDone profile specify code cardinality of 0..1 but then require a cardinality of 1..1 for referencing the notDoneValueSet. Communication, however, does not require indication that a single concept was done or not done, or that none of a group of items was not done. It only requires that the Communication modifierExtension:notDone is true and that a Communication.statusReason is valued with a concept with extensible binding to the NegationReason value set.
      Please confirm that no change is required.

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            feisenberg Floyd Eisenberg
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: