How to start a pilot at your hospital
A practical starting framework, from selecting patients to defining safety and evaluation criteria.
The first condition for a useful pilot is a clear scope. Rather than covering the whole hospital at once, select one specialty, a defined patient group and a measurable timeframe.
For example, adults might be monitored during the first seven days after chemotherapy. Eligibility, who needs a different follow-up method, and how consent is obtained should be agreed with the institution's clinical and legal teams.
The second step is the question set. Every call can cover the same core symptoms, with additional questions based on the patient's treatment plan. Questions should be short, clear and easy to answer by phone.
The third step is an escalation plan. Document which answers create which priority of alert, who sees it, who is responsible outside office hours and what happens when the patient cannot be reached. The system must not make diagnoses or treatment decisions independently.
Information security review belongs before the pilot. Data access, retention, consent and any integrations should be agreed against institutional policies. If a pilot starts without integration, document how information transfer will be managed.
Create a simple measurement plan: answered-call rate, time to review alerts, alerts judged useful by staff and patient experience. Defining measures before launch makes the findings easier to interpret.
At the final review, examine missed calls and unnecessary alerts as well as successful examples. Adjust thresholds, wording and team responsibilities accordingly. A wider rollout should be based on the institution's own data and clinical assessment.