I’m involved in a couple of projects e.g @ehebel Fellowhip project, which are tackling the whole Lab order/ report cycle, including interim messages such as ‘specimen received’.
The plan is to use a template aligned to EHDS Lab Report to receive the messages (HL7v2/FHIR) but we have some choices for handling the Lab order / status events, where we will use the service_request INSTRUCTION and ACTION archetypes
-
Use the EHDS Lab report composition to handle all of the events from the original order through to final report, essentially as a persistent composition and as an ‘incremental report’.
-
Have a separate Lab request template , t ocarry the inital request/ status and again update this for each interim status message.
-
As for 2 but record each Service event as a separate composition, and use AQL to knit the ‘current status’ together.
I know there are legitimate arguments for each but it would be good to understand if there is any overall majority preference, particularly if folks have changed in light of experience @chunlan.ma - your hospital infection system journey will be interesting.
If we can nail this down a bit, it will allow us to package up the whole order/report cycle with FHIRConnect mappings etc and provide another EHRSlice @Seref