DOCTORATE WRITERS: HIM 650 Database Project Proposal-Part 2 Assignment

DOCTORATE WRITERS: HIM 650 Database Project Proposal-Part 2 Assignment

A database designer usually builds a database schema to assist developers whose applications communicate with the database. Data modeling refers to the process of developing a database schema. This stage would come after establishing a logical model in the three-schema methodology to database architecture. Conceptual schemas are concerned with the knowledge demands instead of the architecture of a database. There are two types of database schema (Imam et al., 2018):

• A logical database schema expresses the logical restrictions about the system’s data. It can define referential integrity, tables, and views.
• A physical database schema defines how data is kept on a storage system in records and indexes.

A database schema describes which columns or relationships comprise the database and the attributes featured on every table. As a result, schema design and entity-relationship diagram are sometimes used interchangeably (Imam et al., 2018). The figure below illustrates the schema (ERD) for the proposed prescription database.

Figure 1: Prescription Database Schema

Processes Associated with the Business Rules

A business rule is a guideline, technique, or practice that governs an institution. It is vital to identify and define the business logic when creating a database. These rules allow the database designer to specify the interaction between the participation limitations and guidelines and the appropriate data design. A database designer should comprehend procedures and the kind, role, and scope of the data to create a database that will be useful to the organization. The prescription database is subject to specific business rules listed below.

• A physician can treat one or more patients.
• A physician can order one or more prescriptions, including one or more drugs.
• A pharmacy can only issue drugs prescribed by a physician.
• A patient can only receive drugs issued by the pharmacy and prescribed by a physician.

Entity Relationship Diagram and Data Dictionary

A Data Dictionary collects labels, descriptions, and properties for data components utilized or recorded in a database, computer system, or research project. It defines the interpretations and goals of data items in the context of a project and gives direction on understanding, accepted meanings, and layout (Buchanan et al., 2021). In addition, a Data Dictionary provides metadata on data items. A Data Dictionary’s metadata can help define the scope and properties of data items and the criteria for their utilization and application. The table below describes the data dictionary for the proposed prescription database.