1 / 38

IHS Palliative Care Project

IHS Palliative Care Project. A collaboration to develop palliative care metrics across the care continuum. Objectives. Describe the PC Metric Report Discuss the value of metrics Identify the outcome measurement system developed by the Iowa Health System PC Affinity Group

lan
Download Presentation

IHS Palliative Care Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IHS Palliative Care Project A collaboration to develop palliative care metrics across the care continuum

  2. Objectives • Describe the PC Metric Report • Discuss the value of metrics • Identify the outcome measurement system developed by the Iowa Health System PC Affinity Group • Identify next steps for PC Metrics expansion

  3. Inpatient Palliative Care Metrics • Consultation Volume • Palliative Care Consultation Rate • Length of Stay • Length of Stay Outliers • Cost Savings on Impact Days • Billable Revenue

  4. Consultation Volume

  5. Consultation Volume

  6. Consultation Volume

  7. Consultation Rate

  8. Length of Stay

  9. Length of Stay

  10. Length of Stay

  11. Length of Stay

  12. Cost Savings on Impact Days

  13. Cost Savings on Impact Days

  14. Cost Savings on Impact Days

  15. Billable Revenue

  16. Billable Revenue

  17. Outpatient Palliative Care Metrics • Consultation Volume • Discharge Distribution/DC Reason • Readmission to Acute Inpatient Care • Referred from IPPC • Readmission to Acute Inpatient Care • Without IPPC

  18. Getting started • Created the Palliative Care Affinity Group which includes inpatient and outpatient providers. • Identified basic standards for PC programs • Definition • Interdisciplinary Team • Policies (based on National Consensus Project: Clinical Practice Guidelines)

  19. PC Metrics – Why? • Internal quality assessment • External quality assessment (TJC Accreditation, public reporting, value based contracting) • Research/Exploratory Quality Improvement Initiatives

  20. Determining Metrics • Identified PC metrics based on national standards • series of articles in Journal of Palliative Medicine by Dr. David Weissman and Dr. Diane Meier from Center to Advance Palliative Care) • www.capc.org

  21. Metric Domains Operational Does my program have the features required to provide high quality palliative care? What metrics do I need to measure in order to demonstrate my program has these cores features? Clinical Am I improving the clinical care of patients? Symptom assessment scores, psychosocial assessment scores Customer Am I meeting the needs of patients and families? Satisfaction survey data: patient, family, referring clinician Financial Is my program fiscally responsible?

  22. Project Manager • Committee Team • Formal Metric Documents (K. Routson) • Data Development • Finalized Data Elements • Identifying IT Resources • DB Development • Analytics and Reporting • Finalized • Audit Process • Physicians Group (K. Routson)

  23. Project Manager

  24. Live Demonstration http://cpi.ihs.org/valuebasedcontracting/Hospice_PalliativeCare

  25. Project Technology • Two established programs at Cedar Rapids and Des Moines • Two Microsoft Access Databases • One backed by Microsoft Access • One backed by SQL Server • Need for one Statewide Database across the Continuum of Care

  26. Project Technology • Involvement in Metric Development • Consolidation of Databases • Entry screens of one • Overall structure (SQL Server) of the other • Security Issues with Statewide Database

  27. Project Technology • Involvement in Metric Development • Ensure database and entry screens are configured properly • Work through what data needs pulled from other sources versus entered manually

  28. Project Technology • Consolidation of Databases • Entry screens of one and structure of the other • TSI/EPSi Data • Hospitalizations and Costs • Monthly Feed until all EPSi and Epic conversion is complete • Horizons • Outpatient Metrics • Nightly feed • Medical Record Numbers are entered into Horizons for linking

  29. Project Technology • Security Issues • Multiple Affiliates in one database • Both Inpatient and Outpatient in one database • Not an ACE (Affiliated Covered Entity) • Affiliate Personnel was developing and maintaining the database • Need to be able to handle • Addition of affiliates - Peoria Methodist • Partners external to HIS - Hospice of Siouxland

  30. Project Technology • First Iteration • SQL Server data stored on the IHDM SQL Server • Access database in Network folder • Issues • Data stored at one affiliate for multiple affiliates • Additional lock down of Access database wanted

  31. Project Technology • Second Iteration • SQL Server database that is maintained by IT • Access database accessed via Citrix • Utilized Access Runtime via Citrix to limit ability to access design functions • Issues • Support model being worked through as IHS IT to support Database • Need for Reporting Support

  32. Project Technology • Final • SQL Server database that is maintained by IT • Access database accessed via Citrix • Utilized Access Runtime via Citrix to limit ability to access design functions • Patients can be viewed across the continuum • New Analytics Department in IT to support Database • Center for Clinical Transformations (CCT) to support reporting

  33. Report Developmentconvert data and information into knowledge • Translate ‘word’ definitions into technical specifications • Visually present what is happening • Trust and be confident with the results

  34. Report Developmentconvert data and information into knowledge • Data characteristics must be understood – necessary to define exact specifications • Data must be accurate • Data must be complete

  35. Report Developmentconvert data and information into knowledge • Data are linked across tables or files by common fields. • If data are wrong or missing, knowledge is lost.

  36. Report Developmentconvert data and information into knowledge

  37. Report Developmentconvert data and information into knowledge • Provide reports that users can easily run to detect missing or inaccurate data • Report staff run reports or conduct reasonableness check on data • Design review/audit steps earlier, rather than later, in overall process • Automate as much as possible – moving data introduces opportunity for error

  38. Future Plans • Automate metric report so it can be created internal to the system or via the new EDW and BI tools being developed. • Look at alternatives to Access for entry (i.e. IQ4) • Add tabs in PC Report for PC Clinic, PC LTC, and Hospice • Add clinical metrics in 2012 (pain, dyspnea, advanced care planning) • Add customer satisfaction metric (patient/family, referring provider)

More Related