FDA Overhauls its Draft Guidance on Clinical Decision Support (“CDS”) Software

Ropes & Gray LLP

Ropes & Gray LLP

On September 27, 2019, the U.S. Food and Drug Administration (“FDA”) issued a revised draft guidance entitled “Clinical Decision Support Software” (the “CDS Draft Guidance”), describing the agency’s proposed approach to regulating CDS software. The CDS Draft Guidance revises a previously issued draft guidance on the same subject released by FDA on December 8, 2017.

In its public statement upon release of the CDS Draft Guidance, FDA explained that the revisions to the guidance are intended to address the many stakeholder comments it received on the original draft, particularly relating to the draft’s failure to consider the potential risk of patient harm if a CDS software product were to malfunction. Consequently, the most notable change from the 2017 draft guidance was to incorporate key elements of the software risk categorization framework FDA had helped develop through the International Medical Device Regulatory Forum in 2014 (“IMDRF Framework”). FDA asserts that the approach set forth in the CDS Draft Guidance will strike the right balance between ensuring patient safety and promoting innovation. We expect that some, however, will criticize the draft guidance as missing the mark: providing additional regulatory clarity and latitude for certain low-risk CDS software products, but creating additional ambiguity and uncertainty for others.

21st Century Cures Act and FDA’s Initial CDS Draft Guidance

As outlined in a previous Ropes & Gray Alert summarizing the 2017 CDS draft guidance, Section 3060 of the 21st Century Cures Act (Section 520(o) of the Federal Food, Drug, and Cosmetic Act (“FDCA”)) removed certain software functions from the definition of “device.” One category of software no longer considered a device under FDCA § 520(o)(1)(E) is software that:

  1. Is not intended to acquire, process, or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system;
  2. Is intended to display, analyze, or print medical information about a patient or other medical information, like clinical practice guidelines;
  3. Is intended to support or provide recommendations to an HCP about prevention, diagnosis, or treatment of a disease or condition; and
  4. Is intended to enable HCPs to independently review the basis for the software’s recommendations so HCPs do not primarily rely on the recommendations when making a clinical diagnosis or treatment decision.

In the 2017 draft guidance, FDA proposed to interpret these provisions such that a software function meeting the first three criteria would be considered CDS, but would only be exempt from FDA regulatory oversight if it also met the fourth criterion. It was FDA’s emphasis on this fourth criterion that elicited the bulk of industry criticism. In particular, FDA made the transparency of a software function the key determinant in whether a CDS product would be considered a regulated medical device, regardless of the product’s specific risk profile. Under its previous proposed framework, for example, regardless of whether a software function was intended to provide clinical recommendations for a self-limiting disease like the common cold or a life-threatening disease like cancer, FDA would have decided whether to regulate the software based entirely on whether the software’s inputs and rationale were sufficiently transparent to the user. The risk to the user or patient of the software providing unreliable information would not have been the determining factor.

Partial Incorporation of the IMDRF Risk Categories

In response to comments submitted on the 2017 draft guidance, FDA agreed to incorporate risk-based principles outlined in the IMDRF Framework, a document established to promote international harmonization of regulation of Software as a Medical Device (“SaMD”). The IMDRF Framework describes two major factors for the risk categorization of a SaMD (CDS is one type of SaMD):

  1. The significance of information provided by a SaMD to the health care decision (i.e., whether the information is intended to “inform” clinical management, “drive” clinical management, or “treat or diagnose” a disease or condition), and
  2. The state of the health care situation or condition (i.e., whether the situation or condition is non-serious, serious, or critical). 

These two factors are combined to create a matrix of risk profiles for SaMD from “low impact” (I) to “very high impact” (IV). 

State of Healthcare situation or condition

Significance of information provided by SaMD to healthcare decision

Treat or Diagnose

Drive clinical management

Inform clinical management













 FDA has proposed to incorporate this framework into the newly released CDS Draft Guidance in two ways. First, FDA has evaluated the third statutory criterion from the 21st Century Cures Act (requiring that the software be intended to “support or provide recommendations to” an HCP about prevention, diagnosis, or treatment of a disease or condition) by reference to the “significance of information” factor from the IMDRF Framework. Specifically, FDA states that only SaMD functions that “inform clinical management” meet the definition of a CDS, but functions that either “drive clinical management” or “treat or diagnose” go beyond the statutory criterion that a CDS “support or provide recommendations to an HCP.” This proposed interpretation is significant because it would mean that SaMD functions that do more than “inform” clinical management, at least some of which might have been wholly exempt from the definition of a device under the 2017 draft guidance if sufficiently transparent, would no longer be exempt from the definition of device nor eligible for enforcement discretion. This interpretation is likely to elicit negative comment, as it is far from clear that devices that “aid” or “guide” clinical decision-making (which is how the IMDRF Framework defines the term “drive clinical management”) can be viewed as categorically distinct from devices that “support or provide recommendations” for clinical decision-making (the statutory language). In other words, whereas some software products that “aid” or “guide” clinical decision-making conceivably might do more than “support or provide recommendations” for clinical decision-making, it is not clear how FDA has concluded that all such software products must go beyond what Congress intended by the phrase “support or provide recommendations.” It is also not clear how, if at all, FDA is taking into consideration that software functions that “drive” clinical management presumably are not intended to “trigger an immediate or near-term action,” according to the IMDRF Framework’s criteria.

The second way in which FDA incorporated the IMDRF Framework into its revised draft guidance was to address some commenters’ requests for enforcement discretion for “low impact” CDS functions that are not statutorily exempt from the definition of device because they do not meet the fourth prong of the statutory test, dealing with transparency. As depicted in the table included above, this would include CDS functions that:

  1. Provide information to drive clinical management of a disease in a non-serious situation or condition;
  2. Provide information to inform clinical management for a disease or condition in a serious situation or condition; and
  3. Provide information to inform clinical management for a disease or condition in a non-serious situation or condition.

Although FDA declined to extend enforcement discretion to cover all of these categories, the draft guidance proposes to do so for category 3. As noted above, the CDS Draft Guidance considers software in category 1 not to qualify as CDS, because it is used to drive clinical management. The CDS Draft Guidance does not mention software in category 2 at all or explain its rationale for considering such CDS to be of “higher risk” than the other devices categorized by the IMDRF Framework as “low impact.”

The CDS Draft Guidance provides the following examples of CDS for which FDA will now exercise enforcement discretion because, although they are not sufficiently transparent to be exempt from the definition of device, they are intended to “inform clinical management” for “non-serious situations or conditions”:

  1. Software that provides recommendations of potential allergens and common cold symptoms based on location-specific electronic health records, environmental conditions, and patient-reported outcomes to provide the HCP with options for different diagnoses (e.g., seasonal allergic rhinitis vs. common cold).
  2. Machine-learning algorithm, for which the logic and inputs are not explained, that trends and classifies patient-specific data (e.g., blood test results, weight) to alert HCPs to potential triggers that may be indicative of cholesterol management issues.
  3. Software intended for HCPs, where the basis for the recommendation is not disclosed to the user, to analyze patient information to determine which over-the-counter (OTC) allergy drug class is likely to be most effective in alleviating the patient’s seasonal allergies.

The CDS Draft Guidance also provides examples of software functions that FDA intends to regulate because, although they meet the first three criteria of the statutory CDS definition, they do not meet the fourth criterion and they are intended to “inform clinical management” for “serious or critical situations or conditions.” These examples include machine learning algorithms, for which the logic and inputs are not explained, (i) that identify hospitalized, type I diabetes patients at increased risk for postoperative cardiovascular events or (ii) that categorize likely symptoms of seasonal influenza for each season based on location and current electronic health records of patients diagnosed or suspected to have influenza to assist HCPs in differentiating between common flu symptoms and other illnesses. Likewise, FDA says that it intends to regulate software, for which the inputs are not explained, that identifies patients who may exhibit signs of opioid addiction based on patient-specific data, family history, electronic health records data, prescription patterns, and geographical data.

Other Changes

While the most significant change to the CDS Draft Guidance is the incorporation of the risk-based framework described above, FDA did make some additional changes of note to the draft guidance.

