United States: Health Apps And HIPAA: OCR Publishes New Privacy Guidance For Health App Developers

On February 11, 2016, in response to requests from developers of mobile health applications, the Department of Health and Human Services Office for Civil Rights ("OCR") released a new guidance document addressing the applicability of the Health Insurance Portability and Accountability Act ("HIPAA") to applications that collect, store or transmit health information. The guidance document, entitled "Health App Use Scenarios & HIPAA" ("Health App Guidance"), sets forth several factual scenarios involving mobile health apps, along with OCR's explanation of whether, in each scenario, HIPAA would apply to the developer of the app.


  • OCR's Health App Guidance details six scenarios in which Health Apps collect, store and/or transmit health information directly from consumers and analyzes the relationships developers may have with: (i) consumers/patients, (ii) covered entities ("CEs"), i.e., those entities that are governed directly by HIPAA (health care providers, health plans and clearinghouses) and (iii) business associates ("BAs"), i.e., persons or entities that receive protected health information ("PHI") in order to perform certain functions or activities on behalf of CEs.
  • The Health App Guidance also clarifies that a health app that is downloaded and used solely by individual consumers does not result in the app developer's becoming subject to HIPAA. The reason for this result is that the developer is not creating, receiving, maintaining or transmitting PHI on behalf of a CE or BA. On the contrary, the PHI being used or stored by the app is directly from, and for, the consumer.
  • However, a developer who contracts directly with a CE to collect, maintain or transmit PHI through a particular health app is deemed to be a BA under HIPAA, and accordingly will be subject to HIPAA requirements because the developer is providing a service for the benefit of the CE and has access to the PHI of the CE. A developer who contracts with a BA on behalf of a CE to do the same thing likewise will be subject to HIPAA.

Major Elements of OCR Health App Guidance

The Health App Guidance is the latest development to arise from OCR's mHealth Developer Portal, a platform launched last fall that allows health app developers and others to ask OCR questions regarding health technology and privacy laws, including HIPAA. The mHealth Developer Portal also serves as a vehicle for OCR to publish guidance to educate developers on how HIPAA regulations may apply to new technologies.

The Health App Guidance describes, through the use of six specific scenarios, a broad spectrum of health apps. Health apps that are created and offered directly by or on behalf of CEs or BAs and that store or transmit PHI unambiguously are subject to HIPAA. For example, an independent health app developer that contracts with a health care provider ("Provider") and creates a health app that allows patients to access and manage their health records as part of the Provider's patient portal is clearly a BA and, therefore, must follow all requirements of HIPAA and related regulations.

Scenarios in which Health Apps are Not BAs. The Health App Guidance provides additional clarity for developers who create health apps that are downloaded and used solely by individual consumers. The individual consumer is not a CE or a BA and is voluntarily downloading the app for his/her personal use. Therefore, these developers are not creating, receiving, maintaining or transmitting PHI on behalf of a CE or BA. Accordingly, OCR has stated that such a developer is clearly not a BA for this same reason even if: (i) a Provider recommends the health app to his or her patient, (ii) the consumer uploads his or her electronic health record ("EHR") to the health app from a Provider's patient portal or (iii) the app developer enters into an interoperability agreement with the Provider that allows the consumer to transmit information from the health app to the Provider.

Scenarios in which Health Apps are BAs. In contrast, the Health App Guidance details two scenarios in which a developer will be classified as a BA. In the first scenario, a Provider has contracted directly with the health app developer for patient management services, services that include remote patient health counseling, monitoring of patients' food and exercise, patient messaging and EHR integration. In the second scenario, a health plan ("Plan") offers a health app that allows Plan members to download and store health plan records, to check the status of claims/coverage decisions and to document and track their general wellness information. The Plan then analyzes the health and wellness information uploaded to the health app by members. Because both the Provider and the Plan as CEs are contracting directly with the Health App developer it is considered a BA. In contrast, in this latter scenario, the Health App Guidance specifies that if the same developer offers a separate, direct-to-consumer version of the health app with the same functionality, this version of the health app would not be subject to the HIPAA rules as long as the developer keeps the health information contained in the two versions of the health app entirely separate.

OCR's Key Questions. The Health App Guidance concludes with a series of questions that developers should consider about their business and their health apps to determine if they are BAs. These questions include: (i) whether the health app creates, receives, maintains or transmits identifiable information; (ii) who the clients for the health app are, and whether those clients include CEs or BAs; (iii) whether the health app is selected independently by the consumer; (iv) whether all decisions to transmit health data to third parties are controlled by the consumer; and (v) whether the developer has any contractual or other relationships with third party entities, other than interoperability agreements. OCR does not provide an analysis of exactly how the answers to these questions may affect classification of a health app developer as a BA; instead, and key to the analysis, OCR offers these questions to help developers determine whether their health app's functions and business model focus primarily on consumers, or on creating, receiving, maintaining or transmitting PHI for CEs. If the health app is focused on the latter, its developer will be classified as a BA and be subject to HIPAA.

Context of OCR Health App Guidance

The Health App Guidance follows requests from app developers for additional guidance from OCR on when and how HIPAA applies to the burgeoning field of health apps. OCR has signaled its intention that the Health App Guidance will provide needed clarity and facilitate innovation. Jocelyn Samuels, the Director of OCR, has written in a blog post: "We hope these new scenarios will help developers determine how federal regulations might apply to products they are building; we also hope they will reduce some of the uncertainty that can be a barrier to innovation."

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.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). 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 & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd 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 or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.