cdaefa:EFA XDS/XDR Bindings - Versionsgeschichte

Jcaumanns: /* Constraints and Triggers */

2016-02-14T20:57:01Z

‎Constraints and Triggers

Jcaumanns: Markup-Fehler behoben

2015-01-26T16:10:31Z

Markup-Fehler behoben

Jcaumanns: Formatanpassung für Print

2015-01-15T10:58:51Z

Formatanpassung für Print

Jcaumanns: Querverweise

2015-01-14T13:32:39Z

Querverweise

Jcaumanns: Verweis auf notifyOfConsent entfernt.

2014-09-16T19:13:10Z

Verweis auf notifyOfConsent entfernt.

Jcaumanns: Hinweis zur Gruppierung von Akteuren hinzugefügt.

2014-09-16T16:49:40Z

Hinweis zur Gruppierung von Akteuren hinzugefügt.

Jcaumanns: /* EFA XDR/XDS Binding */ Span und align korrigiert

2014-09-16T16:40:52Z

‎EFA XDR/XDS Binding: Span und align korrigiert

Jcaumanns: Tabelle der Akteurs-Bindings ergänzt.

2014-09-16T16:31:43Z

Tabelle der Akteurs-Bindings ergänzt.

Jcaumanns: Tabelle der Akteurs-Bindings korrigert.

2014-09-16T16:15:15Z

Tabelle der Akteurs-Bindings korrigert.

Jcaumanns: Seitentemplate an Konvention angepasst.

2014-09-09T13:55:07Z

Seitentemplate an Konvention angepasst.

← Nächstältere Version		Version vom 14. Februar 2016, 20:57 Uhr
Zeile 193:		Zeile 193:
	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.}}		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.}}

		+	=== IHE XDS Options ===
		+
		+	The table below shows which IHE XDS options apply to EFA.
		+
		+	{\|class="wikitable"
		+	!XDS Option
		+	!Use for EFA
		+	!Remarks
		+	\|-
		+	\|Document Replacement
		+	\|SHOULD NOT be used
		+	\|EFA clients may replace documents within any dedicated peer. In order to minimize complexity of peer-to-peer deployments, this option may only be used for replacing own documents. It must not be used for replacing documents that have been provided to EFA by another user.
		+	\|-
		+	\|Document Addendum
		+	\|MUST NOT be used
		+	\|This option does not work for EFA peer-to-peer deployments and therefore must not be used.
		+	\|-
		+	\|Document Transformation
		+	\|MUST NOT be used
		+	\|This option does not work for EFA peer-to-peer deployments and therefore must not be used.
		+	\|-
		+	\|Folder Management
		+	\|SHALL be implemented
		+	\|EFA access control builds upon folders. Therefore the implementation of this option is indispensible for EFA compliant systems.
		+	\|-
		+	\|Basic Patient Privacy Enforcement
		+	\|MUST NOT be used
		+	\|EFA requires full and written consent to be given by the patient. BPPC-style consents must not be used for EFA. Respective requests (e.g. providing or requesting a BPPC document) shall be ignored by all EFA actors.
		+	\|-
		+	\|Asynchronous Web Services Exchange
		+	\|MAY be used
		+	\|EFAv2.0 does not constrain the use of this option.
		+	\|-
		+	\|Reference-ID
		+	\|SHOULD be implemented
		+	\|EFA implementations may use the referenceIDList for linking related documents. In this case the FindDocumentsByReferenceId Query may be used for discovering related documents to a given document.
		+	\|-
		+	\|On-Demand Documents
		+	\|MAY be used
		+	\|EFAv2.0 does not constrain the use of this option.
		+	\|-
		+	\|Persistence of Retrieved Documents
		+	\|MAY be used
		+	\|EFAv2.0 does not constrain the use of this option.
		+	\|-
		+	\|Limited Metadata
		+	\|Not applicable because EFA builds upon IHE XDS for which limited metadata is not permitted.
		+	\|
		+	\|}

@@ Zeile 200: / Zeile 200: @@
 {{NoteBox|'''Referenzen und Querverweise'''
 * [[cdaefa:EFA_Spezifikation_v2.0|EFA-2.0-Spezifikation]]
 }}

@@ Zeile 152: / Zeile 152: @@
 {|class="wikitable" style="text-align: left; cellpadding: 10;"
-!Transaction
+!rowspan="2"|Constraints
 !colspan="5"|Triggers for bindings
 |-
 !createECR
 !closeECR

← Nächstältere Version		Version vom 14. Januar 2015, 13:32 Uhr
Zeile 196:		Zeile 196:
	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.}}		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 ==~~

		+
		+	----
		+
		+
		+	{{NoteBox\|'''Referenzen und Querverweise'''
	* [[cdaefa:EFA_Spezifikation_v2.0\|EFA-2.0-Spezifikation]]		* [[cdaefa:EFA_Spezifikation_v2.0\|EFA-2.0-Spezifikation]]
		+	}}

