EFA Information Model IHE XD* Binding

Aus Hl7wiki
Implementierungsleitfaden
Wechseln zu: Navigation, Suche
(→‎Mapping of Core Information Model Classes)
(→‎Mapping of PIM Classes)
Zeile 63: Zeile 63:
 
|-
 
|-
 
|[[cdaefa:EFA_Business_Informationsmodell#ecrInfo|ecrInfo]]
 
|[[cdaefa:EFA_Business_Informationsmodell#ecrInfo|ecrInfo]]
−
| -
+
| see below
−
|As there is no correspondence to a case record object with IHE XD* this class is not mapped onto XDS. This is feasible because the ECR ecrInfo class does not contain any mandatory elements.
+
|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.
 
|-
 
|-
 
|[[cdaefa:EFA_Business_Informationsmodell#consentInfo|consentInfo]]
 
|[[cdaefa:EFA_Business_Informationsmodell#consentInfo|consentInfo]]
Zeile 105: Zeile 105:
 
| shall be used for document referral (associations between registry entries)
 
| shall be used for document referral (associations between registry entries)
 
|}
 
|}
 +
 +
 +
=== ecrInfo ===
 +
 +
{| class="wikitable"
 +
!Attribute
 +
!Description
 +
!Mapping onto IHE XD* metadata
 +
|-
 +
|[[cdaefa:EFA_Business_Informationsmodell#patientID|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 [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol3.pdf#page=41&zoom=auto,88,270 IHE ITI TF Volume 3, Section 4.2.3.1.3]).
 +
|-
 +
|[[#purpose|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 [[cdaefa:EFA_XDS_Folder_Metadata_Binding#codeList|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. 
 +
{| class="wikitable"
 +
!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
 +
|}
 +
|}
 +
 +
{{NoteBox|According to IHE ITI TF volume 3, the deprecation of Folders is not allowed. Therefore this value
 +
shall always be Approved. Nevertheless eCR takes this attribute into account as future versions of the ITI technical framework may allow for further options.
 +
}}
  
 
== Querverweise und Referenzen ==
 
== Querverweise und Referenzen ==
  
 
* [[cdaefa:EFA_Spezifikation_v2.0|EFA-2.0-Spezifikation]]
 
* [[cdaefa:EFA_Spezifikation_v2.0|EFA-2.0-Spezifikation]]

Version vom 16. November 2013, 21:16 Uhr

Logo-hl720.jpg
EFA Information Model IHE XD* Binding
EFA Information Model IHE XD* Binding
Implementierungsleitfaden
vorgelegt von:
February 2013
Jörg Caumanns, Raik Kuhlisch , Ben Kraufmann
Draft
Version: 0.9
Datum: March 2013
Status: xxx
Verfahren: {{{Verfahren}}}
Realm: Flag de.svg Deutschland
Copyright © 2012-2013: HL7 Deutschland


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 		-
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.
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 All folders classified with the same patient ID and purpose codes set up a unique case record.
partitionInfo XDSFolder object see XDS Folder Metadata for details
docMetadata XDSDocument registry object see XDS Document Metadata for details
docRelationship XDS Association object see IHE ITI TF Vol3 section 4.1.6 for details
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
Information icon.svg According to IHE ITI TF volume 3, the deprecation of Folders is not allowed. Therefore this value shall always be Approved. Nevertheless eCR takes this attribute into account as future versions of the ITI technical framework may allow for further options.

Querverweise und Referenzen

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