Stream: genomics
Topic: DiagnosticReport Discussion
Kevin Power (Oct 13 2020 at 19:05):
Thought everyone would want to follow this:
https://chat.fhir.org/#narrow/stream/179166-implementers/topic/DiagnosticReport
Jamie Jones (Oct 13 2020 at 19:12):
Interesting, they'd punt the representedform of the report back to composition. Perhaps we ought to give an example of using comp
Jamie Jones (Oct 13 2020 at 19:13):
Rather then Groupers
Jamie Jones (Oct 13 2020 at 19:14):
Though I don't know DR could rightly reference a composition in R4 (where the IG is based)
Kevin Power (Oct 13 2020 at 19:29):
Would only be applicable in R5 and beyond (without some sort of backporting on our part)
Jamie Jones (Oct 13 2020 at 19:29):
We may want to consider backporting the reference to composition as an extension
Jamie Jones (Oct 13 2020 at 19:29):
If this goes in, I understand the discussion on it is very new
K. Ruch (Jun 11 2021 at 14:29):
Hi All! I have 2 questions in regard to summarized versions of complete reports.
As you know, genomics reports can be quite lengthy. I have received multiple requests from providers to include a summary along with the complete report.
- Is there a standard industry term used by the Work Group for summaries or over-reads of the report?
- Can anyone point me in a direction with available resources for best practices related to genomics summaries?
Arthur Hermann (Jun 18 2021 at 17:38):
Can anyone help Kira with her questions re: summaries?
Bob Freimuth (Jun 23 2021 at 15:14):
I am not aware of any best practices or an industry standard that could help guide this. Unfortunately, reports are very heterogeneous. :-)
The emerge project ran into some similar issues, and their approaches might be informative:
https://emerge-fhir-spec.readthedocs.io/en/latest/issues_and_resolutions.html#
Bret H (Oct 06 2021 at 22:30):
So, in general there is narrative section (.text) that is available in every profile/resource instance. It is meant to be a human readable summary of the data and can include information that is not discreetly available in the data elements themselves.
Bret H (Oct 06 2021 at 22:31):
the risk is not having the statements as discreet data elements (not 'natively' computer friendly)
Last updated: Apr 12 2022 at 19:14 UTC
