As the Product Manager for Inner Expressions you are asked to provide one of your largest clients with additional features in the EMR ( Electronic Medical Records Management) System. The client has requested an integrated Referral Management System that tracks patients from Primary care into the Specialist departments. Appointments are created by either the Primary Care Physicians themselves or other clinical staff like Nurse Practitioners or Clinical Assistants. Each appointment must go through the appropriate checks including checking if the patient has an active insurance with the client, whether the insurance program covers the condition of the patient, patient’s preference for location and timings and availability of the Specialist doctor.

Some appointments may have to be reviewed by the Specialists themselves before they can be approved, the administrator of the facility (hospital) must have the ability to choose by appointment type to either make it directly bookable by the Primary Care Staff or as a type that requires review by the specialist. The system should also allow the Primary Care Staff and specialists departments to exchange notes and comments about a particular appointment. If the specialist department requests tests or reports as mandatory for the appointment, the system must ensure that the patient has these available on the date of the appointment.

The system shall also allow users to track the status of patients’ appts & must store the entire clinical history of each patient. This will be used by the hospital for two main purposes; the specialist and the primary care providers will have access to the patients complete medical history before the patient walks in for the appt and hence allowing for better patient care, the Hospital also stores this data in a general data warehouse ( without Protected Health Information) to do analytics on it and come up with local disease management programs for the area. This is aligned with the Hospitals mission of providing top quality preventive medical care.

The Hospital sets about 300 appointments per day and must support about 50 users at the same time. The existing EMR system is based on Java and an Oracle database system.

• Identify Actors, Use Cases, Relationships
• Draw Use Case Diagrams
• Identify Ideal, Alternate and Exception Flows
• Write a Business Requirements Document

An e Examination system is also known as (e-Pariksha/ Online Examination Scheduler), an Intelligent Web Application which automates the process of pre examination scheduling of Any Academic Institutions, Universities, Colleges and School. This automations primary scope is to save nature by saving tons of paper involved in conducting the examination. All examination communications are done via email management between student and Academia. Usually any examination would start with Exam Registrations, which is connected to Subject Creation, Exam Room Management , Room Allotment, Examination Hall Dairy, and Absentees Information (Variety of Reports) – Required by UniversityThis WebApp edges two sides of Client side and Server side Application. Client side enables student community to fill up their examination registration form online via internet and also they have privileges to check out their examination details like (Day of Start, Complete Time Table, Day-wise Exam Details and Day seating details of the candidate- like room name, seating number subject, date and time. The Server side involves the processing of each candidate exam registration form into workflow like, Subject Loader, Room Management, Seating Manager, Room Allotment, Room Dairies, Absentee Marking, and Rich Crystal Reports to meet various needs of Data set.The WebApp Admin records new chattel into database, deletes archaic ones, and revises any information related to examination. “User”. All users are known to the system by their USN, ID and their The asset management system keeps track of a number of assets that can be borrowed, their ownership, their availability, their current location, the current borrower and the asset history. Assets include books, software, computers, and peripherals. Assets are entered in the database when acquired, deleted from the database when disposed. The availability is updated whenever it is borrowed or returned. When a borrower fails to return an asset on time, the asset management system sends a reminder to the borrower and informs the asset owner.

The administrator enters new assets in the database, deletes obsolete ones, and updates any information related to assets. The borrower search for assets in the database to determine their availability and borrows and returns assets. The asset owner loans assets to borrowers. Each system has exactly one administrator, one or more asset owners, and one or more borrowers. When referring to any of the above actor, we use the term “user”. All users are known to the system by their name and their email address. The system may keep track of other attributes such as the owner’s telephone number, title, address, and position in the organization.

The system should support at least 200 borrowers and 2000 assets. The system should be extensible to other types of assets. The system should checkpoint the state of the database every day such that it can be recovered in case of data loss. Owners and the administrator are authenticated using a user/password combination. Actors interact with the system via a web browser capable of rendering HTML and HTTP without support for JavaScript and Java.

The persistent storage is realized using an SQL database. The business logic is realized using the WebObjects runtime system. The system includes:

• Identify Actors, Use Cases, Relationships
• Draw Use Case Diagrams
• Identify scenarios and write for all Use Cases
• Write up Business Requirement Document