Discovery field guide / Industry
How to find AI opportunities in Healthcare
Where should discovery start?
Follow a patient-facing administrative journey across referral, scheduling, records, and revenue-cycle teams. Look for missing information, duplicate entry, and repeated interpretation that delays a useful next step. Interview frontline staff and the clinical owner together. Keep administrative support separate from diagnosis, treatment, clinical prioritization, and other safety-critical decisions; a scheduling improvement must not quietly change who receives care or how urgently.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one referral pathway or appointment type at a defined service. Trace an ordinary case, an incomplete referral, and an access barrier using approved, de-identified or otherwise permitted material. Identify who can resolve missing information and who owns patient safety.
Where to look across departments
Referral and scheduling coordination
Follow referrals returned for missing records, unclear instructions, or mismatched service criteria. Watch staff interpret free-text requests and contact multiple teams. If eligibility rules are unclear or capacity is unavailable, those are not problems a language interface alone can fix.
Records and revenue-cycle handoffs
Inspect how administrative staff gather supporting documents, reconcile identifiers, and prepare queries for authorized reviewers. Separate document completeness from clinical necessity or coding judgments. Check whether the underlying issue is inconsistent data exchange rather than the time required to read a record.
Who to interview and what each person knows
Coordinator, clinician, and access staff
Ask a referral coordinator or scheduler to reconstruct a delayed journey, then ask the clinical owner what information mattered. Include an interpreter, accessibility lead, or patient representative through an appropriate process. Ticket data may omit patients who could not complete the digital route.
Safety, privacy, and system owners
Interview the clinical safety owner, privacy or data-governance lead, and electronic-record integration owner. Include revenue-cycle leadership when payment workflows are in scope. Establish who can approve use of records and who may change routing or patient-facing instructions.
What to ask: follow the evidence
What prevented the next safe step?
Ask which missing fact, referral detail, or approval blocked the case. Was it unavailable, or already held in another system? What did staff do when the patient could not provide it? Capture fallback and escalation rather than assuming the normal digital path works for everyone.
Where does administration become clinical judgment?
Ask whether a suggested classification could change urgency, service access, or instructions. Who verifies that choice? How is an error noticed before harm? Document how staff distinguish clerical completeness from a clinical assessment and what the patient is told when information is uncertain.
Signals of opportunity, and reasons to look elsewhere
Bounded clerical effort with a safety owner
Repeatedly checking whether a referral contains required administrative information may support investigation if an accountable owner can verify the output. Inferring urgency from narrative symptoms is a materially different task. Keep the distinction visible even when both use the same source document.
Duplicated coordination across systems
Multiple teams repeatedly finding the same record can reveal a useful handoff improvement. First check identity matching, record availability, and authorized access. Capacity shortages and unclear referral policy should remain explicit alternatives rather than being hidden inside an AI proposal.
Industry-specific risks and constraints
Safety and access effects
An administrative error can still delay care, misdirect a patient, or exclude someone unable to use a digital channel. Qualified owners must assess local clinical-safety and regulatory requirements. Do not treat an administrative pilot as clearance for diagnosis, treatment advice, or autonomous clinical triage.
Health information and secondary use
Confirm permitted processing, minimum necessary data, access, retention, provider arrangements, and relevant local rules. Do not copy identifiable patient records into a discovery tool merely because they make an example realistic. Include third-party information and sensitive specialties in the access assessment.
How to evaluate what you find
Use realistic incomplete journeys
Test missing referrals, conflicting identifiers, unavailable records, and relevant language or accessibility needs with approved material. Assess omissions, escalation, and safe fallback alongside staff review effort. Judge whether the next step is correct, not simply whether a generated summary sounds clinically fluent.
Keep outcome claims proportional
Measure administrative completion, avoidable rework, access barriers, and the time staff spend verifying results. Clinical outcomes need an appropriate evaluation beyond a clerical trial. Include integration maintenance and safety monitoring in feasibility so an apparent time saving does not transfer work to clinicians.
How to compare, prioritize, and invest
Choose a bounded, supervised pathway
Start with an administrative task whose result staff can inspect before it affects the patient. Repair identity and data-exchange problems first where needed. Require a named clinical safety owner when the workflow can affect access, even if the technology is marketed as nonclinical.
Invest without trading away access
Compare candidates by correct completion, reduced coordination burden, patient access, and retained human capacity. Define stop conditions for misrouting, unsafe instructions, or unequal failure patterns. Service and clinical leaders should decide whether the evidence supports broader use.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Qualify a healthcare administrative workflow in IntakeOS
Bring a process description and approved sanitized examples, not identifiable patient files. Explore IntakeOS discovery to capture the problem, dependencies, and clinical boundary before your governance owners consider a pilot.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo