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

bug: saving # of tablets in a prescription to 9999999999 sets it to 2147483647 #7314

Closed
tackyunicorn opened this issue Apr 3, 2024 · 0 comments · Fixed by #7315
Closed
Labels
Milestone

Comments

@tackyunicorn
Copy link
Contributor

Describe the bug

When adding a prescription to a patient, an option is provided to configure the number of tablets.
If the value in this field is saved to 9999999999, revisiting the prescription (through an edit operation) reveals its value to be 2147483647

To Reproduce

Steps to reproduce the behavior:

  1. Navigate to a patient's dashboard
  2. Click the pencil icon on Prescriptions
  3. Select an existing prescription / create a new one. Configure the # of tablets to 9999999999
  4. Hit Save on the prescription
  5. Now click on the Edit button for the prescription that was just saved
  6. The # of tablets field shows up as 2147483647
    image

Expected behavior

The # of tablets field should show the correct value that was entered

Client configuration

  • Browser: Google Chrome
  • OpenEMR version: 7.0.2
  • Operating system: macOS

Expected behavior

Client configuration

  • Browser: Google Chrome
  • OpenEMR version: 7.0.2
  • Operating system: macOS
@adunsulag adunsulag added this to the 7.0.2.1 milestone Apr 23, 2024
@adunsulag adunsulag changed the title Saving # of tablets in a prescription to 9999999999 sets it to 2147483647 bug: saving # of tablets in a prescription to 9999999999 sets it to 2147483647 May 18, 2024
@adunsulag adunsulag added the Bug label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants