iTrust intranet · build plan

How we'd build it

This is the plan for turning the demo into something real. It's a training and policy system inside Kenzie, with a small dashboard added at the end. Nothing here is locked in until Dave and I sit down on it.

01 · The stack

We build on Kenzie, not our own setup

Kenzie already has logins, storage and notifications, so we don't need to build those again. We add the intranet on top and pull a few numbers from the tools iTrust already uses.

What we build

This is our part. We'd work in our own copy of Kenzie, on the intranet side only. We don't touch anything clinical or patient related.

Policies and versionsTrainingCompliance view IncidentsVendorsDaily checklists SearchDashboard

What we borrow from Kenzie

Dave and Wen already built these. We'd use them as they are.

Login and accountsFile storageNotifications Cert expiry tracking (V3)Roles, plus a new executive role App shell and sidebarStripe billingDrChrono connection

What we read from

We only pull totals, and we'd connect one tool at a time. Everyone keeps using these tools like they do now.

Microsoft 365 · tasks, calendar QuickBooks · scheduled reports DrChrono · counts only Rippling · alerts only

We don't pull patient records, pay or HR files, and no PHI goes in.

Need from Dave: what Kenzie is built with, where it's hosted, and where the sign-off records should be kept so nobody can change them later.

One login

Staff already log into Kenzie every day, so training reminders show up where they already are.

Easier to support

Dave's team can look after it, and Wen only has to review one system for security.

No rebuild later

If we built it outside Kenzie first, we'd end up rebuilding it inside Kenzie anyway.

02 · The build

Eight parts, in this order

Parts 1 to 3 are what replaces NavX. Even if we stopped there, it'd be worth paying for. The rest we'd add after.

Start here

Replaces NavX

PART 1

Policies and versions

Every policy keeps its old versions. When a policy changes, everyone it applies to gets asked to sign again, and signatures can't be changed later.

policies · versions · signatures

PART 2

Training

Short sections people can come back to, a quick quiz at the end, and a record of which version they finished and when.

modules · sections · progress

PART 3

Compliance view

Shows who's up to date by person, team and practice, including who started and didn't finish. It's where Lea gets her overall number. If training is overdue, Kenzie can lock the person out until it's done.

built from parts 1 and 2

After that

What Dave said a real compliance tool needs

PART 4

Incidents

Someone reports it, it gets a reference number, and we track it until it's closed.

incidents · events

PART 5

Vendors

Cost, renewal date and the signed agreement in one place. Lea sees what we spend, and compliance sees the paperwork.

vendors · agreements

PART 6

Daily checklists

Steve asked for this one. Each role gets a daily checklist, and every sign-off is saved.

templates · sign-offs

PART 7

Search

Type a question like you'd ask a coworker, and get the answer plus the policy it came from.

index over policies and docs

PART 8

Dashboard

We'd do this last because it doesn't replace any software. People pick which panels they see, and it pulls totals from one tool at a time.

read-only connectors

03 · What it replaces

It replaces tools iTrust already pays for

Lea said she'll pay for whatever we replace. These are rough figures, not quotes.

NavX

$10 to 15k

a year · policies and training

Accountable

$5 to 8k

a year · HIPAA templates, if we replace it too

What the dashboard replaces

Nothing

That's why training and policies come first, and the dashboard comes last.

04 · Free vs paid

My first guess, for Dave to push back on

Dave said pricing changes how we'd build it, so we need to agree on this before any real code gets written.

Free To get practices started

Document storage and a simple policy library
A few starter policy templates
Read and acknowledge, without version tracking

Paid Anything an auditor would check

Version history, and sign-off records nobody can change
Training modules and completion records
Compliance reports and overdue lockout
Search, incidents, vendors, checklists
Integrations and the dashboard

Basically: if an auditor would ask to see it, it's paid. That's also why practices pay for NavX and Accountable now.

05 · Before we start

How we'll work, and what we need

How we'll work

Work in our own copy of Kenzie, intranet side only
Fake data until Wen has reviewed security
No PHI. Totals only
A testing guide for Gianne before anyone else sees it
Sit down with 3 or 4 people who use NavX every day instead of sending a survey
Keep whatever Grace likes about NavX

Questions for Dave

What's Kenzie built with, and what should John and I learn before we start?
When can we get our copy of Kenzie and the repo?
Is the intranet the V4 pick, or still up against the referral directory and EHR features?
Where should the sign-off records live so nobody can change them?
Does every iTrust employee have a Kenzie login?
Is the free vs paid line roughly right?
Who owns the policy content? The templates and HIPAA video need a lawyer, not code.
Do we use the notification system as is for training reminders, or extend it?

What I'm asking for: 45 minutes with Dave this week on structure, pricing and the repo. After that we can start on part 1.

← Back to the demo