Health Care and History — Project Documentation

Health Care and History — Project Documentation سا مي محمد@ · 2026 26, Oct Project Overview Health Care and History is a website (with a mobile app to follow) that lets any person keep their medical history in one organized place, so they no longer depend on memory when a doctor asks about past illnesses or current medications. Item Detail Project name Health Care and History Team Team 1 Platform Website first; mobile application later Problem Patients often forget past illnesses, current medications, and other important details. Solution One app where the user records and stores past illnesses, medications, medical history, and personal data. Target users Everyone, across all segments of society Authorized specialists Physician, pharmacist, paramedic Data collected National ID, personal photo, contact details, past illnesses, medications, medical history (fingerprint is added later, with the mobile app) The project is planned to be carried out with the relevant government bodies (Ministry of Health, Ministry of Communications, Ministry of Interior), who would be asked to approve and adopt it. Official procedures and the type of approval are not yet defined. Project Planning The plan is to build the first version as a website that stores a user's medical history and shows it to authorized specialists, then submit it with documentation and a demo by 31 October 2026. The mobile app follows in a later phase. Objectives •Give every user one organized place for their medical history. •Make past illnesses and medications easy to remember and easy to find. • Let a physician, pharmacist, or paramedic see the key information when needed. • Protect the data and control who can access it.Scope In scope (first version) Out of scope (future) Sign-up and login with national ID Official approval from government bodies Profile with photo and contact details Integration with hospital or ministry systems Recording past illnesses and medications Advanced reports and analytics Viewing the full medical history Reminders and notifications Access for physician, pharmacist, paramedic, with patient lookup by national ID or QR code Mobile application, with fingerprint lookup Phases 1. Requirements and stakeholder analysis. 2. Design: database and UI/UX. 3. Development of the website and backend. 4. Testing and fixes. 5. Documentation, demo video, and submission (due 31 October 2026, 12:00 AM). 6. Future: mobile app (with fingerprint lookup), government approval, and wider rollout. Risks Risk Impact Mitigation Sensitive medical and ID data is exposed High Encrypt data, require login, limit access by user role. Government approval is slow or not granted High Present the app as a pilot first and plan approval as a later phase. Users enter incomplete or wrong information Medium Use structured forms and required fields. Short time before the deadline Medium Build a small first version and leave the rest for later. Stakeholder Analysis Users and government bodies matter most: users supply the data and trust the app with it, and government approval decides whether the project can run in practice. Stakeholder Role in the project Main interest Interest Influence Patients (all users) Create and maintain their own medical history Keep history organized, available, and private High HighStakeholder Role in the project Main interest Interest Influence Physician Reads patient history during care Fast, clear view of past illnesses and medications High Medium Pharmacist Reads current medications Avoid mistakes when dispensing High Medium Paramedic Reads key history in emergencies Quick access to critical information High Medium Ministry of Health Planned approving and adopting body Safe, regulated use of medical data Medium High Ministry of Communications Planned approving and adopting body Secure, reliable digital service Medium High Ministry of Interior Planned approving and adopting body Correct handling of national ID data Medium High Team 1 Designs and builds the app Deliver a working, well- documented project High High Course instructors Review and grade the submission Complete documentation, code, and demo Medium High How to engage them •High interest, high influence (patients, Team 1): involve closely and design around their needs first. •High interest, medium influence (physicians, pharmacists, paramedics): consult them on what information they need to see. •Medium interest, high influence (ministries, instructors): keep informed and meet their requirements before launch. Database Design The database has one USER table, and three tables (illness records, medications, access log) that all link back to it.entity-relationship diagram · 4 tables One user has many illness records and many medications. ACCESS_LOG records which specialist opened which patient's history, and when. Table Purpose USER Identity and contact data (national ID, photo, fingerprint, phone, email) and the user's role: patient, physician, pharmacist, or paramedic. ILLNESS_RECORD One row per past illness of a patient. MEDICATION One row per medication a patient takes or took, with dose and dates. ACCESS_LOG One row each time a specialist views a patient's history. The fields above are a proposal for the first version. National ID, photo, and fingerprint are sensitive, so they should be stored encrypted; the exact method is still to be decided. The QR code is generated from the user's ID, so it needs no column of its own. The fingerprint column is used from the mobile app phase, because a website cannot read a fingerprint without special hardware. UI/UX Design The app should be simple enough for anyone to use: a patient logs in, lands on Home, and reaches illnesses, medications, and profile in one click.user flow · patient and specialist A patient signs up or logs in with their national ID, then uses Home to open one of three screens. A specialist logs in with their own role, finds the patient by national ID or QR code (fingerprint comes with the mobile app), and opens the patient's history. Screen Used by What it shows Sign up / Log in Everyone National ID, and at sign-up the personal photo and contact details Home Patient Entry to illnesses, medications, and profile My illnesses Patient List of past illnesses; add and edit My medications Patient Medications taken, with dose and dates; add and edit My profile Patient Personal data, contact details, and the patient's QR code Patient lookup Specialist Field to find a patient by national ID or QR code scan (fingerprint in the mobile app) Patient history Specialist The patient's past illnesses and medications Design principles • Simple: the app is for all segments of society, so each task takes few steps and clear labels. •Clear: past illnesses and medications are visible at a glance, newest first. •Private: login is required, and the user's role decides what they can see.