Transparency Criterion. FDA appears to have softened its interpretation of the fourth statutory criterion regarding the “transparency” of a CDS to be exempt from the definition of “device.” In the 2017 draft guidance, FDA interpreted the requirement that HCPs be able to “independently review the basis of” and “not primarily rely” on recommendations from a CDS as a requirement that an HCP be able to “reach the same recommendation . . . without relying primarily on the software function.” This interpretation was viewed by some as limiting exemption of a CDS to those software functions that perform simple calculations that could be perfectly replicated by HCPs. In contrast, the revised CDS Draft Guidance focuses on whether an HCP could theoretically “understand” or “evaluate” the basis for a recommendation (i.e., whether an algorithm’s logic and inputs are adequately described and available to the HCP). This shift hews more closely to the statutory language and has potentially powerful implications for complex software like machine learning algorithms.

Patient Decision Support Software. Another notable change to the draft guidance is that FDA collapsed its discussion of “Patient Decision Support” software—which it had previously considered separately from CDS in the 2017 draft guidance—into its more general CDS analysis. Under the 2017 draft guidance, FDA created a separate category of software that operated like a CDS (i.e., met the first three statutory criteria), but provided recommendations directly to patients or caregivers rather than HCPs. Because the third criterion in the statute explicitly refers to HCPs, FDA stated that patient/caregiver-directed software operating in this manner could never be exempt from the definition of “device.” Instead, FDA explained that it would exercise enforcement discretion over software products that otherwise met all four statutory criteria, but were directed toward patients or caregivers. The CDS Draft Guidance continues to preserve this distinction in effect, but now refers to such software as one subset of “device CDS.”

Like HCP-directed CDS, the revised CDS Draft Guidance also applies the principles of the IMDRF Framework to patient/caregiver-directed CDS. However, the effect for patient/caregiver-directed CDS is to narrow the enforcement discretion that was available under the 2017 draft guidance. The CDS Draft Guidance maintains the requirement from the 2017 guidance that patient/caregiver-directed CDS meet the fourth criterion of transparency (i.e., be intended to permit the patient to independently evaluate the basis for the software’s recommendations) to receive enforcement discretion. The CDS Draft Guidance proposes to further narrow the types of software functions that would have been eligible for enforcement discretion, though, by adding the requirements that the software be intended to “inform clinical management” for “non-serious health care situations or conditions.” Thus, for example, the following devices described in the CDS Draft Guidance would previously have been eligible for enforcement discretion if sufficiently transparent but now would be subject to FDA oversight because they focus on a serious condition:

  • Software that aggregates data from continuous glucose monitoring, activity trackers, and food logs to help insulin-dependent type 2 diabetic patients identify potential lifestyle triggers for hypoglycemic events and recommends corrective treatment options (e.g., timing of insulin dosing).
  • A software function that provides recommendations to caregivers of pediatric patients with cystic fibrosis by aggregating information on when they should bring such children to the emergency room, based on patient-specific symptoms and care guidelines.


The CDS Draft Guidance marks a significant change in FDA’s thinking about how to regulate CDS software products. That FDA saw the need to re-issue the original draft guidance as yet another draft for public comment reflects FDA’s recognition that it has substantially altered its thinking. In particular, the inclusion of a risk-based enforcement framework for CDS is a major shift in thinking that arguably aligns better both with Congressional intent and the regulatory principles FDA itself has espoused in the past. On the other hand, the CDS Draft Guidance may be viewed by some as a “half-loaf” compromise under which FDA would continue to regulate a wide variety of CDS functions that, under the IMDRF Framework criteria, would appear to be “low impact.”

Industry stakeholders have the opportunity to submit public comments to the revised draft guidance by December 26, 2019. FDA is also hosting a webinar on November 4, 2019 to discuss and answer questions about the CDS Draft Guidance.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Ropes & Gray LLP | Attorney Advertising

Written by:

Ropes & Gray LLP

Ropes & Gray LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide

JD Supra Privacy Policy

Updated: May 25, 2018:

JD Supra is a legal publishing service that connects experts and their content with broader audiences of professionals, journalists and associations.

This Privacy Policy describes how JD Supra, LLC ("JD Supra" or "we," "us," or "our") collects, uses and shares personal data collected from visitors to our website (located at www.jdsupra.com) (our "Website") who view only publicly-available content as well as subscribers to our services (such as our email digests or author tools)(our "Services"). By using our Website and registering for one of our Services, you are agreeing to the terms of this Privacy Policy.

Please note that if you subscribe to one of our Services, you can make choices about how we collect, use and share your information through our Privacy Center under the "My Account" dashboard (available if you are logged into your JD Supra account).

Collection of Information

Registration Information. When you register with JD Supra for our Website and Services, either as an author or as a subscriber, you will be asked to provide identifying information to create your JD Supra account ("Registration Data"), such as your:

  • Email
  • First Name
  • Last Name
  • Company Name
  • Company Industry
  • Title
  • Country

Other Information: We also collect other information you may voluntarily provide. This may include content you provide for publication. We may also receive your communications with others through our Website and Services (such as contacting an author through our Website) or communications directly with us (such as through email, feedback or other forms or social media). If you are a subscribed user, we will also collect your user preferences, such as the types of articles you would like to read.

Information from third parties (such as, from your employer or LinkedIn): We may also receive information about you from third party sources. For example, your employer may provide your information to us, such as in connection with an article submitted by your employer for publication. If you choose to use LinkedIn to subscribe to our Website and Services, we also collect information related to your LinkedIn account and profile.

Your interactions with our Website and Services: As is true of most websites, we gather certain information automatically. This information includes IP addresses, browser type, Internet service provider (ISP), referring/exit pages, operating system, date/time stamp and clickstream data. We use this information to analyze trends, to administer the Website and our Services, to improve the content and performance of our Website and Services, and to track users' movements around the site. We may also link this automatically-collected data to personal information, for example, to inform authors about who has read their articles. Some of this data is collected through information sent by your web browser. We also use cookies and other tracking technologies to collect this information. To learn more about cookies and other tracking technologies that JD Supra may use on our Website and Services please see our "Cookies Guide" page.

How do we use this information?

We use the information and data we collect principally in order to provide our Website and Services. More specifically, we may use your personal information to:

  • Operate our Website and Services and publish content;
  • Distribute content to you in accordance with your preferences as well as to provide other notifications to you (for example, updates about our policies and terms);
  • Measure readership and usage of the Website and Services;
  • Communicate with you regarding your questions and requests;
  • Authenticate users and to provide for the safety and security of our Website and Services;
  • Conduct research and similar activities to improve our Website and Services; and
  • Comply with our legal and regulatory responsibilities and to enforce our rights.

How is your information shared?

  • Content and other public information (such as an author profile) is shared on our Website and Services, including via email digests and social media feeds, and is accessible to the general public.
  • If you choose to use our Website and Services to communicate directly with a company or individual, such communication may be shared accordingly.
  • Readership information is provided to publishing law firms and authors of content to give them insight into their readership and to help them to improve their content.
  • Our Website may offer you the opportunity to share information through our Website, such as through Facebook's "Like" or Twitter's "Tweet" button. We offer this functionality to help generate interest in our Website and content and to permit you to recommend content to your contacts. You should be aware that sharing through such functionality may result in information being collected by the applicable social media network and possibly being made publicly available (for example, through a search engine). Any such information collection would be subject to such third party social media network's privacy policy.
  • Your information may also be shared to parties who support our business, such as professional advisors as well as web-hosting providers, analytics providers and other information technology providers.
  • Any court, governmental authority, law enforcement agency or other third party where we believe disclosure is necessary to comply with a legal or regulatory obligation, or otherwise to protect our rights, the rights of any third party or individuals' personal safety, or to detect, prevent, or otherwise address fraud, security or safety issues.
  • To our affiliated entities and in connection with the sale, assignment or other transfer of our company or our business.

How We Protect Your Information

JD Supra takes reasonable and appropriate precautions to insure that user information is protected from loss, misuse and unauthorized access, disclosure, alteration and destruction. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. You should keep in mind that no Internet transmission is ever 100% secure or error-free. Where you use log-in credentials (usernames, passwords) on our Website, please remember that it is your responsibility to safeguard them. If you believe that your log-in credentials have been compromised, please contact us at privacy@jdsupra.com.

Children's Information

Our Website and Services are not directed at children under the age of 16 and we do not knowingly collect personal information from children under the age of 16 through our Website and/or Services. If you have reason to believe that a child under the age of 16 has provided personal information to us, please contact us, and we will endeavor to delete that information from our databases.

Links to Other Websites

Our Website and Services may contain links to other websites. The operators of such other websites may collect information about you, including through cookies or other technologies. If you are using our Website or Services and click a link to another site, you will leave our Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We are not responsible for the data collection and use practices of such other sites. This Policy applies solely to the information collected in connection with your use of our Website and Services and does not apply to any practices conducted offline or in connection with any other websites.

Information for EU and Swiss Residents

JD Supra's principal place of business is in the United States. By subscribing to our website, you expressly consent to your information being processed in the United States.

  • Our Legal Basis for Processing: Generally, we rely on our legitimate interests in order to process your personal information. For example, we rely on this legal ground if we use your personal information to manage your Registration Data and administer our relationship with you; to deliver our Website and Services; understand and improve our Website and Services; report reader analytics to our authors; to personalize your experience on our Website and Services; and where necessary to protect or defend our or another's rights or property, or to detect, prevent, or otherwise address fraud, security, safety or privacy issues. Please see Article 6(1)(f) of the E.U. General Data Protection Regulation ("GDPR") In addition, there may be other situations where other grounds for processing may exist, such as where processing is a result of legal requirements (GDPR Article 6(1)(c)) or for reasons of public interest (GDPR Article 6(1)(e)). Please see the "Your Rights" section of this Privacy Policy immediately below for more information about how you may request that we limit or refrain from processing your personal information.
  • Your Rights
    • Right of Access/Portability: You can ask to review details about the information we hold about you and how that information has been used and disclosed. Note that we may request to verify your identification before fulfilling your request. You can also request that your personal information is provided to you in a commonly used electronic format so that you can share it with other organizations.
    • Right to Correct Information: You may ask that we make corrections to any information we hold, if you believe such correction to be necessary.
    • Right to Restrict Our Processing or Erasure of Information: You also have the right in certain circumstances to ask us to restrict processing of your personal information or to erase your personal information. Where you have consented to our use of your personal information, you can withdraw your consent at any time.

You can make a request to exercise any of these rights by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

You can also manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard.

We will make all practical efforts to respect your wishes. There may be times, however, where we are not able to fulfill your request, for example, if applicable law prohibits our compliance. Please note that JD Supra does not use "automatic decision making" or "profiling" as those terms are defined in the GDPR.

  • Timeframe for retaining your personal information: We will retain your personal information in a form that identifies you only for as long as it serves the purpose(s) for which it was initially collected as stated in this Privacy Policy, or subsequently authorized. We may continue processing your personal information for longer periods, but only for the time and to the extent such processing reasonably serves the purposes of archiving in the public interest, journalism, literature and art, scientific or historical research and statistical analysis, and subject to the protection of this Privacy Policy. For example, if you are an author, your personal information may continue to be published in connection with your article indefinitely. When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize it, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible.
  • Onward Transfer to Third Parties: As noted in the "How We Share Your Data" Section above, JD Supra may share your information with third parties. When JD Supra discloses your personal information to third parties, we have ensured that such third parties have either certified under the EU-U.S. or Swiss Privacy Shield Framework and will process all personal data received from EU member states/Switzerland in reliance on the applicable Privacy Shield Framework or that they have been subjected to strict contractual provisions in their contract with us to guarantee an adequate level of data protection for your data.

California Privacy Rights

Pursuant to Section 1798.83 of the California Civil Code, our customers who are California residents have the right to request certain information regarding our disclosure of personal information to third parties for their direct marketing purposes.

You can make a request for this information by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

Some browsers have incorporated a Do Not Track (DNT) feature. These features, when turned on, send a signal that you prefer that the website you are visiting not collect and use data regarding your online searching and browsing activities. As there is not yet a common understanding on how to interpret the DNT signal, we currently do not respond to DNT signals on our site.

Access/Correct/Update/Delete Personal Information

For non-EU/Swiss residents, if you would like to know what personal information we have about you, you can send an e-mail to privacy@jdsupra.com. We will be in contact with you (by mail or otherwise) to verify your identity and provide you the information you request. We will respond within 30 days to your request for access to your personal information. In some cases, we may not be able to remove your personal information, in which case we will let you know if we are unable to do so and why. If you would like to correct or update your personal information, you can manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard. If you would like to delete your account or remove your information from our Website and Services, send an e-mail to privacy@jdsupra.com.

