This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Vocabulary Tooling - 28-June-2016"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
== Agenda == | == Agenda == | ||
* Review objectives and schedule of tasks | * Review objectives and schedule of tasks | ||
| − | **Investigate suitability of FHIR vocabulary services for all HL7 product families. HL7 needs to converge its multiple silos of vocabulary maintenance tooling and persistence stores. The current VML, VMIF, MSAccess, and RoseTree tools need updates and maintenance, and we have limited ability to do this. In addition, any significant failure in these tools may cripple our ability to publish V3 ballots and the Normative Editions since we have limited ability to debug and fix the current tooling. The FHIR services and tools are actively being used, maintained, and enhanced, and it makes sense to investigate their suitability before seriously evaluating tooling outside of HL7. | + | **Investigate suitability of FHIR vocabulary services for all HL7 product families. HL7 needs to converge its multiple silos of vocabulary maintenance tooling and persistence stores. The current VML, VMIF, MSAccess, and RoseTree tools need updates and maintenance, and we have limited ability to do this. In addition, any significant failure in these tools may cripple our ability to publish V3 ballots and the Normative Editions since we have limited ability to debug and fix the current tooling. The FHIR services and tools are actively being used, maintained, and enhanced, and it makes sense to investigate their suitability before seriously evaluating tooling outside of HL7. This evaluation will serve as input into the existing Vocabulary project 947, HL7 Vocabulary Maintenance Tooling. |
| − | This evaluation will serve as input into the existing Vocabulary project 947, HL7 Vocabulary Maintenance Tooling. | ||
* Review of capabilities of current FHIR Terminology Service | * Review of capabilities of current FHIR Terminology Service | ||
Revision as of 12:57, 28 June 2016
Contents
Minutes 28-June-2016
Call to Order
Agenda Check
- No Changes
Announcements
- No announcements.
Agenda
- Review objectives and schedule of tasks
- Investigate suitability of FHIR vocabulary services for all HL7 product families. HL7 needs to converge its multiple silos of vocabulary maintenance tooling and persistence stores. The current VML, VMIF, MSAccess, and RoseTree tools need updates and maintenance, and we have limited ability to do this. In addition, any significant failure in these tools may cripple our ability to publish V3 ballots and the Normative Editions since we have limited ability to debug and fix the current tooling. The FHIR services and tools are actively being used, maintained, and enhanced, and it makes sense to investigate their suitability before seriously evaluating tooling outside of HL7. This evaluation will serve as input into the existing Vocabulary project 947, HL7 Vocabulary Maintenance Tooling.
- Review of capabilities of current FHIR Terminology Service
- Import capabilities, V2/V3/CDA
- Editing
- Change tracking
- Access (browser, etc.)
- Gap alignment between FHIR capabilities and Tooling Requirements
Tasks
- Draft of requirements -July 2016
- Updated FHIR value set editing tool - August 2016
- Initial MIF generation from FHIR resources tool - September 2016
- Draft of report with gaps - 2016 Sep WGM
- Addressing of gaps with FHIR team - Fall 2016
- Final report draft - December 2016
