clarify must support rules1

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • (many)
    • 2.1
    • Hide

      We are not aware of a mustsupport extension - assume you mean the mustSupport flag - any profiled resources by FHIR definitions support the mustSupport flag - including bundle.type - the support for the flag is at the element level, not at the datatype level - bundle.type is 1..1 and fixed to "message" - but flagging it as must support does not hurt it, but draws more attention to it. With using mustsupport we are definitive in what you will get.

      Show
      We are not aware of a mustsupport extension - assume you mean the mustSupport flag - any profiled resources by FHIR definitions support the mustSupport flag - including bundle.type - the support for the flag is at the element level, not at the datatype level - bundle.type is 1..1 and fixed to "message" - but flagging it as must support does not hurt it, but draws more attention to it. With using mustsupport we are definitive in what you will get.
    • Eric Haas/Riki Merrick: 5-0-0

      This reads as if all data elements SHALL be treated as required. In some situations, the data type may not support the mustsupport extension. For example, Bundle.type.

      Existing Wording:

      Must Support on any data element SHALL be interpreted as follows:

      As part of the notification message or a query result as specified by the [Da Vinci Notifications CapabilityStatements], the Sender SHALL be capable of including the data elements defined in the Da Vinci Notification profiles that have a MustSupport flag.

            Assignee:
            Unassigned
            Reporter:
            Emma Jones
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: