Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Healthtech content: accurate, compliant and trusted

Updated · 6 min read

Short answer Write one version per reader, and check each against the rule that reader's content can break. Patient stories need written permission and typical results. Clinician pages need real evidence and your exact FDA or Health Canada status. Buyer pages need security and savings claims you can prove, because the FTC has made a software maker pay over one.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

One message per reader, one rule per message

A health software company usually sells to several people at once: the patient who uses the app, the clinician who has to trust it, and the clinic or hospital staff who sign the contract. Each wants different proof, and each kind of content breaks a different rule.

ReaderWhat they askFormat that worksThe rule that bites
Patient or caregiverWill this help me, and is it safe?Short plain-language pages, how-to videos, storiesHIPAA marketing authorization, FTC rules on testimonials
ClinicianDoes the evidence hold up? Is it cleared?Evidence summaries, study write-ups, demosFDA or Health Canada status, FTC rules on expert endorsers
Buyer (IT, finance, practice manager)Is it secure, and will it pay for itself?Security page, ROI case studies, implementation guideFTC Act (US) or Competition Act (Canada) on provable claims

Write the claim once, as precisely as your evidence allows. Then rewrite it for each reader without making it stronger.

Writing for patients: plain words, real stories with permission

The CDC defines the goal simply:

"Plain language is communication your audience understands the first time they read it or hear it." (CDC: Plain Language Materials and Resources)

That means short sentences, everyday words for body parts and conditions, and one task per page. A patient searching at midnight wants to know what the app does, what it doesn't do, and when to call a doctor instead.

Patient stories are the most persuasive content you can publish, and the most regulated.

  • If you are a provider, health plan or their vendor (a business associate), HIPAA counts any communication that "encourages recipients" to buy or use a product as marketing (45 CFR 164.501). Using patient information for it needs the patient's signed authorization: a covered entity "must obtain an authorization for any use or disclosure of protected health information for marketing" (45 CFR 164.508). A vendor may use clinic patient data only as its business associate contract allows (45 CFR 164.502). A clinic customer's patient is never yours to feature without that authorization.
  • If you are a consumer app outside HIPAA, get written permission anyway, and follow the FTC's Endorsement Guides. A story about results implies typical results. If your data doesn't show that, you must state what users generally achieve (16 CFR 255.2). The FTC adds that "Results not typical" disclaimers "don't cure the deception" (FTC: Health Products Compliance Guidance).

Replying to patient reviews has its own HIPAA trap; see responding to patient reviews.

Writing for clinicians: evidence and your exact status

Clinicians read the methods before the headline. Give them the study design, number of patients, the comparison and the limits. Keep your own customer data apart from peer-reviewed results, and label each.

State your regulatory status in the regulator's words. A US device that went through a 510(k) premarket notification is "FDA cleared," not "FDA approved." The rule is blunt:

"Any representation that creates an impression of official approval of a device because of complying with the premarket notification regulations is misleading and constitutes misbranding." (21 CFR 807.97)

In Canada, no one may advertise a Class II, III or IV medical device for sale unless the manufacturer holds a licence (or an authorization) for it, except in a catalogue that carries a clear warning (Medical Devices Regulations, section 27). Pre-launch "coming soon" pages for licensed-only devices need regulatory review.

Clinician names on your content come with two duties under the FTC's Endorsement Guides:

  • An expert endorser's qualifications "must in fact give the endorser the expertise" you present (16 CFR 255.3), and they must actually have evaluated the product.
  • A paid advisor, investor or clinician given free product has a connection the reader wouldn't expect, which "must be disclosed clearly and conspicuously" (16 CFR 255.5).

For how Google weighs authorship on health pages, see E-E-A-T for a small business.

Writing for buyers: security and savings claims you can prove

Content for practice managers, IT and finance feels safer because no patient reads it. It isn't. In 2016 the FTC charged the maker of Dentrix G5, dental practice software, with making "deceptive claims that the software provided industry-standard encryption of sensitive patient information." The company paid $250,000 (FTC press release, January 5, 2016). The claim sat in marketing aimed at dentists.

Claim buyers loveWhat to have on file first
"HIPAA compliant"Exactly what you do: sign a business associate agreement, encryption method, access logs, audit reports
"Bank-level encryption"The named standard and where it applies (stored data, data in transit)
"Saves 10 hours a week"Measured data from real customers, with how many and over what period
"Integrates with your EHR"The systems you actually connect to, and how

Name the clinic only with its written consent, and keep every patient detail out of case studies.

Canada sets the same bar in law. The Competition Act treats as reviewable a performance or efficacy claim "that is not based on an adequate and proper test thereof, the proof of which lies on the person making the representation" (Competition Act, section 74.01). The test comes before the claim.

If buyers will see tracking on your demo or sign-up pages, check it too: Meta pixel and Google Analytics on a clinic website.

A review process a small team can run

You don't need a compliance department. You need the same four checks on every piece, in order:

  1. Fact check: every number and claim linked to its source; drop what you can't source.
  2. Clinical review: a licensed clinician in the right field confirms the medical facts and signs with a date.
  3. Claim review: someone compares product claims to your clearance, licence and evidence file.
  4. Privacy review: written authorization on file for any patient or customer named; no patient details.

AI can draft. A human checks every fact before it ships; for Google's view, see does Google penalize AI content?

Example

A remote-monitoring startup's patient page

The page said "users cut ER visits in half," taken from three customer quotes. The team replaced it with their measured average across 400 users, a plain explanation of what the device tracks, and a "when to call 911" box.

A 510(k)-cleared imaging tool's clinician hub

The homepage said "FDA approved AI." The team changed it to "FDA cleared," linked the clearance number, and listed the paid status of each radiologist quoted in its evidence summaries.

A Canadian scheduling vendor's case study

The draft named the clinic and quoted a patient. The vendor got the clinic's written consent, removed the patient, and replaced "saves $50,000 a year" with the clinic's measured six-month change in no-shows.

FAQ

Can we say our software is "HIPAA compliant"?

Only if you can show what it means in practice. Spell out the business associate agreement, encryption and controls behind it, because the FTC has acted against false data-security claims made to dentists.

Do patient testimonials need a disclaimer?

A disclaimer alone doesn't fix them. If a story shows better results than users generally get, the FTC expects you to state the typical result.

Is "FDA cleared" the same as "FDA approved"?

No. A 510(k) clearance doesn't denote official approval, and federal rules call implying it misleading.

Do I need a doctor to review every post?

Only posts that state medical facts. Product, pricing and setup pages can be reviewed by your own team.

Different for you?

Keep learning

NextBiotech content: a 10-step strategy that simplifies scienceTen steps for biotech content: what you may say before and after approval, plain-language science, review, SEO and ads limits in the US and Canada.

Ask us one question

One line is enough. We reply by email.

Sources

  1. CDC: Plain Language Materials and Resources
  2. 45 CFR 164.501: Definitions (marketing)
  3. 45 CFR 164.508: Uses and disclosures for which an authorization is required
  4. 45 CFR 164.502: Uses and disclosures of protected health information (business associates)
  5. 16 CFR 255.2: Consumer endorsements
  6. 16 CFR 255.3: Expert endorsements
  7. 16 CFR 255.5: Disclosure of material connections
  8. FTC: Health Products Compliance Guidance
  9. 21 CFR 807.97: Misbranding by reference to premarket notification
  10. Medical Devices Regulations (Canada), SOR/98-282, section 27
  11. FTC: Dental practice software provider settles FTC charges it misled customers about encryption of patient data (January 5, 2016)
  12. Competition Act (Canada), section 74.01