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 transfer #7120

Closed
aparnacoronasafe opened this issue Jan 30, 2024 · 4 comments
Closed

Patient transfer #7120

aparnacoronasafe opened this issue Jan 30, 2024 · 4 comments

Comments

@aparnacoronasafe
Copy link
Member

Describe the bug
When a patient who has "Transfer allowed" on the profile, when the file is pulled into another facility, the encounter is not closed in the previous facility.

To Reproduce
Steps to reproduce the behavior:

  1. Go to any patient profile (Patient A) and "Allow transfer"
  2. Go to any facility and Click on 'Add patient'
  3. Type in Patient A's phone number is the patient registration form
  4. A pop-up to pull the patient record appears. Input the patient A's DOB.
  5. The patient card gets transferred to the new facility.
  6. Try filing a consultation for the patient. An error appears saying a consultation already exists.
  7. Any log update filed on the patient actually gets logged on the last hospital records.

Expected behavior
Allow pulling of patient records only for discharged patients. If it is a live patient in another facility, show an error saying "the patient's record is Live in XYZ facility. Kindly contact the Nodal person of the facility at "Emergency contact no. for the facility" to transfer the patient file"

@gigincg please review

@Ashesh3 Ashesh3 self-assigned this Feb 1, 2024
Copy link

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.

@github-actions github-actions bot added the stale label Feb 16, 2024
@Ashesh3
Copy link
Member

Ashesh3 commented Feb 18, 2024

@aparnacoronasafe I am unable to replicate this. When i repeat the above steps, the old consultation correctly gets auto-closed, and a new consultation is filed at the destination facility.
@nihal467 could you confirm if we still have this issue?

@github-actions github-actions bot removed the stale label Feb 19, 2024
@Ashesh3
Copy link
Member

Ashesh3 commented Feb 21, 2024

@aparnacoronasafe @nihal467 is this issue still happening? I am not able to reproduce this issue with the steps given. The old consultation correctly gets auto closed.

@Ashesh3
Copy link
Member

Ashesh3 commented Mar 6, 2024

Closing this issue as non-reproducible. Please feel free to reopen it if the problem persists.

@Ashesh3 Ashesh3 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
@Ashesh3 Ashesh3 removed their assignment Mar 6, 2024
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

No branches or pull requests

2 participants