Chair: @Julie James
Scribe: @Julie James
H - HTA Member
O - observer
L - liaison
P - present
A - Apologies
Global eHealth Collaborative
American Dental Association
Blue Wave Informatics LLP
|H||P||Susan Matney||Intermountain Health|
|H||A||Sylvia Thun||HL7 Germany|
Minutes of TC 2019-03-14 Approval as on Confluence
This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."
Meeting Minutes from Discussion
|Topic||Characteristics of Realm Transferable Standards Specifications|
HTA will be mentioned on the PSS as interested parties so we will be consulted as the project progresses.
|Topic||HL7 Terminology Portal|
Next two code systems to be worked on
JMJ to get a template page and which we can fill out for the remaining code systems
Why are we providing this information? To provide an inventory of correct "standard" information for code systems that may be used in HL7 specifications/health information exchange. There is a technical need for this - for example providing the OIDs and URLs for code systems.
On the governance side, should we be recommending particularly code systems for use? Maybe a star system (5 stars - great....)?
RB: DICOM, SM: Nursing, JMJ: EDQM, MedDRA, ATC etc.
|Topic||New S-I Collaboration Agreement - to be carried forward to next meeting|
Review of the agreement; any changes to be made
|Topic||Publication of HTA Policies|
See HTA Policy Pages HTA Process and Policy Documents
Email sent to Austin Kreisler, TSC Chair, to inform all co-chairs
Julie will attend a TSC TC to present the HTA document "General policy on the use of external code systems"
We have received comments from SGB related to the "Publication of Policy on Retired or Legacy HL7 Code Systems". Julie will need to attend the SGB with Carol M (Vocab co-chair) to "defend" the document. Note that the issue of legacy HL7 code systems came to HTA first from the community, and has an impact on external code systems since these are the best source of domain specific code systems.
RMcC: Vocab WG is focused on "technology" and not governance of good terminology practice within HL7 standards; e.g. expectations of how to identify versions of value sets and code systems (tactical). Domain experts have to decide content to use in specifications. Policy statements are not what Vocab has tended to do.
The HL7 Community view HTA as the body that should set policy and governance for "terminology", not just external terminology as currently stated in the GOM and brings things such as the legacy code system issue to HTA (rather than Vocab). SGB and TSC and ultimately the HL7 Board need to be clear as to good terminology practice and who has general terminology policy and governance responsibility within HL7 and make sure that whoever they say has it, actions it.
Julie also to reach out to Carol in advance of the meeting with SGB.
|Topic||HTA Confluence Site|
Continuing the site clean-up and removing duplicate information.
Should not have any Word documents; have all information as Confluence pages. Folk can download the content of a Confluence page as a Word document if they need to for any reason.
Europe changes to summer time this weekend. This means that HTA calls will now be back to 4pm EST; 10pm/9pm will stay in Europe/UK.
Adjourned at 22.02 UTC.