The Kaiser Permanante, Term Paper Example

Description of the process including what functional area it belongs

My organization is the Kaiser Permanante and it has a very peculiar health information system designed to meet the needs of the extensive network of providers at the various hospital locations. Despite immense successes as client load increases it becomes necessary to make databases changes so prevent slowing up of the system as now exists when retrieving patients’ information. Therefore, expansion of the existing database profile is recommended. The process encompasses eleven (11) stages (Basic Database Tutorial, 2013).

Stage 1entails scope definition of the database program. Here information technology experts will discreetly identify subdivisions within the organizational structure to be serviced by the new database modifications. At the same time definition of functions utilizing the modification will be addressed as well as evaluation of existing systems comparing them with planned conversion interventions. In culminating this stage a proposal will be presented to management for approval(Date, 2003).

Once approval is obtained this facilitates transition through the remaining stages. Stage  two (2) involves organizing the project; stage three (3); selecting the database management system products; stage four (4) developing the initial implementation plan; stage five (5) designing the database; stage six (6) perform training; stage seven (7) install and test database; stage eight (8) develop a detailed conversion plan; stage nine (9) convert existing applications; stage ten (10) add finishing touches and stage eleven (11) adapt a regular evaluation of the new database system (Basic Database Tutorial, 2013).

Descriptions of tasks or activities involved with the processwith key attributes used for activity or task analysis.

Activities/ tasks pertain to the various stages/processes through which the implementation phases must pass. For example, in stage two when the database project is actually organized a team of technicians is delegated with the task of designing the new database programs and selecting appropriate software interventions. Next a database administrator is appointed to manage project progress by organizing regular meetings with vendors and organization’s technical staff. A vendor is then selected by this team to begin the database implementation process (Beynon-Davies, 2004).

This team along with vendors then identifies files, which must be converted to facilitate accuracy of the system.Subsequently, relevant program applications are selected along with clerical support to monitor the data conversion process. A schedule of hours needed to modify the database is developed by vendor and team. Training in data manipulation (DML); data manipulation language control (DMLC) and data definition language (DDL). Individual assignments related to the implementation of each program are given to programmers who will modify files that have to be loaded in the system (Lightstone, Teorey & Nadeau, 2007).

As the stages progress towards actual implementation the vendor and programmers will bring up one application at a time; code DM LC schema and sub schema; modify relevant programs for DBMS testing; code programs to be converted; generate the database by testing and debugging review and approve test results. The next very important task entails revision and updating applications as they are being converted, which is undertaken by programmers.After  modification implementation, the database must be monitors of functionality issues and further updated accordingly (Lightstone et.al, 2007).

Summary of approaches to each analysis areaalong with expected outcomes

As was outlined earlier there were eleven (11) stages to this database conversion implementation process representing the approaches to be taken. The first stage entailed defining the scope of this project, which eliminates any issues of beginning and not being able to complete since an analysis of specific tasks were not taken into consideration during the initial evaluation. Also, obtaining the organization‘s approval was ensuring that there would be enough funding for the project and every contractor including the vendor would be appropriately compensated for their expertise (Beynon-Davies, 2004).

Subsequently, by planning ahead documenting the database management system; developing the initial plan and allowing expert reviews are strategies designed to confirm that the system analysis was thorough acquiring non subjective data. Subjective data would tend to give the project a biased approach whereby the opinions of just a few have been regarded as valuable for consideration in the implementation phases. Significantly, designing the databases andincluding training as part of the program is a technique used to enable user ability of the conversions. It makes no sense converting databases and staff or end-users cannot articulate programs neither understand the software mechanisms involved in transfer and storage of patient information (Date, 2003).

Another approach which is beneficial to this project involves the data definition aspect of the process. Database language has always created difficulty regarding user ability in information technology systems. It creates such discrepancies that it makes the system obscure and incompatible. Therefore, defining language; testing tools and ultimately evaluating and re-evaluating system functionality for optimal outcomes can tremendously improve database receptivity atKaiser Permanante.

References

Basic Database Tutorial (2013).  Database Implementation Procedure.  Retrieved on February 3^rd, 2013 from   http://www.cl500.net/implementing.html

Beynon-Davies, P. (2004). Database Systems 3rd Edition. Palgrave, Basingstoke, UK

Date, C. (2003). An Introduction to Database Systems, Fifth Edition. Addison Wesley

Lightstone, S. Teorey, T.;& Nadeau, T. (2007). Physical Database Design: the database professional’s guide to exploiting indexes, views, storage, and more. Morgan Kaufmann Press.