Common Terminology Services - Release 2 (CTS 2)

1. Common Terminology Services - Release 2 (CTS 2) Russell Hamm Informatics Consultant Apelon, Inc. Craig Stancl Sr. Programmer / Analyst Mayo Clinic / Foundation

2. Outline • Common Terminology Services Release 2 • Healthcare Service Specification Project • CTS 2 Process Overview • Next Steps • OMG RFP • OMG Timeline

3. Common Terminology Services - Release 2 (CTS 2) • Project of the HL7 Vocabulary Workgroup • Developed under the Service Oriented Architectures (SOA) Healthcare Service Specification Project (HSSP) framework • Expand the scope of functionality (of CTS 1) to include • Administrative functions • Expanded search capability • Mapping functionality • Authoring / Maintenance

4. What is the Healthcare Service Specification Project? • A joint standards development activity occurring in multiple organizations, including Health Level 7 (HL7), the Object Management Group (OMG) • An effort to create common “service interface specifications” tractable within Health IT • Its objectives are: • To create useful, usable healthcare standards that address business functions, semantics and technologies • To complement existing work and leverage existing standards • To focus on practical needs and not perfection • To capitalize on industry talent through open community participation

5. The HSSP Process HL7 HL7 SOA WG Service Functional Model OMG OMG HDTF OMG RFP HL7 DSTU ANSI Standard RFP Responders Technical Specification Adapted from Rubin/HL7

6. Understanding HSSP Artifacts, Roles, Attributes Implementation SFM RFP Submission Owned / Produced by HL7 Community Produced / owned by OMG community Produced by OMG Member “Submitters” Owned by organizations and vendors Defines what a service does but not how Translates SFM into technical requirements Defines the service’s technical spec Builds the service that lives behind the interface Independent of technical platform ID’s supported technical platforms Defines interfaces, platform bindings, and conformance profiles Complies with a “conformance profile” Audience is tech leads, EAs, tech spec developers Audience is community with implementation interest Audience is project team architect, lead developers, etc. Audience are consumers of the system or service Adapted from Rubin/HL7

7. Current Status • The CTS 2 SFM passed ballot as DSTU in May 2009 • Comment resolution was completed in September • HL7 accepted publication of CTS 2 DSTU in October 2009 • OMG RFP issued in September 2009 • Submitter teams can now form to develop the Technical Specification for CTS 2 • Mayo obtained “Contributing” OMG membership in November 2009. • Mayo OMG Letter of Intent submitted in December 2009.

8. Next Steps • Identify interested submitters for the OMG RFP (identified by submission of letter of intent (LOI). • Coordinate a joint response team • Collaboration is the preferred model • Develop Platform Independent Model (PIM) and Platform Specific Model (PSM) for CTS 2 • Submit feedback to HL7 for Normative CTS 2 standard

9. OMG Timetable 9

10. Resources • CTS • www.hl7.org • CTS 2 SFM • http://www.hl7.org/documentcenter/ballots/2009may/downloads/V3_CTS_R2_DSTU_2009OCT.pdf • OMG RFP for CTS 2 • http://www.omg.org/cgi-bin/doc?ad/2009-9-17 • HSSP Project • http://hssp.wikispaces.com/ • CTS 2 Project Lead • Russell Hamm (rhamm@apelon.com) • Craig Stancl (stancl.craig@mayo.edu)

11. Questions • Questions and discussion