Note Fields

Every dispatch in AngelTrack has several fields whose purpose is to record phone calls, confirmations, unusual events, changes, and problems, for reference later in the event someone starts asking questions.

Billing Notes and !Bang Comments

These notes can be kept by dispatchers during call-taking, and modified using the Dispatch Edit page. Billing Notes can also be viewed and modified by billers at all steps of the postprocess.

Any sentence in the Billing Notes that begins with an exclamation point will be shown in any subsequent invoice. This is called a !bang comment.

For example, of the following two comments, the second one is a !bang comment that will be printed in the facility's invoice:

Confirmed, PAN will be required for this transport.
!Nurse Jane was informed via telephone to file for a PAN, but said she would follow up on it and then hung up.

The exclamation point allows a dispatcher, biller, or QA reviewer to provide an explanation that will automatically show up in any subsequent invoice. That explanation could help the customer understand the basis for a fee or charge, sparing your billing department a phone call. For further reading, see the Invoice Comments guide.

Prior Authorization Notes

These notes are kept by dispatchers and billers using the Prior Authorization Queue, to keep track of their efforts to help facility staff complete and submit the necessary paperwork.

As with the Billing Notes, any sentence in the Prior Authorization Notes that begins with an exclamation point will become a !bang comment, and thus will be shown in any subsequent invoice. Use this feature to provide explanatory notes to facilities and patients, who may not understand why they are being billed for a particular call.

Dispatcher Comments

These notes are intended to be kept by dispatchers during call-taking, and modified using the Dispatch Edit page. They are shown to the crew during call execution, and they are preserved across recurring dispatches. They are viewed by QA reviewers and by billers during postprocess.

Any sentence in the Dispatcher Comments that begins with a dash character will not be preserved across recurring dispatches. This allows a dispatcher to provide a one-time comment to the crew -- such as "Going one hour early today for new-patient paperwork" -- that will not be shown again on future recurrences. For example:

Make sure the nursing home places the patient on a Hoya pad.
-Patient's daughter will be riding in the van today.

In the example above, the first sentence will be preserved across all future recurrences, whereas the second sentence will appear just this one time.

Dispatcher Notes

These notes are also kept by dispatchers, but are not shown to crew members. Instead, they are used to record details of phone conversations, changes, reschedules, and other abnormal events that do not rise to the level of an incident. They are not preserved across recurring dispatches. They are viewed by QA reviewers and billers during postprocess.

Any sentence in the Dispatcher Notes that begins with an exclamation point will become a !bang comment, and therefore will be shown in any subsequent invoice.

On the dispatch board and on the Confirmations for Tomorrow page, the Write.empty icon will open a popup window for quickly adding a dispatcher note to the dispatch. The icon changes to Write.full once there are some dispatcher notes recorded; hover your mouse over the icon to read them.

Crew Comments

These notes are provided by crew members while completing the followup report for a dispatch. They are used to explain extenuating circumstances or unusual data, and as such are shown to QA reviewers and billers during postprocess. They are never included in any invoice.

QA Review Dialog

The QA Review dialog is a two-way conversation between crew members and QA reviewers, allowing them to explain themselves to each other off-the-record. After a dispatch graduates from QA, the QA Review dialog is not shown to anyone.