Stream: Orders and Observation WG
Topic: ORU Mapping
Iryna Roy (Apr 19 2019 at 03:20):
Hello dear implementers, I am searching for information about ORU to FHIR mapping - particularly I need to map who ordered the lab test (Ordring Provider) and who should receive it (CC providers) - help! I am lost
Lloyd McKenzie (Apr 19 2019 at 03:51):
Who ordered it would be ServiceRequest.requester. As for cc recipients, I'm not sure. @Eric Haas ?
Eric Haas (Apr 19 2019 at 16:01):
Part of Task? @Hans Buitendijk have you looked at this yet in the mappings?
Lloyd McKenzie (Apr 19 2019 at 16:04):
It seems like it should be part of the ServiceRequest, not Task. If you write a lab order and ask 3 labs to fulfill it before you find one that can/will, the 'cc request' wouldn't be any different for each of those requests - that means that it should probably be part of the order, not the fulfillment request.
Eric Haas (Apr 19 2019 at 16:17):
Task identifies the recipients too
Lloyd McKenzie (Apr 19 2019 at 17:27):
Task.restriction.recipient is for when you've got an order for a group of people/animals and are seeking fulfillment for just one of them. It has nothing to do with distribution of the results.
Eric Haas (Apr 19 2019 at 23:21):
Well the definition forTask.restriction.recipient : "For requests that are targeted to more than on [sic] potential recipient/target, for whom is fulfillment sought?"
makes do sense to me..
although it implies the request needs multiple recipients. Which is absent from ServiceRequest and the pattern.
Eric Haas (Apr 19 2019 at 23:28):
I think we need to discuss whether add'l recipients ( in addition to the orderer) are need in both places. like in CommunicationRequest
Eric Haas (Apr 19 2019 at 23:34):
Lloyd McKenzie (Apr 19 2019 at 23:59):
Task.restriction.recipient would apply if the ServiceRequest was for a Group and the Task was asking for the fulfillment of the service for just one Patient within that Group. That's totally different than "cc this other Practitioner with the results of the service request"
Eric Haas (Apr 21 2019 at 04:28):
recipient of task vs recipient of request is confusing still
Lloyd McKenzie (Apr 21 2019 at 06:29):
We could propose a name-change if you like.
Iryna Roy (Apr 22 2019 at 15:28):
I would agree with Lloyd, based on my previous history with standards, this is what I would think - ServiceRequest may contain Ordered by and CC list. I would think tasks are related to Care plans, care plan activities, workflows, etc. My system is exchanging lab requests/results and is not aware of care aspects. Thank you! I will try the service request
Hans Buitendijk (Sep 18 2019 at 19:00):
We discussed in OO WGM today and agreed that we will have a gForge to provide a recipient extension. We are looking at using an existing extension for C-CDA on FHIR by having that extension expanded so we can use it with ServiceRequest.
Eric Haas (Sep 19 2019 at 12:40):
@Vassil Peytchev can you answer my question?
Eric Haas (Sep 19 2019 at 12:44):
@Hans Buitendijk we talked about this earlier this week. in FHIR how would the order be forwarded to the cc securely. ( assuming outside of trusted network )
Last updated: Apr 12 2022 at 19:14 UTC
