Harm Reduction Syringe Services Encounter Log
Track each syringe services encounter in one place, including exchange counts, naloxone, wound care, referrals, and first-visit demographics. Built for SSP staff who need a clear record for reporting, follow-up, and anonymous participant tracking.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Syringe Services Programs · Community Health Clinics · Public Health Outreach · Harm Reduction Nonprofits
Overview
The Harm Reduction Syringe Services Encounter Log is a structured workplace form for documenting one syringe services program visit at a time. It captures the core encounter details staff need to track program activity: date, time, site, anonymous participant code, visit type, syringe exchange counts, naloxone services, health and wound care, referrals, and follow-up. The first-visit demographics section is separated so staff only collect those fields when they apply, which supports data minimization and keeps the form shorter for repeat visits.
Use this template when your program needs a consistent record for operational tracking, participant follow-up, and state or local reporting. It works well for fixed sites, mobile outreach, and pop-up services where staff need to document what was provided without over-collecting PII. The conditional sections help with progressive disclosure, so a syringe-only encounter does not force staff through wound care or referral fields that do not apply.
Do not use this template as a general intake form or as a substitute for a full clinical chart. It is not meant to collect unnecessary identifiers, detailed medical histories, or broad social-service assessments. If your workflow requires names, insurance data, or clinical documentation beyond the encounter, keep those in a separate system with appropriate access controls. This template is strongest when it stays focused on the encounter itself and the immediate actions taken during the visit.
Standards & compliance context
- Use data minimization by collecting only the fields needed for encounter tracking, reporting, and immediate follow-up.
- If the form collects any PII or sensitive health information, include a clear consent or disclosure statement and restrict access to authorized staff.
- Keep the participant code anonymous or pseudonymous where possible to reduce privacy risk and support safer outreach documentation.
- If wound care or health service fields are used, limit the record to the minimum necessary information for the program purpose.
- Make required fields and conditional branches explicit so the form is accessible and usable under WCAG 2.1 AA expectations.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Encounter Identification
This section ties each visit to a date, site, participant code, and staff member so the encounter can be tracked without over-collecting identity data.
-
Date of Encounter
Date this visit occurred.
-
Time of Encounter
Approximate time of visit (optional; required by some state reporting systems).
-
Service Site / Location
Select the site or mobile unit where services were provided.
- Other Site Description
-
Participant Anonymous Code
Enter the participant’s unique anonymous identifier (e.g., first two letters of mother’s first name + birth month + birth year). Do NOT enter name or full date of birth.
-
Visit Type
Is this the participant’s first visit to this program, or a return visit?
-
Staff Initials / ID
Initials or staff ID of the SSP worker completing this log.
Syringe Exchange
This section records the core exchange activity, including what was returned, what was distributed, and which supplies were provided.
-
Syringes Returned by Participant
Total number of used syringes returned at this visit. Enter 0 if none returned.
-
Syringes Distributed to Participant
Total number of new syringes provided at this visit.
-
Gauge / Size(s) Distributed
Select all gauge sizes distributed (optional; include if tracked by your program).
-
Ancillary Supplies Provided
Select all additional harm reduction supplies distributed at this encounter.
Naloxone Services
This section documents overdose prevention support, including naloxone provision, education, and whether the participant reported using naloxone since the last visit.
- Was Naloxone Provided?
-
Naloxone Formulation(s) Dispensed
Select all formulations provided at this encounter.
- Number of Naloxone Kits / Units Dispensed
-
Overdose Recognition and Response Education Provided?
Did staff provide verbal or written overdose education (signs of overdose, rescue breathing, calling 911, naloxone administration)?
-
Did Participant Report a Recent Overdose (Self or Witnessed)?
Document any overdose event reported during this encounter for surveillance purposes.
-
Was Naloxone Used Since Last Visit?
If returning participant, did they report using naloxone to reverse an overdose since their last encounter?
Health Services and Wound Care
This section captures any clinical support offered during the encounter so staff can track health needs without turning the log into a full medical chart.
-
Health Services Provided at This Encounter
Select all services delivered during this visit.
-
Wound / Abscess Location (if wound care provided)
Select primary wound site if wound care was delivered.
- Wound / Abscess Severity
-
HIV Rapid Test Result
Record result only if test was administered. Do not record result if participant declines disclosure.
-
Hepatitis C Rapid Test Result
Record result only if test was administered.
Referrals Made
This section shows which referrals were offered, accepted, and completed as warm handoffs, which is essential for follow-through tracking.
-
Referrals Offered to Participant
Select all referrals offered, regardless of whether participant accepted.
-
Referrals Accepted by Participant
Select all referrals the participant agreed to pursue. Leave blank if none accepted.
-
Warm Handoff Completed?
Was a direct introduction or phone call made to connect the participant to a referred service during this encounter?
-
Participant Interest in MOUD / Treatment
Capturing readiness to change supports program evaluation and follow-up outreach.
Participant Demographics (First Visit Only)
This section is limited to the first visit so the program can collect only the demographic data it actually needs.
-
Privacy Notice
The following questions are voluntary and anonymous. Demographic data is collected in aggregate for state reporting only. No individual-level data is shared with law enforcement or other agencies. Participant may decline any or all questions.
-
Age Range
Select participant’s approximate age range. Do NOT record date of birth.
- Gender Identity
-
Race / Ethnicity
Select all that apply.
-
Primary Substance Used (Self-Reported)
Substance most frequently used; used for program planning and state reporting.
- Current Housing Status
Staff Notes and Encounter Summary
This section gives staff a place to note safety concerns, summarize the visit, and record any follow-up plan that needs action.
-
Encounter Notes
Record any relevant observations, safety concerns, follow-up actions, or service gaps. Use anonymous language only (e.g., ‘participant’ not name).
-
Safety Concern Flagged for Follow-Up?
Flag if this encounter requires supervisor review, mandatory reporting consideration, or follow-up outreach.
- Follow-Up Scheduled or Planned?
- Planned Follow-Up Date
How to use this template
- Set up the encounter fields with the correct input types, using numeric inputs for syringe counts, dropdowns for categorical fields, and conditional logic for sections that only apply on some visits.
- Assign each staff member a clear role for data entry, review, and follow-up so the person documenting the encounter knows whether they are capturing the live visit or completing it after the fact.
- Record the encounter identification details first, including date, time, site, participant code, visit type, and staff initials, so the rest of the log stays tied to the correct visit.
- Complete the service sections that apply to the encounter, such as syringe exchange, naloxone, wound care, and referrals, and leave non-applicable fields hidden or blank according to your form rules.
- Review the summary, safety flag, and follow-up fields before submission, then confirm what happens after the form is submitted so staff know where the record goes and who will act on it.
- Export or review the log on your reporting cadence, reconcile counts against inventory or referral records, and update the template if local reporting rules or program workflows change.
Best practices
- Use an anonymous participant code instead of collecting names unless your reporting requirement clearly requires an identifier.
- Keep first-visit demographics behind a first-visit-only condition so repeat encounters stay fast and minimally invasive.
- Make syringe returned and syringe distributed separate numeric fields so staff do not have to infer net exchange from a single entry.
- Use progressive disclosure for naloxone, wound care, and referral details so staff only see the fields that apply to the encounter.
- Mark optional fields clearly and avoid making every field required, especially in outreach settings where some information may not be available.
- Add a short disclosure line explaining what the data will be used for and who can access it when any PII or sensitive health information is collected.
- Include a follow-up date field only when follow-up is actually scheduled, and pair it with a clear action owner.
- Review entries at the end of the shift for missing counts, duplicate participant codes, and inconsistent visit types before exporting reports.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records a single syringe services program encounter from check-in through follow-up. It captures exchange counts, naloxone distribution, wound care, referrals, and first-visit demographics in a structured format. Use it when you need a consistent encounter record for program operations and state reporting. It is designed for anonymous or low-PII workflows.
Who should complete the encounter log?
SSP staff, outreach workers, nurses, or peer workers can complete it during or immediately after the visit. The staff member who handled the encounter should enter the details while the information is fresh. If your program uses role-based workflows, one person can collect the data and another can review it for completeness. Keep the process simple enough to fit a high-volume, low-friction setting.
How often should this form be used?
Use it for every encounter that your program needs to count or report. That usually means each participant visit, whether the person receives syringes, returns syringes, gets naloxone, or only asks for referrals. If your site has multiple touchpoints in one day, log each encounter separately so counts stay accurate. Avoid batching details from memory at the end of the shift.
Does this template collect personal information?
It is built around an anonymous participant code rather than a full identity record. That supports data minimization and reduces unnecessary PII collection. If your program adds names, phone numbers, or other identifiers, include a clear consent/disclosure field and limit access to authorized staff only. Keep first-visit demographics optional unless your reporting rules require them.
What are the most common mistakes when using this log?
Common issues include leaving syringe counts blank, mixing up returned versus distributed quantities, and marking every field as required even when it only applies to some visits. Another frequent problem is skipping conditional logic for naloxone, wound care, or first-visit demographics, which makes the form longer than it needs to be. Programs also sometimes forget to record what happened after a referral or follow-up was scheduled. A short review step at the end of the encounter helps catch these gaps.
Can this be customized for our local reporting rules?
Yes. You can add or remove fields based on state syringe exchange reporting requirements, local health department needs, or internal program metrics. Keep the core encounter fields stable so your data stays comparable over time. If you add new fields, make sure each one has a clear purpose and uses the right field type, such as dropdowns for categories and numeric inputs for counts.
How does this fit with other systems or workflows?
This log can feed a spreadsheet, case management system, or public health reporting workflow. It works well when paired with a participant registry, referral tracker, or inventory log for syringes and naloxone. If you export the data, map each field consistently so counts and categories do not drift between systems. Keep the encounter log as the source of truth for what happened during the visit.
What should we do before rolling it out at a site?
Train staff on which fields are required, which are conditional, and when to use the anonymous participant code. Test the form with a few real-world scenarios, such as a syringe-only visit, a naloxone visit, and a wound care visit, to make sure the branching works. Confirm that the submission flow includes a clear confirmation and that staff know where the record goes after submission. Review any local privacy, consent, and reporting expectations before launch.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
Ready to use this template?
Get started with MangoApps and use Harm Reduction Syringe Services Encounter Log with your team — pricing built for small business.
