EFA Metadata Bindings

Dieses Material ist Teil des Leitfadens CDA für die elektronische Fallakte. Direkt im Wiki geändert werden sollten Schreibfehler, ergänzende Hinweise. Offene Fragen, die der Diskussionen bedürfen, sollten auf der Diskussionsseite aufgenommen werden. Liste der Seiten dieses Leitfadens: hier, Liste der Seiten, in denen dieses Material verwendet (transkludiert) siehe hier .

Anmerkung: Die unter den einzelnen Überschriften in geschweiften Klammern angegebenen Kürzel dienen der Unterstützung des Kommentierungsverfahrens. Bitte geben Sie bei einem Kommentar oder einem Verbesserungsvorschlag zu dieser Spezifikation immer das Kürzel des Abschnitts an, auf den sich Ihr Kommentar bezieht. Alle Kommentare werden in der Lasche "Diskussion" zu der kommentierten Seite gesammelt und gegenkommentiert.
Hinweise zum Kommentierungsverfahren einschließlich aller Formulare und Kontaktadressen finden Sie auf der Seite "Kommentierung EFAv2.0".

---

Mapping of Core Information Model Classes

Bitte markieren Sie Kommentare zu diesem Abschnitt mit dem Code {MdaBs.01}

For the linkage of XDS compliant components with eCR components the following mapping of business objects MUST be implemented:

Electronic Case Record	IHE XDS
Patient	Patient
eCR CaseRecord	Set of XDS Folders that have values of XDSFolder.patientID and XDSFolder.codeList in common
eCR Partition	XDS Folder
no correspondence	XDS Submission Set
eCR Medical Data Object	XDS Document Entry (document metadata) Repository Object (document data)

Mapping of PIM Classes

Bitte markieren Sie Kommentare zu diesem Abschnitt mit dem Code {MdaBs.01}

Instances of ECR PIM Classes are shared through XD* transactions and within XD* metadata. The following table shows the respective binding of these classes to IHE XD* message arguments and ebRS metadata slots/elements.

ECR PIM Class	IHE XD*	Comments
patientID	XDSDocumentEntry.patientId XDSFolder.patientID	-
communityID	XDSDocumentEntry.homeCommunityId XDSFolder.homeCommunityID	-
purpose	XDSFolder.codeList	see XDS Folder Metadata
ecrInfo	see below	As there is no correspondence to a case record object with IHE XD* this class is mapped onto folder metadata. This implies that the ecrInfo fraction of all folder's belonging to the same eCR shall be identical and synchronized.
consentInfo	-	ECR consentInfo objects are represented as structured, coded documents. See "Leitfaden Patienteneinwilligung" for details. The binding of consentInfo is not subject to the EFA Specification. An EFA domain must agree on a specific binding. Implementation Guide for CDA®, Release 2: Consent Directives, Release 1 MAY be used.
consentDoc	-	Consent documents are represented as documents of a format that is to be agreed by each ECR domain (e.g. PDF/A).
partitionID	XDSFolder.uniqueID	see IHE ITI TF Vol3 section 4.1.9.1 for details
partitionList	set of XDSFolder objects	-
ecrRef	XDSFolder.patientID and XDSFolder.codeList and XDSFolder.homeCommunityID	All folders classified with the same patient ID and purpose codes set up a unique case record. The homeCommunityID signals the XDS Affinity Domain where the reference is valid.
partitionInfo	XDSFolder object	see XDS Folder Metadata for details
docMetadata	XDSDocument registry object	see XDS Document Metadata for details
docRelationship	XDS Association object	see Append and Replace in IHE ITI TF-3#4.1.2
documentID	XDSDocument.uniqueID XDSDocument.repositoryUniqueID	shall be used for document retrieval (retrieveDocument transaction).
	XDSDocument.entryUUID	shall be used for document referral (associations between registry entries)

ecrInfo

Attribute	Description	Mapping onto IHE XD* metadata
patientID (mandatory)	Identifier of the patient who is subject to the eCR	All XDS folders representing the partitions of an eCR instance shall be assigned the same patientID attribute (see IHE ITI TF Volume 3, Section 4.2.3.1.3).
purpose (mandatory)	purpose for maintaining the eCR	All XDS folders representing the partitions of an eCR instance shall be classified with the same purpose (see folder metadata codeList element).
ecrStatus (mandatory)	Status of an eCR instance	The status of en eCR is implemented through the eCR access policy and the avaibalility status of the XDS folders that represent the partitions of the ecR. status XDS folder availabilityStatus eCR Access Policy open approved access policy reflects the patient's consent suspended approved access policy only allows access to the case record manager and to privacy commissionars retired approved deny-all access policy assigned to the eCR. archived - all eCR data and metadata have been deleted from the XDS registry and repository

MountPoint

Instances of the ECR PIM class MountPoint SHALL be bound to XDSDocumentEntry as follows:

ECR PIM MountPoint attribute	IHE XDS Metadata Attribute	Comments
patientID	XDSDocumentEntry.patientId
sourcePatientID	XDSDocumentEntry.sourcePatientId

The XDSDocumentEntry SHALL be a member of a XDSFolder. This XDSFolder SHALL have a codeList-Classification containing

• (code="ECR-mountpoint", codeSystem="IHE-D-Cookbook-FolderClassCode") and
• a purpose code.

Querverweise und Referenzen

• EFA-2.0-Spezifikation