Update README.md

README.md

@@ -1,21 +1,20 @@
 # oBDS2FHIR
 
-Using the two XSLT files ([oBDS2MDS.xsl](https://github.com/samply/obds2fhir/blob/main/src/main/resources/oBDS2MDS_FHIR.xsl) and [MDS2FHIR.xsl](https://github.com/samply/obds2fhir/blob/main/src/main/resources/MDS2FHIR.xsl)), XML files conforming to [oBDS](https://basisdatensatz.de/xml/) or the legacy version [ADT/GEKID V2*](https://basisdatensatz.de/xml/) can be transformed into FHIR 
-resources conforming to [de.dktk.oncology](https://simplifier.net/packages/de.dktk.oncology/).
+oBDS2FHIR (formerly ADT2FHIR) is a tool to transform files exported by German tumor documentation systems into FHIR bundles for use in the [Bridgehead](https://github.com/samply/bridgehead) (or other FHIR-based software).
 
+Using the two XSLT files ([oBDS2MDS.xsl](https://github.com/samply/obds2fhir/blob/main/src/main/resources/oBDS2MDS_FHIR.xsl) and [MDS2FHIR.xsl](https://github.com/samply/obds2fhir/blob/main/src/main/resources/MDS2FHIR.xsl)), XML files conforming to [oBDS](https://basisdatensatz.de/xml/) or the legacy version [ADT/GEKID V2*](https://basisdatensatz.de/xml/) can be transformed into FHIR resources conforming to [de.dktk.oncology](https://simplifier.net/packages/de.dktk.oncology/).
+
+This software was originally created for the [German Cancer Consortium's Clinical Communication Platform](https://dktk.dkfz.de/) and has since been made open source.
 
 ## Usage
 
-The main method transforms oBDS conform data into FHIR bundles.
+The main method transforms oBDS compliant data into FHIR bundles.
 Therefore, put your oBDS data in the input directory ```/clincial_data/Input_Patients```. 
-Optionally, you can (1) pseudonymize (e.g. see [Mainzelliste](https://bitbucket.org/medicalinformatics/mainzelliste)) and (2) import the data in a FHIR server (e.g. see [Blaze](https://github.com/samply/blaze)).
-
-The tool oBDS2FHIR is desinged as docker-compose application.
-
+Optionally, you can (1) pseudonymize (e.g. see [Mainzelliste](https://bitbucket.org/medicalinformatics/mainzelliste)) and (2) import the data into a FHIR server (e.g. see [Blaze](https://github.com/samply/blaze)).
 
 ### Docker
 
-To run oBDS2FHIR, put the oBDS xml files in ```/clinical_data/Input_oBDS/``` and run:
+oBDS2FHIR is designed for use with docker compose. To run, put the oBDS xml files in ```/clinical_data/Input_oBDS/``` and run:
 ```sh
 docker-compose up
 ```
@@ -28,40 +27,40 @@ The configuration is set in the ```docker-compose.yml``` file and is preconfigur
 Set the environment variables either directly in Java oder via docker compose (start with the default values from the Dockerfile):
 
 
-```FILE_PATH``` defines the directory of the clinical oBDS data in the docker container.
+* ```FILE_PATH``` defines the directory of the clinical oBDS data in the docker container.
 There souldn't be a reason to change this for docker.
 
-```FILE_TYPE``` defines the data type of the clinical data (oBDS|ADT_GEKID).
+* ```FILE_TYPE``` defines the data type of the clinical data (oBDS|ADT_GEKID).
 This is an optional parameter to increase performance. if not set, each file will be checked individually.
 
-```STORE_PATH``` defines the URL of the FHIR server API.
+* ```STORE_PATH``` defines the URL of the FHIR server API.
 You can use the default value, when using the default BLAZE server (https://github.com/samply/blaze).
 
-```STORE_AUTH``` sets the FHIR server authentication. *Leave it empty if there is no authentication.*
+* ```STORE_AUTH``` sets the FHIR server authentication. *Leave it empty if there is no authentication.*
 
-```IDENTIFIER_SYSTEM``` defines the system of the FHIR identifiers.
+* ```IDENTIFIER_SYSTEM``` defines the system of the FHIR identifiers.
 You can use the default value or set your own system URL.
 
-```MAINZELLISTE_URL``` for pseudonymization in the transformation step; sets the URL of the pseudonymization service. *Leave it empty if there is no pseudonymization.*
+* ```MAINZELLISTE_URL``` for pseudonymization in the transformation step; sets the URL of the pseudonymization service. *Leave it empty if there is no pseudonymization.*
 
-```MAINZELLISTE_APIKEY``` sets the pseudonymization service authentication. *Leave it empty if there is no pseudonymization.*
+* ```MAINZELLISTE_APIKEY``` sets the pseudonymization service authentication. *Leave it empty if there is no pseudonymization.*
 
-```IDTYPE``` sets the pseudonym type. *Leave it empty if there is no pseudonymization.*
+* ```IDTYPE``` sets the pseudonym type. *Leave it empty if there is no pseudonymization.*
 
-```SALT``` defines a random additional input for the hashing applied in generating the FHIR ids from oBDS. **Please do change this** 
+* ```SALT``` defines a random additional input for the hashing applied in generating the FHIR ids from oBDS. **Please do change this** 
 
-```SSL_CERTIFICATE_VALIDATION``` can be set to false **IF** your FHIR server is only accessible via https and you do **NOT** have a valid SSL certificate. Not recommended!
+* ```SSL_CERTIFICATE_VALIDATION``` can be set to false **IF** your FHIR server is only accessible via https and you do **NOT** have a valid SSL certificate. Not recommended!
 
-```ADD_DEPARTMENTS``` can be set to true if you want to add the departments that commited the patient report (=oBDS Melder). *Probably not  necessary*.
+* ```ADD_DEPARTMENTS``` can be set to true if you want to add the departments that commited the patient report (=oBDS Melder). *Probably not  necessary*.
 
 ###### Volumes:
 
-```./clinical_data:/obds2fhir/clinical_data``` You can use the default value, which then mounts the host ```clinical_data``` directory to the docker container.
+* ```./clinical_data:/obds2fhir/clinical_data``` You can use the default value, which then mounts the host ```clinical_data``` directory to the docker container.
 
-```/etc/bridgehead/traefik-tls:/.../:ro``` If you use https, please set the correct certificate path here.
+* ```/etc/bridgehead/traefik-tls:/.../:ro``` If you use https, please set the correct certificate path here (should work out of the box for use with Bridgeheads).
 
 ###### Network - extra_hosts:
-``"host.docker.internal:host-gateway"`` If you run oBDS2FHIR in an additional docker-compose file on the same host and you are not managing the docker network yourself, then use this configuration to enable access to other services (FHIR server; pseudonymization service).
+* ``"host.docker.internal:host-gateway"`` If you run oBDS2FHIR in an additional docker-compose file on the same host and don't manage the docker network yourself, then use this configuration to enable access to other services (FHIR server; pseudonymization service).
 
 
 ## Notes
@@ -71,10 +70,10 @@ You can use the default value or set your own system URL.
     -_Lokal_DKTK_ID_Pat_System_ needs to conform to https://www.hl7.org/fhir/datatypes.html#uri
 
 You should modify the identifier system (replace http://dktk.dkfz.de/fhir/onco/core/CodeSystem/PseudonymArtCS with
-a local URL). You can just make one up (or use the default), but note that this URL will be used as Identifier.system
-in the resulting FHIR Patient resources (Identifer.value will be (A) a **hash** based on patient master data or if pseudonymization 
-is configured (B) be replaced by Mainzelliste pseudonym).
+a local URL). You can just make one up (or use the default), but note that this URL will be used as ```Identifier.system```
+in the resulting FHIR Patient resources (```Identifer.value``` will either be (a) a hash based on patient master data or, if pseudonymization 
+is configured, (b) be replaced by a Mainzelliste-generated pseudonym).
 
 Since ids are required in FHIR but optional in the oBDS XML schema, they are generated via content hashing
-if not present. However, it is recommended to provide all optinal ids in the importet oBDS XML files.
-Additionally, ```Patient_ID```, ```Diagnosis_ID``` and ```Sample_ID``` are required. 
+if not present. However, it is recommended to provide all optional ids in the imported oBDS XML files.
+Additionally, ```Patient_ID```, ```Diagnosis_ID``` and ```Sample_ID``` are required.