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
82 lines
3.6 KiB
Markdown
82 lines
3.6 KiB
Markdown
# Frequently Asked Questions
|
|
|
|
## Index
|
|
|
|
- [Report a bug][report-bug]
|
|
- [Request a feature][new-feature]
|
|
- [Commercial Support & Consulting][commercial-support]
|
|
- [Academic collaborations][academic]
|
|
- [FDA Clearance or CE Marking][fda-clearance]
|
|
- [HIPAA Compliance][hipaa]
|
|
|
|
### How do I report a bug?
|
|
|
|
Navigate to our [GitHub Repository][new-issue], and submit a new bug report.
|
|
Follow the steps outlined in the [Bug Report Template][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](contributing.md). If you have
|
|
resources and would like to fund the development of a feature, please
|
|
[contact us](http://www.ohif.org) or work with community members that offer
|
|
[consulting services][commercial-support].
|
|
|
|
### Who should I contact about Academic Collaborations?
|
|
|
|
[Gordon J. Harris](http://www.dfhcc.harvard.edu/insider/member-detail/member/gordon-j-harris-phd/)
|
|
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](http://radicalimaging.com/))
|
|
|
|
**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][501k-clearance] from the U.S. F.D.A or [CE Marking][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](https://github.com/OHIF/Viewers/blob/master/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][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.
|
|
|
|
<!--
|
|
Links
|
|
-->
|
|
|
|
<!-- prettier-ignore-start -->
|
|
<!-- INDEX -->
|
|
[report-bug]: #how-do-i-report-a-bug
|
|
[new-feature]: #how-can-i-request-a-new-feature
|
|
[commercial-support]: #does-ohif-offer-commercial-support
|
|
[academic]: #who-should-i-contact-about-academic-collaborations
|
|
[fda-clearance]: #does-the-ohif-viewer-have-510k-clearance-from-the-us-fda-or-ce-marking-from-the-european-commission
|
|
[hipaa]: #is-the-ohif-viewer-hipaa-compliant
|
|
<!-- OTHER -->
|
|
[501k-clearance]: https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/HowtoMarketYourDevice/PremarketSubmissions/PremarketNotification510k/
|
|
[ce-marking]: https://ec.europa.eu/growth/single-market/ce-marking_en
|
|
[hipaa]: https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act
|
|
[new-issue]: https://github.com/OHIF/Viewers/issues/new/choose
|
|
[bug-report-template]: https://github.com/OHIF/Viewers/issues/new?assignees=&labels=Bug+Report+%3Abug%3A&template=---bug-report.md&title=
|
|
<!-- prettier-ignore-end -->
|