In thinking about patient privacy, many folks assume that HIPAA is the first and last word on the subject.
Nothing could be farther from the truth. Protected health information under HIPAA (PHI) is also protected by a variety of other federal and state regulatory schemes. In addition, there is personal information that is not subject to HIPAA at all but is subject to other protections — PII.
What falls into the PII category? It can include a lot of different sorts of information, but keep in mind that it includes personal information that could be PHI under HIPAA if it were collected by a covered entity or business associate. This subset of PII could include steps and other data collected by a personal activity tracker (Fitbit and the like), information input or collected by health apps on a smartphone, and more. It may also include personal information less closely connected to any health care provider or payor as well, such as food diaries, personal logs of health related information, symptoms, etc. PII does not include electronic health record data, but it does include EHR data if it is downloaded by a patient into a third party repository (i.e., a PHR that is not a service of the provider’s EHR).
Last year, the FTC released a tool intended to help app developers determine what their compliance obligations may be, and ONC released an updated model privacy notice. At the time, ONC noted that it was time to update a tool originally focused on PHRs and broaden it to cover activity trackers, smartphone apps and more. (ONC had previously published a model privacy notice in 2011.)
Recognizing that many web service and app developers have not done a great job communicating privacy policies and protections to consumers, the federales mounted a challenge to encourage the development of easy to understand privacy policies and easy to configure protections. Winners of the MPN privacy notice snapshot challenge were announced recently. The top finalist posted an example of its model privacy notice and a set of configurable controls available on GitHub so that developers may download and use them in their application designs.
ONC is encouraging their use — and it’s not a bad idea.
Given the range of cybersecurity issues in the news these days, and the increasingly widespread concerns about data security, not to mention end users’ rights, it makes sense for web service and app developers to be as transparent as possible about their privacy policies. In addition, thanks to the ever-increasing globalization of commerce, US developers need to be concerned about international standards, and the compliance date for the EU’s General Data Protection Regulation (GDPR) is less than a year away. Privacy policies and other policies and procedures that are adequate for compliance with US law are not, on their own, sufficient for compliance with EU or other international laws, and the more explicit approach laid out in the model privacy notice will go some distance towards readying US businesses for the next step on this journey — GDPR compliance.
This article was originally published on HealthBlawg and is republished here with permission.