Stream: implementers
Topic: Messages "about" a specific ServiceRequest
Tim Berezny (Dec 11 2018 at 17:53):
We are building a FHIR eReferral specification, using a messaging paradigm. Messaging events include things like submit-referral, add-appointment, update-status, send-communication, etc…
Most events include only the messageHeader + the main resource of the event (like appointment or task).
Every message is “about” a specific referral (ServiceRequest). However, not every message includes the ServiceRequest resource in it. We are trying to determine an easy way to identify which referral each message is “about” without traversing deep into the multiple resource calls, or adding additional resources (i.e., serviceRequest) into each payload.
The current idea is, the sending system will submit its own native identifier with the initial ServiceRequest, then every subsequent message with include that identifier in the messageHeader, no matter the event. MessageHeader does not have an identifier, so we would need to add an identifier element.
Is this an appropriate workflow to tie messages to a specific ServiceRequest? Is there another method we should consider?
Lloyd McKenzie (Dec 11 2018 at 21:20):
You could just populate the MessageHeader.focus.identifier with the ServiceRequest.identifier
Tim Berezny (Dec 11 2018 at 21:40):
Oh that's a very very interesting and elegant idea. Thanks @Lloyd McKenzie , I think we'll try that.
Last updated: Apr 12 2022 at 19:14 UTC
