ALL-IN-CARE

ALL-IN-CARE is a C# desktop application that unifies the services a patient normally has to chase separately. A patient can book a consultation without travelling to the hospital to channel a doctor, receive a prescription electronically, order the medicine against that prescription, and have it delivered to their door rather than queueing at a pharmacy counter.

Routine healthcare imposes a disproportionate amount of logistics on the patient, and the fragmentation compounds it. Channelling, prescription and dispensing are handled by separate organisations with no shared record, so the patient becomes the integration layer, carrying information between them. ALL-IN-CARE removes that burden by putting the four parties who actually need to coordinate inside one system with one shared record.

The application is built around four distinct user roles (patient, doctor, pharmacy and delivery rider) each with its own authentication path, home screen and workflow, all sharing one codebase and eighteen database tables. The roles interlock rather than sitting side by side: a doctor releases a prescription, that prescription appears in the patient’s order form as a selectable item fetched from the database, the patient chooses a partner pharmacy by delivery city, the pharmacy sees the order, and the rider sees the delivery. Each handover is a database transition rather than a manual step.

The most valuable engineering decision was populating selectors from the database rather than accepting free text, which removed whole classes of invalid input, most importantly the possibility of ordering against a prescription that was never issued.

What I contributed

• Interface design, all twenty-one forms: sole owner of the design phase across every form in the application: home, login, channelling, pharmacy checkout, contact, the seven patient screens, the three doctor screens, all four sign-up routes, other login, pharmacy and rider
• Six database tables: implemented Patient, Patient Records, Today Channels, Current Channels, Pharmacy Stocks and Rider Deliveries, spanning the identity, scheduling and fulfilment groups
• Eight forms wired and coded: connected the database and implemented behaviour for Channel Now, Doctor Details, Appointments, Payment Details, Today Channels, Sign Up Pharmacy and Sign Up Rider, and shared the Patient form with both other members
• Joint work: the initial system discussion, the database modelling session, the system-wide error-checking pass, and the design of the entity relationship, class and use case diagrams