EFA XDS Document Metadata Binding
 |
Dieses Dokument gibt wieder:
Implementierungsleitfaden EFA XDS Document Metadata Binding (0.9). Die Teilmaterialien gehören der Kategorie cdaefa an. |
February 2013
Jörg Caumanns, Raik Kuhlisch
| Version: | 0.9 |
| Datum: | March 2013 |
| Status: | xxx |
| Verfahren: | {{{Verfahren}}} |
| Realm: |  Deutschland
|
Inhaltsverzeichnis
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).
=
For each document the following set of metadata MUST be provided:
| Slot Name | Binding | Slot Value |
|---|---|---|
| Id | Attribute | Identifer of the document. This identifier MUST be the same for <rim:ExtrinsicObject/@id> and <ihe:Document/@id>. |
| mimeType | Attribute | … |
| objectType | Attribute | MUST be set acc. to section 4.3.1.2 of [IHE IT TF 3] |
| Status | Attribute | MUST be "urn:oasis:names:tc:ebxml-regrep:StatusType:Approved" |
| creationTime | rim:Slot | MUST be set to the document creation time. At least YYYYMMDD MUST be provided. |
| languageCode | rim:Slot | … |
| sourcePatientID | rim:Slot | MUST be of the same value as $XDSDocumentEntry.PatientId (see below) |
| healthcareFacilityTypeCode | Classification | … |
| practiceSettingCode | classification | … |
| confidentialityCode | classification | SHOULD always be set to “N”. |
| XDSDocumentClassCode | classification | … |
| XDSDocumentFormatCode | classification | … |
| XDSDocumentEntry.PatientId | External identifier | Equals to the patient identifier that was agreed on upon EFA instantiation (encoded as HL7 v3 II data type) |
| XDSDocument.UniqueId | External identifier | MUST refer to the OID of the document that is included within the <ihe:Document> element. |
Other metadata than the ones listed above SHOULD NOT be used and MUST NOT be processed by EFA clients and providers.
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:
Name der Praxis^^^^^&1.2.276.0.76.4.5&ISO^^^^260326822
