1. Terminology to Support Merging Data Sets James J. Cimino, M.D. Columbia University New York-Presbyterian Hospitals

2. Uses for Merged Data Sets - I will list some of the obvious here

3. Requirements of Terminology Represent data from multiple local sources Provide higher-level concepts to support –Re-use –Aggregation Fit the institutional data model Maintainable

4. What Would We Buy? "Starter set" of high-quality, comprehensive content Tools or services for maintaining currency with local terminologies Maintenance contract to keep current with national standards Compatibility with homegrown and commercial applications

5. What is in the Starter Set? Lab: LOINC Pharmacy: NDC plus other models Radiology: ??? ICD-9/10/CM and other billing codes Anything useful for aggregation and re-use

6. What Should the Tools Do? Multiple, relatively unsophisticated editors Batch updates from local term sets Support addition of high-level terms needed locally Server functions –Free-standing –Integrated

7. Maintenance Concept-oriented and concept-permanent Timely (daily would be ideal) Authoritative editorial board

8. What's Around? UMLS SNOMED Read Smaller term sets