Descrição do projeto
A database for coursework written in MySQL, PHP is required.
Base requirement.
The database serves to serve patients of the medical center. A clear Russian standard interface, consisting of windows, buttons and tabs, should be easy to master even for an inexperienced user.
Creating tables with the necessary criteria, links and queries.
There must be authorization for the administrator, registrar and honey. Staff, patient review mode.
Tables and their contents.
Initially, the database already stores a list of doctors who work in the medical center. Each doctor has its own unique number (ID), and also in the database his specialty, surname, name, patronymic, number of medical book are indicated. (Table honey). Staff).
The database contains separate patient records. Their surname, name, patronymic, gender, date of birth, Nopolis, NoSNILS, diagnosis, attending physician are prescribed. They also have their own unique ID number. (Table. Patients.
Separately, a form of diagnoses is created, including the No of diagnosis, name, ID of recommended drugs. (Table. Diagnosis.
Next, a form of drugs containing the No of the drug, name, indications, contraindications, side effects, methods of use is created. (Table. Drugs.
The following data are used: inspection number, place, date of examination, doctor ID, patient ID, Nodiagnosis, Nodrug, special prescriptions. (Table. Inspection.
The Registrar table stores his individual number, surname, name, patronymic.
Authorization.
The administrator authorization must be carried out by password. The password must be edited and changed in the administrator section.
Authorization of the registrar occurs by individual ID and individual password access in the bundle. Passwords should be stored separately in the database, and edited in the mode of a particular person.
Authorization of personnel occurs by individual ID and individual password access in the bundle. Passwords should be stored separately in the database, and edited in the mode of a specific person of the staff.
The patient’s viewing mode is switched on with the simultaneous introduction of SNILS and policy No.
Distinction of rights.
(1) Administrator.
Can view all tables; edit, delete, add entries to them.
(2) Registrar.
Request for a sample by doctor - & gt; ID of a doctor, specialty.
Request for change, addition of the patient -> patient ID, surname, first name, patronymic, gender, date of birth, Nopolis, NoSNILS, attending physician.
Request for change, addition of examination -> No examination, venue, date of examination, doctor's ID, patient's ID.
3) Honey. Staff.
Actions of the individual employee of the staff (under the ID entrance).
Request for a sample (by name of diagnosis or drug) -> see: No diagnosis, name of diagnosis, Nopreparation, Name of the drug, contraindications of the drug, method of use of the drug.
Request for a sample-> see: all of your patients (surname, first name, patronymic, gender, date of birth, diagnosis, place of examination, date of examination, name of the drug).
Request for sampling and modification of inspection (ID honey). The employee on the tab. Review) -> see: No examination, venue, date of examination, patient name, date of birth of the patient; change: Nodiagnosis, Nopreparation, special prescription.
(4) The patient.
Request for a sample of "Personal Data" - & gt; see: surname, first name, patronymic, gender, date of birth, Nopolis, NoSNILS, diagnosis.
Request for the sample "OSITION RESULT" - & gt; see: date of examination, place of examination, name and specialty of the attending physician, the prescribed diagnosis, special prescription, prescribed drugs (name), method of use of drugs, side effects.
Base requirement.
The database serves to serve patients of the medical center. A clear Russian standard interface, consisting of windows, buttons and tabs, should be easy to master even for an inexperienced user.
Creating tables with the necessary criteria, links and queries.
There must be authorization for the administrator, registrar and honey. Staff, patient review mode.
Tables and their contents.
Initially, the database already stores a list of doctors who work in the medical center. Each doctor has its own unique number (ID), and also in the database his specialty, surname, name, patronymic, number of medical book are indicated. (Table honey). Staff).
The database contains separate patient records. Their surname, name, patronymic, gender, date of birth, Nopolis, NoSNILS, diagnosis, attending physician are prescribed. They also have their own unique ID number. (Table. Patients.
Separately, a form of diagnoses is created, including the No of diagnosis, name, ID of recommended drugs. (Table. Diagnosis.
Next, a form of drugs containing the No of the drug, name, indications, contraindications, side effects, methods of use is created. (Table. Drugs.
The following data are used: inspection number, place, date of examination, doctor ID, patient ID, Nodiagnosis, Nodrug, special prescriptions. (Table. Inspection.
The Registrar table stores his individual number, surname, name, patronymic.
Authorization.
The administrator authorization must be carried out by password. The password must be edited and changed in the administrator section.
Authorization of the registrar occurs by individual ID and individual password access in the bundle. Passwords should be stored separately in the database, and edited in the mode of a particular person.
Authorization of personnel occurs by individual ID and individual password access in the bundle. Passwords should be stored separately in the database, and edited in the mode of a specific person of the staff.
The patient’s viewing mode is switched on with the simultaneous introduction of SNILS and policy No.
Distinction of rights.
(1) Administrator.
Can view all tables; edit, delete, add entries to them.
(2) Registrar.
Request for a sample by doctor - & gt; ID of a doctor, specialty.
Request for change, addition of the patient -> patient ID, surname, first name, patronymic, gender, date of birth, Nopolis, NoSNILS, attending physician.
Request for change, addition of examination -> No examination, venue, date of examination, doctor's ID, patient's ID.
3) Honey. Staff.
Actions of the individual employee of the staff (under the ID entrance).
Request for a sample (by name of diagnosis or drug) -> see: No diagnosis, name of diagnosis, Nopreparation, Name of the drug, contraindications of the drug, method of use of the drug.
Request for a sample-> see: all of your patients (surname, first name, patronymic, gender, date of birth, diagnosis, place of examination, date of examination, name of the drug).
Request for sampling and modification of inspection (ID honey). The employee on the tab. Review) -> see: No examination, venue, date of examination, patient name, date of birth of the patient; change: Nodiagnosis, Nopreparation, special prescription.
(4) The patient.
Request for a sample of "Personal Data" - & gt; see: surname, first name, patronymic, gender, date of birth, Nopolis, NoSNILS, diagnosis.
Request for the sample "OSITION RESULT" - & gt; see: date of examination, place of examination, name and specialty of the attending physician, the prescribed diagnosis, special prescription, prescribed drugs (name), method of use of drugs, side effects.
Desenvolvimento web Transferência bancária
