1 / 34

Strategic Initiative Thoughts

Transformation - Transparency - Teamwork. Strategic Initiative Thoughts. SITF members Hans Buitendijk, Liora Alschuler, Ken McCaslin, Klaus Veil, Dan Russler 14 September 2006. Where did we come from?. Drivers: Recognized need to improve/accelerate standards development

millie
Download Presentation

Strategic Initiative Thoughts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transformation - Transparency - Teamwork Strategic InitiativeThoughts SITF members Hans Buitendijk, Liora Alschuler, Ken McCaslin, Klaus Veil, Dan Russler 14 September 2006

  2. Where did we come from? • Drivers: • Recognized need to improve/accelerate standards development • A burgeoning organizational structure • Responsiveness to volunteers/stakeholder/PIC concerns • Request to the Board to “do something” • Initially leading to formation of the Organizational Review Committee (ORC) • Established January 2004 • Broad representation • Identified key issues and recommendations • Robert Wood Johnson Foundation expressed interest to explore ways to accelerate the standards development process • Discussions started early 2005 • Yielded a unique opportunity to gain new perspective on organization and process with dedicated focus

  3. Strategic Initiative TaskForce • Strategic Initiative Taskforce • Kickoff – August 2005 • Multi-national, multi-faceted group of HL7 members, staff, and consulting team • Objectives • Create a strategy/plan to restructure the organization to: • Establish and meet long term strategic objectives • Support role as global/international SDO while addressing concerns of national affiliates • Develop standards more efficiently and expeditiously • Deliverable by May 2006 WGM

  4. A Very Basic Premise • Optimize the effectiveness of our core resource: the volunteers • Maintain culture of volunteerism • Global participation • Document institutional process • Identify new sources of volunteers • Support: Comprehensive toolkit • Support: Professional/HQ staff • Support: e-Working • Support: Organization/Governance

  5. Problems & Solutions

  6. Problems & Solutions

  7. Problems & Solutions

  8. Problems & Solutions

  9. Transition Planning • Board of Directors met August 2006 • Developed transition strategy • Start to identify transition team(s) • Assigned major task areas: • Structure/Organization/Governance • Product Life Cycle/Project Management • Product & Services Strategy • Communication/Branding • Funding/Revenue Sources • Volunteer Resources

  10. Foundation & Technologies Structure & Semantic Design Domain Experts Establish Harmonization Processes Clarify Governance Provide Project Support Modeling & Methodology Services Oriented Architecture RIM Java Arden Syntax Conformance Infrastructure & Messaging CCOW XML Vocabulary Tools Security Electronic Services Templates Structured Documents Orders and Observations Publishing Personnel Management TermInfo Scheduling & Logistics Attachments Patient Administration Implementation Clinical Decision Support RCRIM Financial Management Clinical Genomics Image Integration Healthcare Devices Early Adopters Community Based Health Lab Patient Care Pharmacy Patient Safety Pediatrics Data Standards EHR Clinical Guidelines Cardiology Anesthesiology Public Health/Emergency Response Government Projects Anatomic Pathology Emergency Care

  11. Structure/Organization/Governance

  12. Role of TSC • What you will see in the SIIP Draft: • The co-chairs of the Committees and SIG’s represent the primary labor pool and will remain the core source of technical expertise and development within HL7. The Technical Steering Committee (TSC) is the primary voice and organization belonging to this core cadre of volunteers. • It will be re-invigorated by providing self-elected leadership and a voice on the TD and the Board. • ... In addition to these new powers, the TSC will adopt a new routine for meetings to facilitate communication and lessen the need for joint meetings. • Summary: • Elects own co-chairs who sit on Board of Directors • Elects 3 reps to TD • Input to slate of nominations for open election to TD • Elects 2 representatives to the Board nomination committee • Introduce more flexible meeting schedule • How is the Board responding to these recommendations?

  13. Transitional Technical Task Force • The Transitional Technical Task Force (T3F) is a forerunner of the Technical Directorate which will be brought in under the changes initiated within the 2005-2006 Strategic Initiative. • The T3F will develop an approach that will be ratified by the Technical Directorate and endorsed by the Board of Directors.

  14. T3F Tasks • Define parameters of an HL7 technical architecture including: • Relationship among HL7 technical work products including specifications, implementation guides and tools. • Relationship of those products to external products/standards • Define the relationship of these products to the HL7 Products & Services strategy. • Establish an approach to meeting new product requirements identified by the Products & Services Task Force.

  15. What can we expect? • When fully defined, the Technical Directorate will ratify this approach, with the endorsement of the Board. At that time, they will address issues/questions such as, for example: • When to create a new specification and when to constrain an existing specification? • When to use messaging and when to use a service oriented architecture? • When to use a message and when to use a document?

  16. How will the T3F be formed? • The T3F will be created at the September Plenary: • 2 members elected by the International Affiliates (Sunday) • 3 members elected by the Technical Steering Committee (Monday) • 1 member appointed by the Board (Tuesday) • The Transition Team will recommend to the Board, and the Board will approve, a method and schedule to convene the T3F, latest January, 2007

  17. Board • What you will see in the SIIP draft: • Nominations: 2 options – from membership or member-elected nominating committee • Composition • 3 elected from TSC (co-chairs) • 1 from Advisory Council • 1 Emeritus (5-year term, elected) • 1 each from 3 geo groups of Affiliates • 1 from US Affiliate • 4 directors at large • Officers: Chair, Secretary, elected by the Board • Alternate from Governance Transition Team: • Nominations: no change • Composition: “Streamlined” Board of Directors • 4 fewer Directors at large • 2 from Affiliates • Vice-chair replaces chair-elect • No HL7 Technical or vice-chair positions • How will these issues be resolved? • With recommendations by the Transition Team • By the Board • In conjunction with the CEO • Ultimately reflected in changes to Bylaws and Policies & Procedures • Member votes to adopt Bylaws • P&P is set by the Board

  18. Transition to US Affiliate/HL7 • What you’ll read in the SIIP Draft: • Affiliate or HL7 or joint membership • Financial obligations tbd • “The change will take place over a 3-year period ...” • How is the Board addressing these points: • Under discussion: • Affiliate or HL7 or joint membership • Financial obligations: developed in collaboration with Affiliates • Transition timing recommended by Transition Team, approved and adopted by Board in consultation with CEO

  19. Conclusion • Change is happening • Many aspects in play • What is known: • Board is committed to the HL7 Mission • Objective is more rapid, effective standards development • What is unknown: • Exact form, timing of transition

  20. Process & Productivity

  21. Objectives • HL7 will implement a product-oriented project management approach to ensure development of high-quality standards and associated products in a committed timeframe. • All standards will undergo quality testing at key stages of the development process.

  22. Product-oriented Project Management Approach

  23. Product-oriented Project Management Product Sunset

  24. Next Steps • Seek your comments on Product Oriented Project Management Approach • Peer Review and source document will be posted on the HL7 Website under Strategic Initiatives • Email responses to transition@hl7.org by 11/01/2006

  25. Volunteers

  26. Volunteers • The HL7 work is done by volunteers ... • ... but many are "volun-tolds" (eg. their contribution is driven by their organisation's goals) • HL7 recognises that its "workers" cannot be managed the same way as a corporation or army ... • How to "push a piece of rope"? • HL7 is listening!!! • Proposed approach: • Support, support, support ... • Motivation ... • Work management

  27. Volunteers: Support • HL7 has and will continue to increase the professional support to its volunteer workers: • Project Management Office √ • Technical Editor (in progress) • Better web-site tools for balloting √ • Better web-site tools for tele-conferences √ • Better web-site for collaboration (Wiki) • Better V3 tooling (Manager & Collaborative √) • Also: • Free WiFi, First-timer Education, Co-chair Training, e-Learning, nice locations, …

  28. Volunteers: Motivation • Volunteer Recognition: • "Volunteer of the Year" √ • Co-Chair recognition • Recognition of other functions: Facilitators, Editors, TC/SIG "Secretaries", etc. • Volunteer Recruitment: • Outline professional benefits of participation • Outline different “jobs” within HL7 • Outline skills-enhancement of working in HL7

  29. Volunteers: Work Management • Project Management: • Overview/information, NOT control/pressure • Project Management Office √ • Project Reporting System (in progress) • New Projects: • ... Require sufficient resources • ... Require commitment • … Have sunset mechanisms

  30. Wrap-Up

  31. Execution: Current • Hiring Technical Editor • Investing in Tooling • Contracting for Web-site • Contracting for e-learning • Contracting project tooling

  32. Execution: Next Step • Convene Transitional Technical Task Force • Enhance TSC Org Structure • Refine design of Technical Directorate

  33. Management & Coordination • Hire CEO • Create Product line management • Improve Marketing Message • Prioritize

  34. Strategic InitiativesA renewed HL7 on the horizon Thank you for your attention. QUESTIONS?

More Related