EFA XDS/XDR Binding

Aus Hl7wiki
Implementierungsleitfaden
Wechseln zu: Navigation, Suche
(EFA XDR/XDS Binding: Links korrigiert und Operationen für Use Case Offline-Token hinzugefügt.)
(EFA XDR/XDS Binding: Diagramme hinzugefügt, die Actor-Binding beschreiben)
Zeile 20: Zeile 20:
 
== EFA XDR/XDS Binding ==
 
== EFA XDR/XDS Binding ==
 
<tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EDXDg.01}</tt>
 
<tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EDXDg.01}</tt>
 +
 +
[[Datei:EFA-Actor-Bindings.png|583px]]
 +
 +
[[Datei:EFA-Actor-Bindings-P2P.png|765px]]
  
 
Within EFA the actors and transactions of the IHE XDS/XDR integration profiles are mapped onto EFA logical services and operations as follows:
 
Within EFA the actors and transactions of the IHE XDS/XDR integration profiles are mapped onto EFA logical services and operations as follows:

Version vom 18. Juni 2014, 15:22 Uhr


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}

EFA-Actor-Bindings.png

EFA-Actor-Bindings-P2P.png

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 notifyOfConsent Document Metadata Notify ITI-53
Transaction issueAccessToken
Transaction redeemAccessToken
Transaction listRecordLocations Patient Location Query ITI-56
Transaction registerRecordLocation Patient Identity Feed HL7 V3 ITI-44
Transaction registerData Register Document Set ITI-42 registerData
Transaction listPartitionContent Registry Stored Query ITI-18 listPartitionContent
Transaction provideData Provide and Register Document Set ITI-41 provideData
Transaction retrieveData Retrieve Document Set ITI-43 retrieveData

Constraints and Triggers

The EFA XDS/XDR Bindings bind multiple operations of the EFA Service Functional Model to the IHE transactions ITI-18 and ITI-41. Thus, the XDS Document Repository or XDS Document Registry must determine the intended binding with the set of constraints that is valid for a request message. All request messages must satisfy

  • a set of common constraints on the ITI-Transaction and
  • a distinct set of constraint which triggers a binding.

A ITI-18 request or ITI-41 request is invalid if both conditions are not met. In this case the XDS Document Registry and XDS Document Repository respectively MUST respond with an error.

Common constraints on ITI-41

  • The request MUST contain exactly one XDS Folder.
  • The XDS Folder MUST satisfy the EFA XDS Folder Metadata Binding.
  • The request MUST contain at least one XDS Document
  • All XDS Documents MUST satisfy the EFA XDS Document Metadata Binding.
  • All XDS Documents MUST be a member of the XDS Folder.
  • The following object types MUST NOT have EFA semantics:
    • SubmissionSet,
    • HasMember (1),
    • HasMember (3) and
    • HasMember (4) (see IHE-ITI-TF-Vol3 4.1.2).

Triggers

The distinct sets of constraints for the bindings are defined in the table below (R = required, O = optional, - = forbidden).

Transaction Constraints Triggers for EFA XDS/XDR bindings
ITI-41 createECR closeECR registerConsent createPartition provideData
One XDS-Document is a consentInfo which gives a new consent or does not revoke all active consents R - R - -
One XDS-Document is a consentInfo, which revokes all active consents - R - - -
The provided XDSFolder and a registered XDSFolder have the XDSFolder.codeList and XDSFolder.patientID in common (i.e. the EFA exists) - R R R R
The XDSFolder is not registered (uniqueID) R O O R -
The XDSFolder is registered (uniqueID) - O O - R
ITI-18 listPartitions listPartionContent
Query Name: FindFolders [IHE ITI TF-2a#3.18.4.1.2.3.7.3] R -
Query Name: GetFolderAndContents [IHE ITI TF-2a#3.18.4.1.2.3.7.11] - R

Querverweise und Referenzen