Update ATC Documentation

EPR-ATC-Simulator/installation.md

@@ -7,18 +7,18 @@ date: 01/07/2019
 toolversion: 1.2.0
 version: 1.01
 status: Draft
-reference: KER1-MAN-IHE-ATC_SIMULATOR_INSTALLATION-0_01
+reference: KER1-MAN-IHE-ATC_SIMULATOR_INSTALLATION-1_01
 customer: IHE-EUROPE
 ---
 
-# ATC Simulator - Installation & configuration
+# ATC Simulator - Installation & configuration
 
-## Source code
+## Source Code
 
 Sources of the tool are available on Inria's Gforge in the Gazelle project: 
 [EPR > atc-repository](https://gitlab.inria.fr/gazelle/specific-tools/epr/atc-repository).
 
-## Patient Audit Consumer 
+## Patient Audit Consumer
 
 This project can be loaded on a Gazelle WebService tester instance. This way you will be able to launch a suite of requests from the simulator emulating 
 the Patient Audit Consumer actor of the CH:ATC profile.
@@ -39,6 +39,7 @@ audit event from his Patient Audit Record Repository.
 
 First step to set up the Patient Audit Record Repository actor from the simulator is to checkout sources.
 You can checkout the entire ATC simulator sources from the url [here](https://gitlab.inria.fr/gazelle/specific-tools/epr/atc-repository).
+The full project for released version can also been found on a ZIP archive format on nexus.
 For the Patient Audit Record Repository actor you will need three things : 
 * The SoapUI project __ATC/soapui/ATC-MockService-soapui-project.xml__
 * The folder __ATC/test_data/AuditEvent__ that contains all Audit Events known by the simulator.

EPR-ATC-Simulator/user.md

@@ -25,7 +25,7 @@ As a Patient Audit Consumer, this simulator is aimed to send messages to a Patie
 As a Patient Audit Record Repository, this simulator can be requested Audit Events by your system.
 
 
-# Patient Audit Consumer
+# Patient Audit Consumer
 
 When acting as a Patient Audit Consumer, this simulator is able to send multiple requests to your SUT to test the handling of parameters :
 
@@ -38,7 +38,7 @@ When acting as a Patient Audit Consumer, this simulator is able to send multiple
 
 It can also send bad requests (missing requested parameters, parameters providing no matches, etc) to test the behavior of the SUT against erroneous requests.
 
-## How to access the Simulator ?
+## How to access the Simulator ?
 
 The simulator is accessible via Gazelle Webservice Tester. If the simulator is available on the instance of the tool, it should appear in the project list with the name **ATC_Repository**.
 This name may also be followed with the version of the specification in brackets.
@@ -46,7 +46,7 @@ This name may also be followed with the version of the specification in brackets
 ![ATC Simulator for Patient Audit Consumer](./media/atc_repo_gwt.png)
 
 
-## How to send messages to an SUT ?
+## How to send messages to an SUT ?
 
 If the simulator is available on the instance of Gazelle Webservice Tester you are using, it can then be launched as any other project from the tools.
 
@@ -64,7 +64,7 @@ Once you defined all parameters for the Simulator to send requests, simply press
 This Execution can be retrieved anytime in the **Execution List** menu.
 
 
-# Patient Audit Record Repository
+# Patient Audit Record Repository
 
 The ATC Simulator can also simulates a CH:ATC Patient Audit Record Repository.
 A **Patient Audit Consumer** queries a **Patient Audit Record Repository** for Audit Events defined by this profile.
@@ -76,10 +76,10 @@ Each request sent must have a security token in the header, this part is used to
 * Is the assertion valid in time ? (Time not Before in the past and Time not After in the future)
 * Does the mock know the patient ID passed as a **resource-id** attribute ? If not, the mock will say you do not have the right to acces the information. The list of available patient ID is displayed below.
 
-## Data Set
+## Data set
+
+### Token Security
 
-###Token Security
-	
 Here are the ID to put in the SAML token in **resource-id** attribute. 
 If you query any other patient id, the mock will respond with an error message saying that you are not authorized to access information related to the given patient ID.
 
@@ -112,7 +112,7 @@ Here are the endpoints to use to send your request to the Patient Audit Record R
         
 It requires TLS mutual authentication with testing certificate (from GSS PKI).
 
-##ATC URI example
+### ATC URI example
 
 Here is an example URI for a requets on patient with ID **761337610430891416^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO** looking for audit events between
 **2015-01-01** and **2020-01-01**