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

Subscriptions should clarify reliable vs unreliable subscriptions

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • Subscriptions Framework
    • 3.9
    • Hide

      Will add an extension that says "channel should be treated as though it is using a non-guaranteed delivery mechanism, effectively labeling the subscription as 'best effort'."

      Show
      Will add an extension that says "channel should be treated as though it is using a non-guaranteed delivery mechanism, effectively labeling the subscription as 'best effort'."
    • Gino Canessa/Bas van den Heuvel: 13-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      The subscriptions framework supports two modes of operation: reliable and unreliable.

      These two modes of operation should be described more explicitly in this overview, including the choices related to notifications and topics related to these different modes of operation.
      I.e. in unreliable notifications, the event-number can be omitted (see FHIR-38920), the $events and $status operation are not required. The notification mechanisms id-only nd full-resource are less usefull.

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: