Book Appointment

A Hospital Web Team Spends a Quarter Repairing Old Patient Pages

Healthcare IT

The following story is invented for illustration. The hospital, the team and the events are made up, though anyone who has worked on a hospital website will recognise the shape of it. It concerns an oncology centre’s patient information pages and the quarter in which the team decided to look after what they had before publishing anything else. Nothing here concerns medical care; it is about pages, forms and links.

The request that started it

The centre’s digital coordinator, a careful and slightly overworked administrator, received a message from the head of patient services. A family had arrived for a first visit carrying a printed form from the website. The form asked for a document the registration desk no longer collected, and it listed a department extension that had been reassigned the previous spring. The family had been polite about it, but the head of patient services was not, quite reasonably, relaxed.

The coordinator’s first instinct was to apologise and fix that one form. Her second, after a night of thinking about it, was to ask a more uncomfortable question: if one form had drifted, how many others had?

The inventory

The team spent a week listing every page, form, downloadable document and outbound reference on the patient section of the website. The list was longer than anyone expected, partly because several pages had been created for events or programmes that had since ended, and partly because three different people had once written separate pages about how to prepare for a first visit.

For each entry the coordinator recorded four things: who owned it, when it was last reviewed, what it depended on, and what happened if it failed. The “what happens if it fails” column turned out to be the most useful. A broken link to a cafeteria menu was an irritation. A wrong department number on a page patients read before an important appointment was a real cost to somebody’s morning.

Three piles

The team sorted the inventory into three piles, using a simple rule that the coordinator pinned above her desk.

  • Still right. Review date updated, nothing else changed.
  • Needs work. A defect was found, assigned to a named person and given a date.
  • No longer needed. Retired, with a redirect to the page that replaced it where one existed.

The pile sizes surprised everyone. The retire pile was the second largest. Several pages described a patient transport arrangement that no longer ran. Two others were near-copies of a main information page. One was a temporary notice from a building works period that had ended long before.

The coordinator also reread the centre’s own material on the value of dependable cancer care information for patients and pointed out in the team meeting that every wrong detail on a site works against exactly that promise. No one argued.

What the review actually found

The faults fell into recognisable groups, and none of them were dramatic.

  1. Several downloadable forms existed in two versions, with the older one still linked from a secondary page.
  2. A contact page named a role holder who had left; the role itself had moved to a shared inbox the page never mentioned.
  3. Outbound links to a patient support organisation, an insurer’s information page and a laboratory’s booking page had all quietly changed.
  4. An enquiry form was delivering messages to an address that a former colleague had used. Nobody had read those messages for months.

That last finding changed the mood in the room. The enquiry form had displayed a thank-you message every time someone used it. People had been writing to the centre and hearing nothing back, and the site had been politely telling them all was well.

Dealing with the links

The outbound references were the hardest part, since the team did not control any of the destinations. A volunteer who knew the site well spent two afternoons clicking through them, and by the end said, with some feeling, that nobody should have to do this by hand. The coordinator agreed and looked for something that could do the watching. The team moved their published addresses into URLSnow, a platform for managing links that checks each one automatically overnight and records whether it still responds. From then on a link that stopped working appeared as a flagged item for the team to look at in the morning, rather than waiting for a visitor to run into it.

The coordinator was careful about what the tool was for. It could tell her a destination had gone silent. It could not tell her whether the information behind a link that still worked was appropriate for patients, so the human review stayed in the process.

The routine that replaced the project

A one-off clean-up is satisfying and temporary. The team wanted something that would survive a busy winter, so they agreed a modest routine.

  • Every page has an owning department, listed on the inventory, not an individual’s name.
  • One section of the site is reviewed each fortnight. The reviewer tests every form and contact route as an outsider would.
  • Clinical or procedural wording is never edited by the web team. If something looks out of date, it is flagged to the relevant department, which decides.
  • New pages are not approved until someone has checked that no existing page already covers the subject.
  • Nothing goes live without a named department, a date for its first re-read and a note of what it leans on.

That fourth rule had the biggest effect. Over the following months several proposals for new pages ended up as improvements to existing ones, which saved effort and kept the site smaller. The centre’s guidance on building and then properly looking after a website had always said as much in general terms; now the team had the habit to match.

The quiet quarter

When the quarter ended the coordinator presented a short summary to the leadership group. It contained no dazzling numbers, and she resisted the temptation to invent any. It said that every contact route on the patient section had been tested, every form had an owner and a known destination, every outbound reference had been opened and judged, and a set of obsolete pages had been removed with proper redirects. The enquiry inbox now had two readers and a handover note.

The head of patient services asked what the team would be launching next. The coordinator replied that the next launch had been postponed by a fortnight, because the new page for a visiting-days notice overlapped with one already published, and the team was merging them first.

What the story illustrates

Three lessons carry over to any similar organisation. First, decay is quiet: broken things on a website rarely announce themselves, so the review has to be scheduled and not waiting for a complaint. Second, the largest risks are often hidden behind reassuring signals, such as a confirmation message on a form that goes nowhere. Third, upkeep does not require a large team or a large budget. It requires an inventory, owners, a modest routine and the willingness to remove what is no longer needed.

The coordinator kept her three-pile rule on the wall. Whenever someone arrived with an idea for something new, she would ask a polite question first: which of the existing pages might already do this job, and are they in good enough repair to carry it?