Stream: genomics
Topic: Link DiagnosticReports hierarchically
Patrick Werner (Jan 14 2019 at 20:47):
I identified this issue before and already filed: GF#17205
O&O voted this with "not persuasive", they pointed to the existing extension: http://build.fhir.org/diagnosticreport-profiles.html#extensions
Joel Schneider (Jan 14 2019 at 20:52):
If each DiagnosticReport is tied to a ServiceRequest (via DiagnosticReport.basedOn), it may be possible to use ServiceRequest.basedOn to capture the interrelationships.
Patrick Werner (Jan 14 2019 at 21:00):
Yes you could, but i can imagine use cases where you don't have the ServiceRequest anymore. Looking at the DR Extensions i don't think "basedOn" is expressed by one of the existing extensions. (extends, replaces, addendum)
Joel Schneider (Jan 14 2019 at 22:03):
Could those use cases be satisfied by using a single DiagnosticReport to aggregate all the pertinent Observation resources? Is there some additional value provided by directly referencing other DiagnosticReport resources? (Presumably, the other DiagnosticReport resources would still each reference a subset of the aggregated Observation resources.)
Last updated: Apr 12 2022 at 19:14 UTC
