Answer

Using Zachman Framework for Enterprise Data Architecture for Computer-based Patient Record System (CPR)

The Zachman Enterprise Architecture Framework is used to guide and structure enterprise architecture (Lapalme et al., 2016), Given that Computer-based Patient Record System (CPR) has multiple needs and requirements, it requires a framework to understand what steps should be taken in designing it. Zachman’s framework is well suitable for that task as it can provide guidance on what kind of artifacts are needed in different stage of the process of collecting and storing patient data. The aim of this paper is to describe how Zachman’s framework for enterprise data architecture would be used in developing Computer-based Patient Record System

Using Zachman framework to create the structure of the CPR and understanding when to use the different data models will be paramount. First, the CPR will be divided into different teams tasked with a specific function. For instance, the human resource department will produce a set of policies that will govern the way each team will operate. In addition, each team will be assigned different tasks and supplied with a particular set of instructions and work load. The teams will work alongside each other before starting their tasks. Each team will then need to come up with an answer to the questions of how, why, what, when, where and who for doing a particular task as depicted in the Zachman’s framework in figure 1 below. Choosing of the teams is not done randomly, rather, it is done according to a distinct view of the organization; planner’s view, owner’s view, designer’s view, implementer’s view, sub-constructor’s view and user’s view. Each of the teams, when necessary, will be required to provide a particular UML and/or an entity relationship diagram that would be used to answer the questions stated above. Upon completion of this task, a table can be generate showing how zachman has will be used to determine a successful development and maintenance of a computer-based patient record system (Hastarista, 2016).