CS818 SOFTWARE SYSTEM ENGINEERING Team 3 Steve Grimes, Craig Mitchell, Mark Oden, Mark Ramos, Brian Rater, Kat Reagan

Mission Statement Your company has identified a market niche for a patient- oriented medical information system. The product is expected to provide: A standard electronic patient records portable across multiple health care providers accessible by the Internet User interface and reports Secure interface for update/access to patient records Electronic interface to pharmacy system, insurance systems, and provider billing systems Users can tolerate only a few minutes of outage time per year; security of patient information, billing information, and pharmacy pricing data is very important; response times to data updates, queries, and transactions with external systems must be accomplished within a few seconds.

Drivers Driver NameRationalImportance SecurityMust protect billing and price integrity; privacy concerns; Legal responsibilities; prevent malicious hacking; prevent unauthorized access; prevent fraud and identity theft. High AvailabilityIf System is used for medical purposes, availability is critical. Providing incomplete records may lead to misdiagnosis. Down time may be adverse during emergencies. If System is used for personal use, availability’s importance will not be as high. Critical /Medium* InteroperabilitySystem must operate with many complex and constantly changing systems Medium PerformanceIf System is used for medical purposes, slow response times could cause delays in emergency and urgent care situations; can increase the time it takes a doctor or nurse to see each patient If System is used for personal use, availability’s importance will not be as high. High/Medium*

Drivers 1.Security: Must protect data integrity of billing and prices; privacy concerns; Legal responsibilities; prevent malicious hacking; prevent access by unauthorized users; prevent fraud and identity theft 2.Availability: May be needed in emergencies; having only some records and not others can lead to misdiagnosis 3.Interoperability: System must operate with many complex and constantly changing systems 4.Performance: Slow response times could cause delays in emergency and urgent care situations; can increase the time it takes a doctor or nurse to see each patient

Challenged Drivers: Availability Availability: “Users can tolerate only a few minutes of outage time per year” 1. Few is unclear and subjective to interpretation. 2.5 minutes of yearly downtime or % availability will allow about one second of down time per day. Maintenance and system recoveries must be done without human intervention. This down time allowance may be appropriate if system is used by medics, doctors, or hospitals. 3.8 hours of yearly downtime or 0.999% availability would allow 10 minutes a week. This will allow time for human involved maintenance and scheduled downtime. This solution may be appropriate if system is not used during emergencies. Performance: “response times to data updates, queries, and transactions with external systems must be accomplished within a few seconds” 1.For emergency services, a second response time is reasonable. 2.This expectation may not take in consideration external systems 3.Non emergency services, such as pharmacy information, may not need this stringent requirement.

Open Issues 1.Will a patient have access to the system? 2.Health care provider is a very broad term. What type of health care provider will access this system? 3.Will this system be accessed by doctors, hospitals, or other emergency care professionals? 4.Will there be central repository for patient records? 5.Will the system be used in emergency situations? 6.What legal issues will be involved in this system (federal and in all states) 7.We will need to understand scope of pharmacy and insurance systems