-
Notifications
You must be signed in to change notification settings - Fork 27
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
Searching by policy number in Lookup patient
seems to be not working
#2749
Comments
Both of these are bugs! Good chance that this bug will be solved by a fix for #2713. Not sure whats going on with the search button in the second bug! If you could create a second issue for that it would be appreciated! |
Sure, count with that. I'll create a separate one for that specific issue! @wlthomson |
…-by-policy #2749 update patient search by policy
Fixed by #2778. |
Tested in v5.0.0 rc2 Testing
@wlthomson but clicking on searched result will redirect to the patient list page rather than specific patient detail page. |
Thanks @ArpitaSussol!
No worries, that's the current intended behaviour. Moving to done 🎉. |
Describe the bug
In Dispensary module, new policies can be added for internal/external patients, and then can be found through Lookup patient -> Filling in
Personal policy number
or/andFamily policy number
inputs. I couldn't find a new policy that I just created, when entering its information, nothing is retrieved. See example below:Policy previously created:
Personal policy number
:Personal policy number
andFamily policy number
.NOTE: @wlthomson, this doesn't allow me to search, it automatically disables the button. Is it a normal behaviour when trying to search using both numbers? Otherwise I will create a separate issue.
To reproduce
Steps to reproduce the behavior:
Lookup patient
Expected behaviour
All patients, with the same previously entered policy numbers, should appear on the list.
Proposed Solution
N/A.
Version and device info
Additional context
While testing #2678
The text was updated successfully, but these errors were encountered: