Stream: Orders and Observation WG
Topic: Shipping method for orders
Yassiel Oliva (May 28 2019 at 12:37):
Hi, I'm representing laboratory orders using RequestGroup and ServiceRequest. Now, as part of the lab flow, we need to send to the patients a kit. Now I need to store in some way the shipping method I want to use for each kit but I'm not sure where to put that kind of information. can anyone point me in the right direction?
Lloyd McKenzie (May 28 2019 at 13:07):
DeviceRequest would be the mechanism for ordering the kit. You might need an extension for shipping method though. You could submit a change request for a standard extension.
Jose Costa Teixeira (May 28 2019 at 23:01):
We should add that to SupplyRequest also. If it is only about the physical transportation, I would use SupplyRequest rather than DeviceRequest
Lloyd McKenzie (May 28 2019 at 23:15):
Supply Request doesn't link to Patient
Jose Costa Teixeira (May 30 2019 at 22:11):
yep, my bad. We discussed adding it for this exact purpose but it is not there yet.
Lloyd McKenzie (May 30 2019 at 22:22):
I'd be opposed to adding it. The FMG agreed to allow SupplyRequest as a resource solely on the grounds that it was for non-patient-specific purposes (and thus there was no overlap with DeviceRequest and MedicationRequest). We don't want to do anything that would create that overlap.
Jose Costa Teixeira (May 31 2019 at 06:01):
Implementations use that motion of delivery to a patient. We may keep the boundary "patient specific" but then we have to carefully look at boundaries across all xxxRequests resources to avoid gaps and overlaps
Jose Costa Teixeira (May 31 2019 at 06:02):
If something is being requested to be delivered to a patient and we do not care whether it is a device or a med or a nutrition, what do we use for that?
Jose Costa Teixeira (May 31 2019 at 06:05):
This is not a clinical request (in the functional sense and with the legal implications of it). I think that all our xxxRequests are clinical. But I may be wrong
Jose Costa Teixeira (May 31 2019 at 06:07):
When implementing, this was the 20% of function that gives 80% of the work or 80% of the z segments and Z events in v2
Jose Costa Teixeira (May 31 2019 at 06:11):
This notion of requesting stuff to be delivered to a patient - or to a location but to put in a patient's shelf - is implemented in systems - ERPs, not EHRs
Jose Costa Teixeira (May 31 2019 at 06:12):
As a way out, we could have a thing called ProductRequest that can be used for logistics purposes...
Jose Costa Teixeira (May 31 2019 at 06:13):
But then we'd have to take good care of scopes and boundaries again
Lloyd McKenzie (May 31 2019 at 12:11):
My leaning would be to generify DeviceRequest
Richard Bagley (Jun 11 2019 at 19:30):
Are you guys thinking of this a value tied specifically for reuse whenever a Patient reorders? That was not our intent.
Yassiel Oliva (Jun 12 2019 at 14:44):
our kits are delivered using some carriers and with its own configurations. we are trying to find a place to store that kind of information
Andrea Pitkus, PhD, MLS(ASCP)CM, CSM (Apr 29 2020 at 13:09):
Have you looked at observation definition as part of the Order Catalog IG? It lists all kinds of specimen criteria as part of the CLIA Specimen Collection Manual and can list temperature and other specimen requirements. It might be able to support your shipping needs too. Unclear if you are asking if the specimen was sent frozen, on ice, etc. as part of your need?
Last updated: Apr 12 2022 at 19:14 UTC
