90 likes | 263 Views
HL7 CTO Report to the TSC. John Quinn January 14, 2012. HL7 Tooling. We have an offer from Sparx Systems where they will fund ($4K) a contest around UML modeling and tooling. The tooling work group was contacted and asked to create suggestions on a objective for the contest.
E N D
HL7 CTO Report to the TSC John Quinn January 14, 2012
HL7 Tooling • We have an offer from Sparx Systems where they will fund ($4K) a contest around UML modeling and tooling. • The tooling work group was contacted and asked to create suggestions on a objective for the contest. • As of today we don’t have a final suggestion whose scope reasonably fits the money promised.
HL7 Tooling • At this time I intend to propose to the general session two needs: • Recommendations for a tooling-based contest objective that will be announced one month after the San Antonio Meeting.
HL7 Tooling • Instructions/Suggestions from the Tooling Wiki*: • The Model Interchange Format is organized as a set of XML Schema files that describe the key metadata to express published standards. The MIF is used to transform the approved models as serialized XML files. The MIF was designed to meet the requirements of the V3 Methodology to express concepts that could not be expressed in XMI. • Requirements for MIF[1] • The following ideas were proposed - we haven't decided which of these ideas will be proposed, although we have concluded that the second proposal should be postponed as it is dependent on the first idea. • Produce a UML Profile for MIF Static Models - This is a task so that other modeling tools have a chance to be configured to understand MIF • Produce a MIF to XMI XML transform consistent with an updated UML Profile - This task is dependent on the completion of task 1. • Produce a viewer that can browse MIF schemas (Meta level)- this task makes it easier to understand the relationship among the MIF files and their elements. • Produce a viewer that can browse MIF based models (model level)- this task makes it easier to understand the serialized models expressed in MIF XML. • Produce a viewer that can browse instances from MIF based models (instance level) - this task makes it easier to evaluate instances based on serialized MIF models.(there is some work that already exists) * http://wiki.hl7.org/index.php?title=HL7_Tooling_Challenge
HL7 Tooling • We need more: • Tool-smiths (i.e., people who write code); • Requirements Documenters; • Test Case Developers; • Tool Testers. • We are down to about four full-time-equivalent participants in the Tooling WG and the HL7 organization needs work done in tooling. • Some funds have been allocated in the HL7 2012 Budget to provide compensation for “approved” tooling development and maintenance activities.
Clinical Information Modeling Initiative (CIMI) • A non-HL7 activity that has met four times • HL7 meetings in Orlando (5/11), San Diego (9/11) and San Antonio (1/12) and London UK (12/11). • Group is a derived activity from the “Fresh Look Initiatives Report” chaired by Stan Huff. • About Forty individuals participated in San Antonio (1/12,13 & 14).
CIMI • HL7 • CDISC • IHTSDO • ISO TC 215 • Singapore MOH • Australia NEHTA • UK NHS • Canada Health Infoway • Sweden • NICITZ (Dutch National ICT Institute for Healthcare ) • 13606 Organization • Kaiser Permanente • Mayo Foundation • Intermountain Healthcare • US DOD • US VA • US ONC • Mitre Corporation • others
SAIF Canonical Definition* • Continue progress at making HL7 SOA “Services Aware”: The ArB passed a significant milestone when it completed a balloted version of the Services Aware Interoperability Framework (SAIF) Canonical Definition. The TSC now continues in its project to determine a standardized approach to the adoption of SAIF into our products so that they are all “services aware” and have a common approach for using HL7 in a Services Oriented Architecture where interoperability can be achieved through software callable services.*From annual report
Product Brief Release* • Product Documentation: Over this last year we initiated and completed a project to inventory all of our products, create and publish standardized documentation on these products and create a mechanism to maintain this documentation. This was completed in 2011 as a foundational first step to support a formal strategic product strategy. We analyzed over 100 independent balloted pieces of HL7 that are in current publication as HL7 Standards, created a standard format for describing them, identified the current responsible work group for each one and then allowed time for these work groups to review and suggest corrections and changes to them. As a 25 year member of HL7 I can attest that this is the first time that this has been done since HL7’s inception in 1987.*From annual report