Emergency Room
... orders and the auxiliary departments. Deliverables from Task ER2 • Database This task allows for the development of the specific entities (departments, users, physician orders, supplies, and patients), relationships between these entities, and a backup/recovery process in the event that the primary database system goes down. Deliverables from Task ER3 • Completed database, input, and output specifications GUI interface (Oracle Forms), Windows, Barcode scanners, laser printers, PC Tablets, extra PCs, Oracle Application Server and CDFs will be used as database inputs and outputs. This task requires internal controls using exception reports in order to have checks-and-balances of the system. Deliverables from Task ER4 • Placing of responsibility between systems owners, users, analysts, designers, and programmers . This task delegates the job specifications that the programmer will have to code for all the database, input, and output specifications. The Systems Analyst Systems Users will provide a final walk through and approval of the system. Deliverables from Task ER5 • Updated project plan The project plan involves reevaluating the project scope. Work Breakdown Structure (WBS) for Design Phase 1. Design Phase 1.1 Design Task 1 – Design Application Architecture 1.1.1 Application Architecture 1.1.1.1 Oracle Forms used as front-end interface 1.1.1.2 Oracle Database 1.1.1.3 Oracle Application Server 1.1.1.4 Wireless LAN 1.2 Design Task 2 – Design the System Databases 1.2.1 Database 1.2.1.1 Entity creation 1.2.1.2 Entity relationships 1.2.2 Backup/Recovery database 1.3 Design Task 3 – Design the System Interface 1.3.1 Completed database 1.3.1.1 GUI Interface 1.3.1.2 Appropriate user forms 1.3.1.3 Appropriate reports 1.3.2 Hardware specifications 1.3.2.1 Tablet PC’s 1.3.2.2 Extra desktop PC’s 1.3.2.3 Barcode scanners 1.3.2.4 Laser printers 1.4 Design Task 4 – Package Design Specifications 1.4.1 Placing of responsibility between systems designers, analysts, users, programmers and owners 1.4.1.1 Programmers will be responsible for all required coding for database operations 1.4.1.2 Systems owners, analysts and users provide final walk- through and approval of the system 1.5 Design Task 5 – Update the Project Plan 1.5.1 Updated project plan 1.5.1.1 Systems analysts and programmers make any final changes or additions to the system and update scope revisions in the project plan. Error! Not a valid link. Physical Data Flow Description Process 1 - The nurse enters patient vitals into the Medical Visit DB. A trigger sends an e-notification to registration to inform them of a new visit by a patient. Process 2 - Registration personal enters patient billing information into the Accounts DB. A Patient Authorization Form is printed for the patient’s signature. Process 3 - Based on the patient’s priority assigned by the nurse in vitals and room algorithm, the patient is assigned a room number, which is entered into the Medical Visit DB and Room file. Process 4 - The doctor issues orders, which are entered into the Medical Visit DB, concerning the patient. Process 5 - Any internal doctor orders are completed and scanned into Medical Visit DB, also any item inventoried is subtracted from the Inventory file. Process 6 - Any external doctor orders are sent to external entities via Comma Delimited File (CDF) and results are returned via the same. Process 7 - At the time of the doctor’s discharge of the patient, data is exported via a CDF to Hospital Billing and Medical Records. The Room file is updated to proper status. Process 8 - All visits are stored in the visit history database. Error! Not a valid link. In process one, the nurse calls patient from the waiting room into the Triage Area. The Patient's Prior Visit History is checked via the Visit History database. Assessment of patient vitals is input into the Visit Database. After assessment, the nurse assigns a priority for treatment code, which is used to determine the order of care. {Priority codes: blue-highest priority, yellow-mid priority, green-low priority} After the Nurse's Assessment and Priority Codes are input into the database, a trigger informs the Registration Personnel that a patient is waiting to have their demographic and insurance information processed. Error! Not a valid link. In process two, the ER Registration Clerk calls the patient from the waiting area after receiving the alert trigger sent by process 1.3. {For higher priority patients, the ER Registration Clerk will interview patient in the treatment room.} The patient’s account is queried from the Accounts DB. If a new patient is being treated, the patient information {refer to Patient table in the ERD} is entered into the Accounts DB; otherwise, the patient information is updated into the Accounts DB. The clerk will enter a transaction for any money collected in the Patient_Payment table. After the Accounts DB is updated, a trigger is fired to print the Patient Authorization Form, which the patient or authorized representative will sign for release of information and treatment authorization Error! Not a valid link. In process three, visit information is read by the Room Assignment program, which accesses available rooms from the Room table {refer to Room table in ERD} and assigns the patient to an appropriate exam room based on the room assignment algorithm. {Refer to Room Assignment Algorithm} The patient's exam room number is then updated in the Visit database (DB) {refer t...