AngelTrack 2.1 build 282 release notes

Release dates

New releases are always installed during a maintenance window, at 02:00 your local time on Sunday morning.

Early access 2017-Mar-12
All customers 2017-Mar-19

Improvements and new features

  1. More improvements to the Live Map based on customer feedback (thank you to everyone who took the time to give their opinions):
  2. New reports are now available under Dispatch Home:
  3. The Coding page now gracefully handles the coding of calls where no transport was performed. Some insurance carriers will pay for these dud calls, which AngelTrack calls BNTs. They are coded without a location modifier. They include a service line for pickup but do not include a service line for mileage.
  4. The Coding page now displays a warning about the patient's PAN setting if it is set to "Always" or "Never".
  5. The dispatch boards now warn dispatchers who might otherwise accidentally unassign a dispatch from a crew that is already transporting or at destination.

Significant bugfixes

  1. When running AngelTrack in Australia, neither the PCR Billing page nor the patient data popup would accept an Australian-format phone number or ZIP code in the patient's next-of-kin and employer fields.
  2. When using a detached biller, the "Record Claim Filed Events" button in the Insurance Filing Queue failed to advance a dispatch to "Awaiting payment" if the dispatch already had an appropriate "Claim filed" payment event recorded.
  3. If the Preferences are configured for a default dispatch service of ALS or MICU, the Dispatch Create page would fail to honor it.
  4. The state report QA/QI for Gennessee County sometimes returned an application error.
  5. The Medication Edit page's RxNorm lookup tools failed to return a result from any RxNorm query, when using the Chrome browser.

Index of all release notes for all releases