1 / 49

heartbase An Evolution of SIR Functionality by Nick Gawrit

heartbase An Evolution of SIR Functionality by Nick Gawrit. Overview. In this presentation, we will explore how SIR and industry requirements have changed over the years and how this has impacted the heartbase application. Overview. Key Points of Focus. PQL enhancements

bianca
Download Presentation

heartbase An Evolution of SIR Functionality by Nick Gawrit

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. heartbaseAn Evolution of SIR Functionalityby Nick Gawrit

  2. Overview In this presentation, we will explore how SIR and industry requirements have changed over the years and how this has impacted the heartbase application. heartbase presentation SIR Conference 2005

  3. Overview Key Points of Focus • PQL enhancements • Secondary indices • Datavisor’s screen painter • Registry and Government requirements • Overall impact of these on the heartbase data model. heartbase presentation SIR Conference 2005

  4. Version Migration • heartbase has successfully migrated to four new versions of SIR over the past 12 years, including SIR386, SIR40, SIR2000, and SIR2002. • Version changes have allowed heartbase to migrate from a DEC VAX platform to Windows 2003 (and all the versions in between) creating a highly robustdatabase application. heartbase presentation SIR Conference 2005

  5. Migration Trying to get somewhere better… • That has been our experience with SIR. • Each version better than the next, with many changes from the time Alpha/Beta is done until we complete our mission. heartbase presentation SIR Conference 2005

  6. Migration Visual Effects • Character Based -> • Windows OS with character screens -> • GUI screens  • improved GUI interaction. heartbase presentation SIR Conference 2005

  7. Migration Software Versions • 386 to 4.0 • 4.0 to SIR2000 (also VAX and UNIX migration to SIR2000) • SIR2000 to SIR2002 • SIR2002 to SIRXS heartbase presentation SIR Conference 2005

  8. Migration How to Migrate to a New Version • Unload/Delete/Reload • Database Export heartbase presentation SIR Conference 2005

  9. Migration Comment Everything worked perfectly and preserved the deep robust history of the product. heartbase presentation SIR Conference 2005

  10. PQL Enhancements PQL has been a mainstay of the SIR software product. We have used it for virtually all of the heartbase application development. We will explore some of the commands that have been added and how they affect heartbase. heartbase presentation SIR Conference 2005

  11. PQL Enhancements New commands we use focus on Visual PQL • DISPLAY infobox • DISPLAY YESNOBOX • DISPLAY CANCELBOX • CURDIR(0) • APPDIR(0) • DIALOGS • BUTTONS, check boxes, edit boxes, etc • Getitxt, etc • EDITFILE • PQL ESCAPE heartbase presentation SIR Conference 2005

  12. PQL Enhancements Affect on heartbase • Character Based Event Manager heartbase presentation SIR Conference 2005

  13. PQL Enhancements Affect on heartbase • Initial GUI looking event manager heartbase presentation SIR Conference 2005

  14. PQL Enhancements Affect on heartbase • Version 2 GUI event manager heartbase presentation SIR Conference 2005

  15. PQL Enhancements Old Command Consistency amongst versions PQL Code 1992 RETRIEVAL PROCESS CASES PROCESS REC CATH GET VARS ALL WRITE ALL END REC END CASE END RETRIEVAL PQL Code 1999 RETRIEVAL PROCESS CASES PROCESS REC CATH GET VARS ALL WRITE ALL END REC END CASE END RETREIVAL PQL Code 2005 RETRIEVAL PROCESS CASES PROCESS REC CATH GET VARS ALL WRITE ALL END REC END CASE END RETRIEVAL = =

  16. PQL Enhancements Comment PQL is a very powerful tool that allowed us to evolve from a character based set programming language to a visually pleasing programming language without sacrificing the knowledge base we built while learning the product. heartbase presentation SIR Conference 2005

  17. Secondary Indices Alternate lookup techniques for SIR were only available if you programmed them yourself. We will look at the old methods we used for lookups and then show how this code has changed given the new Secondary index features in SIR. heartbase presentation SIR Conference 2005

  18. Secondary Indices Case Zero • Issues/Problems • Synchronization • Locking case zero impacts • Programming required for lookups and searches • Record type requirements heartbase presentation SIR Conference 2005

  19. Secondary Indices Implementation of Secondary Indices • How to use it • Initial usage had its problems • Where we are at today heartbase presentation SIR Conference 2005

  20. Secondary Indices Implementation of Secondary Indices • How to use it • Go to Database on Main Menu and create a secondary index • Create a PQL program to create the index heartbase presentation SIR Conference 2005

  21. Secondary Indices Implementation of Secondary Indices • Initial usage had its problems • Index Corruption • Problems accessing with Master heartbase presentation SIR Conference 2005

  22. Secondary Indices Implementation of Secondary Indices • Where we are at today • Replaced 5 Record Types so far • Allowed access to data that would have required the addition of at least 5 more record types. • Eliminated about 25% of PQL event management code. heartbase presentation SIR Conference 2005

  23. Secondary Indices Comments The implementation of secondary indices gave a much needed boost to make SIR a more mainstream product. Logical case structure, underlying relational structure, along with the new secondary indices gave SIR the ability to compete more effectively with other database software. heartbase presentation SIR Conference 2005

  24. DataVisor Screen Painter DVPainter is a data entry screen application development tool designed to work with SIR databases. With DVPainter, users design the content, appearance and behavior of their data entry screens. heartbase presentation SIR Conference 2005

  25. DataVisor Screen Painter Evolution of Data Presentation • Windows 3.11 started the change from a character based format to a graphical based screen format. • Industry impacts and perceptions of data presentation. • Graphical (GOOD) vs. Character (BAD) heartbase presentation SIR Conference 2005

  26. DataVisor Screen Painter Screen Painting by Tom Tom Shriver invented the first screen painter (character based.) heartbase presentation SIR Conference 2005

  27. Registry/Government Requirements The Painter • Each logical view is painted independently • Trigger mechanisms are version independent • Screen Descriptions and painter functionality control what gets displayed. heartbase presentation SIR Conference 2005

  28. DataVisor Screen Painter Screen Painter 1- Character Based • Exit points • No mouse control heartbase presentation SIR Conference 2005

  29. DataVisor Screen Painter Screen Painter 2 – Graphical based in SIR2000 • Exit points • Mouse control heartbase presentation SIR Conference 2005

  30. DataVisor Screen Painter Screen Painter 3- Graphical based and more • Graphical Buttons • Exit points • Mouse control heartbase presentation SIR Conference 2005

  31. Registry/Government Requirements Reporting registries and the government dictate changes required in heartbase. In this section we will view a concept used by heartbase called “filter views.” heartbase presentation SIR Conference 2005

  32. Registry/Government Requirements Outside factors that influence heartbase • American College of Cardiology • Society of Thoracic Surgeons • Anthem • Oryx (JCAHO) • CCORP • Get with the Guidelines • Leapfrog heartbase presentation SIR Conference 2005

  33. Registry/Government Requirements Problem How to present data when many registries require the same data, different data and have multiple versions of their datasets active? heartbase presentation SIR Conference 2005

  34. Registry/Government Requirements Filter Views Filter views allow users to have logical representation of their data in whatever way is needed. Recently, we have had to migrate from ACC version 2.0c to version 3.04, while allowing users to access their data and to harvest their data from either version. heartbase presentation SIR Conference 2005

  35. Registry/Government Requirements Possible Solutions • Create a new database for each version • Add all the new data points to the existing old application • Create a way to logically see the data points for each version in one database. heartbase presentation SIR Conference 2005

  36. Registry/Government Requirements Create a new version for each database • Easy to do • No problem with data definition overlap • No longitudinal history in the database • Data replication • Difficult reporting due to 2 databases. heartbase presentation SIR Conference 2005

  37. Registry/Government Requirements Add all the new data points to the existing old application • Easy to do for changing data points • Difficult to interpret underlying relational DB model changes • Confusing to users. • Difficult to enforce edits, such as parent/child relationship • Appearance of similar definition fields on the same screen that are different. heartbase presentation SIR Conference 2005

  38. Registry/Government Requirements Create a way to logically see the data points for each version in one database. • More PQL programming required than the other solutions • Easy to present different models in effect • Easy for users to comprehend • Easy to enforce parent/child relationships • Easy to move same data from one view to the next • Maintain all longitudinal history heartbase presentation SIR Conference 2005

  39. Registry/Government Requirements How do filter views work? • The Event Manager • The Painter heartbase presentation SIR Conference 2005

  40. Registry/Government Requirements The Event Manager • Allows a way to navigate the relational database using folder concepts. • Links various PQL subroutines together. • Utilizes Secondary Indices • Manages all manual data collection, including add/change/delete heartbase presentation SIR Conference 2005

  41. Registry/Government Requirements heartbase Event Manager heartbase presentation SIR Conference 2005

  42. Registry/Government Requirements heartbase ACC Hosp View heartbase presentation SIR Conference 2005

  43. Registry/Government Requirements heartbase STS Hosp View heartbase presentation SIR Conference 2005

  44. Registry/Government Requirements Comment One thing is constant, Change. When changes occur, the result is data dilemmas. What do you do with old data and new data. What do you do with definition changes? How do users handle the transition period? heartbase presentation SIR Conference 2005

  45. Data Model Changes Given all the changes above, how has the heartbase data model changed? The heartbase data model has had the need to evolve with changing demands, features of SIR, regulatory changes, and user input. Let’s take a quick look on how the data model has evolved since 1992. heartbase presentation SIR Conference 2005

  46. Data Model Changes heartbase Data Model heartbase presentation SIR Conference 2005

  47. Data Model Changes Data Model Considerations • Keys (Case and SORTIDs) • Design with the future in mind • Sorting out like types of information • Speed issues • To normalize or not normalize (types of users affect this thought) heartbase presentation SIR Conference 2005

  48. Data Model Changes Impacts on data model • Reporting and data presentation needs • Flattening out of relational structures in more than one format • Secondary Indices • Case Zero reliance reduction • Government/Regulatory Changes • More detailed oriented data capture • Definition consolidation and separation heartbase presentation SIR Conference 2005

  49. The heartbase Team heartbase presentation SIR Conference 2005

More Related