Facilitator: Anthony Julian
Note Taker: Anthony Julian
|X||Anthony Julian||Mayo Clinic|
Meeting Minutes from Discussion
|Decision Link(if not child)|
|Methodology||Block vote #6||3-0-1|
No action V2MGMT did not meet.
|Methodology||Repetition of UAC||Next meeting|
|Methodology||Messaging in FHIR|
Expectation of content models. Whether or not the expected response from a request in fhir messaging is intended to be a bundle in all cases: If you are
returning an operation outcome is it in the bundle, or separate? Vassil Peytchev Contradictory language in message header resource description: needs to
be clarified, and made consistent with the messaging framework page. http://build.fhir.org/messaging.html 184.108.40.206,1
Synchronous is clear. Asynchronous requires an immediate response,
However synchronous message exchange does not cater for multiple response messages, which may arise when processing queries, and also imposes through-put limitations which may become relevant at high volumes. Additionally, it might not be practical or appropriate to wait for response messages. In these cases, the asynchronous message pattern should be used.
In Asynchronous messaging, the server acknowledges receipt of the message immediately, and responds to the sender separately. The server may respond more than once to any given message. (with a message bundle carrying a messageHeader.)
3.4.3 $process-message - - Issues!
This says that it can return HTTP response, but messaging says must return a bundle of type messages.
The simplest way to handle messages where there are also RESTful interactions occurring is to use the $process-message. This operation accepts a message, processes it according to the definition of the event in the message header, and returns a one or more response messages. See the opreation definition for further details.(Correct Spelling)
The following rules apply when using $process-message:
|Methodology||Guidance for data sharing.||Next meeting|
|Minute Approval||2020-05-07-InM WG Agenda/Minutes|
|Block vote #6|
Let me know if you would like to pull an item out to discuss. You will get another opportunity on the call to remove an item.
Jira Issue Summary (Reporter) Resolution