What Does this Mean?

System Design:

• Stage of implementation where the overall architecture of Allscripts is decided based on the needs of Flagler Hospital.
• The system is organized as a set of sub systems that interact with each other. While designing the system as a set of interacting subsystems, the department specific IS analysts conduct current state assessment and future state design sessions with departmental subject matter experts (SME's) to ensure they are on the right path to meet the needs of Flagler Hospital end-users.

System Build:

• Once design decisions are made, the analysts take these decisions and tailor the software based on their findings discovered during the System Design stage.
• Building involves adding current Flagler specific data into the system as well as historical data.

System Testing and Validation:

• System Testing involves two areas of testing, Application testing and Integrated testing.

• Application Testing refers to testing all the modules within Allscripts to ensure the workflows and processes contained within it work as designed to enable Flagler Hospital employees to do their jobs. We will utilize scenarios such as admitting a patient, scheduling a patient and entering orders on a patient to make sure the applications perform properly. This is the first stage of testing.

• After confirmation that Allscripts software works as it is supposed to through application testing, integrated testing begins to ensure that Allscripts will communicate properly hospital- wide.

System Training:

• Pilot training program with members of the Pit Crew
• Refining the training curriculum and training methodology for the various roles of the end users.
• Training will be conducted as follows:

1. Train the trainers
2. Super User training
3. Ancillary training
4. Nursing training
5. Physician training

Go Live:

• The date when Flagler Hospital employees will begin using Allscripts exclusively and Meditech use will cease.

• We will "Go-Live" on Allscripts in July 2013.