1. heartbase An Evolution of SIR Functionality by Nick Gawrit

2. heartbase presentation SIR Conference 2005 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.

3. heartbase presentation SIR Conference 2005 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. Overview

4. heartbase presentation SIR Conference 2005 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 robust database application.

5. heartbase presentation SIR Conference 2005 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. Migration

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

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

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

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

10. heartbase presentation SIR Conference 2005 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.

11. heartbase presentation SIR Conference 2005 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 PQL Enhancements

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

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

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

15. PQL Code 1992 RETRIEVAL PROCESS CASES PROCESS REC CATH GET VARS ALL WRITE ALL END REC END CASE END RETRIEVAL Old Command Consistency amongst versions 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 PQL Enhancements ==

16. heartbase presentation SIR Conference 2005 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. PQL Enhancements

17. heartbase presentation SIR Conference 2005 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.

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

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

20. heartbase presentation SIR Conference 2005 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 Secondary Indices

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

22. heartbase presentation SIR Conference 2005 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. Secondary Indices

23. heartbase presentation SIR Conference 2005 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. Secondary Indices

24. heartbase presentation SIR Conference 2005 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.

25. heartbase presentation SIR Conference 2005 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) DataVisor Screen Painter

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

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

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

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

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

31. heartbase presentation SIR Conference 2005 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.”

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

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

34. heartbase presentation SIR Conference 2005 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. Registry/Government Requirements

35. heartbase presentation SIR Conference 2005 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. Registry/Government Requirements

36. heartbase presentation SIR Conference 2005 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. Registry/Government Requirements

37. heartbase presentation SIR Conference 2005 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. Registry/Government Requirements

38. heartbase presentation SIR Conference 2005 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 Registry/Government Requirements

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

40. heartbase presentation SIR Conference 2005 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 Registry/Government Requirements

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

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

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

44. heartbase presentation SIR Conference 2005 One thing is constant, Change. 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? 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? Registry/Government Requirements Comment

45. heartbase presentation SIR Conference 2005 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.

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

47. heartbase presentation SIR Conference 2005  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) Data Model Changes Data Model Considerations

48. heartbase presentation SIR Conference 2005 Impacts on data model  Reporting and data presentation needs oFlattening out of relational structures in more than one format  Secondary Indices oCase Zero reliance reduction  Government/Regulatory Changes oMore detailed oriented data capture oDefinition consolidation and separation Data Model Changes

49. heartbase presentation SIR Conference 2005 The heartbase Team