EFA XDS/XDR Binding

Aus Hl7wiki
Implementierungsleitfaden
Wechseln zu: Navigation, Suche
(→‎Constraints and Triggers: Verhalten für Hybrid-Systeme)
(→‎Constraints and Triggers: Clarified Constraints on ITI-Transactions for EFA operation bindings.)
Zeile 97: Zeile 97:
 
=== Constraints and Triggers ===
 
=== Constraints and Triggers ===
  
−
The IHE ITI-41 and ITI-18 transactions are profiled by multiple EFA logical operations. The following table defines how an XDS/XDR document repository (document recipient) or document registry can decide by an incoming message which EFA operations binding is addressed.
+
Multiple logical operations of the EFA Resource Manager are bound to the IHE transactions ITI-18 and ITI-41. The addressed EFA operation binding must be determined by a set of constraints that a ITI-18-request or ITI-41-request satisfies. The distinct sets of constraints for the EFA operation bindings are defined in the table below. A cross in a EFA-operation-column marks a constraint as required.
 +
 
 +
Requests that do not satisfy one of the given sets of requirements are not valid EFA requests. In this case the XDS Document Registry and XDS Document Repository MUST respond with an error.
 +
 
  
 
{|class="wikitable" style="text-align: left; cellpadding: 10;"
 
{|class="wikitable" style="text-align: left; cellpadding: 10;"
−
!Transaction
+
!
−
!Flavour
+
!colspan="5"|Requirement set for EFA operation bindings
−
!Trigger
+
|-
−
!EFA behavior
+
!Constraints on ITI-41
 +
!createECR
 +
!closeECR
 +
!registerConsent
 +
!createPartition
 +
!provideData
 +
|-
 +
|Exactly one XDS-Folder is provided
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 +
|-
 +
|All XDS-Documents are associated with an XDS-Folder
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 
|-
 
|-
−
|ITI-41
+
|The XDS-Folder is classified as EFA-Folder via XDSFolder.codeList
−
| -
+
| align="center"|X
−
|provided documents are not associated with a folder
+
| align="center"|X
−
|The EFA document repository/recipient SHALL respond with an error. This request is not defined for EFA as each provided document shall be associated with a folder (partition).
+
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 
|-
 
|-
−
|ITI-41
+
|One XDS-Document is a consentInfo which gives a new consent or does not revoke all active consents
−
| -
+
| align="center"|X
−
|documents provided are associated with a folder. The folder codeList does not signal an EFA folder. 
+
|
−
|EFA document repository/recipient SHALL respond with an error. This request is not defined for EFA as non-EFA folders are not covered by the EFA access control model.
+
| align="center"|X
 +
|
 +
|
 +
|-  
 +
|One XDS-Document is a consentInfo, which revokes all active consents
 +
|
 +
| align="center"|X
 +
|
 +
|
 +
|  
 
|-
 
|-
−
|ITI-41
+
|The provided XDSFolder and a registered XDSFolder  have the XDSFolder.codeList and XDSFolder.patientID in common (i.e. the EFA exists)
−
| -
+
|
−
|a consent (consentInfo) is included within the set of provided documents
+
| align="center"|X
−
|depending on the type of consent the createECR, closeECR or registerConsent binding shall be enforced. closeECR and registerConsent require that the provided folder codeList signals an existing EFA instance.
+
| align="center"|X
 +
| align="center"|X
 +
| align="center"|X
 
|-
 
|-
−
|ITI-41
+
|The XDSFolder is not registered (uniqueID)
−
| -
+
| align="center"|X
−
|The folder associated to the provided documents does not exist
+
|  
−
|The document repository/recipient shall enforce the createPartiton binding
+
|  
 +
| align="center"|X
 +
|
 
|-
 
|-
 +
|The XDSFolder is registered (uniqueID)
 +
|
 +
|
 +
|
 +
|
 +
| align="center"|X
 
|-
 
|-
−
|ITI-41
+
!Constraints on ITI-18
−
| -
+
!listPartitions
−
|any other condition
+
!listData
−
|The document repository/recipient shall enforce the provideData binding
+
!colspan="3"|  
 
|-
 
|-
−
|ITI-18
+
|Flavor FindFolder
−
|FindFolder
+
| align="center"|X
−
| -
+
|  
−
|The document registry shall enforce the listPartitons binding
+
|colspan="3"|
 
|-
 
|-
−
|ITI-18
+
|Flavor GetFolderAndContents
−
|GetFolderAndContents
+
|  
−
| -
+
| align="center"|X
−
|The document registry shall enforce the listData binding
+
|colspan="3"|
 
|-
 
|-
−
|ITI-18
 
−
|any other flavor
 
−
| -
 
−
|the document registry shall respond with an error as other flavors than FindFolder and GetFolderAndContents shall not be implemented by an EFA compliant document registry.
 
 
|}
 
|}
  

Version vom 18. Dezember 2013, 22:35 Uhr

Logo-hl720.jpg
EFA XDS/XDR Binding
EFA XDS/XDR Binding
Implementierungsleitfaden
vorgelegt von:
February 2013
Jörg Caumanns, Raik Kuhlisch
Draft
Version: 0.9
Datum: March 2013
Status: xxx
Verfahren: {{{Verfahren}}}
Realm: Flag de.svg Deutschland
Copyright © 2012-2013: HL7 Deutschland


Anmerkung: Die Kürzel unter den einzelnen Überschriften 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".

EFA XDR/XDS Binding

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

Within EFA the actors and transactions of the IHE XDS/XDR integration profiles are mapped onto EFA logical services and operations as follows:

Role EFA Service Functional Model IHE XDS/XDR Binding
Actor EFA Client Document Source (for createECR, createPartition, closeECR, registerConsent, provideData)
Document Consumer (for listPartitions, retrieveData) 		-
Actor EFA Resource Manager Document Repository implementing Document Recipient (for createECR, createPartition, closeECR, registerConsent)
Document Registry (for listPartitions) 		-
Actor EFA Document Registry XDS Document Registry -
Actor EFA Document Repository XDS Document Repository (implementing Document Recipient for provideData) -
Transaction createECR Provide and Register Document Set ITI-41 createECR
Transaction createPartition Provide and Register Document Set ITI-41 createPartition
Transaction closeECR Provide and Register Document Set ITI-41 closeECR
Transaction listPartitions Registry Stored Query ITI-18 listPartitions
Transaction registerConsent Provide and Register Document Set ITI-41 registerConsent
Transaction registerData Register Document Set ITI-42 registerData
Transaction listData Registry Stored Query ITI-18 listData
Transaction provideData Provide and Register Document Set ITI-41 provideData
Transaction retrieveData Retrieve Document Set ITI-43 retrieveData

Constraints and Triggers

Multiple logical operations of the EFA Resource Manager are bound to the IHE transactions ITI-18 and ITI-41. The addressed EFA operation binding must be determined by a set of constraints that a ITI-18-request or ITI-41-request satisfies. The distinct sets of constraints for the EFA operation bindings are defined in the table below. A cross in a EFA-operation-column marks a constraint as required.

Requests that do not satisfy one of the given sets of requirements are not valid EFA requests. In this case the XDS Document Registry and XDS Document Repository MUST respond with an error.


Requirement set for EFA operation bindings
Constraints on ITI-41 createECR closeECR registerConsent createPartition provideData
Exactly one XDS-Folder is provided X X X X X
All XDS-Documents are associated with an XDS-Folder X X X X X
The XDS-Folder is classified as EFA-Folder via XDSFolder.codeList X X X X X
One XDS-Document is a consentInfo which gives a new consent or does not revoke all active consents X X
One XDS-Document is a consentInfo, which revokes all active consents X
The provided XDSFolder and a registered XDSFolder have the XDSFolder.codeList and XDSFolder.patientID in common (i.e. the EFA exists) X X X X
The XDSFolder is not registered (uniqueID) X X
The XDSFolder is registered (uniqueID) X
Constraints on ITI-18 listPartitions listData
Flavor FindFolder X
Flavor GetFolderAndContents X
Attention icon.svg Hybrid EFA/non-EFA systems should verify that a request is an EFA request prior to processing it with EFA semantics. Non-EFA requests MUST be rejected with an error message if processed with EFA semantics.

Querverweise und Referenzen

Abgerufen von „https://wiki.hl7.de/index.php?title=cdaefa:EFA_XDS/XDR_Bindings&oldid=16718“