United States: App Users Beware: Most Healthcare, Fitness Tracker, And Wellness Apps Are Not Covered By HIPAA And HHS's New Faqs Makes That Clear

Individuals who use healthcare apps such as fitness trackers, weight loss, wellness, exercise, etc., BEWARE! A couple of recent developments have highlighted the fact that most apps are not subject to HIPAA, which means that with broadly-worded privacy policy these healthcare apps can and do readily share healthcare and other data collected by the apps with third parties, including marketing and analytics companies, such as Google and Facebook. Some apps are sharing sensitive healthcare data even without a privacy policy.

The first eye-opening development was a study published in the journal JAMA Network Open (JAMA Study) reported that a number of healthcare apps marketed to people who wanted to stop smoking or who had depression were providing user data, including user health/medical information to third party advertisers and analytics companies such as Facebook.

Notably, the JAMA Study was clear that much of the data the apps reviewed shared did not immediately identify the individual user nor was it strictly medical. However, all but 3 of the 36 apps reviewed shared information that was a valuable predictor of individual behavioral conduct with advertisers or analytic companies. A few apps also shared sensitive information including substance use information app users had self-reported through the various apps.

The JAMA Study was certainly not the first study of its kind. The Wall Street Journal in a piece titled "You Give Apps Sensitive Personal Information. Then They Tell Facebook" revealed that Flo, a period-tracking app, shared users' health information, including period dates and pregnancy plans, with third-party sites such as Facebook.

Other health apps have self-reported security flaws and/or to sharing user personal health information with advertisers and analytic companies. Not surprisingly, the revelation that private health information was being shared to massive information-gathering powerhouses stirred up a lot of questions, such as:

  • How could this happen?
  • Isn't health/medical information private, not so easily shareable, or at least subject to higher privacy standards?
  • What was communicated to the users about what information would be shared and how?
  • What did the apps' privacy policies say about this information sharing or, rather, what didn't the privacy policies say?
    How can health app users make informed decisions about whether they want to use an app if they don't know who will be given access to their personal health information?

These are all very valid questions, which is why it is interesting that, around the same time that the JAMA Study was released, the Department of Health & Human Services Office for Civil Rights (HHS), which enforces HIPAA, issued five new FAQs addressing the applicability of HIPAA to health-related apps.

Before diving into HHS's FAQs, it is important to preface that most people assume that HIPAA protects health information from disclosure or at least provides some higher level of security over health information. However, HIPAA is narrower than most people believe, which it why the FAQs are interesting in that they demonstrate exactly where HIPAA's Privacy and Security Rule protections end, especially as it pertains to healthcare apps, and how health-information collection and sharing (as found in the JAMA Study) is so profound.

The key to understanding how these healthcare apps can disclose so much sensitive information unbeknownst to the users is understanding that, in most instances, the healthcare apps at issue are not covered by HIPAA and, therefore, not subject to HIPAA's Security Rule and Privacy Rule requirements. That means the healthcare data those app companies collect is also not protected by HIPAA's protections.

HIPAA does not provide a blanket, overarching protection to all medical/health/wellness information. HIPAA is limited to "covered entities" and their "business associates" who are sharing "protected health information" ("PHI" or "ePHI" when discussing electronic information) concerning "covered transactions". All of the quoted terms are specifically defined by HIPAA and most third-party healthcare apps do not qualify as a "covered entity", a "business associate", as having "PHI" or as engaging in a "covered transaction" for purposes of triggering HIPAA's requirements.

Looking to HHS's FAQs, they are specific to transactions between a patient, a healthcare provider, and the healthcare provider recommending a course of treatment that includes transmitting healthcare information to an app. This, in and of itself, sheds a tremendous amount of light as to how so much PHI information is not protected by HIPAA.

*** FAQ 572 ***

Does a HIPAA covered entity that fulfills an individual's request to transmit electronic protected health information (ePHI) to an app bear liability under HIPAA for the app's use or disclosure of the health information it received?

For instance, the first FAQ addresses whether a covered entity is liable under HIPAA if it sends ePHI to an app at the patient's request and the app discloses that information. This FAQ is important for understanding why third-party apps, which are wholly unaffiliated with any covered healthcare entity, can disclosure or otherwise share healthcare information without violating HIPAA.

As the FAQ answer makes clear, the key to determining how much protection a particular piece of PHI has is to understand the relationship between the healthcare provider that is recommending or requiring a patient to use a particular app and the app developer itself. If the app itself is developed by or on behalf of the healthcare covered entity, then the use of that app would be subject to HIPAA protections because the app developer would be either a covered entity or a business associate to the healthcare provider as defined by HIPAA. If, however, there is no such relationship and the app is strictly a third-party app with no affiliation to the healthcare provider, such as all those reviewed in the JAMA Network Open study, HIPAA would not apply or offer any protections for the disclosure of or sharing of PHI.

In other words, once health information is received from a covered entity, at the individual's direction by an app that is neither a covered entity nor a business associate (as defined under HIPAA), the information has lost its HIPAA protection it might have once had. This means that any subsequent use, disclosure, etc., of e-PHI by the non-covered entity would not trigger liability under HIPAA and no up-the-chain liability for the healthcare provider in the event of a breach, misuse, etc.

If, however, the app was developed for and/or provided on behalf of the covered healthcare provider, the covered healthcare provider would be liable for any breach or other improper disclosure of PHI.

Putting this into application, think about an app that is provided by and/or developed for a healthcare provider, such as a hospital. The app can be used to help patients check their records, schedule appointments, review their invoices, etc. That app and any use of the information provided by patients through the app would be subject to HIPAA's protections.

Conversely, a fitness tracking, wellness or health monitoring app that is advertised via Facebook, Instagram, or by other means, is found via the App Store, has no affiliation to a hospital or clinic, and was not recommended by a healthcare provider would not be subject to HIPAA.

*** FAQ 573 ***

What liability does a covered entity face if it fulfills an individual's request to send their ePHI using an unsecure method to an app?

The next FAQ is interesting because it analyzes whether a covered entity is liable if is grants an individual's request to send their PHI using an unsecured method to an app. It is not surprising that HHS determined that the covered entity would not be liable for unauthorized access to an individual's PHI if the individual requests their PHI be sent to an app via an unsecure method. It is surprising to most that this is even an option and that, somehow, an individual can somehow direct his or her PHI to be sent electronically through an unsecure channel.

The real issue identified here is not in HHS's answer, but rather brought to light with the knowledge that somehow individuals can consent to the unsecured transmission of their PHI because who would actually do that and why. As to the why, well, it is postured as a matter of convenience. As to who, well, the answer is that most people have no idea they are consenting to this. This consent is usually obtained when a patient arrives for a doctor's appointment and has to sign the HIPAA Privacy Notice that is put in front of them as the patient signs in for an appointment. Somewhere in that notice is a request for consent to allow PHI to be sent via unsecured channels if deemed quicker or more convenient by the healthcare provider.

The FAQ makes it clear that if PHI is sent this way via the individual's consent, the healthcare provider would not be liable for any loss that may occur during transmission to the app. HHS recommended, but did not require, that covered entities inform individuals of the potential risks involved in consenting to an unsecured transmission.

*** FAQ 574 ***

Where an individual directs a covered entity to send ePHI to a designated app, does a covered entity's electronic health record (EHR) system developer bear HIPAA liability after completing the transmission of ePHI to the app on behalf of the covered entity?

The next FAQ addressed liability after transmission by a covered entity's electronic health record system in the event a patient directs a covered entity to send PHI to a particular app. Again, and in line with the key issue identified initially above, HHS determined that the answer depends on the relationship, if any, between the covered entity, the EHR-system developer, and the app.

Here, a business associate relationship exists if the entity creates, receives, maintains, or transmits PHI on behalf of a covered entity in order to execute covered transactions of the covered entity.

