MongoDB aids healthcare professionals by providing a flexible and scalable database platform. It allows for secure storage and retrieval of diverse healthcare data, facilitating real-time analytics, patient record management, and seamless integration of healthcare applications. MongoDB empowers professionals to make data-driven decisions, improving patient care and operational efficiency.
They state on their website that MongoDB is HIPAA compliant which is clearly a positive sign, but the Health Insurance Portability and Accountability Act (HIPAA) legislation states that you can’t stop here and you need to thoroughly vet the vendor.
According to the HIPAA rules for Covered Entities and Business Associates:
'If a covered entity engages a business associate to help it carry out its health care activities and functions, the covered entity must have a written business associate contract or other arrangement with the business associate that establishes specifically what the business associate has been engaged to do and requires the business associate to comply with the Rules’ requirements to protect the privacy and security of protected health information. In addition to these contractual obligations, business associates are directly liable for compliance with certain provisions of the HIPAA Rules.'
Below we provide some general guidelines on how to first quickly screen this vendor for the HIPAA compliance fundamentals, and if all initial checks pass successfully, then to proceed and do your own in-depth audit to ensure that this vendor will qualify as your HIPAA-compliant Business Associate.
✅ They communicate they are HIPAA compliant which is a positive sign, as they legally commit from their side using such public statements.
'For organizations in healthcare and related fields subject to the requirements of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), MongoDB Cloud is HIPAA-ready and enables covered entities and their business associates to use a secure cloud database environment to process, maintain, and store protected health information (PHI).'Source: HIPAA Compliance with MongoDB
✅ They state they will sign their standard BAA with covered entities/business associates, which is again a good sign because if they don’t sign a BAA then it’s a deal-breaker for HIPAA compliance.
'Yes. MongoDB has a standard BAA that we present to customers for signature. Please contact us to begin the process.Source: MongoDB FAQ on Business Associate Agreement (BAA)
✅ They publicly outline various of the privacy & security safeguards they have in place, but these can be very broad statements and you need to check the low level details here.
'At MongoDB, we take security seriously. If you believe you have discovered a potential security vulnerability in one of our products, we encourage you to disclose it quickly to us.'Source: MongoDB Security Page
There is no one-size-fits-all set of requirements when selecting a 3rd party vendor as one of your HIPAA-compliant Business Associates, but here are some general guidelines:
First, you need to determine on which plans they offer HIPAA compliance and whether pricing makes sense for you:
You need to contact the vendor directly about Enterprise plans are eligible for HIPAA complianceSource: MongoDB Pricing Page
Then, you need to carefully review & sign their legal contracts, especially their Business Associate Agreement and Terms of Service (ask them for the latest versions - in some cases, you might need to sign an NDA):
MongoDB’s Business Associate Agreement
MongoDB's Terms of Service
Finally, at least once a year, reassess whether or not the vendor is still in compliance with HIPAA.
Source 1: U.S. Department of Health & Human Services HIPAA Privacy Rule Guidance Material
Source 2: U.S. Department of Health & Human Services HIPAA Security Rule Guidance Material
HIPAA compliance has no one-size-fits-all vendor assessment methodology but we have covered here various best practices on how to thoroughly evaluate MongoDB for HIPAA compliance, so that they can be eventually trusted to process or store your sensitive patient data.
Regardless of the above, for all your 3rd party vendors, you need to follow the fundamental HIPAA principle and always disclose to them the 'minimum necessary' information, which means only disclosing the amount of PHI you absolutely have to.
If you follow the 'minimum necessary' principle and you regularly evaluate your 3rd party vendors for their commitment to the HIPAA standards while having solid Business Associate Agreements with them in place, then you can minimize the risk of a potential HIPAA violation and decrease the probability of a damaging data breach happening in the first place.
The above is provided for informational purposes only and in order to help encourage adoption of security & privacy best practices for handling sensitive patient data. It does NOT constitute legal or healthcare advice in any way. The information presented here has been collected either from publicly available information or through direct email communication with the company, and everyone needs to perform their own independent HIPAA compliance audit before selecting any 3rd party vendor as their Business Associate that will process any type of their Protected Health Information (PHI). Keragon Inc is not liable for any damage or liabilities arising out of or connected in any manner with information found on this page.