Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated OS-2 (PHC module) with File Tracking Functionality Enabled #1466

Merged
merged 262 commits into from
Apr 15, 2024

Conversation

prabhatsuman
Copy link

Based on the changes you provided, here is the updated pull request template:


Issue that this pull request solves

Closes: # (issue number)

Proposed changes

Brief description of what is fixed or changed

  1. Implemented the Medical Relief use case using the File Tracking SDK:

    • This change introduces new functionality to manage and track files in the Medical Relief use case, improving efficiency and accuracy in file management.
  2. Corrected the issue with the generate report feature and added functionality to transfer files from the compounder to the patient:

    • The bug with generating reports has been fixed, and the new functionality allows smooth file transfers between the compounder and patient, improving the overall workflow.
  3. Corrected the issue related to adding schedules:

    • This change resolves any errors encountered when adding schedules, improving the schedule management system and ensuring accurate scheduling.
  4. Updated the migration files to be in sync with the latest staging branch:

    • The migration files have been updated to match the current state of the latest_staging branch, ensuring data integrity and consistency across different environments.
  5. Merged the changes with the correct latest_staging branch:

    • Ensured compatibility and seamless integration with the latest_staging branch to avoid any integration challenges.
  6. Verified the merge on Docker to ensure no errors remain in the deployment process:

    • Tested the merged changes in Docker to validate the deployment process and confirm there are no remaining issues.

Types of changes

Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other (please describe):

Checklist

Put an x in the boxes that apply

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have created a new branch for this pull request
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • My changes do not break the current system and pass all the current test cases.

Screenshots

  • If there are any changes in the user interface, please attach screenshots here.

Other information

  • Add any other information relevant to the pull request that reviewers should know about.

Ensure to replace placeholders like "(issue number)" with actual values that apply to your project.
Screenshot from 2024-04-16 00-01-21
Screenshot from 2024-04-16 00-00-53
Screencast from 16-04-24 12:03:13 AM IST.webm

akshatnema and others added 30 commits February 18, 2023 15:19
Co-authored-by: A Anunaya <[email protected]>
Co-authored-by: Aksh Bansal <[email protected]>
@prabhatsuman
Copy link
Author

All Changes look good to me and can be merged without conflicts.

@prajjwalkapoor @ChaudharyRaman

@ChaudharyRaman
Copy link
Contributor

LGTM.

@ChaudharyRaman ChaudharyRaman merged commit 688830b into FusionIIIT:os-2 Apr 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.