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

How to create a (mandatory) Subscription resource as referenced from SubscriptionStatus

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • FHIR R5 Subscriptions Backport (FHIR)
    • 1.1.0
    • FHIR Infrastructure
    • STU
    • R4 Backported R5 SubscriptionStatus
    • Hide

      Subscription notifications are (by definition) tied to a Subscription.

      If you wish to send a message that is not tied to a Subscription, an application can either make a RESTful call where the application acts as a client or can use FHIR Messaging.

      Use of infrastructure resources such as SubscriptionNotification is not currently supported outside of their defined scope.

      If there is a desire is to modify the infrastructure to be more generic and not tied to subscriptions, that needs to be filed in a ticket against the core specification (R6). If such a change is made there, the backport IG can respond in kind.

      Propose documenting Server-based management of Subscription resources as well as the rationale described above in the IG.

      Show
      Subscription notifications are (by definition) tied to a Subscription. If you wish to send a message that is not tied to a Subscription, an application can either make a RESTful call where the application acts as a client or can use FHIR Messaging. Use of infrastructure resources such as SubscriptionNotification is not currently supported outside of their defined scope. If there is a desire is to modify the infrastructure to be more generic and not tied to subscriptions, that needs to be filed in a ticket against the core specification (R6). If such a change is made there, the backport IG can respond in kind. Propose documenting Server-based management of Subscription resources as well as the rationale described above in the IG.
    • Rick Geimer / Corey Spears: 13-0-0
    • Clarification
    • Non-substantive

    Description

      The SubscriptionStatus in the notification bundle has a mandatory reference to a Subscription, but there is no mention in the IG how this Subscription would be created. If no Subscription is assumed to exist, the reference would not be resolvable. If it is assumed to exist, it should be made clear who creates it. Since this cannot be the party being notified (prior to being notified) it would be notifying party, which seems odd.

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            niekvangalen Niek van Galen
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: