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

Why not response-url?

    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

      Why is response-url explicitly not permitted? Since you're already not permitting async=true, it seems like the $process-message operation definition would also not permit any other querystring parameters. Is there an additional reason you're calling it out explicitly?

      Existing Wording:

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

      (Comment 10 - imported by: Jean Duteau)

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: