EFA XDS Folder Metadata Binding

Aus Hl7wiki
Implementierungsleitfaden
Wechseln zu: Navigation, Suche
K
K (→‎eventCodeList)
Zeile 18: Zeile 18:
 
Unless stated otherwise in the following sub-sections, folder metadata MUST be used as defined in table 4.1-7 of [IHE ITI TF Vol3 v9.0]. Further constraints MAY apply for EFA national profiles (see below for the German profile).
 
Unless stated otherwise in the following sub-sections, folder metadata MUST be used as defined in table 4.1-7 of [IHE ITI TF Vol3 v9.0]. Further constraints MAY apply for EFA national profiles (see below for the German profile).
  
−
=== eventCodeList ===
+
=== odeList ===
  
−
The linkage of a folder to a case record is implemented through the ''eventCodeList'' classification of that folder. Each folder SHALL contain at least 2 event codes:
+
The linkage of a folder to a case record is implemented through the ''codeList'' classification of that folder. Each folder SHALL contain at least 2 event codes:
 
# a single event code that denotes the folder as part of a case record. The respective classification is done by assigning an event code of (code="ECR", codeSystem="IHE-D-Cookbook-FolderClassCode") to the folder.
 
# a single event code that denotes the folder as part of a case record. The respective classification is done by assigning an event code of (code="ECR", codeSystem="IHE-D-Cookbook-FolderClassCode") to the folder.
 
# one or more event codes that signal the medical motivation of maintaining that specific case record. These event codes can be a diagnosis code, a contract type, etc. Folders that are assigned to multiple case records SHALL be classified with multiple of such event codes (at least one per case record). Only the code systems and codes as listed in the following table SHALL be used.
 
# one or more event codes that signal the medical motivation of maintaining that specific case record. These event codes can be a diagnosis code, a contract type, etc. Folders that are assigned to multiple case records SHALL be classified with multiple of such event codes (at least one per case record). Only the code systems and codes as listed in the following table SHALL be used.

Version vom 5. April 2013, 21:31 Uhr

Logo-hl720.jpg
EFA XDS Folder Metadata Binding
EFA XDS Folder Metadata Binding
Implementierungsleitfaden
vorgelegt von:
February 2013
Jörg Caumanns, Raik Kuhlisch
Draft
Version: 0.9
Datum: March 2013
Status: xxx
Verfahren: {{{Verfahren}}}
Realm: Flag de.svg Deutschland
Copyright © 2012-2013: HL7 Deutschland


Folder Metadata

Unless stated otherwise in the following sub-sections, folder metadata MUST be used as defined in table 4.1-7 of [IHE ITI TF Vol3 v9.0]. Further constraints MAY apply for EFA national profiles (see below for the German profile).

odeList

The linkage of a folder to a case record is implemented through the codeList classification of that folder. Each folder SHALL contain at least 2 event codes:

  1. a single event code that denotes the folder as part of a case record. The respective classification is done by assigning an event code of (code="ECR", codeSystem="IHE-D-Cookbook-FolderClassCode") to the folder.
  2. one or more event codes that signal the medical motivation of maintaining that specific case record. These event codes can be a diagnosis code, a contract type, etc. Folders that are assigned to multiple case records SHALL be classified with multiple of such event codes (at least one per case record). Only the code systems and codes as listed in the following table SHALL be used.
Purpose Code System Name Code System OID Value(s)
Diagnosis ICD-10-GM 1.2.276.0.76.5.311 see http://www.dimdi.de/static/de/klassi/icd-10-gm/kodesuche/onlinefassungen/htmlgm2013/index.htm
Disease Management Contract (DMP) S_KBV_DMP 1.2.276.0.76.5.223 see http://www.kbv.de/keytabs/ita/schluesseltabellen.asp?page=S_KBV_DMP_V1.01.htm
Integrated Care Contract (IV Vertrag) S_VDX_VERTRAGSART 1.2.276.0.76.5.257 09
This event code just signales that this folder is linked with a case record that serves an integrated care contract. Information about the contract SHALL be given with the display name of this event code.
GP managed care (Hausarztzentrierte Versorgung) S_VDX_VERTRAGSART 1.2.276.0.76.5.257 07
This event code just signales that this folder is linked with a case record that serves a GP managed care contract. Information about the contract SHALL be given with the display name of this event code.


Example: Diagnosis (ICD-10)

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="ECR">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>IHE-D-Cookbook-FolderClassCode</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="Elektronische Fallakte"/>
    </rim:Name>
 </rim:Classification>

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="I21.0">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>1.2.276.0.76.5.311</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="Akuter transmuraler Myokardinfarkt der Vorderwand"/>
    </rim:Name>
 </rim:Classification>


Example: DMP

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="ECR">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>IHE-D-Cookbook-FolderClassCode</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="Elektronische Fallakte"/>
    </rim:Name>
 </rim:Classification>

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="6">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>1.2.276.0.76.5.223</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="COPD"/>
    </rim:Name>
 </rim:Classification>

Example: IV Vertrag

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="ECR">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>IHE-D-Cookbook-FolderClassCode</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="Elektronische Fallakte"/>
    </rim:Name>
 </rim:Classification>

 <rim:Classification 
    id="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    lid="urn:uuid:c33ca26a-29b4-45be-a9b9-de60adca4c64"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="09">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>1.2.276.0.76.5.257</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="IV Vertrag Darmkrebs"/>
    </rim:Name>
 </rim:Classification>

German Profile

For using EFA within the German national healthcare IT infrastructure (Telematikinfrastruktur) the constraints listed below MUST be considered.

patientID

Only the following identification schemes MUST be used. If multiple schemes are available for a practice, the order in the table denotes the order of preference.

Person Role Scheme Root OID
Patient Fixed part of unique health insurance number (KVNR). 1.2.276.0.76.4.8
Patient Full health insurance number (KVNR) 1.2.276.0.76.4.1
Patient Local identifier within the healthcare organization. Local identifiers MUST NOT be directly derived from personal id numbers that are assigned by non-healthcare authorities. Local Root OID


Abgerufen von „https://wiki.hl7.de/index.php?title=cdaefa:EFA_XDS_Folder_Metadata_Binding&oldid=12498“