Update docs for docs.ohif.org

docs/connecting-to-image-archives/dcm4chee-with-docker.md

@@ -0,0 +1,41 @@
+# DCM4CHEE with Docker
+
+1. Install Docker (https://www.docker.com/)
+2. Follow the DCM4CHEE Guidelines for Running on Docker.
+
+    The easiest path is to use Docker-Compose which will start and stop multiple containers for you. There are excellent instructions provided by the DCM4CHEE team on the 'light archive' repository:
+
+    https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker#use-docker-compose
+
+    * Create docker-compose.yml and docker-compose.env files
+    * Start the containers:
+
+    ```` bash
+    docker-compose start
+    ````
+
+    **Note:** If you are running this on Mac OSX you will probably need to change the default docker-compose.yml file slightly. Specifically, the paths that refer to /var/local/ will likely need to be changed to /opt/
+
+3. Run the OHIF Viewer or Lesion Tracker using the dcm4cheeDIMSE.json configuration file
+
+````bash
+cd OHIFViewer
+PACKAGE_DIRS="../Packages" meteor --settings ../config/dcm4cheeDIMSE.json
+````
+
+## Web Service URLs from DCM4CHEE:
+Original source here: https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker#web-service-urls
+
+> - Archive UI: <http://localhost:8080/dcm4chee-arc/ui> - if secured, login with
+
+>     Username | Password | Role
+>     --- | --- | ---
+>     `user` | `user` | `user`
+>     `admin` | `admin` | `user` + `admin`
+> - Keycloak Administration Console: <http://localhost:8080/auth>, login with Username: `admin`, Password: `admin`.
+> - Wildfly Administration Console: <http://localhost:9990>, login with Username: `admin`, Password: `admin`.
+> - Kibana UI: <http://localhost:5601>
+> - DICOM QIDO-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
+> - DICOM STOW-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
+> - DICOM WADO-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
+> - DICOM WADO-URI: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/wado>

docs/connecting-to-image-archives/dicomweb.md

@@ -0,0 +1,3 @@
+# DICOM Web
+
+[DICOMWeb](https://en.wikipedia.org/wiki/DICOMweb) refers to RESTful DICOM Services and is a recently standardized set of guidelines for exchanging medical images and imaging metadata over the internet. Not all archives fully support it yet, but it is gaining wider adoption.

docs/connecting-to-image-archives/dimse.md

@@ -0,0 +1,3 @@
+# DICOM Message Service Element
+
+DIMSE Stands for [DICOM Message Service Element](http://dicom.nema.org/medical/dicom/current/output/chtml/part07/chapter_7.html) and is the standard method through which DICOM archives communicate. We support this messaging standard for the retrieval of study, series, and instance metadata because it is widely support. For certain PACS systems, it also (currently) provides faster query results than DICOMWeb.

docs/connecting-to-image-archives/options.md

@@ -0,0 +1,3 @@
+# Connecting to Image Archives
+
+We support DIMSE and DICOMWeb. Which one to use is up to you and depends on your PACS system. DICOMWeb requires no setup on the PACS-side whatsoever, whereas DIMSE may require you to add the 'OHIFDCM' aeTitle to the known DICOM Modalities of your Archive. This is the case for Orthanc, for example (See https://github.com/OHIF/Viewers/wiki/Orthanc-with-DIMSE).

docs/connecting-to-image-archives/orthanc-with-docker.md

@@ -0,0 +1,33 @@
+# Orthanc with Docker
+
+Depending on whether or not you want uploaded studies to persist in Orthanc after Docker has been closed, there are two different methods for starting the Docker image:
+
+## Temporary data storage
+This command will start an instance of the jodogne/orthanc-plugins Docker image. *All data will be removed when the instance is stopped!*
+
+````
+docker run --rm -p 4242:4242 -p 8042:8042 jodogne/orthanc-plugins
+````
+
+## Persistent data storage
+In order to allow your data to persist after the instance is stopped, you first need to create an image and attached data volume with Docker. The steps are as follows:
+
+1. Create a persistent data volume for Orthanc to use
+
+    ````
+    docker create --name sampledata -v /sampledata jodogne/orthanc-plugins
+    ````
+
+    **Note: On Windows, you need to use an absolute path for the data volume, like so:**
+
+    ````
+    docker create --name sampledata -v '//C/Users/erik/sampledata' jodogne/orthanc-plugins
+    ````
+
+2. Run Orthanc from Docker with the data volume attached
+
+    ````
+    docker run --volumes-from sampledata -p 4242:4242 -p 8042:8042 jodogne/orthanc-plugins
+    ````
+
+3. Upload your data and it will be persisted

docs/connecting-to-image-archives/osirix.md

@@ -0,0 +1,3 @@
+# Example: Osirix
+
+...