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 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.
That's the work, and it suits independent SNFs, small chains, and long-term care operators across California — particularly those transitioning IP coverage, recovering from a difficult survey cycle, or already running a competent DON and IP delegate who need the infrastructure under them to hold.
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 cycle, documented end to end.
From raw EHR export to a reviewed dashboard, every step is the same each month — which is exactly what makes the resulting data defensible. Reporting itself runs on several clocks at once: weekly respiratory submissions, monthly reporting for elected modules, seasonal healthcare personnel vaccination, and the annual facility survey. The calendar tracks all of them. See how I work →
Data pull
Scheduled EHR, lab, and pharmacy exports.
Cleaning & validation
Deduplication, onset categorization, denominator checks.
NHSN submission
Prepared, validated, and submitted on your approval.
Dashboard refresh
Counts reconcile to what was submitted.
DON / IP review
A recurring check-in closes the loop.
Quarterly trend review
Longer look back, with leadership.
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.
RN, CIC, California-licensed.
- 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 — and I contractually cannot be one. Cura builds and maintains surveillance and reporting infrastructure that supports your existing DON and IP delegate. You may not designate me as your Infection Preventionist for purposes of 42 C.F.R. § 483.80(b) or California Health & Safety Code § 1255.9, and my hours count toward neither that requirement nor your direct patient care hours. Every engagement assumes you employ a qualified full-time IP throughout.
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. The engagement assumes one EHR; a second system is scoped as a change before work starts.
How long does a Foundation engagement take?
Four to six weeks for the build, depending on data access and facility complexity. Two items intentionally run longer and arrive after close at no additional charge: the written continuation recommendation, which requires watching your team run two reporting cycles unassisted, and — if you use an electronic denominator source — a three-month parallel validation of it.
What happens to patient data?
No patient health information is exchanged until agreements are signed and a secure channel is set up. The Business Associate Agreement must be executed before any Statement of Work involving PHI takes effect — that is a hard precondition. This contact form is explicitly not for PHI.
Do we have to continue after Foundation?
No, and I will tell you in writing if you shouldn’t. Foundation closes with a determination assessed against stated self-sufficiency criteria; where you meet all of them I issue a self-sufficiency statement and don’t propose ongoing services. You keep a perpetual license to everything built for you, and the dashboard transfers to your own environment on request at no charge — whether or not you continue with me.
Do we own the dashboard and scripts?
You hold a perpetual, irrevocable license to use the deliverables for your internal operations at the facilities named in the Statement of Work, and it transfers to an acquirer of that facility. It does not extend to sister facilities, a parent, or a management company that isn’t named, and I retain the underlying methods and templates. Third-party hosting and licensing costs are yours.
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.