Stream: implementers
Topic: Placer Order Number
Burke Mamlin (Mar 16 2016 at 19:35):
Anyone know if there's a link from Observation to the order it is fulfilling (i.e., OBR-2 Placer Order Number in v2)? We want to carry the placer number through to results and I'm not seeing where it would go. Perhaps I'm just having a senior moment. 
Grahame Grieve (Mar 16 2016 at 20:43):
OBR corresponds to DiagnosticReport, and that has the link
Lloyd McKenzie (Mar 16 2016 at 22:43):
Plan is for Observation to be able to point to it's corresponding Order - that will be part of the fallout from the Workflow process
Eric Haas (Mar 17 2016 at 01:11):
OK that little nugget I missed - how exactly are we proposing to do that and If we go that route the I think the mash up of DR and Obs is essentially complete and we don't need both.
Lloyd McKenzie (Mar 17 2016 at 01:43):
Every "event" type resource that can be the result of a request should have a "request" (or equivalent) element 0..* Reference(varies) that points to the request resource that could have resulted in that action (orders, encoded orders, reflex orders, recommendations, plans, proposals, etc.). In this case, I'd expect DiagnosticOrder, ReferalRequest, ProcedureRequest and CarePlan at a minimum.
Lloyd McKenzie (Mar 17 2016 at 01:44):
It may be that DR isn't needed anymore, I don't know. But certainly you're not going to have a DR just because someone made an order.
Last updated: Apr 12 2022 at 19:14 UTC
