baristure/healthconn

HealthConn

Built by HackItOrion Team

Healthconn breaks the communication difficulties between doctors and patients.

• Effective booking flow
• Easy complaint explanation
• Multilanguage support
• ✨Many other things

Tech Stack

HealthConn uses a number of popular tools to work properly:

• ReactJS
• Redux, Redux-Toolkit, Thunk and Persist
• TailwindCSS
• AWS Lambdas
• TypeScript
• PostgreSQL
• Github

License

MIT

healthconn's Issues

Services and doctor cards and endpoints

Please create these cards as we speak

Refactor login page styling

Please take as a reference to the register page as a design pattern

Create Db Migrations

We destroy the stacks when we've done with testing so every time we need to test something we have to create db tables again and again. Instead of this we should implement a programmatic db migration system like liquibase, flyway etc.

Greetings page

Doctor Entity Related Functions

Those functions should be implemented:

• get doctor by id
• get doctor by email

User Repository and DTO objects should be updated

Hi. Initially we had copy/pasted the boilerplate code. But our business requirements requires additional fields in the db for user entity. Related DTOs, repository functions and lambda functions should be updated.

We may need to add prefix for backend endpoints like *api*

If we serve backend and frontend in the same domain we need to define a prefix for backend endpoints.

Update Register Functions

We decided to split user table to doctor and patients tables, so register function should be updated to receive patient specific informations.

Appointment related endpoints

GET /appointments

POST /appointments
Create a new appointment
payload

`{
"date": "2022-11-30T12:00:00.000Z",
"complaints": [
{
"part": "head",
"side": "front",
"severity": "3",
"comment": "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
},

],
"userId": null,
"doctorId": null,
"serviceId": null,
}`

GET /appointments/:appointmentId
response

{ id:"", user: { first_name: "John", last_name: "Doe", gender: "Male", blood_type: "A+", birth_date: "21.03.1991", weight: 95, height: 1.9, story: "Nisi eiusmod est ut commodo aliqua non sunt ipsum consectetur voluptate laboris. Ea pariatur officia enim non in ex ad ipsum officia ipsum minim anim enim. Adipisicing labore sint Lorem adipisicing minim minim nulla id Lorem amet. Officia laboris sint ea elit dolore excepteur. Lorem magna et ea aliquip aliquip ut irure anim excepteur excepteur nisi eu amet. Officia culpa aute ullamco elit ullamco proident duis excepteur. Officia ipsum reprehenderit tempor aute exercitation.", }, date: new Date(), service: { name: "Cardiology", }, doctor: { first_name: "Jane", last_name: "Doe", title: "Prof. Dr.", office_number: "12312345", location: "Floor 2, No:25", }, complaints: [ { part: "head", side: "front", severity: 6, comment: "Deserunt esse sint enim occaecat minim.\n Duis quis sint dolor veniam aute Lorem nisi consequat eu excepteur elit reprehenderit anim.", }, { part: "right_hand", side: "back", severity: 2, comment: "Deserunt esse sint enim occaecat minim.\n Duis quis sint dolor veniam aute Lorem nisi consequat eu excepteur elit reprehenderit anim.", }, ], recognization:"" }

PUT /appointments/:appointmentId
payload
{appointmentId:"1234", recognization:"Deserunt esse sint enim occaecat minim.\n Duis quis sint dolor "}

update profile

PUT /profile

Newman integration

Service related endpoints

In order to get a list of available services, FE sends a GET request to /services and expects some of the data structure:
(I have found a pictures related to this list)

rest.get("/services", (req, res, ctx) => {
    const data = [
      {
        service_id: faker.random.numeric(5),
        name: "Radiology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Psychology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Pathology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Oral and Dental Health",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Sports Medicine",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Hematology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Gastroenterology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Endocrinology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Dermatology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Cardiology",
      },
      {
        service_id: faker.random.numeric(5),
        name: "Anesthesiology",
      },
    ];

After clicking on a particular service, FE sends a GET request to /services/:service (radiology, cardiology, etc) and receives the list of relevant specializations.
Example:

const data = [
      {
        id: number,
        first_name: string,
        last_name: string,
        office_number: number,
        speciality: string ("radiology"),
        rating: float (4.5)
        image_url: string,
        mobile_number: string,
      },
      ...
    ];

After clicking on the doctor's card, FE sends GET request /services/:service/:doctor_id and receiving a data:

const data = [
      {
        id: number,
        first_name: string,
        last_name: string,
        memberships: string[],
        publications: string[],
        resume: string,
        speciality: string,
        image_url: string,
      },
     ...
    ];

Complaint-Severity table need body side information

Enum("front", "back")

Doctors table need location information

We need to add the doctor's office location to the doctor's table for example "Floor 5 No. 22"

Update Register Page fields

Please add mobile phone number input to the fields, and update the validation object to match to the backend system.
our request payload seems like that
{
"first_name": "Baris",
"last_name": "Ture",
"email": "[email protected]",
"password": "Test1234",
"mobile_number": "[phone]",
"type": "patient"
}