FHIR Chat · Glossary · genomics

Stream: genomics

Topic: Glossary


view this post on Zulip Jamie Jones (Sep 19 2019 at 17:28):

Draft of all the guidance we provide in observation profile spreadsheet (and some LOINC lookups I expanded with local tooling for convenience): http://build.fhir.org/ig/HL7/genomics-reporting/Glossary.html

view this post on Zulip Kevin Power (Sep 19 2019 at 17:45):

Nice and very useful. However, I am not sure I would call this a glossary?

Also, as we change/adjust codeable concepts, how do we regenerate this page? Do you have to use your local tooling to do that?

view this post on Zulip Jamie Jones (Sep 19 2019 at 18:52):

We decided to view a centralized statement of our definitions on the "glossary" tracker, and I think it is quite useful to see what needs more clarity (any blank entries in the table correspond with gaps in definition on the profiles themselves).

And yes, I don't want to mess with the framework too much, so updates to the spreadsheet would have to be duplicated here, which is why we waited to apply until ready for publication. Should be much easier to integrate once we switch to new templating.

view this post on Zulip Jamie Jones (Sep 19 2019 at 18:55):

https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16513&start=0

view this post on Zulip Jamie Jones (Sep 19 2019 at 18:56):

Happy to name/format it however is most appropriate, definitely open to suggestions for improvement.

view this post on Zulip Jamie Jones (Sep 19 2019 at 18:58):

There are a couple example/textual answer lists we already provide that could be easily added in, for starters.

view this post on Zulip Kevin Power (Sep 19 2019 at 19:09):

This is one of those that I don't really have a better alternative for it, and if the group is happy with this as our starter 'glossary', I am happy with it. Great work @James Jones !

view this post on Zulip Dora Walter (Sep 26 2019 at 12:37):

missing text: Example for Allelic read depth (82121-5)

There are two kinds: Allele depth (AD) and depth of coverage (DP). These are complementary fields that represent two important ways of thinking about the depth of the data for this sample at this site.

AD is the unfiltered allele depth, i.e. the number of reads that support each of the reported alleles. All reads at the position (including reads that did not pass the variant caller’s filters) are included in this number, except reads that were considered uninformative. Reads are considered uninformative when they do not provide enough statistical evidence to support one allele over another.

DP is the filtered depth, at the sample level. This gives you the number of filtered reads that support each of the reported alleles. You can check the variant caller’s documentation to see which filters are applied by default. Only reads that passed the variant caller’s filters are included in this number. However, unlike the AD calculation, uninformative reads are included in DP.

Source: https://gatkforums.broadinstitute.org/gatk/discussion/1268/what-is-a-vcf-and-how-should-i-interpret-it

missing text: Example for Human reference sequence assembly version (62374-4)
A reference genome (also known as a reference assembly) is a digital nucleic acid sequence database, assembled as a representative example of a species' set of genes. (Source: https://en.wikipedia.org/wiki/Reference_genome)

view this post on Zulip Bret H (Sep 27 2019 at 02:32):

@James Jones nice work. suggest to provide more clarity on the the codes - e.g. separate code with new line with 'LOINC XXXX-X' The short hand profile names are nice but are not the names on the profiles. Change HTML so that the Headers of the columns are always at the top as you scroll. feel free to tell me to add it. lots of JS tricks to provide more info on each line - any flexibility here or do we have a HL7 FHIR style guide?


Last updated: Apr 12 2022 at 19:14 UTC