For skilled nursing facilities on PointClickCare
NourishNet watches every weight in PointClickCare, puts each significant change in front of your dietitian, and closes the loop only when the chart shows it was dealt with.
Synthetic data. No real residents appear on this site.
The problem
Significant unplanned weight loss is one of the most visible things a surveyor checks under F692. Most facilities already have the data. What they lack is someone, or something, watching it every day.
A 5% loss charted on Tuesday can sit unseen until the dietitian's next visit. Between visits, nobody is watching the scale.
The dietitian writes a recommendation. Whether the care plan or the order actually changed is something you find out in survey.
DONs, regional dietitians and corporate have no shared view of which units are slipping, or which dietitian is behind.
How it works
Nobody is asked to attest that something was done. NourishNet keeps watching PointClickCare until the chart shows it.
Sync reads census, weights, progress notes, care plans, orders, labs, vitals and MDS items from PointClickCare. It never writes back.
Versioned rules apply the F692 thresholds, admission weights and weighing cadence. A reading that looks implausible goes to Nursing as a reweigh request first.
Every alert ends with the dietitian's verdict: confirmed change, expected change, or wrong weight. Only the dietitian can make that call.
A confirmed change stays open until sync sees the progress note, care-plan revision or order change in PointClickCare. Then it closes itself.
Significant unplanned loss under 42 CFR 483.25(g). Stamped with the rule version on every result, so you can always show which rule fired.
For your team
Everyone signs in to the same data and sees it from where they stand: the dietitian's next decision, the DON's floor, the region's weakest building.
Dietitian
DON and ADON
Regional dietitian
Corporate
Survey readiness
Twelve reports, each anchored to 42 CFR 483.25(g) and F692. They run on demand from the current record, so there is nothing to assemble the night before.
The systems audit turns gaps into items with an owner and a date. When the record shows a gap is gone, the item closes without anyone ticking a box.
Every report exports to CSV, and every view and export is recorded in the audit log.
Beyond the scale
Every rule is plain arithmetic you can read, tested, and stamped with its version. Nothing is a black box.
Reviews due at 30, 60 and 90 days, then quarterly. Residents still losing weight on a supplement are flagged for the unit manager.
Read from the record: diuretics, cognition, tube feeds, age, recent dehydration or UTI, and lab signals such as a high BUN-to-creatinine ratio.
Residents whose loss meets the AND/ASPEN weight-loss characteristic but have no malnutrition diagnosis coded, with an estimate of the PDPM impact.
Catches rounding bias and weights copied forward from the last entry, so bad data is fixed before it turns into an alert.
A triage score built from 20 signals, with every point explained. Your organisation sets it, and each building can adjust it.
Ranks residents by nutrition-related readmission factors so the plan reaches the right people first. It ranks; it does not predict.
AI, carefully
Inside NourishNet
Sent to the model
A leak guard checks the exact payload before it leaves. Names are put back only inside NourishNet, on your screen.
Security
PointClickCare stays the system of record. NourishNet keeps the work around it: alerts, verdicts and review dates. Privacy was a design rule from the start, not a feature added later.
No writes, ever. PointClickCare stays your system of record, and NourishNet never changes a chart.
Every read and export of resident data is logged with its purpose, in an audit log that can't be edited.
Every record belongs to a facility, and people see only the buildings they are assigned to.
Notifications carry counts and a link back into the app. Never a name.
The model receives de-identified, already-computed facts, and nothing else.
TLS in transit. PointClickCare credentials and sessions are sealed with AES-256-GCM.
FAQ
No. Weights, notes, care plans and orders stay in PointClickCare, entered the way they are today. NourishNet reads them and tells each person what needs their attention.
Never. It is read-only by design. When NourishNet drafts a note, the dietitian edits it and charts it in PointClickCare themselves.
Census, weights and heights, progress notes, care plans, orders, diagnoses, labs, vital signs, and MDS items including BIMS and GG eating.
Meal intake, the MAR and diet orders aren't available through PointClickCare's interface today, so NourishNet doesn't depend on them. Where a rule would need them, it says so instead of guessing.
Dietitians, DONs and ADONs, administrators, dietary managers, MDS coordinators, regional dietitians and corporate. Each sees the buildings they are assigned to, in the view that fits their job.
No. Every alert ends with a dietitian's verdict, and every number comes from the rules engine. The AI drafts prose and answers questions over de-identified facts.
No, and we don't present it as one. It is a transparent triage aid: every point is explained, your organisation sets the weights, and each change is versioned.
Book a demo. We'll walk through NourishNet on synthetic data, with the dietitian's day, the DON's floor view and the regional roll-up, and talk through connecting your buildings.
A 30-minute walkthrough on synthetic data: the dietitian's day, the DON's floor view and the regional roll-up.