-
Notifications
You must be signed in to change notification settings - Fork 5
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
Users unable to enter new patients on the Platform #1190
Comments
I can reproduce in staging - I was able to add one patient but then the second failed
It seems like our uniqueness constraint does not handle URN being null |
I think unique_reference_number may end up as the empty string in the database rather than NULL. This is from a patient I added locally:
Confirmed in psql:
I suspect |
I was confused why I didn't get emails about this error but because it was a form validation error (I think) it wasn't logged at error |
Hiya,
I’ve received two separate queries from users who are unable to add new patients, encountering a message that reads: "Unique reference number (URN) already exists."
For the first query, I’ve checked, and there is no record of the patient in the system, nor has the patient been uploaded by any other user/trust. Therefore, they should be able to create a new entry...but they can't.
For the second query, the user has confirmed that the patients are newly diagnosed and would not have been added to the platform previously by them or any other trust.
Could you please look into this?
Let me know if there is anything you need from me.
Saleema
The text was updated successfully, but these errors were encountered: