From patient data to care intervention in under 24 hours
A read-only EHR connection is all it takes. Patientrig ingests, scores, and queues interventions without disrupting your existing clinical workflows or requiring any EHR write access.
Connect once. Data flows daily.
Patientrig establishes a read-only connection to your EHR using standard HL7 FHIR APIs or ADT event feeds. We pull three data types: admission-discharge-transfer events, claims and encounter history, and pharmacy fill records. That's all we need to build the risk model.
The connection takes 1–2 hours to configure with your EHR team. Once live, data refreshes automatically every 24 hours. No manual exports, no CSV uploads, no scheduled IT tasks.
A ranked patient queue, updated every 24 hours
Our risk model analyzes three signal types simultaneously: appointment-adherence patterns (how often has this patient missed, and in what sequence), medication refill history (how many days before the prior fill did they refill, and is that window lengthening), and social determinants proxies derived from encounter patterns and zip-level data.
Each chronic disease population gets its own model — a CHF patient's risk pattern looks nothing like a Type 2 diabetic's. The output is a ranked queue per care team: who needs outreach today, what type of outreach, and why.
Three channels, one queue. The right reach for each patient.
Intervention isn't one-size-fits-all. Patientrig supports three outreach channels — each targeting the most effective point in the care pathway. The care coordinator reviews the queue, confirms interventions for high-priority cases, and lets the system handle routine outreach automatically.
The escalation logic adapts: if a patient doesn't respond to SMS within 48 hours, it surfaces to the nurse call queue automatically. If the gap is a refill issue, the pharmacy alert fires in parallel — reaching the pharmacist who can follow up at pickup.
Implementation timeline
From signed contract to live care coordinator queue — 4 weeks.