Files
ohif-viewer/docs/latest
ladeirarodolfo 7c4ee734fa refactor: 💡 React components to consume appConfig using Context (#852)
* refactor: 💡 React components to consume appConfig using Context

React components to consume app configuration using React Context and
React Hooks. Non React components to continue using global variable
window.config. Related documentation also changed.

Closes: #725

* refactor: 💡 Removing unecessary code

On current React component there is no need to import useContext method
from React, so, removing it.

* refactor: 💡 Code review

Code review. Minor changes based on review inputs and moving userManager
to an init method

BREAKING CHANGE: #725

Closes: #725

* docs: don't include implementation detail in docs

* docs: don't include implementation detail in docs

* docs: no need to specify implementation details in employment recipe

* docs: no need to specify implementation details in deployment recipe
2019-09-06 14:31:26 -04:00
..
2019-05-17 09:42:38 -04:00
2019-03-04 13:45:57 +01:00
2019-09-05 21:08:14 -04:00

Looking for a Live Demo? Preview The OHIF Viewer

ATTENTION! You are looking at the docs for the React version of the OHIF Viewer. If you're looking for the Meteor version's documentation (now deprecated), select it's version from the dropdown box in the top left corner of this page.

Introduction

The Open Health Imaging Foundation (OHIF) Viewer is an open source, web-based, medical imaging viewer. It can be configured to connect to Image Archives that support DicomWeb, and offers support for mapping to proprietary API formats. OHIF maintained extensions add support for viewing, annotating, and reporting on DICOM images in 2D (slices) and 3D (volumes).

OHIF Viewer Screenshot

The OHIF Viewer: A general purpose DICOM Viewer (Live Demo)

The Open Health Imaging Foundation intends to provide a simple general purpose DICOM Viewer which can be easily extended for specific uses. If you find yourself unable to extend the viewer for your purposes, please reach out via our GitHub issues. We are actively seeking feedback on ways to improve our integration and extension points.

Where to next?

Check out these helpful links: