113 Clinical Flowsheets Application Overview

1. #113 Clinical Flowsheets Application Overview Faculty Jeremy AckleyDan PetitBrian Juergensmeyer August 11, 2010

2. Class Agenda

3. Team Overview Anne RegaAnne Rega

4. Project Scope

5. Project Scope (cont.) Clinical Connectivity system defined Clinical Flowsheets Application (User Interface) Clinical Console Application (Administrator User Interface) CliO Back-end Service (System Framework) CP Gateway (HL7 Message Processing) ICU Instruments, CIS (HL7 Interface)

6. Project Scope (cont.) The system will share data with Clinical Reminders Index Vitals Lite CPRS HDR 3rd Party Vendors, COTS Products

7. Project Scope (cont.) The system will Provide a common interface with variety of instruments in a clinical setting Allow secure access to ICU patient data from any networked VA workstation Provide a customizable, flowsheet-based user interface to enter, view, edit patient data Provide reporting functionality Provide ADT feed to minimize data re-entry Reporting functionality (standard: End of Shift, Transfer, PMI) and custom. Reporting functionality (standard: End of Shift, Transfer, PMI) and custom.

8. Project Scope (cont.)- Recognizing the Need - Update with recent poll results once they�re done.Update with recent poll results once they�re done.

9. Project Scope (cont.)- Recognizing the Need - Update with recent poll results once they�re done.Update with recent poll results once they�re done.

10. Project Objectives and Business Benefits

11. Project Objectives and Business Benefits Business Benefits Provide mechanism for data standardization for internal and external systems Link disparate vendor ICU systems to VistA Allow observed data to be stored in VA central database Offer automated process for paper-based VA ICU sites Allow observed data to be viewed, edited, analyzed over an unlimited time-span Provide improved data security Provide user friendly access to data Reduce errors in manual data entry Promote efficient, safe clinical decisions and care Data standardization � Jeremy will touch onData standardization � Jeremy will touch on

12. Target Audience and Target Uses of the System

13. Project Accomplishments To-Date Development: Reporting functionality, role based privelages, abnormal range alerts, nursing care actions, ADT interfaceDevelopment: Reporting functionality, role based privelages, abnormal range alerts, nursing care actions, ADT interface

14. Project Accomplishments To-Date Usability Study for Flowsheets application and CP Console application Stage I, Hines VAMC Stage II, Charleston VAMC Preliminary/ Alpha Testing Hines VAMC � GE Marquette bed-side monitors Beta Testing St. Louis Denver Charleston Lexington Pittsburgh Baltimore

15. Future Project Milestones 08/2010 Complete Beta testing of Clinical Flowsheets System Complete Operational Readiness Testing/Review 09/2010 Transition MD*1.0*16 to Enterprise Product Support (EPS) Team CY - 3Q/2010 Production implementation Scope-out second release of Clinical Flowsheets application Prepare for interfacing with additional ICU instrument vendors

16. Terminology History Initially identified terms going over several paper flowsheets From a variety of sites Entered all data into spreadsheet Standards and Terminology Workgroup reviewed all data elements and their attributes Committee members from all over the nation Hold a variety of different positions (CAC�s, Nurse Managers, Nurses, etc.) Have met regularly for over 2 years now

17. Terminology Observations are the cornerstone of terminology What is an observation? A single observable measurement or assessment for a single patient at a specific time Usually quantifiable Assessments may be simple or an in-depth analysis may be required (for scalar assignments)

18. Components of an Observation 1 Observation Name Description of the observation being taken Abbreviation Help Text for the observation Value Type Length, Width etc. for unit conversions Data Type Complex, Pick List, Numeric, Boolean, String

19. Components of an Observation 2 Anatomical Location Body Position Laying, standing, sitting, etc. Method of Observation Example: heart rate; apical, carotid, Art. Line Product Juice, blood, water

20. Components of an Observation 3 Quality of Measurement Actual, estimated Units of Measurement cm, mm, kg, events per hour

21. VUID Based VA Unique Identifiers (VUIDs) Integers associated with terminology elements such as concepts, expressions, etc. Generated by and used as a Primary Key for Enterprise Reference Terminology (ERT) and Standard Data Services (SDS). Used to uniquely identify a medical concept or expression independently of application, user interface contexts or VHA site.

22. Next Steps Working with STS to get standardized terms through VA Data Standardization Process Working in concert with STS to ensure terminology compatibility for later data standardization Continue to identify observations Working with various assessment Scales/Scoring systems Braden, Glascow Coma, etc. Mapping to SNOMED-CT terminology system Mapping existing terms into CP Gateway Mapping Tables and Views to further test the application

23. System Overview - 2007

24. CP Console

25. View Designer

26. Column Definition

27. View as Flowsheet

28. View as Input

29. Observation Display

30. Audit Warning

31. Correction Screen

32. Flowsheet with Correction

33. Date Range Selector

34. Viewing Log Files (Verified)

35. Viewing Log Files (Corrected)

36. Another View

37. HL7 Monitor

38. HL7 Patient Match

39. HL7 Instrument Match

40. HL7 Message Viewer

41. Q/A Questions