Contains explanations and disclaimers of certain datasets and columns in Report Builder
Column: "Balance"
For any call marked "Finished", this column always shows zero, even if there is a write-off amount. This is different than the rest of AngelTrack, where finished calls display their write-off amount in their "Balance" field.
If any finished dispatch has a non-zero balance, i.e. has a writeoff amount, the amount will be displayed in the column named "Writeoff Amount".
Column: "Gross Charges"
The "Gross Charges" column contains the sum of:
- Price quote
- Service charges
- Discounts
- Finance charges
Column: "Net Charges"
The "Net Charges" column contains the sum of:
- Price allowed (if set), else the Price quote
- Service charges, if no Price allowed is set
- Discounts, if no Price allowed is set
- Finance charges
In other words, the "Net Charges" column takes account of any adjudication performed by the primary insurance carrier. It does NOT include any reductions due to a PR or NAA, nor the effect of any sequestrations which AngelTrack records as pseudo-payments.
Column: "Billable Odometer"
When using the three "Billable Odometer" columns in the Dispatches-Distances dataset, remember that labs calls, and telemedicine, and all fire responses capture the billable odometer as the distance from post to scene.
Column: "Crow Flies"
There are several "Crow Flies" columns, in the Dispatches-Distances dataset. They are:
"Crow Flies - Post to Origin" contains the distance as the crow flies from the primary responder's posting station to the scene. This number is useful during datamining, when looking to see which locations are drawing responses from posting stations that are too far away.
"Crow Flies - Enroute to Origin" is similar to the above, but it shows the distance as the crow flies from the point where the crew marked "enroute" to the scene. It can be very different than the distance from their posting location, since crews will often go straight from one call to the next without returning to post. If this column contains large values, it means lots of slack mileage occurring.
"Crow Flies - Back to Post" shows the distance as the crow flies from the dropoff point to the assigned crew's posting station. Note that crews often do not return to their posts after a dropoff, sometimes they go straight to the next call -- a fact not captured by this column. Instead, this column is used to identify patterns of calls that send your crews to far-away locations.
Column: "Repose Name"
The "Repose Name" column contains the origin name for any outbound or one-way trip ("Trip Is Outbound" = true), or the destination name for any return trip ("Trip Is Outbound" = false). In this manner, it tends to show the initiating facility, and is therefore a better choice for row grouping than "Origin Name".
Likewise the column "Repose Is Contracted For Service" returns "true" if the provided service is covered by the contract with the repose facility. This is similar to, but not the same as, the "Bill To Facility Is Contracted For Service" in the Dispatches-Financial dataset.
Column: "Trip is Emergent"
This column contains "true" if any of the following are true:
- The trip was dispatched as "Emergent" or "Critical";
- The enroute driving was "Emergent" or "Non-emergent upgraded to emergent"; or
- The transport driving was "Emergent" or "Non-emergent upgraded to emergent".
Column: "Ins Policy Type"
To assist you with row grouping, these columns contain "--" when the associated dispatch is not billable to insurance, or when the associated payment event's counterparty is not "Insurance".
They contain "??" when insurance is applicable but the policy type is not recorded.
Column: "Ins Payor ID"
To assist you with row grouping, these columns contain "-----" if insurance is not billable or applicable, or "?????" if insurance is applicable but the payor ID is not recorded.
Column: "Minutes From PSAP to Scene"
This column is null for scheduled trips. It contains data only for emergent, critical, and lower-acuity calls... but you will probably want to filter out all lower-acuity responses when performing an analysis of your response times.
Dataset: Dispatches-Runtimes
This dataset contains data only for each dispatch's primary responder. For the case of a fire call, or an EMS catch-and-release, the primary responder is the first unit that responded. For an EMS transport, the primary responder is the unit that performed the transport -- even if they were not the first unit to respond.
The dataset includes trips that were delegated to affiliates, in case your affiliates provide you with progress reports and you wish to analyze their times. Since affiliates usually do not provide progress reports, you will probably want to filter out those trips, using the "Trip is Delegated" column from the dataset.
Dataset: PCR-MI
This dataset limits itself to trips where a PCR M.I. form is filled out and is marked "Yes, MI Occurred". Remember it is possible for the attending to fill out an M.I. form but mark it "No, MI did not occur", for a false-alarm situation.
Dataset: PCR-MedsGiven
For performance reasons, this dataset limits itself to trips where the service provided is any of:
- Labs
- Telemedicine
- BLS
- ALS
- MICU
For all other service levels, this dataset returns only NULLs.
Dataset: PCR-FirstIntubation
This dataset contains a record for any dispatch where the attending has filled out the Airway Intervention form in the PCR and indicated that an intubation was attempted by any party -- even if not successful.
The presence of the Airway Intervention form is required; it is not sufficient to record an intubation procedure record without an airway form.
Dataset: PCR-FirstIV
This dataset contains record for any dispatch where the attending has filled out the IV Intervention form in the PCR and indicated that an IV was successfully placed or adjusted (maintained) by any party.
For all other records, this dataset returns only NULLs.
Dataset: PCR-Injury
This dataset contains a record for any dispatch where the attending has filled out the Injury form in the PCR and indicated that an injury did occur or was "unknown".
For all other dispatches, this dataset returns only NULLs.
Dataset: Checklists
If a checklist is assigned to a shift but no crew member ever fills out and saves any part of it, then the "Checklist Saved By" column will report the name of the shift's primary crew member, on the assumption that he or she was responsible for either filling it out or making sure another crew member fills it out. This makes the column useful for analyzing crew checklist performance.
Dataset: Payment Events Zero / Payment Events Non-zero
The datasets that pull from Payment Events do not include charges and payments for subscriptions, because those are not associated with any dispatch record. Subscription activity is instead reported in the ledgers.
Report Builder's date range controls select rows based on the Date Received, rather than on the Date of Bookkeeping.
For payment event records which are insurance approvals or denials, the column "Received Date" contains the adjudication date, not the date of any associated monetary payment or reversal.
Multi-Response Calls
If a dispatch had multiple responders, then all of its response datafields in Report Builder -- including leg times, GPS coords, reasons for delay, and so on -- pertain to the primary responder.
The primary responder is whichever unit performed the patient transport, if any. If there was no patient transport, then the primary responder is whichever unit was assigned first.
The dataset named Dispatches-Crew reports the existence and identity of any secondary responder. Data for any tertiary responders are not exposed in Report Builder.
Trips delegated to affiliates are assumed to have only a single responder. To learn more about AngelTrack's multi-response functionality, please refer to the Multi-Responder Guide.