09.04.2013 Views

SNOMED CT® Release Format 1 (RF1) Guide - ihtsdo

SNOMED CT® Release Format 1 (RF1) Guide - ihtsdo

SNOMED CT® Release Format 1 (RF1) Guide - ihtsdo

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

224 | <strong>SNOMED</strong> CT <strong>Release</strong> <strong>Format</strong> 1 (<strong>RF1</strong>) <strong>Guide</strong> July 2012<br />

Note: The discussion of rules is included although rules are not yet used in the released <strong>SNOMED</strong> CT<br />

Cross Maps. However, this feature may be of interest to implementers.<br />

3.2.11.5.1. Nature of the Rules<br />

The types of rules required may vary according to the nature of the Target Scheme. However, the following<br />

general types of rule can be recognized in several different types of mapping:<br />

• Age or sex of the person to whom the Concept is applied.<br />

• Qualifiers associated with the mapped Concept.<br />

• Temporal attributes of the mapped Concept.<br />

• Coexisting conditions:<br />

• Including pathological conditions and other conditions (e.g. pregnancy).<br />

• Related statements:<br />

• Procedure applied to particular condition.<br />

• Condition treated by particular procedure.<br />

• Condition arising as a result of particular procedure.<br />

• Other statements of causation (e.g. condition caused by accident).<br />

3.2.11.5.2. Representation<br />

Each type of rule can be expressed as a function with parameters which when evaluated returns a true or<br />

false result (similar to the NHS Casemix grouper tools). Alternatively the rules could be expressed as SQL<br />

style queries against an agreed common data model (similar to the NHS MIQUEST Health Query Language).<br />

In either case, the end result is a decision that either accepts or rejects a particular mapping.<br />

Whichever form of representation is used the Extensible Markup Language (XML) is suggested as a<br />

general-purpose syntax because it support flexible expressions and facilitates parsing. Thus the content of<br />

the MapRule is an XML string that contains one or more elements. According to the form of expression each<br />

element may represent either a function with parameters or query predicate.<br />

3.2.11.5.3. Processing order<br />

When determining which of a set of cross map options is to be used for mapping a particular Concept a further<br />

consideration is the order in which the rules are tested.<br />

The following example is used to illustrate each of the options:<br />

Concept “A” can be mapped to one or more of the five possible cross map codes (“V”,“W”,“X”,“Y”,“Z”)<br />

• “V” applies if the patient does not have co-existing condition “B” or “C”;<br />

• “W” applies if the patient is under aged 60 and has co-existing condition “B”;<br />

• “X” applies if the patient is aged 60 or over and has co-existing condition “B”;<br />

• “Y” applies if the patient is under aged 60 and has co-existing condition “C”;<br />

• “Z” applies if the patient is aged 60 or over and has co-existing condition “C”.<br />

In addition to the five single target code options, there are two possible combinations<br />

• “W,Y”and“X,Z” indicating the presence of co-existing conditions “B”and“C” in either age group.<br />

3.2.11.5.3.1. Order Implementation processing<br />

To allow order independent processing of Cross Maps, the rules associated with all options for mapping a<br />

Concept must be complete and mutually exclusive. For every possible occurrence of a Concept only one<br />

Cross Map must have a mapping rule that evaluates as true.<br />

© 2002-2012 International Health Terminology Standards Development Organisation CVR #: 30363434

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!