Clarify how the 'qualification' [0..*] array with unbound/required terminology is supposed to work. - HRex #104

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • Financial Mgmt
    • Profile overview [deprecated]
    • Differential View
    • Hide

      This has already been removed in the STU3.1 release of US-Core (i.e. the release based on FHIR R4).

      Show
      This has already been removed in the STU3.1 release of US-Core (i.e. the release based on FHIR R4).
    • Richard Esmond / Marti Velezis : 9-0-0

      Existing Wording: qualification S 0..* BackboneElement Binding: (unbound) (required)

      Proposed Wording: qualification S 0..* BackboneElement Binding: (ValueSet TBD) (required)

      The qualification[] vocabulary binding both both unbound (i.e. no terminolgoy binding) and 'required; binding strength - this seems to be a contradiction. This is to no terminology constraint. It's unclear how this data element is interoperable if the implementers are required to use an unabound/no-binding CodeableConcept.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Ioana Singureanu
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: