Healthcare · Website Development
A nurse practitioner-led practice offering both virtual and in-person care has to answer a question no ordinary clinic site does: which of these applies to me, and where do I have to live for it to apply? Eligibility varies by service and by region, memberships run alongside direct-pay, and a patient who cannot resolve that in a few seconds does not book.
We built the site around eligibility rather than around the practice structure: each service states plainly whether it is virtual, in person, or both, and where it is available, so the answer arrives before the booking button does.
Why a telehealth site is harder than a clinic site
A single-location clinic has one implicit answer to "can you see me": yes, if you can get here. A telehealth practice does not. WheelHouse Health delivers virtual primary care across Virginia, in-person care in selected Northern Virginia locations, and in-home visits to a narrower area still - and the boundary is different for each of the five services.
That turns the site's main job from persuasion into qualification. A patient in Richmond and a patient in Lake Ridge are looking at the same page and need different answers, and neither will hunt for it. The same is true of money: concierge memberships sit alongside direct-pay visits, and a page that hides the price forces an enquiry before the patient knows whether the practice is even in their range.
How we approached the build
We started from the questions a patient actually arrives with - what can you treat, can you treat me where I live, is this virtual or in person, what does it cost - and made each one answerable without a form.
Services were nested under a single hub rather than scattered through the menu, so the five care types read as one offering with five routes into it. Each service page states its own delivery mode and geography in its own words. The membership page publishes all five tiers with their prices and their add-ons, and carries the line that keeps the whole page honest: a membership is not health insurance.
Because this is a healthcare practice, the compliance pages are part of the build rather than an afterthought - a HIPAA Notice of Privacy Practices sits alongside the privacy policy and terms, and the booking route hands off to the practice's own patient portal rather than collecting clinical detail on a marketing site.
What was built
- A WordPress build with five service pages under one services hub, each stating its own delivery mode and service area
- A membership page publishing all five tiers, their inclusions, prices and spouse or employee add-ons
- One booking route repeated site-wide, handing off to the practice's own patient portal
- A clinician profile so patients know who they are booking with before they book
- HIPAA Notice of Privacy Practices alongside the privacy policy and terms of use
- An FAQ and a concierge care blog for the questions that arrive before the first visit
- A structured URL hierarchy so each service earns its own search entry rather than competing with the hub
What changed
The site now answers the qualifying questions on the page. A visitor can see which of the five services is virtual, which is in person, which is available at home, and what a membership costs, without sending an enquiry to find out.
That also changes what an enquiry is worth. The people who reach the booking step have already self-selected on geography, care model and price, so the practice spends less of its clinical time on conversations that were never going to lead anywhere.
What another practice should take from this
Publish the constraint. The instinct with a service that has eligibility rules is to keep them vague so nobody rules themselves out - but a patient who cannot tell whether they qualify does not book optimistically, they leave. Stating the geography and the delivery mode plainly on every service page loses the enquiries that were never eligible and keeps the ones that were.
The same applies to price. A membership page with the numbers on it does more filtering in ten seconds than a contact form does in a week.
Telehealth website questions
1Does a telehealth site need different pages from a clinic site?
Yes. A clinic site answers where and when; a telehealth site has to answer whether the patient is eligible at all, and the answer differs per service. That belongs on each service page rather than buried in an FAQ.
2Should membership prices be published?
On this build, yes. Prices filter the audience before the practice spends clinical time on a conversation, and a page that withholds them reads as more expensive than it is.
3Who handles the clinical data?
Not the marketing site. Booking hands off to the practice's own patient portal, so clinical detail is never collected on the website.
4Does the site handle HIPAA compliance?
The site publishes the practice's HIPAA Notice of Privacy Practices and keeps clinical intake off the marketing pages. Compliance itself is a practice obligation, not something a website can grant.