Our custom OHIF Viewer.
Go to file
2019-04-08 13:10:29 +02:00
config Restrict Scope for Cloud Healthcare API Example Config (#378) 2019-04-05 16:13:14 +02:00
dockersupport feat(google-cloud): Add docs for how to use OHIF against Google Cloud Healthcare 2019-04-03 18:17:38 +02:00
docs docs(google-cloud): Update Google Cloud docs to clarify instructions 2019-04-05 17:37:45 +02:00
img Update docs for docs.ohif.org 2018-01-30 15:05:15 +01:00
LesionTracker chore(dicomweb-client): Switch to dicomweb-client.js to push logic out of OHIF 2018-10-04 11:40:48 +02:00
OHIFViewer fix(toolbar): Remove unnecessary Presentation State button 2019-03-22 16:43:39 +01:00
Packages fix(google-cloud): Update healthcare-api-adapter to use v1beta1 URLs (#379) 2019-04-08 13:10:29 +02:00
StandaloneViewer feat(standalone-viewer): Add authorization header (#322) 2018-12-12 18:01:46 +01:00
test Add Travis CI setup with Gitbook build / deploy to gh-pages, StandaloneViewer build / deploy to AWS S3, and ohif/viewer docker image build / push to dockerhub 2018-07-05 21:55:03 +02:00
.dockerignore Add dockerfile and docker-compose setup. 2018-03-28 13:33:15 +02:00
.eslintignore Begin adding Gitbook for Viewers documentation 2018-01-29 15:01:58 +01:00
.eslintrc.js Begin adding Gitbook for Viewers documentation 2018-01-29 15:01:58 +01:00
.gitignore feat(google-cloud): Add support for Google Cloud Healthcare API DICOM Store Switch (#325) 2019-03-22 16:42:26 +01:00
.jscsrc LT-92: Enabling single line if for return, continue and break statements 2017-01-18 11:01:52 -02:00
.jshintrc Removing cornerstone imports from globals 2017-12-28 08:59:25 -02:00
.travis.yml including skip configuration if the push comes from external PR 2019-01-31 11:23:35 -02:00
conf.json Commented a lot of functions. Tried to get jsDoc and/or docco to work 2015-11-16 17:49:35 +01:00
development.Dockerfile fix(dockerfile): Fix jessie-updates issues with node:8.10.0-slim image 2019-04-04 09:02:15 +02:00
docker-compose.yml fix(dockersupport) Adding a relative path into docker-compose to use dockersupport/ app.json (#216) 2018-07-03 17:26:36 +02:00
dockerfile fix(dockerfile): Fix jessie-updates issues with node:8.10.0-slim image 2019-04-04 09:02:15 +02:00
generateStaticSite.sh Update references to meteor-build-client-fixed to use the new version and supporting legacy browsers. (#334) 2019-01-16 10:35:52 +01:00
ghc-dockerfile feat(google-cloud): Add support for Google Cloud Healthcare API DICOM Store Switch (#325) 2019-03-22 16:42:26 +01:00
LICENSE Initial commit 2015-10-13 10:57:37 +02:00
package-lock.json feat(google-cloud): Add support for Google Cloud Healthcare API DICOM Store Switch (#325) 2019-03-22 16:42:26 +01:00
package.json feat(netlify) Add static site deployment from Netlify (add /viewer to the deploy preview URL) (#232) 2018-07-23 10:19:52 +02:00
README.md Update README.md 2018-01-30 17:02:03 +01:00

Viewers

This repo contains the OHIF DICOM Viewer and Lesion Tracker, and various shared meteor packages.

Documentation is available here: http://docs.ohif.org/

Demos

OHIF Viewer - A general-purpose radiology viewer with a variety of tools exposed.

Lesion Tracker - A prototype viewer focused on oncology metrics.

Community

Have questions? Try posting on our google groups forum.

Docker usage

Following the instructions below, the docker image will listen for DICOM connections on port 4242, and for web traffic on port 8042. The default username for the web interface is orthanc, and the password is orthanc.

Temporary data storage

docker run --rm -p 4242:4242 -p 8042:8042 jodogne/orthanc-plugins

Persistent data storage

  1. Create a persistant 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