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

Conformance and must supports

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • 0.1.0 [deprecated]
    • FHIR Infrastructure
    • (NA)
    • Hide

      Generally, since the core specifications do not include Must Support, and we are backporting core functionality, we are trying to avoid over-use of the flag.

      After review, adding a Must Support flag to the Subscription.criteria field feels appropriate.

       

      Additionally, we will review the spec to ensure that usage of Must Support is consistent and the implications of it are described.

      Show
      Generally, since the core specifications do not include Must Support, and we are backporting core functionality, we are trying to avoid over-use of the flag. After review, adding a Must Support flag to the Subscription.criteria field feels appropriate.   Additionally, we will review the spec to ensure that usage of Must Support is consistent and the implications of it are described.
    • Bas van den Heuvel / Gino Canessa : 11-0-1
    • Enhancement
    • Compatible, substantive

    Description

      Conformance and must supports: I notice few if any MS on the elements meaning that they are all optional - is that feasible from an implementation perspective?

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            ehaas Eric Haas
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: