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

Consider describing administratively created subscriptions

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • R6
    • FHIR Infrastructure
    • STU
    • Workflow
    • Hide

      Will categorize the current mechanism as Dynamic and add the Administrative process to the IG.

      Show
      Will categorize the current mechanism as Dynamic and add the Administrative process to the IG.
    • Michael Donnelly / Rick Geimer: 13-0-0
    • Enhancement
    • Compatible, substantive

    Description

      I believe there are two methods of creating a subscription:

      • Dynamically - where the client does RESTful POST to register a Subscription with the server.  
      • Administratively - where an admin user on the server configures a subscription for a client. 

       

      Dynamic subscription creation is covered well in the current spec.  However, the "[Creating a Subscription" section only describes dynamic subscriptions, and implies that might be the only way.  It seems worth describing the two different ways so that the reader understands that administratively created subscriptions are an option.

       

      Given the real-world governance processes many integrations need to follow (i.e., admins will want to evaluate the performance and data security impacts of a subscription a client wants), I expect administratively created subscriptions may be common enough to warrant mention in the subscription page.

      Attachments

        1. image-2024-01-08-14-35-18-443.png
          image-2024-01-08-14-35-18-443.png
          25 kB

        Activity

          People

            ginocanessa Gino Canessa
            cooper.thompson Cooper Thompson
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: