Teleconference 2020-08-19

This is a reminder ** Not requiring further discussion

HL7’s Virtual Plenary & Working Group Meeting from September 21-25

Currently scheduled (via the Doodle website):

• HTA (Open) Tuesday 22 September - two "slots" between 19.00-23.00 BST (I think); we can choose when to meet within that range; will aim for 19.00-21:00 BST (14.00-16.00 EST)
• HTA with Vocab Wednesday 23 September - two slots 2-3pm EST - focus on UTG and 3-4pm EST 

Tripartite HTA-Vocab-FHIR-I - to check/confirm 6-8pm EST Thursday 24 September (not required for Europeans to attend since it is at midnight)

Topics to include

• • Code System Maintenance
  • When is a code system not a code system
  • Managing externally sourced artefacts in UTG

No new PSS currently

Carol and Suzy Roy 

1) DICOM 

2) NCI-Thesaurus (https://confluence.hl7.org/display/TA/National+Cancer+Institute+-+Thesaurus)

• 19-Aug-2020:
  • Rob pointed out that the URL includes an extension (.owl) and questioned whether the could persuade them to drop the .owl extension.
    • Reuben pointed out that Vocabulary has a page with guidance around URLs on this: https://confluence.hl7.org/display/VOC/Proposed+Vocabulary+WG+Policy+on+Creation+of+Canonical+URLs+for+UTG+Code+Systems
  • Devera pointed out that there may be implementation guidance which states the same OID for the thesaurus and metathesaurus.

3) LOINC

• 19-Aug-2020:
  • Meeting between HL7 and LOINC
    • Rob H and Reuben met with LOINC (Swapna and others) on Tuesday, 17 August 2020.
    • Parties agreed to short and long term goals in relation to the Using LOINC with FHIR page – http://build.fhir.org/loinc.html.
    • LOINC wants to get the copyright statement and other items fixed – Rob is working on this now. 
  • Grahame's page on copyrights
    • Julie queried why a page is required when copyright information is available from the HTA. Grahame responded that his page will be observational and track changes across the core and all implementation guides which is not supported by current tooling. This is a new QA this to ensure HTA conformance.
    • Roel queried whether a link to the HTA pages could be supported. Grahame said he could, but these are not machine processable. Reuben suggested that UTG may provide a solution if the NamingSystem and CodeSystems for external code systems in UTG could be tagged as endorsed by the HTA. Grahame suggested that another approach might be to export the HTA confluence page to a JSON file which Grahame's tooling could process.
    • Reuben volunteered to work with Grahame, Ted, and Josh to come up with an approach to address the need for machine processing.
  • Grahame demonstrated the IG build's generation of HTA analysis with the build of USCore: http://build.fhir.org/ig/HL7/US-Core/qa-hta.html.
    • The tool displays all the non-HL7 code systems used and evaluated copyright statements in value sets used.
    • Reuben commented that HL7 policy needs to address the expectations and requirements for including copyright statements in value sets in HL7 standards and implementations.
      • Julie suggested that this should be discussed at the Vocabulary and HTA joint. Grahame was invited to attend the joint HTA/Vocab/FHIR-I meeting at the virtual September 2020. 
    • Rob M queried the cardinality of copyright in value set and suggested this could be a way to resolve this. Reuben responded that it is 0..1. 
    • Reuben called out that we need consider to copyright of the value set as separate to the copyright of the external code systems it uses.
    • Grahame suggested an extension could be used on the include itself. Rob M and Reuben agreed this is a good approach and Reuben suggested it might be core field given its importance. Grahame said a ticket could be raised suggesting the change and indicated an extension would typically be the way to start and then move it into the core resource. Reuben agreed to raise a ticket.
    • Grahame pointed out that licensing on the HTA page does not differentiate between the copyright of the code system and the copyright of the use of the system. Rob M queried for an example and Grahame agreed to provide one.