Part 2 PDMP SUD-medication scope

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

Live 42 CFR 2.36 refers to SUD medication prescribed or dispensed by the Part 2 program. It does not create a route for every medication known to the program or for an entire treatment record. The report must also be required by applicable state law and preceded by section 2.31 consent.

Verify the program-originated event

Current 42 CFR 2.36 ties the report to SUD medication prescribed or dispensed by the Part 2 program. Preserve medication identity, form, strength, dosage, units, quantity, event type, date, responsible professional, source record, corrections, and state-field mapping.

Use an approved payload

Generate the report from allowlisted fields required by the current state rule and supported by consent. Inspect the transmitted message, including hidden metadata, default segments, attachments, free text, copied history, and vendor-added fields.

Consent follows the actual information

The § 2.31 consent should meaningfully describe the information and recipient. A consent mentioning medication does not automatically support every field a vendor integration can send. Reconcile state requirements, consent scope, and the payload.

Prove the program-originated event

Link the report to a prescribing or dispensing event by the Part 2 program. Preserve medication identity, code, form, strength, dosage, quantity, units, days' supply where applicable, event type, authorizing professional, site, timestamps, status, source, and correction history. Distinguish an order from a dispensed fill or administered dose.

Exclude outside prescriptions, patient-reported histories, claim records, planned medications, canceled orders, and copied lists unless the rule and verified facts independently support them.

Classify SUD medication and state scope

Use qualified clinical, pharmacy, Part 2, and state-law review to determine which medication and event the route covers. Map the current state PDMP requirement, controlled-substance or product rules, exemptions, and technical codes to the program source. Preserve rule and code-set versions.

Do not let an EHR category or vendor drug flag settle the legal and clinical classification without review. Monitor new products, formulations, codes, and state changes.

Build the narrow payload

Create an allowlist of state-required fields that are supported by the source event and consent. Map every patient, prescriber, dispenser, medication, date, quantity, and transaction field. Block counseling notes, diagnoses, unrelated medications, payer history, attachments, free text, and hidden metadata.

Inspect source queries, interface transformations, vendor-added fields, logs, error files, retries, and the actual PDMP message. Test multiple medications, reversals, partial fills, corrections, unusual units, and missing values.

Preserve clinical meaning

Keep medication code, name, formulation, strength, dosage, quantity, unit, prescribed or dispensed status, and relevant date aligned. Prevent unit conversion, truncation, stale status, duplicate event, and old-value errors. Route ambiguous records to a qualified clinician or pharmacist rather than inferring a regimen.

When a source record changes, determine whether the PDMP needs a correction or reversal and link every version and acknowledgment.

Reconcile law, consent, and data

For each report, show the state requirement, section 2.31 consent, applicable recipient, program event, approved fields, secure route, transmission, response, and correction status. If a required state field falls outside the signed description or reliable source, hold and escalate rather than broadening the report silently.

Audit successful, rejected, corrected, late, held, and excluded events for both overdisclosure and clinically misleading omission. Review mappings after formulary, code-set, EHR, vendor, and state specification changes.

Create a clinical validation set covering common products, new formulations, compound or combination records, partial dispensing, dose changes, canceled orders, and corrected administrations. Compare the source display, outbound code, PDMP acknowledgment, and later query display where access is authorized. Investigate any transformation that makes two different states look the same. This validation protects both privacy and prescribing safety because an overly narrow field map can misstate the allowed medication facts.

Example

Twenty-three outbound messages are sampled. Twenty contain only state-required, consented fields from a verified program prescribing or dispensing event; three attach a medication history. Payload compliance is 20 of 23 messages.

SUD-medication payload checklist

• link every report to a verified program prescribing or dispensing event;
• classify the SUD medication and current state-reporting requirement;
• map only required, consented fields through source, interface, vendor, and PDMP;
• preserve medication identity, formulation, units, status, dates, and corrections;
• block unrelated records, narrative, hidden fields, and stale values; and
• reconcile law, consent, payload, acknowledgments, rejections, and reversals.

The scope is both legally narrow and clinically exact. A minimal report must still preserve the meaning of each allowed medication field.