Stream: implementers
Topic: Specimen in DiagReq
Jose Montoya (Dec 01 2016 at 23:36):
Hey all,
Jose Montoya (Dec 01 2016 at 23:37):
Is there a reason why Specimen was removed from DiagnosticRequest?
Jose Montoya (Dec 01 2016 at 23:37):
The client for whom we're implementing the resources is concerned that HL7 had a specimen field inside the DiagOrder and v2 had it, but v3 removed it?
Jose Montoya (Dec 02 2016 at 12:01):
Anybody?
Grahame Grieve (Dec 02 2016 at 19:09):
@Eric Haas ?
Eric Haas (Dec 02 2016 at 19:30):
its coming back. OO went back and forth. Typically the request precedes the specimen so specimen references the request. Sometimes it opposite. Tracker to create either an extension or element. Need to avoid direct cross referencing of resources here.
Grahame Grieve (Dec 02 2016 at 20:11):
what goes in the v2 specimen field? type of specimen?
Grahame Grieve (Dec 02 2016 at 20:12):
workflows I know of where the specimen comes first:
- biopsy / resection
Workflows where the request comes first
- normal lab (phlebotmoty rounds etc)
Grahame Grieve (Dec 02 2016 at 20:12):
but the lab doesn't always see the request before the specimen?
Jose Montoya (Dec 03 2016 at 22:05):
It's a ref to the Specimen
Jose Montoya (Dec 03 2016 at 22:16):
And related to the changes between DiagOrder and DiagRequest, what happened to Items? Is it coming back as well, or it's expected to only order 1 item per request? Seems to me it should allow multiple items per request.
Grahame Grieve (Dec 04 2016 at 05:26):
Follows the same pattern as MedicationRequest - multiple individual DiagnosticRequest, with a grouping item
Eric Haas (Dec 04 2016 at 07:03):
DiagnosticRequest now follows the Workflow request pattern = check it out here: http://build.fhir.org/request.html. in V2 there is a specimen segment contains type, identifiers, dates etc. And yes the two workflows are reason why needed references both ways.
Jose Montoya (Dec 04 2016 at 21:43):
When speciment gets added back to DiagReq will it be an array as it was in DiagOrder or a single object? Do we know at this point?
Grahame Grieve (Dec 04 2016 at 21:46):
you should not assume that it's going to be added back in at this point. You should definitely create a task to ensure that it doesn't get overlooked
Eric Haas (Dec 04 2016 at 21:49):
it will be like in DSTU2
Jose Montoya (Dec 04 2016 at 21:50):
Ok great, thanks.
Last updated: Apr 12 2022 at 19:14 UTC
