Download presentation
Presentation is loading. Please wait.
Published byTrevor Harrington Modified over 9 years ago
1
HL7 Tooling Collaborative Richard Kavanagh CFH – Development Manager HTC – Project Directorate Lead
2
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
3
HL7 Tooling Background The majority of HL7 tooling has been developed as a result of volunteer contribution. Tools developed to date have been instrumental in progressing the HL7 standards.
4
HL7 Tooling Background However, Tooling is developed by a small number of key volunteers. Enhancements are often slow and prone to delays. Many tooling components do not share a common architecture. Difficult for tools to be developed in a distributed environment.
5
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
6
CFH Tooling Background The CFH perspective.. Core model design tool branched from main HL7 tool a number of years ago. Recent changes to the tool were slow and problematic. Training to avoid tooling “quirks” was significant. Recent changes have increased quality and productivity.
7
CFH Tooling Background UK version of model design tool. MIFs not HMDs. Long slow development. Renders a “tabular view” from MIF.
8
CFH Tooling Background Annotations editor Annotations persisted in the MIF file. Bulk Text Insertion tool. Increased efficiency Increased consistency.
9
HL7 Tooling Background The CFH perspective.. The cost of development is high. Further tooling requirements are equally beneficial to other HL7 users. A pooling of resource would provide a more cost effective means of developing tooling. Desire to converge with main HL7 tools. A “Tooling Collaborative” is required to maximise the investment made in tooling.
10
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
11
HTC Evolution Timeline Dec. 2005 - NHS CFH and HL7 UK host a workshop to gauge the level of UK interest in collaborative tools development. Outcome - the formation of the NHS CFH Tooling Steering Group. Mar. 2006 - the Tooling Steering Group finishes its task and releases business case, project structure and requirements architecture documents for V3 tools development collaboration. The NHS Technology Board approves NHS CFH to lead the formation of a tooling collaborative as described in the documents. May 2006 - the HL7 Board approves their participation in the collaborative and names their representative. June 2006 - the first meeting of the HTC Executive. Aug. 2006 - release of the first RFP. Sep. 2006 - the second meeting of the HTC Executive. Jan 2007 – release of the first HTC tools.
12
HTC Executive Members – October 2006
13
HTC Overview HTC Organisational Structure. Executive Board -One voting representative per member. -One chair (non voting) -“Closed” meetings. -Main meetings at WGMs. -Financial commitment.
14
HTC Overview HTC Organisational Structure. Project Directorate -A Project Directorate Lead. -A Chief Technical Officer appointed by the Eclipse Foundation. -An HL7 Architect appointed by HL7, Inc. -A User Requirements Lead -A technical architect or project management representative of any Executive Board member organisation (optionally)
15
HTC Overview HTC Organisational Structure. Project Directorate (continued ) -Meetings are “open” -Weekly conference calls. -Face to Face meeting at WGMs
16
HTC – Executive Board The EB is expected to ensure that: Ensure that the HTC meets the high-priority requirements of its user community. Ensure the Project Directorate and Sub-Project resources are available as required.
17
HTC – Executive Board The EB has the following responsibilities: Provide the leadership and vision to produce the Roadmap of the Project's overall direction, priorities and deliverables. Approve Sub-Projects, including their licensing approaches and governance arrangements. Approve the deliverables from Sub-Projects. Coordinate relationships with other Eclipse Foundation Projects
18
HTC – Executive Board Current Executive Board membership : Laura Sato ( Chair ) Jane Curry ( HL7 Liaison ) Skip McGaughey ( Eclipse ) Nancy Orvis( DoD ) Brian Barry ( Intel ) Ken Lunn ( CFH ) Andy van Heusen ( Quicksilva ) Chris Chute ( Mayo Clinic ) Grant Gillis ( Canada Health Infoway )
19
HTC – Project Directorate The PD is expected to ensure that All HTC technical documents and reports are produced as needed and are publicly available. All Sub-Projects operate effectively. All Sub-Project plans, technical documents and reports are publicly available
20
HTC – Project Directorate The PD has the following responsibilities: Ensure that overarching HTC as well as Sub- Project plans are produced. Work with the Eclipse Foundation to establish the development processes and infrastructure needed for the development team to be effective. Recommend new Sub-Projects to the EB. Recommend Sub-Project deliverables for approval by the EB.
21
HTC – Project Directorate The PD has the following responsibilities (continued) Recommend the initial set of Sub-Project committers for each new Sub-Project. Help to ensure that the Sub-Projects have enough contributors, and work to fill vacancies. Produce the HTC Schedule and Technical Policies documents.
22
HTC – Project Directorate Current Project Directorate membership : PD Lead - Richard Kavanagh HL7 Architect- Lloyd McKenzie CTO- Brian Barry User Requirements Lead - Vacancy US DoD- Geoff Roberts. HL7 Model Designer- Jiva Medical
23
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
24
HTC – Roadmap Vision “ The HL7 Tooling Collaborative has been established with resource contributions from key HL7 stakeholders, to deliver significant benefits within 1 year of the project's initiation.”
25
Business Requirements Modeller tools Terminology Management tools HL7 Model Designer Schema Generator Code Generator Frameworks Example & Test Message Generator Message Tester Design Analysis toolsArtefact Configuration Management tool Shared Artefact Repository
26
HTC – Roadmap Vision Completed tools by end of Year 1: Infrastructure components Shared artefact repository Business requirements modeller HL7 Model Designer Schema generator Example instance generator
27
HTC – Roadmap Vision Completed tools by end of Year 2: Terminology tools Design analysis tools Message testers Code generator frameworks
28
HTC – Roadmap Vision Licensing of HTC Tools Wherever possible HTC products will use the “Eclipse Open License”. Other models can be used at the discretion of the Executive Board.
29
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
30
HL7 Model Designer RFP Issued Sept’06 – 2 responses received. Progression based on response received from Jiva Medical. Grahame Grieve – Sub-Project Lead. Phased functionality release, to match current resource availability. PID including, scope and timelines to be published in next two weeks. First phase deliverables at Jan’07 WGM.
31
Shared Artefact Repository Geoff Roberts – Sub-Project Lead, Requirements gathering underway. PID including, scope and timelines to be published by end of November. Seeking development resource contributions from Intel.
32
Project Directorate Artefacts Deliverables for the Jan’07 WGM Roadmap delivery plan for Jan’07 WGM. HTC Technical Policies & Architecture document. “How to get involved” guidelines.
33
Agenda HL7 Tooling Background CFH Tooling History HL7 Tooling Collaborative Overview HL7 Tooling Collaborative Roadmap Current Projects The Future
34
HTC – The Future. More members required to ensure we meet all of the HL7 community needs. More funds required – actively being pursued. A commitment for delivery to ensure benefit is realised early. Stimulate growth through Open Source development.
35
HTC – The Future. Can it work ? Will it deliver ? It already has. ( in a fashion )
36
Eclipse – XML Instance Editor
37
XML Instance Editor Project initiated prior to formation of the HTC. Used as a project to test the viability of Eclipse for tooling developments. Project delivered by Jiva Medical. CFH donation to the HTC at Jan’07 WGM
38
Business Requirements Modeller tools Terminology Management tools HL7 Model Designer Schema Generator Code Generator Frameworks Example & Test Message Generator Message Tester Design Analysis toolsArtefact Configuration Management tool Shared Artefact Repository
39
HTC – The Future. Get Involved and shape the tools of tomorrow. Executive Membership Laura.Sato@nhs.net Project Directorate Richard.Kavanagh@nhs.net Website Http://HL7ToolingCollaborative.org
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.