Changes in Our Privacy Policy

We reserve the right to change this Privacy Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our Privacy Policy will become effective upon posting of the revised policy on the Website. By continuing to use our Website and Services following such changes, you will be deemed to have agreed to such changes.

Contacting JD Supra

If you have any questions about this Privacy Policy, the practices of this site, your dealings with our Website or Services, or if you would like to change any of the information you have provided to us, please contact us at: privacy@jdsupra.com.

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at www.jdsupra.com) (our "Website") and our services (such as our email article digests)(our "Services") use a standard technology called a "cookie" and other similar technologies (such as, pixels and web beacons), which are small data files that are transferred to your computer when you use our Website and Services. These technologies automatically identify your browser whenever you interact with our Website and Services.

How We Use Cookies and Other Tracking Technologies

We use cookies and other tracking technologies to:

  1. Improve the user experience on our Website and Services;
  2. Store the authorization token that users receive when they login to the private areas of our Website. This token is specific to a user's login session and requires a valid username and password to obtain. It is required to access the user's profile information, subscriptions, and analytics;
  3. Track anonymous site usage; and
  4. Permit connectivity with social media networks to permit content sharing.

There are different types of cookies and other technologies used our Website, notably:

  • "Session cookies" - These cookies only last as long as your online session, and disappear from your computer or device when you close your browser (like Internet Explorer, Google Chrome or Safari).
  • "Persistent cookies" - These cookies stay on your computer or device after your browser has been closed and last for a time specified in the cookie. We use persistent cookies when we need to know who you are for more than one browsing session. For example, we use them to remember your preferences for the next time you visit.
  • "Web Beacons/Pixels" - Some of our web pages and emails may also contain small electronic images known as web beacons, clear GIFs or single-pixel GIFs. These images are placed on a web page or email and typically work in conjunction with cookies to collect data. We use these images to identify our users and user behavior, such as counting the number of users who have visited a web page or acted upon one of our email digests.

JD Supra Cookies. We place our own cookies on your computer to track certain information about you while you are using our Website and Services. For example, we place a session cookie on your computer each time you visit our Website. We use these cookies to allow you to log-in to your subscriber account. In addition, through these cookies we are able to collect information about how you use the Website, including what browser you may be using, your IP address, and the URL address you came from upon visiting our Website and the URL you next visit (even if those URLs are not on our Website). We also utilize email web beacons to monitor whether our emails are being delivered and read. We also use these tools to help deliver reader analytics to our authors to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

Analytics/Performance Cookies. JD Supra also uses the following analytic tools to help us analyze the performance of our Website and Services as well as how visitors use our Website and Services:

  • HubSpot - For more information about HubSpot cookies, please visit legal.hubspot.com/privacy-policy.
  • New Relic - For more information on New Relic cookies, please visit www.newrelic.com/privacy.
  • Google Analytics - For more information on Google Analytics cookies, visit www.google.com/policies. To opt-out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout. This will allow you to download and install a Google Analytics cookie-free web browser.

Facebook, Twitter and other Social Network Cookies. Our content pages allow you to share content appearing on our Website and Services to your social media accounts through the "Like," "Tweet," or similar buttons displayed on such pages. To accomplish this Service, we embed code that such third party social networks provide and that we do not control. These buttons know that you are logged in to your social network account and therefore such social networks could also know that you are viewing the JD Supra Website.

Controlling and Deleting Cookies

If you would like to change how a browser uses cookies, including blocking or deleting cookies from the JD Supra Website and Services you can do so by changing the settings in your web browser. To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you every time a site wishes to save a cookie. It's also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use your browser's "Help" function or alternatively, you can visit http://www.aboutcookies.org which explains, step-by-step, how to control and delete cookies in most browsers.

Updates to This Policy

We may update this cookie policy and our Privacy Policy from time-to-time, particularly as technology changes. You can always check this page for the latest version. We may also notify you of changes to our privacy policy by email.

Contacting JD Supra

If you have any questions about how we use cookies and other tracking technologies, please contact us at: privacy@jdsupra.com.

- hide

This website uses cookies to improve user experience, track anonymous site usage, store authorization tokens and permit sharing on social media networks. By continuing to browse this website you accept the use of cookies. Click here to read more about how we use cookies.