EFA Metadata Bindings
K (Markup-Fehler behoben) |
K (Markup-Fehler behoben) |
||
Zeile 5: | Zeile 5: | ||
== Mapping of Core Information Model Classes == | == Mapping of Core Information Model Classes == | ||
− | + | <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {MdaBs.01}</tt> | |
− | Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {MdaBs.01} | ||
This section defines the XDS-Metadata bindings for the [[cdaefa:EFA_Business_Informationsmodell#EFA_Informationsmodell|classes of the EFA core information model]]. | This section defines the XDS-Metadata bindings for the [[cdaefa:EFA_Business_Informationsmodell#EFA_Informationsmodell|classes of the EFA core information model]]. | ||
Zeile 32: | Zeile 31: | ||
== Mapping of PIM Classes == | == Mapping of PIM Classes == | ||
− | + | <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {MdaBs.01}</tt> | |
− | Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {MdaBs.01} | ||
This section defines the XDS-Metadata bindings for the [[cdaefa:EFA_Business_Informationsmodell#PIM_Data_Structures|classes of the EFA platform independent model]]. | This section defines the XDS-Metadata bindings for the [[cdaefa:EFA_Business_Informationsmodell#PIM_Data_Structures|classes of the EFA platform independent model]]. |
Aktuelle Version vom 27. Januar 2015, 11:08 Uhr
Dieses Material ist Teil des Leitfadens CDA für die elektronische Fallakte.
|
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".
Inhaltsverzeichnis
Mapping of Core Information Model Classes
Bitte markieren Sie Kommentare zu diesem Abschnitt mit dem Code {MdaBs.01}
This section defines the XDS-Metadata bindings for the classes of the EFA core information model.
The following table describes how EFA classes MUST be mapped to classes and object types of IHE ITI.
EFA core information model | IHE ITI |
---|---|
Patient | Patient |
eCR CaseRecord | Set of Folder-objects, that have values of Folder.patientID and Folder.codeList in common |
eCR Partition | Folder |
eCR Medical Data Object | DocumentEntry for metadata, Document for binary data |
The object type SubmissionSet of IHE ITI has no corresponding class of the EFA core information model. Therefore, SubmissionSet SHALL be used as specified in IHE ITI but it MUST NOT have EFA semantics.
Mapping of PIM Classes
Bitte markieren Sie Kommentare zu diesem Abschnitt mit dem Code {MdaBs.01}
This section defines the XDS-Metadata bindings for the classes of the EFA platform independent model.
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.
EFA PIM | IHE ITI Metadata Model | Comments |
---|---|---|
patientID | Folder.patientId
DocumentEntry.patientId |
- |
communityID | DocumentEntry.homeCommunityId
Folder.homeCommunityId |
- |
purpose | Folder.codeList | see XDS Folder Metadata |
consentInfo | Document | 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 | Document | Consent documents are represented as documents of a format that is to be agreed by each ECR domain (e.g. PDF/A). |
partitionID | Folder.uniqueId | see IHE ITI TF Vol3 section 4.1.9.1 for details |
partitionList | set of Folder objects | - |
ecrRef | Folder.patientId
Folder.codeList Folder.homeCommunityId |
Folders that have the same patient ID and the same purpose codes form a distinct case record. The homeCommunityId indicates the XDS Affinity Domain where the reference is valid. |
partitionInfo | Folder | see XDS Folder Metadata for details |
docMetadata | DocumentEntry | see XDS Document Metadata for details |
docRelationship | Document Relationship | see Append and Replace in IHE ITI TF-3#4.1.2 |
documentID | DocumentEntry.uniqueId
DocumentEntry.repositoryUniqueId |
shall be used for document retrieval (retrieveDocument transaction). |
DocumentEntry.entryUUID | shall be used for document referral (associations between registry entries) |
MountPoint
Instances of the EFA PIM class MountPoint SHALL be bound to DocumentEntry as follows:
ECR PIM MountPoint attribute | IHE XDS Metadata Attribute | Comments |
---|---|---|
patientID | DocumentEntry.patientId | |
sourcePatientID | DocumentEntry.sourcePatientId | |
communityID | DocumentEntry.homeCommunityId |
The DocumentEntry SHALL be a member of a Folder. This Folder SHALL have a codeList classification containing
- (code="ECR-mountpoint", codeSystem="IHE-D-Cookbook-FolderClassCode") and
- a purpose code.
ecrStatus
The EFA PIM class ecrStatus MUST be implemented by means of access policies. The values of ecrStatus MUST correspond to access policies and system configuration as follows:
- Open
- The access policy implements the patient's consent.
- Suspended
- The access policy implements the patient's consent with the exception that only the consented case record manager and their substitutes are authorized.
- Retired
- No access policy permits access to the case record.
- Archived
- No XDS metadata and no documents reside in the EFA system.
The IHE ITI TF-3 states that the value of the XDS attribute Folder.availabilityStatus must always be Approved. Therefore, the lifecycle of case records does not correspond to this XDS attribute. |
Referenzen und Querverweise |