HIM 650 Database Project Proposal-Part 2 Assignment

HIM 650 Database Project Proposal-Part 2 Assignment

HIM 650 Database Project Proposal-Part 2 Assignment

Most drugstores and a growing number of practitioners depend on technology systems to keep patient profiles up to date, including diagnostic data, laboratory data, and prescription data. These systems offer some protection against pharmaceutical mistakes, treatment repetition, and drug reactions (Schiff et al., 2018). They often operate independently, with no knowledge of medications given by other primary care doctors or issued by other pharmacists. For instance, a recent analysis by Schiff et al. (2018) discovered that nearly one in every five patients receiving methadone treatment therapy obtained and filled prescriptions for other drugs, mainly from a separate clinician or drugstore. Therefore, this project proposes a consolidated prescription database which will be a beneficial tool for reducing incorrect prescriptions administration and distribution, especially for prohibited medications that are susceptible to abuse or resale, including opioid analgesics and benzodiazepines.

Goals and Objectives

Prescription opioid misuse affects many people, with approximately 117,000 people in Minnesota abusing them each year (Treatment Solutions, 2021). Prescription drugs addicts visit multiple doctors and pharmacies to obtain multiple prescriptions. Many users have mastered the art of “doctor shopping” to get adequate drugs to fulfill their craving. Therefore, the proposed prescription database’s goal is to provide pharmacists and practitioners with past and current patient prescription data on drug usage. The anticipated database will compile prescription data relating to prescription drugs by various people across the state of Minnesota.

Database Schema

A database schema is the conceptual design of an entire or portion of a database system. It can be represented visually and as a collection of procedures known as integrity constraints that control a database (Khalfallah et al., 2018). These procedures are written in a data definition language like SQL. A database schema, part of a data dictionary, describes how the objects that comprise the database, such as stored procedures, views, tables, and other elements, interact (Khalfallah et al., 2018). Developers often utilize database schemas in software design to lay out how a database must be structured. A database schema is used to design the layout of a database and will assist ensure that data inputs are structured consistently, that each record entry has a unique primary key, and that no vital data is missing.