@@ Zeile 112: / Zeile 112: @@
 |Provide and Register Document Set ITI-41
 |[[cdaefa:EFA_XDS_ResourceManager#EFA_XDS.2FXDR_Binding:_registerConsent|registerConsent]]
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#listRecordLocations|listRecordLocations]]

@@ Zeile 81: / Zeile 81: @@
 out-bound: listPartitions, listPartitionContent
 |}
 The EFA operations MUST be bound to IHE-ITI transactions as follows:
 {|class="wikitable" style="text-align: left; cellpadding: 10;"
 |-
-|EFA Service Functional Model
+|'''EFA Service Functional Model'''
-|IHE XDS/XDR
+|'''IHE-ITI Profile'''
-|Binding
+|'''Binding'''
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#createECR|createECR]]

@@ Zeile 16: / Zeile 16: @@
 |'''IHE-ITI actors'''
 |'''Operations'''
-|-
+|- style="vertical-align:top;"
 |rowspan="2"|EFA Client
 |Document Source
@@ Zeile 23: / Zeile 23: @@
 |Document Consumer
 |out-bound: listPartitions, listPartitionContents, retrieveData
-|-
+|- style="vertical-align:top;"
-|EFA Resource Manager
+|rowspan="5"|EFA Resource Manager
 |Document Repository
 |in-bound: createECR, closeECR, registerConsent
 |-
 |Document Source
 |out-bound: registerRecordLocation
 |-
 |Document Recipient
 |in-bound: registerRecordLocation
 |-
 |Initiating Gateway
@@ Zeile 42: / Zeile 39: @@
 |out-bound: listRecordLocations
 |-
 |Responding Gateway
 grouped with Document Consumer (see IHE-ITI-TF-Vol1#18.2.3.2)
 |in-bound: listRecordLocations
-|-
+|- style="vertical-align:top;"
-|EFA Document Registry
+|rowspan="3"|EFA Document Registry
 |Document Registry
 |in-bound: listPartitions, listPartitionContent, registerData
 |-
 |Initiating Gateway
@@ Zeile 60: / Zeile 55: @@
 out-bound: listPartitions, listPartitionContent
 |-
 |Responding Gateway
@@ Zeile 67: / Zeile 61: @@
 out-bound: listPartitions, listPartitionContent
-|-
+|- style="vertical-align:top;"
-|EFA Document Repository
+|rowspan="3"|EFA Document Repository
 |Document Repository
 |in-bound: createPartition, provideData, retrieveData
@@ Zeile 74: / Zeile 68: @@
 out-bound: registerData
 |-
 |Initiating Gateway
@@ Zeile 82: / Zeile 75: @@
 out-bound: retrieveData
 |-
 |Responding Gateway

@@ Zeile 9: / Zeile 9: @@
 This section specifies the binding of the [[cdaefa:EFA_Dienste|EFA components]] to IHE-ITI actors and the binding of the [[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)|EFA operations]] to IHE-ITI transactions.
-The [[cdaefa:EFA_Dienste|EFA actors]] SHALL be bound to IHE-ITI actors as follows:
+The [[cdaefa:EFA_Dienste|EFA actors]] MUST be bound to IHE-ITI actors as follows:
 {|class="wikitable" style="text-align: left; cellpadding: 10;"
@@ Zeile 27: / Zeile 27: @@
 |Document Repository
 |in-bound: createECR, closeECR, registerConsent
 |-
 |EFA Document Registry
@@ Zeile 70: / Zeile 90: @@
 out-bound: listPartitions, listPartitionContent
 |}
-In detail, EFA operations MUST be bound to IHE-ITI transactions as follows:
+The EFA operations MUST be bound to IHE-ITI transactions as follows:
 {|class="wikitable" style="text-align: left; cellpadding: 10;"
-!EFA Service Functional Model
+|-
-!IHE XDS/XDR
+|EFA Service Functional Model
-!Binding
+|IHE XDS/XDR
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#createECR|createECR]]
 |Provide and Register Document Set ITI-41
 |[[cdaefa:EFA_XDS_ResourceManager#EFA_XDS.2FXDR_Binding:_createECR|createECR]]
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#createPartition|createPartition]]
 |Provide and Register Document Set ITI-41
 |[[cdaefa:EFA_XDS_ResourceManager#EFA_XDS.2FXDR_Binding:_createPartition|createPartition]]
 |-
@@ Zeile 90: / Zeile 111: @@
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#listPartitions|listPartitions]]
-|Registry Stored Query [ITI-18]
+|Registry Stored Query ITI-18
 |[[cdaefa:EFA_XDS_ResourceManager#EFA_XDS_Binding:_listPartitions|listPartitions]]
 |-
@@ Zeile 118: / Zeile 139: @@
 |-
 |[[cdaefa:EFA_Anwendungsdienste_(logische_Spezifikation)#provideData|provideData]]
 |Provide and Register Document Set ITI-41
 |[[cdaefa:EFA_XDS_DocumentRepository#EFA_XDS_Binding:_provideData|provideData]]
 |-
@@ Zeile 125: / Zeile 146: @@
 |[[cdaefa:EFA_XDS_DocumentRepository#EFA_XDS_Binding:_retrieveData|retrieveData]]
 |}
 === Constraints and Triggers ===

@@ Zeile 1: / Zeile 1: @@
-{{Infobox Dokument
+{{DocumentPart
 }}
 ''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.<br>Hinweise zum Kommentierungsverfahren einschließlich aller Formulare und Kontaktadressen finden Sie auf der Seite "[[cdaefa:Kommentierung EFAv2.0|Kommentierung EFAv2.0]]".''
 ----