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

Subscription response should be complete

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Post Acute Orders (FHIR)
    • 0.1.1
    • Orders & Observations
    • (NA)
    • 2.8
    • Hide

      The implementation of subscription notification with a following retrieval of the actual response is assumed to be fully automated by the respective systems and will not present a burden to the provider.  This method is intended to support the general subscription methods planned for R5.

      Will clarify this in the IG

      Show
      The implementation of subscription notification with a following retrieval of the actual response is assumed to be fully automated by the respective systems and will not present a burden to the provider.  This method is intended to support the general subscription methods planned for R5. Will clarify this in the IG
    • Bob Dieterle / Marti Velezis : 7-0-8
    • Clarification
    • Non-substantive

    Description

      We strongly recommend that the subscription model return a complete reponse. A provider should not have to go retrieve a response (which proves burdensome) when it could be sent directly to them.

      Existing Wording:

      We are soliciting input on the use of the Subscription resource on the Task resource as a way of communicating updates by the service provider to the ordering provider. While we may recommend the use of a notification with a subsequent request for the current status by the ordering provider, we have made provision for the subscription to request a complete response including the Task and the specific order resource.  

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: