A surveillance infrastructure practice for skilled nursing facilities.
NHSN reporting, validated surveillance data, and dashboards your DON can sustain after handoff. CIC-credentialed, California-based, and scoped to what your facility actually needs.
Surveillance data is only useful if it's defensible.
Failed NHSN submissions, surveillance that lives in a fragile spreadsheet, numbers that can't survive a survey — most facilities don't have a staffing problem, they have an infrastructure problem. When the data is clean and the workflow is documented, reporting stops being a monthly scramble.
Skilled nursing facilities and long-term care operators in California — independent SNFs, small chains, and facilities transitioning IP coverage or recovering from a difficult survey cycle. I work especially well with facilities that have a competent DON and IP delegate who need infrastructure support, not replacement.
SNF Surveillance Readiness Checklist
A plain, one-page checklist for pressure-testing your facility’s surveillance and NHSN reporting before a survey — the same starting points I use on a Foundation build.
What it covers
- Data sources and export cadence are documented
- Line-list definitions match NHSN protocols
- A submission runbook exists and is current
- Validation catches gaps before they reach the dashboard
- An action log carries findings month to month
No PHI, no sign-up required — just ask and I’ll send it.
Three ways to work together. One scope.
Foundation
Managed Surveillance
Add-Ons
One monthly cycle, documented end to end.
From raw EHR export to a closed action log, every step is the same each month — which is exactly what makes the resulting data survey-proof. See how I work →
Data pull
EHR exports pulled on a scheduled cadence.
Validation & cleaning
Recipes flag gaps, outliers, and inconsistencies.
Dashboard refresh
Validated data updates the dashboard.
NHSN reporting check
Submission follows the documented runbook.
DON / IP review
A short review closes the loop.
Action log follow-up
Items carry forward to the next cycle.
A dashboard your team actually runs.
Every engagement produces a working surveillance dashboard — validated data in, audit-ready reporting out, documented so your DON can sustain it after handoff.
Credentialed, scoped, accountable.
- CICCertified in Infection Control (CBIC).
- RNActive California registered nurse license.
- BAA + MSAEngagements proceed under signed agreements.
- CaliforniaCDPH, CMS LTC, and state surveillance familiarity.
Frequently asked.
Do you replace our Infection Preventionist?
No. Cura builds and maintains surveillance and reporting infrastructure that supports your existing DON and IP delegate — it does not replace clinical program leadership or bedside practice change.
Which EHRs do you work with?
I work from CSV and XLS exports out of PointClickCare, MatrixCare, and most major EHRs. If your system can export surveillance data, I can build a cleaning recipe for it.
How long does a Foundation engagement take?
Foundation is a fixed-fee engagement that typically runs four to six weeks, depending on data access and facility complexity.
What happens to patient data?
No patient health information is exchanged until agreements are signed (MSA + BAA) and a secure channel is set up. The contact form is explicitly not for PHI.
Do we have to continue after Foundation?
No. Many facilities run Foundation and stop there, owning the system outright. Managed Surveillance is available when you want ongoing support, but it is never required.
Start with a focused surveillance review.
The most useful first conversations are 30 minutes and free — no pitch, just a look at where your reporting stands.