TCS Healthcare United Kingdom

The Walton Centre NHS Foundation Trust

Customer Service Automation

The Walton Centre faced long waits and inefficient headache referral intake because clinicians spent large portions of first appointments collecting basic history manually, delaying treatment and making it hard to triage urgent cases quickly enough.

Assuming more than 99% of headaches are primary headaches
Capturing 95% of the required information through the AI chatbot service
Specialist clinicians typically spend 40% or more of their time gathering and validating basic information
The overall appointment time for the first appointment can be reduced by 40%.

Reported impact

Business outcome

The Walton Centre improved the patient intake experience, gave clinicians earlier visibility into headache cases, reduced appointment time spent on history taking, captured almost all required referral information digitally, and created a more secure and consistent pathway into specialist neurology care.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

The Walton Centre and TCS implemented a website-based conversational AI service to move headache triage and history collection upstream of the first specialist appointment. Patients use the AI chatbot to answer clinician-authored structured questions and provide additional details in natural conversation, while the service captures the response flow as a structured patient summary. TCS built the solution with AWS support and connected the output directly to the trust's electronic medical record system so consultants can review symptoms, history, and red flags before the first face-to-face visit. That architecture lets the trust standardize data capture, keep records secure, and reduce paper-based handling while giving clinicians a governed digital intake process that can identify severe cases earlier and shorten time spent on administrative questioning during appointments.

Data flow

Patients interact with the AI chatbot on The Walton Centre website, answering clinician-prepared questions and adding extra details through natural conversation. The service turns that intake into a structured patient summary report, then sends the report securely into the electronic medical record system so consultants can review the case before the first in-person appointment.

Solution architecture

4 components · 3 layers
  1. Compute
    • AWS Provides the cloud foundation for the chatbot service that the trust runs on its website.
  2. Storage
    • electronic medical record system Stores the secured patient summary so clinicians can access it inside the trust's existing workflow.
  3. Serving
    • AI chatbot Conducts the conversational intake flow for headache patients and captures structured and natural-language answers.
    • patient summary report Packages the captured symptoms, medication details, and history for consultant review before the first appointment.

Architecture clues

  • Natural-language follow-up is used to capture additional patient details beyond the fixed workflow.
  • The conversation flow follows structured questions prepared and reviewed by Walton Centre clinicians.
  • The digital intake path reduces paper handling while supporting GDPR-compliant data capture.
  • The service writes a secured summary directly into the electronic medical record system.

Evidence from the source

"Capturing 95% of the required information through the AI chatbot service enhances clinicians' overall efficiency"
"Once the patient completes the entire flow, the output captured by this service (a patient summary) is sent to the electronic medical record system"
"Our AI-supported chatbot captures over 95% of the key information needed to provide specialist advice to these patients"
"The collaboration resulted in a chatbot service, employing conversational AI to address headache-related concerns."
"The overall appointment time for the first appointment (typically focused on history taking) can be reduced by 40%."
Transparency Evidence & methodology 95/100 reference value · 95% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    6 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. TCS

    Conversational chatbot helps alleviate strain for Walton Centre

    First-party
    https://www.tcs.com/what-we-do/industries/public-services/case-study/walton-centre-migraine-conversational-chatbot
    Source type
    Vendor-published customer story
    Published
    Jul 17, 2024
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence