Hospital Information System Requirements - Project 1
Hospital Information System Requirements - Project 1
Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences & Technology 4006-430 Medical Application Integration Project 1
Envisioning Statement Happy Healthy Kid is in need of an electronic appointment scheduling system. The system must be able to schedule appointments, prevent overbooking of appointments, cancel and reschedule appointments and provide a summary of appointments for the day. The appointment specialist is the only person allowed to directly interact with the system. Each appointment must be designated with a unique identifier, date and time, duration, type and a resource. An appointment can be made for either the doctor or the nurse practitioner. In addition, the scheduling system should maintain patient demographic information in addition to appointment history. Appointment Process A parent will call to schedule an appointment, stating his or her appointment needs. The appointment specialist will check the availability of the doctor for specified date and time, and will book the appointment. Details of the appointment are confirmed with an appointment card that is mailed to the patient. Four different events could occur following the original scheduling of the appointment: 1) The patient arrives at the clinic at the scheduled appointment time 2) The parent cancels the appointment. 3) The appointment requirements change requiring a subsequent confirmation. 4) The parent / patient does not show up for the appointment Registration / ADT Process The Appointment Scheduling System interacts with the Registration / ADT System. The patient arrival in the clinic completes the appointment and triggers an event that is sent to the Registration / ADT system known as a patient registration. Several other registration / ADT events may occur. 1) A patient can be admitted to the hospital into a nursing unit - room / bed 2) The nurse can transfer a patient to a different bed. 3) The nurse can discharge the patient (send the patient home). 4) The registration clerk can update patient information such as insurance information. 5) The medical records data integrity manager can merge a patient. This occurs when the registration clerk creates a duplicate patient. A merge associates all patient information updates from the duplicate patient into the correct patient and deactivates the duplicate patient identifier.
Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences & Technology 4006-430 Medical Application Integration Project 1
Use Case
Context Diagram
Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences & Technology 4006-430 Medical Application Integration Project 1 Use Case Number: 1 Use Case Name: Make Appointment Primary Actor: Patient Secondary Actor: Appointment Specialist Description: The parent calls the clinic to arrange a date and time for an examination of his/her kid (patient). Pre-Condition: 1. The patient is a registered patient with Healthy Happy Kid Clinic. 2. The patient does not have an appointment for the requested date/time. Post-Condition: 1. Appointment Specialist successfully registered the appointment in the system Normal Course of Action: 1.0 The parent calls the appointment specialist. 2.0 Appointment specialist accesses the patient record. 3.0 Appointment specialist selects date and time of appointment. 4.0 Appointment specialist selects doctor or nurse based on type of visit. 5.0 Appointment specialist asks the parent to commit the appointment. 6.0 System makes appointment and provides details about (e.g. date, time, duration, type of visit) for the appointment. Alternative Flows: 3.1 Appointment is not available at the specified date and time 3.2 Appointment Specialist selects alternatives 3.3 System offers alternatives 5.1 Appointment Specialist rejects the offer
Your Assignment 1. Develop Use Case Reports to support the following 5 use cases. a. Arrive Patient (same thing as Register Patient) into Clinic b. Admit Patient (into an acute care facility / hospital bed) c. Transfer Patient (from one nurse unit, room, bed to another) d. Place Radiology Order on Patient e. Merge Patient (create a new patient by accident, deactivate mrn, move any data entered on wrong patient back to the correct one)
Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences & Technology 4006-430 Medical Application Integration Project 1
Pre-Condition:
Post-Condition:
Alternative Flows
Exceptions
2. Develop Use Case Diagrams for d and e listed above. The classroom lab computers have Microsoft Visio installed. Use the UML Diagram template. The Use Case diagram is incomplete. Consider other relationships that exist between actors, use case events, and how use cases cross system boundaries. For instance, placing a radiology order must first require that the patient was registered in the ADT system and that the information was sent to the radiology system. Two system boundaries would be required.