Teletriage

What is teletriage?

Teletriage is clinical triage done at a distance. A registered nurse, or in some services a physician or advanced practice clinician, asks structured questions about a symptom, applies a triage protocol and gives the caller a disposition, from self-care at home to an emergency department, with care advice to match.

The output of a teletriage call is a decision with a clinical owner. The software exists to make that decision consistent, to record why it was made, and to get the record to the clinician who sees the patient next.

Where is teletriage used?

Teletriage sits wherever patients call before they know what kind of care they need. The setting changes who answers, which protocols apply and where the record must go.

• After-hours practice lines: Nurses answer calls for one or more practices overnight and on weekends, and send each note back to the patient's own practice.
• Health plan nurse lines: Members call a plan-run line, which has no direct EHR access to the treating practice and relies on summaries and referrals.
• Virtual care front doors: A telehealth service triages first, then routes the patient to a video visit, an in-person clinic or emergency care.
• Hospital and health system call centers: Central nurse lines that also book appointments, so triage and scheduling share one system.
• Employer, school and campus programs: Lines for a defined population, which often need extra privacy controls and different follow-up paths.

How does a teletriage call run from intake to disposition?

A well-built triage call follows the same order every time, with emergency screening before anything else. The steps below are the core workflow the software has to support.

• 1. Intake: Capture caller identity, patient demographics, call-back number and the patient's current location, and match the patient to an existing record where one exists.
• 2. Emergency screen: Ask the emergency questions first. A positive answer ends the protocol and directs the caller to emergency services, with the location already on screen.
• 3. Protocol selection: The nurse picks the symptom protocol that fits the main complaint. The software suggests protocols from the complaint but never chooses one silently.
• 4. Question flow: The nurse works through the protocol questions in order. Each answer is stored as structured data, not as free text typed after the call.
• 5. Disposition: The protocol gives a recommended disposition. The nurse accepts it or overrides it up or down, and an override requires a reason.
• 6. Care advice and action: The nurse gives the protocol's care advice, books an appointment or refers the patient, and confirms the caller understood.
• 7. Handoff: The encounter note goes to the patient's EHR or primary practice the same day, with the disposition and any follow-up the practice must act on.

Two time stamps matter for quality review: when the call arrived and when a nurse first spoke to the caller. Programs that only track call length miss the wait that callers experience.

Call-backs need their own queue. When a caller leaves a message or the line is busy, the system should hold the call-back with its arrival time and the screened complaint, so the most urgent call-backs rise to the top instead of waiting in arrival order.

Protocols, overrides and the disposition record

The protocol set is clinical content, and the software is the engine that runs it. A program can license a published symptom protocol set, such as the Schmitt-Thompson protocols, or write its own. Writing and maintaining a full set takes sustained clinical effort, so licensing is the faster starting point for a new line.

Licensed content usually arrives as structured data that the engine loads and versions. Each call should record the protocol version used, so a later review can see exactly what the nurse was shown.

Overrides are where clinical judgment shows up in the data. A nurse who upgrades a disposition because the caller sounds worse than the answers suggest is doing the job well. A pattern of downgrades on one protocol may point to a training need or a protocol that does not fit the population.

Local additions, such as a practice's preferred urgent care sites or after-hours pharmacy list, belong in separate configuration, not inside the licensed protocol text. Mixing them makes protocol updates risky.

Who can triage a caller in another state?

Only a nurse licensed for the state where the caller is located. The Nurse Licensure Compact states that a nurse must be licensed in the state where the patient is located at the time nursing service is provided, and that this applies to telehealth as well as in-person care.

A multistate compact license covers patients in other compact states. A caller located in a non-compact state still needs a nurse who holds that state's license.

For the software, that means patient location is a required field captured at the start of every call, not taken from the home address on file. The routing logic should send each call to a nurse whose licenses cover the caller's current state, and block the protocol from starting if none is available.

Nurse licenses then become data the system maintains: license states, compact status and expiry dates, checked automatically when nurses log in and when calls are routed.

Can software or AI make the triage decision?

Software can recommend, but the program has to decide who owns the decision, and that choice affects FDA status. Under FDA's final Clinical Decision Support Software guidance (issued January 2026), software can fall outside device regulation when it supports a health care professional who can independently review the basis for its recommendations.

A nurse-facing protocol engine that shows the questions, answers and the protocol logic behind a disposition fits that model well. The nurse can see why the software suggested a disposition and can override it.

A patient-facing symptom checker sits outside that carve-out, because it is not aimed at a health care professional. That does not make it a device automatically; FDA's wellness and enforcement discretion policies may apply, and intended use decides. A product team should get a regulatory review before launch.

Large language models fit best around the decision rather than inside it: summarizing the caller's description for the nurse, suggesting a protocol to open, or drafting the note for the nurse to edit. Each suggestion should be visible as a suggestion, and the nurse's final answers should remain the record.

What should the triage record and audit trail hold?

The record has to let a reviewer rebuild the call. That means the protocol and version, every answer, the recommended and final disposition, any override reason, the advice given and the actions taken.

The HIPAA Security Rule lists audit controls as a required standard at 45 CFR 164.312(b): mechanisms that record and examine activity in systems containing ePHI. For triage software, that covers who opened, edited or exported each call record, and when.

Call recordings, if kept, are part of the record set. Decide the retention period with the clinical and legal leads, store recordings with the same access controls as the note, and link each one to its call.

The handoff to the treating practice is the step most often left manual. An HL7 v2 or FHIR interface to the practice EHR, or at minimum a secure message to the practice inbox with the structured note attached, keeps the triage note from living only in the call center system.

Where teletriage builds go wrong

The failure points below come from the workflow itself, and each one has a design control.

• Location taken from the address on file: The caller is traveling and the nurse is not licensed there. Control: ask for current location on every call.
• Free-text answers: Protocol answers are typed into a note after the call, so no one can audit them. Control: capture answers as structured fields during the call.
• Silent overrides: Dispositions change without a reason. Control: require a reason code and free text for every override.
• Notes stuck in the call center: The treating clinician never sees the triage note. Control: send it to the practice EHR the same day and track delivery failures.
• Scheduling staff giving advice: Non-clinical staff answer symptom questions. Control: route any symptom call to a nurse queue and limit non-clinical scripts to booking.
• Self-care calls never reviewed: A caller advised to stay home later goes to the emergency department. Control: review a sample of self-care dispositions and any linked emergency visits.

How Agnotic can help

A triage program depends on software that captures the call accurately and moves the record to the right place. Agnotic Technologies builds that software for practices, nurse lines and virtual care services: multi-channel intake, licensure-aware routing, protocol engines that load licensed content, override capture, audit logging and EHR handoffs.

Your clinical leaders choose the protocols and own the dispositions. Agnotic builds the system that records each step and the quality review queues that show where the program needs attention.

Sources

• Nurse Licensure Compact: Nurses and the NLC, telehealth
• FDA: Clinical Decision Support Software guidance
• eCFR: 45 CFR 164.312, Technical safeguards