AngelTrack 2.1 build 490 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. ATTENTION ALL TEXAS PROVIDERS - The Texas trauma registry is migrating to NEMSIS v350 this weekend. Please read this carefully:
   • All trips with a date of service prior to 2023-11-12 (this weekend) will be uploaded to the older (v334) Texas trauma registry webservice, which will come back online 2023-11-13 and remain availalble for several months so that you can clear your backlog. Your existing upload credentials will keep working as-is.
   • All trips after the cutover date will be uploaded to the newer (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 will receive 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 DEACTIVATE YOUR EXISTING (v334) TEXAS UPLOAD CREDENTIAL. It should remain untouched, because AngelTrack still needs it to upload trips occurring before the cutover date.
   • 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 upload 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 beginning 2023-11-12.
2. Invoices printed as CMS-1500s will now print the line-item costs in box 24F... provided that the invoice's charges, mileage, and minutes all still add up correctly (as they did when originally generated). If a biller edits the line items in an invoice such that the totals no longer match, or if the counterparty's price schema has changed since the invoice was generated, AngelTrack will leave box 24h empty to avoid confusion.
3. Updated schematron from VA.
4. Support for Mexico phone numbers and ZIP codes, and for Puerto Rico geocoordinates.
5. Fixes for the customer self-pay portal.

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 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.
2. 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.
3. 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.
4. 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.
5. Build 483: AngelTrack is now integrated with Pulsara. To learn more, read the Pulsara Integration Guide.
6. 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.
7. 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.
8. 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!
9. 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.
10. Build 478: AngelTrack is now approved for NEMSIS v350 operations in Orange County, California. Providers in Orange County please read the following. OCEMS now directs you to begin your "Training" phase, where you teach your crews to operate a v350 PCR. However, AngelTrack has already been showing a v350 user interface to your crews for the past 18 months, so no retraining is necessary on that aspect because the PCR will not change. The only differences your crews will experience after California transitions to v350 are:
    1. California's v350 schematron will take effect, imposing a slightly different set of data validation rules; and
    2. A mandatory custom PCR field will appear, asking about the trip disposition. This field offers a selection of custom values dictated by Orange County, and is independent of the traditional five-field "Disposition" block asked by the Followup page. This custom field must be answered for every PCR, even when no patient contact occurs, and AngelTrack cannot auto-fill it for you because the choices require information which AngelTrack does not possess.
    After the training period, you must contact CA-OCEMS and book your "mock call" evaluation, where you will run a mock call and input a PCR for upload to OCEMS for review.
11. Build 477: The Customer Portal for Facilities now allows your facilities to input a customer service rating, 1 to 5 stars, for each trip, to give feedback on how well your dispatchers and crews provided service. To learn more, read the Collecting Customer Service Ratings from Facilities Guide.
12. Build 476: Custom PCR fields now have more options and flexibility. To learn more, visit the Custom EMS PCR Fields Guide.
13. Build 475: New "self-dispatch" mode, for providers who don't have a dispatch office, where the crews receive calls directly from a call-center. To learn more, visit the Self-Dispatch PCR Guide in the knowledgebase.
14. Build 475: Any employee who is both a Crew member and a Call-taker now has all the privileges conferred by self-dispatch mode, allowing them to book their own calls, place themselves on-shift, use the crew-side dispatch board, and self-close their own trips.
15. Build 474: The writeoff/sold system is overhauled. To learn more, visit the Writeoff Guide in the knowledgebase.
16. Build 474: AngelTrack is integrated with Stryker LIFENET to import ECG-monitor data from LIFEPAK devices. To learn more, please see the Stryker LIFENET Integration Guide.
17. Build 472: AngelTrack is proud to announce its new Contextualizer technology, which helps crews understand and resolve State Data Validation error messages by tracing them to their underlying PCR datafields, making it easier to understand how to make the necessary corrections.