No such business associate relationship exists between an EHR-system developer if the EHR-system developer does not own the app or, if it does, does not provide the app to, through or on behalf of the covered entity. For example, if the EHR-system developer creates an app, makes it available via the App Store as part of an entirely separate revenue stream or business unrelated to its role as a business associate to a healthcare covered entity, then it would not be liable under HPAA for any PHI use or disclosure it receives via its app.

***FAQ 575***

Can a covered entity refuse to disclose ePHI to an app chosen by an individual because of concerns about how the app will use or disclose the ePHI it receives?

Another FAQ addressed whether a covered entity could refuse to disclose a patient's PHI if it had concerns about the app's use or disclosure of the PHI. HHS determined that the covered entity's concerns were irrelevant because HIPAA general prohibits a covered entity from refusing to disclose PHI to a third-party app as requested by an individual if the PHI is in a form/format used by the app. This disclosure is allowed based on the individual's right of access under HIPAA. The other side of this is that the covered entity also does not bear responsibility for any misuse of the PHI during or after it transmits such data pursuant to an individual's request. And since the third-party app also bears no responsibility since it is not covered by HIPAA, it is really the individual who shoulders all the risk if he or she asks his/her ask their healthcare provider to transmit their PHI to a third-party app.

***FAQ 576***

Does HIPAA require a covered entity or its EHR system developer to enter into a business associate agreement with an app designated by the individual in order to transmit ePHI to the app?

The last FAQ analyzed whether HIPAA requires a covered entity or its EHR-system developer to enter into a business associate agreement with an app designated by the individual before transmitting PHI to the third party's app. Again, the answer is dependent on the relationship between the app developer and the covered entity and/or its EHR-system developer.

As set forth in other FAQ analysis, HHS reasserted its position that HIPAA does not require a covered entity or its EHR-system developer to enter into a business associate agreement with an app developer if the app does not create, receive, maintain or transmit PHI on behalf of or for the benefit of the covered entity.

If, however, the app was developed on behalf of the covered entity or provided by the covered entity, then a business associate agreement would be required because HIPAA would be triggered by the nature of the relationship.

What about the apps' privacy policies?

The other interesting tidbit to come out of the JAMA Study was how little the apps' privacy policies disclosed about how PHI would be shared. In some cases, the privacy policies were completely silent in this area. The issue then, and rightfully so, is how can the app developers get away with inaccurate privacy policies? The answer is that the oversight for privacy policies that are not covered by HIPAA are also not enforced by HHS; rather, they are subject to enforcement by the Federal Trade Commission. The FTC has levied fines and penalties against some website and app developers for miscommunications in their privacy policies, as the FTC considers the issue a matter of fraud under Section 5 of the Federal Trade Communication Act, but enforcement in this area is behind the technology. So, while the FTC has the enforcement power to make these app developers be honest and clear about their information sharing and disclosing practices, it is likely that there are just too many to go after and information such as the findings of the JAMA Study is just starting to shed light on this situation.

Takeaways


The key takeaway here is that app users bear the bulk of responsibility when they choose to input their personal health or other information into apps.

Health information does not have a universal protection and HIPAA is extremely limited as to its protections to such apps.

Even if the app is subject to HIPAA, there are a number of ways information can be disclosed via individual consent – and sometimes via consent the individual is not even sure they are granting.

When it comes to healthcare, wellness, fitness tracking, and other apps, it is critical for users to remember that the widespread information sharing to third party advertisers and analytics sites, such as Facebook and Google, applies exactly the same as it occurs with other information such as shopping preferences. An entity cannot share information that is not disclosed to it. So, unless an individual is sure the app he or she is using is covered under HIPAA and that does not otherwise allowed information to be shared to a third-party app via unsecured means, users must understand that information shared to an app may very well be shared to many other entities and people.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Similar Articles
Relevancy Powered by MondaqAI
 
In association with
Related Topics
 
Similar Articles
Relevancy Powered by MondaqAI
Related Articles
 
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Mondaq Free Registration
Gain access to Mondaq global archive of over 375,000 articles covering 200 countries with a personalised News Alert and automatic login on this device.
Mondaq News Alert (some suggested topics and region)
Select Topics
Registration (please scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions