Creating your own DPC website? Make sure you have these things in place

A lot of DPC doctors starting out don’t have much money but they have time, so they decide to create their own website. It’s easy to pick a template on a website platform, make a home page about DPC, write an About page, add a few photos, and publish. Especially with AI assistance, the result usually looks really good. But, it often skips the parts you’ve never had to think about before: the legal pages and the fine print that sit behind them. We didn’t realize we needed those pages until we were open for a few years.

I talked about this recently with Kim Cunningham, an attorney who works with healthcare practices and DPCs in particular. Both of us have looked at a lot of DPC websites, and we frequently see the same gaps. Some websites have no privacy policy. Some have no terms and conditions. Some have a contact form that collects information with no explanation of where it goes or no consent for contact afterwards.

Here is what I’d put on your site before it goes live. Disclaimer wording rules vary by state, so have an attorney in your state look over the final version before you publish.

Start with what can get you in trouble

A clear statement that DPC is not insurance. Many states require your membership agreement to say this, sometimes in specific wording, so check the rules for your state. Clearly state on your website as well that DPC is not insurance, so nobody thinks they’re buying coverage.

An emergency notice. You don’t monitor your site around the clock, and a patient having worrisome medical symptoms could put that in a contact form at 2 a.m. To avoid that, put a short notice near the contact form submission that says to call 911 for emergencies. Place the notice next to where people reach you, not hidden at the bottom of the page in the footer.

A privacy policy. It should describe what information your site collects, what you do with it, and who else receives it. Don’t copy one word-for-word from another practice. Theirs describes their website, and your privacy policy has to describe yours. This is not the HIPAA notice of privacy practices. It only covers your website, and people frequently confuse the two.

Terms and conditions. These explain that the site is information only. Visiting the site or using it does not make someone your patient.

Disclaimers. These can be placed in the terms & conditions page. They state that using the site or filling out a form does not create a physician-patient relationship, and that a person is not your patient until they sign your agreement. If the site has much medical information on it, add that it isn’t medical advice.

An accessibility statement. Federal law expects websites to be usable by people with disabilities, with readable text size and descriptions on photos for people who can’t see them. Kim said you don’t have to meet every item to have a statement. The statement says you know about the requirement, what you’ve done so far, what you may do later, and how someone can contact you if they can’t use the site. A third-party accessibility widget by itself on your website doesn’t make it compliant. There should be some process behind it.

A cookie banner. Most websites collect IP addresses and place cookies on visitors’ devices, and the banner is how you notify visitors. A DPC was recently sued over a missing cookie banner.

Unfortunately, there are people who go from website to website looking for missing notices, then send a demand letter, sometimes asking for several hundred dollars to not report you. It’s much easier to have the notices on your site than dealing with that.

Templates are okay. Kim said it’s fine to start from a policy template, whether from another practice, an association, or a purchased one, because these notices are pretty standard. Read it and adjust it to match what your site really does. If you hire a web designer, ask whether they include these.

Text and email consent. If you plan to text or email patients, ask for permission on your sign-up or intake form. Give texting and email each their own checkbox, and have the patient provide the phone number and email address you should use to contact them. One general consent buried in the agreement isn’t enough.

Know what is running on your site

A plugin (sometimes called an app or extension) is an add-on that gives your site a feature it doesn’t have on its own, like a contact form, a booking calendar, or a chat widget. Some of them collect information from your visitors. Make a list of every plugin and tool on your site, including any you use for ads. Ask whoever built the site, or your template provider, what information is collected and where the information goes. If you’re not sure what’s okay, an attorney can tell you which ones to remove and which to mention in your privacy policy.

If someone else built your site, ask them whether it includes a privacy policy, terms and conditions, disclaimers, an accessibility statement, and a cookie banner. Many designers have templates for these and may include them or add them for a small fee. Then scroll to the bottom of your site and check that those pages are there and accurately describe your site.

Your website checklist before you launch

  • Your website privacy policy, terms and conditions, and disclaimers are on the site and match what your site does
  • You have an accessibility statement and a cookie banner
  • Your not-insurance and emergency language is on the site
  • Your contact and intake forms have separate checkboxes for text and email
  • You have a list of the tools and plugins running on your site

If you can’t check one off, or you’re not sure about one, that’s when to ask an attorney.

Next time, I’ll cover the other part of your website: the things that help people find you.