Lexicon Query Services

1. Lexicon Query Services Harold Solbrig 3M Health Information Systems 2/19/99 Lexicon Query Services

2. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

3. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

4. Thought or Reference Symbol Referent Why Terminology? Refers To Symbolises Stands For Ogden’s Semiotic Triangle* *C.K. Ogden and I.A. Richards, The Meaning of Meaning, 1923

5. Why Terminology? Thought or Reference Refers To Symbolises ROSE Stands For Symbol Referent

6. Thought or Reference Symbolises Refers To ROSE Stands For Symbol Referent Why Terminology? Thought or Reference Refers To Symbolises ROSE Symbol Stands For

7. Why Terminology? CONCEPT CONCEPT Symbolises Refers To Refers To Symbolises ROSE ROSE Stands For Stands For Referent Designation Designation

8. Why Terminology? CONCEPT CONCEPT Symbolises Refers To Refers To Symbolises ROSE ROSE Stands For Stands For Designation Designation Referent

9. Miscommunication • Occurs when • Symbols are incorrectly transmitted • Symbols symbolize different thoughts to the receiver • Computers • Reduce transmission error • Exacerbate symbolization problem through lack of context and feedback

10. Miscommunication • To reduce the symbolization problem: • Produce unambiguous symbols • Precisely define symbol meaning on both the transmitting and receiving end

11. Coding CONCEPT CONCEPT Symbolises Refers To Refers To Symbolises ROSE ROSE Stands For Stands For Designation Designation Referent Rose(2) 1 a: Websters Collegiate Dictionary Tenth Edition Rose(2) 1 a: Websters Collegiate Dictionary Tenth Edition

12. Terminology “Terminology is concerned with the study and use of the systems of symbols and linguistic signs employed for human communication in specialised areas of knowledge and activities” International Association of Terminology, 1982 Lexicon Query Services

13. Terminology The lexicon of a special subject language reflects the organizational characteristics of the discipline by tending to provide as many lexical units as there are concepts… The items which are characterised by special reference within a discipline are the ‘terms’ of the discipline, and collectively they form its ‘terminology’; those which function in general reference over a variety of sublanguages are simply called ‘words’ and their totality the ‘vocabulary’. A Practical Course in Terminology Processing Juan C Sager Lexicon Query Services

14. Terminology Example • Sub Language - International Classification of Diseases • Term - Angina pectoris • Words • Anginal pain • Stenocardia • Anginal syndrome • Angina Lexicon Query Services

15. Code A unique string of characters which represents a term within a terminology. • Succinct (usually) • May or may not have intrinsic form or meaning • Represents a the meaning behind a term in a terminology. • Example (ICD-9-CM): • 413 AGINA PECTORIS Lexicon Query Services

16. Coded Terminology • Set of unique concept codes assigned to terms within a terminology • aka “Coding Scheme” 001 Cholera 001.0 Due to vibrio cholerae 001.1 Due to Vibrio Cholerae El Tor 001.9 Cholera, Unspecified ... Lexicon Query Services

17. Coding Schemes • May vary in size and complexity • HL7 2.3 Table 1 has 4 codes: M Male F Female O Other U Unknown • UMLS Contains > 475,000 concepts in 16+ tables. Lexicon Query Services

18. Uses of coding schemes To aid in the creation and validation of precise, unambiguous information. • Phrase matching and lookup • Selection lists • Code Refinement • Classification tools • Information validation Lexicon Query Services

19. Parts of a coding scheme • Coding scheme • Representational scheme • Categorization / classification / structuring of codes Lexicon Query Services

20. Coding Scheme • Set of codes and represented terms 574 Cholelithiasis 574.0 Calculus of Gallbladder with Acute Cholecystitis 574.1 Calculus of Gallbladder with other Cholecystitis 574.2 Calculus of Gallbladder without mention of Cholecystitis ... • Associated definitions, notes, comments, etc. 574 Definition: Presence or formation of gallstones. Comments: The following fifth-digit subclassification is for use with... Lexicon Query Services

21. Representational Scheme • Text strings, pictures, sound bites, etc. • Independent lexical classification • Association between text, etc. and codes • Language • When it applies • Lexical information (plural, single, spelling, adjective, noun, …) Lexicon Query Services

