Did the customer address bug get fixed? #1702
nara-falconeer
announced in
General
Replies: 1 comment 1 reply
|
Hi @nara-falconeer I do see the bug was filed. I can also see it has already been flagged as highest priority. The ETA is to aim for end of the month. I would love to know more about your workflow so I can ensure the fix will work for your needs. With your patients that have an old and new address (really any patient with multiple addresses), how would you know which address to use for your health exchange integrations verse which ones to use for ordering? Would you want an option to mark an address as "preferred" like you can do now with the phone numbers? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We had reported a rather serious bug. Our customers live in facilities. Most of customers have an "old address" that is individual, and a current address that is a "Facility" address. We keep the old address so health exchange integrations work - they rely on at least one matching address and a lot of our patients are new in their new faciilty address and might not yet have health exchange data with the new address.
Canvas transmits only individual addresses when it sends out information about patients, which in our case is not the current address. This has been disastrous for us with large DMEs like hospital beds getting delivered to wrong addresses. We have to spend a lot of manual cycles in sending the patient address to pharmacies, referrals, DME orders etc as the data transmitted by Canvas is incorrect.
We filed a but several weeks ago - not sure if this has since been fixed. If it has not yet been fixed, please let us know what the ETA is.
All reactions