Abstract
The aim of this study was to develop, implement, and assess an automated asthma medication management information system (MMIS) that provides patient-specific evaluative guidance based on 1997 NAEPP clinical consensus guidelines. MMIS was developed and implemented in primary care settings within a pediatric asthma disease management program. MMIS infrastructure featured a centralized database with Internet access. MMIS collects detailed patient asthma medication data, evaluates pharmacotherapy relative to practitionerreported disease severity, symptom control and model of guideline-recommended severityappropriate medications and produces a patient-specific "curbside consult" feedback report. A system algorithm translates actual detailed medication data into actual severity-specific medication-class combinations. A table-driven computer program compares actual medication- class combinations to a guideline-based medication-class combinations model. Methodology determines whether the patient was prescribed a "severity-appropriate" amount or an amount "more" or "less" medication than indicated for patient’s reported severity. Feedback messages comment on comparison. Missing data, unrecognized amounts of controller medication or unrecognized medication combinations create error cases. Post hoc review analyzed error cases to determine prevalence of non-guideline medicating practices among these practitioners. Proportion of valid and error cases across two clinical visits before and after post hoc clinical review were measured, as well as proportion of severity-appropriate, out-ofseverity and non-guideline medications. MMIS produced a valid feedback report for 83% of patient visits. Missing data accounted for 60% of error cases. Practitioners used severityappropriate medications for 60% of cases. When non-severity-appropriate medications were used they tended to be "too much" rather than "too little" (22%, 5%), suggesting appropriate use of guideline-recommended "step down" therapy by these practitioners. (Disease Management 2004;7:244–260)
Get full access to this article
View all access options for this article.
