In August 2021, the BBC reported on a pilot in England in which people receiving social care had sensors installed in their homes. The devices tracked movement, temperature and the use of particular appliances, and software analyzed the data to spot changes in behavior that might signal a health problem. The system used no cameras, but the idea of monitoring daily routines inside someone’s home raised obvious privacy questions.
Remote monitoring, connected devices and cloud platforms all create health information in new places. This article looks at what that means for a healthcare organization in the United States under the HIPAA Security Rule, and what to check before adopting a new technology. It is general information, not legal advice; your counsel and compliance lead are the authority on how the rule applies to you.
Who the Security Rule applies to
The HIPAA Security Rule is in 45 CFR Part 164, Subpart C. Under 45 CFR 164.302, a covered entity or business associate must comply with its standards and requirements with respect to electronic protected health information (ePHI). Whether your organization, or a vendor you work with, is a covered entity or a business associate is defined in the HIPAA regulations; ask counsel if you are unsure.
What the rule asks for
The general rules in 45 CFR 164.306 require covered entities and business associates to ensure the confidentiality, integrity and availability of all ePHI they create, receive, maintain or transmit, and to protect against reasonably anticipated threats to it. The rule is flexible about how: in choosing security measures, an organization must take into account its size, complexity and capabilities, its technical infrastructure, the costs of the measures, and the probability and criticality of potential risks.
Two parts matter most when new technology arrives.
The administrative safeguards in 45 CFR 164.308 list risk analysis and risk management as required implementation specifications. Risk analysis means an accurate and thorough assessment of the potential risks and vulnerabilities to ePHI. A new device, app or cloud service changes those risks, so it belongs in the analysis.
The technical safeguards in 45 CFR 164.312 set standards for access control, audit controls, integrity, person or entity authentication, and transmission security. Within access control, unique user identification and an emergency access procedure are labeled “Required,” while automatic logoff and encryption and decryption are labeled “Addressable.” Under 164.306, an addressable specification must be assessed for whether it is reasonable and appropriate, not simply skipped.
Why “HIPAA compliant” software is not the whole answer
Vendors often describe products as HIPAA compliant. Microsoft’s own HIPAA documentation notes that there is currently no certification standard approved by the Department of Health and Human Services for a business associate to demonstrate HIPAA compliance. What a vendor can offer is a business associate agreement and features that support your safeguards.
That agreement matters. Under 164.308(b)(1), a covered entity may let a business associate create, receive, maintain or transmit ePHI on its behalf only if it obtains satisfactory assurances, in line with 45 CFR 164.314(a), that the business associate will appropriately safeguard the information. Section 164.314(a) says the contract must provide that the business associate will comply with the applicable requirements, flow those requirements down to its subcontractors, and report security incidents it becomes aware of.
Even with an agreement in place, configuration and behavior stay with you. A document shared through a public link, an account without MFA or a former employee who still has access can expose patient data on a platform that offers every safeguard.
Questions to ask before adopting new health technology
- What patient information does it collect, and where is that data stored?
- Will the vendor sign a business associate agreement, and which of its services does the agreement cover?
- Does each user get a unique login, and can you require MFA?
- Is data encrypted when it travels between the device, the app and the vendor’s systems?
- Can you get audit logs showing who viewed or changed records?
- How do you remove a user’s access, and how is data returned or destroyed if you leave the vendor?
- Has the new technology been added to your risk analysis?
What to do next
List every system that stores or transmits patient information, including newer additions such as patient messaging, remote monitoring devices and cloud file sharing, and confirm each one has a business associate agreement where one is needed and appears in your current risk analysis. Have your compliance lead or counsel review the results. Our HIPAA compliance and healthcare IT pages describe the technical side of that work. Titan Tech is not an auditor or assessor, but you can request a Blind Spot Scan for a technical look at accounts, devices and backups.