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

Absence of validation for emails in default installation #7337

Open
boscosylvester-john opened this issue Apr 11, 2024 · 0 comments · May be fixed by #7338
Open

Absence of validation for emails in default installation #7337

boscosylvester-john opened this issue Apr 11, 2024 · 0 comments · May be fixed by #7338

Comments

@boscosylvester-john
Copy link

Describe the bug

In the default installation of OpenEMR, there is no validation for the email fields especially in the patient's demography section. This is important as many users of OpenEMR would not know of an option to add this validation after their installation. Moreover, as it is an email field many users would assume OpenEMR already performs some validation for emails, similar to the names field.

To Reproduce

without email validation

Steps to reproduce the behavior:

  1. Create a new patient by filling details in the Name (first name and last name), DOB and Sex from the 'Who' section and enter the Contact Email as 'a' in the 'Contact' section. Click on Save and create a new patient.
  2. Click on the 'Finder' section in the top navigation bar and select the newly created patient
  3. Open the 'Demographics' section
  4. Go to the 'Contact' section
  5. Check the value for 'Contact Email'
    A user has been created with an invalid email.

Expected behavior

If the 'Save' button is clicked and an invalid email address is present in the 'Contact Email' or 'Trusted Email' fields, then an error message should be displayed indicating the email is incorrect.

Client configuration

  • Browser: Google Chrome Version 123.0.6312.106 (Official Build) (64-bit)
  • OpenEMR version: v7_0_2
  • Operating system: Windows
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 a pull request may close this issue.

1 participant