it has two parts which is 3A and 3B. you have to provide me part A this sunday night by using the mentioning software. it all mention there. in fact i highlighted some parts.
because last time ur writer blame me that ididnt tell about the software but it was all mention in the document. which clearily shows he didnt go through serious.
this is the template where he has to answer. basically there is scenario given and on basis of that he has create a EERD which is a diagram.
part B i will ask todo next week. But these are related to each other. beacuse on te basis of part A we have to create data which is part B.
so th writer needs o planned from now.
i think i have clear everything to u.
if uhave any doubt.
he has do it on online server which is ‘phpmyadmin’ last tim i have provided my login detail. but he didnt do anything. but this time i am telling u now.
this is ma friend work from last session.
but DONT take it 100%. he missed few things.
take it as sample. please
by the way please do let him know that we have been taught this book Database Concepts, 7th edn, Pearson Education, New Jersey, USA.
The database system developed in this paper is of a scenario of the telemedicine in a healthcare facility. On admission, the patient’s and the Contact person’s records are taken, tests are done by a medical practitioner and are recorded in the information systems, as well as the prescription and visit dates. Further, details of the visit data are recorded in different class. The different classes of necessity are accessible and interconnected in the system to the administration and the respective clinicians. The classes in this EERD diagram have respective subclasses that are necessary for its database management.
The EERD diagram below has been created on LucidChart, with the entities and relationships well indicated. The database enhances process flow, information storage and information availability to reduce medical error. The development of this database system is poised to heighten patient-clinicians satisfaction through reducing the treatment timeline in the entire cycle by enhancing the relationships of different entities in the healthcare facility and thus enabling information coordination and exchange in a single cycle. The database developed in oriented towards out-patients only.
Fig 1: EERD for telemedicine in a hospital facility.
The client rules for this facility are:
- Every patient’s details must be fed in the database before treatment process can be initiated.
- Clinicians who attend to a client patient from the first visit are expected to be the ones to monitor their progress over time throughout the treatment. However, in case of unavailability of specific physicians and attendance has to be by another, duty transfer procedures are initiated. In such a case, the system is accessed through the administration for entirety.
- Administration is supposed to take information of patients and doctor from time to time, being the patrons of information exchange or custodians of all the information in the facility.
- Every out-patient in contact with the facility should at least have a contact person. Failure to this, patients are admitted for inpatient care. This is influenced by the fact that the facility is referral and deals with ambulatory patients.
- Every test and prescriptions have to be documented and uploaded in the system for future reference.
- Visit data are meant to ease the load of searching medical information (Therefore they are stored separately from the visit description class. The entities, though, relate to each other to each other in case of referral treatment).
Contact persons are to be contacted strictly by the administration through the call office in cases of needs, unless urgency demands otherwise.