Stream: implementers
Topic: Checked diagnostic reports
Ismel Martínez Díaz (Sep 09 2019 at 18:19):
Is there a resource or field that allows to mark or know the diagnostic reports checked by practitioners?
Lloyd McKenzie (Sep 09 2019 at 18:59):
Your two best candidates would be Provenance (record of it having been done) and Task (request for it to be done, with status indicating completion once finished). You can also use the meta.tag mechanism having tags for things like "Dr. Smith needs to see this" or "Dr. Smith has reviewed this".
Ismel Martínez Díaz (Sep 09 2019 at 19:40):
Thanks. Can you give some link to the meta.tag mechanism ? I think a Provenance or a Task will not work.
Grahame Grieve (Sep 09 2019 at 20:09):
@Brian Postlethwaite isn't this what VerificationResult is for?
Lloyd McKenzie (Sep 09 2019 at 21:37):
http://build.fhir.org/resource.html#Meta
Lloyd McKenzie (Sep 09 2019 at 21:37):
Tags are arbitrary URIs that indicate something about the resource that can change without (typically) breaking the resource signature. They're typically used for workflow management type functions.
Brian Postlethwaite (Sep 09 2019 at 22:07):
That does sound more like verificationresult than provenance to me too.
John Moehrke (Sep 09 2019 at 22:24):
the distinction between VerificationResult and Provenance is still unclear. I have interest in looking closely at making VerificationResult as extensions on Provenance. But that work has not gotten attention.
John Moehrke (Sep 09 2019 at 22:25):
Thanks. Can you give some link to the meta.tag mechanism ? I think a Provenance or a Task will not work.
Why do you think this is not a role of Task or Provenance or VerificationResult?
John Moehrke (Sep 09 2019 at 22:26):
There are security tags for Integrity assertions. http://build.fhir.org/v3/SecurityIntegrityObservationValue/vs.html
These are similarly situated to the meta tags that Lloyd mentioned; but are a defined valueSet
Ismel Martínez Díaz (Sep 10 2019 at 13:37):
@Lloyd McKenzie thanks for the link. @John Moehrke I think that Task or Provenance or VerificationResult are more general resources. A DiagnosticReport review or checking must be a DiagnosticReport status or property. Or there should be a resource closer to DiagnosticReport more related with the object characteristics instead of object actions and proccess.
Lloyd McKenzie (Sep 10 2019 at 15:22):
Many things might be looked at/reviewed - orders, results, plans, etc. The mechanism for handling them should generally be consistent
Eric Haas (Sep 10 2019 at 17:05):
the status in DR imply checking or posting or verification
Eric Haas (Sep 10 2019 at 17:05):
or whatever you wanna call it
Eric Haas (Sep 10 2019 at 17:06):
if you want more information on who what and where then use Provenance, if you want even more then consider VerficiationResult although that is still relatively new
Last updated: Apr 12 2022 at 19:14 UTC