22. Representational Scheme 574 Cholelithiasis French Preferred Lithaise Biliaire French Synonym CHOLELITHIASE English Plural Cholelithiases English Case cholelithiasis Entlish Other Cholelithiasis, NOS Lexical Group L0008350 Lexical Group L0164767 Cholelithiases LITHIASE BILIAIRE Cholelithiasis, NOS Cholelithiasis NOS cholelithiasis ... Lexicon Query Services

23. Categorization / classification / structuring of codes within the terminology(Systemization) Lexicon Query Services

24. Systemization • Associations between codes • isPartOf • isSubtypeOf • isSubclassificationOf • references • depends on • ... Lexicon Query Services

25. Systemization 576.9 (Biliary Tract Disease) hasSubtypes 574 (Cholelithiasis) 576.9 (Biliary Tract Disease) ... 574 (Cholelithiasis) hasSubtypes 574.0 (Calculus of galbladder without… 574.1 (Calculus of galbladder with… … 574 (Cholelithiasis) hasSibling 751.61(Biliary Atresia) 576.4 (Biliary Fistula) ... Lexicon Query Services

26. Systemization • Associations between codes and non-coded information • hasCount, hasSize, hasColor, … Lexicon Query Services

27. Cross Scheme Functionality • Associations between codes from different coding schemes • Synonymous, broader than, narrower than • Relationship between terminology and “outside” world. Lexicon Query Services

28. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

29. Lexicon Query Services RFP • Issued January 1997 • Requests an interface specification to access to the common features of a set of lexicon query services. Lexicon Query Services

30. Sony Interface Panasonic Lexicon Query Services

31. An Interface • Allows a change of vendor, size, power and implementation to change without having to re-train (or re-program) the user. Lexicon Query Services

32. A IDL Interface Specification enum Serialstate { rewind, stop, run, pause, fastForward }; interface SerialButtons { Serialstate pushButton(in SerialState whichButton); }; (followed by a lot of text) Lexicon Query Services

33. CORBA Interfaces • Hardware Independent • Operating System Independent • Network Protocol Independent • Application and Language Independent Lexicon Query Services

34. LQS RFP Interface • Provides a common, well understood way of accessing any coded terminology. • Terminology implementations would be delivered by many vendors, with varying structure and content. • Terminology clients could be written without intimate knowledge of the vendor. Lexicon Query Services

35. LQS RFP Requirements • Read Only Access • Mandatory Requirements: • List the content of a coding scheme • Retrieve concept code for concept • Retrieve concept attributes and characteristics • List attribute and/or relationship types • List concepts which participate in given association • List all relationships in which a concept participates • Access concepts by attribute value • List concepts which satisfy multiple relationship/attribute value combinations. Lexicon Query Services

36. LQS RFP Requirements • Optional Requirements • Term matching on soundex, pattern etc. • Hierarchical relationship traversal • Ability to represent concepts as co-ordinated terms. Lexicon Query Services

37. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

38. Response Overview • Formed a loose consortium of 26 individuals representing 14 different organizations. • Created: • Use Scenarios • Definition of Terms • Abstract Model • IDL Specification • Meta-Terminology (Value Domains for LQS) Lexicon Query Services

39. Use Scenarios • Attempt to categorize the access needs and functionality for the terminology. • Included external input as well as RFP requirements • Served a secondary role of creating a “terminology of terminolgy” that we could focus on. Lexicon Query Services

40. Definition of Terms • Many terms were renamed and redefined several times as the model developed. • Served a secondary function of validating the abstract model. If the associations and behavior of the model class didn’t match the name then we had some rework to do. • Some of the final definitions were reasonably arbitrary. Lexicon Query Services

41. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

42. Abstract Model • Created using UML • Purpose is to represent the information and computational viewpoints • Attempted to remain “abstract” and NOT include shortcuts, performance enhancements, etc. • Describes what, not how. Lexicon Query Services

43. Terminology Service Lexicon Query Services

44. Coding Scheme Lexicon Query Services

45. Coding Scheme Version Lexicon Query Services

46. ConceptDescription Lexicon Query Services

47. Systemization Lexicon Query Services

48. Value Domain Lexicon Query Services

49. Presentation Outline • Introduction to Terminology and Coding • Description of the LQS RFP • Overview of the response • Abstract Model Overview • IDL Overview • Demonstration Lexicon Query Services

50. IDL • Hand “translated” from model, using Use Scenarios as guidance • Contains shortcuts, flattenings, performance tweaks, naming changes (IDL conventions), etc. • Abstract model maps into IDL. (Reverse isn’t always TRUE). Lexicon Query Services