1. Centralized Terminology Services A HL7 Opportunity

2. Centralized Terminology Services are becoming more important... KP has some systems that use centralized terminology services G-CPR plans to use centralized terminology services Others... No widely accepted standard for centralized terminology services exists

3. CORBA-MED Lexicon Query ServicesCORBA-MED Lexicon Query Services –High CORBA overhead, specifies an implementation, not an information standard –Vendors may prefer other implementation methods (RMI, Sockets,...) British NHS Standard API for Clinical Terms Version 3British NHS Standard API for Clinical Terms Version 3 –Tied to a specific terminology system

4. Standardize Information Exchange Use XML to specify the information exchange between client and serverUse XML to specify the information exchange between client and server Work to integrate current standards without specifying a specific implementationWork to integrate current standards without specifying a specific implementation –CORBA, RMI, Sockets,...

5. Form a Terminology Server Subgroup Use existing standards as a foundationUse existing standards as a foundation Harmonize the standards without specifying a specific implementationHarmonize the standards without specifying a specific implementation

6. Benefits Vendors can consolidate functionality of terminology servicesVendors can consolidate functionality of terminology services –Transport layer independent standard –No need to take a position on CORBA vs DCOM vs RMI vs others

7. Close DiscussionDiscussion Volunteers?Volunteers?