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

Clarify your intent for message synchronicity.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 0.1.0 [deprecated]
    • Pharmacy
    • Systematic Query Workflows
    • 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

      Overall, this section is a bit confusing after only a cursory read of the $process-message operation definition. You should further clarify that, although the Requestor isn't permitted to specify the synchronicity, the data source is.

      Existing Wording:

      Note: The async and response-url Process Message parameters are not to be used when exchanging Specialty Rx messages\.

      (Comment 9 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: