He Pharmacist Care Plan Generator

Problem Solved

Clinical pharmacy care often requires turning a diagnosis, medication timeline, monitoring forms, and post-discharge follow-up into a reviewable document. Manual drafting can miss guideline differences, PC-01 through PC-10 form fields, and the handoffs between pre-admission, inpatient, and post-discharge stages. This skill generates a structured pharmaceutical-care package for a named clinical condition, keeping templates, source attribution, and stage planning consistent.

How It Works

Given a disease name, optional ICD-10 code, department, standard length of stay, and clinical guidelines, it prioritizes user-provided sources first, then built-in templates, and finally web search of authoritative references. When multiple guidelines are supplied, it compares key decisions, ranks sources by national standard > society guideline > expert consensus, and records conflicts with source labels. Outputs include an HTML care plan, a separate HTML pathway timeline, structured JSON forms and monitoring items, an XML template, and a book-style chapter document. Long-course conditions expand the timeline into pre-admission, inpatient, and post-discharge phases, covering medication reconciliation, prescription review, discharge education, and follow-up records.

Boundaries

It is useful for drafting care pathways, teaching templates, or organizing disease-specific pharmacy workflows, but it does not replace pharmacist review, clinical decision-making, or individualized patient management. Patient fields remain placeholders and must not be filled with real chart data. When guidelines conflict or special populations are involved, verify against the current product label, local protocol, and latest institutional guidance.