Understanding for identifying a database project proposal for collecting data and for designing and developing a small database that can be used to compile and report clinical data related to either quality measures or pharmaceutical products
Topic: Data Base Project Proposal par1
Paper details: The purpose of this assignment is to provide learners a basic understanding for identifying a database project proposal for collecting data and for designing and developing a small database that can be used to compile and report clinical data related to either quality measures or pharmaceutical products and utilization.
There are three parts to the database project proposal. The initial step involves identifying an idea for a database and describing its purpose. The second
part allows you to design the database components. The third part requires you to present the database proposal to stakeholders. Feedback from the
instructor at every stage will help you make improvements in the database project.
To complete Part 1 of the Database Project Proposal assignment, create a 500-750-word proposal outlining the following elements:
State the project problem and definition of terms.
Identify database users (personnel/credentials): Who are they? What are their competencies and background?
Discuss the types of data that users will collect for the proposed database and describe at least three reports that will be generated for analysis. Explain their
use and who will use the reports?
Describe the project goals and clear measurable objectives for the database. Identify the steps you will take to meet the goals and objectives.
Forecast any potential problems or barriers to meeting the project goals and objectives. Are there any specific assumptions that need to be made?
Discuss data communications protocols that could be used in your database project. Refer to the “Blockchain Personal Health Records: Systematic Review”
article, provided in the topic Resources.
Conclude with the value of the project with emphasis on feasibility and the benefit of the expected results.
Prepare this according to the guidelines found in the APA Style Guide
Garfinkel reports that the United States has become a nation of databases. Today, databases are being used to track credit card transactions, phone calls, ATM withdrawals, and bank account balances.
With the disclosure that more than 98,000 Americans a year die from medication errors, the healthcare industry is also quickly adopting the use of databases to track everything from prescription medications and laboratory tests to patient outcomes.
The reason for the shift is that until now, most medical information has been recorded on paper, a practice that has led to a great deal of waste, duplication, and inappropriate utilization of treatments.
Recently, the US Department of Health and Human Services (HHS) announced plans to create a national database containing electronic medical records that track a person’s interaction with the healthcare system from birth to death.
To stay current with the HHS proposal to digitize healthcare information, AHIMA has adopted a strategic plan called electronic health information management (e-HIM), which calls for the creation of practices that “ensure the availability of health information to facilitate real-time healthcare delivery and critical health related decision-making for multiple purposes across diverse organizations, settings, and disciplines.”
These goals, although ambitious, will not come to fruition unless healthcare information is stored accurately, reliably, and securely in well-designed computerized databases.
Mon states that the most common form of database used in healthcare is the relational database. Relational databases can be used to track patient care in the form of treatments, outcomes of those treatments, and critical indicators of a patient’s current state such as blood pressure, heart rate, and blood glucose levels.
Relational databases can also be used to interconnect with multiple informational systems throughout a healthcare facility. For example, a relational database in a cardiac care unit can be directly linked to a hospital’s registration system. Upon registration, a newly admitted patient’s demographic information is sent automatically to the cardiac database using Health Level 7 protocols.This eliminates the need for cardiac care clinicians to input patient information into the database, freeing them to concentrate on providing the patient with the best care possible.
Relational databases have the potential to eliminate paper storage and transfer of information and to answer important questions about healthcare efficacy rather than merely serving as an accounting mechanism.
For example, diabetic patients sharing similar health risk factors (for example, slightly overweight, high HbA1c and fasting blood glucose readings) can be closely monitored to determine how different drugs (for example, Glucovance) help to control those factors. From an administrative and prevention standpoint, relational databases can be used to identify at-risk patients, for example, those who have a family history of aneurysms. Once identified, patients can be screened to prevent them from succumbing to a particular disease.