Medical practices, US
Medical practice website design for US practices that keeps PHI out of the wrong places
Medical practice website design for a US practice is about getting patients booked without leaking their health information to ad platforms. That means deciding which pages touch PHI, keeping tracking off them, connecting booking and forms to systems that can hold PHI, and making every page accessible. We build these remotely from Noida; your privacy officer and counsel own the compliance decisions.
- Practice site
- $1,500–4,500 indicative
- Booking and forms
- Via your EHR or a vendor under BAA
- Tracking
- None on pages that handle PHI
- Accessibility
- Built to WCAG 2.2 AA
Updated · By the Codebrix team
What the site does, and which parts touch PHI
Most of a practice website is public information. A few parts collect or display health information, and those decide the architecture.
| Part of the site | Touches PHI? | How we build it |
|---|---|---|
| Services, providers, insurance accepted, locations, hours | No | Static pages, fast, light analytics |
| Appointment booking | Usually yes: a person plus a visit with your practice | Your EHR or practice management system's scheduler, or a booking vendor that signs a BAA with you |
| New-patient and intake forms | Yes | Your EHR's forms, or a forms vendor under a BAA, never a general form builder emailing you |
| Patient portal | Yes | A link to your EHR's portal; we do not rebuild it |
| Contact form | Can be, if people type symptoms | Short form with a warning not to include medical details |
Booking and patient forms: where HIPAA starts
The cheapest way to build a medical practice website badly is a free form plugin that emails intake answers to the front desk. The safer pattern is to keep PHI inside systems that your practice has a Business Associate Agreement with, and to have the website hand patients over to them cleanly.
- Booking buttons deep-link to the right provider, location and visit type in your scheduler, so patients do not start again.
- Embedded widgets load only on the booking page, with no marketing scripts alongside them.
- Confirmation and thank-you pages carry no visit type or condition in the URL or page title.
- If a custom booking or forms app is the right call, it is a web application project with HIPAA's technical safeguards in scope; see HIPAA app development.
Ad pixels and analytics: HHS guidance on tracking technologies
HHS's Office for Civil Rights issued its bulletin on the use of online tracking technologies by HIPAA covered entities and business associates on 1 December 2022. It says regulated entities are not permitted to use tracking technologies in a way that results in impermissible disclosures of PHI to third parties. It describes tracking on login-protected pages, such as patient portals, as generally having access to PHI, and says a tracking vendor with that access is a business associate needing a BAA.
On 20 June 2024, a federal court in the Northern District of Texas vacated the part of the guidance that said HIPAA obligations are triggered when an online technology connects an IP address with a visit to an unauthenticated public page about specific health conditions or providers. HHS's page states this and says it is evaluating its next steps. The rest of the bulletin was not vacated. HHS blocks automated fetching, so we confirmed this through its own pages via search; read the current HHS bulletin before deciding.
- An inventory of every script and pixel on the current site, by page, before we design anything.
- No advertising pixels, session recording or chat widgets on booking, forms, portal links or thank-you pages.
- Ad conversion tracking, if your counsel allows it, measured in a way that sends no health detail to the ad platform.
- Analytics configured to drop query strings and page titles that could reveal a condition.
- A tag change process: nobody adds a script to production without your sign-off.
Reviews without breaking FTC rules
The FTC's Consumer Reviews and Testimonials Rule took effect on 21 October 2024. It bans fake reviews, incentives conditioned on a positive or negative review, undisclosed insider reviews and suppressing reviews through baseless threats or intimidation. The FTC's Q&A adds that the rule has no specific ban on asking only happy customers for reviews, but staff warn that doing so could still violate the FTC Act.
- Review requests go to every patient after a visit, not only to those who scored you highly.
- Reviews on the site come from the platform where they were posted, unedited.
- Reply templates for the front desk that never confirm someone is a patient or mention their care. Your privacy officer approves the wording.
Accessibility: ADA, Section 1557 and Section 504
The Justice Department states that private medical offices are covered by Title III of the ADA as places of public accommodation (ADA.gov), and its web guidance applies the ADA to what those businesses offer online. HHS's Section 1557 rule requires covered health programs delivered through information and communication technology, including websites and apps, to be accessible to people with disabilities.
For recipients of HHS federal financial assistance, the Section 504 rule sets WCAG 2.1 AA as the standard for web content and mobile apps. On 7 May 2026, HHS announced a one-year extension: recipients with 15 or more employees now have until 11 May 2027, and those with fewer than 15 until 10 May 2028. Whether your practice is a recipient is a question for your counsel. We build to WCAG 2.2 AA; the W3C states that content conforming to 2.2 also conforms to 2.1. More on our ADA website accessibility page.
What goes wrong on medical practice websites
| Problem | How we prevent it |
|---|---|
| Ad pixel left on the booking page by a marketing agency | Tag inventory, script allow-list, sign-off for every new tag |
| Intake answers emailed in plain text to a shared inbox | Forms kept inside your EHR or a vendor under BAA |
| Condition names in URLs sent to analytics | Neutral URLs on PHI pages, query strings stripped |
| Online scheduler that a screen-reader user cannot complete | Keyboard and screen-reader testing of the full booking path, vendor issues reported to the vendor |
| Reply to a review confirms the reviewer is a patient | Approved reply templates and a short staff guide |
Price, timeline and what we need
| Build | Indicative range | Timeline |
|---|---|---|
| Practice site, up to 6 pages, booking via your EHR | from $1,500 | 2–3 weeks |
| Multi-location or multi-provider site with CMS and blog | from $4,500 | 5–8 weeks |
| Custom booking, forms or patient app | $5,500–22,000 | 6–16 weeks |
From you: your EHR or scheduling vendor and their integration options, your privacy officer's decisions on analytics and ads, provider bios and photos, and insurance and location details. The time-zone set-up is on our US overview. If reminders or after-hours calls matter, see our AI receptionist page, which covers what such tools must not do with PHI.
Frequently asked questions
Can we keep Google or Meta ad pixels on our practice website?
HHS's guidance says HIPAA regulated entities may not use tracking technologies in a way that results in impermissible disclosures of PHI. A 2024 court order vacated one part of that guidance about unauthenticated public pages, and the rest stands. We keep pixels off booking, forms and portal pages, and your counsel decides what, if anything, runs on public pages.
Will you make our website HIPAA compliant?
No developer can make you compliant; HIPAA compliance is your practice's programme, run with your counsel and privacy officer. We build so that PHI stays inside systems covered by your Business Associate Agreements, keep tracking off PHI pages, and implement HIPAA's technical safeguards as specified where a custom app is in scope.
Will Codebrix sign a Business Associate Agreement?
If our team would create, receive, maintain or transmit PHI for you, HIPAA requires a BAA, and we settle that during discovery. For most practice websites it does not arise, because booking and forms stay in your EHR or a vendor under your BAA, and our engineers work with synthetic test data rather than real patient records.
Should we build our own online booking?
Usually not at first. Your EHR or practice management system's scheduler already knows provider availability and visit types and already holds PHI under your agreements. We deep-link and embed it well. A custom booking app makes sense when the vendor's tool blocks patients, for example on accessibility, and we scope that as a web application.
What accessibility standard should a medical practice site meet?
The Section 504 rule sets WCAG 2.1 AA for recipients of HHS federal financial assistance, with deadlines extended in May 2026 to 11 May 2027 for those with 15 or more employees. Title III of the ADA covers private medical offices. We build to WCAG 2.2 AA, which also conforms to 2.1, and your counsel judges compliance.
How much does medical practice website design cost?
Indicatively, a practice site of up to six pages with booking through your EHR starts at $1,500 and takes two to three weeks. A multi-location site with CMS and blog starts at $4,500. A custom booking, forms or patient app falls in our web application range of $5,500 to $22,000. You get a fixed quote after discovery.
Sources
- HHS OCR: Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates
- HHS: Bulletin on online tracking technologies (1 December 2022)
- HHS: Section 1557 summary of nondiscrimination protections
- HHS: OCR extends web and mobile accessibility compliance deadline (7 May 2026)
- ADA.gov: Access to Medical Care for Individuals with Mobility Disabilities
- ADA.gov: Guidance on Web Accessibility and the ADA
- FTC: Consumer Reviews and Testimonials Rule, Questions and Answers
- W3C: Web Content Accessibility Guidelines 2.2
Related
United States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read moreHealthcare apps
HIPAA compliant app development: what we build, and what stays your job
HIPAA compliant app development explained: the Security Rule safeguards we build in, BAAs with AWS, Google Cloud or Azure, and PHI kept to the minimum.
Read moreAccessibility
ADA website accessibility services: WCAG 2.2 AA audits, fixes and builds
ADA website accessibility services from an India-based team: WCAG 2.2 AA audits, fixes in your own code, and builds tested with real screen readers.
Read moreHealthcare
A healthcare app development company in India that builds for clinics
Healthcare app development company in India for clinics: booking, reminders, patient portals and websites, built with the DPDP Act and ABDM in mind.
Read moreLocal SEO
Local SEO for US small businesses: profile, reviews, pages and schema
Local SEO services for US small businesses: a Google Business Profile built to Google's rules, honest review requests, real location pages and schema.
Read moreAI receptionist, US
An AI receptionist for small businesses that answers after hours and books into your calendar
AI receptionist for small business: answers after-hours calls, books into your calendar and hands urgent callers to staff, with consent set by counsel.
Read more