intelli health ontario the new and improved access to the phpdb n.
Skip this Video
Loading SlideShow in 5 Seconds..
intelli HEALTH ONTARIO : The NEW and IMPROVED Access to the PHPDB* PowerPoint Presentation
Download Presentation
intelli HEALTH ONTARIO : The NEW and IMPROVED Access to the PHPDB*

intelli HEALTH ONTARIO : The NEW and IMPROVED Access to the PHPDB*

1443 Vues Download Presentation
Télécharger la présentation

intelli HEALTH ONTARIO : The NEW and IMPROVED Access to the PHPDB*

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. intelliHEALTH ONTARIO:The NEW and IMPROVED Access to the PHPDB* 2007 APHEO Conference JoAnn Heale ( Health Data & Decision Support Unit, MOHLTC *Provincial Health Planning Database

  2. Recommendations from PHPDB User Survey • Assist external PHPDB users to overcome VPN problems • Develop additional functionality and products to cater to users with different levels of expertise and needs • Improve the format of the PHPDB code tables to make them more easily accessible • Modify the website to make it more user-friendly and up-to-date

  3. Requirements for Future PHPDB Access • Maintain current Hummingbird BI functionality • Customize access to datasets and/or data fields • Assure security/privacy guidelines are met • Provide ‘thin client’ access to the PHPDB • Add enhanced reporting functionality

  4. Web-based Access – no VPN required!

  5. Web link – restricted access

  6. Directory of Information Maps (Table[s])

  7. Red + Grey Tables in PHPDB Red Table in PHPDB Maintain Functionality of Old Access • All tables and almost all data items (attributes) from the PHPDB are available in WRS • Example: Inpatient Discharge IMs

  8. Meet Privacy/Confidentiality Guidelines • No personal identifiers • Chart number • Birth Date • Health number • Unique Record Keys Used as Measures Only • E.g. CIHI Key is not available as a data item but is used as the measure # inpatient discharges • E.g. Encrypted HN is not available as a data item but is used as the measure # patients (HN)

  9. Enhanced functionality for all levels of user…

  10. Enhanced Functionality – Measures Are Created for Users What the User Sees in WRS: D = Distinct Measure HN = patient with health number

  11. How the Measures were Calculated • # Ext Causes • Count on hlth_serv_type field (always IP) from External Cause table • There can be multiple (or no) external causes per discharge • # Ext C Dschg (D) • Count distinct on cihi_key from External Cause table • Distinct measures cannot be totaled across cells and can only be used in list reports • # Dschg (D) • Count distinct on cihi_key from Inpatient Discharge (red) table • Requires outer join between IP Discharge & External Cause • # Pts with Ext C (D-HN) • Count distinct on identification_num (HN) from External Cause table – where identification_cd = ‘H’ Note: WRS allows multiple distinct measures in one report (list only) – Hummingbird allowed only one per query

  12. Enhanced functionality – no need to link to code tables…

  13. Enhanced functionality – distinct measures can only be used in lists – no totals

  14. Enhanced functionality – formatted crosstab reports

  15. All measures in all information maps have been tested (by Ian Taylor) against the PHPDB

  16. New Products • Summary Information Maps • Based on cubes built from 6-7 most-frequently queried dimensions • Very fast query time, e.g. medical services query takes seconds-minutes • Drill down or expand dimensions • Standard reports built from each Summary IM • Special Reports • SAS datasets created to join record level and aggregate datasets • Available for pilot group – live birth rates, death rates, death rankings by leading cause • In creating rates datasets, some records have to be excluded (e.g., unknown age, sex, public health unit)

  17. Example of Summary Information Map

  18. Example of Special Reports Developed Death Rates Report Leading Causes of Death Report

  19. Death Rates Report: Nine Sections

  20. Sample Report View for Death Rates Report

  21. User Can Select and View Pages

  22. Most Report Sections Include Graphs

  23. You can quickly sort, e.g. by death rate

  24. … or by number of deaths

  25. You can filter on any data item, e.g. age group

  26. … and make comparisons between PHUs

  27. Footers include detailed information on source data

  28. Leading Cause of Death Report: Six Sections

  29. Sample: Lead Cause Rank Under 20 Yr

  30. User can select from prompted items

  31. User can refine report to explore other issues

  32. User can sort/rank report on any data item

  33. Other Features of Reporting Tool(available for users of the Special Reports) • Customize for agency’s needs and save to ‘My Folders’ • Add ‘conditional highlighting’ to any report • E.g., any cell with fewer than 5 displays as ‘NR’ • Create additional custom measures • E.g., Deaths < 20 Yr, Rank < 20 Yr in Leading Cause of Death Report • Rank and display any data item, • E.g. display leading causes of death that account for 75% of all deaths • Filter any data item • Use available filters or create custom filters

  34. Next Steps • Pilot group (20 users) trained week of Oct. 22 2007 • PHPDB Advisory Group reinstated • Pilot group tests Web Report Studio for one month • Pilot group & Advisory Group provide feedback to development team • Product revisions in December-January 2008 • Roll-out to existing users February-April 2008 • Hummingbird BI phased out to coincide with roll-out

  35. Questions?

  36. User-friendly graphing options

  37. User friendly prompt lists have been created

  38. Sample output- can edit report to improve formatting