The questions we hear most, answered.

Enter a new hire once and everything that depends on them starts. The onboarding checklist opens, their licenses join the list ordered by what lapses next, the policies for their role go out for acknowledgment, their continuing education cycle opens, and they are included in the next monthly exclusion screening. None of those steps depends on somebody remembering to do it.

See the platform

A chain maintains one master policy and publishes it to every location. Placeholders such as the pharmacy name, the state, and the pharmacist in charge are filled in from each location's own record, so every site holds the same policy with its own details. Publishing writes an immutable version, acknowledgments are tracked against the exact version that was read, and when version two goes out it replaces version one everywhere while carrying forward the answers each pharmacy already gave. A document with an unanswered placeholder cannot be published.

Policies and procedures

The Office of Inspector General publishes a list of individuals and entities excluded from federal health care programs. Paying an excluded party is a civil money penalty per claim, and the exposure runs from the day they were paid rather than the day somebody noticed. NotchRx loads the new exclusion file each month and screens your active roster, anybody with an invitation still outstanding, and your own list of contractors, billing services, suppliers, and owners. New hires are screened when they join. Only potential matches are escalated for human review, and every determination is kept with who made it and why.

OIG/SAM exclusion screening

Pharmacist, technician, and intern licenses, CPR and BLS cards, immunization certificates, and any custom credential type your organization defines, alongside the credentials the pharmacy itself holds: state board permits, DEA registrations, and accreditations. The list opens ordered by consequence, worst first, with expiration in its own column. Renewal reminders are configured once and sent automatically to the right person before something lapses.

Credentials and licenses

Primary source verification means asking the issuing board directly whether a credential is what it appears to be, rather than reading a copy and believing it. NotchRx keeps the two apart: any pharmacy with Compliance Operations can mark a credential reviewed, and only the primary source verification module can record it as verified. Every check records who asked, which body, by what method, what the board showed the credential to be, and anything adverse that came up. Checks are never overwritten, so a surveyor can see when each one ran and who ran it. A chain can perform verification centrally, and Managed Verification lets an organization verify on behalf of pharmacies it does not own.

Credentials and licensesSee pricing

A checklist is a group of tasks, and both live on the same page. Checklists can recur on a cadence you set, start from an event such as a new hire, or run once, and they are assigned by role, by person, or by location. Steps that need evidence ask for it, and a step that depends on a policy acknowledgment will not close until that acknowledgment is on file. Some tasks create themselves: publishing a policy that requires a signature creates the acknowledgment tasks, and a policy reaching its review date creates a review task.

Tasks and checklists

A person's license determines the state, the license type, the renewal date, and the applicable cycle. NotchRx keeps the state requirement, accepted completions, the evidence, and how each hour was credited beside the license record the cycle comes from. Completions can be imported from a connected education provider, starting with CE Impact, or submitted manually with a certificate, and they count immediately. If the credential or the published state table is incomplete, the product reports what is missing rather than producing a false compliant result.

Continuing education

The evidence is kept as the work happens rather than assembled when somebody asks: every policy version and who acknowledged it, each monthly screening run and its determinations, every credential check and what the board said, every completed task with its proof, and every administrative change. Records can be read for one location or rolled up across the organization. Removing somebody from a roster marks them terminated rather than deleting their acknowledgments, and turning off a module does not delete what it produced.

Audit readiness

An independent pharmacy sets itself up in a single form: industry, name, and address. An access code is generated immediately so the team can be invited, and policies can be adopted from the NotchRx library the same day. Larger organizations get onboarding handled with us, including bulk import of locations and employees from a spreadsheet template, white-label branding, and account management.

Who it's forRequest a demo

Yes. Upload the documents you already hold during onboarding, adopt policies from the NotchRx library, or link out to policies that live in another system when you would rather not keep two repositories. Whichever way a policy arrives, the platform versions it, publishes it, and tracks who has acknowledged it.

Policies and procedures

NotchRx holds compliance records on behalf of the organizations that use it: policies and their versions, acknowledgments, credentials and their scans, task completion and proof, screening determinations, and an audit trail of administrative actions. It is a compliance system, not a patient record system. Some information is deliberately kept out. The identifier used to confirm an exclusion match is entered on the government's own site and never into NotchRx, dates of birth published in the OIG exclusion file are discarded when it is imported, and Social Security numbers are not stored.

Privacy

An independent pharmacy sees and resolves its own records; nobody else decides for it. In a chain, the central team reads a rollup across the estate and can open the one location that is behind, with visibility you control. Some views are deliberately narrower: a chain sees continuing education counts rather than individual certificates, and a scanned license can only be opened by a pharmacy administrator or the person who uploaded it.

Who it's forPrivacy