amigoscode/cohort-2-e

cohort-2-e's Issues

Create Emails API

User Story: As a developer, I want to be able to retrieve a list of all emails registered in the system

Acceptance Criteria:

Scenario 1: Retrieving a list of all emails

Given no query parameters

When I make a GET request to the API endpoint to retrieve a list of emails

Then the system should respond with a 200 status code and a list of all emails in the system.

Scenario 2: Retrieving emails details

Given an emailId as a path variable

When I make a GET request to the API endpoint to retrieve the email details

Then the system should respond with a 200 status code and email details data in the response body

Initiate backend CD workflow

Create frontend functionalities for sending Email

Add and populate .gitignore

Create Orders API

User Story: As a developer, I want to be able to retrieve a list of all orders in the system

Acceptance Criteria:

Scenario 1: Retrieving a list of all orders

Given no query parameters

When I make a GET request to the API endpoint to retrieve a list of orders

Then the system should respond with a 200 status code and a list of all orders in the system.

Scenario 2: Retrieving orders details

Given a orderId as a path variable

When I make a GET request to the API endpoint to retrieve the order details

Then the system should respond with a 200 status code and order details data in the response body

Write tests for Provider entity

Determine values for Status and State

Write tests for Orders entity

Create frontend view for schedule list

Create view to update schedule

Create functionality to autogenerate email order when Approved by Medical doctor is issued

The order entities are created in the moment that the Medical doctor Approves the schedule so the status "Approved By Medical Doctor And Email Sent" is issued.

Initiate application database

Add Postgres docker dependency
Create database
Create flyway files

Add clean architecture structure to the project

Dockerize backend

Add services for pgadmin and postgres database

Create frontend functionalities for Email entity

Initiate BloodBank project frontend

Change schedule list priority order based State

1. Delete Status from Model and database
2. Update State ENUM values and filed in database

TECHNOLOGIST : TO REVIEW BY TECH,
MEDICHAL DOC : REVIEWED BY TECH

Design User API

Create Patients API

User Story: As a developer, I want to be able to retrieve a list of all patients registered in the third party system

Acceptance Criteria:

Scenario 1: Retrieving a list of all patients

Given no query parameters

When I make a GET request to the API endpoint to retrieve a list of patients

Then the system should respond with a 200 status code and a list of all patients in the system.

Scenario 2: Retrieving patients details

Given a patientId as a path variable

When I make a GET request to the API endpoint to retrieve the patient details

Then the system should respond with a 200 status code and patient details data in the response body

Add Spring Security

Generate JWT token
Add authentication
Add security

Add flyway to manage database

Initiate backend CI workflow

Add GitHub actions workflows

Create frontend functionalities for Provider entity

Update API post methods with loggedin user and current created date time

Initate BloodBank project backend

Name: HlaProductOrdering

Start backend project
Start maven project
Add maven dependencies (Spring dependencies)
Add application.yaml

Design ERD

Create provider entity

Start git project

Create Schedule API and Schedule Version API

User Story: As a developer, I want to be able to retrieve a list of all schedules

Acceptance Criteria:

Scenario 1: Retrieving a list of all schedules

Given no query parameters

When I make a GET request to the API endpoint to retrieve a list of schedules

Then the system should respond with a 200 status code and a list of all schedules in the system.

Scenario 2: Retrieving schedules details

Given a schedule Id as a path variable

When I make a GET request to the API endpoint to retrieve the schedule details

Then the system should respond with a 200 status code and schedule details data in the response body

Scenario 3: Creating a schedule

Given Nothing

When I make a POST request to the API endpoint with the patient id information to create the schedule

Then the system should respond with a 200 status code with the schedule object in the response body

Scenario 4: Updating a schedule

Given Schedule id path variable

When I make a PUT request to the API endpoint with the schedule details to update the schedule

Then the system should respond with a 200 status code

Scenario 5: Retrieving a list of all schedule versions

Given Schedule id path variable

When I make a GET request to the API endpoint to retrieve a list of schedule versions

Then the system should respond with a 200 status code and a list of all schedules versions in the system.

Scenario 6: Retrieving schedules version details

Given a schedule Id and version id as a path variable

When I make a GET request to the API endpoint to retrieve the schedule version details

Then the system should respond with a 200 status code and schedule version details data in the response body

Create user entity

Authenticate users in the system

Design API

initiate frontend CD workflow

Create frontend functionalities for Patient entity