AngelTrack 2.1 build 350 release notes

Release dates

New releases are always installed during a maintenance window, at 02:00 Central Standard Time on Sunday morning, which is early Sunday afternoon for AUS customers.

Early access 2020-Apr-19
All customers 2020-May-03

Special bulletin: Timeclock IPv6 Transition Occurs This May 30th 2020

If you use AngelTrack's timeclock with its IP address restriction feature so as to allow clockin only from company premises, please read this bulletin and follow the migration instructions before Saturday, May 30th, 2020:

AngelTrack Timeclock IPv6 Transition


Improvements and new features

  1. CO*253 "sequestration" amounts are now tracked and accounted separately from the insurance adjudicated price. It is no longer necessary to manually subtract CO-253 amounts from the allowed price when typing in a paper EOB.
  2. CO*253 sequestered amounts are now displayed in various grids and reports in order to show their contribution to the balance due, and for tax purposes.
  3. Patient responsibility [PR] determinations by carriers are now tracked and accounted explicitly, rather than implicitly (in the allowed price). These amounts are shown on the "Billing" tab of Dispatch Edit, and are also shown when manually adding a new payment event. This improvement means that the following situations no longer require manual intervention by a biller:
  4. As a result of the aforementioned, when the Payor is set to 'Patient', the calculated PR (if any) determines how much the patient can be invoiced. As such, changing the Payor can now change the balance due. To learn more, read the Patient Responsibility guide; it explains AngelTrack's PR algorithm, whose complexity is meant to address the possibility of errors in X12.835s and in payment event records. Note that there is a difference between "no PR set," meaning the patient owes the full balance, versus "PR is zero," meaning the patient owes nothing even if a balance remains.
  5. The Import an EDI Document now has three different warning levels for when an EDI does not match the patient's insurance policies on file. The new higher warning level -- a red icon instead of yellow -- indicates that the X12.835 conflicts with the patient record in a serious way, such as a mismatch in policy type. Recall that AngelTrack is sometimes uncertain whether an X12.835 is from the primary, secondary, or tertiary, because AngelTrack's patient records may be incorrect, and because X12.835s from secondary carriers routinely misreport themselves as primary adjudications.
  6. The aforementioned problem -- Medicaid secondary carriers returning X12.835s claiming to be primary adjudications -- is now handled more gracefully. See Dealing With Medicaid-Integrated or "Dual Complete" Type Policies for details.
  7. When importing an EDI document or recording a manual payment event, there is a new "Automatic workflow" option, for use in deciding how the new payment affects workflow (payor + postprocess status). This option uses a new algorithm, still in beta testing, which looks at payment events and postprocess data in order to choose the dispatch's next workflow move. The results of the automatic decision can be reviewed afterward and countermanded if necessary.
  8. The aforementioned algorithm also offers workflow suggestions, displayed on the "Billing" tab of Dispatch Edit underneath the "Workflow location" field.
  9. Updated schematrons from AL, CA, MA, OK, and PA.
  10. Updated national schematron from the NEMSIS TAC.
  11. When a coded trip has neither a date of injury nor a date of symptom onset, e.g. an interfacility transfer, the date of service will now appear in CMS-1500 box 15, rather than in box 14. The date qualifier will still be 454. (This change mimics the 1500s generated by ClaimMD.)
  12. New city/state report: Assessments By Symptom or Impression, useful for COVID-19 analysis because it can search all of the symptom ICD-10s and impresson ICD-10s recorded in the PCR assessments.
  13. New city/state report: Oklahoma State Run Log, may be useful for other regions too.
  14. Billing grids now display the date of service in addition to the date of activation, for trips which activate just before midnight but which do not commence transport until the next calendar day.


Index of all release notes for all releases