Healthcare · Moraph software

Pharmacy Diversion Monitor

Spot unusual controlled substance handling early, and review it fairly

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Pharmacy Diversion Monitor brings together automated dispensing cabinet transactions, medication administration records, waste documentation and schedules, and compares each clinician's controlled substance handling with peers in similar roles and units. Unusual patterns are raised for your diversion team to review with the evidence behind them, and every review, interview and outcome is recorded. A flag is a reason to look, not a finding: your team decides what happened and what is reported.

The problem it solves

Most hospitals review controlled substance activity through reports exported from dispensing cabinets, compared by hand with administration records and waste witness logs. The work is slow, depends on a few experienced pharmacists, and tends to find problems late. Discrepancies are resolved on the unit without a central record, reviews of the same clinician are spread across email and spreadsheets, and when a theft or significant loss has to be reported, assembling the evidence takes days.

  • Dispensing, administration and waste data sit in separate systems
  • Peer comparisons are run by hand and only occasionally
  • Reviews, interviews and outcomes are not kept in one record
  • Evidence for loss reporting and investigations is assembled after the fact

Who uses it

  • Controlled substance diversion program managers and specialists
  • Pharmacy directors and pharmacists responsible for controlled substances
  • Nurse managers and nursing leadership
  • Diversion committees with pharmacy, nursing, compliance, security and human resources members
  • Compliance officers responsible for DEA registration obligations

Requirements it supports

Controlled Substances Act (21 U.S.C. 801 et seq.)DEA security requirements for registrants (21 CFR 1301.71 to 1301.76)DEA theft or significant loss reporting (21 CFR 1301.76(b), DEA Form 106)DEA recordkeeping requirements (21 CFR Part 1304)Medicare Conditions of Participation: pharmaceutical services (42 CFR 482.25)HIPAA Privacy and Security Rules (45 CFR Parts 160 and 164)

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    The flag queue

    Reviewers start from one queue of flags, each with the rule or measure behind it and the unit it came from.

    FlagClinicianUnitReasonScoreStatus
    FL-1182Clinician 4417 (fictional)Surgical ICUWaste rate well above peer groupHighNew
    FL-1179Clinician 2093 (fictional)Emergency departmentRemovals with no administration recordedHighIn review
    FL-1171Clinician 3368 (fictional)5 NorthRemovals during shifts not scheduledMediumIn review
    FL-1166Clinician 1820 (fictional)PACUWaste recorded long after removalMediumUnit follow-up
    FL-1160Clinician 5512 (fictional)OncologyOverride use above peer groupLowClosed, explained
    Reviewers start from one queue of flags, each with the rule or measure behind it and the unit it came from.

  2. Step 2

    Why the flag was raised

    Each flag shows the measures compared with peers and the transactions behind them, in words a reviewer can check.

    Clinician 4417 (fictional) · Surgical ICU · Waste pattern

    Peer group
    ICU registered nurses, day shift
    Period
    30 days
    Wastes of hydromorphone
    19, peer median 4
    Wastes with same witness
    14 of 19
    Removals linked to administration
    All

    Reasons

    • Partial-dose wastes far more frequent than peers on the same unit and shift
    • Most wastes witnessed by the same colleague
    • Pattern began in the second half of the period
    Each flag shows the measures compared with peers and the transactions behind them, in words a reviewer can check.

  3. Step 3

    The linked transactions

    Every removal is shown with its administration and waste, so the reviewer can see exactly where the pattern comes from.

    RemovalMedicationPatientAdministeredWastedWitness
    Day 12, 07:52Hydromorphone 2 mgPatient 612070.5 mg at 08:051.5 mg at 08:06Clinician 4630
    Day 12, 11:40Hydromorphone 2 mgPatient 612070.5 mg at 11:471.5 mg at 11:49Clinician 4630
    Day 13, 09:15Hydromorphone 2 mgPatient 612441 mg at 09:301 mg at 13:02Clinician 4630
    Day 13, 14:20Hydromorphone 1 mgPatient 612441 mg at 14:28NoneNone
    Every removal is shown with its administration and waste, so the reviewer can see exactly where the pattern comes from.

  4. Step 4

    From flag to case

    When a flag has no explanation, it becomes a restricted case; only the people named on it can see it.

    Case DV-0091 · Restricted

    1. Flag FL-1182 reviewed, no explanation foundDiversion specialist
    2. Case opened, access limited to named membersDiversion specialist
    3. Pharmacy and nursing leaders added to caseDiversion specialist
    4. Transaction audit for 90 days recordedPharmacist reviewer
    5. Interview scheduled under policyHuman resources partner
    6. Case summary sent to committeeDiversion specialist
    When a flag has no explanation, it becomes a restricted case; only the people named on it can see it.

  5. Step 5

    The committee decision

    The committee decides the outcome, and the product records the decision, follow-up actions and any loss report information for the registrant.

    Case DV-0091 · Outcome

    Decision by
    Diversion committee
    Outcome
    Recorded under policy
    Follow-up
    Monitoring plan, 3 scheduled reviews
    Loss reporting
    Information prepared, awaiting registrant review
    Rule tuning
    No change proposed

    Actions

    • Monitoring plan opened
    • Witness practice education for Surgical ICU
    • Loss report information sent to registrant
    The committee decides the outcome, and the product records the decision, follow-up actions and any loss report information for the registrant.

  6. Step 6

    Patterns that are not about one person

    Unit views show where waste, overrides or late documentation point to a process problem rather than a person.

    UnitMedicationWastes per 100 removalsOverridesLate documentationNote
    PACUFentanyl41LowHighCabinet stocks only larger vials
    Surgical ICUHydromorphone22LowMedium
    Emergency departmentMorphine18HighMediumOverride list under review
    5 NorthOxycodone3LowLow
    Unit views show where waste, overrides or late documentation point to a process problem rather than a person.

