It's not just the server - it's the storage, accessibility (compartmentalization), and transmission of sensitive data (PHI and PII) at all levels. There is a lot more to HIPAA/HITECH than just server configuration - there are legal agreements you have to enter into as well (BAA's), insurance requirements, and potentially a lot more.<p>I'd suggest you work with a company that has a lot of experience in this area before you inadvertently find yourself fined (or sued) into bankruptcy.
There are a few options if you want HIPAA compliance. Note that "HIPAA compliance" is somewhat of a loaded term in that there aren't many super-technical benchmarks to meet, but a general "do-good" attitude including (but not limited to) some of the following points:<p>- Physical server isolation: you cannot have other instances sniffing around in your deallocated garbage memory.<p>- Encrypted data stores: physical theft of the server should not provide access to your data.<p>- Server providers who can sign a Business Associate Agreement: many hospitals and firms with medical data require this in their stipulations.<p>- Audit trails for database modifications, access, etc. Basically, log everything, and this has to be encrypted too if it contains protected health information (PHI).<p>- All PHI over HTTPS if you have a webapp. NO PHI OVER EMAIL OR HTTP.<p>- "Soft" guidelines such as password complexity measures, auto session expiration, disallowed multi-sessions.<p>Again, this is not an exhaustive list. You really need to check with a lawyer who knows this stuff. The fines are enormous (read: business-ending) if you break the rules.<p>How do you work to implement these? Well, find a host who is willing to sign a BAA. Here are the two major contenders I'm aware of:<p>- Use Amazon AWS; they're willing to sign a BAA with you and provide you the physical server isolation you need. However, this doesn't come cheap. Expect >$2,000/mo in costs to keep this configuration. Also, you'd better be a network pro or willing to learn how to manage VPCs correctly to provide proper network-level isolation for the databases.<p>- Use aptible.com (they happen to be a YC company, and I don't know of anyone else doing this). Frank & Chas (the founders) are very responsive and aim to provide a comprehensive package, including backups, audit trails, and even employee training. The Docker-based and heroku-like interface is very appealing:<p><a href="https://support.aptible.com/hc/en-us/articles/202638630-Deploying-your-first-app" rel="nofollow">https://support.aptible.com/hc/en-us/articles/202638630-Depl...</a><p>This option is still expensive. They host on AWS as well, so you're paying for the server costs + premium. However, this will still be a lot cheaper than hiring a competent sysadmin to make sure the execution is flawless.
It's a big task on its own and it seems a bit in-transparent to me.<p>However, you may want to have a look at TrueVault[0] which has been featured on HN[1].<p>[0]: <a href="https://www.truevault.com/" rel="nofollow">https://www.truevault.com/</a><p>[1]: <a href="https://news.ycombinator.com/item?id=7033188" rel="nofollow">https://news.ycombinator.com/item?id=7033188</a>
As some people have mentioned here, there are other issues to think of besides the IT aspect. There is employee training, risk assessment, policy development, and the business account agreements. Accountable is a company that focuses on these type of issues to make them easier by providing things like employee training, ready to use policies and procedures, and business association agreements. I found them while learning about HIPPA compliance, and I have not actually tried the product but it looks like it could be useful for you, so I thought I would mention it here. <a href="http://accountablehq.com/index.html" rel="nofollow">http://accountablehq.com/index.html</a>
Surprised no one has posted this. From the folks at TrueVault. <a href="https://github.com/truevault/hipaa-compliance-developers-guide" rel="nofollow">https://github.com/truevault/hipaa-compliance-developers-gui...</a>
@USNetizen -- You're right...I should have clarified that I want to know how to get an entire stack up and running, although I don't trust myself to do this unassisted.<p>I'm just surprised at how few resources there are that explain what it takes, and I hope that someday soon, healthcare startup CTO's will be referred to clearly documented open source solutions that are fairly fool-proof, rather than paid-for services (@sebst). Amazon's compliance page is unfortunately uninformative (@byoung2).
If you want a HIPAA-compliant server setup for you: <a href="https://www.aptible.com/" rel="nofollow">https://www.aptible.com/</a> (S14)
(Disclosure: I'm a co-founder of Aptible.)<p>As noted in other comments, most of HIPAA is not technical. Most of the requirements relate to risk assessment, policies, training, incident response, etc.<p>With that in mind, I'm going to quickly run down all of the major moving parts and then cover some of the technical considerations for setting up a server.<p>HIPAA has three main rules you need to comply with:<p>1. The Privacy Rule - Governs the use and disclosure of PHI (protected health information). Applies to all forms of PHI (verbal, written, electronic, etc.).<p>2. The Security Rule - Governs safeguards for electronic PHI<p>3. The Breach Notification Rule - Governs your responsibilities during a security or privacy incident<p><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><p>The Security Rule has a general security standard, some documentation/retention rules, and three sections of safeguards. They are:<p>1. Administrative Safeguards<p>2. Physical Safeguards<p>3. Technical Safeguards<p>Some of the safeguards are mandatory. Some are "addressable," meaning if you don't implement them you must document why you chose not to and what other safeguards you applied instead.<p><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><p>Most likely, you're going to start with something like the following for your servers:<p>1. Sign a BAA with any service provider who is going to touch PHI for you.<p>2. Restrict physical and logical server access to authorized individuals. Document how you restrict access and why the methods chosen are reasonable and appropriate given the risk posture of your organization. (There's a LOT packed into this step.)<p>3. Log all access and data modification events. If you use a logging service that isn't HIPAA-compliant, make sure you're not including PHI data you send them.<p>4. Encrypt data at rest and in transit, including inside the network perimeter. Document your network topology and access points.<p>5. Implement backups according to your organization's HIPAA contingency/disaster recovery plan. Document the backup scheme.<p>A few caveats:<p>- I haven't addressed application-level security. The same requirements apply, but the implementation differs.<p>- Your customers will demand additional safeguards that aren't in HIPAA.<p>At Aptible, we help with all of this, plus all of the other requirements (risk assessment, policies, training, etc.), so you can get a complete handle on your compliance status.
Thanks for all of your comments so far. Synopsis is...it's complicated. There are basically no straightforward guides and no reliable, tried-and-true open source solutions that can be deployed with minimal security expertise, at least with respect to the technical setup.<p>Options are to go with a service company like Aptible or TrueVault, or fumble through vast amounts of obtuse technical and legal documentation, then hire a security expert to audit your homemade system and hope that everything goes OK. Both options, as they currently exist, require a fair amount of $$$.
I'd just have someone else do it for me. There are many "enterprise" level hosting companies that can help you with that.<p>I believe that rackspace has a pretty program around compliance.
Hi,<p>training-hipaa.net provides Server Disaster Recovery Plan Template which is the part of HIPAA Compliance.<p>This Server Recovery Plan documents the strategies, personnel, procedures and resources necessary to recover the server following any type of short or long term disruption. You can find more information about this over here <a href="http://www.training-hipaa.net/template_suite/Server_recovery_plan_template.htm" rel="nofollow">http://www.training-hipaa.net/template_suite/Server_recovery...</a>
If you are trying to set up a service for processing or storing PHI, you may be interested in DNAnexus (<a href="https://dnanexus.com/" rel="nofollow">https://dnanexus.com/</a>), which focuses on compliant high throughput data analysis and storage for genome information, but can be used to store other types of PHI data. (Full disclosure, I work at DNAnexus). Email in profile if you want to go into specifics.
You may want to check out BladeLogic Server Automation:
<a href="http://www.bmc.com/it-solutions/bladelogic-server-automation.html" rel="nofollow">http://www.bmc.com/it-solutions/bladelogic-server-automation...</a><p>Datasheet:<p><a href="http://documents.bmc.com/products/documents/27/36/242736/242736.pdf" rel="nofollow">http://documents.bmc.com/products/documents/27/36/242736/242...</a>
Here is some info about doing it on AWS<p><a href="http://aws.amazon.com/compliance/" rel="nofollow">http://aws.amazon.com/compliance/</a>
One missing point in this thread: there is no such thing as HIPAA compliant. There is no government organization that will sanction your set up as "compliant". The HIPAA legislation imposes fines if you leak data, but does not prescribe how you prevent that.<p>That said, the thread does have some great safe guards and industry best practices you should look at.
(Disclosure: I work at FireHost, not in sales!)<p>We sell cloud but focused on security, compliance, and performance. Check us out.<p><a href="http://www.firehost.com/secure-cloud/compliant/hipaa" rel="nofollow">http://www.firehost.com/secure-cloud/compliant/hipaa</a>
@voska "Starting at $3499/month with an annual contract" -- Seems like security experience comes at a price... That said, it's worth taking every precaution to protect patient data.
We have audited HIPAA compliant hosting, at a reasonable price:<p><a href="https://www.atlantic.net/hipaa-compliant-hosting/" rel="nofollow">https://www.atlantic.net/hipaa-compliant-hosting/</a>
We used to use a hosting company Layered Tech that had a HIPPA compliant offering. If you need HIPPA compoanxe I suggest getting it as a managed service.
If one big customer is demanding you be HIPAA compliant then they probably want to see a certification, and depending on size of customer they may be willing to provide funding for that certification. It takes months but the certifying service will provide consulting and training. Essentially it all about tight access controls, encrypting data at rest, and documenting everything and everyone who has access to the internals.