QHR Product Ideas

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:

For further support, please reach out to Accuro Client Services:

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.

Speed up Claims section by reducing Queries

The claims section has generally been considered a "slow area" by our own facility as well as other facilities that I have spoken too. As it stands now, when working in the claims section, clicking from claim to claim loads everything that is attached to the demographics on that claim. This has been confirmed by support at Optimed. "Accuro loads all of the details about the patients, appointments/claims, insurers for those, the procedure codes, etc. Basically anything to do with the patient or the bill that is related to billing will be looked up. " Remove this complete querying of the patient like appointment history, encounter notes, etc etc, this does not need to load up when the user is just putting in a tariff/billing code. Query this Bill only and any information required for the Biller to complete this. If the end user presses F3/F4, switches to another left hand button (patient, EMR) section then query the SQL server for this information then. I believe if this can be done, the Claims section will run more seamlessly, Billing in the facilities I have spoken too, and our own, is managed by a dedicated team who are required to do a lot of data entry, enter details, click down to next claim, this constant loading on the back end switching from claim to claim is making the experience unpleasant and interrupted with unnecessary querying of data that 9 times out of 10 is not required. If the user requires more information, then that is the time to have the few second delay whilst the data is fetched and most users would find this acceptable. An facility/end user choice of how the claim sections queries would even be better! Would be very good to get some Optimed Development in on this !!
  • Guest
  • Jun 20 2016
  • Released
  • Attach files
  • +6