Pharmacy Policy Analysis

Problem to solve

Pharmacy policy documents are often scattered across government portals, WeChat accounts, and academic search channels, while terms such as “must,” “should,” and “recommended” can easily become management requirements without a clear source, threshold, or owner. This skill turns policy retrieval, clause breakdown, indicator design, and operational documentation into a repeatable workflow for pharmacy compliance, quality management, and information-system requirements analysis.

How it works

• Policy retrieval and capture: Searches government websites, Baidu Academic/Baidu Government, Doc88, and WeChat articles, saves snapshots, and maintains an index with policy name, document number, issuing body, effective date, and local file path.
• Structured analysis: Uses the people, machines, materials, methods, and environment matrix to break down staffing qualifications, equipment and system requirements, drug handling, legal basis, and site/IT conditions, then maps them to pre-event, in-process, and post-event management stages.
• Indicator and document generation: Produces indicator tables grounded in policy clauses, marking source, mandatory or recommended nature, and threshold basis; can export Excel policy tables, HTML analysis reports, Word notices, PPT briefings, and controlled-drug registration templates for receipt, dispensing, inventory, destruction, and dual-control checks.

Boundaries

The skill produces analysis drafts and document templates, not legal conclusions. Regulator interpretations, interface standards, security compliance, and operational decisions still require manual review; significant decisions should be marked as needing further validation.