The binder problem
Healthcare organizations rely on hundreds of policies and procedures. Most are kept in a way nobody would choose.
Shared drives and email
Three versions of the same policy, and nobody sure which one the team is following.
Approvals by signature sheet
Signed, scanned, filed. When an auditor or surveyor asks who approved the infection control policy and when, someone goes looking.
Review dates in a spreadsheet
Kept by one person. Found to be out of date during an inspection, or after an incident.
Acknowledgement by assumption
"Staff have been made aware." Of which version? Which staff? Since when?
Who it is for
Built for healthcare organizations of all sizes.
One surgery center, five urgent care locations, a home health agency, a medical group or a small hospital: the policies differ, and the work of keeping them approved, read and reviewed is the same.
- Urgent care
- Ambulatory surgery centers
- Medical groups
- Specialty clinics
- Behavioral health
- Home health
- Hospice
- Long-term care
- Rural healthcare
- Hospitals
How a policy lives here
One loop, and the record writes itself.
- 01
Written
An author uploads the PDF or Word file. It has a number, a department, a review cycle. Nobody else sees it yet.
- 02
Sent for approval
The approval workflow takes it: the department, then the approver, then whoever your organization’s chain requires. Each decision is on record with a name, a time and any comment.
- 03
Approved and published
The last signature publishes it. Staff see it that moment; the previous version is kept, read-only, forever.
- 04
Acknowledged by the right people
Everyone it applies to is asked to read it and say so. Reminders chase the ones who have not, and an administrator sees who is overdue.
- 05
Reviewed before it lapses
Ninety, sixty and thirty days before its review date the owner is reminded. A lapsed review is easy to miss until someone asks for the policy; here it is a task that arrives on time.
What is in it
The core is the policy loop. The rest is what compliance asks for next.
Policy library
Numbered, filed by department, category and type, searchable by full text. Every version kept.
Approval workflows
Whatever your chain is: department review, then approver, then a committee. Decisions recorded with names and times. Stalled approvals chased weekly.
Acknowledgements
Assigned to everyone or to chosen departments on publish. Reminders, overdue reports, a record that answers "who has read this?"
Review cycles
A date on every policy, reminders at 90, 60 and 30 days, an overdue list for the administrator.
Audit log
Who did what, when, to which record. Exportable. Retained.
Add-ons
Scope of Service, Forms & Attestations, Competency & Training, Exceptions & Variances. Switched on per organization.
What each one doesdays before a review date the first reminder goes out, then at 60 and 30
is how long a sign-in link lives. No passwords, nothing to reset
passwords for your staff to manage, ever
Pricing
Simple, transparent pricing.
You shouldn’t need an enterprise software contract just to manage your policies and procedures. Plans go by the number of locations, never by the number of people.
Clinic
$1,995 / year
1 location
Professional
Most popular$2,995 / year
Up to 5 locations
Organization
$5,995 / year
Up to 15 locations
All plans include unlimited employees and readers.
Hospitals and health systems: contact us for pricing.
Getting in
A link in their email. Never a password.
Staff type their work address and get a sign-in link that lives fifteen minutes and works once. Nothing to reset, nothing to reuse across sites, nothing worth phishing for. Anyone who can change who gets in enters a Google Authenticator code as well.
Security and sign-inWhat a staff member sees. The link reaches their inbox, opens once, and is gone fifteen minutes later.
The standards and regulators a policy library answers to
See it with your own policies.
A demo takes half an hour. Bring three of your policies and we will walk one of them through the loop, end to end.