RxRefund - Nilsu Bozan; Melis Atagun; Eylul Kadioglu; Buse Tosuner; Ahmet Ezdesir;

Week 1 (1.25.2024)

• Accomplishments:

1. A quick summary of the previous semester was made
2. The upload file, company, and user sections was reviewed
3. The page on Notion was updated, and tasks were assigned

• To-do:

1. Check if the database and code are up-to-date and working on AWS
2. Distribute tasks for the analytics, database and frontend
3. Create an architecture for users, including company admin, pharmacy admin, and super user
4. Upload new TXT files without making any changes

Week 2 (2.1.2024)

• Problems:

1. Archived transactions can not go to the archived_data table. We think that it is because new files contain a new column that we do not have in the archive_data table yet.
2. ec2 instance was unable to connect to the database due to security reasons.

• Accomplishments:

1. A quick summary of the previous semester was made
2. Some of the TX files are tested and they were uploaded successfully.
3. Tasks were assigned.
4. Permissions of the database in ec2 instance changed and then successfuly connected to database.

• To-do:

1. company users, access control, include permissions in menu items.
2. Break archive tables by NPI.
3. Implement tx_search for our current pharmacy (NPI) structure
4. Confirm page for #rows and date range in intersection.
5. Improve date range intersection algorithm

Week 3 (2.8.2024)

• Problems:

1. The problem is that we need to divide the process_and_check_npi function in a way that modifies the database after the confirm button is clicked.
2. We need something like “wait” until the button is clicked.

• Accomplishments:

1. Frontend is done for confirming uploads.
2. Buttons are placed (not effective right now).
3. User can see the dates and affected rows.

• To-do:

1. Improve the performance by analyzing the process_and_check_npi function.
2. Make demos from the source code on the EC2 server.
3. Admin should have a list of users for each functionality. It controls what the user can do or not.
4. Admin should be a role, not a user.
5. You are a user and you can be assigned to a role. you can be an admin for Newhard company, which will get you two pharmacies that Newhard company owns.
6. Different forms for adding users and adding companies are required.
7. Users can be company admins or not, pharmacy admins or not.
8. System users should be Jamie and employees.