Our Story

We built Patientrig because chronic patients were disappearing and nobody had a system to catch them

Founded in Pittsburgh, 2024. Three people who came out of clinical informatics and care coordination — and couldn't stop thinking about the patients who fell through the cracks.

2024
Founded in Pittsburgh, PA
3
Founders from clinical informatics and care coordination
4
Chronic populations — one product, done right

The spreadsheet that started everything

In the spring of 2023, I was embedded in a regional health system in Pittsburgh as a clinical informatics lead — my job was to make the data work better for care teams. One afternoon, a care coordinator named Linda showed me how she managed her panel of 800 diabetic patients.

She had a spreadsheet. Color-coded, meticulously maintained. Every Monday morning, she'd run a report from the EHR, paste it into her spreadsheet, and manually sort by last appointment date. Then she'd call patients. She could reach maybe 40 patients a week — which meant 760 patients weren't getting a call that week. Some of those patients had opened a refill gap three weeks earlier. She'd find out at their next appointment, if they showed up.

"There were 800 patients in her panel. She could call 40 a week. The math doesn't work — and it never will, if we keep doing it manually."

I went back to my desk and started thinking about what an automated version of Linda's Monday process would look like. Not a patient portal — Linda didn't need her patients to log in to anything. Not a generic wellness app. A tool built for the care coordinator: something that ran the risk analysis overnight, ranked the patients who needed contact that day, and fired the outreach so Linda could focus on the patients who needed a real conversation.

I left the health system at the end of 2023 and started Patientrig in early 2024 with Derek Osagie, who I'd worked with on EHR integration projects, and Camille Fontaine, who had spent eight years actually working the care coordination queue. We didn't want to build for the market — we built for Linda, and for every care coordinator who's been working a spreadsheet while patients go quiet between visits.

We're based in Pittsburgh, still bootstrapped, still small. We think that's the right size for a company building something this specific. We're not trying to be a population health platform — we're trying to be the best possible tool for the care manager who's responsible for a panel of chronic patients and needs to know who to call tomorrow.

Rebecca Nwosu, CEO and Co-Founder of Patientrig
Rebecca Nwosu
CEO & Co-Founder
The team

Three people who've lived in the problem

No one on this team came from enterprise health IT sales. We came from clinical informatics, healthcare data engineering, and care coordination itself.

Rebecca Nwosu, CEO and Co-Founder of Patientrig
Rebecca Nwosu
CEO & Co-Founder
Former clinical informatics lead at a regional health system. Built her first patient outreach model in Excel before concluding the gap wasn't a process problem — it was a tooling problem. Patientrig's risk model architecture reflects what care coordinators actually need to see, not what the EHR surfaces by default.
Derek Osagie, CTO and Co-Founder of Patientrig
Derek Osagie
CTO & Co-Founder
10 years in healthcare data engineering. Previously built claims reconciliation pipelines at a regional payer. Leads all EHR integration and risk model architecture. Responsible for the read-only connection approach that makes our 4-week implementation timeline possible.
Camille Fontaine, Head of Clinical Success at Patientrig
Camille Fontaine
Head of Clinical Success
Spent 8 years as a care coordinator and population health manager before joining Patientrig. She's the reason our workflow feels like it was designed by someone who's actually worked the queue — because it was. Leads onboarding for every new customer personally.
What we believe

Three principles that shaped every product decision

01
Clinical specificity over general wellness
We build for four specific chronic conditions — not "patient engagement" as a category. A CHF patient's ACE inhibitor refill gap looks nothing like a hypertension patient's BP reporting silence. Generic population health tools flatten both into the same alert. We don't.
02
Intervention timing matters more than intervention volume
Sending 500 SMS messages isn't better than sending 50 at the right moment in the right patient's care trajectory. Our risk models prioritize timing precision over outreach volume. A well-timed pharmacy alert beats a weekly wellness newsletter.
03
Data access without workflow disruption
Every feature we build must work with a read-only EHR connection and require minimal care team training. If it needs write access or a week of staff onboarding, we haven't designed it correctly yet.
Pittsburgh, PA
Based in Pittsburgh — home to UPMC, Allegheny Health Network, and a dense concentration of academic medical centers and health IT.
[email protected] +1 (412) 359-8186 525 William Penn Place, Suite 3000, Pittsburgh, PA 15222