240 Matching Annotations
  1. Feb 2023
    1. confidentiality provisions in place

      This is not true.

      They shared data with Facebook and Facebooks "confidentiality provisions" say "This is ours now and we will make this public". And they did in fact share the information. Which is how the watchdog found out about it.

      Specifically, the FTC stated in its compliant:

      ...GoodRx has taken no action to limit how Advertising Platforms like Facebook, Google, and Criteo, and other third parties like Branch and Twilio, could use the personal health information it shared with them. Rather, GoodRx agreed to each of these third parties’ standard terms of service, or entered into agreements that permitted each Advertising Platform to use GoodRx users’ personal health information expansively, including for other advertising or for their own internal business purposes

    2. primarily IP addresses and web page URL information related to looking at content

      The FTC compliant contradicts this saying:

      This included the name of the medication for which users accessed a GoodRx Coupon (“Drug Name,” such as “Lipitor”); the website URL, which in many cases included a medication name; the health condition related to the medication (“Drug Category,” such as “high cholesterol”); the medication quantity (“Drug Quantity,” such as “30-day supply”); the pharmacy name (“PharmName”); and the user’s city, state and zip code. The pixel also collected website microdata with additional information about the prescription medication and health condition(s) for which users accessed GoodRx Coupons. Finally, the pixel collected users’ IP addresses. In May 2019, GoodRx configured the pixel to automatically share with Facebook additional personal information, including user first and last name; email address; phone number; city, state, and zip code; and gender

    3. We are thoughtful and disciplined about what information we gather and how and why we use it.

      Just to be clear.

      GoodRx took information from its customers. Promised that it would not share information with third parties, and then shared it with Facebook anyway.

      The FTC Compliant summarizes the matter like this:

      GoodRx’s privacy policy representations described above were false and deceptive. In fact, since 2017, GoodRx has shared its users’ personal and health information with Advertising Platforms and other third parties in violation of its promises, including for targeted advertising, without providing notice or obtaining affirmative express consent

      Everything you read after this should be with this in mind.

    4. While we may elect to update such forward-looking statements at some point in the future, we disclaim any obligation to do so, even if subsequent events cause our views to change.

      While I understand that this is boilerplate language for a public company, it reduces trust to say "If we change our mind and our policies, we reserve the right to keep this page up as it is".

      This is a strong indication that this document exists as a message to investors and regulators primarily and not as letter to the patient community that make up GoodRX customers.

    5. No medical records were shared.

      This is disingenuous and demonstrably false.

      First, using the pixel was just one of the problems that the FTC covers. GoodRX injected specific medication data labels into the Facebook Graph, which means that portions of medical records were injected into Facebook by GoodRX.

      This sentence might say "We did not explicitly share medical records with Facebook using the pixel". And be true.

      Because even the fact "John Smith uses GoodRX to purchase medical information" meets the criteria for Personal Health Information under US law. This kind of information would count as Social Determinate of Health data which is now commonly part of Electronic Health Records.

      This means that Facebook could have inferred portions of a medical record using the pixel on the GoodRx website.

    6. The Facebook pixel continues to be used by many websites on the Internet, including U.S. Government websites, insurance companies, hospitals and others.

      This is actually a good point.

      In fact, I would suggest that GoodRX point out that only within the last month or two did Health and Human Services (HHS) Office of Civil Rights (OCR) clearly release guidance that the Facebook pixel was not HIPPA compliant.

    7. At that time, we also added a number of new, industry-leading ways for consumers to protect their privacy, including an option to request the deletion of personal data.

      This feature is required for GDPR compliance. GDPR does in fact cover US companies when they grow so large that they have EU citizens as customers.

      GDPR came into effect in 2018, but it was complete in 2016.

      This means that the single example from GoodRX of a "new industry leading way of protecting privacy" is in fact mere-compliance with industry regulation and best practice.

      This is another example of GoodRX holding themselves out to be leaders, when in fact they are clearly playing a game of catch-up regarding their privacy practices.

    8. took action to be an industry leader on privacy practices

      This is a very generous way to refer to action that can only be classified as "we stopped screwing up" or "we were no longer abusing the privacy of our customers".

      This is like saying "Last year we could not field an NBA team, and this year we can! Which is essentially the same as winning and NBA championship". Merely being in the NBA != being a championship team.

    9. to advertise in a way that we believe was compliant

      There are only two possibilities:

      A. GoodRX understood exactly how the "Facebook data vacuum cleaner" worked, and decided: 'other people are doing this too.. so it is OK for us to do it'

      or

      B. GoodRX (like the rest of the world) did not really understand how Facebook operated until a watchdog told them that they were publishing medication data by advertising in the way they were.

      If GoodRX understood what it was doing with Facebook (A) then it would have known that what it was doing was clearly a violation of their own privacy policies and therefore an FTC breach notification.

      If GoodRX did not understand what it was doing with Facebook, then referring to this as "believing to be compliant" is disingenuous. "Believing that you are compliant" presumes that you have a reasonable understand of what you are doing.

    10. proactively made updates

      If the CEO of GoodRX had discovered that they were putting patient data into Facebook for the world to see, and then decided "hey we should not be doing this" and then instituted a change to stop that from happening. That would be "proactive".

      But as the FTC compliant clearly documents, the actions that they took three years ago were in reaction to a privacy watchdog (and possibly more than one) discovering that they were sharing data when they should not.

      It is not reasonable to use the phrase "proactively" when the correct word by all accounts is "reactively". This is an inappropriate spin on their previous failure, and factually inaccurate

    1. Rather, GoodRx agreed to each of these thirdparties’ standard terms of service, or entered into agreements that permitted each AdvertisingPlatform to use GoodRx users’ personal health information expansively, including for otheradvertising or for their own internal business purposes

      This contradicts what GoodRX has said in its statements.

    2. In August 2019, HeyDoctor began prompting users to view a GoodRx Coupon formedications prescribed during their telehealth consultation. When a user did so, GoodRxconfigured the pixel to share information about the prescribed medication with Facebook,through a Custom Event called “drug.” It shared the medication name (such as “nitrofurantoin”);dosage (such as “100 mg”); form (such as “capsule”); whether the user was interested in viewingthe GoodRx Coupon (such as “interested: Yes”); and the name and location of the users’pharmacy (such as “Pharmacy: Capsule Pharmacy, New York, NY”). The pixel also sharedusers’ IP address, and website microdata with additional information about the prescriptionmedication and health condition(s) for which users accessed GoodRx Coupons.

      uhmm isnt this a HIPAA violation?

    3. This included the name of the medication for which users accessed aGoodRx Coupon (“Drug Name,” such as “Lipitor”); the website URL, which in many casesincluded a medication name; the health condition related to the medication (“Drug Category,”such as “high cholesterol”); the medication quantity (“Drug Quantity,” such as “30-day supply”);the pharmacy name (“PharmName”); and the user’s city, state and zip code. The pixel alsocollected website microdata with additional information about the prescription medication andhealth condition(s) for which users accessed GoodRx Coupons. Finally, the pixel collectedusers’ IP addresses.

      This is the details of what was collected by the pixel integration according the FTC

    4. GoodRx’s privacy policy representations described above were false anddeceptive. In fact, since 2017, GoodRx has shared its users’ personal and health informationwith Advertising Platforms and other third parties in violation of its promises, including fortargeted advertising, without providing notice or obtaining affirmative express consent.

      This is the center of the FTC compliant against GoodRX.

    1. The Federal Trade Commission has taken enforcement action for the first time under its Health Breach Notification Rule against the telehealth and prescription drug discount provider GoodRx

      This is the basic enforcement. I do not believe this went to court. And this is the first time this has ever been enforced.

  2. Oct 2016
    1. Law Enforcement Purposes. Covered entities may disclose protected health information to law enforcement officials for law enforcement purposes under the following six circumstances, and subject to specified conditions: (1) as required by law (including court orders, court-ordered warrants, subpoenas) and administrative requests; (2) to identify or locate a suspect, fugitive, material witness, or missing person; (3) in response to a law enforcement official’s request for information about a victim or suspected victim of a crime; (4) to alert law enforcement of a person’s death, if the covered entity suspects that criminal activity caused the death; (5) when a covered entity believes that protected health information is evidence of a crime that occurred on its premises; and (6) by a covered health care provider in a medical emergency not occurring on its premises, when necessary to inform law enforcement about the commission and nature of a crime, the location of the crime or crime victims, and the perpetrator of the crime.34

      HIPAA pretty much rolls over for law enforcement. Hard to imagine a circumstance where the law would protect a healthcare provider who refused to cooperate with a warrant or other request that they felt was an unreasonable invasion of their patients privacy, or the doctor-patient relationship.

  3. Jun 2016
    1. The previous methodology assigns beneficiaries in two steps based on the plurality of primary care services furnished 1) by primary care physicians, and 2) by specialist physicians, nurse practitioners, physician assistants, and clinical nurse specialists.     In the final rule, we are revising the assignment methodology to remove certain specialty types whose services are not likely to be indicative of primary care services from Step 2, which places greater emphasis on primary care physicians.  Additionally, we will include primary care services furnished by nurse practitioners, physician assistants, and clinical nurse specialists in Step 1 to recognize the primary care delivered by these professionals. Finally, through rulemaking in the 2017 Physician Fee Schedule, we expect to propose that beneficiaries may attest that their main doctor is participating in a performance-based risk track ACO and be assigned to that ACO.

      This is as good a summary of the assignment changes as I have seen anywhere

    1. A) Yes. If charitable organizations participate in the Shared Savings Program through an ACO along with private parties, the charitable organization must be sure that it continues to meet the requirements for tax exemption to avoid adverse tax consequences. For example, its participation must: not result in its net earnings inuring to the benefit of private shareholders or individuals, and not result in its being operated for the benefit of private parties participating in the ACO. The IRS determines whether prohibited inurement or impermissible private benefit has occurred based on all the facts and circumstances.

      It says "yes" but many have argued that these two constraints essentially mean "no"

  4. Mar 2016
    1. In 2000, Seisint Inc. (now LexisNexis Group) developed a C++-based distributed file-sharing framework for data storage and query. The system stores and distributes structured, semi-structured, and unstructured data across multiple servers.

      Not sure if this counts as a predecessor to Big data...