Page tree
Skip to end of metadata
Go to start of metadata

Meeting Information

https://zoom.us/j/98660729671?pwd=Z3VRcSs4RTA1M0tQVGtMUFJBWWd5UT09

Attendee Pass: HTAMeet

Chair:  Julie James

Scribe: Reuben Danielsand Caroline Macumber

Attendees

Attendee type:

H - HTA Member

O - observer

L - liaison

Present

P - present

A - Apologies

Name

Affiliation

HPJulie JamesBlue Wave Informatics LLP
Hat 8pm

Roel Barelds

Precipius b.v.

HPSusan MatneyIntermountain Health
Hat 8pmSylvia ThunHL7 Germany
HPCarol MacumberClinical Architecture
HPReuben DanielsSaludax
H
Davera GabrielJohns Hopkins University Institute for Clinical and Translational Research
L

Wayne Kubick

HL7 (CTO)

L
Suzy RoySNOMED International
O
Andrea MacLeanCanada Health Infoway
O
Bapi BeheraPrime Therapeutics
OPJessica BotaUTG/Apelon
OPTed KleinKlein Consulting / HL7 UTG / Vocabulary WG CoChair
O
Swapna AbhyankarRegenstrief Institute
O
Rob HausamVocabulary WG CoChair
LPRob McClureUS Realm Liaison
O
Carmela CoudercVocab WG CoChair
O
Mary Kay DanielCognoscente

Minutes of Previous Meeting (2020-10-14) 

Motion to accept proposed and accepted.

Agenda Topics


Agenda Outline

Agenda Item

StatusLead

Meeting Minutes from Discussion

Management

Quorum

Minutes Approval

N/AJulie

Quorum is met

Motion to approve Minutes proposed

SM moves, RB seconds: Motion 3-0-0

TopicNew PSSContinuousJulie

Report on PSS/NIB process conversation with Melva
New PSS Process in JIRA will have a "uses external terminology" question which will trigger a link to HTA involvement to work further with the project.
NIB - will be harder to get any checks here until the ballot desktop migration happens.  Aim is that no NIB be accepted until all external code systems referenced already have at least a "stub" set of metadata in Terminology.HL7.org but that is a while away yet.

CodeX Cancer Registry Reporting  PSS-1667 - Getting issue details... STATUS

Topic

External SDO Issues or additional topics

SNOMED CT versions

Continuous

Reuben

1) Report on TSC regarding wording for third party copyright

"TSC has reviewed the request to include text for 3rd party content and wordsmith the provided text, resulting in the following. Upon agreement by HTA, the final text will then need to be sent to HQ for review by HL7 legal for final approval. Text the TSC suggested is:

"Please note that some external, licensed code systems content when present in an HL7 specification is subject to additional copyright from third parties' (for example proprietary assessment scale content in LOINC, and/or language translation copyright), the use of which must comply with the applicable terms of use from the third party. For further information and for details of how implementers should manage use of additional party content (including license obligations) please see the copyright information provided by the code system authority."

Motion to accept this text: RD/SM - 3:0:0

Julie James to communicate this to Karen van at HQ

2) SNOMED CT editions – to seek agreement that each SNOMED edition requires its own code system information page (and, in future, its own FHIR CodeSystem resource in HL7 Terminology)

Countries with national extensions/NRCs may need to be able to directly reference their own editions of SNOMED CT.  Similar issues may exist with ICD-X and ATC in European countries that have their own "extensions" to these two code systems.  "If the Edition matters, you must include the version."

Reuben proposes: a) that we update our SCT page to be explicitly the "international edition" b) additional pages be created for national editions as required c) UTG / Terminology@HL7.org be updated in line with a) and b)

Motion to accept this RD/CM - 3:0:0

Practical technicalities will be discussed offline (Ted/Reuben) - can multiple Naming System resources have the same URI (distinguished only by what is present in the version identifier) and still work in the IG Publisher?

Vocab will work on the implementation of this.

TopicHL7 Terminology Single Repository and Supporting ProcessCompletedReuben

Report on TSC meeting for the agreed policy

TSC has endorsed unanimously that Terminology.HL7.org will be the single repository for external code system information for HL7.  Clearly, this endorsement is excellent, but it now behoves us to make this work, including how to manage this within the community.  Further discussion with TSC may be needed for this.

TopicRapid Processing for Code Systems ("stubs")NewReubenRepresenting HTA-managed external code system information data elements for a code system in HL7 Terminology FHIR CodeSystem resources (the so-called 'stubs')
TopicEDBA ContentCompletedJulie - Jim McClay from ECWG

Emergency Department Benchmarking Alliance (EDBA)  https://doi.org/10.1111/acem.13978

From an email exchange, it appears this is all going forward OK and does not require HTA input at this time.

TopicHTA Content Pages ReviewContinuousReuben

New for this TC:

  • Review of data elements for HTA-managed external code system information
    • Agreeing whether any of these can be removed e.g. "HL7 users of this information - which HL7 products use this link (if known)"
    • Agreeing whether any new elements need to be added e.g. "Endorsed for use by HTA". "Last reviewed", "Next review".
    • Agreeing which elements may be optional and which may be mandatory.

Raw data is available here

For any blanks, please insert an "N/A"

Topic

External Code Systems 


Continuous

Susan



Carol

Have URLs from HCA Healthcare for CCC code systems

Also working with ICN / ICNP.....particularly for those countries which will not be using the SNOMED cross walk; 

ENP and ICF - outstanding; Julie to do LCP

FM WG: CPT - copyright statement is approved, are reviewing all the other info....also shared with US Core

ICD-9CM and ICD-10CM - both done, reusing legacy identifiers as nothing back from NCHS

NCPDP - 7 code systems all approved, although have temp identifiers...will become permanent soon

NUBC - 6 code systems all done and ready for production

NDC - ready for approval; Approval motion: RD/SM 3:0:0

CMS RARC codes - managed/stewarded (owned) by CMS, published by X12

X12 - 3 done (published by X12 but not necessarily "owned" by them)

DRGs - last one on Mary Kay's list

Major vote of thanks to Carol for all this amazing effort; everyone to buy Carol a drink at the next real meeting

All these are "US Realm" - what is the responsibilities of the US Realm Steering Committee in this?  

Having done all this, it may be that we should separate out "owner", "maintainer/steward" and "publisher"

TopicUTG UpdateContinuousCarol/Ted


TopicAny Other BusinessContinuousJulie

Code system development   

AdjournmentMeeting adjournedN/AJulie

Call adjourned at 20.05 UTC

Action Items

  • Reuben Daniels  create the ISCO-08 Page
  • Reuben Daniels to check with Joshua Procious to determine if we can transfer tickets from FHIR or UTG project to the HL7 JIRA project
  • 8-Jul-2020:Davera Gabriel will run with NCI Thesaurus vs NCI Meta-thesaurus matter.
  • 19-Aug-2020: Grahame's Page:Reuben Daniels  volunteered to work with Grahame, Ted, and Josh to come up with an approach to address the need for machine processing of HTA information about external code systems.
  • 19-Aug-2020: Copyright for value sets:Reuben Daniels to raise a ticket for the creation of a field to capture external code system copyright's in the FHIR ValueSet resource in compose.include 
  • No labels

1 Comment

  1. TSC has reviewed the request to include text for 3rd party content and wordsmith the provided text, resulting in the following. Upon agreement by HTA, the final text will then need to be sent to HQ for review by HL7 legal for final approval. Text the TSC suggested is:

    Please note that some external, licensed code systems content when present in an HL7 specification is subject to additional copyright from third parties' (for example proprietary assessment scale content in LOINC, and/or language translation copyright), the use of which must comply with the applicable terms of use from the third party. For further information and for details of how implementers should manage use of additional party content (including license obligations) please see the copyright information provided by the code system authority.