For behavioral and mental-health groups

One clear view across every site,
without exposing patient data.

Your raw patient data is sanitised in your own browser first. The AI never sees raw PHI.

Census, billing and outcomes live in different systems, so the group-wide picture is always a step behind. We build the dashboard you already wish you had, on a sanitised copy of your data, so the numbers are current and your patient records never leave your machine in the raw.

Now in pilot: onboarding a first cohort

What we build for you

The dashboards groups ask for first.

Census and utilisation

Track occupancy and utilisation by site, day by day, so the group-wide picture is current, not a month behind.

Outcomes by programme

See which programmes move patients and which need attention, side by side across every site.

Admissions funnel

Find where referrals stall before a client is admitted, and fix the leak.

The problem we remove

The reporting bottleneck, gone.

  • Census, billing and outcomes live in different systems, so the group-wide picture is always out of date.
  • You want one clear view across every site, but a normal build means handing patient data to an outside team. That is exactly the exposure we remove.
  • Leadership asks for the numbers weekly, and every answer starts with a manual export.

Privacy by default

Two ways to send data. Both run in your browser.

You choose how much ever leaves your machine. Either way, your raw file never leaves it.

Nothing real leaves your machine

Start with a sample

Send about ten rows per table. We invent a full-size dataset with the same shape and build on that. Nothing real reaches us at all, so no data agreement is needed.

Pseudonymised, data agreement first

Sanitise your real data

Every value is swapped for a realistic fake, in your own browser. The output is pseudonymised rather than invented, so it needs a short data agreement (BAA / DPA) first.

Honest limits: pseudonymisation is not anonymisation. Column names leave in default mode and dominant category patterns can persist. We are upfront about that on purpose.

Questions, answered honestly

Behavioral health, answered.

Do you handle patient data (PHI)?

Your raw patient data is sanitised in your own browser before anything is sent, so the third-party AI only ever sees a sanitised copy, never raw PHI, and never the re-identification key. Handing raw records to an outside build team is exactly the exposure this removes.

Are you HIPAA compliant?

Vizmask is in pilot and we do not claim a certification we have not completed. What we can say plainly: the AI never sees your raw patient data, and for the sanitised-real-data path a data agreement (BAA / DPA) is put in place before any real data is handled. For the sample path, nothing real ever reaches us.

What dashboards do you build for behavioral health?

The three most groups ask for first: census and utilisation by site, outcomes by programme, and the admissions funnel. We build the one you already wish you had, then expand from there.

Which BI tool do you use?

Power BI, Metabase or Tableau, your choice, so you keep working in the tool your team already knows. Every build passes the same optimisation and verification gate before delivery.

Is my data anonymous after sanitising?

No, and we will not claim it is. It is pseudonymised: materially harder to re-identify, but not anonymous. Column names leave in default mode and dominant patterns can persist. That honesty is the point.

See the dashboard you already wish you had.

Book a demo or launch the tool. Nothing real is sent until you approve, and your raw patient file never leaves your machine.