AngelTrack 2.1 build 260 release notes

Release dates

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

Early access 2016-Jun-11
All customers 2016-Jun-18

To join the early access program, contact AngelTrack Support at (800) 946-1808.

Improvements and new features

  1. AngelTrack is now NEMSIS certified. AngelTrack is certified on NEMSIS v3.4.0, the latest version of the standard.
  2. New system for tracking company-owned medical devices such as ECGs, IV pumps, and ventilators. Can upload a photo of each. AngelTrack keeps track of device inspection dates in order to warn you of devices requiring scheduled maintenance.
  3. New system for tracking of crew immunizations. Employees can enter this data about themselves, or members of HR can do so.
  4. Crew certificate tracking now includes tracking of:
  5. Patients With a Balance report query runtime reduced by 2/3rds.
  6. The NEMSIS 3 XML Workbench now indents and formats the XML in the normal human-readable way, for easier experimentation and debugging.
  7. Revenue Accrual Report now has an option to show the current month.
  8. Master Billing Queue can now filter by tag is / tag is not.
  9. Invoice Generator for Patients load time -- noticeable only when there are hundreds of patients with outstanding balances -- is reduced by 95%.
  10. When a crew member enters any message for their QA reviewer, the underlying dispatch will no longer be allowed to skip QA if it was otherwise eligible to do so.
  11. The patient datafield named "Insurance policy type" is now called "Insurance carrier type" (e.g. Medicare, Medicaid, Private). And there is a new field named "Insurance policy type" which offers the standard X12 policy types: When this new policy type datafield is set, it will be directly echoed to 837P field SBR09 in loops 2000B and 2320. If the policy type datafield is not set, then AngelTrack will do what it did in the past: infer the policy type from the carrier type. Either should work fine because carriers don't need this information anyway.
  12. Many additional detail fields added to the PCR Injury report.
  13. PCR Assessment body-map now supports affirmative "exam not done" findings.
  14. All patient documents now have a new "Provided by" field, used to record the name of the person or agency that provided the document.
  15. New built-in certificate types for various types of rescue training.
  16. Support for non-standard insurance payor IDs longer than 5 characters.
  17. New PCR signature form: "Receipt for patient belongings", which permits the crew to attach a high-resolution color photo of the patient's belongings, which the patient then signs.
  18. QA Review form now allows a medical director (an employee that belongs to the QA and Doctor roles) to review a call, provide commentary, and then given an electronic signature.
  19. Automatic handling of 837P loop 2300 CLM11 (cause of accident). All four choices (AA, OA, AP, and EM) are supported, and are automatically selected based on the injury causes selected by the crew using the PCR Injury page.
  20. Cause of accident checkboxes are likewise automatically filled-in on the CMS-1500 form.
  21. The Payment Event Finder grid is now leaner, with some controls removed in favor of faster load times and reduced data size so as to support very large queries.
  22. The PCR's CPR / MI / cardiac arrest bookkeeping system is overhauled to work more like other PCR applications. Existing CPR records have been automatically upconverted to the new system.
  23. Automatical handling of the 837P loop 2310A (referring provider) and CMS-1500 box 17 (referring provider). The referring physician name and NPI can be collected by crews, in the followup information. The data is then displayed to the biller on the Coding page, for edit and review. After the biller saves their work, the data will appear in the proper loop in the 837P and/or proper box in the CMS-1500.
  24. In order to more accurately reflect its purpose, the Revenue Visualizer is renamed Cash Receipts Visualizer, and moved from the "Receivables" group to the "Reports" group on the Billing Home page.
  25. Likewise the Call Payor Visualizer is now named Call Payor Mix Visualizer, and the Facilities Payor Matrix report is now named the Facilities Payor Mix report.
  26. New report Claims Activity Visualizer shows the number of claims filed by insurance carrier type, and gross amounts claimed, over any date range, rendered in any interval.
  27. Invoices can now be paid retroactively, specifying any date in the past as the posting date. All linked payment events will then show the selected posting date, and thus also your revenue and accrual reports. All associated journals and timestamps will nevertheless show the current date, so that an audit will show the payment was made retroactively.
  28. When importing an electronic EOB (i.e an 835 EDI document), the payment event records created will now reflect the date the check was issued (BPR016), rather than the dates the claims were adjudicated (DTM*050), if the 835 specifies a date of check issuance. If the 835 does not specify a check issuance, then the payment event records will reflect the date the claims were adjudicated, the way AngelTrack has always done.
  29. The Followup page has always required a reason for delay whenever any leg of a trip runs longer than x minutes. For example, if a crew spends more than 30 minutes enroute, the Followup page demands to know why. Previously, these thresholds (e.g. 30 minutes) were hardcoded. Now they are configurable: they are the same "Leg time warnings" thresholds used by the dispatch board. They are configurable using the Preferences page under the Settings page.
  30. Invoices now keep track of how many times their included dispatches have been previously invoiced. This is used to keep track of a contractual requirement to (for example) bill every receivable three times before selling it to a collections agency.

Significant bugfixes

  1. When using zoned dispatching, the "Assigned Dispatches" chart sometimes shows all assigned dispatches from all zones, even if the Global zone is not selected.
  2. When a crew member attempts to create a new patient record using the PCR, an error message is sometimes returned.
  3. The VIN decoder in the Vehicle Edit page did not support VINs newer than 2010.
  4. Attempts to edit the "Effective date" field in the "HR History" grid of the "HR" tab of the Employee Edit page had no effect.
  5. Coding page wrongly rejects ICD-10 codes whose extension character (the optional seventh digit) is numeric.
  6. An application error will occur if you open the Payment Event Edit page, switch to the "835 Decoded" tab, then to the "835 Raw" tab, then back to the "835 Decoded" tab.
  7. BillFlash exports specified the date of service as DD-MM-YYYY, rather than MM-DD-YYYY, and (per request from BillFlash) no longer include the time.
  8. Crew members whose employee accounts have been toggled inactive (i.e. laid off) and then active again could not update their electronic signature.
  9. In the Safari browser, the PCR Assessment page's body-diagram did not vertically center its popover UI, requiring the crew member to scroll up or down to use the popover.

Index of all release notes for all releases