IWeb Unmerge Status Presentation April 16, 2007 Stefanie Handrick Tyrus Peace Nathan Winchester

Project Overview IWeb software used by state agencies to store immunization records Original software written in Adelphi Most functionality has been ported to a Java web app Supports merging of patient records into one patient Unmerging patient records still in Adelphi Requires separating each record into patients and remerging

Project Requirements Port unmerge functionality to Java web app Make the unmerge more user friendly by: Allowing specific records to be selected to create several patients Associate remaining records with a particular patient

Design Classes com.stchome.siis.accessors.UnmergeAccessor setMaster updateReserve getRecords getMaster Struts class execute validate

Use Case Assumption: the user is a System Administrator Basic work flow: User clicks “Unmerge Client” under the “Administration” heading System displays the [Unmerge] screen User enters the Id of the patient to unmerge and clicks “Unmerge” button System displays all reserve records for the patient Id entered User selects a check box for every record that should be a master record

Use Case Basic work flow continued: User clicks “Unmerge” button [Unmerge] screen is update to display remaining reserve records with a combo box listing all master records User selects appropriate master record for each reserve record User clicks “Unmerge” button System displays [Unmerge Confirmation] screen User clicks “Unmerge” button System displays [Unmerge Successful] screen

Use Case Alternate work flows: Patient does not exist User clicks “Back” button Not enough master records selected Master records not selected for all reserve records User cancels the unmerge

Test Cases Unmerging a client with no merge history Unmerging a client with n reserve records into n patients Unmerging a client with n reserve records into less than n patients

User Interface The following slides contain mockups of what the screen will look like while unmerging a patient.

Summary Identified problem and requirements Identified classes that are needed to implement the solution Identified use case for the system administrator Created test cases Created screen shots for the user interface

Next Steps Clean up the mockups and work flow to reflect any changes Evaluate the identified classes to verify correctness Implementation and testing