49d343941e
* ci: test docs-publish * Specify to use prod * Babel should transpile with env set by webpack * in-progress * in-progress * Polyfill for ie11 and edge features * Ditch polyfills w/ babel - we'll use a service for now * Bump tools version; shift vtk.js up a layer * Specify we shouldn't target older than IE 11 * ditch babel plugins that should be covered by preset-env * Add a top level build demo command * Let our babel config determine settings * Same babel fixes as PWA * Rebuild deps that don't satisfy our target * Mini helper script for excluding all node_modules, except... * Shift vtk.js dep up a layer * Kill core-js * Export in a node happy way * Updated yarn lock * Set NODE_ENV when launching anything w/ WebPack * docs: updated FAQ * docs: on browser support * Add support for redux browser extension * misc. small clean-up * docs: Remove roadmap page; add browser-support to sidebar * Formatting * Remove roadmap links * Formatting * ci: Remove config syntax error * Simplified bug report template * update community request template * Update question's template * simplify build scripts * specify new script names * fix: for measurement api being pruned by minimizer in prod builds * Use named exports * Simplify config * Let's not do so much heavy lifting for a dev-server build * fix dev build * Add hotkeys to demo * fix: jest babel config and env specific configs * Remove call to non-existant command * Shift experimental proposal plugin up a layer * Use `https` * Try with reduced number of package exceptions * Try to resolve cypress issue * Try to fix cypress issue in CI * Skip https
3.6 KiB
Frequently Asked Questions
Index
- Report a bug
- Request a feature
- Commercial Support & Consulting
- Academic collaborations
- FDA Clearance or CE Marking
- HIPAA Compliance
How do I report a bug?
Navigate to our GitHub Repository, and submit a new bug report. Follow the steps outlined in the Bug Report Template.
How can I request a new feature?
At the moment we are in the process of defining our roadmap and will do our best to communicate this to the community. If your requested feature is on the roadmap, then it will most likely be built at some point. If it is not, you are welcome to build it yourself and contribute it. If you have resources and would like to fund the development of a feature, please contact us or work with community members that offer consulting services.
Who should I contact about Academic Collaborations?
Gordon J. Harris at Massachusetts General Hospital is the primary contact for any academic collaborators. We are always happy to hear about new groups interested in using the OHIF framework, and may be able to provide development support if the proposed collaboration has an impact on cancer research.
Does OHIF offer commercial support?
The Open Health Imaging Foundation does not offer commercial support, however, some community members do offer consulting services. The following contacts may be useful:
- Rob Lewis (Radical Imaging)
Please file a Pull Request if you wish to add your name or organization to this list.
Does The OHIF Viewer have 510(k) Clearance from the U.S. F.D.A or CE Marking from the European Commission?
NO. The OHIF Viewer is NOT F.D.A. cleared or CE Marked. It is the users responsibility to ensure compliance with applicable rules and regulations. The License for the OHIF Platform does not prevent your company or group from seeking F.D.A. clearance for a product built using the platform.
If you have gone this route (or are going there), please let us know because we would be interested to hear about your experience.
Is The OHIF Viewer HIPAA Compliant?
NO. The OHIF Viewer DOES NOT fulfill all of the criteria to become HIPAA Compliant. It is the users responsibility to ensure compliance with applicable rules and regulations.