Recent orders
DATABASE PLAN BARRIERS TO BAR-CODE MEDICATION ADMINISTRATION
Database PLAN: BARRIERS TO BAR-CODE MEDICATION ADMINISTRATION
Name:
Number:
Course:
Lecturer:
Introduction
The systems of medication administration using bar codes were developed with an aim of reducing drug administration errors a long side associated costs as well as to enhance patient safety. This is possible via safe medication administration which is essential to guarantee quality healthcare. The errors or accidental processes can occur as a result of work created by nurses (Barbara, 2012). The rest of this paper is organized in to barriers to medication problems, conceptual data model for the planned database. The entities planned for the database, entity identifiers and relationships and concluding summary in that order. The respective Entity relationship diagram and illustration of relationships are shown at the appendix after references.
Barriers to Bar-Code Medication Administration
There are various barriers that affect Bar-Code medication Administration (BCMA). First is the lack of system or technology acceptance by users who are nurses in this case. The acceptance of technology is normally a prerequisite for the adoption of technology such as bar code medication implementation. This technology acceptance is based on ease of use as well as usefulness. Another issue is that the implementation of this kind of technology for bar code medication can easily disrupt work routines, thus making it difficult for the administration part of it (Taliercio et al., 2014).
Next is the lack of involvement by nurses/users during implementation process. This reduces their chance of understanding how the bar code system works. As a result, they end up having a negative attitude towards it. Failure to understand a new technology and its operations implies high probability of making errors or inefficient usage by the respective users. There is also lack of effective and efficient communication amid those involved. This makes it difficult to analyze the problem of implementation part of bar code technology to be used for medical administration in addition to weaknesses and solutions involved (Taliercio et al., 2014).
Lack of thorough analysis or examination or the existing norms, standards and work culture involved can also make the bar code medical administration system to fail in terms of how to administer its operations. Since the introduction, of such technology leads to the change of workflow as mentioned above, failure to redesign the workflow can also result to implementation failure, thus making medical administration hard. Other barriers include lack of good support as a way of making users such as super-user nurses feel comfortable during implementation process. There is also lack of sufficient knowledge about using the system as well as lack of training which is very significant to the adoption process of bar code medical administration system (Taliercio et al., 2014).
Some barriers also come as a result medication errors that takes place during prescription, dispensing, prescribing, prescription auditing, transcribing among other processes that are conducted by nurses. These errors can be grouped into medication administration errors and near misses errors. Medication administration errors are those that reach the patient and pose risk to the safety of patient while near misses. Bar code medication administration system can be used to reduce a number of these errors to a given level. Nevertheless, the system of bar codes may at times fail to identify and reduce these errors to the acceptable level depending on the error type and magnitude, contrary to the capability of the system. A good example are the omission errors, wrong patient error, preparation error and dosing time error among others which are the leading type errors that originate from nurses according to past research(Wang et al., 2015). In general, it is thus the problem of equipment such as computers and scanners used those results to these problems. The problem with the equipment is perhaps the way in which they are designed. The equipment may be working but poorly designed in such a way that users cannot comfortably use them without making errors unless they are well traimed or guided.
The conceptual data model for the planned data base
Conceptual data model will consist of five classes of information namely medication, patient particulars, Nurse/Dr information, Institution (Hospital information) and summary information. Medication information will comprise of attributes such as Patient Id, Nurse Id, medicine, dosage, Treatment period and disease. Patient information will comprise of PatientId, Patient Name, Age, gender and diagnosis. The Nurse/ Dr information includes Dr Name, Nurse Name, Dr Id, Nurse Id, and department. The general information part of the database consists of Hospital Name, Nurse Name, Dr Name, Patient name, Patient Id, patient age, diagnosis, treatment and dosage. Each class will exist in form of table in the database with unique identifier keys. The management of information in all tables within the database will be made easier by relating all the tables using the most suitable type of relationship. The illustration of this conceptual model of the planned database is shown in appendix 1.
Entities planned for the database
Entities in this case are objects from which medical data are to be created. In other words, they represent names of things to be describes using various attributes within relational tables of the planned database. They include Patient, Nurses, Doctors, Hospital and medicine.
E-R diagram for each entity
The entity relationship diagram patient consists of attributes that describes the patients in question. The attributes such as Patient Name, Age, gender and Patient Id will be used in this case. The entity relationship diagram for Nurses/Doctors will consists of descriptive names such as Nurse Id, Doctor Id and their names and the department of work. The medicine entity will consists of Medicine Id, medicine name, medicine type and dosage. Hospital attributes include hospital name, Ward, department, Receptionist, Contact and others. Patient will be identified by patient Id, Hospital by Hospital Code, Medicine by medicine Id, Nurses and doctors by Work Id. The illustration of these entity relationship diagram (ERD) is as shown in appendix 2.
Relationships between entities
There are various types of relationship that may exist amid entities in this case. They include one to one (1:1), one-to-many (1: M) / Many to one (M: 1) and many to many relationship (M: M) relationship. In this case Patient and medicine will be associated through one-to- much relationship, implying the possibility of treating one patient using two or more types of medicine at a time. Medicine as an entity will be associated with Hospital through many-to-one relationship. This means that several types of medicine can be found in one hospital at a time. The nurses and doctors are also related with hospital entity on many-to-many basis, implying that a hospital has several doctors and nurses. The patient and doctor are also associated on a one-to-one relationship. This means that only one nurse or doctor can attend to one patient at any given time.
A one to one relationship signifies that one entity in a relational database of records is related to another one entity in a different table of the same database. One to many, also called many to one relationship is where one entity in one table of a relational database associates with several entities in a different table of the same database. On the other hand, many- to -many relationship involves one entity in say table (A relating to one entity in table (B) while at the same time one entity in table (B) relating to one entity in table (A) within a relational database.
Summary and conclusion
The barriers with bar code medical administration (BCMA) come as a result of nurses bypassing bar code BCMA due to equipment issues. The main equipment being computer and scanning devices are the problems in that nurses are lacks sufficient know how on how to use the equipment. This also happens because of lack of adequate training for users (nurses). Therefore lack of knowhow becomes the major cause of all these barriers mentioned above to larger extent. The issues of insufficient know how for the use of equipment makes it apparent that it not really the problems with NDC number on the medication is not being correct to result users’ failure in scanning the medication. Therefore, a database model has been created consisting of relevant entities for the purpose of solving the barriers mentioned above.
References
Barbara Voshall, D. N. P. (2012). Barcode Medication Administration Work-Arounds: A Systematic Review and Implications for Nurse Executives. Diabetes.
Taliercio, V., Schachner, B., Borbolla, D., Luna, D., Villalba, E., & Quiros, F. (2014). The expectations of nurses about the implementation of a barcoded medication administration system: a qualitative study. Studies in health technology and informatics, 205, 191.
Wang, X., Luo, Y., Shang, M., Li, Z., Zhang, M., & Sun, Z. (2015, January). Application of Mobile Nursing Information System in High-quality Nursing. In International Conference on Education, Management, Commerce and Society (EMCS-15). Atlantis Press.
Appendices
Appendix1: Conceptual data model
Summary information
Clients/Patient particulars
Nurses and/or doctor’s particular or information
Medicine information
Hospital Information
Appendix 2: Entity Relationship Diagram (ERD)
Confidentiality Rule for Defense Attorneys
Name
Professor’s name
Course
Date
Confidentiality Rule for Defense Attorneys
Confidentiality is the most important rule that defense attorneys must practice in their mandate of representing the clients. Attorney-client privilege is a rule which protects the confidentiality of oral and written conversations between clients and their attorneys. In line with this rule, defense attorneys are not permitted to divulge clients’ secrets, and neither can other parties compel them to. This rule encourages clients to share information freely with their lawyers for effective representation. Defense attorneys cannot reveal the content of their conversations without their clients’ informed consent. This rule applies to both private attorneys and public defenders. There are situations where attorney-client privilege does not apply and confidentiality can be waived. An example is if the defendant and their client lack reasonable expectations of privacy in a place where they are having the conversation. If other people overhear a conversation that was not audible enough that they were having in a public place, then it is grounds to testify the contents of their conversation in a court of law. At times this law can apply if a client discusses their case over cell phone in a private area.
Conflicts of interest tend to be endemic for majority of prosecutors’ discretion. For prosecutors, conflicts of interest are decisions that form the primary source of abuse and misconduct. Decisions made by prosecutors tend to be riddled with complex beliefs, interests, and motivations that have the ability to make them stray from their duty to make execute justice. On the other hand, conflicts of interests of defense attorneys because they can only be raised after trial. For instance, in a case of co-defendants, if one criminal defense attorney happens to represent two defendants with adverse interests in the same case, this would be a clear case of conflict.
Database Manipulation Normalisation is the process by which one breaks down the files into tables in order to create the data
Database Manipulation
Introduction
Normalisation is the process by which one breaks down the files into tables in order to create the database. There are three to four steps which are followed when normalizing a table. The first step is the First Normal Form (1NF), the second type of normalization is the Second Normal Form (2NF), the third form is Third Normal Form (3NF), lastly is the Boyce-Codd Normal Form (BCNF). There are other forms of normalization although, they are rarely used. This paper tries to analyze how one can break down the files into the table for the sake of creating a database (Churche, 2007). Database is said to be normalized if only it is in 3NF.
First Normal Form (1NF)
The following rules are followed when normalizing a table in the 1NF for an organized database. The first step involves the eliminating of the columns which are in the same table; the second step is to create a separate table for every group of the related data then identifies every row with the unique columns that is the primary key. The tables in Community library database have not met the requirement of the 1NF, 2NF, and 3 NF since different columns in the tables has been repeated. The columns of the table repeatedly include the column of the data type, length and descriptions. This table can be created as a one table as shown below;
Field Name Data Type Length/Format Description
Customer ID Number Primary Key
First Name Text 20
Last Name Text 20
SSNoText Standard length Social Security Number
Address Text 50 City Text 15 State Text 15 ZipCodeText 6 Phone Text 13 Email Text 30 DOB Date Standard Date of birth
DOA Date Standard Date of Application
Checkout ID Number Primary Key
Customer ID Number Foreign Key
ItemAcquiredText 30 Foreign Key. ID of Book/CD acquired for checkout
ItemTypeText 1 1 for book and 0 for CD
ItemTitleText 50 ItemGenreText 30 Description Text 200 Edition Text 15 YearofPubText 5 Year of publication
Second Normal Form (2NF)
This step addresses a concept of removing data which are repeated in a given table. It has rules which must be followed during normalization. The first step is making sure that the requirements in the first normal form are met. Secondly, remove the subsets of data which multiples the rows of the table then place the data in different tables. The third step is creating the relationships between the tables as well as, predecessors by use of the foreign keys (Coronel, 2011).
Field Name Data Type Length/Format Description
Customer ID Number Primary key
SSNoText Standard length Social Security Number
ZipCodeText 6 ItemTypeText 1 1 for book and 0 for CD
Customer ID Number Foreign Key
Description Text 200 YearofPubText 5 Year of publication
Third Normal Form (3NF)
This form goes more steps further. One must have to meet the requirements of the second normal form, and then remove columns which depend upon a primary key.
Apply SQL to create tables
CREATE TABLE Customers(P_Id int,LastName varchar(255),FirstName varchar(255),Address varchar(255),City varchar(255))
Conclusion
Data should always be organized properly in the database. It is done by creating tables as well as, establishing the relationships between the tables in regard to the rules designed to protect the data and to make database to be flexible by removing the redundancy as well as, inconsistent dependency. Redundant data is known to be wasting the disk space as well as, creating the maintenance problems. If the data which exists in many places must be changed, the data must be changed in precisely to the same way in all locations.
References
Churcher, C. (2007). Beginning database design. New York: Apress ;.
Coronel, C., Morris, S., & Rob, P. (2011). Database systems: design, implementation, and management (9th ed.). London: Course Technology Cengage Learning. Ling, T. W., Lee, M. L., & Dobbie, G. (2005). Semistructured database design. New York: Springer.
