FHIR Chat · Missing change for Level of Evidence

Stream: genomics/committers

Topic: Missing change for Level of Evidence

Kevin Power (Oct 17 2019 at 14:28):

In a separate email thread regarding the LOINC updates for Level of Evidence / Clinical Evidence, I discovered a change that we voted on but I don't think we applied. Wanted to get input from this group:

I did some searching back through our weekly meeting notes, and I did find this vote:
https://confluence.hl7.org/display/CGW/CG-2019-08-27

      Motion 1: Remove the text about AMP from the description of 93044-6 so that the Level of Evidence concept is distinct from Level of clinical significance

          motion/2nd: Swapna/Clem
          discusion - none
          abstains 0
          nay 0
          yeas 13
          motion passes

It seems we did not apply this change, as this is still in the IG:
Definition

        Indicates the quality and type of evidence supporting this assertion. E.g. Tier I - Level A, Tier I - Level B, Tier II - Level C, Tier II - Level D, Tier III, Tier IV, Not Applicable.

@James Jones or @Patrick Werner – Am I missing something? Seems like we missed this one? This should have been turned into a tracker, but wasn’t.

Jamie Jones (Oct 17 2019 at 15:51):

I don't think we realized that text was in the IG at the time, or it would have been removed in that discussion. I can update it as a clerical error if you think that is justified.

Kevin Power (Oct 17 2019 at 16:24):

I am fine with that

Jamie Jones (Oct 17 2019 at 16:27):

Yeah this was hidden within the spreadsheet and only viewable as a tooltip for the component until we put the glossary in. Is there a time we are setting as an official freeze for the publication build?

Kevin Power (Oct 17 2019 at 16:31):

I am fine applying this change, but of course we will want to be careful about many changes right now.

Jamie Jones (Oct 17 2019 at 19:59):

I have this fixed locally but am getting SSL errors on _genUpdatePublisher.sh so don't want to push until I verify the build didn't change on us... can anyone run an update locally?