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

Add missing Asynchronous Scenario step on Specification page

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Hybrid/Intermediary Exchange (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • Specification
    • 5.6.1
    • Hide

      Update the narrative and diagram in the asynchronous flow section 5.6 as follows:

      Change Step 5 from:

      • The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which the response data will be available

           to

      • The destination processes the request and returns the location to poll for status to the intermediary. The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which status of the request will be available

       

      Add a step following Step 5:

      • The originator polls for status until the server responds with a "completed" HTTP status code 200 and body containing one or more URLs at which to retrieve the response data

       

      Change Step 6 from:

      • The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination

           to

      • The originator later retrieves the response data using the URL(s) previously returned in the completed status response Content-Location parameter of the initial response from the destination

       

      Update the diagram to include the added polling step

      Show
      Update the narrative and diagram in the asynchronous flow section 5.6 as follows: Change Step 5 from: The destination responds with an HTTP status code of  202 Accepted , and an HTTP header containing a  Content-Location  parameter that specifies the URL at which the response data will be available      to The destination processes the request and returns  the location to poll for status  to the intermediary. The destination responds with an HTTP status code of  202 Accepted , and an HTTP header containing a  Content-Location  parameter that specifies the URL at which  status of the request  will be available   Add a step following Step 5: The originator polls for status until the server responds with a "completed" HTTP status code 200 and body containing one or more URLs at which to retrieve the response data   Change Step 6 from: The originator later retrieves the response data using the address previously returned in the  Content-Location  parameter of the initial response from the destination      to The originator  later  retrieves the response data using the  URL(s)   previously  returned in the  completed status response   Content-Location  parameter of the initial response  from the destination   Update the diagram to include the added polling step
    • Frank McKinney / Christiaan Knaap: 11-0-0
    • Correction
    • Non-substantive
    • 0.1.0

    Description

      The Asynchronous Scenario section oversimplifies the async flow. The narrative and diagram should be updated as follows:

      Change Step 5 from:

      • The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which the response data will be available

           to

      • The destination processes the request and returns the location to poll for status to the intermediary. The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which status of the request will be available

       

      Add a step following Step 5:

      • The originator polls for status until the server responds with a "completed" HTTP status code 200 and body containing one or more URLs at which to retrieve the response data

       

      Change Step 6 from:

      • The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination

           to

      • The originator later retrieves the response data using the URL(s) previously returned in the completed status response Content-Location parameter of the initial response from the destination

       

      Update the diagram to include the added polling step

      Attachments

        Activity

          People

            Unassigned Unassigned
            frank_mckinney Frank McKinney
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: