Stream: implementers
Topic: ProcedureRequest for lab orders
Natalya Pogrebetsky (Feb 06 2018 at 20:04):
Hello everyone,
We are using ProcedureRequest resource for test orders (lab). Is there a way to use one entity to capture all the common stuff on an order? For example ordering practitioner or cc’list will be the same for all test requests in one order, we would like to avoid repeating the common information
Vassil Peytchev (Feb 06 2018 at 20:10):
Task resource, and workflow execution: http://build.fhir.org/workflow-communications.html
Natalya Pogrebetsky (Feb 06 2018 at 20:27):
Thank you Vassil. But ProcedureRequest resource is not on the workflow- summary list.
Lloyd McKenzie (Feb 06 2018 at 21:27):
The general rule in FHIR is "repeat everything everywhere". The reason is that even if in a particular interaction you know that you're passing along a bundle of information where the receiver might be able to "infer" that certain information applies multiple places, there's no guarantee that information will be shared in the same packaging structure in the future. Furthermore, experience with the notion of "conducted" context turned out to work rather badly in other HL7 standards. It was very difficult to specify cleanly what sort of conductance should occur. And even when well-specified, it was inconsistently implemented.
So: In FHIR, everything gets asserted on every single resource instance - who the patient is, who the author is, when it was created, who should action it, etc. This is still pretty light-weight because most of these common elements are references - so you only need to include the URL pointer to the Patient, Practitioner, Organization, Device, etc.
If a resource doesn't list a subject, that means that there is no subject or the subject is unknown. It does NOT mean the subject should be inferred from some other element.
Vassil Peytchev (Feb 07 2018 at 15:29):
Natalia, please take a look at http://build.fhir.org/servicerequest.html - unless there's a need to keep backwards compatibility with some existing implementation, it seems that ServiceRequest is the most current resource that represents diagnostic requests (such as lab orders).
Natalya Pogrebetsky (Feb 07 2018 at 16:15):
Thank you Lloyd and Vassil!
Last updated: Apr 12 2022 at 19:14 UTC
