This project is currently under active development. Core features have been implemented, and we are working on expanding functionality.
\nThis is an independent project, not a group effort.
\nThis is a Django-based healthcare appointment management system that allows patients to book appointments with doctors. It includes advanced user authentication, appointment scheduling, and doctor management. The project is continuously evolving, with more advanced features planned for future implementation.
\nCurrent Features-
\nUser Management: - Patient and Doctor registration and authentication
\n- Traditional username/password registration
\n- Google Sign-Up integration for easy access
\n- Email verification for enhanced security
\n- User profile management (edit profile, change password)
\n- Admin user management with distinction between social and traditional sign
\n-ups-
\nAppointment System:
\n- Create, view, update, and delete appointments
\n- Appointment status tracking (Scheduled, Completed, Cancelled)
\n- Doctor availability management
\n- Doctor Management:
\n- Doctor registration with specialization
\n- Doctor profile management- Admin Interface:
\n- Manage users, doctors, and appointments
\n- Distinguish between users registered via social auth and traditional methods
\nPlanned Features
\n- Patient Payment System
\n- Drug Booking and Ordering System
\n- Dispatch Management (Dispatch Company Registration)
\n- Real-Time Chat Functionality
\n- AI Chatbot Integration
\n- Enhanced Admin Dashboard
\n- User Feedback and Rating System
\n- Notifications System
\nTechnologies Used
\n- Django
\n- Django Rest Framework
\n- SQLite (default database)
\n- Google OAuth for social authentication
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"36548151","collectionId":"11bbe9ac-bdc2-4af9-b755-af0dbb060db5","publishedId":"2sAYBUCXPR","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2024-11-23T03:00:29.000Z"},"item":[{"name":"create patient","event":[{"listen":"test","script":{"id":"2b85485e-31e5-4f87-8bc6-64bf762ea711","exec":["pm.test(\"Successful POST request\", function () {"," pm.expect(pm.response.code).to.be.oneOf([200, 201]);","});",""],"type":"text/javascript","packages":{}}}],"id":"4dacb465-f59f-4a07-b7fd-d93ca4a8cd22","request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"username","value":"marama","type":"text"},{"key":"email","value":"marama@gmail.com","type":"text"},{"key":"password","value":"test12345","type":"text"},{"key":"password_confirm","value":"test12345","type":"text"},{"key":"is_patient","value":"True","type":"text"},{"key":"image","type":"file","fileNotInWorkingDirectoryWarning":"This file isn't in your working directory. Teammates you share this request with won't be able to use this file. To make collaboration easier you can setup your working directory in Settings.","filesNotInWorkingDirectory":["/C:/Users/MELVIN/Pictures/WhatsApp Image 2022-10-25 at 5.39.05 AM[boye].jpeg"],"src":"/C:/Users/MELVIN/Pictures/WhatsApp Image 2022-10-25 at 5.39.05 AM[boye].jpeg"},{"key":"date_of_birth","value":"2024-11-1989","type":"text"}]},"url":"http://127.0.0.1:8000/api/register/","description":"This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.
\nA successful POST request typically returns a 200 OK or 201 Created response code.
This is a PUT request and it is used to overwrite an existing piece of data. For instance, after you create an entity with a POST request, you may want to modify that later. You can do that using a PUT request. You typically identify the entity being updated by including an identifier in the URL (eg. id=1).
A successful PUT request typically returns a 200 OK, 201 Created, or 204 No Content response code.
This is a DELETE request, and it is used to delete data that was previously created via a POST request. You typically identify the entity being updated by including an identifier in the URL (eg. id=1).
A successful DELETE request typically returns a 200 OK, 202 Accepted, or 204 No Content response code.