Yes
The database is created for supporting a healthcare organization to record the diseases and patient database. The database is supposed to be storing the data of the diseases, patients and which patient has diagnosed with which diseases. The spread sheets are very error prone and time consuming. Finding results from a spread sheet is a complex work that everyone does not understand. For this reason, the database is implemented. It will provide the doctors and other staff of the organization a simple interface to interact and easy communication medium. The database is developed also with the purpose of allowing the doctors to find the treatment related information very easily. As the RDBMS is based on establishing relationships among the entities, the developed database in Microsoft Access will be extremely useful for the organization.
The database will run the query of identification of the patient and diseases name based on the most frequent diseases from a certain date to year end. This query combines both the patient and diseases entities. These entities together provide the details of the diseases frequency information. This query is based on the referential integrity between patient and diseases. If the referential integrity is correctly formed, then finding the result would be possible otherwise the database cannot support the basic need of the query.
The ER diagramming has been followed for designing the database of the system. As the name suggests, it is based on entities and relationships and these two things are only focused on in this project. An ERD or entity relationship diagram can be referred to as the graphical visualization of information system in terms of data used and processed in the system. Through the ER Diagram, the entities like diseases and patient is created. The definition of the model states that a real world system does not support any many-to-many relationship. After designing the many-to-many relation among the diseases and patient, it was not possible to correctly represent the patient and diseases relation properly without data anomalies. Therefore, as per the instructions of the ER diagram development, a bridge table is created to support the relation and convert the many-to-many into one-to-many.
The first entity is the diseases itself. This entity has a primary key named as ‘ID’. This is an auto number which means every time a new row is created it will updated automatically. No two auto numbers are same in the same entity. This number is not implemented for give meaning to the entity, it is here for providing structural support to the entity. The entity has no such attribute that will have different value for each row, therefore this ID is used as primary key. The other filed is the name. This name will be used in the real world practice like in prescription or bills instead of ID. The diseases has symptoms, tests, primary treatments and all these information can be easily captured using the attributes of the entity. Each row of the entity just hold the information of each diseases.
The second entity is the patient. The patient entity is developed for the purpose of storing the patient details and the details of their treatment. This entity has a primary key named as ‘ID’. This is an auto number which means every time a new row is created it will updated automatically. No two auto numbers are same in the same entity. This number is not implemented for give meaning to the entity, it is here for providing structural support to the entity. The entity has no such attribute that will have different value for each row, therefore this ID is used as primary key. The name of the patient will be used in the prescription but in the bills, the ID will also be present. This entity has a diseases foreign key to store the diseases that it had. This makes the whole entity prone to data anomaly. It is fine until one patient is diagnose with a different diseases second time. This time the same patient has to be created again to just store the diseases ID. This is the issue many-to-many relation can create in real world. However, a bridge table can easily handle this issue.
It is possible to state that the diseases name and ID also the patient name and ID can determine each other.
ID à name
name à ID , for both the entities as these two attributes are same in patient and diseases entities. However, this condition does not apply when two names are same but ID is different. Therefore, only the universal condition will be considered and that is ID determines the name. As ID is primary key, it cannot same for two or more rows.
ID à name.
Like the name attribute, the other attributes also have dependency on the primary key. It is shown in the below.
ID à name, primaryTreatment, possibleTests, mainMedicines, symptoms
ID à name, residentialAddress, contactNumber, emailAddress, emergencyContactNumber, contactPersonName, diseases
Now the issues is with the diseases attribute in the patient entity. If it is considered that all attributes are in one entity and there is no normalization then dependency would be like following.
diseasesID, patientID à diseases
As the above functional dependency suggests, the diseases is dependent on both the primary keys.
patientID à patientName, residentialAddress, contactNumber, emailAddress, emergencyContactNumber, contactPersonName, diseases, diseasesName, primaryTreatment, possibleTests, mainMedicines, symptoms
diseasesID à diseasesName, primaryTreatment, possibleTests, mainMedicines, symptoms, diseases
So the transitive dependency is existed through the diseasesID.
The diseases and patient entities have many-to-many relationship among them. It is because, the patient can be diagnosed with the different disease next time he/she comes for checkup. On the other side, more than one patient can be diagnosed with same diseases.
a) First Normal Form:
Suppose the table is like HealthCare (patientID, patientName, residentialAddress, contactNumber, emailAddress, emergencyContactNumber, contactPersonName, diseasesName, primaryTreatment, possibleTests, mainMedicines, symptoms)
Now the diseases related attributes have to be multivalued. The primary condition for being in first normal form is no multivalued data should be present in the database. Therefore the new table must have atomic valued attributes. This means, for each diseases, the patient details will be repeated.
The table must not have any partial dependency to be in the second normal form. The partial dependency is as shown below.
diseasesID à diseasesName, primaryTreatment, possibleTests, mainMedicines, symptoms, diseases
The dieasesID is not a primary key but other non-key attributes is dependent on it. Two tables are created diseases and patient. The tables are as following.
Patient (patientID, patientName, residentialAddress, contactNumber, emailAddress, emergencyContactNumber, contactPersonName, diseases)
Diseases (dieasesID, diseasesName, primaryTreatment, possibleTests, mainMedicines, symptoms)
The diseases act as the foreign key.
The entity must not have any transitive dependency. However, it is already shown the transitive dependency remains through dieasesID. If it is removed then following entities are created.
Patient (ID, name, residentialAddress, contactNumber, emailAddress, emergencyContactNumber, contactPersonName)
Diseases (ID, name, primaryTreatment, possibleTests, mainMedicines, symptoms)
PatientDiseases (patientID, diseasesID, startDate, endDate)
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.
Greenstein, M. A., Grunin, G., Schwenger, M. N., & Swamikrishnan, P. (2018). U.S. Patent Application No. 15/837,211.
Setiaji, B., & Wibowo, F. W. (2016). Chatbot using a knowledge in database. In 7th International Conference on Intelligent Systems, Modelling and Simulation.
We provide professional writing services to help you score straight A’s by submitting custom written assignments that mirror your guidelines.
Get result-oriented writing and never worry about grades anymore. We follow the highest quality standards to make sure that you get perfect assignments.
Our writers have experience in dealing with papers of every educational level. You can surely rely on the expertise of our qualified professionals.
Your deadline is our threshold for success and we take it very seriously. We make sure you receive your papers before your predefined time.
Someone from our customer support team is always here to respond to your questions. So, hit us up if you have got any ambiguity or concern.
Sit back and relax while we help you out with writing your papers. We have an ultimate policy for keeping your personal and order-related details a secret.
We assure you that your document will be thoroughly checked for plagiarism and grammatical errors as we use highly authentic and licit sources.
Still reluctant about placing an order? Our 100% Moneyback Guarantee backs you up on rare occasions where you aren’t satisfied with the writing.
You don’t have to wait for an update for hours; you can track the progress of your order any time you want. We share the status after each step.
Although you can leverage our expertise for any writing task, we have a knack for creating flawless papers for the following document types.
Although you can leverage our expertise for any writing task, we have a knack for creating flawless papers for the following document types.
From brainstorming your paper's outline to perfecting its grammar, we perform every step carefully to make your paper worthy of A grade.
Hire your preferred writer anytime. Simply specify if you want your preferred expert to write your paper and we’ll make that happen.
Get an elaborate and authentic grammar check report with your work to have the grammar goodness sealed in your document.
You can purchase this feature if you want our writers to sum up your paper in the form of a concise and well-articulated summary.
You don’t have to worry about plagiarism anymore. Get a plagiarism report to certify the uniqueness of your work.
Join us for the best experience while seeking writing assistance in your college life. A good grade is all you need to boost up your academic excellence and we are all about it.
We create perfect papers according to the guidelines.
We seamlessly edit out errors from your papers.
We thoroughly read your final draft to identify errors.
Work with ultimate peace of mind because we ensure that your academic work is our responsibility and your grades are a top concern for us!
Dedication. Quality. Commitment. Punctuality
Here is what we have achieved so far. These numbers are evidence that we go the extra mile to make your college journey successful.
We have the most intuitive and minimalistic process so that you can easily place an order. Just follow a few steps to unlock success.
We understand your guidelines first before delivering any writing service. You can discuss your writing needs and we will have them evaluated by our dedicated team.
We write your papers in a standardized way. We complete your work in such a way that it turns out to be a perfect description of your guidelines.
We promise you excellent grades and academic excellence that you always longed for. Our writers stay in touch with you via email.