Stream: v2 to FHIR
Topic: Task - MSH v ORC
René Spronk (Mar 25 2022 at 15:39):
In the draft message mappings I see that some orders have a Task generated from the MSH, and a Task for ORC. I certainly understand the latter. MSH to Task could be the 'receiver responsibilities' (to create an application ack) - but that's just a guess. What's the rationale behind that mapping?
Craig Newman (Mar 25 2022 at 18:24):
Including @Hans Buitendijk . The v2-to-FHIR project hasn't discussed tasks much (the mapping you may have seen in the ORM message map) hasn't been completed yet (there is no MSH to Task map yet). I suspect it's a hold over from an earlier Zulip discussion we've had https://chat.fhir.org/#narrow/stream/179188-v2-to-FHIR/topic/task.20vs.20message.20header where you proposed a receiver responsibility Task be created. This is probably something we should come back to.
René Spronk (Mar 26 2022 at 10:26):
Ah, yes, the 'implicit workflow implications of a message'. Given that these aren't documented in the v2 standard, it's probably better (from a mapping perspective) to document the fact that there may be such workflow expectations/implications, without including it in the actual mappings.
Last updated: Apr 12 2022 at 19:14 UTC
