Web Meeting Info:
Join Zoom Meeting - https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09 | Meeting ID: 718 380 6281 P: 370553
+1 646 558 8656 US (New York) | Find your local number: https://zoom.us/u/aciVC9RrJ6
- Review policy page
What to review
|VSD-P progress||Carmela, Marc, Jess and Carol completed their QA based on rows in the Resource Grid. All changes were reviewed on March 9. Marc will be making the changes.|
Monday Code System Identifier & UTG series ending
Code System Identifier Monday 6 PM EDT series ending today. CC to continue the series. Will start from workflow diagram, and use that to develop the following materials.
|NCPDP Code System Issue|
Check on action item below: Any other steps to take? DONE/Resolved. IG authors agreed to change the url.
Did anyone enter a ticket into UTG for the issue with value set v2-0895? Not in THO, Present on Admission. Minutes from last week below:
No ticket has been entered. This is for Rob M. who will follow through.
There is a value set v2-0895, that declares a CodeSystem version.
The CodeSystem content for https://terminology.hl7.org/2.1.0/ValueSet-v2-0895.json.html doesn't seem to be in THO. Only the most recent version of a CodeSystem is in the build.
The ValueSet CLD references the previous version of the CodeSystem. To make thinks interesting, the CodeSystem name also changed. A ValueSet that used the previous version of the CodeSystem wasn't updated. PresentOnAdmission
RM: somehow through NamingSystem document this convoluted scenario.
We reviewed and confirmed existing policies.
Review and define plan
New JIRA project
(did not get to this topic)
|Rob M.||Clarify how to set up the JIRA project for existing standards|
FSH for NamingSystem & CodeSystem
https://fshschool.org/FSHOnline/#/share/38aggbG NamingSystem template
https://fshschool.org/FSHOnline/#/share/2O5MJsG CodeSystem template
There is no documentation to help someone attach to a UTG ticket to establish a NamingSystem. How can we help people do this quickly. To move forward, we cannot wait for a perfect tool. We quickly looked at ontoserver UI to create CodeSystems.
Did not discuss
|From LM email|
R5 draft deadline is in 16 days. Vocab needs to think about how to prioritize the work to be done.
Must be clean and ready for QA by March 30.
ConceptMap is priority #1. The FHIR tracker call on 3/11/2021 focused on ConceptMap as will the one on 3/25.
https://gist.github.com/lawley/3a59cf669d29a6d62e2948bc51e101a3 Consolidated information from Michael Lawley
https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=12101 Vocab dashboard (CC confirmed tickets in Michael's document are on dashboard)
Using Codes / Selecting a Code System Identifier Text Review
did not discuss
Co-chair review of this text:
Confirm so ticket can be applied.
Decided to talk about this at the 6 pm meeting.
3/1/2021 update: The identifier meeting attendees clarified the target audience for the materials we are creating.
Decided to focus first on getting the diagram up to date - which is for an IG author audience.
Note: the Monday 6 pm ET discussions have been specific to the URL - for use in FHIR. There are other identifiers for the other HL7 product families. This should be managed through UTG. Not only identifiers, but different metadata across the product families. Example?
Once the HTA material is in HTA, the problem will be less. TOOLING REQUIREMENTS - create OIDs for every FHIR terminology
Code System Identifier Deprecation
Did not discuss on 3/15
Discussion from 2/08. 3/15 note: this is now a "to do" item on the policy page
Action item from 2/1: compare/merge material from WGM Policy for terminology in FHIR IGs and the Vocab material during the Task Force call today. Done.
2/15/2021 Update: Vocab needs to define a deprecated identifier policy - the addition of a new publication status code is great, but doesn't solve everything. There is an immediate need to document how to work with the R4 definition before we get to R5. Based on last discussions, implementations can't distinguish between inactive and deprecated by looking at the effective period. TK will update the ticket with his thoughts on this issue. Unfortunately we are time limited. This was pushed to R5.
Governance: (still need a policy)
Deprecated status takes precedence over the validity period.
How to detect deprecated identifiers
Chance for mis-interpretation? Adding deprecated to the status value set does not help the NamingSystem identifier deprecated issue.
Ran out of time.
|External code systems - Canada|
Did not discuss on 3/8
Discussion from 2/15: Note from 3/15 - this is now on the policy page as a "to do"
Rob H: get the proposed text integrated into the FHIR specification (in the CI build), and review in context.
We reviewed FHIR-29968 and did not get to the point where we have a text block to propose for the R5 build.
This was discussed at length during Q5 Tuesday during the WGM. Jan 2021 - HL7 WGM - Tuesday Q5 Minutes
See discussion notes from previous co-chair call: 2021-01-18 Vocab Chair Agenda/Minutes
Should we also review the definition of preferred binding strength?
How to distinguish between extensible and preferred?
Did not discuss on 3/15
This is encapsulated in one of the policy statements yet to be defined - in the lower priority section.
Supporting C-CDA FHIR IG
Did not discuss on 3/15
|From WGM. How does C-CDA address terminology quality now that Term Info cannot be referenced?|
- Rob McClureStraighten out PresentOnAdmission