SDLC Final Project- Testing and Installation

SDLCFinal Project- Testing and Installation

InstituteAffiliation:

TestingProcess, Installation, and Training Summary

Themission of the testing face of the project is to develop, implementand test system components and software according to the hospital’sand patient needs. Therefore, it will involve the testing,installation, and training of staff on the use of devices’software, hardware, and interface, ensuring building andimplementation of ICT applications. It also includes the diagnosis ofprograms, planning, and making sure the designed codes for theoperating system are all functional to ensure optimum efficiency andfunctionality.

TestPlan

Inline with Doolin (2004), the first initiative is coming up with anopen test strategy and an in-depth test plan. The plan should gobeyond testing technical and functional application requirements andinclude outcome focused test of different business ideologiesandother processes, for instance, the services rendered to thecustomers, customer or patient enrollment, and provider management.In so doing, the test will ensure set goals and objectives are met inthe major dockets, that is, the business level, financial,operational benefits, clinical level, and operational level.

Thenext step is developing a test business scenario that represents thehospital’s related processes that generate high volumes transactionprocesses, and has the potential having the greatest financial andoperational impact at the hospital. The domain intensive pre-testingwill involve domain experts with deep knowledge about the installedsystem, software, and interactive interface, ensuring the criticalscenarios of the hospital are test first (Doolin, 2004). Next,scenarios will be executed thoroughly on an end-to-end testing basisvalidating the full execution of the business processes in line withthe hospital’s set objectives. The testing to should see to it thatall parties involved, that is, the IT system and the hospitalprocesses are integrated, operational, and they are ready to acceptand process the set code formats.

TestSummary

Testdesigns of the environment, the data, the test strategy, testscenarios, and the actual test is to be carried out with the sole aimof a quick return to normal business operations, thoughtechnologically simplified. Therefore, the test will commence withthe identification of hardware and software required for the relevantapplication to be used in the personal data assistant (PDAs) and inthe main server system administering the intranet. Through a riskbased approach, the test data will be defined, test datarequirements, and test data management tools and processes. Riskbased operations will be conducted in close cooperation with internalhospital stakeholders and patients (Doolin, 2004).

InstallationProcess and Training Summary

Beforeinstallation commences, the hospital must not assume the vendor ofthe system addresses the effects implementation of the hospital keyoperational areas, that is, the patient registration, clinicaldocumentation, coding, order entry, billing, and other functionsrelated to the hospital’s operations.

Implementation

Theimplementation phase has all the directions of the operationactivities identifying the method and approaches to implement a newsystem through code mapping. Therefore, the following key activitieswill be carried out in the implementation phase allowing a transitionprocess. The hospital will determine the vendor’s capacity toinstall updates of the system, coordinating updates affectinginternal policies, thus, ensuring a continued update on softwareaffecting internal processes such as clinical, financial, andreporting.

Theimplementation phase will also entail finalizing the system andtechnical requirements, coordination of update of the identified testdata, approve and update code design to facilitate system change, andcoordinate and conduct testing based updating the system logic. Someof the available resources to be used include the American academy ofprofessional coders (AAPC) code translator to offer medical codes,and t he healthcare information management systems that will assistusers in the prediction of financial impacts, which will aidunderstanding of the new system’s impact on key areas includingcoding, revenue generation, project management, and informationtechnology (Doolin, 2004).

TestingPhase

Thetesting process will be tasked to prove the system meets itsrequirements and it is consistent in the results it gives. Thus,testing will offer compliance across all internal policies,processes, and systems, as well as be compliant with externalstakeholders of the hospital. After the completion of the changes,the hospital will carry out several tests, which include individualcomponent tests, system tests, and performance tests of the newsystem. For example, running of a physician test, checking thehospital’s information exchange capacities with physicians ensuringcoordination and procedure related information exchange is handledwithout a hitch.

TransitionalPhase

Thehospital will finally develop a transition plan to monitor and trackthe system implementation (Doolin, 2004). During this period, thehospital is to monitor the different impacts caused by the transitionon the different operations. In addition, the hospital incollaboration with system’s software vendor will train the hospitalstaff give way to a hitch free transition from the old system to thenew system with minimal resistance.

Thetable below illustrates an operational time frame

Strategy Plan

(2-4 days)

Implementation

(6 days)

Testing (3day)

Transitional Phase

(2 weeks)

Creating a strategy and detailed test plan

directions of the operation activities identifying the method and approaches to implement a new system through code mapping

proving the system meets its requirements

Establishing a plan to incorporate the new system and training hospital staff applications of the new system

Supportand Maintenance Plan

Hospitalshardware and software will be maintained through configurationmanagement. Configuration management entails the in-depth recordingand updating information linked to a department and in this case thehospital’s information system, inclusive of all hardware andsoftware running in the system (Chapin et al, 2001). Thus, theconfiguration management will record versions and updates applied insoftware instauration for the different packages and the location andnetwork addresses of the different hardware devices. Therefore,whenever the system will require a hardware or software upgrade, thesystem manager will unprecedented access on the management programallowing full access to installed software on the system, and make aninformed decision.

Developerswill ‘use configuration management in the hospital’s softwaredevelopment enabling them to manage the source codes, documentations,arising problems, and requested changes and implemented on thesystem. Therefore, the configuration management will provideassurance that the information system in operation and beingmaintained is under correct configuration and changes made arereviewed ensuring security setups are up to date. The hospital willalso involve outside bodies such as the Information TechnologyConfiguration control Board to review and assess the security statusof the hospital’s system to issue approves prior to implementation(Chapin et al, 2001).

Throughconfiguration management, maintenance of hardware and software suchas PDAs, Computers, and the system software will be done in fashionthat is controlled and pre-tested to prevent occurrence of anyadvance effects on the information system functionality, includingcompromising its security, or affecting any of the connectingdepartment ability to transmit information. In addition, thehospital’s information security officer in conjunction with thesystem administrator, they will develop and maintain a departmentconfiguration management on all the systems under their managementauthority, being part of the system security documentation to becertified (Chapin et al, 2001).

Thehospital’s system administrator and information security officerwill also play the roles of local configuration controllers ensuringthat all hardware, software, and other network components installedon the local area network (LAN) do not affect the existing local ITinfrastructure. In addition, they will ensure that the locallyapproved software and hardware functions from the hospital aresupporting the local network segment. Also, ensure that the hospitalinformation technology application baseline includes current,complete, and accurate data setups running on support or majorapplications, and all other resources approved for installation inthe hospital’s network.

Beforeimplementation of application software on the department’s system,the system administrators in consultation with hospital’s medicaland management staff will define the requirements, security needs toensure confidentiality and integrity of data input, transactionprocessing, and data output. Finally, the application will have to betested I the development envelopment prior to operation to ensurepresences of satisfactory operation controls (Chapin et al, 2001).

ConcludingRemarks

Hospitalmanagement systems go to more than providing hospitals with anopportunity to enhance patient care but also increase the facilityefficiency and profitability. Additionally, a well implementedmanagement system will allow administrators the opportunity toimprove the hospital’s operational control and streamlineoperations.

References

Chapin,N., Hale, J. E., Khan, K. M., Ramil, J. F., &amp Tan, W. G. (2001).Types of software evolution and software maintenance. Journalof software maintenance and evolution: Research and Practice,13(1),3-30.

Doolin,B. (2004). Power and resistance in the implementation of a medicalmanagement information system. InformationSystems Journal,14(4),343-362.