Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda Outline

Agenda Item

StatusLead

Meeting Minutes from Discussion

Management

Quorum

Minutes Approval

N/AJulie

Quorum is met

Motion to approve Minutes proposed

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

TopicNew PSSContinuousJulie

No new PSS; need to get Terminology on the PSS/NIB process formally

TopicExternal SDO Issues or additional topicsContinuous

Carol

Confirm wording for the third party copyright statement for LOINC

On HTA page, will note that there is third party copyright and put the link to the LOINC page - done (Julie)

TK: Terminology@HL7.org as the single repository for external terminology might need to a general/introductory verbiage which includes about third party copyright 

TODO: Change proposal (R2 will freeze in 1-2 weeks) Caroline Macumber Julie James Reuben Daniels

  • Rob McClure presented content from LOINC in relation to third party copyright.
  • Julie James noted there was concern around individuals using LOINC in apps / messaging in FHIR.
  • Rob McClure if you use an app to administer the survey instrument you need to go to the IP owner because you're administering the survey – HTA's approach should be the same: if you implement you need to talk to the people who own the IP.
  • Caroline Macumber noted that some of the content is subject to third party copyright. We should craft a general statement for use by FHIR.
  • Sylvia Thunnoted you may need to mention additional parties who do translation i.e. fourth party translations. Rob McClure noted his understanding of LOINC is that they have agreed those who have put in the copyright statement have agreed to the HTA's approach. Caroline Macumber noted there may be additional copyright requirements that are met.
  • Rob McClure we should come up with 
TopicHL7 Terminology Single Repository and Supporting ProcessOngoingReuben

"Vocab, FHIR-I and HTA recommend that HL7 create a single maintained authoritative repository of information about external code systems and their use (e.g., copyright and identifiers) in HL7 artifacts at terminology.hl7.org. The authority for changes to the repository content rests solely with HTA. Inclusion of external code system code content will follow HTA processes.

Usage in HL7 artifacts specific to product families will reside where product family management deem them to reside. "

Motion approved at the final meeting of Vocab/FHIR-I and HTA

Need to take this to TSC (Austin/Anne W) Reuben Danielswith Rob McClure -1) get this onto TSC Agenda 2) Speak to this to TSC

Also need to consider the "rapid processing" infrastructure and be ready to implement this

TopicEDBA ContentNewJulie - Jim McClay from ECWGEmergency Department Benchmarking Alliance (EDBA)  https://doi.org/10.1111/acem.13978
TopicHTA Content Pages ReviewContinuousReuben

HTA_External_Terminologies-Information_Findings-20200916-1.pdf

Raw data is available; will generate a specific Confluence page for this Reuben Daniels

Topic

External Code Systems 


ContinuousSusan

2) Canonical URLs for nursing classifications ICF, ICNP, LEP, ENP, CCC

JIRA: 

Jira
serverJira
serverId9b965702-34a7-3433-bf10-7f66fd69238c
keyFHIR-25263

Zulip: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/canonicals.20for.20classifications.20of.20nursing.20interventions

The ICNP terminology is being incorporated into SNOMED and it is not clear how/whether ICNP will continue to be maintained as a separate terminology; a subset of ICNP is currently part of GPS.  Susan will follow up for ICNP and also CCC.

Sylvia to follow up on ICF - rehabilitation etc.https://apps.who.int/classifications/icfbrowser/Default.aspx (browser link) and LEP - https://www.lep.ch/de/

ENP Page set up; only some content present to date

TopicUTG UpdateContinuousCarol/Ted
TopicRapid Processing for Code SystemsNewMary Kay

Needs to implement the "rapid processing" for code system stubs.  

TK & RD have started laying out the process - starting with new content and working onward.  MK can be included in that too - once the scenarios and pathways are drafted.

CM: surely what MK needs is for us to get the CS metadata and get those stubs in.  HTA owns the relationship with the requestor; we put the request in using the tools and when the artefacts are ready we notify the requestor.

MK: Review the HTA External CS pages on Confluence....Identify all the code systems.  If we have all the information correct, it's OK.  If it's not correct, tell us what we need to change.  If the CS is not there, give us the data we will get it added.  MK to send the spreadsheet with the CS list to Reuben/Julie/Carol

TopicAny Other BusinessContinuousJulie
AdjournmentMeeting adjournedN/AJulie

Call adjourned at xx.xx BST

...