Physician Reminder System The Western Pennsylvania Hospital 10/3/ Earl Crane Hap Huynh Jeongwoo Ko Koichi Tominaga
10/3/00Physician Reminder System, Location
10/3/00Physician Reminder System, A history of firsts Then 1848 First public hospital chartered in Pittsburgh 1937 First hospital to develop and use time-lapse photography for research purposes 1959 First in Pittsburgh to open an intensive care unit Now 1971 First hospital in Pittsburgh to build a heliport 1982 First teen and young adult Spina Bifida clinic in Pennsylvania 1997 First Burn Trauma Center to receive verification from the American College of Surgeons and American Burn Association
10/3/00Physician Reminder System, Physician Reminder System Mission Proactive patient management JIT physician reminders Compliance with practice guidelines Result: –High quality outpatient care and follow up –Improved patient outcomes and reduce variations in care
10/3/00Physician Reminder System, Physicians Reminders or suggestions for preventive care, treatment changes or referrals, patient education at time of visit Patients Reminders regarding appointments and compliance Office Staff Reminders of actions during current appointment and of future appointments Services provide to users
10/3/00Physician Reminder System, User Requirements Most important is response time JIT Reminders: remind physicians to enforce clinical best practices for treatment of three diseases Identify time-driven reminders Identify visit-driven reminders Maintain patient’s medical history
10/3/00Physician Reminder System, Demographic data from patient registration system Specific clinical data entered by physicians Secure data from unauthorized viewing System functionality Diagnosis Visit Test Data Billing and lab system System Requirements
10/3/00Physician Reminder System, Hardware Architecture Client –MS Windows 95/98 Server –MS Windows NT Database –Oracle 8i User Interface –Visual Basic 6.0 Database Connectivity –ActiveX Data Objects
10/3/00Physician Reminder System, Software Architecture Patient Management Reminder Systems Report Engine Administration Systems User Interface Time-driven Front End Business Logic Back End Common Database Security Logic Visit-driven
10/3/00Physician Reminder System, Usage Architecture Physician Reminder System Patients Nurses Labs Hospital Information System Doctors Staffs Notification from reminders Test data Management Reminder & Response Patient & Reminder Information Interconnectivity with other systems
10/3/00Physician Reminder System, Usage Scenario for Physician
10/3/00Physician Reminder System, Login and Function Selection
10/3/00Physician Reminder System, View “Patient List” Form.
10/3/00Physician Reminder System, See Reminders
10/3/00Physician Reminder System, Respond to reminders
10/3/00Physician Reminder System, Visit Details
10/3/00Physician Reminder System, Test Results
10/3/00Physician Reminder System, View and update diagnosis
10/3/00Physician Reminder System, Add new diagnosis
10/3/00Physician Reminder System, Project Timeline Client Meetings 9/26Meeting 1- Prof. Padman, PRS developer, provided system documentation 10/6Meeting 2-West Penn Medical Director and IS staff review the hospital’s network architecture 10/23-10/27Meeting 3-Identify vulnerabilities and discuss intrusion scenarios 11/13-11/17Meeting 4-Review findings and recommend mitigation strategies 11/27-11/29Meeting 5-Client response and feedback Class Presentations 10/3Project Briefing 1 10/31Project Briefing 2 11/14Project Briefing 3 12/7Project Briefing 4
10/3/00Physician Reminder System, Team Activities Team Meetings to Date 9/23Initial team meeting-Project discussion and assignment of roles 9/28Client debriefing and presentation discussion Weekly Meeting Standing Team Meetings- Tuesdays 11am-1pm Additional Meeting will be schedule as needed