From evaluation to launch
Build a patient outreach workflow your team can use with confidence. Explore connection options, prepare the right people and data, and plan a focused pilot with Positive Check.
Start with the platform workflow that fits your team. For an EHR or another external system, confirm compatibility and the scope of any custom work during your technical review. API availability does not mean a prebuilt connector exists for every system.
Manage patients, schedules, call records and alerts in the provider console. Discuss a dashboard-led pilot if you want to evaluate the workflow before scoping a custom connection.
Prepare: Identify who will enroll patients, review results and respond to alerts.
Bulk patient import is available in the platform. Agree the import format and field mapping with the team before preparing a production roster.
Prepare: Confirm patient identifiers, contact details, preferred language and call windows with your implementation contact.
The platform offers API access to patients, call records and transcripts, conversations, alerts and analytics, with API-key authentication and per-key rate limits.
Prepare: Request the current OpenAPI documentation and agree access, field mappings and the data your workflow needs.
The platform supports signed webhooks to receive events from your systems, plus structured report exports with de-identified options for sharing.
Prepare: Agree supported events, signature verification, delivery handling and report fields before implementation.
Explore the platform capabilities or request API documentation and an integration review.
Use these steps to plan your launch together. Timing depends on your data readiness, security review and integration scope; agree milestones during scoping.
Choose a care program and a focused patient cohort. Agree what a successful pilot would show, such as contact completion, time spent reviewing calls or alert response time.
People to involve: Provider operations lead and Positive Check
Review the Business Associate Agreement and security requirements before exchanging patient information. Identify your clinical escalation owner, access roles and approved data-transfer method.
People to involve: Provider clinical, IT and security leads with Positive Check
Review call questions, cadence, languages, call windows and escalation rules. Start with test records; check imports or API mappings, summaries, notifications and handoffs before enrolling the pilot cohort.
People to involve: Positive Check with provider clinical and integration leads
Agree staff training and patient introduction materials. Make sure the care team knows how to review calls, respond to alerts and handle a missed check-in, and that patients know what to expect from Lola.
People to involve: Provider care team with Positive Check
Set a pilot review date and compare results with your starting point. Adjust scripts, call windows and escalation routing before agreeing a wider rollout.
People to involve: Provider program owner and Positive Check
No. API access is not a promise of a prebuilt EHR connector. Bring your system name, version, available interfaces and intended data flow to the technical review. Confirm which connection is supported, what requires custom work, who maintains it and how failures are handled before committing to a production rollout.
Agree the current import template before transferring patient records. Review identifiers, contact details, language and call-window preferences with the implementation team, including required fields and validation rules. This page is a planning checklist, not an API or CSV specification. Use synthetic records for scoping and an approved secure transfer method for production data.
Assign named provider owners for patient eligibility and consent, clinical review, escalation coverage and documentation before launch. Agree the platform configuration and handoff process with Positive Check, including out-of-hours coverage and unsuccessful contacts. Automation supports the workflow; it does not replace clinical judgment or establish that every alert will receive an immediate human response.
Discuss a dashboard-led pilot if your team can review calls and alerts in the provider console. Confirm how patients will be enrolled and how clinically relevant information will reach the care record. A limited pilot can test the operational fit, but any temporary manual transfer steps must be included in workload and security reviews.
Agree a baseline, reporting period and expansion criteria before launch. Measure completed contacts, staff review time, alert response times and patient opt-outs with clear denominators. Test missed calls, incorrect contact details and failed handoffs as well as successful calls. The clinical and operations owners should approve expansion only when coverage and follow-up responsibilities are workable.
Request written pricing for the agreed patient volume, outreach scope and integration requirements. Clarify any minimum commitment, onboarding or custom-work charges, support responsibilities and pilot terms. Separate one-time costs from recurring costs and include your own clinical staffing. Calculator assumptions are not a binding quote or a complete estimate of the cost to deliver care.
Published by Positive Check. Content updated September 13, 2026.
Walk through the platform with us and discuss the setup, integration questions and pilot goals that matter to your organization.