ohif-viewer/docs/latest/configuring/data-source.md

171 lines
6.2 KiB
Markdown
Raw Normal View History

2019-05-10 04:13:39 +02:00
# Data Source
After following the steps outlined in
[Getting Started](./../development/getting-started.md), you'll notice that the
OHIF Viewer has data for several studies and their images. You didn't add this
data, so where is it coming from?
2019-05-10 04:13:39 +02:00
2019-05-10 05:25:07 +02:00
By default, the viewer is configured to connect to a remote server hosted by the
nice folks over at [dcmjs.org][dcmjs-org]. While convenient for getting started,
the time may come when you want to develop using your own data either locally or
remotely.
2019-05-10 04:13:39 +02:00
## Set up a local DICOM server
2019-05-10 05:25:07 +02:00
> ATTENTION! Already have a remote or local server? Skip to the
2019-05-10 06:35:36 +02:00
> [configuration section](#configuration-learn-more) below.
2019-05-10 04:13:39 +02:00
2019-05-10 05:25:07 +02:00
While the OHIF Viewer can work with any data source, the easiest to configure
are the ones that follow the [DICOMWeb][dicom-web] spec.
2019-05-10 04:13:39 +02:00
2019-05-10 05:25:07 +02:00
1. Choose and install an Image Archive
2. Upload data to your archive (e.g. with DCMTK's [storescu][storescu] or your
archive's web interface)
3. Keep the server running
2019-05-10 04:13:39 +02:00
2019-05-10 05:25:07 +02:00
For our purposes, we will be using `Orthanc`, but you can see a list of
[other Open Source options](#open-source-dicom-image-archives) below.
2019-05-10 04:13:39 +02:00
2019-05-10 05:25:07 +02:00
### Requirements
2019-05-10 04:13:39 +02:00
2019-05-10 15:25:51 +02:00
- Docker
- [Docker for Mac](https://docs.docker.com/docker-for-mac/)
2019-06-05 16:11:13 +02:00
- [Docker for Windows (recommended)](https://docs.docker.com/docker-for-windows/)
- [Docker Toolbox for Windows](https://docs.docker.com/toolbox/toolbox_install_windows/)
2019-05-10 15:25:51 +02:00
_Not sure if you have `docker` installed already? Try running `docker --version`
in command prompt or terminal_
2019-05-10 04:13:39 +02:00
> If you are using `Docker Toolbox` you need to change the _PROXY_DOMAIN_
> parameter in _platform/viewer/package.json_ to http://192.168.99.100:8042 or
> the ip docker-machine ip throws. This is the value [`WebPack`][webpack-proxy]
> uses to proxy requests
2019-06-05 16:11:13 +02:00
2019-05-10 05:25:07 +02:00
### Running Orthanc
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
_Start Orthanc:_
2019-05-10 05:25:07 +02:00
```bash
# Runs orthanc so long as window remains open
yarn run orthanc:up
2019-05-10 04:13:39 +02:00
```
2019-05-10 06:35:36 +02:00
_Upload your first Study:_
2019-05-10 04:13:39 +02:00
1. Navigate to
[Orthanc's web interface](http://localhost:8042/app/explorer.html) at
`http://localhost:8042/app/explorer.html` in a web browser.
2019-05-10 06:35:36 +02:00
2. In the top right corner, click "Upload"
3. Click "Select files to upload..." and select one or more DICOM files
4. Click "Start the upload"
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
#### Orthanc: Learn More
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
You can see the `docker-compose.yml` file this command runs at
[`<project-root>/.docker/Nginx-Orthanc/`][orthanc-docker-compose], and more on
Orthanc for Docker in [Orthanc's documentation][orthanc-docker].
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
### Connecting to Orthanc
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
Now that we have a local Orthanc instance up and running, we need to configure
our web application to connect to it. Open a new terminal window, navigate to
this repository's root directory, and run:
2019-05-10 04:13:39 +02:00
```bash
# If you haven't already, enable yarn workspaces
yarn config set workspaces-experimental true
# Restore dependencies
2019-05-10 04:13:39 +02:00
yarn install
2019-05-10 06:35:36 +02:00
# Run our dev command, but with the local orthanc config
yarn run dev:orthanc
2019-05-10 04:13:39 +02:00
```
2019-05-10 06:35:36 +02:00
#### Configuration: Learn More
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
> For more configuration fun, check out the
> [Essentials Configuration](./index.md) guide.
2019-05-10 04:13:39 +02:00
2019-05-10 06:35:36 +02:00
Let's take a look at what's going on under the hood here. `yarn run dev:orthanc`
is running the `dev:orthanc` script in our project's `package.json`. That script
is:
```js
cross-env NODE_ENV=development PROXY_TARGET=/dicom-web PROXY_DOMAIN=http://localhost:8042 APP_CONFIG=config/docker_nginx-orthanc.js webpack-dev-server --config .webpack/webpack.pwa.js -w
2019-05-10 06:35:36 +02:00
```
2019-05-10 04:13:39 +02:00
- `cross-env` sets three environment variables
- PROXY_TARGET: `/dicom-web`
- PROXY_DOMAIN: `http://localhost:8042`
- APP_CONFIG: `config/docker_nginx-orthanc.js`
- `webpack-dev-server` runs using the `.webpack/webpack.pwa.js` configuration
file. It will watch for changes and update as we develop.
`PROXY_TARGET` and `PROXY_DOMAIN` tell our development server to proxy requests
to `Orthanc`. This allows us to bypass CORS issues that normally occur when
requesting resources that live at a different domain.
2019-05-10 04:13:39 +02:00
2019-08-20 22:39:25 +02:00
The `APP_CONFIG` value tells our app which file to load on to `window.config`.
By default, our app uses the file at
`<project-root>/platform/viewer/public/config/default.js`. Here is what that
configuration looks like:
2019-05-10 15:29:18 +02:00
```js
window.config = {
routerBasename: '/',
servers: {
dicomWeb: [
{
name: 'Orthanc',
wadoUriRoot: 'http://localhost:8899/wado',
qidoRoot: 'http://localhost:8899/dicom-web',
wadoRoot: 'http://localhost:8899/dicom-web',
qidoSupportsIncludeField: false,
imageRendering: 'wadors',
thumbnailRendering: 'wadors',
},
],
},
2019-06-05 16:11:13 +02:00
};
2019-05-10 15:29:18 +02:00
```
To learn more about how you can configure the OHIF Viewer, check out our
[Configuration Guide](./index.md).
2019-05-10 05:24:50 +02:00
## Open Source DICOM Image Archives
2019-05-10 15:26:03 +02:00
Our example uses `Orthanc`, but there are a lot of options available to you.
Here are some of the more popular ones:
2019-05-10 05:24:50 +02:00
| Archive | Installation |
| --------------------------------------------- | ---------------------------------- |
| [DCM4CHEE Archive 5.x][dcm4chee] | [W/ Docker][dcm4chee-docker] |
| [Orthanc][orthanc] | [W/ Docker][orthanc-docker] |
| [DICOMcloud][dicomcloud] (**DICOM Web only**) | [Installation][dicomcloud-install] |
| [OsiriX][osirix] (**Mac OSX only**) | Desktop Client |
| [Horos][horos] (**Mac OSX only**) | Desktop Client |
_Feel free to make a Pull Request if you want to add to this list._
<!--
Links
-->
<!-- prettier-ignore-start -->
[dcmjs-org]: https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/wado
[dicom-web]: https://en.wikipedia.org/wiki/DICOMweb
[storescu]: http://support.dcmtk.org/docs/storescu.html
[webpack-proxy]: https://webpack.js.org/configuration/dev-server/#devserverproxy
[orthanc-docker-compose]: https://github.com/OHIF/Viewers/tree/master/.docker/Nginx-Orthanc
2019-05-10 05:24:50 +02:00
<!-- Archives -->
[dcm4chee]: https://github.com/dcm4che/dcm4chee-arc-light
[dcm4chee-docker]: https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker
[orthanc]: https://www.orthanc-server.com/
[orthanc-docker]: http://book.orthanc-server.com/users/docker.html
[dicomcloud]: https://github.com/DICOMcloud/DICOMcloud
[dicomcloud-install]: https://github.com/DICOMcloud/DICOMcloud#running-the-code
[osirix]: http://www.osirix-viewer.com/
[horos]: https://www.horosproject.org/
<!-- prettier-ignore-end -->