EFA XDS/XDR Binding
(→Constraints and Triggers) |
(→Constraints and Triggers: Allow Warning for hybrid systems, if folder for document not provided.) |
||
| Zeile 108: | Zeile 108: | ||
| - | | - | ||
|provided documents are not associated with a folder | |provided documents are not associated with a folder | ||
| − | |EFA document repository/recipient | + | |EFA document repository/recipient SHOULD respond with an error as each provided document shall be associated with a folder (partition). In case of a hybrid EFA/Non-EFA system, the EFA document repository/recipient SHALL respond with a warning, if an error would interfere with Non-EFA behavior. |
|- | |- | ||
|ITI-41 | |ITI-41 | ||
Version vom 7. November 2013, 17:49 Uhr
 |
Dieses Dokument gibt wieder:
Implementierungsleitfaden EFA XDS/XDR Binding (0.9). Die Teilmaterialien gehören der Kategorie cdaefa an. |
February 2013
Jörg Caumanns, Raik Kuhlisch
| Version: | 0.9 |
| Datum: | March 2013 |
| Status: | xxx |
| Verfahren: | {{{Verfahren}}} |
| Realm: |  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
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.
| Transaction | Flavour | Trigger | EFA behavior |
|---|---|---|---|
| ITI-41 | - | provided documents are not associated with a folder | EFA document repository/recipient SHOULD respond with an error as each provided document shall be associated with a folder (partition). In case of a hybrid EFA/Non-EFA system, the EFA document repository/recipient SHALL respond with a warning, if an error would interfere with Non-EFA behavior. |
| ITI-41 | - | documents provided are associated with a folder. The folder codeList does not signal an EFA folder. | EFA document repository/recipient responds with an error as non-EFA folders are not covered by the EFA access control model. |
| ITI-41 | - | a consent (consentInfo) is included within the set of provided documents | 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. |
| ITI-41 | - | The folder associated to the provided documents does not exist | The document repository/recipient shall enforce the createPartiton binding |
| ITI-41 | - | any other condition | The document repository/recipient shall enforce the provideData binding |
| ITI-18 | FindFolder | - | The document registry shall enforce the listPartitons binding |
| ITI-18 | GetFolderAndContents | - | The document registry shall enforce the listData binding |
| 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. |
