IG:HL7 diagnosis: Unterschied zwischen den Versionen
K (→Qualifier of Tumor Formular) |
(→table Diagnosis Confidence) |
||
Zeile 170: | Zeile 170: | ||
For out-patient care (§ 295 SGB V, Germany) diagnosis confidence attrinutes are mandatory, while for in-patient care (§ 301 SGB V) | For out-patient care (§ 295 SGB V, Germany) diagnosis confidence attrinutes are mandatory, while for in-patient care (§ 301 SGB V) | ||
they are forbidden i.e. must not be specified. (Sou rce: DIMDI) | they are forbidden i.e. must not be specified. (Sou rce: DIMDI) | ||
+ | |||
+ | {| class=wikitable | ||
+ | ! Code as of §295 SGB V | ||
+ | ! Implementation | ||
+ | ! Meaning | ||
+ | ! Explanation | ||
+ | |- | ||
+ | |G | ||
+ | | | ||
+ | |certain | ||
+ | |diagnosis validated | ||
+ | |- | ||
+ | |V | ||
+ | |uncertaintyCode=UN | ||
+ | |suspicious | ||
+ | |suspicion diagnosis | ||
+ | |- | ||
+ | |Z | ||
+ | | | ||
+ | |state after | ||
+ | |an earlier diagnosis is related | ||
+ | |- | ||
+ | |A | ||
+ | |negationInd=true | ||
+ | |excluded | ||
+ | |this diagnosis has been excluded (use negationInd in Level 3) | ||
+ | -} | ||
===Localization=== | ===Localization=== |
Version vom 10. November 2011, 08:34 Uhr
This article or section is in the middle of an expansion or major restructuring and is not yet ready for use. You are welcome to assist in its construction by editing it as well. If this article has not been edited in several days, please remove this template. This article was last edited by Gheidenreich (talk| contribs) 13 years ago. (Purge) Diese Seite oder Abschnitt ist derzeit ein Entwurf und ist noch nicht fertiggestellt. Du bist eingeladen, bei der Fertigstellung mitzuwirken. Wenn dieser Beitrag länger als einige Tage nicht editiert wurde, entferne diese Vorlage. This article was last edited by Gheidenreich (talk| contribs) 13 years ago. (Purge) |
Representation of Diagnosis based on the Clinical Document Architecture Rel.2 for Healthcare in Germany Version 1.1 |
Inhaltsverzeichnis
- 1 Introduction
- 2 Diagnosis Types
- 3 Common Diagnosis Descriptions
- 4 Diagnosis Model in HL7 V3
- 5 Representation of Diagnosis in specific Codesystems
- 6 Representation of Cancer Diagnosis
- 7 Cancer Diagnosis in HL7 V3
- 8 Representation for specific Use Cases
- 9 Terminology
- 10 Appendix A: Other
- 11 Appendix B: Indices
Introduction
Introduction
Scope
Diagnosis Types
Common Diagnosis Descriptions
Diagnosis Model in HL7 V3
Summary
Diagnoses represented in HL7 V3 shall useu the class Observation, which is modelled as shown in fig. 1.
Detailed descriptions of classes and data types in this model can be found in the related HL7 V3 documentation and Data Type Guidelines.
The following sections specifiy how diagnosis attributes shall be mapped into the Observation model.
Plain Text
value.originalText diagnosis as a plain text ST[0..1] Plain text descriptions of the specific diagnosis shall be stored in the subelement originalText of element value. If it is not necessary to specify a text or should this text not be available, the @nullFlavour attribute shall be used. This element shall explain the reason why there is no plain text. A value of "NAV" states that no coded text is available (yet). More values are described in the HL7 documentation.
The attribute @language of subelement originalText may be used to specify the language of the prosaic diagnosis text.
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
...
<value xsi:type="CD" nullFlavor="NAV">
<originalText>Rektumkarzinom mit Höhenlokalisation ab Anokutanlinie/Linea dentata
</originalText>
</value>
</observation>
Diagnosis Code and Text
value Diagnosis Code CD[0..1] Representing a diagnosis via a code and its associated text shall be done va the value element (in the model: an attribute of the Observation class).
The XML attribute @code shall store the diagnosis code and @displayname shal store the associated diagnosis text.
Such a structured representation of e.g. an ICD10 coded diagnosis looks like this:
The XML attribute @codeSystem shall store the OID for the specific ICD-10-GM version being used and the @codeSystemName attribute shall store the plain text name of the coding system and version.
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
...
<!-- ICD-Code of a diagnosis -->
<value xsi:type="CD" code="I01.0"
displayName="Akute rheumatische Perikarditis"
codeSystem="1.2.276.0.76.5.311" codeSystemName="icd10gm2006"/>
...
</observation>
Diagnosis Type
code classification code CD CW[1..1] The XML attribute shall specifiy the classification code using the attribute @codeSystem for storing the OID of that coding system (also see Annex <10>)
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
<code code="DX" codeSystem="1.2.276.0.76.5.342"/>
...
</observation>
Diagnosis Date
author.time Diagnosis Date IVL<TS>[0..1] The diagnsis date shall specify when the diagnosis was made as the time in the clinical process which is not necessarily the documentation date. The diagnosis date shall be represented using the author instance which shall be connected via Participation to the current Observation instance. Instances of author contain a model attribute time of type IVL<TS>. Detailed information regarding the person giving the diagnosis shall be modelled using an instance of assignedEntity.
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
...
<author>
<!-- Diagnosedatum -->
<time value="20100111"/>
<assignedAuthor>
...
</assignedAuthor>
</author>
...
</observation>
Documentation Date
dataEnterer.time documentation date TS [1..1]
The documentation is the date when the diagnosis has been entered by e.g. a clinician. The data value is mapped to an instance dataEnterer which is related via a Particpation to the Observation instance (see fig. 1 Observation Model).
The dataEnterer class has an model attribute time of type TS, such that in XML the data value will be mapped into an element time and an XML attribute @value.
In case there is no dataEnterer instance, the participation relation with its model attribute typeCode=ENT also manages a participationRole instance representing the data entering person that would otherwise be modelled through a instance of dataEnterer.
<!-- structured representation of diagnosis -->
<observation classCode="OBS" moodCode="EVN" negationInd="true">
...
<!-- documentation date -->
<participant typeCode="ENT">
<time value="20060606"/>
<participantRole>
...
</participantRole>
</participant>
...
</observation>
Diagnosis Time Interval
effectiveTime diagnosis time interval IVL<TS>[0..1]
The model attribute effectiveTime of class Observation specifies the time interval for which the specified is (or, has been) clinically relevant.
In XML, the sub-element low shall specify the begin data and sub-element high shall specifiy the end date. Dates for low or high may also be specified without the other.
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
...
<effectiveTime>
<low value="20050127"/>
</effectiveTime>
...
</observation>
Diagnosis Confidence
value.qualifier diagnosis confidence CR [0..1]
the diagnosis confidence shalöl be rpsented in the model attribute value using a sub-element qualifier.
<!-- structured representation of diagnosis -->
<observation moodCode="EVN" classCode="OBS">
...
<value xsi:type="CD" nullFlavor="NI">
<originalText>......</originalText>
<!--diagnosis confidence -->
<qualifier>
<name code="8" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="G" codeSystem="2.16.840.1.113883.3.7.1.8"/>
</qualifier>
</value>
</observation>
XML attribut @code in name shall specify the name of the diagnosis confidence qualifier, based on the table given below. XML attribut @codeSystem shall specify the OID of the system giving these qualifier names. The diagnosis confidence shall be specified using XML attribute @code in the XML element value.
For out-patient care (§ 295 SGB V, Germany) diagnosis confidence attrinutes are mandatory, while for in-patient care (§ 301 SGB V) they are forbidden i.e. must not be specified. (Sou rce: DIMDI)
Code as of §295 SGB V | Implementation | Meaning | Explanation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
G | certain | diagnosis validated | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
V | uncertaintyCode=UN | suspicious | suspicion diagnosis | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Z | state after | an earlier diagnosis is related | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A | negationInd=true | excluded | this diagnosis has been excluded (use negationInd in Level 3)
-} LocalizationExplanationsReasons for ExceptionsUsing more Attributes of ObservationRepresentation of Diagnosis in specific CodesystemsICD-10-GM-coded DiagnosesTerms of ICD-10 CodesSecondary CodesSide LocalisationConfidence of DiagnosesMapping of ICD-10-coded Diagnoses into HL7 v3Structured representations of ICD10-encoded diagnoses must support primary and secondary codes, code extensions, side localizations and confidence. The primary code represents the main disease. The secondary code extends the primary code and is either used to describe manifestations in organs ("asterisk") or the cause (etiology, e.g. which bacteria) of the main disease ("exclamation") In order to represent this dependency, an additional oberservation instance will be connected via the ActRelationship to that Observation instance containing the primary code. So we have the following basic structure for ICD10-encoded diagnoses: Datei:Figure2.jpg Figure 2: Class Diagram of ICD-10 Diagnoses in HL7 v3 The attribute typeCode in the ActRelationship shall represent the code extension The related Observation instance (connected via the ActRelationship) has MFST (Manifestation) as its typeCode in order to represent 'asterisk"-codes. Exclamation-Code extensions are being represented as Observation instances connected via ActRelationships with typeCode CAUS (Cause). The resulting XML structure of an ICD-10 encodeded diagnosis looks like this: <!-- Structured Representation of Diagnosis-->
<observation moodCode="EVN" classCode="OBS">
…
<!-- Primary Code-->
<value xsi:type="CD" code=" E14.30" codeSystem=" 1.2.276.0.76.5.311"/>
<entryRelationship typeCode="MFST">
<observation moodCode="EVN" classCode="OBS">
…
<!-- Secondary Code-->
<value xsi:type="CD" code=" H28.0" codeSystem=" 1.2.276.0.76.5.311"/>
</observation>
</entryRelationship>
</observation>
In this case the containing ActRelationship instance is of class entryRelationship- repesented by an element of that name. Attribute @typeCode has MFST as a fixed value for representing an asterisk code. value.@code ICD-Code ST [1..1] XML-Attribute @code shall store the specific ICD-10 Code. value.@codeSystem OID of ICD-Codeset UID [1..1] XML-Attribute @codeSystem shall keep the OID of the ICD-10 Version being used. The appendix gives hints towards versions being used in practice. value.@codeSystemName Name of ICD-10 Version ST [0..1] XML-Attribute @codeSystemName may store the Name of the used ICD-10 Version. value.@displayName ICD-Code Text ST [0..1] XML-Attribute @displayName may store the verbose text of the ICD-Code. OIDs and names of ICD-10 versions may be obtained from DIMDI (www.dimdi.de) Representation of Side Localisationvalue.qualifier Side Localisation CR [0..1] The side localisation code shall be represented using the child element qualifier of the value element, as it refines the specification of that diagnosis code (as decided by HL7 DE TC meeting on 2005-09-01, minutes item 1.3.2). An example representation looks like this: <!-- Structured Representation of a Diagnosis -->
<observation moodCode="EVN" classCode="OBS">
<code code="DX" codeSystem=""/>
<!-- Primary code-->
<value xsi:type="CD" code="E14.30" codeSystem="1.2.276.0.76.5.311">
<qualifier>
<name code="7" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="L" codeSystem="2.16.840.1.113883.3.7.1.7"/>
</qualifier>
</value>
<entryRelationship typeCode="CAUS">
<observation moodCode="EVN" classCode="OBS">
<code/>
<!-- Sekundary code-->
<value xsi:type="CD" code="H28.0" codeSystem="1.2.276.0.76.5.311">
<qualifier>
<name code="7" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="B" codeSystem="2.16.840.1.113883.3.7.1.7"/>
</qualifier>
</value>
</observation>
</entryRelationship>
</observation>
Child element 'name' within element 'qualifier' defines the type of qualifier. Therefore, in order to express a qualifier for side localisation, the fixed value „7“ from code system OID 2.16.840.1.113883.3.7.1.0 shall be used: <qualifier>
<name code="7" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="L" codeSystem="2.16.840.1.113883.3.7.1.7"/>
</qualifier>
Representation of Diagnosis Confidencevalue.qualifier Diagnosis Confidence CR [0..1] The Diagnosis Confidence can be considered an extension to the ICD-10 code, shall be represented by the child element qualifier of the value element. <!-- Structured Representation of a diagnosis-->
<observation moodCode="EVN" classCode="OBS">
<code code="" codeSystem=""/>
<!-- Primary code-->
<value xsi:type="CD" code="E14.30" codeSystem="1.2.276.0.76.5.311">
<qualifier>
<name code="8" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="G" codeSystem="2.16.840.1.113883.3.7.1.8"/>
</qualifier>
</value>
<entryRelationship typeCode="CAUS">
<observation moodCode="EVN" classCode="OBS" negationInd="true">
<code/>
<!-- Secondary code-->
<value xsi:type="CD" code="H28.0" codeSystem="1.2.276.0.76.5.311">
<qualifier>
<name code="8" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="A" codeSystem="2.16.840.1.113883.3.7.1.8"/>
</qualifier>
</value>
</observation>
</entryRelationship>
</observation>
Child element 'name' within element 'qualifier' defines the type of qualifier. Therefore, in order to express a qualifier for diagnosis confidence, the fixed value '8' from code system OID 2.16.840.1.113883.3.7.1.0 shall be used: Child element 'value' within 'qualifier shall store the respective confidence value. Possible values are listed in Table 2. <observation classCode="OBS" moodCode="EVN">
...
<value xsi:type="CD" code="A25.1" codeSystem="1.2.276.0.76.5.311" codeSystemName="icd10gm2006">
<qualifier>
<name code="8" codeSystem="2.16.840.1.113883.3.7.1.0"/>
<value code="G" codeSystem="2.16.840.1.113883.3.7.1.8"/>
</qualifier>
</value>
</observation>
When representing an EXCLUDED diagnosis the attribute @negationInd shall be specified as „true“. Specifying a Diagnosis using a Thesaurus IndexOne more way of specifying a diagnosis is by using an index referring to an entry in a medical thesaurus.
Example: Mapping an Alpha-ID-coded DiagnosisAs an example, the diagnostic thesaurus „Alphabetische Verzeichnis zur ICD-10 GM“ (alphabetic directory of ICD-10 GM) is being used in Germany. This directory allows to locate a verbose description of ICD-10 terms and to find the corresponding ICD-10 GM code. The so-called Alpha-ID has been developed to process entries of that alphabetic directory. It is an identification number for each textual entry in the "alphabetic directory". In order to find this alpha-ID, a mapping file has been provided by DIMDI (www.dimdi.de). The Alpha-ID is needed because in medical documentation, the descriptions of diagnoses need to be more differentiated than what ICD-10 codes actually can express. Using the alpha-ID allows for a much finer granularity of diagnosis descriptions.[DIMDI,Alpha_Id]. As an example the ICD-10 Code “A01.0 Typhus caused by Salmonella typhi“ encodes multiple diagnoses such as „liver typhus“, „lung typhus“ and many more. By using the Alpha-Id it is possible to specify the specific type of typhus, like e.g. „liver typhus“ as„I18721“ and „lung typhus“ as „I21312“. 1;I22457;A01.0;;;Darmtyphus 1;I75303;A01.0;;;Eberth-Krankheit 1;I71406;A01.0;;;Enteritisches Fieber 1;I22466;A01.0;;;Enterotyphus 1;I22467;A01.0;;;Febris enterica 1;I17704;A01.0;;;Gallenblasentyphus 1;I71415;A01.0;;;Gastroenteritisches Fieber 0;I78350;A01.0;;;Gastrointestinale Perforation bei Typhus 1;I17794;A01.0;;;Gehirntyphus 1;I21313;A01.0;;;Hauttyphus 1;I22455;A01.0;;;Ileotyphus 1;I94981;A01.0;;;Infektion durch Bacterium typhosum 1;I73671;A01.0;;;Infektion durch Eberthella typhosa 1;I22458;A01.0;;;Infektion durch Salmonella typhi 1;I18721;A01.0;;;Lebertyphus 1;I21312;A01.0;;;Lungentyphus 1;I96251;A01.0;;;Lymphadenitis mesenterialis durch Salmonella typhi 1;I66509;A01.0;;;Posttyphoider Abszess 1;I22456;A01.0;;;Status typhoides 1;I22463;A01.0;;;Typhoenteritis 1;I71447;A01.0;;;Typhogastrisches Fieber 1;I22462;A01.0;;;Typhoides Fieber 1;I31416;A01.0;;;Typhomanie 1;I22464;A01.0;;;Typhoperitonitis 1;I22454;A01.0;;;Typhus 1;I22461;A01.0;;;Typhus abdominalis 1;I73926;A01.0;;;Typhusinfektion Figure 3: Excerpt from mapping file „icd10gm2009_alphaid_edv_ascii20081006.txt“
Figure 4 shows an excerpt of the metafile which defines the fields of the mapping file for the Alpha-Id. Each record consists of six fields, each being separated by a semicolon. The fields in each record contain the following data: Field 1: Validity (0-not valid, 1-valid) Field 2: Stable Identification with prefix I or T ("Alpha-Identifikationsnummer") Field 3: Primary key (with cross) Field 4: Asterisk key (with asterisk) Field 5: Additional key (with exclamation) Field 6: Related text Figure 4: Excerpt from Alpha-ID metafile „icd10gm_alphaid_edv_ascii_liesmich.txt“
<observation moodCode="EVN" classCode="OBS">
…
<value xsi:type="CD" code="I2173" codeSystem="1.2.276.0.76.5.309" codeSystemName="alphaid2006"/>
...
</observation>
value.@code Alpha-Id ST [1..1] XML-Attribute @code stores the index referring to an enty in the „Alphabetisches Verzeichnis“ value.@codeSystem OID ofAlpha-ID UID [1..1] XML-Attribute @codeSystem stores the OID of the Alpha-ID Version being used. value.@displayName Alpha-Id Text ST [0..1] XML-Attribute @displayName may be used to display a text related to the current Alpha-Id value.@codeSystemName Name of Alpha-ID Version ST [0..1] XML-Attribut @codeSystemName represents the Name of the coding system, in our case alphaid2006. OID and name of ICD-10 Version can be obtained from DIMDI (www.dimdi.de) Diagnosis Specification using Identifiers in a NomenclatureOne way of specififying a diagnosis is to use the code representing a diagnostic term in some medical nomenclature. A well-known nomenclature in medicine is SNOMED-CT ("systematic nomenclature of medicine - clinical terms") Compared to ICD-10 it has more concepts for diagnoses and mostly does not classify. In general using a term of a nomenclature often preserves more information than using a term of a classification. Classification is selecting a common representation for a set of concepts that are (under some aspect) considered similar. As a result, classification reduces information, which is demonstrated by the following examples I.e. as a part of clinical documentation of diagnosis the encoding using alpha-id or some identifier in a nomenclature would be preferred over using a classification like e.g. ICD-10. The example shows concepts all being represented through the same ICD-10 code Q92.8 for 'Other specified trisomies and partial trisomies of autosomes'. A simple comparison of codes from nomenclatures gives an example of missing clarity and precision of the ICD-10 classification.
Table 6: Diagnoses in different coding systems
Precoordinated and Postcoordinated Concepts of a NomenclatureFor specifiying a diagnosis using a terminology there are two fundamental approaches: The pre-coordinated approach selects a fixed term among a comprehensive list with representations for all possible concepts. The list of all pre-coordinated terms limits the set of concepts which can be represented. The post-coordinated approach constructs each term out of (more or less independently) encoded aspects of the concept to be represented. The resulting term is the combination of the encoded aspects of the given concept. ICD-10 is a good example of a pre-coordinated terminology, as it lists all the terms for the concepts it can represent. The cross-asterisk extension to ICD-10 is an example of post-coordination. More info can be found under the Terminfo project [Terminfo] of HL7 International. Diagnosis by Thesaurus Index or Term within a NomenclatureA term in a nomenclature is specified through the @value attribute of class Observation. An example (SNOMED CT) of the structured representation looks like this: <observation moodCode="EVN" classCode="OBS">
...
<value
xsi:type="CD" code="314888007"
codeSystem="2.16.840.1.113883.6.96"
codeSystemName="SNOMED CT"
displayName="Typ-II-Diabetes with diabetic cataract"/>
...
</observation>
Attribute value.@code Index or Term in NomenclatureCD CWE [1..1] The XML attribute @code keeps the index referring to an entry in a thesaurus or nomenclature. Attribute value.@codeSystem OID of NomenclatureUID [1..1] The XML attribute @codeSystem stores the OID of the thesaurus or nomenclature. Attribute value.@displayName TextST [0..1] Through the XML attribute @displayName a plain text related to the index can be given. Attribute value.@codeSystemName Name of Nomenclature[0..1] The XML attribut @codeSystemName describes the name of the thesausrus or nomenclature. Representation of Cancer DiagnosisIntroductionIn this chapter, diagnostic aspects of documentation of tumor diseases will be described. Different aspects of diagnostical descriptions of tumor diseases are described by ICD-O (Oncology) and by further classifications to document the expansion (tumor spread) or diseases stage, respectively, the latter one mostly being classified by the TNM-System. Especially for hemato oncological diseases (Leukemias and Lymphomas), other systems (e.g. Ann-Arbor-Classification) are used. TNM-System discribes:
For non-TNM–-classifiable diseases or in addition to the TNM-System there are a number of further classification systems:
Discriptions can be found here: http://www.med.uni-giessen.de/akkk/gtds/grafisch/doku/bd5f.htm http://www.tumorzentren.de/tl_files/dokumente/adt_basis.pdf This list probably will be always incomplete because of the medical progress. ICD-OThird Edition of ICD-O [DIMDI, WHO] is the topical one. ICD-O consists of two axes, Topography- and Morphology-Axis. In ICD-O, tumor can be classified by
In this case, tissue structure and tissue grading is redundant. Precisely: The first four digits of morphology-code describe tissue-type. The fifth one describes biological behaviour (dignity-code):
The sixth digit describes grading, differentiation or phenotype (Histology/Pathology):
For Leukemias and Lymphomas, the sixth digit signifies the immunophenotype
TNM System describes
For the topography axis, there exists an (hierarchical) enlargement, the ‘localisation key’ (Wagner, G. (HRSG.): Tumorlokalisationsschlüssel, 5. Auflage, Springer Verlag, Berlin, Heidelberg, New York, Tokyo 1993), which can supply at some positions clinical relevant differentiation. The morphology axis is composed of a four-digit code for tissue basic structure, a characteristic number for dignity and an additional grading item. The key itself does not contain all possible combinations of histology and dignity, but points out those ones, for whome exist special discriptions. Vice versa not all combinations of basic structure and dignity are possible (so there is no ‘benign leukemia’). Not either there is a grading system available for all kinds of tumor. For some ones, additional information (for Example ‘Cell-line’) is used at the corresponding position. Tumor LocalizationFor Tumor-Coding first of all, the site is important. It will be classified by the Topography -Axis of ICD-O. Topographical -Codes of ICD-10 are based on chapter II (Neoplasm –C 00 – C 97) of ICD-10. However, some of the topographical Codes of ICD-10 (Codes) are not used, because their content is discribed by histology- and digit-Codes of ICD-O. (e.g. Differentiation in situ/ infiltrated, melanoma vs. scin cancer). Tumor Histology and DignityFurthermore, in ICD-O, tumor morphology i.e. tissue structure (histology) and biological behavior (dignity) is discribed by special Codes. Tumor histology is coded by a four-digit number, which is assumed of the morphology-axis of Standardized Nomenclature of Patholoy (SNOP). Dignity-Code is attendant on morphology-Code, seperated by /. Examples:
Tumor GradingGrading is derived from the comparison of primary tissue with the neoplasm of this tissue. There are five grading-degrees (s.o.) and further three degrees for Malignant Lymphoma. Registration of tumor grading is also provided in TNM. Qualifier of Tumor FormulaICD-O –Codes can be specified by the following qualifier: Here ICD-O provides additionally the following codes for Lymphoma, which specify the Cell line: B-Cell, T-Cell, Null-Cell Lymphoma. ICD-O uses the Codes 1 – 9. A detailled System is discribed in Chapter 9 under 9.5.2 and 9.53. ExampleGRAPHIC IS MISSING DisplayName is only available in correlation to qualifiers. According to ICD-O-3 formation rule there are much more discriptions possible as ICD-Catalog proposes.
TNM ClassificationThe TNM classification describes the expansion (spread) of the tumor , i.e. stadium and prognosis of the disease. As a special feature, the TNM classification uses the same notation for all tumors but supports different interpretations for different entities. As an example, a T3 for mamma carcinoma has a different interpretation then the stomach carcinoma. The current edition is 7th which is valid since January 2010, which is a reason why many TNM-6- codes may still be in use. Therefore all TNM-codes should have a version identifier, because non translatable differences are in the different editions. A simple overview can be found in http://de.wikipedia.org/wiki/TNM.
T0 stands for "no primary tumor found" (e.g. because being eradicated by therapy) Tis stands for a very early (non-infiltrating) stage tumor (Tumor in situ) and TX stands for a diagnosis which can not judge the stage because of missing data For some tumors subcategories like e.g. T2a, T2b have been defined.
For some tumors, thisexclusion ("N0") requires the examination of a minimum amount of nodes. The higher the N category the more severe is the lymphatic node affection. If no sufficient data is available NX is being diagnosed.
For many patients one single diagnoss will be made, either a cTNM or a pTNM, such that this type of finding must be distinguished. This preoperative ("c" or no prefix) / pathology ("p") attribute can be captured independently for each of the T N M categories. Therefore the typically used pTNM often meanes pTpNcM, because the spread of a timur can best be diagnosed through surgery while lymphatic spread only by pathology. The prefix "r" describes remaining tumors (after non-disease intervals) and a prefix "y" if the classification was assessed after systemic or radiation treatment (ycTNM, ypTNM etc.). For multiple Primary tumors the suffix "m" (or the number of tumors) will be put after the T-category value(T2(m), T2(5)).
There are voluntary components e.g. the certainty-Faktor (C-Factor) Other components require pathology lab examination (L-, V- or Pn-Category)
letter A, B and C for further classification). For some tumors further modifiers are being documented as a suffix (mostly in parenthenses) like e.g. (sn), (mol-),(mol+). In addition, the TNM supplement introduces innovative or "under test" extensions, which raises doubts whether ta full control of TNM entries. Typical T-Categories (without pre-/suffices) are being listed in chapter "Sites" Typical N-Categories (without pre-/suffices) are being listed in chapter "Nodes". Typical M-Categories (without pre-/suffices) are being listed in chapter "Metastases". 9 Reference: DKFZ Qualifiers of the Tumor FormulaDespite values for T,N and M the TNM formula may also contain various qualifiers. The following table gives an overview which qualifiers can be used for which information and where they are being used. This is case-sensitive! a Autoptical c Clinical C C-Faktor (certainty) G histopathological Grading L Lymphatic vessel invasion m multiple Tumors M distant metastases N Regional lymphatic node metastases p pathological Pn perineural Invasion r Rezidiv tumor R Residual tumor after treatment sn Sentinel-Lymphatic nodes Stage Anatomic Stage-Grouping T Expansion (spreading) of Primary tumor V Venous invasion y Classifikation after initial multi-modal Therapy Ann Arbor ClassificationFor lymphoma the TNM-classification does not make sense and therefore theso-called Ann-Arbor classification will be applied. In this system, the stages I-IV are being distinguished, with an additional suffix letter - A meaning "no general symptoms" - B "with general symptoms" - E "extra-lymphatic organ affected" - S "spleen affected" As with TNM, the Ann-Arbor classification distinguishes between cliniclal (cS) and pathological (pS) grading. According to Durie & Salmon tere are gradings from I to III or the grades according to SWOG from 1-4 for the "Multiple Myeloma". FIGO StagesFIGO stages ignificantly overlap with the TNM classification, especially on the T-axis. Therefore no details are being given here. Gleason ScoreThe so-called Gleason-Score serves to classify the prostate carcinoma. The total numeric value is the sum of two indicators for • loss of differentiation (1-5) • growth pattern (1-5) Resulting values range from 2 to 10 (also see Scores & Assessment DSTU). Furthermore there is a more recent Gleason classification (according to Dhom, Müller and Helpap [Helpap 2002, Helpap2007]), which also requires to specify the procedure (esp. the two degrees) being used. PapanikolaouThe so-called Pap-Test [Pap] is based on colored cell samples from the cervix and is used as an early indocator for cervical cancers. WHO GradingThe so-called WHO Grading serves as an individual progonossi on the one hand and also is an indicator towards further treatment on the other hand. Tumors of WHO Grade I and II in most cases can be treated by surgery alone, while tumors with WHO Grading III and IV normally need additional treatment by radiation or chemotherapie after surgery. The grading looks like this:
Table 9: WHO Grading (OID 1.2.276.0.76.5.394) The fourth edition of the "World Health Organization (WHO) Classification of tumours of the central nervous system" (2007) lists all relevant tumor entities. Also see "Brain Tumor Basics" (http://www.abta.org/sitefiles/sitepages/524309b806778d4f7b79044d97f324ea.pdf) ConclusionThe following data of tumors can be represented by these respective classifications (through values and/or modifiers)
Cancer Diagnosis in HL7 V3Representation for specific Use CasesTerminologyIntroductionThis chapter separates codes in use from normative specifications, in order to allow updates to such codes without having to rewrite the normative part. Therefore this chapter is just informative. Current codes have to be requested.
Overview of Value Sets
Table 12: Value Sets UICC 5. Edition (OID 2.16.840.1.113883.15.8) UICC 6. Edition (OID 2.16.840.1.113883.15.7) UICC 7. Edition (OID 2.16.840.1.113883.15.6)
Overview of Coding Schemata
Table 13: Coding Schemata Diagnosis Types In GermanyThe following codes are being used for typing of diagnoses. This table is a pragmatic collection of the current state-of-the-art in german systems. An international classification is not available at this time.
Table 14: Diagnosis Types (OID 1.2.276.0.76.5.342) ICD-O CodesDignityDignity refers to a tumor property related to their biological behavior in the body. 13
Table 15: Dignity Codes (OID 1.2.276.0.76.5.335) 12 In this case, a cause has to be documented along with the diagnosis – but that is not covered in this implementation guide. It also has to be clarified whether such diagnosis is equal to “suspicious for”. 13 DIMDI www.dimdi.de ICD10GM, ICDO3
Grade of Differentiation/GradingThe following table lists possible gradings. The entity column lists to what tumor entities these grades apply. ref.14
Table 16:Grade of Differentiation/Gradings (OID 1.2.276.0.76.5.336) 14 DIMDI www.dimdi.de ICD-O-3
Cell TypeThis qualifier identifies the immune phenotype related to a lymphoma.
Table 17: Lymphoma-Affected Cell Type (OID 1.2.276.0.76.5.413) Validity of R ClassificationThis qualifier documents the focus of the Residual¬ Classification15.
Table 18: Validity of R-Classifikation (OID 1.2.276.0.76.5.414) 15 Altmann based on TNM V7, Giessen, 2010 Existence of Residual TumorThis qualifier indicates, where a Residual Tumor exists ref. 16.
Existence of residual Tumor 16 Dudeck J. Basisdokumentation für Tumorerkrankte. Giessen. 1999. Codes for TNM-ClassificationTumorsThis section lists known T-Categories ref. 17 (without representing possible extensions). Descriptions vary with the related entity. Codes shall be used along with tumor diagnosis, as one code may have different meanings. (e.g. T1 may refer to 23 cm or 24 cm).
Table 20: (T) Tumor Codes Value Set (OID 1.2.276.0.76.11.1) 17 TNM 5.,6.,7. Edition NodesAny code for involvement of lymph nodes shall only be used together with tumor diagnosis.
Table 21: (N) Lymph Node Codes Value Set (OID 1.2.276.0.76.11.2) MetastasisCode describing distant metastases shall only be used together with tumor diagnosis.
Table 22: (M) Metastasis Code Value Set (OID 1.2.276.0.76.11.3) Residual Tumor
Table 23: Residualtumor Codes Value Set (OID 1.2.276.0.76.11.4) Stage grading as of UICC
Table 24: Stage Classification ref. 18 Value Set (OID 1.2.276.0.76.11.5) 18 In: Schmoll HJ, Höffken K, Possinger K eds. Kompendium Internistische Onkologie. „Collection of Internistic Oncology “. Springer. 4. Edition; 2006 Venous Invasion
Table 25: Venous Invasion Code Value Set (OID 1.2.276.0.76.11.6) Lymphatic System Invasion
Table 26: Lymphatic Invasion Codes Value Set (OID 1.2.276.0.76.11.7) Perineural Invasion
Table 27: Perineural Invasion Code Value Set (OID 1.2.276.0.76.11.8) Qualifier
Table 28: TNM-Qualifier Value Set (OID 1.2.276.0.76.11.9) Certainty
Table 29: Certainty Factor Codes (OID 1.2.276.0.76.5.341) Localisation of Distant Tumours / Metastases
Table 30: Metastases Localisation Codes (OID 1.2.276.0.76.5.401) Codes for Gleason ScoreThe Gleason Grading system helps evaluating the prognosis of men with prostate cancer, as a part of a strategy of prostate cancer staging which predicts prognosis and guides therapy. The Gleason score is based on microscopic findings.
Table 31: Loss of Differentiation according to Gleason Score ref. 19 (OID 1.2.276.0.76.5.402) Documentation by the GleasonSum (Gleason¬Score) as the sum of the two most dominating findings: Uniformly structured tumors: two times the points of above table. Non-uniformly structured tumors: points for the dominating share of findings (so-called primary grading) + points for second-largest share (secondary grading), if punch biopsy show more than two grades, the second component will be based on the most adverse component found. 19: Dt. Gesellschaft f. Urologie e.V. Ann Arbor CodesThe tumor staging system for lymphomas. Principal Stages
Table 33: Ann Arbor (OID 1.2.276.0.76.5.405) Modifiers for Constitutional Symptoms
Table 34: Ann Arbor constitutional symptoms (OID 1.2.276.0.76.5.416)
Table 35: Ann Arbor Extensions for Spreading in Organs Code Set (OID 1.2.276.0.76.5.417) Papanicolaou CodingResults of the so-called Pap-Test
Table 36: Grading according to Papanicolaou (OID 1.2.276.0.76.5.406) Appendix A: OtherAppendix B: Indices |