EFA XDS Document Metadata Binding

EFA XDS Document Metadata Binding

EFA XDS Document Metadata Binding

Implementierungsleitfaden

vorgelegt von:
February 2013
Jörg Caumanns, Raik Kuhlisch

Draft

Version:	0.9
Datum:	March 2013
Status:	xxx
Verfahren:	{{{Verfahren}}}
Realm:	Deutschland

Copyright © 2012-2013: HL7 Deutschland

Document Metadata

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

classCode

The document class SHALL be provided as a LOINC code.

Example:

 <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:41a5887f-8865-4c09-adf7-e362475b143a"
    classifiedObject="urn:uuid:fbf2ea29-3aa3-4bc5-9187-01d7b6b0f481" 
    nodeRepresentation="11520-4">
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>2.16.840.1.113883.6.1</rim:Value>
        </rim:ValueList>
    </rim:Slot>
    <rim:Name>
        <rim:LocalizedString xml:lang="de" charset="UTF-8" value="EKG Befund"/>
    </rim:Name>
 </rim:Classification>

typeCode

The typeCode SHOULD be identical to the classCode.

Comments

This slot is optional. If given, it SHALL hold a summary of the document content.

Example:

<rim:Description>
   <rim:LocalizedString xml:lang="de" charset="UTF-8" value = "Befund zur Magenspiegelung vom 3.3.13"/>
</rim:Description>

German Profile

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

Author Institution

For the German healthcare system the following identification schemes MUST be used. If multiple schemes are available for an organization, the order in the table denotes the order of preference.

Organization	Scheme	Code System OID
Practice	Telematik ID This ID scheme MUST be preferred only if the Telematik ID is recorded within the SMC-B AUT certificate of the practice.	not defined yet
Practice	ID of the SMC-B AUT Certificate	1.2.276.0.76.4.77
Practice	»Institutskennzeichen (IK)« acc. to § 293 SGB V	1.2.276.0.76.4.5
Practice	KBV »Arztnummer Praxis«	1.2.276.0.76.4.10
Hospital department or faculty	Telematik ID This ID scheme MUST be preferred only if the Telematik ID is recorded within the SMC-B AUT certificate of the department/faculty.	not defined yet
Hospital department or faculty	ID of the SMC-B AUT Certificate	1.2.276.0.76.4.77
Hospital	Telematik ID This ID scheme MUST be preferred only if the Telematik ID is recorded within the SMC-B AUT certificate of the hospital.	not defined yet
Hospital	ID of the SMC-B AUT Certificate	1.2.276.0.76.4.77
Hospital	»Institutskennzeichen (IK)« acc. to § 293 SGB V	1.2.276.0.76.4.5

Example:

A resident practice with the Institutskennzeichen 260326822 would be encoded as:

<rim:Slot name="authorInstitution">
  <rim:ValueList>
    <rim:Value>Name der Praxis^^^^^&1.2.276.0.76.4.5&ISO^^^^260326822</rim:Value> 
  </rim:ValueList>
</rim:Slot>

Author Person

For the German healthcare system the following identification schemes MUST be used. If mul-tiple schemes are available for a role, the order in the table denotes the order of preference. If multiple IDs are known, at least the two SHOULD be provided.

Person Role	Scheme	Code System OID
Physician	Telematik ID This ID scheme MUST be preferred only if the Telematik ID is recorded within the HBA AUT certificate of the physician.	not defined yet
Physician	ID of the HBA AUT Certificate	1.2.276.0.76.4.75
Physician	Lebenslange Arztnummer KV	1.2.276.0.76.4.16
Hospital Staff Practice Staff	Any internal identification scheme that guarantees a unique identification within the scope of the identified organization. The <representedOrganization> and an <id> for this organization MUST be recorded.	local code system

Example:

A physician with the Arztnummer 12345678 would be encoded as:

<rim:Slot name="authorInstitution">
  <rim:ValueList>
    <rim:Value>Name des Arztes^^^^^&1.2.276.0.76.4.16&ISO^^^^12345678</rim:Value> 
  </rim:ValueList>
</rim:Slot>

HealthcareFacilityTypeCode

The healthcare facility type code SHALL be encoded as an OID. The values to be used SHALL be taken from table 3 in [[1]]. Only the following values from that table SHOULD be used:

Facility Type	OID
hospital	1.2.276.0.76.4.53
medical practice	1.2.276.0.76.4.50
dentists practice	1.2.276.0.76.4.51”
pharmacy	1.2.276.0.76.4.54

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

sourcePatientInfo

This slot SHALL NOT be used for protecting the confidentiality of personal medical information.