Multi-Step QA Review Workflow

You can configure AngelTrack to enforce a multi-step QA review process that involves multiple people.

Configuration

This QA review process will utilize AngelTrack's tags system.

You must have at least two spare tags for this. If you've run out of tags, then look at your current tag usage, and see if you can't shift some of it over to the Source Tracking System.

1. Visit the Tags List by clicking the relevant hyperlink in the Dispatch Sidebar.

2. Create one tag for each phase of your QA review process. For example, you might create these two tags:

   • QA Clinical Passed

   • QA Billing Passed

3. Visit the Preferences page, under Settings, and open the "QA Review" tag. Find the "Tags required to pass" item, and add all of the QA-related tags you created.

Now you're ready to train your QA reviewers to use the process!

Using the Process

Each QA reviewer is responsible for one or more of the QA review steps, and so will use the QA Review Queue's tag filters to constrain the list to only those trips which are waiting for them.

For example, the person responsible for clinical review will configure the tag filter to show only those trips which do NOT have the "QA Clinical Passed" tag.

(You can toggle a tag-filter to "NOT mode" by clicking it, causing it to turn red.)

The QA Review Queue will remember each user's tag-filter settings, so that every time they visit, they can see just the trips which concern them.

On the QA Review form, each reviewer will subtract the relevant tags from the trip to reflect their approval. When the reviewer saves the form, if attempting to pass the trip onward to billing, AngelTrack checks the required tags, and refuses to send it onward if any review steps are still missing. In that case, the review can simply save the form without passing it onward, so that the other reviewer(s) can find it waiting for them in the queue.

Exemptions

The aforementioned system creates a gate at the QA Review page. It does not, however, obstruct the following alternate workflow paths that a dispatch might follow:

• Dispatcher or biller jumps the trip entirely over QA;

• The trip is eligible for QA bypass and does so;

• The trip is not subject to QA review.

• The trip is imported through an API or via NEMSIS import and goes straight to 'Billing office'.

In those situations there is no opportunity for a tag barrier, so your billing process must take account of that possibility.