diff --git a/EPR-ADR-Simulator/user.md b/EPR-ADR-Simulator/user.md
index 943855368695091370dbe2a0953424cd6e4adc2d..0de214df0dde39541e202ec4ac4b9197b5c463c6 100755
--- a/EPR-ADR-Simulator/user.md
+++ b/EPR-ADR-Simulator/user.md
@@ -4,9 +4,9 @@ subtitle: ADR Simulator
author: Youn Cadoret
function: Developer
date: 02/06/2019
-toolversion: 1.2
+toolversion: 1.3
version: 1.0
-status: To be reviewed
+status: Approved Document
reference: KER1-MAN-IHE-ADR_SIMULATOR_-0_01
customer: IHE-EUROPE
---
@@ -17,13 +17,13 @@ eHealthSuisse ADR Provider MockUp
eHealthSuisse ADR Provider MockUp simulates a CH:ADR Provider actor.
ADR provider, will allow to manage access policy to the clinical data stored by an XDS Document Registry as well as to the access policies themselves, which are stored in a Policy Repository.
-With the information insert in to the request, the ADR provider will could determine if user can access to the information or no, with decision like **"Permit"**, **"NotApplicable"**, **"Deny"** or **"Indeterminate"**.
+With the information insert into the request, the ADR provider could determine if user can access to the information or not, with decision like **"Permit"**, **"NotApplicable"**, **"Deny"** or **"Indeterminate"**.
+
+Whether it will be for the access request XDS, ATC or PPQ, the ADR request is build in two parts.
+The first part,that we will call "Subject", allows to inform information on user with a ID,a homeCommunity and the qualification id.
+Finally, the second part, that we will call "Resource", allows to inform information on the patient, like his identification.
-Whether it be for the access request XDS, ATC or PPQ, the ADR request is build in two parts.
-The first part,that we will call "Subject", allow to inform information on user with a ID,a homeCommunity and the qualification id.
-Finally, the second part, that we will call "Resource", allow to inform information on the patient, like his identification.
-
* **Permit**: the evaluation was successful.
* **NotApplicable**: the evaluation was successful, but the patient no granted rights to the subject.
@@ -48,7 +48,7 @@ Finally, the second part, that we will call "Resource", allow to inform informat
| 761337610436974489 | 2.16.756.5.30.1.127.3.10.3 | urn:oid:1.3.6.1.4.1.21367.2017.2.6.2 | lavdic |
| 761337610435209810 | 2.16.756.5.30.1.127.3.10.3 | urn:oid:1.3.6.1.4.1.21367.2017.2.6.2 | bovie |
-
+
### End Point
@@ -158,7 +158,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### Request example for ADR due to PPQ
@@ -226,7 +226,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### Request example for ADR due to ATC
@@ -297,4 +297,4 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
## Mock messages on GWT
-The mock messages feature is available for this mock from 1.3.0 version.
+The mock messages feature is available for this mock from 1.3.0 version.
diff --git a/EPR-PPQ-Simulator/user.md b/EPR-PPQ-Simulator/user.md
index fa79f2e0e15fd2e4f975906f64941b5fc8b8ea1f..6c6e0f89d62233d304b60b7852099eaacc646672 100755
--- a/EPR-PPQ-Simulator/user.md
+++ b/EPR-PPQ-Simulator/user.md
@@ -4,9 +4,9 @@ subtitle: PPQ Simulator
author: Youn Cadoret
function: Developer
date: 02/06/2019
-toolversion: 1.2
+toolversion: 1.3
version: 1.0
-status: To be reviewed
+status: Approved Document
reference: KER1-MAN-IHE-PPQ_SIMULATOR_-0_01
customer: IHE-EUROPE
---
@@ -18,12 +18,12 @@ eHealthSuisse PPQ Repository MockUp
eHealthSuisse PPQ Repository MockUp simulates a PPQ Repository actor.
PPQ transactions are used by the policy source to add, update or delete policies stored in a policy repository
-and used policy consumer to retrieve policies in the repository.
-to do that, PPQ is build around of four different requests : **XACMLPolicyQuery, AddPolicyRequest, UpdatePolicyRequest** and **DeletePolicyRequest**
+and use policy consumer to retrieve policies in the repository.
+To do that, PPQ is build around of four different requests : **XACMLPolicyQuery, AddPolicyRequest, UpdatePolicyRequest** and **DeletePolicyRequest**
**XACMLPolicyQuery :**
The Policy Consumer sends this message when it needs to retrieve existing XACML policies
-or policy sets of a patient stored byin a Policy Repository (of the patients referenceCommunity).
+or policy sets of a patient stored in a Policy Repository (of the patients referenceCommunity).
**AddPolicyRequest** and **UpdatePolicyRequest :**
The Policy Source sends these messages when it needs to add new or update existing
@@ -33,7 +33,7 @@ policies and/or policy sets stored within the Policy Repository (of a patients r
The Policy Source sends these messages when it needs to delete existing patient-specific
policy sets stored within the Policy Repository (of a patient?s referenceCommunity).
-
+
### Data Set
@@ -63,7 +63,7 @@ policy sets stored within the Policy Repository (of a patient?s referenceCommuni
It requires TLS mutual authentication with testing certificate (from GSS PKI). [The wsdl can be browsed here](/ppq-repository?wsdl)
-
+
### XACMLPolicyQuery with Patient ID example
@@ -98,7 +98,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### XACMLPolicyQuery with PolicySetIdReference example
@@ -122,7 +122,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### AddPolicyRequest example
@@ -188,7 +188,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### UpdatePolicyRequest example
@@ -254,7 +254,7 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
</soap:Body>
</soap:Envelope>
```
-
+
### DeletePolicyRequest example
@@ -287,4 +287,4 @@ It requires TLS mutual authentication with testing certificate (from GSS PKI). [
```
## Mock messages on GWT
-The mock messages feature is available for this mock from 1.3.0 version.
+The mock messages feature is available for this mock from 1.3.0 version.
diff --git a/EPR-RMU-Simulator/user.md b/EPR-RMU-Simulator/user.md
index 6787019f9813399567168e2786ab056c60c0a740..d350d9c4d63907128ac01e288473cfd14cf4a706 100755
--- a/EPR-RMU-Simulator/user.md
+++ b/EPR-RMU-Simulator/user.md
@@ -4,9 +4,9 @@ subtitle: RMU Simulator
author: Youn Cadoret
function: Developer
date: 28/06/2019
-toolversion: 1.1.0
+toolversion: 1.2.0
version: 0.01
-status: to be reviewed
+status: Approved Document
reference: KER1-MAN-IHE-RMU_SIMULATOR_USER
customer: IHE-EUROPE
---
@@ -26,7 +26,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
* The Update Responder responds according to the Document Registry response.
* To build correctly \[ITI-92\] request, we need to retrieve the last good version of document registry. So first of all, it's important to execute Registry Stored Query \[ITI-18\] request; indeed this request will return the last version Approved of the document registry. And with this response we can build an adapted \[ITI-92\] request
-
+
### Data Set
@@ -35,7 +35,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
| PatientID | SourceID | UniqueID | HomeCommunityID |
|--------|:---:|-----:|------|
-| CHPAM4489^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1218 | urn:oid:1.2.3.4.5.6.2.333.23 |
+| CHPAM4489^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1218 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM1416^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1229 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM0456^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1232 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM9127^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1111 | urn:oid:1.2.3.4.5.6.2.333.23 |
@@ -55,8 +55,8 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
* [ITI-57 : http://ehealthsuisse.ihe-europe.net/update-document-set?wsdl](http://ehealthsuisse.ihe-europe.net/update-document-set?wsdl)
* [ITI-18 : http://ehealthsuisse.ihe-europe.net/registry-stored-query?wsdl](http://ehealthsuisse.ihe-europe.net/registry-stored-query?wsdl)
* It requires TLS mutual authentication with testing certificate (from GSS PKI). [The wsdl can be browsed here](https://ehealthsuisse.ihe-europe.net:10443/xcmu-responding-gateway?wsdl)
-
-
+
+
### Restricted Update Document Set \[ITI-92\] Request example
@@ -72,10 +72,10 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
</soap12:Header>
<soap12:Body>
-
+
<lcm:SubmitObjectsRequest xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:xdsb="urn:ihe:iti:xds-b:2007" xmlns:xop="http://www.w3.org/2004/08/xop/include">
- <rim:RegistryObjectList>
-
+ <rim:RegistryObjectList>
+
<rim:RegistryPackage id="urn:uuid:fd22545f-d7f6-4ca1-8ff1-d8bae7364ac1" objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:RegistryPackage" home="urn:oid:1.2.3.4.5.6.2.333.23">
<rim:Slot name="submissionTime">
<rim:ValueList>
@@ -249,7 +249,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Restricted Update Document Set \[ITI-92\] Success response example
```xml
@@ -265,7 +265,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Restricted Update Document Set \[ITI-92\] Failed response example
```xml
@@ -285,7 +285,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Request example
```xml
@@ -322,7 +322,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</s:Body>
</s:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Success response example
```xml
@@ -472,7 +472,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</S:Body>
</S:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Failed response example
```xml
@@ -488,4 +488,4 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</query:AdhocQueryResponse>
</S:Body>
</S:Envelope>
-```
\ No newline at end of file
+```
diff --git a/EPR-XDSMU-Simulator/user.md b/EPR-XDSMU-Simulator/user.md
index 47a154c20cf1de892ee70235f6f894592ac8335c..34784133a86ef117176e7df454260fcddaa8d6e9 100755
--- a/EPR-XDSMU-Simulator/user.md
+++ b/EPR-XDSMU-Simulator/user.md
@@ -4,9 +4,9 @@ subtitle: XDSMU Simulator
author: Youn Cadoret
function: Developer
date: 28/06/2019
-toolversion: 1.1.0
+toolversion: 1.2.0
version: 0.01
-status: to be reviewed
+status: Approved Document
reference: KER1-MAN-IHE-XDSMU_SIMULATOR_USER
customer: IHE-EUROPE
---
@@ -19,14 +19,13 @@ ehealthSuisse XDS Metadata Update MockUp simulates a Document Recipient.
The XDS Metadata Update profile provides a capability to change selected metadata attributes of documents registered.
-The actors involved in this profile are : Initiator, Responder and Document Registry/recipient.
+The actors involved in this profile are : Document Administrator and Document Registry/recipient.
+
+* The Document Administrator sends Update Document Set \[ITI-57\] request to the Responder specifying the patientID.
+* The Document Registry/recipient checks if the request is valid, if not, the transaction fails. If the request is valid, the Document Registry responds if the update has been done or not.
+* To build correctly \[ITI-57\] request, we need to retrieve the last good version of document registry. So first of all, it's important to execute Registry Stored Query \[ITI-18\] request; indeed this request will return the last version Approved of the document registry. And with this response we can build an adapted \[ITI-57\] request
-* The Update Initiator sends Restricted Update Document Set \[ITI-92\] request to the Responder specifying the homeCommunityID and the patientID.
-* The Update Responder checks if the request is valid, if not, the transaction fails. If the request is valid, the Responder sends the request to the Document Registry/Document. Then, the Document Registry responds if the update has been done or not.
-* The Update Responder responds according to the Document Registry response.
-* To build correctly \[ITI-92\] request, we need to retrieve the last good version of document registry. So first of all, it's important to execute Registry Stored Query \[ITI-18\] request; indeed this request will return the last version Approved of the document registry. And with this response we can build an adapted \[ITI-92\] request
-
### Data Set
@@ -35,7 +34,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
| PatientID | SourceID | UniqueID | HomeCommunityID |
|--------|:---:|-----:|------|
-| CHPAM4489^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1218 | urn:oid:1.2.3.4.5.6.2.333.23 |
+| CHPAM4489^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1218 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM1416^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1229 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM0456^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1232 | urn:oid:1.2.3.4.5.6.2.333.23 |
| CHPAM9127^^^CHPAM&1.3.6.1.4.1.12559.11.20.1&ISO | 1.3.6.1.4.1.12559.11.13.2.5 | 1.3.6.1.4.1.12559.11.13.2.6.1111 | urn:oid:1.2.3.4.5.6.2.333.23 |
@@ -54,8 +53,8 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
* [ITI-57 : http://ehealthsuisse.ihe-europe.net/update-document-set?wsdl](http://ehealthsuisse.ihe-europe.net/update-document-set?wsdl)
* [ITI-18 : http://ehealthsuisse.ihe-europe.net/registry-stored-query?wsdl](http://ehealthsuisse.ihe-europe.net/registry-stored-query?wsdl)
* It requires TLS mutual authentication with testing certificate (from GSS PKI). [The wsdl can be browsed here](https://ehealthsuisse.ihe-europe.net:10443/xcmu-responding-gateway?wsdl)
-
-
+
+
### XDS Metadata Update \[ITI-57\] Request example
```xml
@@ -70,10 +69,10 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
</soap12:Header>
<soap12:Body>
-
+
<lcm:SubmitObjectsRequest xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:xdsb="urn:ihe:iti:xds-b:2007" xmlns:xop="http://www.w3.org/2004/08/xop/include">
- <rim:RegistryObjectList>
-
+ <rim:RegistryObjectList>
+
<rim:RegistryPackage id="urn:uuid:fd22545f-d7f6-4ca1-8ff1-d8bae7364ac1" objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:RegistryPackage" home="urn:oid:1.2.3.4.5.6.2.333.23">
<rim:Slot name="submissionTime">
<rim:ValueList>
@@ -247,7 +246,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### XDS Metadata Update \[ITI-57\] Success response example
```xml
@@ -263,7 +262,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Restricted Update Document Set \[ITI-92\] Request example
@@ -280,10 +279,10 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
</soap12:Header>
<soap12:Body>
-
+
<lcm:SubmitObjectsRequest xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:xdsb="urn:ihe:iti:xds-b:2007" xmlns:xop="http://www.w3.org/2004/08/xop/include">
- <rim:RegistryObjectList>
-
+ <rim:RegistryObjectList>
+
<rim:RegistryPackage id="urn:uuid:fd22545f-d7f6-4ca1-8ff1-d8bae7364ac1" objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:RegistryPackage" home="urn:oid:1.2.3.4.5.6.2.333.23">
<rim:Slot name="submissionTime">
<rim:ValueList>
@@ -457,7 +456,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Restricted Update Document Set \[ITI-92\] Success response example
```xml
@@ -473,7 +472,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Restricted Update Document Set \[ITI-92\] Failed response example
```xml
@@ -493,7 +492,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</soap12:Body>
</soap12:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Request example
```xml
@@ -530,7 +529,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</s:Body>
</s:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Success response example
```xml
@@ -680,7 +679,7 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
</S:Body>
</S:Envelope>
```
-
+
### Registry Stored Query \[ITI-18\] Failed response example
```xml
@@ -700,4 +699,4 @@ The actors involved in this profile are : Initiator, Responder and Document Regi
## Mock messages on GWT
-The mock messages feature is available for this mock from 1.3.0 version.
+The mock messages feature is available for this mock from 1.3.0 version.