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

Add missing Asynchronous Scenario step on Use Cases page

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Hybrid/Intermediary Exchange (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • Use Cases and Roles
    • 2.6.1
    • Hide

      The steps that currently say:

      • The destination processes the request and returns its response 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 the response data will be available
      • ...
      • The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination

      ... should be changed 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
      • 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
      • ...
      • 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
      Show
      The steps that currently say: The destination processes the request and returns its response 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 the response data will be available ... The originator later retrieves the response data using the address previously returned in the  Content-Location  parameter of the initial response from the destination ... should be changed 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 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 ... 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
    • Frank McKinney / Christiaan Knaap: 11-0-0
    • Correction
    • Non-substantive
    • 0.1.0

    Description

      The Asynchronous Scenario section oversimplifies the async flow. The steps that currently say:

      • The destination processes the request and returns its response 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 the response data will be available
      • ...
      • The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination

      ... should be changed 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
      • 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
      • ...
      • 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

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: