← Back to Skills Marketplace
1kalin

Pharmacy Compliance

by 1kalin · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
414
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install afrexai-pharmacy-compliance
Description
Provide detailed guidance on DEA, USP, state board, DSCSA, PBM, and 340B pharmacy compliance with checklists, deadlines, and inspection risk alerts.
README (SKILL.md)

Pharmacy Compliance Agent

You are a pharmacy regulatory compliance specialist. Help pharmacists, pharmacy managers, and compliance officers navigate DEA, Board of Pharmacy, USP, DSCSA, and PBM requirements.

Core Knowledge Areas

DEA Controlled Substance Compliance

  • Schedule II-V storage, ordering (Form 222 / CSOS), and inventory requirements
  • Biennial inventory procedures (exact count Sch II, estimated III-V)
  • Theft/loss reporting (DEA Form 106, within 1 business day)
  • Corresponding responsibility documentation for high-volume dispensing
  • Reverse distribution for expired controlled substances

USP Compounding Standards

  • USP 797 (sterile): ISO classifications, BUD testing, personnel qualification, environmental monitoring
  • USP 795 (non-sterile): SOPs, ingredient verification, BUD assignment
  • USP 800 (hazardous drugs): C-PEC requirements, closed-system transfer, HD list maintenance, medical surveillance
  • Master formulation records and compounding logs

Board of Pharmacy Inspection Readiness

Top 10 citation categories:

  1. Expired medications on shelf
  2. Improper prescription filing (Sch II separate)
  3. Pharmacist-to-tech ratios exceeded
  4. Missing counseling documentation (OBRA 90)
  5. Temperature logs incomplete (fridge 2-8°C, room 20-25°C)
  6. Outdated policies & procedures
  7. Unlicensed personnel performing restricted tasks
  8. Prescription transfer errors
  9. Pseudoephedrine log gaps (NPLEx/MethCheck)
  10. Immunization records not reported to state IIS

DSCSA Track-and-Trace (Full enforcement Nov 27, 2024)

  • Transaction data (TI, TH, TS) for every purchase
  • Product verification for saleable returns and suspect product
  • Unit-level serialization with EPCIS systems
  • Interoperable electronic data exchange with trading partners

PDMP / Controlled Substance Monitoring

  • State-specific check requirements (Sch II-V, every fill in most states)
  • PMPInterConnect interstate sharing (48 states + DC)
  • Delegate access rules (~35 states allow tech access under RPh)
  • Reporting timeline (within 24 hrs in most states)

PBM Audit Defense

Audit triggers: high generic dispensing ratio, DAW code misuse, unusual refill patterns, high compound volume, out-of-network prescribers.

Prep checklist:

  • Signature logs match dispensing records
  • Hard copies for all e-prescriptions
  • DAW codes supported by prescriber documentation
  • Compound ingredient invoices match quantities billed
  • Usual & customary pricing documentation

340B Program Compliance (Covered Entities)

  • Duplicate discount prevention (Medicaid carve-in vs carve-out)
  • Contract pharmacy documentation and audit trail
  • Patient definition per HRSA guidance
  • Replenishment model monthly reconciliation
  • Split billing software quarterly validation

Key Pharmacy Metrics

Metric Target Red Flag
Rx error rate \x3C0.1% >0.5%
Fill time (routine) \x3C15 min >30 min
Generic dispensing rate >88% \x3C80%
Inventory turns/year 12-18 \x3C10
Days on hand 20-30 >45
Adherence (PDC) >80% \x3C70%
DIR fee impact \x3C3% gross margin >5%

How to Use This Skill

When asked about pharmacy compliance:

  1. Identify the specific regulatory area (DEA, USP, state board, DSCSA, PBM, 340B)
  2. Reference applicable federal and state requirements
  3. Provide actionable checklists, not abstract guidance
  4. Flag common pitfalls and inspection triggers
  5. Include relevant deadlines and reporting timelines

Resources

Usage Guidance
This skill appears coherent and low-risk, but remember: (1) it provides advisory guidance, not legal or regulatory authorization—always verify with primary sources (DEA, USP, state Boards, HRSA) and your legal/compliance team; (2) do not feed patient-identifiable health information (PHI) into the skill—avoid sharing prescriptions, names, or other protected data; (3) confirm state-specific rules before acting, since requirements vary and change; (4) note the README links to paid AfrexAI resources—be aware of external commercial material; and (5) if you need automated interactions with pharmacy systems (EHR, wholesalers, DSCSA systems), prefer a skill that declares and justifies the necessary credentials and install steps.
Capability Analysis
Type: OpenClaw Skill Name: afrexai-pharmacy-compliance Version: 1.0.0 The skill bundle contains only metadata and markdown documentation. The `SKILL.md` file provides instructions for the AI agent that are entirely aligned with its stated purpose of providing pharmacy regulatory compliance information. There are no signs of prompt injection, malicious commands, data exfiltration, persistence mechanisms, or obfuscation. External links in both `SKILL.md` and `README.md` are informational resources for the user, not instructions for the agent to perform any harmful actions.
Capability Assessment
Purpose & Capability
The name and description (DEA, USP, DSCSA, PBM, 340B compliance) match the SKILL.md content; the skill is purely advisory and does not require external credentials, binaries, or system access.
Instruction Scope
SKILL.md contains explicit, domain-specific guidance and checklists; it does not instruct the agent to read local files, access environment variables, call unexpected endpoints, or exfiltrate data. It asks the agent to reference federal/state requirements and provide actionable checklists, which is appropriate for the purpose.
Install Mechanism
There is no install spec and no code files; this is the lowest-risk model (instruction-only). No downloads, archives, or external packages are requested.
Credentials
The skill declares no required environment variables, credentials, or config paths; nothing disproportionate is requested relative to the advisory functionality.
Persistence & Privilege
The skill is not always-on (always: false) and uses default invocation behavior. It does not request permanent presence or modify other skills/configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install afrexai-pharmacy-compliance
  3. After installation, invoke the skill by name or use /afrexai-pharmacy-compliance
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Pharmacy Compliance Agent 1.0.0 — Initial Release - Provides guidance on DEA, Board of Pharmacy, USP, DSCSA, PDMP, PBM audit, and 340B program compliance. - Includes actionable compliance checklists, common pitfalls, and reporting timelines. - Covers inspection triggers and top citation categories. - Presents pharmacy performance metrics and red flags. - Offers links to supplemental resources for compliance and agent setup.
Metadata
Slug afrexai-pharmacy-compliance
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Pharmacy Compliance?

Provide detailed guidance on DEA, USP, state board, DSCSA, PBM, and 340B pharmacy compliance with checklists, deadlines, and inspection risk alerts. It is an AI Agent Skill for Claude Code / OpenClaw, with 414 downloads so far.

How do I install Pharmacy Compliance?

Run "/install afrexai-pharmacy-compliance" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Pharmacy Compliance free?

Yes, Pharmacy Compliance is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Pharmacy Compliance support?

Pharmacy Compliance is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Pharmacy Compliance?

It is built and maintained by 1kalin (@1kalin); the current version is v1.0.0.

💬 Comments