Naloxone Dispensing and Standing Order Documentation

This template is for pharmacies, clinics, harm-reduction programs, and other authorized dispensers documenting naloxone provided under a standing order. It works best when staff need a consistent record of the dispense event, counseling, and any refusal or follow-up. It is not a general medication inventory form or a treatment plan. Use it when you need a clear audit trail for a specific naloxone handoff.

A simple log usually records only that naloxone was handed out. This template also captures the standing order reference, product formulation, quantity dispensed, education topics, teach-back completion, and whether follow-up is needed. That makes it easier to show what was provided and what the recipient understood. It also supports minimum-necessary documentation by separating PII disclosure from the dispense details.

Complete it for each naloxone dispensing event, not as a batch summary at the end of the day. Individual event-level documentation helps preserve accuracy, supports an audit trail, and reduces missing details. If your workflow includes repeat education or refill-style distribution, use a new record each time. Do not reuse a prior entry unless your policy explicitly allows an amendment with clear version history.

Yes, the structure separates recipient identity and contact details from the core dispensing record so you can collect only what you need. If your program allows anonymous submission or minimal identification, keep the PII fields optional and use consent language where appropriate. The key is to avoid collecting unnecessary personal data when the dispense can be documented without it. Make sure your local policy and legal requirements allow that approach.

Common mistakes include leaving out the standing order reference, skipping counseling documentation, and using free-text notes instead of structured fields for product formulation or quantity. Another frequent issue is marking every field required, which can block legitimate dispensing scenarios such as refusal or anonymous distribution. Teams also forget to record what happens after submission, especially when follow-up is needed. Clear validation and conditional logic help prevent those gaps.

Record the education topics covered, the method used, and whether teach-back was completed. If the recipient declined counseling or only accepted partial education, note that in the counseling notes rather than forcing a yes/no that hides the nuance. Keep the notes focused on what was actually discussed, such as overdose recognition, administration steps, and emergency response. Avoid unnecessary detail that does not support the dispensing record.

Yes, it should be customized to match the formulations and workflows you dispense, such as nasal spray or injectable products. You can add conditional logic for product-specific instructions, program-specific consent language, or location-based routing for follow-up. Keep the field set lean and only add fields that your staff will actually use. That helps maintain usability and reduces documentation burden.

The form is designed to create a clear audit trail for standing-order dispensing, counseling, consent, and follow-up. It supports minimum-necessary documentation by separating recipient PII from the event record and by making consent explicit when contact details are collected. If your organization has pharmacy, public health, or internal policy requirements, map those requirements to the fields before rollout. The template should reflect your local rules, not replace them.

After submission, the record should route to the appropriate internal owner for review, storage, or follow-up based on your workflow. If follow-up is needed, the form should create a clear next action so staff know whether to call, message, or schedule a return visit. If no follow-up is needed, the record should still be retained according to your retention policy. A submit-confirmation line helps the recipient and staff know the interaction is complete.