How to best create connections for a booking app?

Admin 1
Viewed 295

I am new to Django and relational databases coming from the Firebase world. I am having trouble figuring out the best modeling for a Doctor-Patient booking app and generally how relational DBS works best; I would like to minimize future problems by doing a great job now. I am going to use Django and Django Rest Framework at the backend to feed a React frontend.

So far, I've created these models in a clinic app. Patients and Secretaries are going to be part of the users, and so are Doctors. I then create the Serializers and Viewsets for the API.

class Clinic(models.Model):
    name = models.CharField(max_length=200)
    description = models.TextField()
    accepted = models.BooleanField(default=False)

class Doctor(models.Model):
    clinic = models.ManyToManyField(
        Clinic, related_name="doctor")  
    first_name = models.CharField(max_length=200)
    last_name = models.CharField(max_length=200)
    email = models.EmailField(max_length=240, default="email")
    appointment_duration = models.IntegerField(default=20)

class Secretary(models.Model):
    clinic = models.ForeignKey(
        Clinic, on_delete=models.CASCADE, related_name="secretary")  
    name = models.CharField(max_length=200)
    email = models.EmailField(max_length=240, default="email")
    doctors_responsible_for = models.ManyToManyField(Doctor)

class Patient(models.Model):
    first_name = models.CharField(max_length=200)
    last_name = models.CharField(max_length=200)
    email = models.EmailField(max_length=240, default="email")
    date_of_birth = models.DateField()
    age = models.PositiveIntegerField(default=0)
  1. Should I create a User model to be able to differentiate users (Doctors, Secretaries and Patients)? They are all going to be able to register and log in and each will see different things on the page. Should I just return 'is_doctor' or 'is_secretary' from the serializer API and show different content from there?

I'm confused as to how I would connect a User model with a Doctor or Secretary model, for example, or if I even need to since they're all users...

  1. How would I differentiate users (Doctor, Secretary, Patient) at the registration moment? E.g., for each of them to have a different registration form with a boolean for is_doctor, is_secretary?

  2. I can't to come up with a solution for storing booked appointments. I'm wondering if I should create a new model, Bookings, for saving bookings but I'm not sure if this booking model should hold every single booking (from any patient to any doctor), considering this app will be used by a lot of people. Or should bookings be under each patient and each doctor?

In this case, secretaries will also be able to manually add bookings to a Doctor calendar and add the patient as well.

  1. I am building all of this in a single app, clinic, perhaps it is recommended to create different apps for this?

  2. Each doctor will need to have its own calendar for this app to work, with say, 'day 12, blocks of 20mins from 09:00 to 11:30'. Should I create a Calendar model? Or how is it best to achieve this? How to best come up with this model? This calendar will be populated with blocks of time from whatever each doctor chooses as their availability.

django-rest-framework orm django-models django database
2 Answers

First of all, I'm a django noob, so please read the following with that it mind.

Looks pretty good - the only thing I see missing is how you link patients to clinics and or doctors.

The other thing I notice is how doctors can have multiple clinics. I assume each clinic has its own calender, rather the doctor itself? Or maybe both? i.e. Even if a doctor was available on his calendar, he might not have a room at the clinic for the patient as other doctors' calenders would clash with it.

Personally, I wouldn't create a new app for clinic unless you want to model it in far more detail. Keep it simple initially.

Also, if you're allowing doctors, secretaries, and patients to login to your site, it might be better to have consumer/provider class model descending from custom user. ideas...

I would start thinking about the problem in more abstract terms. Service/provider/consumer.

But, I think you're on the right track.

user_102881700

I can throw in some ideas.

Models

I think you are on the right track. You just need to associate models Doctor, Secretary and Patient to the User model. I would recommend you to create a custom user model inherited from AbstractUser. In this model, you can either add a choice field with choices for each type of user. link to docs

Also, you need to link the user model with the correct model.

  1. One way to do is to have a OneToOneField for the user model in all your user type models: Doctor, Secretary, Patient
  2. Or you can explore generic relations. It will further streamline things for you. link to docs.

Signup

You can provide a field for users to select at the time of signup, or provide separate links to signup and handle things at the backend. Something like If you are a doctor, click here to signup. In both cases, you'll need to override the signup process.

So a signup link can look like: /signup/doctor/ or /signup/patient/. All signup will be using the same view, just different url kwargs. link to docs

You can just create rows on the relevant model for user type on form success.

Booking

Yes, you need to create a separate model, and you can store all your bookings in this model. Doesn't matter how many users use your app. Just use a good database solution, like Postgres. There are ways to optimize your queries, like indexing, don't worry about it for now. Just make sure to save all references like, patient, doctor, created, last modified, created by which user, from_datetime, to_datetime, etc.

It would be better to handle the 20 min appointment blocks in forms.py. You can create a list of acceptable time blocks, so that if in future you want to change this time to say 30 min, its easily doable. Just handle all validations at the form level and it should do the trick.

user_41860080
Related