cdaefa:EFA XDS DocumentRepository - Versionsgeschichte

Jcaumanns: /* Constraints on the Request Message */

2015-11-02T15:30:24Z

‎Constraints on the Request Message

Jcaumanns: Markup-Fehler behoben

2015-01-26T16:11:36Z

Markup-Fehler behoben

Jcaumanns: Querverweise

2015-01-14T13:43:24Z

Querverweise

Jcaumanns: /* Expected Actions */

2014-12-15T11:53:55Z

‎Expected Actions

Jcaumanns: /* EFA XDS Binding: provideData */

2014-10-15T13:57:28Z

‎EFA XDS Binding: provideData

Jcaumanns: Links zu Security Considerations eingefügt.

2014-09-16T18:09:34Z

Links zu Security Considerations eingefügt.

Jcaumanns: Seitentemplate an Konvention angepasst.

2014-09-09T13:56:11Z

Seitentemplate an Konvention angepasst.

Jcaumanns: /* Constraints on the Request Message */ Added table for constraints that trigger the binding.

2013-12-20T14:40:14Z

‎Constraints on the Request Message: Added table for constraints that trigger the binding.

Jcaumanns: /* Constraints on the Request Message */ Fixed Typo: DocumentResponse -> DocumentRequest

2013-11-25T16:40:36Z

‎Constraints on the Request Message: Fixed Typo: DocumentResponse -> DocumentRequest

Jcaumanns: /* Response Message (Failure or Partial Failure Scenario) */ Provide document reference ist jetzt zulässig

2013-11-18T15:47:14Z

‎Response Message (Failure or Partial Failure Scenario): Provide document reference ist jetzt zulässig

@@ Zeile 188: / Zeile 188: @@
 |-
 |[[cdaefa:EFA_Business_Informationsmodell#documentID|documentID]]
-|DocumentRequest/repositoryUniqueId<br>DocumentRequest/documentUniqueId
+|DocumentRequest/RepositoryUniqueId<br>DocumentRequest/DocumentUniqueId
 |The requestor SHALL provide these unique IDs as obtained when the contents of an ECR partition were intially listed.
 |-
 |[[cdaefa:EFA_Business_Informationsmodell#docData|docData]]
-|DocumentResponse/document
+|DocumentResponse/Document
 | -
 |}

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

@@ Zeile 4: / Zeile 4: @@
 ----
-== EFA Document Repository XDS Binding ==
+=== EFA Document Repository XDS Binding ===
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.01}</tt>
@@ Zeile 31: / Zeile 31: @@
 |}
-== EFA XDS Binding: provideData ==
+==== EFA XDS Binding: provideData ====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02}</tt>
@@ Zeile 41: / Zeile 41: @@
 * The application of security measures and the contents of the SOAP security header are specified normatively
-=== Constraints on the Request Message ===
+===== Constraints on the Request Message =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02.01}</tt>
@@ Zeile 71: / Zeile 71: @@
 |}
-=== Expected Actions ===
+===== Expected Actions =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02.02}</tt>
@@ Zeile 82: / Zeile 82: @@
 In case of an error that relates to the transmission of the request or the processing of the EFA security token, the EFA Document Registry Service provider MUST respond with a fault message according to section xx.
-=== Response Message (Full Success Scenario) ===
+===== Response Message (Full Success Scenario) =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02.03}</tt>
@@ Zeile 116: / Zeile 116: @@
 |}
-=== Response Message (Failure or Partial Failure Scenario) ===
+===== Response Message (Failure or Partial Failure Scenario) =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02.04}</tt>
@@ Zeile 158: / Zeile 158: @@
 |}
-=== Security Considerations ===
+===== Security Considerations =====
 See [[cdaefa:EFA_XDS_SecurityConsiderations|Security Considerations]].
-== EFA XDS Binding: retrieveData ==
+==== EFA XDS Binding: retrieveData ====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03}</tt>
@@ Zeile 171: / Zeile 171: @@
 * The application of security measures and the contents of the SOAP security header are specified normatively
-=== Constraints on the Request Message ===
+===== Constraints on the Request Message =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03.01}</tt>
@@ Zeile 199: / Zeile 199: @@
 * The data to be retrieved SHALL all be associated with the same XDS Folder. It SHALL be classified as an ECR partition.
-==== Example ====
+====== Example ======
 <syntaxhighlight lang="xml">
@@ Zeile 210: / Zeile 210: @@
 </syntaxhighlight>
-=== Expected Actions ===
+===== Expected Actions =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03.02}</tt>
@@ Zeile 222: / Zeile 222: @@
 In case of an error that relates to the transmission of the request or the processing of the EFA security token, the XDS Document Registry MUST respond with the respective error status.