Workflows

The principal workflows

  1. Collect

    Transactions from your automated dispensing cabinets, administration and waste records from the EHR, and staff schedules arrive on your schedule and are linked by patient, clinician, medication and time.

    • Cabinet removals, returns, wastes, overrides and discrepancies arrive by interface or file
    • Administration and waste documentation arrive from the EHR
    • Schedules and assignments arrive from your staffing or time system
    • Each removal is linked to its administration, waste or return
    • Records that cannot be linked are listed for data review

  2. Analyze

    Each clinician's handling is compared with peers in the same role, unit and shift, and patterns your team has chosen to watch are scored with the reasons shown.

    • Peer groups built by role, unit and shift pattern
    • Measures such as removals per patient, waste frequency, overrides and delayed documentation compared with peers
    • Single-transaction rules check items such as removals with no administration or removals while off shift
    • Unusual patterns raised with the measures and transactions behind them
    • Statistical scores shown alongside the plain reasons, never on their own

  3. Review

    A diversion specialist or pharmacist reviews each flag, looks at the underlying transactions and decides whether it has an explanation, needs follow-up with the unit, or should become a case.

    • Flag opened with the measures, peer comparison and transactions
    • Reviewer checks patient context, such as acuity and orders, in the linked records
    • Explained flags closed with a reason
    • Documentation issues sent to the nurse manager for education and follow-up
    • Unexplained patterns escalated to a case

  4. Investigate

    Cases keep the evidence, interviews, actions and outcome in one record, with decisions taken by the people your policy names and reportable losses prepared for your registrant to submit.

    • Case opened and access restricted to the people named on it
    • Transaction audits, interviews and testing results recorded
    • Diversion committee or designated leaders decide the outcome
    • Theft or significant loss information prepared for your DEA registrant to file
    • Follow-up actions such as monitoring or education tracked to closure

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Diversion specialist

Diversion program manager, diversion specialist, controlled substance compliance pharmacist or nurse

Runs the day-to-day program: reviews flags, opens and works cases, and keeps the evidence and decisions together.

Sees

  • All flags with their measures and transactions
  • Peer comparisons for every clinician in scope
  • Cases they are named on
  • Discrepancy and waste review results

Does

  • Reviews and closes flags with a reason
  • Escalates flags to a case and names the people on it
  • Records transaction audits, interviews and evidence
  • Prepares case summaries for the committee
  • Prepares theft or significant loss information for the registrant
  • Proposes changes to rules and thresholds

Cannot

  • Decide a case outcome alone where your policy requires the committee
  • Apply a rule or threshold change without committee approval
  • See cases they are not named on
Approvals
Case outcomes and rule changes are approved by the diversion committee or the leaders your policy names.
Notified about
New flags, unresolved discrepancies past the time your policy sets, and case tasks coming due.

Pharmacist reviewer

Clinical pharmacist, pharmacy operations manager, controlled substance pharmacist

Reviews flags and discrepancies for the units and medications they cover, bringing pharmacy knowledge to whether a pattern has an explanation.

Sees

  • Flags for their assigned units
  • Linked transactions and peer comparisons
  • Cabinet discrepancies and their resolution status

Does

  • Reviews flags and records whether they are explained
  • Escalates unexplained flags to the diversion specialist
  • Resolves or escalates cabinet discrepancies
  • Adds medication or process context to a review

Cannot

  • Open cases or see restricted case records unless named
  • Change rules or thresholds
  • Close a flag on a clinician they directly supervise or work alongside, where your policy excludes it
Approvals
Their closures can be sampled by the diversion specialist for second review.
Notified about
New flags for their units and discrepancies unresolved past the time your policy sets.

Nurse manager

Nurse manager, unit director, charge nurse with delegated access

Follows up documentation problems and discrepancies on their units, without seeing investigations.

Sees

  • Documentation follow-ups sent to them for their units
  • Unresolved discrepancies on their units
  • Unit-level patterns by medication and shift

Does

  • Follows up late or missing documentation with staff
  • Records education given and the response
  • Resolves discrepancies with the staff involved
  • Raises a concern to the diversion specialist

Cannot

  • See flags or peer comparisons for individual clinicians unless shared
  • See cases or know that a case exists
  • Close a flag
Approvals
None; follow-ups they complete are reviewed by the diversion specialist or pharmacist.
Notified about
New follow-ups for their units and discrepancies they need to resolve.

Diversion committee member

Chief pharmacy officer, chief nursing officer, compliance officer, security director, committee chair

Governs the program: decides case outcomes, approves rules and thresholds, and oversees reporting.

Sees

  • Case summaries brought to the committee
  • Program trends by unit, medication and outcome
  • Rule and threshold changes awaiting approval

Does

  • Decides case outcomes and required actions
  • Approves rule and threshold changes
  • Approves theft or significant loss reports before the registrant submits them
  • Reviews program reporting

Cannot

  • Edit evidence or case notes
  • Approve a change they proposed themselves without a second member
  • See named detail for cases outside committee scope
Approvals
Decisions follow your committee's charter; the product records who decided and when.
Notified about
Cases and rule changes awaiting a decision, and committee packs ready for a meeting.

Human resources partner

Employee relations partner, human resources business partner

Takes part in cases where employment action may follow, so the process follows your human resources policies.

Sees

  • Cases they are named on
  • Interview records and outcomes for those cases
  • Follow-up actions assigned to human resources

Does

  • Records employment actions and dates
  • Schedules and records interviews with the diversion specialist
  • Tracks return-to-work and monitoring agreements

Cannot

  • See flags or cases they are not named on
  • Change evidence or transaction data
  • Decide case outcomes outside your policy
Approvals
Employment decisions follow your human resources policies; the product records them but does not make them.
Notified about
Cases they are added to and actions assigned to them.

Auditor (read-only)

Internal auditor, compliance auditor, external reviewer (under temporary access)

Reviews the program's records and decisions without being able to change anything.

Sees

  • Flags, cases and reports within the scope granted
  • Rule and threshold history
  • The audit trail

Does

  • Searches and reads records within their scope
  • Exports records they have been given access to, with each export logged
  • Leaves review notes where enabled

Cannot

  • Change, approve or delete anything
  • See records outside the scope and dates granted
  • Keep access after it expires
Approvals
Their access is approved by the committee chair or an administrator, with a scope and an end date.
Notified about
Nothing by default; access granted and expiring is confirmed to the person who approved it.

Administrator

Application administrator, pharmacy informatics analyst

Manages users, roles, interfaces and peer group settings without access to flags or investigations.

Sees

  • Users, roles, units and peer group settings
  • Interface status for cabinet, EHR and scheduling data
  • The record of permission changes

Does

  • Adds and removes users, or maps them from single sign-on groups
  • Assigns roles and units
  • Maintains unit and cabinet mappings
  • Monitors interface errors and works them with Moraph support
  • Runs access review reports

Cannot

  • Open flags, cases or peer comparisons
  • Change rules or thresholds
  • Grant themselves a review role without a second administrator
Approvals
Role changes that grant access to flags or cases are approved by the diversion committee chair.
Notified about
Interface errors, access reviews coming due and accounts not used for a period your policy sets.

Permissions at a glance

ActionSpecialistPharmacistNurse managerCommitteeHR partnerAuditorAdmin
View flags and peer comparisonsFullOwn work onlyNo accessView onlyNo accessView onlyNo access
Close flags with a reasonFullOwn work onlyNo accessNo accessNo accessNo accessNo access
Escalate a flag to a caseFullOwn work onlyNo accessNo accessNo accessNo accessNo access
Work restricted casesOwn work onlyNo accessNo accessView onlyOwn work onlyView onlyNo access
Decide case outcomesNo accessNo accessNo accessApprovesNo accessNo accessNo access
Resolve cabinet discrepanciesFullOwn work onlyOwn work onlyNo accessNo accessNo accessNo access
Complete documentation follow-upsView onlyView onlyOwn work onlyNo accessNo accessNo accessNo access
Change rules and thresholdsNo accessNo accessNo accessApprovesNo accessView onlyNo access
Prepare loss report informationFullNo accessNo accessApprovesNo accessView onlyNo access
View audit trailView onlyNo accessNo accessView onlyNo accessView onlyView only
Manage users and rolesNo accessNo accessNo accessApprovesNo accessNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • A flag is not a finding. The product proposes patterns worth reviewing; people decide whether there is an explanation, whether a case is opened and what the outcome is, and each decision is recorded with its reason.
  • Cases are restricted to the people named on them. Nurse managers work documentation follow-ups without seeing flags or knowing whether a case exists.
  • Roles are configured with you during implementation, including who may review clinicians they work alongside. Every permission change is recorded in the audit trail.
  • Staff sign in through your identity provider, and roles can follow its groups. Auditors get temporary read-only access with a defined scope and an end date.

Features

What it does

Linked transaction view

Each removal from a dispensing cabinet shown with its administration, waste or return, and the time between them.

Peer comparison

A clinician's handling compared with peers in the same role, unit and shift pattern, so differences in patient mix are taken into account.

Explained flags

Every flag lists the measures and transactions that produced it, in words a reviewer can check, alongside any statistical score.

Single-transaction rules

Rules for removals without administration, waste without a witness, removals while off shift and overrides, set and tuned by your team.

Discrepancy tracking

Cabinet count discrepancies followed from the unit to resolution, with unresolved ones raised to pharmacy.

Waste and witness review

Waste documentation, witness patterns and wastes recorded long after removal, compared across clinicians and units.

Restricted case records

Investigations visible only to the people named on the case, with interviews, evidence and outcomes in one place.

Loss reporting preparation

Theft or significant loss information gathered from the case for your DEA registrant to review and submit on DEA Form 106.

Unit and medication views

Patterns by unit, medication and shift, to find process problems that are not about any one person.

Rule and threshold history

Every change to a rule, measure or threshold, with who proposed and approved it and when.

Monitoring plans

Follow-up monitoring for a clinician returning to practice or under agreement, with reviews scheduled and recorded.

Committee packs

Summaries of flags, cases, outcomes and trends for the diversion committee, without names unless the committee's role allows.

Integrations

How it connects to your systems

Connects toHowWhat flows
Automated dispensing cabinetsRemovals, returns, wastes, overrides, counts and discrepancies from the dispensing cabinet system you use, by interface or scheduled file.In: cabinet transactions and discrepancy records.
EHR medication administrationOrders, administrations and waste documentation from the medication administration record.In: orders, administrations and documented wastes.
Anesthesia recordsWhere used, anesthesia medication records so procedural areas are compared on their own terms.In: anesthesia administrations and wastes.
Pharmacy inventoryVault and pharmacy inventory movements for controlled substances, to compare with cabinet activity.In: inventory receipts, transfers and counts.
Scheduling and time systemsShifts and clock times, so removals while off shift can be identified.In: schedules and clock-in and clock-out times.
Single sign-onStaff sign in through your identity provider (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APIAggregate flag, case and program data available to your data warehouse through the Moraph Work API, with restricted case detail excluded by default.Out: flags, case status and program measures.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Staff sign in through your identity provider, so your password and multi-factor policies apply.

Restricted investigations

Case records are visible only to the people named on them, and the existence of a case is hidden from everyone else.

Business associate agreement

Moraph signs a business associate agreement with your organization, because the product processes protected health information.

Encryption and keys

Data is encrypted in transit and at rest, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail

Every view of a flag or case, every decision and every export is logged with the person and time, and cannot be edited.

US hosting

Data is hosted in Moraph's United States region; every release passes security testing gates and ships with a software bill of materials.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Open flags

For diversion specialists and pharmacist reviewers

Flags awaiting review with their measures, unit, age and assigned reviewer.

Break down by
Unit, Rule or measure, Reviewer, Age
Delivered as
Live work list; CSV export
Used for
Making sure every flag is reviewed in the time your policy sets.

Unresolved discrepancies

For pharmacy and nurse managers

Cabinet count discrepancies not yet resolved, by unit, medication and age.

Break down by
Unit, Medication, Cabinet, Age
Delivered as
Live work list; scheduled email
Used for
Resolving discrepancies before they become unexplained losses.

Documentation follow-ups

For nurse managers and diversion specialists

Late or missing administration and waste documentation sent to units, and whether follow-up is complete.

Break down by
Unit, Issue type, Status
Delivered as
Live work list; scheduled email
Used for
Closing documentation gaps on each unit.

Program

Flag outcomes

For diversion committee

Flags raised, closed as explained, sent for unit follow-up and escalated to cases, by rule and period.

Break down by
Rule or measure, Unit, Outcome, Period
Delivered as
Live dashboard; PDF for committee packs
Used for
Seeing which rules lead to useful reviews and which need tuning.

Unit and medication patterns

For pharmacy director and nursing leadership

Waste, override and documentation patterns by unit, medication and shift, without individual names.

Break down by
Unit, Medication, Shift, Period
Delivered as
Live dashboard; CSV export
Used for
Finding process problems such as cabinet setup or waste practice that are not about one person.

Case summary

For diversion committee

Open and closed cases with stage, outcome and follow-up actions, with names shown only to roles allowed to see them.

Break down by
Stage, Outcome, Unit, Period
Delivered as
Live view; PDF for committee packs
Used for
Overseeing investigations and their follow-up.

Monitoring plans

For diversion specialists and human resources partners

Clinicians under a monitoring plan, the reviews scheduled and completed, and results.

Break down by
Plan status, Review due, Unit
Delivered as
Live work list
Used for
Making sure agreed monitoring happens as planned.

Regulatory and audit

Loss reporting log

For compliance officer and DEA registrant

Theft or significant loss information prepared, approved and recorded as submitted by your registrant, with the case it came from.

Break down by
Registration, Status, Date
Delivered as
Live view; PDF and CSV export
Used for
Showing that reportable losses were identified and handled.

Rule and threshold history

For diversion committee and auditors

Every change to a rule, measure or threshold, with who proposed and approved it and when it took effect.

Break down by
Rule, Change date, Approver
Delivered as
Live view; PDF and CSV export
Used for
Evidencing that monitoring was set and changed deliberately.

Access to flags and cases

For compliance and privacy officers

Who viewed which flags and cases, from which role and when.

Break down by
User, Role, Record, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Making sure investigation records are seen only by the people who should see them.

Audit trail extract

For internal audit

Every action on a selected flag, case or period, including decisions, exports and approvals.

Break down by
Record, User, Action, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Evidence for audits and inspections without assembling it by hand.

Exports, access and evidence

  • Every report can be exported to CSV, and summary and evidence reports to PDF. Reports can be scheduled to arrive by email for the people entitled to see them.
  • Program reports show units, medications and shifts without individual names by default; named detail appears only for roles allowed to see it.
  • Aggregate program data is available through the Moraph Work API for reporting alongside your pharmacy and quality data, with restricted case detail excluded unless you choose otherwise.
  • Reports respect each viewer's role: nurse managers see their units' follow-ups, and only people named on a case see its detail.
  • Regulatory and audit reports can be run as of a past date and give the same result each time. Running and exporting a report is itself recorded in the audit trail.

Deployment

Where and how it runs

Moraph cloud

Hosted and operated by Moraph in the United States region, with interfaces to your cabinet, EHR and scheduling systems.

Dedicated environment

A single-tenant environment for health systems whose policies require isolation, scoped in the proposal.

Health system deployment

One deployment across several hospitals, so clinicians who work at more than one site are seen in full, with each site's team seeing its own work.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Data connections

We connect your dispensing cabinet, EHR, inventory and scheduling data and check that removals link to administrations. We need contacts from pharmacy informatics and each system's team.

Unit and peer groups

Units, cabinets and peer groups are mapped so clinicians are compared with peers who do similar work.

Rules and measures

Rules, measures and thresholds are configured from your diversion policy and approved by your diversion committee.

Historical review

Rules are run against historical data and results reviewed with your diversion team before go-live, so thresholds fit your units.

Case workflow and access

Case stages, who may be named on cases, committee approvals and human resources involvement are set to match your policies.

Training and go-live

Diversion specialists, pharmacists, nurse managers and committee members are trained on their own workflows, including how to treat a flag fairly.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • A flag is a statistical or rule-based signal, not evidence of diversion. Your team reviews each flag and decides what it means.
  • Analysis depends on complete and timely data from dispensing cabinets, the EHR and scheduling systems. Gaps in any of them reduce what can be detected.
  • It does not submit DEA Form 106 or any other report. Your DEA registrant reviews, approves and submits reports through the DEA's own channels.
  • It does not make employment, licensing board or law enforcement decisions or referrals; those follow your policies and are made by your staff.
  • It is not a dispensing cabinet system or an inventory system, and it does not control access to medications.
  • Diversion that leaves no trace in the connected data, such as tampering with a vial after a documented administration, may not be detected.
  • Drug testing, security camera review and other investigation steps are recorded in the case but carried out with your own processes and systems.
  • It is designed for US controlled substance requirements; rules in other countries are not included.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Load a sample of your own de-identified cabinet and administration data and check how many removals link correctly
  2. Review a past case your team investigated and see whether the pattern would have been flagged, and when
  3. Ask a pharmacist reviewer whether each flag's reasons are clear enough to act on
  4. Confirm that nurse managers cannot see flags or cases
  5. Walk through a case from flag to committee decision and review what is recorded
  6. Test a threshold change against historical data and review the approval record it produces

Questions

Frequently asked questions

Does a flag mean someone is diverting?

No. A flag means a clinician's handling differs from peers or meets a rule your team set. Most flags have an explanation, such as patient mix, and your reviewers record it.

Does it use artificial intelligence?

Statistical models score unusual patterns alongside plain rules, and every score is shown with its reasons. The product proposes what to review; your staff decide what it means and what happens next.

Can it file our DEA Form 106?

No. It gathers the information from the case for your DEA registrant, who reviews, approves and submits the report through the DEA's own channels.

Who can see an investigation?

Only the people named on the case and roles you grant, such as committee members for summaries. Nurse managers do not see flags or know whether a case exists.

How is it priced?

As a subscription, usually measured by the number of facilities or dispensing cabinets, with implementation charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate Pharmacy Diversion Monitor

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Pharmacy Diversion Monitor guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Pharmacy Diversion Monitor support guide.

Related products