The spirit of the QHR ideas portal is to collect ideas and feedback from our users for integrations, enhancements, and new features.
We want to hear from you, and encourage you to submit, comment, and vote!
Please note that this site is not regularly monitored, and that there may be a delay in response to your submissions.
QHR reserves the right to choose what is built into the application, and it is the intention of QHR to build the software to meet the needs of the marketplace.
User Resources:
Accuro Learning Academy, our eLearning platform (reach out to Client Services for your sign-up code)
For further support, please reach out to Accuro Client Services:
1-866-729-8889
Accuro Menu > Help > Send Feedback
Interested in connecting with us for user research, or participating in user testing? You can sign-up by filling out this web form, and we will reach out to you for feedback when we're evaluating new ideas.
I was so excited to get the AccuroGo announcement but instantly angry that it was only available to ASP clinics (ie the ones that pay more to QHR to house their data). ASP isn't a viable option for a large clinic like ours with a giant database. We've already invested for 7 years in our EMR/IT infrastructure with a local server. That must be true of 25-30% of your clinics. It's hard not to think you're penalizing them as an inducement to switch to ASP (again, more $$$ to QHR).
I get that the login used by the app is the Citrix login but I've spoken to my IT team and there are several ways you could have/can make this functionality accessible to local server users securely. Please consider adding this functionality soon.
AccuroGo addresses a major deficit of Accuro which is the ability to easily upload photos.
Any clinic that does any procedures (biopsy, surgery, cosmetic injections) will often take photos of the patient as part of the clinical record.
Major competitors including Telus EMR (MedAccess, Wolff) have this feature.
This should be a priority as it directly impacts patient care. For example, a patient with multiple skin cancers and previous biopsies on the scalp, may end up with surgery on the wrong site without clear photographic documentation.
If this truly is about money, then you can always charge server users an extra $5/month or whatever nominal amount to recover the development costs.
I fully agree. We are on a local server (i.e., not ASP) because of our larger scale--the local install is faster and has better uptime.
Not having AccuroGo available to our providers is a major penalty: most of our docs work outside the clinic at least 1 day per week (e.g., LTC, hospital care team, rehab) and having mobile access to the EMR is very important to them, more so every day.
We have remote access to our local sever, but it is not optimized for smartphones or tablets (it's not great on laptops either). Hence why having a well designed app is a critical success factor for us.
If AccuroGo is not provisioned for local installs, we are being forced to choose between mobility and speed/reliability. We are not happy with this dilemma and if it's not addressed, we will be reluctantly looking at all our options.