-=== Response Message (Full Success Scenario) ===
+===== Response Message (Full Success Scenario) =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03.03}</tt>
 If the EFA Document Repository Service provider is able to decode and process the received message it responds with the discovered documents acc. to the specification of the ITI-43 response message.
-=== Response Message (Failure or Partial Failure Scenario) ===
+===== Response Message (Failure or Partial Failure Scenario) =====
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03.04}</tt>
@@ Zeile 269: / Zeile 269: @@
 |}
-=== Security Considerations ===
+===== Security Considerations =====
 See [[cdaefa:EFA_XDS_SecurityConsiderations|Security Considerations]].
 * [[cdaefa:EFA_Spezifikation_v2.0|EFA-2.0-Spezifikation]]

@@ Zeile 213: / Zeile 213: @@
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.03.02}</tt>
 The XDS Document Repository SHALL respond to a Retrieve Document Set request message with the Retrieve Document Set response message containing a success indicator and listing all requested documents. The provider of the XDS Document Repository MUST verify that the requestor has sufficient rights to access the requested documents.
 In processing of this request the ECR Provider SHALL
 * assess the access control policy of the [[cdaefa:EFA_Business_Informationsmodell#ecrRef|ecrRef]] object that is assigned with the XDS Folder that is associated to the requested documents. If a document is not associated with an XDS Folder or if no ecrRef object is assigned to the XDS Folder, the XDS Document Repository MUST respond with a "policy violation" error.
 * respond to the requestor with the requested documents.

@@ Zeile 34: / Zeile 34: @@
 <tt>Bitte markieren Sie [[cdaefa:Kommentierung_EFAv2.0|Kommentare]] zu diesem Abschnitt mit dem Code {EXoce.02}</tt>
-Providing a document to an ECR provider's repository service is bound to the IHE ''Provide and Register Document Set'' transaction (ITI-41). This EFA binding introduces minor extensions and restrictions on the respective XDS actor and transaction definitions in order to properly cover the EFA use cases and to align with the EFA security framework:
+Providing a document to an ECR provider's repository service is bound to the IHE ''Provide and Register Document Set'' transaction (ITI-41). This ECR binding introduces minor extensions and restrictions on the respective XDS actor and transaction definitions in order to properly cover the EFA use cases and to align with the EFA security framework:
 * Documents must be associated with an XDS Folders, i.e an ECR partition, which in turn is part of an ECR that carries the permissions for accessing data.
 * Additional error messages are defined that cover specific failure conditions of the EFA use cases
 * The availability of data fields is aligned to EFA privacy requirements

@@ 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]]".''
 ----

@@ Zeile 59: / Zeile 59: @@
 The ProvideAndRegisterDocument request message is issued by an EFA client at the point of care for providing and registering a medical document to an existing ECR partition. Each transmission carries one or more documents. All provided documents will be registered with the same XDS Folder within the same logical EFA.
-The request message implements the IHE Provide And Register DocumentSet transaction (ITI-41) request message as profiled in [IHE ITI TF-2b] considering the following constraints:
-* Each provided document SHALL be associated with an XDS Folder.
+The request message implements the IHE Provide And Register DocumentSet transaction (ITI-41) request message as profiled in [IHE ITI TF-2b]. Implementations SHALL satisfy
-* The target XDS Folder SHALL be available in advance to this transaction. All provided documents SHALL be associated with the same XDS Folder (these restrictions ensure the proper implementation of the [[cdaefa:EFA_Document_Repository_SFM|EFA Document Repository SFM]] which implies the existence of a ECR partition and only allows for a single partitionID to be included with the request).
+* the [[cdaefa:EFA_XDS/XDR_Bindings#Common_constraints_on_ITI-41|Common constraints on ITI-41]],
-* The requestor (EFA Client) SHOULD provide documents embraced by a single IHE XDS submission set acc. to [IHE ITI TF-2a].
+* the distinct set of constraints which trigger this binding, given in the table below (R = required, O = optional, - = forbidden).
-* All metadata of the submission set and all associations between documents and submission sets MUST NOT have EFA semantics. The EFA Provider MUST solely rely on the document metadata and contents.
-* The EFA provider MUST NOT register documents that are only provided through metadata and/or associations.
+{|class="wikitable" style="text-align: left; cellpadding: 10;"
 === Expected Actions ===

@@ Zeile 151: / Zeile 151: @@
 |4109
 |The provided document MUST NOT be processed by the service provider. The HP MAY request the patient to extend the consent.
 |}