Classified out of the note, not off a checkbox.
5of 13 falls this monthEvery incident, in one language
Falls, behaviours, hydration and skin come out of the notes your teams already write, and get read against each other rather than one report at a time. Nobody charts anything twice.
One command centre
Every screen carries a date range: a weekend view on a Monday, last quarter or last year for QAPI.
35% under the monthly cap
Organisation baseline 10.7 falls per home
Open issues flagged against each home's own policy
Flagged in the week it happens, not at survey.
4of 13 incidentsWhere it keeps repeating, before the next shift.
6of 13, in a resident's roomRead alongside the falls, not on its own.
3days under goal, Mon to SatOr log it here
Most homes keep logging in the EHR and Ascenix reads it. If your team would rather log incidents here, they can, and every one is posted back up to the health record, so the chart stays complete either way. Read-only is the default; write-back is a switch you turn on.
Your packet, as a form
- The paper packet your home already uses, rebuilt as a digital form that matches it field for field.
- One Add Incident button, on any module: a fall, a behaviour, a hydration miss, a skin issue.
- Resident demographics come across on their own, so nobody retypes a name, a date of birth or a room.
Posted back to the chart
- Each incident is written back to the resident's record in your EHR or EMR, so the chart is never behind what your team logged.
- A surveyor, a family member or a nurse on nights finds it where they already look, not in a second system.
- Turned on per home. Leave it off and Ascenix reads and nothing else.
The layer that turns records into decisions
The same records, read four ways: who is next, what fell short, what leadership needs out, and which way the month is moving.
Ranked before the next shift
Cedar · falls, hydration 88
Birch · hydration, behaviours 81
Birch · falls 64
Maple · hydration 58
Cedar · falls 41
Rule-based score over incidents already documented
Risk Radar scores every resident across every module at once. It is deliberately rule-based, over incidents already documented, so a ranking can be explained to a surveyor rather than defended as a black box. Each name opens into a twelve-week severity heatmap and a projection of where the next period is heading.
Red in the week it happens
Okonkwo, Samuel · 72-hour follow-up
72-hour post-incident monitoring complete. No new injury. Vitals stable. Neurological checks clear. Resident returned to baseline.
Posted to the EHR. The record is closed.
| Resident / Date | Location | RHA Location | Cause | Interventions | Actions |
|---|---|---|---|---|---|
| Whitfield, Eleanor02/23/2026 · 3:45 PM | Resident's Room | N/A | Resident fell due to unknown cause. T… | Nursing interventions inclu… | |
| Okonkwo, Samuel02/23/2026 · 9:30 AM This incident is non-compliant because: | Resident's Room | N/A | Resident fell due to slipping from her c… | Nursing interventions inclu… | |
| Bergeron, Alice02/22/2026 · 7:15 PM | Reception / Lobby | N/A | Resident fell due to unknown cause. T… | Nursing interventions inclu… | |
| Castellanos, Miguel02/22/2026 · 5:40 AM | Resident's Room | N/A | Resident fell due to getting out of bed… | Nursing interventions inclu… | |
| Novak, Ruth02/22/2026 · 12:00 AM | Hallway | Glenmore | The resident fell due to a lack of balan… | Resident was redirected ba… | |
| Tremblay, Denis02/21/2026 · 2:00 AM | Resident's Room | N/A | Resident fell due to unknown cause. T… | Nursing interventions inclu… |
Every incident is checked against your own post-incident standard, not a generic one. A record that falls short turns red with the reason on the flag. Add the missing note, post it to the EHR, and the flag clears.
Out in one click
| Total falls | 13 of 20 goal |
| Falls with injury | 5 |
| Hospital transfers | 1 |
| Behaviour events | 7 from 11 |
| Non-compliant records | 4 |
| Falls per 100 resident-days | 0.46 |
Any filtered view, one click, for QAPI or survey
Monthly goals, organisation baselines and exports built for what they are actually used for: QAPI packs, board reporting and survey. One click to PDF, or any filtered view out to secure CSV or Excel. Custom columns, quarters, year-over-year trends and measures like falls per 100 resident-days, at no charge.
Every home against the baseline
Maple Ridge is running almost a fifth over the organisation average.
One view across every home, benchmarked against the organisation average. Injury rate, non-compliance, fall rate and counts, per home, so the one that is deviating is a fact on a screen before the month is over. Any view goes out to CSV in one click.
When they keep happening
The 05:00 to 07:00 window carries 13 of 35 incidents, and it is the shift with the lowest staff presence.
Thirteen of thirty-five falls land between 05:00 and 07:00. The histogram runs on three months because a time-of-day pattern needs volume behind it, and the cluster is the one Glenn reports on the board above.
Rising, falling, and why
Holistic for the home, or personalised to one resident at a time.
Whether behaviours are rising or falling, and what is likely behind them. The month's insights arrive as plain sentences: the peak window, the most common type, the residents above the average. Not another chart to interpret.
Sample data. No real resident information appears on this site.
Ask it what’s going on
Glenn reads a home's full incident history and answers in plain language. Then you ask it follow-ups the way you would ask a colleague.
On top of all of it, on every board.
Sample data. No real resident information appears anywhere.
What it does
- Summarises a resident's incident history and suggests targeted care-plan interventions, instantly.
- Checks the existing care plan first: if non-skid socks are already charted, it looks for the gap instead of re-suggesting them.
- Drafts the progress note for your team to copy into the EHR, so a person stays between the analysis and the chart.
Things to know
- We integrate with any note structure the team already uses, RNAO or anything else.
- We support custom compliance requirements. If the data is in the EHR, we can get it.
Can it do that?
Usually yes, and usually customised to how your homes already work.
What actually counts as non-compliant?
Whatever your policy says. It is configured to your own post-incident standard rather than a generic one. Typically that is the wrong number of post-fall notes, a missing POA notification, or an incomplete assessment.
A nurse wrote the progress note but forgot the RMS form. Does the incident vanish?
No. Ascenix pulls from both. It captures the incident from the progress note and flags the missing form in red, so the gap is visible instead of silent.
Can we clear a flag when we know the work was done?
Yes. You can override and clear a compliance flag directly in the platform. The common case is recording Self-POA where a resident is their own decision maker and no POA was contacted.
Can I look at one resident rather than the whole home?
Yes. Search and filter the dashboard down to an individual to see their trends, including recurring falls.
Can we get quarterly and annual views for QAPI?
Yes. The reporting is highly customisable and quarter-by-quarter or annual graph views are straightforward to add. Any filtered dashboard view exports instantly to PDF, or to a secure CSV or Excel file for a scorecard or a QA/PI meeting.
Our psych unit needs behaviours split more finely than yours.
That is a normal request. Specific behaviours can be split, an attempt to hit separated from actual physical contact for instance, and new features like that are typically added within a couple of weeks rather than a release cycle.
Four modules.
One suite.
Captured once, read together: falls, behaviours, hydration, and skin and wounds.
Because the data sits together, a hydration dip can be seen influencing falls and a behaviour spike can be seen creating compliance risk. That connection is the whole point, and it is not available when each of these lives in a separate report.
The 05:00 to 07:00 window carries 13 of 35 incidents
Falls
Counts, injuries and hospital transfers against a monthly goal, with the analytics that show when and where the patterns repeat.
- Time, location and injury-type analytics highlight recurring falls and predisposing factors.
- RNAO post-fall assessments pulled in and audited for missing fields.
- Post-incident compliance on every fall, against your own standard.
Grouped by unit, time of day and documented trigger
Behaviours
Verbal, physical, wandering, refusal and hallucination incidents by time and unit, with triggers, interventions and PRNs on one per-resident table.
- Antipsychotic-use concerns flagged against your policy rather than a generic rule.
- Redirection and reassurance recorded as attempted before any PRN was given.
- Cross-facility comparisons surface homes or residents needing support before risk escalates.
Two falls followed in the same week
Hydration
Intake against each resident's own goal from the care plan, colour-coded by streak and printable for shift handoff.
- Printable for shift handoff: the five to ten residents to push fluids on tonight.
- Filterable by unit, by infection status, and by G-tube against oral intake.
- Reporting and export tools show goal achievement and home-level risk profiles.
| Open pressure injuries | 3 |
| Highest stage on the unit | Stage 2 · Room 118 |
| Repositioning documented | 11 of 12 |
| Wound assessments on time | 8 of 8 |
| Also on this resident | falls, hydration |
Out of the Risk Management records your teams already complete
Skin and wounds
Brings skin and wound incidents into the same picture as the rest, so a pressure injury is read alongside everything else happening to that resident.
- Pulled from the same Risk Management records your teams already complete. No new charting.
- Tracked as a first-class incident type through analysis, compliance and reporting.
- Carried into Risk Radar's severity view alongside falls and behaviours.