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

Verify if the proposed message synchronicity is compliant with FHIR.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 0.1.0 [deprecated]
    • Pharmacy
    • Message submission
    • Hide

      Change the guide's aysnchronous processing to follow what's defined in the $process-message operation--removing the prohibition on use of the async parameter.

      Adjust wording in Systematic Queries and Message Submission pages accordingly.

      Show
      Change the guide's aysnchronous processing to follow what's defined in the $process-message operation--removing the prohibition on use of the async parameter. Adjust wording in Systematic Queries and Message Submission pages accordingly.
    • Frank McKinney / Tim McNeil : 11-0-3
    • Clarification
    • Compatible, substantive
    • 0.1.0 [deprecated]

    Description

      Our understanding is that sync or async should be decided by the requesting side, and the responding system must follow it. Not the other around. (see FHIR Operations page: https://www.hl7.org/fhir/messageheader-operation-process-message.html)

      Existing Wording:

      Specialty Rx Query Responses are expected to be systematically produced using data in the patient’s electronic health record. They may be returned synchronously or asynchronously in near real-time. The Requesting System cannot influence which behavior occurs; when a message is received, the Data Source System determines whether it will respond synchronously or asynchronously.

      (Comment 21 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            dzhang Daniel Zhang
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: