Independent Healthcare-Adjacent CX Project

Patient Intake & Documentation-Compliant Support Workflow

How a non-clinical support team handles patient-facing questions without mishandling sensitive information.

Self-initiated project · grounded in formal Health Information Management training

Why I can build this credibly: I hold a diploma in Health Information Management and completed a hospital internship working with EHR/EMR systems and patient intake. This project applies that documentation-and-privacy discipline to a support-team context — a combination most CX candidates can’t offer.

Telehealth and health-tech support teams field patient-adjacent questions all day — appointment changes, records requests, billing — while staffed by agents with no clinical training. The risk isn’t rudeness; it’s an agent answering something they shouldn’t, or logging sensitive information carelessly. This workflow draws the line clearly.

Scope & honesty note: Independent demonstration project, not work performed for a real employer. It reflects general documentation-discipline and data-minimization principles; it is not clinical or legal advice, and a real deployment would be reviewed against the specific organization’s compliance requirements.

1. Request triage: handle, hold, or escalate

Every inbound patient request is sorted into one of three lanes before the agent responds. The rule is bright-line so a non-clinical agent never has to make a clinical judgment.

Request type	Lane	Rule
Appointment scheduling / reschedule / cancellation	HANDLE	Fully within a non-clinical agent’s scope. Confirm identity first, then act.
Billing, invoices, insurance-status questions	HANDLE	Handle logistics; never speculate on coverage outcomes — state what is on record only.
Records request / release of information	HOLD	Verify identity and authorization, then route through the formal records-release process. Never send records over chat/email directly.
“Is this symptom normal / what should I do?”	ESCALATE	Any clinical or medical-advice question goes to clinical staff immediately. Agent does not interpret, reassure, or advise.
Medication questions, dosage, side effects	ESCALATE	Clinical-only. Escalate; do not answer even if the agent “knows.”
Urgent / emergency language (“chest pain,” “can’t breathe”)	ESCALATE	Immediate escalation path + direct the patient to emergency services. Highest priority, no queue.

2. Intake flow

Step 1 — Verify identity. Confirm at least two identifiers before discussing any account detail. No verification, no information.

Step 2 — Classify the request against the triage table above. When unsure which lane, default to the more cautious lane (HOLD or ESCALATE).

Step 3 — Act or route. HANDLE lane: resolve and log. HOLD lane: start the formal process. ESCALATE lane: warm-hand to clinical staff with a short, factual summary.

Step 4 — Log the interaction using the documentation template below — factual, minimal, need-to-know only.

3. Escalation-trigger checklist

If any of these are true, the agent stops and escalates rather than continuing:

The question asks for interpretation of a symptom, result, medication, or treatment.
The patient uses urgent or emergency language.
The request involves releasing medical records or clinical documentation.
The agent would have to guess to answer.
The patient is distressed in a way that needs clinical, not support, handling.

4. Documentation-logging template

Built on data-minimization: capture what’s needed to continue the interaction and nothing more. No clinical detail is recorded by a non-clinical agent.

Date/Time: [timestamp] Verified ID: [yes/no + method] Request type: [scheduling / billing / records / clinical-escalated] Lane: [HANDLE / HOLD / ESCALATE] Action taken: [factual, one line] Routed to: [team/person, if escalated] Follow-up needed: [yes/no + what + when] Notes: [need-to-know only; no clinical interpretation]

5. Principles this enforces

Principle	How the workflow applies it
Data minimization	The log captures only what’s needed to continue service — no extra clinical or personal detail.
Need-to-know access	Records and clinical detail stay in the formal channels, not in a support chat transcript.
Scope discipline	A bright line keeps non-clinical agents from ever giving clinical guidance.
Auditability	Consistent logging means any interaction can be reconstructed factually later.

Why this matters for the role

Healthcare-adjacent support has a smaller qualified applicant pool precisely because most CX candidates can’t speak to documentation and privacy discipline. This workflow demonstrates that discipline directly — and it’s backed by real Health Information Management training, not claimed from a template.