Administrative | 5m0m | JB | - Rollcall & Proxies
- Note that meetings are recorded
- Agenda check
|
Scope | 10m0m | JB | Purpose of call is to review open tickets in the UTG Jira project (UP), specifically tickets in the following states: - Consensus Review
- Waiting For Input
- Proposal Draft
- Environment Setup
|
V2 Example Code Systems | 10m | MF | - There are code systems in V2 that V2MG feels should never be used for a value set
- How do we indicate it should never be used in an implementation?
- CodeSystem.experimental = true could be an option, but depends how validation tooling flags it
- May have been removed from Chapter 2C but there are references to things that may have been removed
- We still need something for them so that they resolve, even if removed from 2C
- Needs additional discussion and investigation
|
Follow-up on THO vs. FHIR discussion | 15m | JB | - Discussed with Grahame on TSMG main call, 7/25
- Need to determine the following:
- Content that exists in both THO and R5 with the same canonical URL
- Exact match on content - remove resource from R5
- Grahame modified version so that it referenced THO or FHIR based on the version, not sure logic for validation though
- If minor version is 1, it was migrated as part of 4.0 cleanup and 4.1 prep. If 3, it was part of prep for R4B, Ted saw some with minor version a 6
- All have a major version of 0 in THO due to some build hack to pull out the right thing and not give duplicate resource errors
- Versions are different - look to see if the content is different & determine which content is correct - a manual review
- Content is different, do manual review to determine which is the most up to date - another manual process
- Content anchored in THO that only exists in R5
- Move to THO and remove from R5
- Check for hl7.org/fhir content in THO
- Determine handling of hl7.org/fhir value sets that reference THO anchored code systems
- Michael will take first pass at getting lists of the following
- From fhir spec, find url for all code systems and value sets anchored in terminology.hl7.org
- From THO, find url for all code systems and value sets
|
Next THO release | 5m | JB | - Jess will post to Zulip on the committers thread to see if a THO release is needed prior to the R5 content deadline
|
Ticket Review | 45m30m | JB | Note that we really need to make sure new content has an OID assigned! Tickets to be reviewed this week: Jira |
---|
server | Jira |
---|
serverId | 9b965702-34a7-3433-bf10-7f66fd69238c |
---|
key | UP-312 |
---|
| - tagged Corey to ensure he saw response Jira |
---|
server | Jira |
---|
serverId | 9b965702-34a7-3433-bf10-7f66fd69238c |
---|
key | UP-280 |
---|
| - tagged voters to review and vote Jira |
---|
server | Jira |
---|
serverId | 9b965702-34a7-3433-bf10-7f66fd69238c |
---|
key | UP-246 |
---|
| - this one has a broken link that Marc will investigate Handling of V2 UTG tickets: - Michael will bring list of V2 related UTG tickets to V2MG for further review and potential next steps
Jira |
---|
server | Jira |
---|
jqlQuery | project = UP AND status != complete AND status != "Proposal Implemented" AND status != withdrawn AND status != cancelled AND status != "change not needed" AND "Proposal Type" = "V2 Vocabulary (including V2 Tables)" ORDER BY Status, "Proposal Type" |
---|
serverId | 9b965702-34a7-3433-bf10-7f66fd69238c |
---|
|
Open questions TSMG: - Recommend that we put together a template copyright for HL7 content (might be one that exists already for IGs/standards)
|
Adjournment | 0m | JB | Call adjourned at 5at 4:00PM34PM EDT. Next call in two weeks at 4:00PM EDT August, 9 2022. |