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

Patient transferred notification shows UUID instead of patient name #6811

Closed
rithviknishad opened this issue Dec 8, 2023 · 3 comments · Fixed by #6829
Closed

Patient transferred notification shows UUID instead of patient name #6811

rithviknishad opened this issue Dec 8, 2023 · 3 comments · Fixed by #6829
Assignees

Comments

@rithviknishad
Copy link
Member

Describe the bug
Patient transferred notification shows UUID instead of patient name

To Reproduce
Steps to reproduce the behavior:

  1. Add patient that already had a consultation
  2. Transfer the patient to new facility

Expected behavior
Show name in place of UUID

Screenshots
image

@konavivekramakrishna
Copy link
Contributor

image
image

the API response does not contain the patient name

@rithviknishad
Copy link
Member Author

Why do you need the patient name from the transfer API?

The front end is already aware of the patient object before even the transfer API is called. Users can see the patient's name in the transfer modal right?

@rithviknishad
Copy link
Member Author

No, this is shifting, not this.

You'll have to do the following to to "Patient Transfer"

  • Click Add Patient
  • Type phone number of an existing patient's phone number (can be discharged or active patient)
  • This will prompt you asking whether the patient is one of in the list.
  • Next it'll ask you to select a patient from that and verify the date of birth.
  • Once successful, you'll be able to transfer the patient and land to consultation page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants