Project Delivery

4.1 HMS - Deliverable Functions:

Most of the functions outlined in section 2 will be delivered with the final software product. Exceptions would include the following options: The staff of Sirius Software Products feel that given the very short development period of this project, the above listed functions could not be feasibly completed by the assigned completion date. Given favorable development conditions, the on-line help function could be added in a future enhancement.

As noted earlier, this system has not been designed with any security options. These options could be added in future enhancements but it is felt that they are currently out of the scope of this project.

Also, billing options have been completely ignored in the development of HMS. It is felt that billing and financial issues should be handled by the City Hospital's accounting department and reside outside the scope of this project.

4.2 Product Simulation Considerations:

It should be noted that the product to be delivered will be a simulation of the system. The deliverable system will be merely a prototype of the full blown system. The customer should understand that this prototype will merely simulate the operation of the full system. This simulation will however be an accurate representation of the functionality of the full system.

Any outputs will be delivered to the terminal screen for the purpose of this simulation. It must be understood that although the full system would be implemented in a LAN type environment, this simulation will be implemented on a single system environment. It is felt that this is sufficient to demonstrate the functionality of the system prototype.

The operating platform for the HMS prototype will be an Intel based personal computer. This platform was chosen for ease of acquisition, low cost and possible ownership of a number of units by the city hospital. A UNIX mainframe platform was considered but was rejected due to cost considerations. As a primary goal of this project was to reduce the hospital's operating expenses, it was felt that the acquisition of large amounts of new hardware would violate this basic goal.

The prototype will be developed using Microsoft Access to design and build the user interface while Oracle will be used for the database features. Access was chosen for its ease of use and flexibility when prototyping systems with windows type graphical user interfaces.

4.3 Requested modifications:

The following is a list of customer requested modifications and enhancements to the HMS system. In order to clear up any possible confusion, the items are listed here along with the proposed solution.

System Overview

  1. In section 2.3.1, "Update Staff"
    We will implement a list of staff names & id's to allow user to select from, in case the user does not remember the staff name or id.
  2. In section 2.3.2, "Display Staff"
    In additional to the original display funcion mentioned in our ODD (overall design document), the system will handle search based on the staff titles (ie. doctor or supervising nurse or nurse) but there will be no search operation for searching what word the staff member works in (or has worked in).
  3. In section 2.3.3, "Hire Staff"
    There are six key attributes for a staff record; first name, last name, phone number, steet address, title(doctor, nurse or supervising nurse) and pecialty(cardiology, pediatrics, etc...). The system will allow staff records with some duplication of attributes as long as not all six attributes are identical. An error would occur only when there are two records having all identical attributes. This give the system flexibility to allow staff members exist with some identical attributes (such as name and address in the case of people from the same family/household).
  4. In section 2.3.4, "Terminate Staff"
    The system will mark the terminated staff record with a 'terminated flag' instead of deleting it from the database.
  5. In section 2.4.1, "Display Patient"
    In additional to the original display function mentioned in our ODD, The system will also allow the user to display a list of patients in waiting lists as well as patients in each ward.
  6. In section 2.4.3, "Discharge Patient"
    The system will mark the discharged patient record with a 'discharged flag' instead of deleting the patient's record from the database.
  7. There is no any backup system, security system or password system in HMS.

User Interface

  1. A small note box will be added into the following interface screens:-

    This feature will allow special messages/conditions [not handled by other existing input fields] to be input by the user.

  2. Change all the UNDO buttons to MODIFY buttons. This naming may have been confusing; we appologize for any inconvenience.
  3. The user we can use the mouse to the desired input field. Also, the `TAB` and `RETURN` keys may be used to toggle between fields.
Next Section
Previous Section
Back to the Final Design Document titlepage
Back to the main page

Last Modified Mar. 5, 1996 by
Darrell Nash