Oogle

medical and dental practices, clinics and provider groups

A website people use when they're worried, in a hurry, or both.

Healthcare sites get read by people who are anxious, unwell, on an old phone, or helping an elderly relative. Clarity and reliability matter more here than almost anywhere else.

WHAT WE DON'T CLAIM

We're not a healthcare compliance firm and hold no certification here. We won't tell you a website is HIPAA compliant, and we'll say when a question belongs with your compliance advisor.

What a practice website is for.

Most of the traffic is people looking for one fact.

Answer the practical questions first

Where, when, who, what insurance, how to book, what to bring.

Present providers and services clearly

Who works here, what they treat, and at which location.

Work for people who are struggling

Older visitors, small screens, poor eyesight, high stress.

Stay up

Downtime means phone calls that could have been answered online.

Handle form submissions carefully

Whatever a form collects has to be justified and sent securely.

Small failures with big consequences.

Contact details and hours buried

The most-wanted information three clicks deep, while the homepage leads with a mission statement.

Provider pages maintained by hand

Which is why they're out of date.

Accessibility problems that matter here

Low contrast text, unlabeled form fields, information only available as a PDF, and content you can't reach with a keyboard.

What practices and clinics ask.

Is our website HIPAA compliant?

That's not a property a website has. Compliance describes how an organization handles protected health information across all of its systems and processes, and the website is one small part of that. We can build carefully, minimize what is collected, and tell you exactly where submissions go. Whether that meets your obligations is a question for your compliance advisor, and we won't pretend otherwise.

Can patients book appointments on the site?

Usually through your existing practice management or scheduling system rather than something we build. The work is making that handoff clear rather than reinventing scheduling, which is both expensive and unnecessary.

How accessible does the site need to be?

We work to WCAG 2.2 AA as a standard. Whether a specific legal obligation applies to your organization depends on your circumstances and is worth confirming with counsel, but AA is a sensible working target regardless and it makes the site better for everyone.

Practice website not doing its job?

The three questions your front desk answers most often are usually where the whole project starts.