Product Security Case Studies FAQ Book a Demo

Built to pass the security review first

Ascenix is a read layer on your system of record. It does not ask your teams to move their data anywhere, it does not send resident information to a public model, and it writes nothing back to your chart unless you switch that on.

HIPAA · PHIPA · PIPEDA Data stored locally Official PointClickCare Marketplace partner

Where the model runs

  • No PHI goes to a public model. Not ChatGPT, not Gemini, not Copilot.
  • Open-weight models on Ascenix's own servers. Data does not cross borders to public APIs.
  • Resident identifiers are stripped before analysis.
  • Data is stored locally, in Toronto for Canadian clients.

What it will and will not do

  • It does not invent data. The platform is restricted to extracting and analysing what is already in the EHR. No invented residents, no invented incidents.
  • Compliant with HIPAA, PHIPA and PIPEDA.

Nothing goes back unless you ask

  • Read-only into your EHR or EMR by default. Ascenix never writes to the chart on its own.
  • The one exception is incidents your own team logged in Ascenix, posted back to keep the record complete. Turned on per home, off until then.
  • Reports are exported and uploaded, or an AI-drafted note is copied across by your team.

What it plugs into

PointClickCare

Pulls from Risk Management and Progress Notes, updates live, as an official partner on the PointClickCare Marketplace.

Yardi

Connected on the same basis.

MatrixCare

Fully supported, on the same basis.

Any other EHR or EMR

Connected by API, a conversation rather than a blocker.

Read-only, by default. Ascenix writes nothing to your chart unless you switch that on.

Access

Who sees what

  • No user or login limit. A flat fee per home regardless of how many people log in, so there is never a reason to share an account to save a seat.
  • Surveyors and compliance visitors can be given restricted login access, or just a clean PDF, so you control exactly what they review.
  • Support is a phone number. Real cell numbers, not a ticket queue.
Setup

Handled on our side

  • Nothing to install and nothing for IT to run. Connecting to your EHR, wiring in your policy thresholds, building your custom columns and matching your paper packet all happen on the Ascenix backend before a pilot starts.
  • No setup fees and no customisation fees.
  • Changes stay free afterwards. Custom columns, graphs, quarters, year-over-year trends and measures like falls per 100 resident-days are added on request, before the pilot and any time after it.

Security questions

Can Ascenix write a note back into our EHR?

No, and not as a limitation we are working around. It is one direction by design. You can export a PDF report and upload it to the EHR, or have the AI draft a progress note for your team to copy across, which keeps a person in between the analysis and the chart.

Where is our data actually sitting?

Stored securely and locally, in Toronto for Canadian clients, and compliant with HIPAA, PHIPA and PIPEDA. Resident information is anonymised before analysis, and the models are open-weight and run on Ascenix's own servers, so nothing crosses a border to a public API.

Can it read the scanned PDFs in our Miscellaneous tab?

Not currently. Ascenix cannot extract data points from a scanned PDF, so a paper DOS sitting in the Miscellaneous tab stays unreadable to it. The options are to keep that on paper or move it to our digital tracker. We would rather say so here than have it surface in week three of a pilot.

We still run paper packets. Does that rule us out?

No. You can switch paper off entirely and use a custom digital form that replicates your exact packet, which is what the Add Incident button opens. It is built to match what your teams already fill in, not to replace it with ours.

Can we give a surveyor or compliance visitor access?

Yes, either restricted login access or a clean PDF, so you control exactly what they review.

Is there a limit on logins or user accounts?

No. It is a flat fee per home regardless of how many people log in, so there is never a reason to share an account to save a seat.

Bring your security lead to the demo

We would rather answer the hard questions in the first meeting than the fourth.