A medication waste verification program can begin with a focused pharmacy workflow and expand where the evidence is most useful. It does not require a device in every clinical area.

WasteWitness supports investigative testing, collected waste testing, mobile audits, and point-of-care verification. These are different operating models, not levels of analytical accuracy or a required sequence. A hospital can use one approach or combine several.

Choose a starting workflow

Begin with the question your team needs to answer and the staff available to operate the process. The first three options can be pharmacy-operated; point-of-care verification puts wasting directly into the clinician’s workflow.

Investigative testing
Best fit: A specific concern about a returned, unidentified, or potentially tampered sample.
Who and where: Trained pharmacy personnel in a secure testing location.
Collected waste testing
Best fit: Recurring testing of waste returned from selected departments.
Who and where: An authorized technician tests collected samples in pharmacy.
Mobile audits
Best fit: Scheduled or targeted testing across several care areas.
Who and where: A technician brings WasteWitness on an approved cart to the department.
Point-of-care verification
Best fit: Routine verification close to the time and place of wasting.
Who and where: Nurses, anesthesiologists, physicians, or other authorized clinicians use a nearby device.

The operator matters as much as the location. A technician conducting a mobile audit in an OR is using a pharmacy workflow; a clinician routinely wasting into the device is using a point-of-care workflow.

Understand how each option works

Investigative testing

Use chemical testing to add information when a medication return looks inconsistent with its documentation, a syringe is unidentified, or tampering or substitution is suspected. Pharmacy reviews the finding alongside dispensing, administration, waste, and other available records.

Plan the handoff: Identify who secures the sample, records its origin and custody, confirms testing suitability, and reviews the result. Before testing potentially evidentiary material, resolve any sample-retention or additional laboratory-testing needs through the hospital’s investigation process.

Understand the coverage: This is testing prompted by a concern. It does not provide routine coverage of waste events that were never selected for review. Identification of unknowns depends on the supported medication library and analytical capabilities.

Collected waste testing

Clinical teams retain eligible waste in an approved, labeled, tamper-evident package with a receipt or other event identifier. Authorized staff collect the packages, reconcile each sample with its record, and bring selected samples to a technician for testing. This is often called a “bag and tag” workflow.

Choose the testing scope:

  • Random: Test a defined selection across eligible events. Document the selection method and the portion of waste covered.
  • Targeted: Test events selected because of a specific concern. Interpret findings within that scope; they may not represent the wider hospital.
  • Comprehensive: Aim to test every eligible sample in the defined program. Track missing, unsupported, and invalid samples separately from completed verification.

Plan the collection process: Agree on labeling, secure holding, collection frequency, transport, reconciliation, and disposal. Collection and testing are separate responsibilities: receiving a bag is not the same as completing a valid test.

Mobile audits

A technician brings WasteWitness on a mobile cart to an approved location such as the OR, PACU, or another procedural area. The team can follow a planned rotation, select areas for random audits, or focus on a specific concern.

Plan the visit: Coordinate timing and placement with clinical leadership, define eligible events, and identify who provides the sample and event details. Confirm cart suitability, power, network access, supplies, device readiness, and the approved transport procedure with PharmID.

Use the experience: A mobile program can help the hospital understand testing demand and staff experience before deciding whether a dedicated device belongs in that area.

Point-of-care verification

A dedicated WasteWitness device sits within or near the clinical workflow. The clinician signs in, selects the medication information, and wastes into the system. Once the device confirms the waste is recorded, the clinician can return to care while WasteWitness completes analysis, documentation, secure disposal, and rinsing.

Keep staff time in view: Wasting typically takes less than 60 seconds per drug, with no waiting at the device for analysis. Measure clinician interaction separately from analysis time during the evaluation.

Plan for consistent use: Place the device where it is convenient, train the intended users, and define which documentation and witnessing steps occur in the hospital’s existing process. Authorized administrators review the analytical results in the dashboard.

Agree on responsibilities and requirements

Before the first evaluation, give each part of the workflow an owner:

  • Testing scope: Pharmacy confirms eligible medications, concentrations, formulations, and sample requirements. See supported drugs and concentrations.
  • Sample handling: Define identification, secure custody, reconciliation, and the handling of missing or unsuitable samples.
  • Daily operation: Assign training, device checks, rinse-water replenishment, waste-container replacement, and support or downtime responsibilities.
  • Clinical participation: Agree on who wastes, where the device sits, and how the process fits patient-care activity.
  • IT and records: Confirm power, connectivity, sign-in, administrator access, and how a verification event connects with medication documentation.
  • Follow-up: Name the reviewers, establish escalation criteria, and decide where conclusions and next steps will be recorded.

Connect records in a way that fits the deployment

WasteWitness can operate with its own verification record while the hospital continues its existing medication documentation. An EHR integration is not required to get started. The team still needs a reliable way to associate the two records.

Where an integration is planned, confirm the supported systems, data fields, and direction of exchange with PharmID and hospital IT. Automated transfer of medication information or results depends on the available integration. Review deployment considerations.

Define the intended use. WasteWitness analyzes a sample introduced into the device; it does not test through a sealed syringe, vial, or bag. It supports waste verification and investigation, not approval of medication for patient administration. The workflow should follow the device instructions and the hospital’s approved handling, witnessing, documentation, and disposal policies.

Turn results into documented review

MED-ID assesses the sample’s chemical findings against the expected medication and supported concentration. Volume measurement adds another comparison where supported by the device configuration. Keep the result categories distinct:

  • Verified: The measured attributes meet the system’s supported verification criteria for the expected waste.
  • Not Verified: One or more expected attributes could not be verified. Review the specific identity, concentration, or volume finding.
  • Inconclusive: The analysis could not make a conclusive determination of one or more attributes.
  • Invalid: A device or software issue prevented a valid result. Follow the approved troubleshooting and follow-up process.

A discrepancy directs attention to an event; it does not establish diversion on its own. Review medication selection, documentation, formulation, sample handling, and technical context before drawing a conclusion.

WasteScore helps reviewers connect related activity over time, including patterns involving drug identity, concentration, volume, and workflow. Automatic Cases and Watchlist placement help focus attention; hospital reviewers decide what investigation or follow-up is warranted. Explore results and waste activity trends.

Measure the workflow before expanding

Choose a defined evaluation period and agree on the events included. Record the counts behind each rate so collection, testing, and matching results do not become interchangeable measures.

Collection and reconciliation
For collected waste, how many expected samples arrived and could be matched with their records?
Testing coverage
How many eligible events were tested? How many produced usable results? Record missing, unsupported, inconclusive, and invalid events separately.
Findings and follow-up
Which findings required review, how quickly were they reviewed, and what did the team conclude? A discrepancy rate is not a confirmed-diversion rate.
Staff effort
Measure clinician interaction, technician collection and testing, and administrator review time separately.
Device use and readiness
Track testing volume, availability, routine supply work, and interruptions by location or operating period.

Use the findings to refine the initial workflow, expand testing within the same area, or add another model. For example, a hospital might retain collected waste testing for several departments while adding point-of-care devices in selected high-volume locations.

The useful starting point is the one your team can operate consistently and follow through on. Use the evaluation planning article to turn these decisions into an agreed scope.

Adapted from PharmID’s Medication Verification: Hospital Workflow and Use Case Guide (October 2026). This guide supports program planning; detailed operating procedures should use the applicable device instructions and hospital-approved policies.