• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Developing a Quality Audit Report for General Practice Prescribing for Hypertension: Methodology
 

Developing a Quality Audit Report for General Practice Prescribing for Hypertension: Methodology

on

  • 2,704 views

Prof Jim Warren

Prof Jim Warren
National Institute for Health Innovation, The University of Auckland

With Rekha Gaikwad, Thusitha Mabotuwana, John Kennelly, Timothy Kenealy

Statistics

Views

Total Views
2,704
Views on SlideShare
2,698
Embed Views
6

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 6

http://www.slideshare.net 5
http://www.fachak.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Developing a Quality Audit Report for General Practice Prescribing for Hypertension: Methodology Developing a Quality Audit Report for General Practice Prescribing for Hypertension: Methodology Presentation Transcript

  • Developing a Quality Audit Report for General Practice Prescribing for Hypertension: Methodology Prof Jim Warren National Institute for Health Innovation, The University of Auckland With Rekha Gaikwad, Thusitha Mabotuwana, John Kennelly, Timothy Kenealy
  • ‘ Business Intelligence’
    • Or we can use some other terms
      • Quality assurance
      • Continuous process improvement
      • Data analysis
      • Data mining
    • Basically, finding out what’s going on by looking at your computer data (and using that as a basis for change to improve things)
    • Great opportunity in NZ (and Aussie) General Practice because we’re world leaders in uptake of General Practice computing
      • Reliable prescriptions and lab results, improving problem classifications and observations
  • Minlaton
    • I’ve been looking at clinical data entry and patterns in GP data since ’89, but recent context starts with…
    • Minlaton Medical Centre
      • Caters to a combination of farmers and retirees
      • Two full-time GPs in 2003-2004 (now three)
      • Worked with the GPs to introspect with them on their antihypertensive prescribing
      • Using the model of their practice as reflected in their Practice Management System (PMS) data
      • With the goal of identifying areas to improve
  • Tracing individual ‘therapeutic paths’ Nb. Chose these because they’re confounding… most individuals have simple and sensible patterns
  • ‘ High specificity’ alerts
    • It’s a problem if the software is ‘trigger happy’
      • GPs learn to ignore a plethora of naïve alerts
    • Used iterative review of actual therapeutic paths and guidelines to devise a system of alerts
      • Aim: to have alerts that are often a cause for action, and virtually always viewed as at least ‘having merit’
    • ALERT
    • Alert date: 19 Jan 2005
    • Beta-blocker prescribed after Asthma Dx and regular Asthma
    • Medications
      • Beta-blocker on 19-Jan-05
      • Asthma Dx on 25-Nov-99
      • Tested by having the GPs blindly critique a sample of cases (and then revealed the alerts – which were on half the cases – and got their feedback)
      • 87%-96% specificity
  • So why doesn’t everybody make sense?
    • A range of common stories (from Minlaton)
      • Known non-compliance
      • Historical arc of patient has taken them to an unusual (but sometimes acceptable) therapeutic mix (it’s tolerated, so don’t change it)
      • Extra medication supply through a specialist (in Adelaide, in the Minlaton case) or sample packs
      • Historically coded problems may not turn out to be all that severe
    • But also, it’s really hard for GP to see all medication persistence and all indicating and contraindicating problems for a substantially chronic/complex patient
  • Healthwest Fono
    • Largely Pacific practice in West Auckland
    • Looking at development of criteria for a quarterly quality audit report around antihypertensive prescribing
      • Provide baseline for quality improvement
      • Identify specific cases for recall or adjustment at next visit
    • Goal is to reduce CVD events (e.g., stroke, MI), and also renal protection
  • Criteria
    • For a 3-month Evaluation Period some quality improvement opportunities on patients classified with hypertension are indicated by:
      • A lapse in anti-hypertensive therapy of >30 days and the lapse extends into the Evaluation Period
      • Classified with diabetes mellitus and not on ACEi/ARB at any time during Evaluation Period
      • On thiazide(s) and with serum uric acid > 0.42mmo/l at any time during Evaluation Period and not on Allopurinol or Colchicine
  • Beyond the normal Query Builder
    • These queries are hard to get right with conventional technology
    • Mostly we have SQL (structured query language)
      • An ISO standard supported by most database management systems with only minor variations)
      • SQL has us SELECT <what fields we want> FROM <what tables hold them> WHERE <a certain logical condition applies>
    • Great for most things
      • We can handle a fixed time range with the WHERE clause (date>=begin and date<=end)
      • But harder for discussing time intervals based on data – have to compare rows in a table with other rows in the same table
        • This is necessary to query medication persistence (comparing date of one prescription to date of another prescription)
  • Temporal Queries
    • Explosion of Options
      • It is impractical to aspire to a “complete” set of statistics that describe every temporal nuance of the relationships amongst all relevant clinical concepts
  • ‘ Ontology’ management
    • Significant challenges in capturing all necessary codes
      • Problem codes (e.g., all relevant codings of diabetes; maybe excluding gestational)
      • Medications (all agents in each therapeutic category, at the desired granularity, possibly not the eye drops)
    • These are problems of ontology – the relationships among concepts (esp. subsumption of one group of concepts under another)
    • Will be aided significantly if we have widespread uptake of SNOMED
      • SNOMED can relate every medical term into a network of semantic relationships
      • But still will require technology integration (to use this huge network) and careful query quality assurance (e.g., “hypertension” is part of the term “pulmonary hypertension”)
  • HealthWest Fono Findings: an Example Case
    • Agree
    • CVR 20%
    • BP too high
    • Needs ACE
    Yes No Yes 1. A lapse in AHT of >30 days during the EP or the lapse extends into the EP 2. A period of >180 days with no BP measurements extending into the EP Practice Assessment The data from the PMS satisfactorily explains the therapy. The therapy is optimized, or the process of seeking optimized treatment is satisfactory The therapy is free of clinically significant contraindications and interactions. Criteria Assessment
  • Performance of Criteria Ability to detect positive cases Meaning of a negative result Criteria Assessment Suboptimal therapy (+) Optimal therapy (-) Sensitivity = 76% Specificity = 70% Positive Predictive Value = 65% Negative Predictive Value = 80% 13 4 Suboptimal therapy (+) 7 16 Optimal therapy (-) Practice Assessment
  • Results Summary
    • Adherence issues dominate
      • Forming basis of an HRC application
      • Want to proactively remind patients with poor past persistence, particularly to get them back to tune their therapy
    • A lot of thought-provoking cases
      • Questions around gout, ACEi, thiazides, eGFR, allopurinol that I won’t attempt to get right here
      • Seems to be valuable for finding cases on the boundaries of the available evidence
      • Possibly good for raising further clinical research questions (highlighting, and quantifying, substantial groups where the evidence is ambiguous)
  • Building a temporal query support system
    • The types of temporal queries needed fit some very specific categories
      • Missing a compellingly indicated treatment (or presence of contra- indication)
      • Lack of medication persistence
      • Observations persistently outside of goal
      • Lack of monitoring observations
    • Aim is to develop an easy to use interface tailored to the required concepts
      • And that maps the relevant high-level concepts to the specific (and validated) query schemas and detailed sets of problem and drug codes
  • Adherence
    • Obviously, this is just one step on an adherence pathway
    Your Prescribing Other docs’ Prescribing Dispensing Reliable Consumption It’s but one step, but it is along the road to more reliable chronic disease management outcomes
  • Thanks, questions?
    • Prof Jim Warren – jim@cs.auckland.ac.nz
    ??? The Minlaton work: Gadzhanova, S., Iankov, I., Warren, J., Stanek, J., Misan, G., Baig, Z. & Ponte, L., “Developing High-Specificity Anti-hypertensive Alerts by Therapeutic State Analysis of Electronic Prescribing Records,” Journal of the American Medical Informatics Association , Vol 14, No 1, Jan/Feb 2007, pp. 100-109