Requirements specification for Electronic Health Record System (below called the EHR system) Customer Midland Hospital Supplier … The delivery comprises Software, operation and maintenance for an EHR system Contents A. Background and supplier guide 4 A1. Background and vision 4 A2. Supplier guide 5 A3. Overall solution and alternatives 6 B. demands 7 B1. 7 B2. Business goals 8 B3. Early proof of concept 9 B4. Minimum requirements 10 B5. Selection criteria: Highest net benefit 11 B6. Selection criteria: Most score points per dollar 12 C. Tasks to support 13 Work area 1: Patient management 13 C1. patient before arrival 13 C2. Admit immediately 13 Work area 2: Patient treatment 14 C10. Perform clinical session 14 C11. Prescribe medicine for the patient (long subtask) 15 C20. Perform clinical session, mobile 15 D. Data to record 16 D0. Common fields 17 D1. Diagnosis 17 D2. Diagnosis Type 18 D3. Service 18 E. Other functional requirements 21 E1. System generated events 21 E2. Reports 21 E3. Business rules and complex calculations 22 E4. Expansion of the system 23 F. Integration with external systems 24 F0. Common integration requirements 25 F1. SKS 26 F2. LabSys 27 F10. Integration with new external systems 28 G. Technical IT architecture 29 G1. Existing hardware and software Alternative 1: Use what we have 29 G2. New hardware and software Alternative 2: Supplier suggests 29 G3. The supplier operates the system Alternative 3: Supplier's problem 29 H. Security 30 H1. Login and access rights for users 30 H2. Security management 31 H3. Protection against data loss 32 H4. Protection against unintended user actions 32 H5. Privacy requirements 32 H6. Protection against threats 33 I. Usability and design 34 I1. Ease-of-learning and task efficiency 34 I2. Accessibility and Look-and-Feel 35 J. requirements and deliverables 36 J1. Other standards to obey 36 J2. User training 36 J3. Documentation 37 J4. Data conversion 37 J5. Installation 37 J6. Testing the system 38 J7. Phasing out 38 K. The customer's deliverables 39 L. Operation, support, and maintenance 40 L1. Response times 40 L2. Availability 41 L3. Data storage 41 L4. Support 42 L5. Maintenance 43
Work area 2: Patient treatment This work area comprises … Perform clinical session A clinical session may comprise diagnosis, planning, treatment, evaluation, etc. Usually several of these are carried out, but it may also happen that only planning, for instance, is carried out. Start: Contact with the patient or a conference about the patient. End: When nothing else is to be done about the patient right now. Frequency: In total: Around 15,000 per day. Per user: A maximum of 20 per day. Difficult: Disaster with many injured. (Better describe it as a separate task. See the guide booklet.) Users: … Subtasks and variants: Example solutions: Code: 1. Identify the patient. The system can read an electronic bracelet, e.g. for unconscious patients. 2. Assess the state of the patient. See open diagnoses and related indications. See notes. See results of services ordered earlier and compare them with expectations. The data to overview comprises D0 … The system shows an overview of everything on one screen, e.g. with a Gantt-like time dimension. The user can drill down to details from the overview. 2p. Problem: Today clinicians have to log in an out of several systems to see all relevant data. 3. Provide services that can be given on the spot, e.g. blood pressure and SAT. The system it easy to record the results on the spot. 4. Follow up on planned services and results. Check for violated deadlines. The overview shows ordered services and their state, e.g. deadline violation. 5. Adjust diagnoses (modify, add, delete, prioritize). against standard recommendations. Write notes. 5p. Problem: Cumbersome to see standard recommendations. The system can show recommendations and checklists based on a selected diagnosis. 6. Plan and order new services. Check against available time for all parties - including the patient. (See the long subtasks C11, C12 … for prescription, booking …). For bookings, the system shows available dates and times for all parties. 6p. Problem: Parts of the request are forgotten. The system can book standard packages of services. 6q. Problem: Errors when data are written on and recorded later. The system makes it easy to record on the spot. 7. Maybe discharge the patient. (See task C6).