Date/Time:
Tuesday 9:00-10:00PM UTC
Tuesday 4:00-5:00PM USA ET
Wednesday 7:00-8:00AM AEST
Wednesday10:00-11:00AM NZDT
Zoom link - https://hl7-org.zoom.us/j/98197487889?pwd=VVNrNHBoUkJ3dE8xSDdFUTIzWkl5Zz09
Find your local number: https://hl7-org.zoom.us/u/acRd6FlL2a
Attendees
Attendee type: M - TSMG Member O -Observer / Guest | Attendance: P - present A - Apologies X - (Apologies with Proxy) | Name | Affiliation |
|---|
| M (Co-Chair) | P | | Saludax |
| M | P | | Apelon, Inc. |
| M |
| | MaxMD |
| M | P | | National Institute of Standards and Technology (NIST) |
| M (CSDO) |
| | HL7 International |
| O |
| | HL7 Germany |
| O | P | | Klein Consulting |
| O | P | | HL7 International |
| O | P | | Canada Health Infoway |
| O |
| | National Library of Medicine |
| O | P | | MITRE |
Antitrust statement
Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).
Minutes Approved as Presented
Agenda Topics
Meeting was recorded
Agenda Outline | Time Allocation | Lead | Agenda Item |
|---|
| Management | 5 | JB | - Rollcall & Proxies
- Note that meetings are recorded
- Approval of meeting minutes
|
| Administration | 5 | JB | - Started page for collection of existing material related to this subcommittee, open to suggestions on organization
- To be scheduled: Separate session to go through UTG process with those interested (and record)
|
| UTG Questions | 10 | JB | - When adding a new code system or value system to THO, when and how does the THO url get created?
- Create url in proposal (as early in process as possible)
- Must do due diligence to ensure id isn't already being used
- Note: With the url, the last part of the url will be identical to the last part of the file name. <url value="http://terminology.hl7.org/CodeSystem/audit-entity-type"/> and CodeSystem-audit-entity-type.xml for example. Url must end in id value as well.
- Confusion around UTG Editor in documentation
- Working to remove these images/references ASAP
- Question about generating OIDs using OID Generation
- Ask Ted Klein how the OID generation works and how it prevents conflicts with the 'official' HL7 OID registry
- How do we want to instruct people to use this? All the time?
- Need to update documentation on the OID Generation page to describe better how to use it, and how it differs from OID registry
|
| Status | 10 | JB | - Working on UTG Task Force recommendations
- Sprint 2 of UTG Jira development items is in progress, focusing on release tracking
- Jess and Ted reworking requirements after discussion today and will follow up
- Funding secured to help with automating some of the Jira workflow steps
- Ted meeting with new resource, Lawrence, to determine areas that can be automated to ease burden on submitters
- Defining requirements for a web-based UTG Editor
- THO work in progress
- List all resources by <title>
- Add Identifier Systems from FHIR to THO
- Confirmed that we will start moving these over as a Pro Forma change
- Review HTA queue and content in THO to find them all
- Handle external content in "All Code Systems" tab
- Removing all instructions and screenshots related to previous UTG editing tools
- Major sections already removed
|
| Subcommittee Work in Progress | 40 | JB | - Request for THO v3.1.0
- There has been some mention of a need to publish a new release of THO to support the ballot cycle
- Still determining if Implementation Guides can be published against the continuous integration (CI) build or if it must be a published release
- Tickets queued for the next release tracked here: Published in THO version 3.1.0
- Do we want to proceed with requesting a new release on tomorrow's call?
- Wayne wanted a release before the next ballot cycle and also so Marc can learn how to do one
- RD: Need to prioritize things being removed from R5 such as Identifiers Systems, "Using X with FHIR" etc, and would like to see these get into THO before freeze
- TSMG may want to discuss timing with FMG
- Not a lot of time to get crucial changes in prior to Ted's leave must freeze no later than 2/20 (anything not implemented in CI build will not get in)
- Discuss this on TSMG main call tomorrow, 2/2 to land on a decision
- Task force recommendation review and implementation (voting, quorums, WG health, etc.): UTG Task Force Recommendations to TSC
- Tracked by
HSCR-155
-
Getting issue details...
STATUS
and its subtasks
- Feedback from Product Management session at WGM
- Qualifications might be too high of a bar
- Pool of qualified candidates is limited enough already
- The tooling isn't user friendly enough ("have to be a programmer")
- "Terminology is not approachable"
- Next Steps
- Move forward with plan to request that Management Groups provide at least one person to be part of an OSG for the Product Family OSGs
- Consider allowing nomination of participants that are not co-chairs
- Based on community feedback, we will adjust to what the community can provide
- Also request that WGs provide someone willing to learn this process (as an apprenticeship-like role) so that we can bring them up to speed with the help of the appropriate methodology groups
- Ask Rob and Peter for help recruiting for Realm-Based OSG
- Ask TSMG main call for Vocab/TSMG members for the Vocab OSG
- TSC clarification
- Need to ask for clarification for ad hoc OSGs (separate request) and how OSGs may change but membership does not automatically refresh on tickets already in Consensus Review
- Expectations for when members of an OSG need to change
|
| Adjournment | 0 | JB | Call adjourned at 5:00PM EST. Next call in one week at 4:00PM EST February 8, 2022. |
Supporting Documents
Tasks
