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

Should conformance require Subscription write?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • 1.2.0-ballot
    • FHIR Infrastructure
    • STU
    • Conformance
    • Hide

      Propose defining two sets of subscriptions, "client-managed" and "server-managed" to differentiate between the types of uses.

      • Initial descriptions should live on the Topic-Based Subscription Components page.
      • Workflow page should be updated to show the two different patterns.
      • Handling errors page should be updated to describe "manual" resolution in server-managed (i.e., call the facility contact).
      • Create additional CapabilityStatement resources and update the Conformance page.
      Show
      Propose defining two sets of subscriptions, "client-managed" and "server-managed" to differentiate between the types of uses. Initial descriptions should live on the Topic-Based Subscription Components page. Workflow page should be updated to show the two different patterns. Handling errors page should be updated to describe "manual" resolution in server-managed (i.e., call the facility contact). Create additional CapabilityStatement resources and update the Conformance page.
    • Enhancement
    • Non-substantive

    Description

      To conform to the backport IG, servers must support Subscription write. 

      https://hl7.org/fhir/uv/subscriptions-backport/2024Jan/conformance.html#conformance-in-fhir-r4b

      In order to claim conformance with this guide, a server:

      • SHALL support the Subscription resource (read/write).
      • SHALL support the $status operation on the Subscription resource.
      • SHALL support the SubscriptionTopic resource (read/search).
      • SHALL support at least one channel type, and SHOULD include one from this guide
      • SHALL support at least one Payload Type

      In the terms I define in FHIR-43505, this requires support for dynamic subscriptions.  I'd recommend the IG allow for administratively created subscriptions, and have two different named capabilities servers can claim conformance to:  "dynamic subscriptions" and "administrative subscriptions" (alternate name suggestions or wordsmithing welcome).

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: