You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When a patient requests an In Person or Telemed visit and selects a reason during the Intake process, the "Reason" column on the In Person and Telemed tabs in OttEHR Admin should display the specified visit reason. Currently, the column either shows as empty or displays "Unknown," even for visits where a valid reason has been added during Intake.
Steps to Reproduce:
Request an In Person or Telemed visit via Intake and select a visit reason from the dropdown. OR add Walk in visit with reason by In person>Add patient on the Admin portal
Navigate to the OttEHR Admin portal.
Go to the In Person or Telemed tab.
Look at the "Reason" column for the requested visit.
Expected Result:
The "Reason" column displays the selected visit reason accurately.
Actual Result:
The "Reason" column is either blank or displays "Unknown," even when a reason is provided during Intake.
The text was updated successfully, but these errors were encountered:
DenysMyrosh
changed the title
### **OttEHR Admin - In Person and Telemed Tabs - Show Actual Visit Reason**
OttEHR Admin - In Person and Telemed Tabs - Show Actual Visit Reason
Nov 19, 2024
Related to #599
Tested on:
Description:
When a patient requests an In Person or Telemed visit and selects a reason during the Intake process, the "Reason" column on the In Person and Telemed tabs in OttEHR Admin should display the specified visit reason. Currently, the column either shows as empty or displays "Unknown," even for visits where a valid reason has been added during Intake.
Steps to Reproduce:
Expected Result:
The "Reason" column displays the selected visit reason accurately.
Actual Result:
The "Reason" column is either blank or displays "Unknown," even when a reason is provided during Intake.
The text was updated successfully, but these errors were encountered: