RF 2 Mapping Data Set Standard IHTSDO International

RF 2 Mapping Data Set Standard IHTSDO International Health Terminology Standards Development Organisation

History of SNOMED RF 2 and Mapping § 2005: First rules-based map for ICD-9 -CM § 2007 -2012: development of technical mapping standards § § for SNOMED to ICD-10 2009 -20100706 Development of RF 2 refset standard 20120425: quality assurance metrics for RF 2 publication of ICD-10 map(NLM) 20120612 Publication RF 2 map SNCT-ICD-10 20130219 John Gutai develops draft of revised RF 2 mapping data specification

Editorial History: RF 2 map data standards § 2009 -20100706 RF 2 reference set standard specifies simple and complex map refset structures; however § Even “simple” maps should specify the nature of the relationship intended by the map since maps support many varied use cases; simple case does not support all data requirements proposed by ISO § Data structures were complex and could not be easily browsed due to segregation of relationship data into TWO refset files § 20130219 RF 2 standards document drafted by John Gutai: include requirements for ICD-10 knowledge based maps AND simplified one-to-one map projects; released for comment § 20130611 Mapping SIG reviews and discusses draft with UK and other IHTSDO stakeholders

Exemplar development for better understanding § Australian substances mapping (Dion Mc. Murtrie): § AMT substances to SNOMED CT substances § "equivalent" (291000036107) or "generalise" (301000036106) § ICD-10 rules based map: § SNCT concepts (CF, Events, Situations) to ICD-10 § “Properly classified”, “Out of scope”, “Context dependent”(rule required) § ICD-10 UK rules based map: § SNCT concepts (CF, Events, Situations) to ICD-10 § “Properly classified”, “Out of scope”, “Context dependent”(rule required) § Multiple use cases (Map Blocks enabled)

Issues Material to Proposed RF 2 Data Draft § Issues managed: § Addition UK requirements: management of multiple use cases added to support further map complexity (Map. Block artifacts) § Uniform data attributes across all map types § Map relationship formally stated for ALL maps in SNCT metadata § Consolidation of all IHTSDO map artifacts into one release data set: § Supports all proposed use cases § Allows for ONE set of QA metrics and data quality checks § Reduces referential complexity of map data sets § Issues created: § Additional complexity for simple maps § Open issues: § Relationship to conflicting RF 2 data standard