Requires NotchRx Core
Turn static SOP files into managed, living documents.
A policy in a Word file is a snapshot of what somebody believed on the day they saved it. A policy in NotchRx knows which version is in force, which locations hold it, who has acknowledged it, and when it is due to be read again.
One master, many locations
Update once. Publish with the right context.
Placeholders carry the parts that differ by site. The pharmacy name, the state, the pharmacist in charge, the effective date, all filled in from the pharmacy's own record, or answered once by the location, and then travelling inside the document wherever it goes.
Immunization protocol
Master · v4Administered at Pharmacy name in the state of State under Pharmacist in charge.
Store 114
OhioStore 114OhioD. Whitmore
9 of 12 acknowledged
Store 208
OhioStore 208OhioR. Nakamura
11 of 11 acknowledged
Store 341
KentuckyStore 341KentuckyL. Barrett
+ Kentucky addendum
6 of 9 acknowledged
What you get
A policy library that answers questions.
- Maintain a single master document and publish the relevant version to each location.
- Use contextual placeholders for location, state, pharmacy name, pharmacist in charge, and your own custom fields.
- Keep an immutable version history. Publishing writes a snapshot, saving a draft does not.
- Assign acknowledgment when a policy is published, and re-acknowledgment when it changes.
- See who acknowledged which version, and when, down to the individual person.
- Set a review cadence of 6, 12, 24, or 36 months, with 30, 45, or 90 days of notice.
- Configure administrator and read-only access separately.
- Upload the documents you already have during onboarding, or link out to policies that live in another system, when you would rather not keep two repositories.
Immunization protocol
Version 4- D. WhitmorePharmacy managerAcknowledged Mar 2
- J. AlvarezPharmacistAcknowledged Mar 3
- T. ReyesTechnicianReminded Mar 6
- M. OkaforPharmacistNot acknowledged
A policy cannot go out half-written
A document with an unanswered placeholder cannot be published, and a locked policy a chain sends down raises a task to fill the blanks rather than an acknowledgment nobody can honestly sign.
Version history
Every version that was ever in force.
An acknowledgment points at the exact wording that was read, not at text that has since been edited. When a surveyor asks what your Ohio stores were working from in March, the answer is a record rather than a reconstruction.
Editing a published policy does not take it down. Staff keep seeing the live wording until somebody publishes the revision.
- v4 · Mar 1, 2026In force
Minimum age aligned to state rule
Published by D. Whitmore · 16 of 28 acknowledged
- v3 · Nov 12, 2025
Standing order reference updated
Published by D. Whitmore · 28 of 28 acknowledged
- v2 · Jun 3, 2025
Storage temperatures corrected
Published by R. Nakamura · 26 of 26 acknowledged
- v1 · Jan 8, 2025
Adopted from the NotchRx library
Published by R. Nakamura · 26 of 26 acknowledged
Connected capabilities
Everything here shares one record.
See it against one of your own SOPs.
Bring a policy your locations actually use. We will show you what it looks like as a managed document, placeholders and all.