Industry application

Generative AI for Patient Experience: Improve Access Without Crossing the Clinical Boundary

Healthcare organisations can use generative AI to find administrative barriers in patient feedback and coordinate approved service actions. However, they must preserve every clinical question for qualified staff. The useful design therefore connects the patient journey, multilingual feedback and non-clinical follow-up without allowing an administrative system to diagnose, prioritise treatment or reinterpret a patient's concern.

Reconstruct the administrative patient journey

A patient experiences an appointment as one continuous journey. The organisation may record that journey across referral, scheduling, reminders, preparation instructions, arrival, waiting, rescheduling, telephone contact and complaints. When these records remain separate, managers can see a missed appointment or repeated call but cannot see the sequence that produced it.

The organisation should therefore link each administrative event in time. The resulting journey can show whether a patient received an instruction, tried to clarify it, reached the correct team and completed the appointment. It also exposes where the organisation transferred an unresolved request between channels. This evidence gives managers a specific service failure to investigate instead of treating every non-attendance or complaint as the same problem.

Measure distinct parts of patient experience

Patient experience includes several related but different outcomes. Access concerns whether the patient can obtain the service. Continuity concerns whether later staff can use earlier information. Coordination concerns whether teams complete the necessary handovers. Communication concerns whether the patient understands what will happen and what the organisation requires.

A single satisfaction score cannot identify which outcome failed. Managers need measures that correspond to the journey, such as time to appointment, completed appointments, repeated contacts, unresolved administrative requests and patient-reported experience. They should also compare relevant languages, channels, accessibility needs and patient groups. These distinctions locate the service problem and prevent an average score from concealing a barrier faced by a smaller group.

Use generative AI when coded fields omit the explanation

Administrative records show when an event occurred, but they often omit why the patient struggled. The explanation may appear in an Arabic or English call, message, survey response or complaint. Generative AI can transcribe and organise this material, identify a stated access barrier and connect it to the relevant stage of the journey.

The model's output remains an extracted claim, not an established fact. A model may miss negation, confuse the speaker, mistranslate a dialect or merge two concerns. Analysts must retain the source passage, language, time and model confidence so that staff can inspect the evidence. The organisation should test extraction against representative feedback before managers rely on the resulting themes.

Separate administrative evidence from clinical judgement

A patient may combine an appointment request with a symptom, medication question or concern about clinical urgency. The administrative part may be suitable for service analysis. The clinical part requires an authorised professional. A model cannot convert that boundary into a reliable diagnosis merely because both concerns appear in one message.

The workflow must therefore preserve the patient's clinical words and route them to the responsible clinical team. It should not summarise away a qualification, assign urgency or propose treatment. Mixed cases deserve specific testing because they reveal whether the system recognises the limit of its authority while still completing the permitted administrative step.

Limit sensitive data to a defined service purpose

Technical access to a patient record does not establish a valid reason to use it. Before implementation, the healthcare organisation must define the service purpose, determine which information that purpose requires and restrict access to the responsible people and systems. It should also obtain qualified advice on applicable consent, retention, hosting and health-data obligations.

The design should minimise direct identifiers, record the source of each item and prevent unrestricted reuse of patient material. Access logs and retention rules must cover prompts, model outputs and evaluation cases as well as the operational record. These controls reduce unnecessary exposure while preserving enough evidence to investigate the service journey.

Introduce an agent only for approved non-clinical actions

Feedback analysis may show that patients repeatedly receive an unclear preparation instruction. The organisation must first correct and approve the instruction. An Agentic AI workflow may then retrieve the approved version, confirm the patient's preferred channel, prepare the communication and record that the organisation sent it.

The agent may also coordinate an authorised rescheduling request or refer an unresolved case to the responsible service team. It must stop when the case requires clinical interpretation, an unapproved exception or access beyond its role. This sequence matters: the agent coordinates a response that managers and qualified professionals have already defined; it does not invent a healthcare policy from a complaint.

Test the complete route, not only the model response

A fluent message does not prove that the workflow has improved patient access. Evaluation must cover extraction, routing, tool use, permissions and completion. Representative cases should include Arabic and English feedback, ambiguous wording, mixed administrative and clinical requests, inaccessible appointment options, missing records and failed external actions.

The organisation should compare the workflow with the previous process. Relevant outcomes include completed appointments, waiting, repeat contact, corrected administrative requests, patient-reported experience, staff corrections and clinical escalations. It should also check whether faster administrative handling merely transfers more unsuitable cases to clinical staff. The workflow creates value only when it reduces avoidable patient effort without weakening professional review.

Apply the design to an imaging appointment

Consider a patient who misses an imaging appointment after receiving a fasting instruction. The appointment record shows non-attendance, while a later message says that the instruction was unclear and asks whether a prescribed medicine should still be taken. These are two connected concerns with different owners.

Generative AI may extract the unclear instruction as an administrative barrier and link it to the appointment. The workflow may prepare an approved rescheduling route and send corrected preparation information. However, it must preserve the medication question and refer it to qualified staff without answering it. The case closes only when the organisation confirms the administrative action and records the clinical handoff.

Management can then examine whether the corrected instruction reduces similar missed appointments and repeat calls. It can also review whether the workflow routed every medication question correctly. The example demonstrates the complete value proposition: generative AI makes overlooked service evidence usable, while explicit authority protects the clinical decision.

Develop one accountable patient-experience system

Marketways begins with the administrative decision that management needs to improve. We reconstruct the patient journey, define the relevant experience measures and design multilingual analysis that keeps every finding traceable to its source. We then identify which service actions the organisation may automate and where qualified staff must retain control.

Where the organisation requires automated follow-up, Marketways specifies data access, tool permissions, referral conditions, evaluation cases and completion checks. The resulting system helps managers improve access and communication while preserving privacy, clinical authority and a clear record of every action.

Related guides

References

  1. WHO patient-reported experience measures
  2. WHO ethics and governance of AI for health
  3. WHO guidance on large multi-modal models for health
  4. NIST Generative AI Profile
  5. UAE data protection laws