Back to All Articles Subscribe   

Deploying HIPAA-Compliant Software

First published on: 7 June 2018

Medical Imaging software that is used in the clinic must comply with HIPAA. In this article, we list various deployment strategies we have seen along with advantages and disadvantages of each approach. There are likely project-specific considerations that are not included here, but hopefully this list can act as a useful starting place for your project.

1. Native App

Advantages:

Disadvantages:

2. Web App Served Locally

Advantages:

Disadvantages:

3. Web App Served From Cloud

Advantages:

Disadvantages:

4. Web App Served Locally + Cloud Processing Server

Advantages:

Disadvantages:

5. Native App + Cloud Processing Server

Advantages:

Disadvantages:

6. Web App + Cloud Processing Server + 3rd Party HIPAA Platform

Advantages:

Disadvantages:

Footnotes

1 It is also possible to deploy a native app if you need the visualization performance but comes with many of the disadvantages of (1)
2 It may be possible to also use a web app in rare cases. However, web apps don’t currently provide a reliable way to store long-term data. One exception may be if you could use the web app to de-identify the data, but you don’t need to store any PHI for longer than a single session
3 Cloud hosting platforms can go out of business too, however, switching is usually easier






Was this article interesting?

We publish technical articles and coding case studies about topics we run into in the field. Follow us on Twitter or subscribe to our email list:



Back to All Articles