Get started
ComplianceLive · in the productRegister

PolicyVault

SOPs with versions and read-proof, not shelf-ware.

Get PolicyVaultOpen the appAvailable nowHow pricing works →

What it is

Controlled documents with owners, review dates and versioned approvals; staff acknowledge the versions their role requires, and the gap report names who has not read what.

Who uses it
Built for: Every specialty
Reads
Documents
Writes
Versions, acknowledgements
Never
It does not mark a policy current past its review date.
Access
Only people whose role includes it — the clinic owner decides who
Your data
No PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record; operational history stays queryable.

How it works

  1. Create the policyNew policy takes a title and a category, and the database refuses a second policy with the same title — the next revision is a version of the existing one.
  2. Draft the next versionAdd version writes the procedure itself into a numbered draft, and Edit draft keeps changing it for as long as it is unpublished.
  3. Publish itPublish stamps the time and the publisher together and the guarded update then refuses any further edit, so the version people acknowledged is the version that stays on the screen.
  4. Acknowledge what is in forceI have read this records your acknowledgement against the current version, which is computed as the latest published one rather than flagged, and the service refuses an acknowledgement on a draft.
  5. Read the compliance listUnder a policy, Who has read it lists every person against the version currently in force, marked read with the date or not yet — publishing a new version starts that list again.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not mark a policy current past its review date.

AI in PolicyVault

AskQuestions about what is on screen — “What needs attention in PolicyVault today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Policies — SOPs with versions and proof staff read themCaptured from the running demo clinic
PolicyVault — Policies — SOPs with versions and proof staff read them
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Hands to · 1
See the whole clinic →

Questions clinics ask

What does PolicyVault do?
SOPs with versions and read-proof, not shelf-ware. Controlled documents with owners, review dates and versioned approvals; staff acknowledge the versions their role requires, and the gap report names who has not read what.
What data does PolicyVault read and write?
PolicyVault reads documents and writes versions, acknowledgements. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.
What does PolicyVault deliberately not do?
It does not mark a policy current past its review date.
What happens to our data if we uninstall PolicyVault?
All clinical data stays in the record; operational history stays queryable.
Is PolicyVault available today?
Yes — PolicyVault is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see PolicyVault running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Compliance

All 154 →