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.

Automating Billing Rules (with a pop-up warning) during Scheduling

Motivation:

OHIP billing rules can be difficult to keep track of. They can both affect the way we bill and the way we approach scheduling appointments. Rather than manually verifying that the conditions are met, we would like to automate certain checks we regularly.

Note: This was also previously mentioned in a Q-and-A (see question 2: https://accuroemr.com/wp-content/uploads/2019/05/Connect-Q-and-A-3009-Regina.pdf).

Specifications:

  • Provide the ability to define a "check"

    • can have the result: pass / fail

    • can be regarding patient information, ex:

      • demographics

      • provider enrollment history

      • past appointments:

        • for all time

        • within a date range relative to the current date

    • can be programmed to be run:

      • when scheduling a new appointment

      • when marking a patient as "arrived"

      • when billing for a particular procedure code

  • Desired result:

    • if the "check" is met, then do nothing

    • if the "check" is not met, then present a pop-up

      • this should notify the user what condition was not met

Note: As a "nice to have", known checks related to OHIP (or other billing types) could be pre-programmed. Then, there would be the option to configure our software to make use of them.

Example Scenarios: billing with OHIP code Q040

Scenario 1: Pass

GIVEN

a patient has exactly 3 billings in the past 365 days with code K030

WHEN

we bill code Q040 in the same 365 day period

THEN

no pop-up appears (and the original functionality is maintained)

Scenario 2: Fail

GIVEN

a patient does not have 3 billings in the past 365 days with code K030

WHEN

we bill code Q040 in the same 365 day period

THEN

a pop-up appears specifying that the condition of "having 3 billings in the past 365 days with code K030" is not met

  • Patricia Mouaikel
  • May 19 2020
  • Gathering Your Feedback
  • Attach files
  • Daniel Moon commented
    January 19, 2021 16:39

    More-so.

    It would be fantastic to have rules actually apply to codes that are a part of Appointment Defaults. See example:

    Description:
    When using "Billed after date" Billing Rule - Claims made from appointments are not applying the rule. In addition, there is no way to update claims that are already created that should have this rule applied if they were created before the rule was via some sort of re-assess.

    Workflow:
    Expected:
    Create Billing Rule: Billed after date + 02067 + Sept 1st 2017 + Change to: 22067 --> Created an appointment that uses a Type that pulls in 02067 for the code for Sept 2nd 2017 > Rule applies and in Claim the code changes to 22067.

    Actual:
    Create Billing Rule: Billed after date + 02067 + Sept 1st 2017 + Change to: 22067 --> Created an appointment that uses a Type that pulls in 02067 for the code for Sept 2nd 2017 > Rule doesn't effect the Claim's code and it shows 02067 UNLESS you manually open Claim Details and Tab for every single claim.

    Troubleshooting:
    Attempted every order of creating appointment, creating rule, setting appointment type to attempt a different result > Nothing worked.

    **Note: Using New Bill or New Patient Bill functions DID proc the rule.

    Query:
    Would it be possible to add this functionality? Currently, when using a PCode in an Appointment Type it is not generating the Rule proc that is associated to the PCode when the claim is created from this very common method.

    Thank you

  • +4