Encourage checking postMesasge results.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • SMART Web Messaging (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • (NA)
    • Workflow summary\
    • Hide

      Clarify that specifying a broadcast-type pattern is out of scope for the IG, and that an EHR initiating a message to an app is also out of scope, but may appear in future versions of the spec.  Clarify that an EHR may respond to an app message with 0 or 1 responses.

      PR: https://github.com/HL7/smart-web-messaging/pull/24

      Discussion: https://confluence.hl7.org/pages/viewpage.action?pageId=104563953#SMARTWebMessagingBallotReconciliationCC20210212-Jira9b965702-34a7-3433-bf10-7f66fd69238cFHIR-29354 

      Show
      Clarify that specifying a broadcast-type pattern is out of scope for the IG, and that an EHR initiating a message to an app is also out of scope, but may appear in future versions of the spec.  Clarify that an EHR may respond to an app message with 0 or 1 responses. PR: https://github.com/HL7/smart-web-messaging/pull/24 Discussion: https://confluence.hl7.org/pages/viewpage.action?pageId=104563953#SMARTWebMessagingBallotReconciliationCC20210212-Jira9b965702-34a7-3433-bf10-7f66fd69238cFHIR-29354  
    • Matt Varghese / Ryan Moehrke: 9-0-0
    • Clarification
    • Non-compatible
    • current

      Does this mean that providing a response message is optional? I'm not sure that is wise. I would turn the sentence arround. Apps SHOULD be check the status code response message (message with responseToMessagId set to the send message).

      Existing Wording:

      Applications SHOULD be prepared to see, at most, one incoming message with a given responseToMessageId. If multiple response messages (e.g., streams) are needed, this can be accomplished by having the server send “unsolicited” messages, i.e., messages with no responseToMessageId, after a client’s initial request.

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: