SiteGPTStart free trial

Healthcare Website Redesign: A Guide for Hospitals and Clinics

How to plan a hospital or clinic website redesign: patient top tasks, accessibility deadlines, price transparency, tracking tools, safe forms, and where a chatbot fits on public content.

Sai Dheeraj

SiteGPT Team

Healthcare Website Redesign For Hospitals and Clinics

SiteGPTBest AI chatbot for customer service

A person visiting a hospital website is often worried, in a hurry, or looking on behalf of someone else. They need a doctor, a location, a phone number, a price, or the next step. A good healthcare website redesign lets that person finish quickly.

Healthcare adds rules that other redesigns can ignore. The advice below covers public website content. Portals and clinical systems are separate projects.

A few terms first, because the compliance sections depend on them. HIPAA is the Health Insurance Portability and Accountability Act, the US law covering how patient information is handled. PHI, or protected health information, is any health detail that can be traced back to a person, such as a symptom, an appointment, or a name attached to a condition.

A business associate, or BA, is an outside vendor that handles PHI on your behalf. A BAA, or Business Associate Agreement, is the contract that lets it do so. HHS, the US Department of Health and Human Services, writes and enforces the HIPAA rules. WCAG, the Web Content Accessibility Guidelines, is the accessibility standard behind the rule covered below.

iShort answer

Build the new site around patient tasks: find care, find a location, check insurance, book, pay, and understand prices. Set WCAG 2.1 Level AA as the target. The HHS Section 504 rule takes effect on May 11, 2027 for recipients with 15 or more employees. Keep price transparency files easy to reach.

Audit every tracking tag, and map every form or chat box that could collect PHI. A chatbot can answer from public content. Visitors can still type health details, so a patient-facing chat box normally needs a BAA. On SiteGPT, the BAA is Enterprise-only, and training content must stay free of PHI.

The healthcare redesign framework

Five jobs, with the compliance work built in from the start.

1

Rank patient tasks

Use call records, search logs, and testing to find what people must be able to do.

2

Separate public and private

Keep public pages apart from the portal, and draw a clear line between them.

3

Meet public obligations

Plan for WCAG 2.1, price transparency, and clear service information.

4

Map every data entry point

Review forms, tags, and chat boxes for PHI with your privacy officer.

5

Add AI with a contract

Train on PHI-free content. A patient-facing chat box normally needs a BAA, Enterprise-only on SiteGPT.

Key takeaways

QuestionThe short answer
What comes first?Patient top tasks, ranked with call center and search data.
Which accessibility standard?WCAG 2.1 Level AA for HHS funding recipients under Section 504.
When is it due?May 11, 2027 with 15 or more employees. May 10, 2028 with fewer.
What must hospitals publish on prices?A machine-readable file and a consumer-friendly shoppable services display, under CMS rules.
Can a public-content chatbot skip the BAA?Usually not, because visitors can type PHI. The BAA is Enterprise-only on SiteGPT.

What do patients need from a hospital website?

Patients need to find the right care and the next step. Nielsen Norman Group recommends a short list of about 10 top tasks. A hospital's call center is a strong source for that list.

Patient jobWhat the page must answerGood evidence
Find a doctorWho treats this, are they accepting patients, where are they?Provider search logs
Find a locationAddress, hours, parking, directions, and phone numberTop landing pages
Decide where to goEmergency, urgent care, or primary care?Nurse line and call center topics
Check insuranceWhich plans are accepted?Billing and scheduling calls
Book or request careHow do I get an appointment?Form and phone analytics
Understand costWhat will this cost me?Billing calls and price page use
Pay a bill or use the portalWhere do I sign in?Portal referrals
Visit someoneVisiting hours and rulesLocation page traffic

Test each job on a phone. People often look for care away from a desk. Include older adults, caregivers, and people who use assistive technology.

Use plain words throughout. A patient searches for "knee replacement." A service line named "orthopedic arthroplasty" needs that plain label beside it.

How should public pages and the patient portal work together?

Keep public pages and the portal separate, with an obvious path between them. Public pages explain services. The portal handles a person's own records, messages, and results.

ContentWhere it belongsNote
Services, locations, and doctorsPublic siteGood for search and for a chatbot
Pricing informationPublic siteFollow CMS requirements
Test results and messagesPatient portalKeep outside the redesign's public content
Forms with health detailsReviewed secure workflowInvolve your privacy officer
News and health educationPublic siteName a clinical reviewer and a review date

Health content needs its own review process. Put a clinical owner and a review date on each condition and treatment page. Outdated medical content is a safety risk and a marketing problem.

Which accessibility rules apply to healthcare websites?

Recipients of HHS funding fall under the Section 504 web rule. Many hospitals and clinics are in that group. The rule adopts WCAG 2.1 Level AA for web content and mobile apps, including those provided through contracts or other arrangements.

OrganizationCompliance dateStandard
HHS recipient with 15 or more employeesMay 11, 2027WCAG 2.1 Level AA
HHS recipient with fewer than 15 employeesMay 10, 2028WCAG 2.1 Level AA
State or local public hospital, ADA Title IIApril 26, 2027 or April 26, 2028, by populationWCAG 2.1 Level AA

HHS moved those dates back by one year in May 2026, following the Justice Department's extension of its own rule (HHS, Federal Register). A redesign starting today will likely finish close to those dates. Build the standard into the templates now.

Check the areas that often fail: provider search, maps, forms, PDF patient documents, video, and third-party booking tools. WebAIM's 2026 scan found missing form labels on 51% of home pages. On a hospital site, a missing label can block someone from asking for care (WebAIM).

What must hospitals publish about prices?

Hospitals must publish pricing information online in two forms under the CMS Hospital Price Transparency rule. These are a comprehensive machine-readable file covering all items and services, and a consumer-friendly display of shoppable services (CMS).

CMS says new and updated requirements began being enforced on April 1, 2026, and noncompliant hospitals can face civil monetary penalties. Add the price pages to your redirect map, and review the current CMS fact sheet before launch. A price file moved without a redirect becomes a broken link and a compliance risk.

How should you review tracking tools and forms?

Audit each tool and form as a separate decision. A redesign is a good time for this review. Every tag and form gets rebuilt anyway.

Tracking tools. HHS published a bulletin on online tracking technologies. On June 20, 2024, a federal court vacated the part covering certain visits to public, unauthenticated pages, and HHS withdrew its appeal that August (AHA, Hunton). The rest of the bulletin still stands. Logged-in pages still need care. Ask counsel about current federal and state rules.

Item to reviewQuestion to answer
Analytics tagsWhat data leaves the site, and to whom?
Ad pixelsAre they on booking, portal, or condition pages?
Session replay toolsCould they record what a person types?
Contact formsDo free-text fields invite health details?
Appointment requestsWho receives the data, and is there a BAA?
Email notificationsDoes the message repeat what the visitor typed?

Remove any tag nobody can justify. Keep form fields to what staff need, and replace "tell us about your condition" with a phone number or a secure route.

How do you protect search traffic in a healthcare redesign?

Run the redesign as a site migration with more owners than usual. Service, doctor, and location pages can have years of search history. A patient may arrive from an old link.

  • Export every URL, including doctor and location pages, before any design work.
  • Redirect each old page to its closest new page.
  • Keep structured details consistent, including names, addresses, and phone numbers.
  • Tell scheduling and call center staff about the launch date.
  • Monitor 404 errors daily in the first week.

The complete sequence is in the website redesign checklist, including what to test on launch day. Google recommends keeping redirects for at least one year (Google).

Where does a chatbot fit on a healthcare website?

A chatbot fits after core public content is finished. It answers plain questions from your published content. Good topics are services, locations, hours, insurance pages, and how to book.

SiteGPT trains on your website links, files, and text snippets. It shows source links under answers. Visitors can ask for a person with a button or by typing in the chat.

SiteGPT's security page says it has been assessed by DPLMC International against HIPAA security and privacy requirements. The BAA is available on the Enterprise plan only.

Visitor messageSafe response
"Do you have a pediatric clinic near downtown?"Answer from the location pages and link to them
"What are your walk-in hours?"Give the published hours and link to the source
"How do I book a mammogram?"Explain the published steps
"I have chest pain. What should I do?"Give your approved emergency instruction, and do not assess symptoms
"Can you read my test result?"Direct the visitor to the portal or to staff

SiteGPT takes no actions on live systems during a chat, so it cannot book an appointment or look up a record. It answers in a chat window. It does not replace provider search or a search results page. Teams comparing search tools can read about enterprise site search.

Do not let a chatbot give medical advice. Tell it to avoid assessing a person's symptoms, test that behavior before launch, and review real conversations after launch. A grounded answer can still be wrong. The guide on how to stop a chatbot hallucinating gives a test plan.

The wider healthcare use case is covered in AI chatbot for healthcare.

What changes when a chatbot needs a BAA?

A covered workspace has fewer features, so plan for that. A chatbot may read only public pages. Visitors can still type a symptom or a name. SiteGPT's HIPAA page says PHI must not be submitted before a BAA is executed, and BAAs are available on the Enterprise plan only, never on Starter, Growth, or Scale.

Processing can begin only after the BAA is executed and SiteGPT confirms in writing. The workspace documentation and the published BAA set out the terms.

AreaIn a covered SiteGPT workspace
Training contentMust stay free of PHI, including pages, files, snippets, and custom responses
Adding contentWebsite links, file uploads, and text snippets. Cloud file connectors are not supported
Chat integrationsNot available, including Zendesk, Slack, and Crisp
Where PHI can appearUnder SiteGPT's terms, only in visitor conversations on the covered account
Conversation retentionRedacted 7 days after last activity, unless the order form sets another window
LeadsNever auto-deleted, so keep lead forms to basic contact details
Widget notice"Responses are AI-generated" stays on

Confining PHI to conversations is a SiteGPT contract and product rule. It comes from the agreement. HIPAA itself does not set this requirement.

Nothing scans your content for PHI. Your team must review files before upload.

The chain of vendors matters too. SiteGPT's documentation names Convex, OpenAI, and Pinecone as the subprocessors that receive PHI. OpenAI is limited to zero-data-retention endpoints.

How BAAs work at the model provider level is covered in the OpenAI and Anthropic BAA guide. Contract terms are covered in what makes a chatbot HIPAA compliant.

Frequently asked questions

Planning

What should a hospital website redesign prioritize? Prioritize the tasks people come to finish: find a doctor, find a location and hours, check accepted insurance, book or request care, pay a bill, reach the patient portal, and understand prices. Rank them with call center records, site search, and analytics, then test them with patients on a phone.

Is a public hospital website covered by HIPAA? General public pages usually contain no PHI. Forms, portals, and chat boxes can still collect details linked to a person. Map every point where a visitor can submit information. Ask your privacy officer and counsel to review each one.

When do healthcare websites have to meet WCAG 2.1? Recipients of HHS funding fall under the Section 504 rule, which uses WCAG 2.1 Level AA. In May 2026 HHS extended the dates to May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for smaller recipients. Confirm whether your organization is covered and whether the dates have changed.

Compliance

Can hospitals use tracking pixels on public web pages? Check with counsel before you use them. In June 2024 a federal court vacated the part of the HHS tracking bulletin covering certain visits to public, unauthenticated pages, and HHS dropped its appeal. The rest of the bulletin stayed in place, including its guidance on logged-in pages. State privacy laws may also apply. Review each tag during the redesign.

Do appointment request forms need extra care? Yes. A form that links a name to a symptom, condition, or appointment can collect PHI. Any vendor handling that data on your behalf may be a business associate. If so, you may need a BAA. Reduce free-text fields and ask your privacy team to review the form vendor and the notification path.

AI and chatbots

Can a hospital add a chatbot that only uses public website content? Yes, for the training content. SiteGPT supports PHI-free public content such as FAQs, scheduling guidance, and service information on any plan. PHI must not be submitted before a BAA is executed. Visitors can type anything into a chat, so a patient-facing chat box normally needs a BAA. SiteGPT offers the BAA on the Enterprise plan only.

What changes in a SiteGPT HIPAA workspace? Chat integrations such as Zendesk, Slack, and Crisp are unavailable. Cloud file connectors are not supported for HIPAA use. Content comes from website links, file uploads, and text snippets. It must stay free of PHI. Conversation content is redacted seven days after last activity unless the order form sets another window. Leads are never auto-deleted.

Can a website chatbot give medical advice? It should not. Keep it to public information such as services, locations, and how to book. Tell it not to give advice about a person's symptoms, send those questions to staff, and display clear emergency instructions on the site. Test these cases before launch and review them after launch.

Sources