AngelTrack 2.1 build 502 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.

Improvements and New Features

1. Many improvements to the NEMSIS XML import feature, allowing bypass of the PCR. To learn more, visit the Import NEMSIS XML Guide.
2. New built-in stroke screen: Orange County CA.
3. New ventilator fields on the PCR-Airway tab.
4. Bulk NEMSIS XML exports will now be broken into 20MB blocks to avoid choking any downstream importers.
5. The Postprocess Workflow API has a new webmethod by which your biller can retrieve a list of all dispatch IDs at Billing Office, as well as their queue locations.
6. Updated schematrons from OH and VA.
7. TEXAS PROVIDERS please review the notice below regarding the Texas Trauma Registry migration to NEMSIS v350.

Notice for All Texas Providers -- ACTION REQUIRED

The Texas trauma registry has migrated to NEMSIS v350. Please read this carefully:

• All trips with a date of service prior to 2023-11-12 are no longer reportable, because the old (v334) Texas trauma registry webservice is now offline.
• As such, we have disabled your existing v334 upload credential.
• All trips on or after 2023-11-12 are reportable to the new (v350) Texas trauma registry... but for this, you must re-register your agency with Texas EMSTR and go through the process to obtain new upload credentials. You have already received an email blast from Texas EMSTR with all the necessary instructions.
• For each of your existing (v334) Texas upload credentials, your AngelTrack server now has a new blank credential record for v350, into which you will place the new upload credential issued by EMSTR.
• DO NOT EDIT OR REACTIVATE YOUR EXISTING (v334) TEXAS UPLOAD CREDENTIAL. It should remain disabled but still properly configured, in case Texas later reactivates their v334 webservice to accept backlogs.
• AngelTrack has already tested against the new EMSTR webservice and proven to work correctly, so all you must do is obtain the v350 credential and place it into AngelTrack.
• AngelTrack will do everything else automatically... but you MUST re-register your agency with EMSTR and follow their process to obtain a v350 webservice credential; alas AngelTrack cannot do that part for you.
• YOU MUST COMPLETE THESE STEPS or else AngelTrack will not be able to upload any of your trips.

Reminders of Upcoming Events

1. By end of Q1 2024, all AngelTrack servers will reject any connections originating from outside North America and ANZAC. If you have a biller in India, or if you intend to travel to foreign countries and want to access your AngelTrack server while you are there, then you must use a VPN client that can re-originate your traffic within the aforementioned countries. This is cheap and easy, but please arrange it beforehand, before AngelTrack's geo-restrictions go into effect. To learn more, visit the IP Blocklist / Geographic Restrictions Guide.

Reminders of Recent New Features

1. Build 500: The offline PCR now supports custom EMS PCR fields.
2. Build 500: When creating custom EMS PCR fields, you can now create a custom picklist, including a configurable minimum value.
3. Build 499: Your built-in service charge types can now each stipulate a set of tags. Whenever someone adds that tag to a dispatch, AngelTrack will automatically levy that service charge against the dispatch. To learn more, read the Service Charges Guide. You can edit your service charge types list by visiting the Settings page.
4. Build 499: You can now add custom EMS PCR fields to many of the PCR tabs, including vital signs and assessments. To learn more, read the Custom EMS PCR Fields Guide.
5. Build 499: You can now create a schematron for your agency, and upload it into your AngelTrack server, to impose whatever warnings or errors you like on PCR completion. To learn more, read the Custom EMS PCR Validation Rules Guide.
6. Build 498: All AngelTrack home pages (Home, Dispatch, Billing, Supervision, HR, Sales, and Fire) now offer access to Isidore, AngelTrack's support AI who can answer questions by reference to AngelTrack's knowledgebase and training materials. To access Isidore, find and click the link named "Ask Isidore the Support AI".
7. Build 498: AngelTrack is now licensed on a feature-buffet system. All current customers are grandfathered into all available features for the next twelve months, such that the price you've been paying for your AngelTrack license will not change during the grandfather period. To learn more, take a look at the Feature Buffet Guide and the Authorization Guide.
8. Build 497: AngelTrack now has an API key system, which is a more flexible way of managing third-party access to your AngelTrack server, particularly including server-to-server delgation from your friendly affiliates. The following AngelTrack APIs now accept API keys:
   • CAD API Accepting Nemsis including affiliate server-to-server delegation;
   • Postprocess Workflow API; and
   • Movi Integration
9. Build 497: AngelTrack's timeclock now has a Terminal mode, allowing you to designate a specific computer in the dispatch office for all clock-ins and clock-outs. To learn more, read the Timeclock Terminal Guide.
10. Build 496: AngelTrack is now integrated with Tyler Tech Enterprise CAD, to automatically import trip data onto your dispatch board. To learn more, visit the Tyler Tech Integration Guide.
11. Build 495: If you delegate calls to an affiliate who also uses AngelTrack, you can now auto-transmit the delegated calls electronically, rather than via email. To learn more, refer to the Affilaite Server-to-Server Delegation Guide.
12. Build 493: There is now a preference setting allowing you to select v340 or v350 as your default NEMSIS export format.
13. Build 493: AngelTrack has completed NEMSIS v350 national re-certification.
14. Build 489: The virtual credit card terminal is now available, allowing your dispatchers to process credit card payments from customers during call-taking. To activate this feature, first you must set up your Stripe account first, then follow the instructions on the Virtual Terminal Guide.
15. Build 486: When manually importing an X12.835 EOB, AngelTrack will show a blinking warning flag next to any claim where the primary carrier has adjudicated an allowed price below 98% of the Medicare rate for that ZIP code, to help you identify claims where the carrier has made an erroneous adjudication.
16. Build 485: The customer portal now has a preference setting that determines how much advance notice is required for customer self-booking. The default is 24 hours.
17. Build 484: In all price schemas, you can now have a different rate for miles 0-17 than for miles 17+, the way Medicare does.
18. Build 483: AngelTrack is now integrated with Pulsara. To learn more, read the Pulsara Integration Guide.
19. Build 482: The PCR Narrative page can now accept an upload of a voice memo, and will use AI to transcribe the voice memo to text for the narrative.
20. Build 481: The PCR now has full OCR barcode scanning of patient driver's licenses, to automatically scrape demographic data with which to populate the PCR-Patient page. To learn more, visit the OCR Barcode Scanning Guide.
21. Build 480: AngelTrack can now pull case data from your Philips Tempus Pro monitors, via the Philips Corsium cloud service. To learn more, check out the Philips Tempus Pro Monitor Integration Guide. This feature is currently in beta, so your mileage may vary; please let us know how well it works for you!
22. Build 478: If you receive a one-star rating via your customer portal, AngelTrack will auto-submit a "Facility request for service" incident record, so that your supervisors and salespeople can intervene. Via your employee settings, you can register to be automatically notified of new incident records. To learn more, look at the Customer Service Ratings Guide.
23. Build 478: AngelTrack is now approved for NEMSIS v350 operations in Orange County, California.