AngelTrack is cloud software, just like Netflix. All of its IT infrastructure is provided and maintained for you. Do not waste your money on old-fashioned software that requires you to purchase and maintain any server hardware.
The Deployment Punch-List will walk you through the decisions and choices you will make in rolling out the software.
Not for AngelTrack's sake. It does not ever require IT skills to deploy and use.
You will still need someone with basic IT skills to:
You may use any brand you wish.
For crews, tablets need to have four things:
Wireless (QI) charging is also nice to have, because it alleviates all the wear-and-tear on the charging port.
For dispatchers, tablets are needed only if dispatching from the road; otherwise, they can use a regular computer or laptop, whether at the office or at home. In any case, dispatchers do not need to have GPS functionality on their devices.
For field supervisors, best to get them the exact same kind of tablet as the crews have.
For everyone else in your organization, their devices must have a supported web browser (see list above), but whether they also need GPS and mobile internet service is up to you.
Use the Online Estimator to figure your total first- and second-year costs including AngelTrack licenses, mobile devices, cellular service plans, and typical losses.
Yes... but devices used by crew members need to have GPS receivers, mobile internet service, and a supported web browser. See above.
You may be able to add GPS functionality to a device by means of a GPS USB dongle... but dongles don't last long in EMS. They get snapped off.
Likewise for mobile internet service; the cellular carriers will sell you a dongle by which you can add their service to any device, but be prepared to replace it once or twice a year.
It would probably be simpler and more relaxing to just buy new iPads, which have everything already built-in. Your state EMS office may even have a cost-share that will help you pay for them.
AngelTrack runs entirely in the browser.
There is a free app called AngelTrack Beacon that you can install if you want 24/7 location tracking of the device, but it's optional.
AngelTrack's training materials and videos are all online for free. Just direct your crews to the AngelTrack Training Portal, where they will register using their email addresses, and then access all the training courses they wish, no charge.
When you initiate AngelTrack service, your reseller will also conduct live-online training with your company officers.
Your AngelTrack license is "EMS in a box", including dispatch, PCR, QA, billing, timeclock, checklists, HR, fleet, crew scheduler, state trauma registry uploader, and customer portal... everything you need.
At the gold license level, you also get access to the Report Portal, which allows you to roll your own custom reports... but this is not needed to run your EMS operation, because AngelTrack's built-in reports already provide excellent coverage of your operational data.
New features and improvements are published about twice a month. You get all those too, for free, automatically.
Nor do we collect any data about you, or about your employees, or about your customers.
See also the official AngelTrack LLC privacy statement.
We think that's sleazy, and will have no part of it.
AngelTrack cloud servers are hosted exclusively at Rackspace, the top-shelf hosting provider.
AngelTrack is certified compliant with NEMSIS v3.4.0 and v3.5.0, the two newest versions of the specification.
AngelTrack natively supports both v3.4.0 and v3.5.0. It does not use a translation XSLT to do so. The user-interface is unified in a clever way, so that your crews will not require any retraining when your state moves to v3.5.0.
Data can also be output in the older v3.3.4 format, in case your state trauma registry requires it.
AngelTrack's first live dispatch with patient transport was February 14th, 2012. That was AngelTrack 1.0.
Since then, AngelTrack has updated twice or thrice a month, every month. Some updates are minor, some are major, depending on which feature requests and bugfixes were included. AngelTrack is in a state of continuous improvement. See for yourself by checking the index of release notes.
AngelTrack was designed from scratch in America by two American EMS owners, and 100% written from scratch in America by American software developers.
As of December 2021 (build 412), AngelTrack's codebase is as follows:
|Language||Lines of Code|
|HTML, CSS, and XSL||97,584|
The numbers include comments and the help documentation. They do not include whitespace, external libraries, third-party XSLTs, and stock data like lists of cities (263,908 pre-installed) and medications (628,906 pre-installed).
However, all source code is open for inspection to anyone appearing in person at the Missouri development office. This invitation does not extend to employees of competing software firms.
All of your data lives in a dedicated Microsoft SQL Server 2016 database.
All of your data is stored on RAID-10 SSDs ("solid state drives"). Your data will never touch a spinning hard-drive.
Your AngelTrack cloud server is available 24/7/365, subject to the weekly maintenance windows.
Maintenance windows are times that AngelTrack support staff may update or upgrade your cloud server, in order to deploy new AngelTrack features plus any new operating system patches from Microsoft.
Every Sunday morning (i.e. late Saturday night) from 02:00 to 04:00 Central Standard Time, your cloud server might be inaccessible if it is being updated with AngelTrack improvements and/or Windows operating system patches. We say might be because these interruptions usually only last for ten or twenty minutes.
AngelTrack Support answers the phone 24/7/365, including holidays. There is always someone standing by to meet your needs.
The main AngelTrack Support phone is answered only by American citizens with EMS experience. If your question stumps the support guys, they have direct access to the developers.
No problem, they can just tether their workstations to their smartphones.
Or they could grab an available tablet from the crew area. AngelTrack allows them to do their entire job right on the tablet, without need of any installation or configuration process. All AngelTrack needs is a web browser and an internet connection.
Just make sure you've got a backup plan for your telephone service. If your telephones are VoIP, then they will go down too. Fortunately it is easy to configure your VoIP service to ring through to your dispatchers' cellphones. Just make sure you set that up before an internet outage occurs!
Firefox is not supported. AngelTrack will allow you to use Firefox anyway, if you insist, and it will work fine most of the time... but you will not receive technical support for Firefox-related issues in AngelTrack pages.
You may use the built-in Safari browser, but we think you'll like Chrome or Edge better.
If someone has turned them off in your browser, AngelTrack's login page will let you know.
Nor do you need Flash, Silverlight, Microsoft .NET, Acrobat, or any other browser addons. Those addons introduce security vulnerabilities into your browser, so you should uninstall them if possible.
AngelTrack's pages render phone numbers as clickable links of type "tel:", like this one:
(800) 946-1808 click to call AngelTrack headquarters
If you click a tel: link, your browser searches your computer for an application registered to handle it. If no such application is installed, an error message is displayed.
Usually a VoIP "soft phone" or "software telephone" application will register itself as the handler for tel: links. Once that's done, clicking a link will pop up the VoIP software and dial the number automatically, it's super convenient.
Naturally, tel: links work nicely on smartphones, and sometimes tablets.
AngelTrack's doorbell ("ding-dong") and timeclock ("ker-chunk") sounds do not play in mobile Safari on iPhones and iPads. This is a restriction imposed by Apple Inc. for business reasons, and there is no workaround.
On older versions of Safari, you must kill off the Safari process, then relaunch it. When it connects back to AngelTrack, it will then prompt you again to use your location. To kill a process on an iPad, quickly double-click the home button. Swipe left or right to find the desired process. Swipe the process up as if throwing it off the iPad. Then click the home button again to return to normal.
On newer versions of Safari, you can click the "aA" icon at the top-left corner, select "Website Settings", and change the "Location" setting to "Allow".
By default, and unlike Chrome, Safari always asks for location permission for each new page.
On newer versions of Safari, you can click the "aA" icon at the top-left corner, select "Website Settings", and change the "Location" setting to "Allow". It will then permanently stop asking.
You need to restart your browser.
The ∵ symbol indicates that the associated checkbox or radiobutton will remember its setting, even when you close your browser and come back later.
Some will remember their setting just for an hour, or just for the day, or for longer, as we judged was appropriate.
AngelTrack allows your mobile device to display dates and times in whatever manner it sees fit. Therefore you need to configure your mobile device to display 24-hour times.
AngelTrack normally allows your browser to decide how to display the date in a date-picker; your browser, in turn, obeys the date/time settings configured in your computer's operating system. Therefore you must change your computer's date and time format settings, and then restart your browser.
AngelTrack allows your browser to provide the date and time pickers, if your browser is known to support HTML5 date and time controls. However, not everyone likes the controls provided by the browser.
If you would prefer to use AngelTrack's traditional (non-HTML5) date and time pickers, then go to your AngelTrack home page, click Support, and find the link to the "Date/Time Control Preference". That page will let you try both control formats, and choose the one you prefer.
Your preference will be remembered on your current computer; it will not affect your other computers or mobile devices; in this manner, you can set a different preference on your desktop (where you may prefer the traditional controls) versus on your tablet (where the HTML5 controls are usually better).
You need to restart your computer. Then, when you return to the affected AngelTrack page, press CTRL+F5 to force reload all of the page's scripts.
First, force-reload all content on the page:
If still no luck, then restart the browser by closing all open browser windows and tabs.
If still no luck, then restart the computer.
For crew use, AngelTrack tolerates temporary loss of signal, but needs to have an internet connection most of the time.
If you frequently operate in rural areas where the cellular signal drops out, then install a weBoost or similar cellular booster in your vehicles. With one of those devices installed, your crews can then use ordinary tablets and smartphones. This is better than an offline PCR, because it allows live progress data to flow back and forth between crews and dispatchers.
Note that a hotspot will not suffice for rural low-signal areas; you need an actual signal booster... but don't worry, these devices cost less than $600 per vehicle.
The short answer is:
...including the data used by streetmap features. To see how this was calculated, read the AngelTrack's Data Plan Usage document.
Use all the bandwidth you wish, no charge; we purchase it by the terabyte. :)
Book the call like this:
If providing the service for free, then uncheck the ☑ Billable checkbox.
If charging a fee for the service, then set "Bill to" the facility. If the customer is not a nursing home or hospital, then you can configure them as an affiliate, allowing you to use AngelTrack's invoice to process the fee.
If misfortune strikes and your crew does end up treating someone, the crew can create/attach a patient record in the PCR by themselves. If they end up treating a second patient, then close the first dispatch and then dupe it to create a second dispatch, in order to give the crew a fresh PCR record to fill out. You will probably mark the second dispatch non-billable, unless your agreement with the customer stipulates a charge for each patient treated.
If transport is necessary, a dispatcher can (at any time) edit the dispatch and add a destination. If billing separately for the standby service and for each transport, then each transport must be a separate dispatch from the "Standby" dispatch. Remember you can assign multiple dispatches to the crew: the "Standby" call, plus a transport call for their patient.
Obviously you can record the broker's name in the "Caller name" field, but unfortunately that is free-form text that is prone to typographical errors.
A better way of marking certain dispatches is to use the tags system. From "Dispatch home" you can open the "Tags list", and create whatever tags you need. You can create a tag called "Rolled call from broker" for example. Your dispatchers can then set the tag on certain dispatches, and you can pull reports on that tag later.
If you are going to bill the broker for providing the service, then you should mark the dispatch as ☑ Bill affiliate. This requires you to already have the broker configured as a roll-from affiliate; to learn how to do that, read the Affiliates Guide.
You must flag the facility records of all facilities with which you have a contract. Once that flag is set, AngelTrack will automatically tick the facility payor box for you when booking a call to or from the facility.
Don't ignore this issue; make sure you get your facility contracts registered in AngelTrack so that your bill-to checkboxes are being automatically set correctly during call-taking. When they are set correctly, AngelTrack can automate many billing tasks, first and foremost being the assembly of facility invoices.
To learn more about setting up your facilities in AngelTrack, read the Facility Guide.
Go to Settings and select the "EMD Cards" item. You can edit every section of every EMD card.
The State of New Jersey developed standard EMD content, and then graciously released it into the public domain for others to benefit from. AngelTrack uses that content verbatim.
Yes, the "Dispatcher Efficiency Report" judges and compares all of your dispatchers on their ability to 1) minimize the distance between each dropoff and the next pickup, 2) identify opportunities for overlaps, 3) identify opportunities for double-loads, 4) minimize late pickups and late drop-offs, and 5) choose double-loads that save distance versus single-loading.
You'll find the report under Dispatch Home. By default it ignores nights and weekends, because it is not practical to measure dispatcher efficiency when calls are very widely spaced, and when there are only 1 or 2 crew units available... however, if you wish, you can tick the box to include nights and weekends in the analysis.
To learn how to interpret the report, read the Dispatcher Efficiency Guide.
This restriction was a conscious design decision in AngelTrack.
Because so much happens to a dispatch in postprocess -- report completion, QA, insurance review, billing, invoicing -- it was decided that re-opened dispatches would be too disruptive. It is better if every participant in the system can operate on the core assumption that "Once it's closed, it stays closed".
You can, at least, visit Dispatch Followup and change the execution status of a closed call, from "cancelled" to "completed" to "delegated"... but even that change has serious billing implications, so make sure you understand the impact before doing so.
You can also cancel and then dupe a closed dispatch, if you absolutely must re-run it. The original dispatch will thereafter reflect its own history up to the point of cancellation, and then the new dispatch will start from there.
Like the "no reopening" restriction, this restriction was a design decision aimed at minimizing disruptive changes. Remember, AngelTrack was designed to run large call centers with dozens of dispatchers.
If you absolutely must edit the activation time, assignment time, and/or closure time of a closed dispatch, there is a way to do so. It is an intentionally inconvenient task. You'll find the procedure in the online help article Retroactive Editing and Booking.
If you wish to change the assignment of a closed dispatch -- from one shift to another, or to or from an affiliate -- simply open the "Dispatch Edit" page and click on the current assignment (it will be a link). You will be taken to the "Dispatch Assignment" page which will show the list of shifts that were active at the time the dispatch was open, as well as the usual list of affiliates that were open at the time.
FR (First Responder) shifts are always allowed to respond to any call under any circumstances.
Not only is it legal for them to do so, it is also tactically useful when managing an overdue pickup. When the scheduled truck is running late and the patient is angry, send a First Responder to start getting the patient ready, rounding up the paperwork, collecting signatures, and reassuring the family members that transport is coming. By the time the FR has everything ready, the scheduled truck will be arriving.
AngelTrack knows where crews are only when they are accessing AngelTrack on their mobile devices. When they put their devices back to sleep, the location data is no longer uploaded; after ten minutes with no upload, AngelTrack will decide it no longer knows where they are.
If you want continuous crew location data even when their mobile devices are asleep, you must install the AngelTrack Beacon app on the devices. It is lightweight and easy to install. It is discussed in the next section.
Remember, the journal only shows changes. If the journal does not mention any Billing Notes, then the Billing Notes have not changed... ergo, the Billing Notes were written by the dispatcher who originally booked the call, and have not been changed since.
AngelTrack can track your vehicles' city stickers, warning dispatchers which trucks have the necessary sticker to run the call. To learn how to enable this feature, read the Certificate Tracking Guide.
Your AngelTrack administrator must allow Unattended Dispatch Mode. Once allowed, any dispatcher can activate or deactivate the mode. When active, crews can close out their calls by pressing the progress button one final time after they press it to mark "back in service".
To switch the Live Map into dispatch mode, select the ☑ Shift radiobutton. To learn more, read the Dispatching from the Live Map Guide.
The self-serve feature is part of the Customer Portal, which your customers may already be using.
To learn how the self-serve portal works, and how to activate it (it is off by default), read the Customer Portal Requests for Transport help document.
The feature includes a help document for use by your customers, who are learning how to use the portal to request transport: Using Your Customer Portal
Dispatchers must NOT include the suite number in the street address field, as it will choke the mapping software on the mobile devices. There is a separate field for the suite number.
If the MICU certificate type is enabled, then AngelTrack assumes that an ALS crew must have a MICU certificate in order to qualify as a MICU shift.
Disable the MICU certificate type if an ALS crew in a MICU vehicle automatically qualifies as a MICU shift. To learn more, read the MICU certificate help.
There is no HCPCS billing code for BLS-2. BLS-2 is strictly a state-compliance issue.
AngelTrack does recognize when crew members and shifts qualify as BLS-Intermediate or ALS-Intermediate, but again, these are not billable distinctions.
The street-map applications on mobile devices will sometimes second-guess the street address that AngelTrack gives them... and sometimes they guess wrong.
For example, suppose the patient lives at "1201 Woods Lawn Drive". And suppose the dispatcher mistypes it as "1201 Wood Lawn". When AngelTrack's PCR then launches the street-map app, and passes it "1201 Wood Lawn", the app may incorrectly second-guess the address as "1201 Woodlawn Court" instead.
Internally, AngelTrack never alters or second-guesses the street address typed in by the dispatcher.
Piece of cake! See here for details: Multiple Responders guide
It is part of the Shifts system. It works by scheduling your shifts -- i.e. your vehicles and their crew members. In this respect, it is vastly superior to normal employee schedulers, at least for EMS purposes
To access it, click the shifts icon, found in the middle of the top icon bar. That will open the Shifts page. On that page, the "Active" tab shows which vehicles and crews are current on-duty, while the "Schedule" and "Calendar" tabs contain the crew scheduler.
It's so easy, you will hardly notice that you are doing it.
When the Dispatch Assignment page shows you the shifts that are available and eligible to take a dispatch, the list automatically includes all relevant future shifts... and it takes account of their recurrences and exceptions.
As such, you can even preassign a dispatch to a future recurrence of a future shift.
Use an exception.
To quickly do this right from the calendar, click the scheduled shift in question to open the popup menu, and then click the "+ Add exception" choice. In the popup exception editor, select the ☑ Shift is cancelled on this date option.
Refer to the "Holiday" section of the Scheduled Shifts Guide.
From the "Schedule" tab on the Shifts page, find the pending shift and click the "Start now" link.
It is shown as a calendar view at the bottom of their Crew Home page. If the calendar is invisible, it means they are not scheduled to work during the preset month.
Consequently, they can access it from home or while mobile, without the need to clock-in.
Each employee must configure his or her messaging settings and opt-in to those notifications. Once that's done, AngelTrack will send them an SMS or email whenever they are one hour away from the activation of a scheduled shift.
Beacon is a small Android / Apple iOS app that you install into your company-owned mobile devices. It runs in the background and silently monitors the device's movements, reporting in to your AngelTrack cloud server every few minutes.
When using Beacon, your mobile devices will show their live position in AngelTrack's maps and grids even when nobody is using the device... whereas without Beacon, AngelTrack knows the device's position only when someone is using the web browser.
AngelTrack's GPS pins -- collected from the browser during normal use, without any Beacon app -- are as accurate as the device can be.
The sole benefit of Beacon is: it is always on. You will always have live location data for an employee or vehicle that has the Beacon app... whereas with normal AngelTrack, you get live location data only when the employee is actively using their device.
The use of Beacon is included in your AngelTrack license.
The Android version of the Beacon app is available in the Google Play store, as a free download.
The Apple iOS version of the Beacon app is available in the iTunes Store, as a free download.
Once you've downloaded it onto your mobile devices, use your AngelTrack cloud server to issue tokens for the devices. The device reports its position along with the token; the token identifies the device as belonging to a certain vehicle or to a certain crew member.
To learn more about configuring and using Beacon, read the GPS tracking guide available in the online help.
Security is provided by the token, which cannot be guessed by a hacker. Read the aforementioned guide to learn how Beacon's security works.
Beacon phones home once every six minutes when the device is moving slowly, or once every two minutes when the device is moving quickly.
Yes, with their consent of course.
Since they take their personal cellphones everywhere they go, they would be ideal for reporting their individual positions while on duty. When off duty, the employee can easily switch the beacon back off.
Employee tokens start with the letter E, and are used to report the position of one particular person.
Vehicle tokens start with the letter V, and are used to report the position of all crew members currently onboard. You'll use vehicle tokens when you assign your mobile devices to specific vehicles (regardless of who is onboard), rather than to specific employees.
Beacon does absolutely nothing except check GPS position and then upload it to your cloud server.
Its source code is available for inspection by anyone appearing in person at the Houston, Texas development office.
If the Beacon app is using an employee token, that employee must be marked as a crew member and/or a salesperson, and their employee account must not be marked inactive.
If the Beacon app is using a vehicle token, that vehicle must not be marked inactive, and it must be in an active shift. Remember, location pings from vehicles are used to render the locations of the crew members who are onboard.
You might've mistyped the token string. It must be typed exactly, and for security purposes the app does not have any way to check whether the token is mistyped.
Also, double-check that your cloud server's name is typed correctly.
If everything is typed exactly right but it still doesn't report a position, contact AngelTrack support.
In AngelTrack, only employees have positions.
If a position report is received from a vehicle token, the position is recorded for all employees in that vehicle. The employees are plotted on the map, but the vehicle itself is not.
Individual employees can upload positions for themselves using employee tokens, which will override any position information inherited from their vehicles.
Refer to the Beacon Troubleshooting Guide.
Yes; AngelTrack is not married to one particular clearinghouse.
AngelTrack is known compatible with the following clearinghouses:
If you use a different clearinghouse, then discuss this with your AngelTrack integrator when planning your deployment.
AngelTrack LLC recommends Office Ally, and enjoys a good working relationship with them.
If you wish to migrate from your current clearinghouse to Office Ally, AngelTrack Support personnel will walk you through it. Don't be intimidated by the thought of switching clearinghouses; we help EMS companies do it all the time.
You must purchase your AngelTrack license (rather than getting it for free via an AngelTrack billing partner), and your billing agency can continue doing exactly what they do today.
If you wish to integrate your billing agency into your AngelTrack system, create "biller" user accounts for the billing agency's employees. They can then login from their office and service whichever billing queues you desire. They can even do your QA reviews, prior authorizations, and invoices if you so direct. Read the Outsourcing QA and Billing Guide in the online help for more details.
If you do NOT wish to integrate your billing agency, then you will continue doing what you've always done: bundle up run reports as .PDFs or as NEMSIS 3 .XMLs... whichever format the billing agency prefers. AngelTrack will zip them up for you, so you can send them via email or FTP. To learn more, read the Detached Biller Guide.
NEMSIS 3 .XMLs can be easily imported into modern EMS billing software. Some billing software can also import 837P documents.
Bundling of run reports is trivially easy to do using the Insurance Filing Queue's exporter. Later, the billing agency will send back EOBs, which you input back into AngelTrack as Payment Events. If your billing agency can send you electronic (X12.835) EOBs, then AngelTrack can import them in bulk. If all you can get is paper EOBs, then you must input them by hand, a process which takes about about 1 minute per claim.
NEMSIS is the National EMS Information Systems committee, which regulates the format of data files used by EMS software to exchange data. The NEMSIS specification requires certain data to be included in a certain way, so that a dispatch application can talk to a PCR application can talk to a billing application.
NEMSIS version 3 is the data format that your state trauma registry uses If using an external billing application instead of AngelTrack's billing system, AngelTrack can bulk transfer your run reports into it using the NEMSIS 3 format... assuming the billing application is capable of importing data in that format.
NEMSIS version 2, aka NEMSIS "gold", is the obsolete version.
NEMSIS version 3 is the current specification. AngelTrack is certified compliant with NEMSIS 3.
If using an external billing application instead of AngelTrack's billing system, AngelTrack can bulk transfer your run reports into it using the NEMSIS 3 format... assuming the billing application is capable of importing data in that format.
He can integrate with AngelTrack and then use AngelTrack's invoicers for that task, in order to enjoy the advantage of a unified system for tracking every receivable regardless of whether it went to insurance first. For example, your uninsured stretcher transports and all of your wheelchair services will never go through insurance claims, but should all be included on a facility's or patient's invoice. AngelTrack handles that automatically, and there is every reason to let your outside biller make use of that feature.
Or he can remain independent, and just send back copies of paid invoices. You must then record those paid invoices as Payment Events in AngelTrack. (Or you can just ignore the rest of AngelTrack's billing workflow, trusting that the billing agency will not miss any receivables.)
Your documents are accessible from anywhere in America, as you know. But the state is surely looking for a specific answer, so you should reply "All documents are stored at [my head office]". From that location you can use a browser to retrieve whatever documents your state requires.
All documents in AngelTrack are stored as long as the Data Lifetime Rules specify, so long as you maintain an active AngelTrack license.
MACs and individual insurers have non-standard expectations for the 837P document and non-standard contents in the 999, 277CA, and 835 reply documents. So, it is not possible to generate a single 837P document that is guaranteed to satisfy every MAC or every insurer. It is the job of the clearinghouse to understand those expectations and adjust each 837P to meet them.
AngelTrack does not wish to fight that battle, so we guarantee compability only with the OfficeAlly clearinghouse and with the Noridian MAC.
If you use a different clearinghouse, speak with your AngelTrack integrator. He or she will review your clearinghouse's 837P Companion Guide and give you a time estimate on when compatibility can be guaranteed. It usually takes just two weeks.
The insurance queues offer to export any dispatch as a filled-out CMS-1500 .PDF. When you view the .PDF on your screen, you will see the CMS-1500 red form, and all the claim data filled in to the form's editable fields. You can perform additional edits as necessary, right in your browser or .PDF editor.
When you print the .PDF, only the data will be printed: the red boxes will not be included because you must use pre-printed CMS-1500 forms that already have the red boxes.
AngelTrack will print the carrier's mailing address at the top of the CMS-1500 only if a mailing address is on file for that carrier's payor ID.
To view your list of payor IDs, and to add mailing addresses and telephone numbers to them, select Insurance Payor ID List from the Billing Home page. If your clearinghouse includes mailing addresses and/or phone numbers in its payor ID list, then AngelTrack can import them in bulk, via the Import Payor ID List feature available from the aforementioned page.
Unfortunately, most payor ID lists provided by clearinghouses do not include mailing addresses. You'll be lucky if you even get phone numbers.
Refer to AngelTrack's CMS-1500 Crosswalk document.
AngelTrack is a single unified database, which follows every trip from call-taking to final payoff. That is AngelTrack's beauty and its power. It does not have any facility for importing call data midway through that process.
AngelTrack has several methods for calculating commissions, in order to support all three standard commission agreements:
To learn more about calculating commissions in AngelTrack, read the Commission Reports guide.
You may be accustomed to filing round-trip transports as a single claim. Most billing software advises you to do this, adding all services for the date into a single claim... but most billing software is not built for EMS, so this is bad advice.
Some EMS billers insist that it works. They use the modifier to differentiate the outbound trip's service lines from the return trip's. We STRONGLY recommend against this practice, because it too often happens that insurers deny the return trip but send back an approval for the outbound trip. If your biller is not on their game, they may see the approval but not notice that only one trip was paid for.
During our integrations, we have discovered this exact error happening at multiple customer sites. Customers have lost a quarter million dollars a year on this one mistake... and only the last six or twelve months of mistakes can be appealed and re-filed. It's a crushingly expensive mistake.
And even if your biller does notice that only one trip was paid, it's a hassle to split off the return trip and refile the claim, with no guarantee of success.
In our judgment, a round-trip should always be filed as two separate claims. In addition to the aforementioned reasons, the fact is that diagnosis codes justifying the outbound trip are often very different than the diagnosis codes justifying the return trip. And all of the subsequent claim tracking is simplified.
When importing an EOB, AngelTrack creates a payment event record for each claim in the EOB. The payment event record summarizes the action taken by the insurer, and includes the claim's 835 content. Using the "Payment Event Edit" page, you can view the 835's original content (the section of the 835 that pertains to the claim in question). You can also view it decoded into neat tables, showing each service line, adjustment, reason code, and explanation.
(This feature is only available if you use AngelTrack's EOB importer to digest the electronic EOBs (i.e. the X12.835 documents) returned by your clearinghouse. The feature is not available if you create your payment event records manually.)
The "Insurance Appeal Queue" offers a direct link to the latest payment event record for the dispatch. Just click the "Last EOB" link to view the decoded response from the insurer. You can keep that page open in a separate tab while you are filling out your appeal.
When claiming the above service codes against Medicare, AngelTrack will automatically add the GY modifier to those service lines, since Medicare will not ever pay for them. Medicare will then remove the GY modifier when forwarding the claim to any secondary carrier, who might cover those services.
See this CMS bulletin and also this one for details.
If you don't want AngelTrack to automatically add the GY modifier in these situations, you can disable the feature by vising the Preferences page under Settings.
Novitas published article A54574, announcing a list of 395 "suggested" diagnosis codes for ambulance transport. Other ICD-10 codes are accepted of course, but any "suggestion" from Novitas carries weight. And anything Novitas does will soon be picked up by the other MACs around the country.
AngelTrack has a list of about a thousand ICD-10 codes considered relevant for ambulance transport. The code-pickers are populated with this list. If you wish to confine yourself to just the Novitas suggested codes, simply tick the "Hide codes not in the Novitas suggested list" checkbox. The code-pickers will then confine themselves to that subset.
AngelTrack will automatically tick the checkbox for you when the patient's primary or secondary insurance is Medicare.
When a state trooper pulls you over and suggests you slow down, you slow down.
AngelTrack's coding page already knows about the requirement and will offer you a choice of the five allowed codes.
If you select a mixture of original and replacement claims, or a mixture of chargeable and non-chargeable (encounter) claims, AngelTrack must divide them into separate batches, owing to how the BHT segment works in the 837P specification. BHT02 communicates whether the claims in the transaction batch are originals, and BHT05 communicates whether they are chargeable.
It used to work that way.
Then one day a customer's biller accidentally modified the retail price schema, thinking he was modifying a facility contract price. These contract prices (far below retail) were then claimed against insurance, causing a significant loss of revenue and a big hassle.
Then it happened at a second customer site.
That's when we decided to lock down the retail prices, consistent with our motto:
One mistake is the customer's fault, two mistakes is the software's fault.
Thus, today, only the ★ Principal Employee is permitted to modify the retail prices, and only AngelTrack Headquarters tech support can designate or redesignate the principal employee.
The "Gurney" service level works just like wheelchair. Most states do not recognize gurney service, so you can enable gurney service level and use it as your premium wheelchair service, with its own separate price schema.
To learn how to enable the gurney service level, read the Gurney Service Guide.
If you are coding and see that the ☑ GM modifier has been checked, it is because AngelTrack checked it for you. It does this when the transport times (beginning transport → arrived at destination) for the current dispatch overlap those of another dispatch in the same vehicle, indicating that two patients were being transported simultaneously.
Usually this is due to incorrect recordkeeping: either sloppy progress button presses by the crew, or sloppy followup data from the attending. Send the call back to QA with notes to check the transport times against the vehicle's other calls that day.
Open each dispatch by clicking its run ID. Switch to the "Billing" tab. Find the "Workflow location" field. It will give the reason why the dispatch was sent for special handling.
AngelTrack may already have such a report; if it does, we'll show you where it is.
If the report doesn't exist yet, you may be able to roll your own using the Bulk Excel Exporter under Billing Home. The exporter can filter down to a set of records, and then export them directly into Microsoft Excel™ or Google Sheets™ for further slicing and dicing. Almost 200 different data columns are included, so it probably has the data you need.
If the report doesn't exist yet, and can't be emulated by the Bulk Excel Exporter, but is easy to implement, then we will add it to the next build for you. New builds are published every week or two, so you won't have long to wait.
If it is not easy to implement, then we will add it if the report will obviously benefit other customers besides yourself. In that case you probably won't have to wait longer than one or two builds (i.e. two to four weeks).
If it is not easy to implement, and is not obviously useful to other customers besides yourself, then we will quote you a fee to code it up, along with a delivery schedule.
You might also be able to roll your own report in Microsoft Excel™ or Google Sheets™, using bulk data exported from the Bulk Excel Exporter or the Line Items Report.
For every transport, AngelTrack collects and verifies the vehicle's actual odometer readings. AngelTrack also calculates the normal mileage using a "moving average" statistical system. The statistical system is seeded with data from Google Maps™. After seeding, the data grows using odometer readings input by crews.
When filing an insurance claim, AngelTrack by default uses the actual odometer readings, although the biller can choose to claim the calculated normal mileage instead, as he or she sees fit.
When generating invoices, AngelTrack uses the calculated normal mileage, because it is more fair to both parties. To learn how the moving average works, and why it is more fair to all concerned, read the Mileages guide. You can opt out of the normal mileage system, and use plain odometer readings in invoices, by visiting the Preferences page.
See here: Pricing and Price Quotes
The Billing Activity Visualizer shows all billing activity, broken down by type of task. You can filter by specific billers and specific date ranges, to see exactly what tasks each employee did on any given day.
Remember: some billing tasks are much harder than others, so it isn't necessarily fair to say, "You did 20 tasks while your coworker did 40." You must weigh the tasks appropriately before comparing one employee against another.
If there is serious doubt about an employee's activity, you can download the raw webserver logs from the Support page. The webserver logs show every raw request made from every user, including date, time, IP address, and browser type.
Those three dates are separate and independent. Every payment event in AngelTrack has all three. To learn more about them, read the Critical Dates for Accounting explainer.
If you are filing a claim against a private carrier who pays for non-standard service lines (e.g. A0999), you can add these service lines to your claim right on the Coding page.
Scroll down to the section where you specify additional services like oxygen and ECGs. Click the link which reads "Add non-standard service codes", then click the plus sign to add as many as you wish.
Be advised: private carriers who pay for non-standard service lines usually require a few explanatory words in the "Note" field.
When you are recording the primary claim's adjudication from a paper EOB, you must include the chart of adjustment codes. AngelTrack collects those in order to pass them to the secondary carrier. To learn more, read the Payment Events Piecemeal guide.
Deactivated patient rates remain in effect for all attached patients. Deactivation simply means that no new patients can be attached to the rate.
Those two reports differ because the Revenue Accrual Report is only allowed to show you the monetary amounts associated with dispatches which are 1) marked billable, 2) not marked “cancelled”, and 3) which have price quotes (or prices adjudicated by insurance) on file. It does this so that its monetary amounts are suitable for accounting and tax purposes.
Whereas the Payment Event Finder shows the raw data which is used to drive all other reports. Thus the Payment Event Finder will bring back some monetary data which is not yet included in the accrual report – i.e. not yet reportable on the company’s books.
In other words, the Payment Event Finder is not subject to the accrual report’s filters, or those of other reports as the case may be. To override this, tick the various ☑ Hide items... checkboxes at the bottom of the block of filters.
In any event, all of AngelTrack’s reports are driven from the same SQL tables (payment events, etc.) and so they cannot differ in their results except according to their filters.
Explained here: Commission Reports
In short, the Payment Event Finder is not subject to the Billing Activity Visualizer’s filters, and the aforementioned help document explains why. To override this, tick the various ☑ Hide items... checkboxes at the bottom of the block of filters.
UnitedHealthCare updated their systems on 2019 September 1, and the new system checks whether the provider's taxonomy code is correct.
AngelTrack sends the correct taxonomy code for an EMS claim... provided it has not been incorrectly configured under the "Billing Configuration" tab under Settings. However, UHC will reject it if the provider is not correctly enrolled as an EMS provider.
Call the carrier and check the provider's enrollment.
It may also be necessary to switch the taxonomy qualifier from 'PT' to 'BI'; do this "Billing Configuration" tab under Settings.
See here: Air Medical Dispatching and Billing
AngelTrack integrates with NSure to offer one-click queries for elibility, demographic corrections, and insurance discovery. Refer to the NSure Guide to learn how to switch it on and make use of it.
On the Coding page there is an ☑ A0888 Unnecessary Mileage checkbox, and a field where you can input the number of miles that were unnecessary. When you then emit the claim, AngelTrack will include that quantity as an A0888 service line, and claim the remaining miles normally.
Yes, AngelTrack has a webservice by which anyone with 'Biller' or 'Administrator' credentials may download trips that have reached the billing office (i.e. trips that have passed QA), as well as move them forward and back in the postprocess workflow. The API requires you to know the name and password of an active 'Biller' or 'Administrator' account in AngelTrack; everything you do with the API will be logged as actions taken by that user.
The webservice is not publicized, so you must contact AngelTrack Support in order to make use of it.
AngelTrack's revenue reports are informed by payment events, not invoices. Invoices are simply a quick way to create large numbers of payment events: when an invoice is closed as "paid", the payment is applied to all items in the invoice, being recorded as a payment event for each.
Keep in mind, you always have the option of recording payment events by hand. And in fact that is exactly what you'll do when recording a cash payment, as would arrive at the billing office in an envelope filled out by the driver who collected it.
Remember you can add and remove calls piecemeal from an invoice, as you see fit.
In any case, invoices are removed from play by marking them "cancelled". (Remember, nothing is ever deleted in AngelTrack; data is marked 'deleted' or 'inactive', but never discarded.) You do so by clicking the "Close" link in the Invoices list, and then select "Cancelled" as the method of closure.
You can create and cancel as many invoices as you wish, even duplicates, forever protected from over- or under-billing. AngelTrack keeps track of what's payed and what's owed for each dispatch, and it does so totally independent of any invoices that include the dispatch.
It is impossible to lose a receivable, no matter what you do with your invoices.
In fact it is normal for a dispatch to be invoiced multiple times. Suppose you invoice a nursing home for 300 calls, and they only pay half. AngelTrack will use the payment to pay off and "finish" 150 calls, while the other 150 remain unpaid and go for another round of invoicing. They will keep popping up for re-invoicing until they are paid in full.
They will also pop up for re-invoicing if they are overpaid.
AngelTrack can download an invoice to you in PDF format, suitable for attaching to an email, or burning to a CD or thumbdrive.
You also have the option of having AngelTrack automatically email the PDF invoice for you at the moment you click the "Commit" button. For this, the patient's, affiliate's, or facility's email address must be on file. A checkbox will then appear just below the "Commit" button.
Simple, just pay (i.e. close) the invoice while specifying a payment received of zero dollars. AngelTrack will then apply all of the ledger balance as necessary.
Facility invoices include the calculation of what percentage of Medicare rates the customer is actually paying. This is done in order to qualify your EMS company for the Regulatory Discount Safe Harbor 42 C.F.R. § 1001.952(h). To learn more about the safe harbor and the Anti-Kickback Statute, and what AngelTrack does to protect you, read the Anti-Kickback Statute guide.
If the customer's effective prices are equal to or greater than Medicare rates for the respective service in the same ZIP code, then no calculation is shown, because the Anti-Kickback Statute does not apply.
Invoices for your patients and for your affiliates are not subject to the AKS or the safe harbor, and so do not include the calculated percentage.
From the Invoices list you can select multiple invoices for bulk printing. Right underneath the bulk print option is an option to print matching address labels, which will print right from your browser.
The address labels are sized and arranged for standard Avery 5160 labels, 30 per sheet.
AngelTrack can also export you the invoices' address data as a .CSV file for use in a mail merge, if you prefer to generate your address labels that way.
When you bulk print your invoices from your browser, the first page of each invoice will be automatically rotated to portrait mode, so that the TO: and FROM: addresses are correctly positioned for the envelope's window(s). The other pages of the invoice will print in landscape mode as usual.
This feature is not available if you export your invoices to .PDF and then print the .PDF from a reader program.
Visit the Settings page and click on the Business Information item. Select the "Online Resources" tab. Input the URL to a small (100ish x 100ish) logo image.
For invoicing purposes, AngelTrack must* load the logo image from a secure (https:) connection. If you do not have your logo image on a publicly-accessible webserver that offers secure (https:) connections, then email the URL to AngelTrack Support. We will retrieve the image, resize it if necessary, and then upload it right to your cloud server. AngelTrack's invoices will then include it from there.
*This requirement is not AngelTrack's: obviously there is no need to protect your logo image with a secure connection. This requirement exists so that your users' web browsers will not display an error message about loading content from an insecure (http:) source for display in the middle of a secure (https:) page -- i.e. in the middle of an invoice.
Your web browser is adding the URL to the top of each page as a page header, and the page numbers to the bottom as a page footer.
Look through your browser's "Print" menu, or "Print Options" or "Page Setup" or "Page Layout" menu, to find the header/footer settings. Remove any header and footer content, and then reprint.
Yes, AngelTrack will keep track of the number of times each receivable has been invoiced, so that you can be certain it is time to sell it to collections.
In the Invoices List, the number of times invoiced is displayed as one of the columns. The number represents the minimum number of times that any item in the invoice has been invoiced. For example, if an invoice contains one dispatch that was invoiced 3 times previously, plus another dispatch that was invoiced 5 times previously, then the number 3 will be displayed, because all of the receivables have been invoiced at least 3 times.
To increment the number, you must close the invoice as "Unpaid" after 30 days, then create a new invoice, and repeat. By closing an invoice as "Unpaid", the underlying receivables automatically return to "Billing office" where they will be picked up in the next round of invoices. So the whole process is easy to do; just be systematic about it, by doing it once a month every month until the numbers hit 3.
To learn more, read the Weekly/Monthly Reinvoicing Guide.
To learn more about selling receivables to collections, read the Taxes, Collections, and Writeoffs Guide.
Yes, use the "Compact Invoice" format.
Don't do it. The facility will be guilty of kickbacks if they offer to pay their patients' copays.
Make a single combined invoice as usual, then use "Print as singletons" to print it.
You can print it normally, at any time, regardless of whether it is marked "cancelled".
By default, the invoice generators only do the prior month. To include trips from the current month, you must change the cutoff date.
From the patient's record, choose the "Receivables" tab, then click one of the statement icons at the upper-right corner of the grid.
There are four places where late charges can be added to an invoice:
When closing an invoice, an overpayment can be placed on the ledger, but not an underpayment. This is because an underpayment leaves a balance due, and a balance due is best kept on the relevant dispatch, rather than paying off the dispatch and then throwing the balance due onto the ledger. (Ledger balances do not have the the rich tracking features that dispatches have.)
Note: If a ledger contains a credit balance, that credit will be automatically used to cover an underpayment.
Every PAN in AngelTrack must have a destination, as we know. If you obtain an PAN good for any destination, then upload it and choose the patient's residence as the destination. (You may need to create a facility record for the residence.) Once that's done, AngelTrack will match the patient's residence as the origin or destination of any transport, and apply the PAN appropriately.
The only situation where this workaround fails is a three-legged trip: home to dialysis to doctor to home. The trip from dialysis to doctor will not be tagged by the PAN assigned to the home. The PAN must be manually attached to that trip.
You can create a PAN document with no page scans, and just specify the prior authorization number in the "Comments" field. The document will then show up in all relevant run reports, displaying the contents of the "Comments" field.
In fact that is exactly what happens when a dispatcher records a prior authorization number during call-taking: a PAN document record is created, with no scanned attachment, and the authorization number is placed in the "Comments" field.
Later, when your biller is coding your claims, the authorization number from the "Comments" field will be automatically presented to the biller for inclusion in the insurance claim (loop 2300 REF*G101).
There is a preference setting you can choose, on the day your state gets included in the Medicare non-emergent PAN program. When the setting is enabled, AngelTrack will report all non-emergent stretcher calls for Medicare patients as needing both a PAN and an PCS, rather than just a PCS.
No, that would be giving legal advice for which we are not qualified.
Instead, we recommend you contact the law firm of Page, Wolfberg, and Wirth, and sign up for their training and consulting services.
Under Settings, in the Preferences item, you can set the "PCS Completion Mode" to ☑ Required. Read the aforementioned guide to learn more about the PCS settings.
You will then have to be patient with your crews, because sometimes they will be unable to obtain a PCS during a pickup, necessitating a return trip later on to get one signed.
AngelTrack is ready for that, with a built-in electronic certification form that it calls a McPAN.
Enable the McPAN form by visiting Preferences under Settings. AngelTrack will then automatically prompt the crews to get one when a patient hasd Medicaid insurance, and other reports and features will become available for you to track these forms and verify their coverage dates.
The PCS form will detach only when all of the following are true:
But even if the PCS did detach, it is not lost; it will be attached to the patient record, where it can be retrieved with the Librarian, screenshotted, and then re-attached to the trip as a separate document.
All uploaded documents are stored in your cloud server's independent SQL database, alongside all your other data. When a document is later retrieved, it is reconstructed on-the-fly from the data in the database. In this manner, your documents are backed-up as securely as everything else.
PDF is a complex document format that is not compatible with all web browsers. If AngelTrack were to embed a .PDF file inside one of your run reports, your browser may not be able to see what's inside it.
To solve this problem, AngelTrack extracts the images from each .PDF you upload. The images -- rather than the whole .PDF file -- are then embedded in AngelTrack's run reports, guaranteeing compatibility with all web browsers. Your run reports will therefore always display correctly, print correctly, and export correctly.
If a .PDF contains more than a single document scan per page, then AngelTrack will not attempt to extract the images, in case there are text-fields or electronic signatures that would not survive the extraction process. Instead, the .PDF document will be stored whole in AngelTrack.
All uploaded images are resized so that they fit within a 1536x1536 square. This is approximately 150dpi, halfway between "Normal" and "Fine" quality on a fax machine.
ECG scans, patient portraits, crew portraits, vehicle portraits, and vehicle damage photos are always stored in full color. All other document types are converted to greyscale unless the user specifically unticks the checkbox.
If your patient documents uploaded by crew members are not legible, then train them to be aware of light levels, camera angle, camera shake, and camera lens cleanliness. They will probably blame AngelTrack anyway, so the Documents Guide gives proof that AngelTrack's image conversion and greyscaling is not at fault in these situations.
Some tablet and smartphones have low-resolution cameras that aren't up to the task of document photography. Figure out which tablet or smartphone took the picture of the illegible document, and find the original photo in the device's photo album. You will probably discover that the original photo was illegible even before AngelTrack converted it for storage.
It may be necessary to disable the cameras on your older tablets, and instruct crews to use their newer smartphones for document photography.
There are now image-born computer viruses in the wild. An employee could accidentally or knowingly upload one to AngelTrack, in order to attack the billing computers in your back office when they view the run report. By forcibly re-encoding all incoming images, and discarding their .PDF wrappers, AngelTrack protects you from that attack vector.
iOS devices will often store photographs sideways or upside-down, temporarily auto-rotating them for viewing on the device. When these photographs are uploaded, AngelTrack doesn't know they are natively sideways or upside-down, and so it displays them incorrectly.
To correct this, the crew member should check their documents after upload, and rotate the pages as necessary by clicking the ↶ Rotate , ↷ Rotate , and ⇅ Flip buttons which appear in the bottom corners of each page. Billers and dispatchers also have the ability to rotate documents, because the same rotation buttons appear in the document viewer they use to review patient documents.
If all of that is too much of a hassle, then as an alternative try installing a third-party photography app on the mobile devices -- something which gives finer control of the device's photographic features.
The .PDF documents produced by eFax.com use a .PDF trick to vertically re-flip the page images:
/Page q 609.8824 0 0 -776.5714 0 776.5714 cm
This is non-standard and so all eFax.com images extracted by AngelTrack will appear in their native format -- which is vertically flipped.
After uploading such images, you must click the "Page(s)" link to view the document in AngelTrack, and then use AngelTrack's ⇅ Flip button to vertically flip each page image.
JPEG 2000 is an image file format, similar to JPEG and GIF. Certain document scanners use the JPEG 2000 format to encode the images inside the .PDFs they generate for you.
Unfortunately the format is patent-encumbered, and AngelTrack does not support it. Instead, AngelTrack supports the regular JPEG format, as well as PNG, GIF, BMP, SVG, and TIFF.
To switch from JPEG 2000 back to regular JPEG, you may simply need to update your scanner's driver software, or update the software in its PC control panel. If that fails, look inside the scanner's settings to see if it offers a choice of image encoding. Choose regular JPEG instead, or PNG.
You are also free to ignore AngelTrack's warning, and upload the .PDF to AngelTrack anyway. AngelTrack will not be able to extract any images from it, and so instead will store the .PDF whole. It can be retrieved later, but its contents cannot automatically appear inside AngelTrack's run reports, the way that all other documents do.
This is a special rule that applies only to the "Insurance cards" document type. If a .PDF is uploaded containing multiple page scans, only the first large image is accepted.
Remember that the patient's latest "Insurance cards" document is displayed in many places throughout AngelTrack's billing system. This rule exists to prevent a large multi-page scan of insurance cards from overwhelming the web pages where such is displayed.
If the browser on your mobile device will allow you to upload a picture from your camera roll but not a live picture from the camera, then check the mobile device's settings for its browser (Safari or Chrome) to verify that the browser is allowed to access the camera.
All employees can view:
In addition, if an incident is used as a writeup, and a blamed employee is asked to sign the writeup, then the blamed employee will be shown the incident's summary, its cause, all of its contents, and all of its attachments.
Captains and HR can view any incident, open or closed, assigned or unassigned, EXCEPT incidents marked "Lock out captains and HR". Locked incidents can be viewed only by the assigned employee and by the AngelTrack administrator.
In the HR section of AngelTrack's online help you will find the Disciplinary Writeup Guide for doing exactly this.
Simply configure your email address on file in AngelTrack, using your "Employee Edit" page. To access that page, click your initials in the upper-right hand corner of any AngelTrack page.
You may need to tick the adjoining checkbox, in order to opt-in to incident notices (in addition to AngelTrack's other notices). Once opted in, you will also be notified if somebody else makes a change to an incident assigned to you.
Visit your Employee Self-Edit page by clicking your initials in the upper-right corner of any AngelTrack page, and switch your messaging address type from email to SMS, and provide your mobile number.
By default the timeclock is unrestricted. You just need to configure its restrictions.
In the "Timeclock Hosts" page under "Settings", you need to disable the two entries named "All IPv4 addresses" and "All IPv6 addresses". Then create entries for each of your stations or other allowed clock-in/clock-out locations (e.g. remote offices).
The "Timeclock Hosts" page displays your current IP address and pre-creates an entry for allowing clock-in/clock-out from that network; to use it, just name the entry and click "Add". In this manner, you can visit the "Timeclock Hosts" page from each of your stations, adding them one by one.
No, a dynamic IP address is fine.
When specifying a dynamic IP address as an allowed clock-in locations, give only the first two octets. For example, if your dynamic IP address is 188.8.131.52, probably the 133.87 remains constant while the 244.190 changes regularly. Next week it might be 184.108.40.206, or whatever. So tell AngelTrack that only the 133.87 part matters. Specify it like this: "133.87/16". The "/16" part says "Only consider the first sixteen bits", which is the 133 (8 bits) and the 87 (8 bits).
No problem; AngelTrack talks IPv4 and IPv6, and the timeclock's restriction system likewise supports both.
Even if you configure AngelTrack to prevent clockout when there are unfinished reports and unfinished checklists, an employee may be manually clocked-out by a member of any of these roles:
When a manual clockout occurs, the timeclock log entry will be automatically flagged "Needs attention". Only a member of the "Human Resources" role can clear this flag.
The employee who was clocked-out will receive a notification message to that effect, if they have so configured their messaging settings.
When a member of the aforementioned roles clocks out themself, the timecard will display "self (manual)" as the person who performed the clockout. This indicates that AngelTrack's normal clockout checks -- for unfinished reports and checklists -- were bypassed.
Another way that crews can clockout despite unfinished checklists is if their dispatcher is ending their shift despite AngelTrack's warning (on the Shift End page) that the crew still has work to do.
There is an employee privilege you can check off, to allow specific employees to clock in no matter where they are. Use the "Privileges" tab on the "Employee Edit" page to set it.
"Shift Length" is the amount of time between clock-in and clock-out... even if the time interval crosses into the next pay-period.
"Hours in Period", by contrast, is the amount of time that falls within the selected pay period. Therefore, if an employee is on the clock during a pay-period boundary, then their "Hours in Period" will be less than their "Shift Length".
Your station's internet service provider changed your IP address. The new IP address is not in AngelTrack's list of company facilities.
You can add the new IP address, or better yet the new range of IP addressses, to AngelTrack's list of company facilities. Visit the Timeclock Hosts page under Settings to do so; you must be an administrator or a member of HR. To learn more, read the Timeclock Hosts Guide.
If your ISP keeps changing your IP address over wildly different ranges, causing this problem to recur, then consider giving them a few bucks for a "static IP address" that is guaranteed to never change.
Nobody can alter a timecard in AngelTrack without leaving a journal. Every employee can view these journals for their own timecard. The journals are tamper-proof and stored for seven years.
Any time you see the journal icon next to an entry in your timecard, just click it to read the journal. It will show what change was made, when, and by whom.
If you see the lock icon next to an entry in your timecard, it means that HR has locked it in order to do payroll. Once locked, nobody can alter the timecard for any reason.
Yes, configure this by visiting Preferences under Settings.
Use the timeclock's on-call system. It must be enabled in the Preferences under Settings.
Crews will be able to set themselves on-call (i.e. on break) when they are at a company facility (or from anywhere if the timeclock is unrestricted), and dispatchers will be able to mark whole shifts on-call or on-duty from the Shifts page. If a dispatcher assigns a call to a crew that is on break, AngelTrack will then automatically switch them back on-duty.
It will, but only if you are using the shift scheduler to allocate your crews and vehicles. That is the only way that AngelTrack can know that a crew member has clocked-in later than he or she was expected.
Under HR Home, the Labor Hours Visualizer shows you the number of hours recorded on the time-clock, organized by employee patch level, and filterable by date range and zone.
The time-clock is the only accurate way to capture this information. Attempting a similar analysis using shift data gives inaccurate results, because crew members can be in two shifts at once, or in no shift at all but still working at the station, or be recorded as participating in a shift but not yet clocked-in.
The related report Labor Cost Visualizer shows you the same data, but also accounts for the costs of overtime and on-call.
Hourly employees are shown announcements only AFTER they clock in, so as to avoid complaints about having to read announcements while off the clock.
Also, if an employee clocks in and already has a dispatch assigned, announcements will wait until after the dispatch is completed.
On the Crew Home page, there is a "Review Announcements" link that opens a list of all announcements targeted at the employee. Supervisors and other back-office employees can click the "Announcements" link available on both the Supervision home page and the HR home page.
If you wish to forcibly re-show an announcement to all targeted employees, then simply open it in the Announcement Edit page and re-save it.
Remember, if you modify an announcement, it will be automatically re-shown to all targeted employees.
Until a crew member is designated as the attending, all crew members onboard the vehicle are liable for completing the report.
AngelTrack automatically sets the attending to be the first crew member who opens the PCR. So, if nobody has opened the PCR, then the attending is not set, and everyone in the truck is liable.
If a shift contains only a single crew member, then that crew member is automatically marked as the attending for all calls assigned to the shift.
When a dispatch is assigned to a shift, any crew member included in the shift can make themself the attending, by visiting the Followup page and clicking the Make Me the Attending button.
Any lieutenant included in the shift, and any captain (even one not on board), can use the Followup page to select any crew member as the attending.
QA reviewers can alter the attending during the QA review process, in order to fail the report back to a different crew member.
Dispatchers and Billers can alter the attending at any time, using the Followup page.
Under the Settings page select "Document Templates". Edit the template named PCRNarrative.txt. You can rearrange or remove any sections (enroute, onscene, transporting, destination) you wish. You can also add other variables (like [BUSINESS_NAME] or [BUSINESS_STATE_LICENSE_NUMBER] to name a few), additional text, and/or formatting marks to be included in all composed narratives.
To block an individual employee from using it, visit the Employee Edit page and select the "Privileges" tab. Uncheck the "Use the Narrative Composer" box and then save.
To block everyone from using it, visit the Settings page and select "Document Templates". Edit the template named PCRNarrative.txt. Delete any sections (enroute, onscene, transporting, destination) that you will not allow the Narrative Composer to write.
When blocking everyone from using AutoCompose, it's a good idea to let them AutoCompose the enroute section of the narrative. That section contains nothing but dry facts such as date, time, crew names, crew patch levels, vehicle name, origin name, and so forth. It virtually never contains medical content, so AutoComposing it will save your crews a lot of repetitive typing.
AutoCompose randomly chooses different expressions and word order each time it runs. If you closely compare several different AutoCompose narratives for the same dispatch, you will see that the same pertinent information is always included, despite the randomization of phrasing.
When multiple browser tabs were opened to the same narrative, the autosaves could conflict with each other; a long narrative in one browser tab could be overwritten by a stray keystroke in the same narrative in a different tab, or on a different device.
This resulted in phone calls to the support line, accusing AngelTrack of deleting peoples' narratives, so we had to remove the feature.
A dark yellow button in the PCR is an advisory: the information is probably needed, but AngelTrack is not certain that the information is needed, so the crew is not required to input it. They can send their report to QA while dark yellow buttons are still showing.
The PCS button lights up when a PCS is needed (a Medicare patient traveling non-emergent) and not yet on file. It turns bright yellow if your "PCS Completion" preference setting is "Required", versus dark yellow if your setting is "Advisory" or "Strict". Read the PCS Requirements guide to learn more about these settings, and for advice on selecting one.
Crews are not permitted to edit their leg times when the dispatch is still open. Once it closes, editing is permitted.
This restriction exists to prevent the crew from making an edit that could confuse the dispatchers. For example, suppose the crew has been transporting for 40 minutes, and the dispatchers are monitoring the board as usual. Suppose the attending decides to edit the leg times, and makes a mistake. Suddenly the dispatch board changes to "transporting for 2 minutes", and the dispatcher is left questioning her sanity.
The reperfusion checklist is a popover shown by the PCR's "Meds" page.
When the crew selects any medication that is marked as a thrombolytic, a warning icon is displayed, along with a link to pop up the checklist. The answers to the checklist will be saved in the PCR, and will thereafter appear in the run report.
AngelTrack's built-in medication list already has its thrombolytics appropriately marked. If you add a new medication to the list, you can mark it yourself as a thrombolytic.
Go to the PCR Meds page, run the checklist, and then click the Save button. It is not necessary to save the medication record.
AngelTrack provides a interactive versions of the the Los Angeles Prehospital Stroke Screen (L.A.P.S.S.), the Rapid Arterial oCclusion Evaluation (R.A.C.E.) screen, and the Cincinnati screen. The interactive features reduce the amount of cognitive processing needed to complete the screen; remember, these screens are usually performed in a terrible hurry.
The stroke screen is a popover shown by the PCR's "Assessment" page. The screen can be activated manually; it will activate automatically if the crew member enters certain exam findings that are correllated with stroke.
L.A.P.S.S. is the default. To switch the PCR to a different stroke screen, visit Preferences under Settings.
No. The black background protects the crews' night vision.
They are huge so that they are easy for a driver to press on a small smartphone screen.
Remember, the driver is usually accessing AngelTrack from a personal smartphone because the tablet is in back with their partner.
Yes, the list is right here: List of Fields in AngelTrack's PCR (.xlsx)
Bear in mind: AngelTrack is NEMSIS v3 certified, which means it supports everything in the national standard for PCR fields. The list is enormous and frankly excessive for most situations, because it is meant to capture all possible EMS situations.
AngelTrack also has custom PCR fields, allowing you to add an unlimited number of new datafields, and to choose when the crew must answer them.
If the PCR's Patient, Billing, PMHx, and History tabs are not automatically populating with data that was previously collected for the patient, it is probably because there are duplicate patient records in the system: record A was populated, but record B is attached to the dispatch and is not populated yet.
To learn where duplicate patient records come from, and how to merge them away, read the Duplicate Patient Records Guide.
AngelTrack's design philosophy says: if the PCR demands an answer in a datafield, crew members will be forced to lie, because ambulances are hectic places and there isn't always time to collect all data.
This is why datafields in AngelTrack's PCR always have a "[Not recorded]" option. It is the crew's responsibility to collect and input data as best they can, and it is the responsibility of the QA reviewer to approve of missing data on a case-by-case basis.
In other words, missing PCR data is a disciplinary issue, not a technological issue. To that end, AngelTrack gathers statistics on how completely each crew member fills out their PCRs, and these statistics can be viewed as graphs showing each crew member's completeness over time. The graphs provide the quantitative data needed to hold crew members accountable, and to measure their improvement over time.
On a related note, you can add custom PCR fields to the system, and designate them as mandatory under certain circumstances.
The Safari browser does that. You must configure it to always allow AngelTrack to request the device's location. Do this by clicking the "aA" icon at the top-left corner, selecting "Website Settings", and changing the "Location" setting to "Allow".
If Safari does not have the "aA" option, then your device is running an older version of Safari. If it is no longer possible to update it to the latest iOS, then switch to Chrome as your browser. It will ask a couple of times, and thereafter remember and so stop asking.
Yes, under Settings... but note that your state may not allow certain codes. Your state may have posted their list of acceptable codes, on the NEMSIS website.
You can also edit AngelTrack's origin types list (eScene.09), in case your state rejects the NEMSIS standard list.
Yes, under two circumstances: They can do so when AngelTrack is in unattended mode, and they can do so when they belong to the call-taker role and have assigned the call to themselves.
When thus allowed, the crew can choose a destination using the Hospital ER List page, available from the Run Call page and able to be kept always open in a separate browser tab.
For this feature to work right, your facility list must be in good order, with all local hospitals recorded, with their facility type set to ER and their GPS coordinates stored.
If using a ToughBook, make sure to use the stylus.
If that isn't the problem, then read the Touchscreen Signature Problems guide.
Go to Document Templates under Settings and input your custom verbiage in the "UserConfigurableOtherSignature" template 1 or 2. It will then appear in the PCR.
If you collected a signature for the wrong trip, and so need to move it to a different one, do this:
Our WYSIWYG HTML editor is accidentally triggering your popup blocker. You must disable it when visiting AngelTrack.
You may also see this error on AngelTrack's announcement editor, which likewise uses the WYSIWYG HTML editor.
Indeed, the PCR's document storage system keeps images at 1536x1536, which is approximately 150 dpi, and in black and white, because it is intended for medical document storage. It is unsuitable for evidentiary photographs taken of an injury scene where you anticipate a lawsuit against EMS.
In this situation, crews should attach an incident record to the trip, and upload the evidence to the incident instead of to the PCR. Incidents can store any document types and have no limit on image resolution.
When viewed by a QA reviewer using the links on the QA Review form, a run report shows all possible data fields regardless of whether or not they contain information. This is done so that QA is aware of what information was NOT provided by the crew and by the dispatcher.
At all other times, run reports omit data fields if they contain no information, except for the following fields which are always shown even if empty:
You need a fax-over-internet app installed on your mobile device. There are dozens available, and most of them are quite cheap. We've tested both RingCentral (a full-featured VoIP solution) and MetroFax (a low-cost fax-over-internet solution) and had good results.
Once the app is on your device, open the "Print" popover and choose one of the PDF options. AngelTrack will download the entire run report -- including signatures and documents -- in a single .PDF file. Your mobile device will then offer you a choice of applications to handle the .PDF. The fax application should be one of those choices.
Rather than faxing, it would probably be easier to simply email the report to them. Ask them for their email address and then relay it to your dispatcher to save into the facility's or patient's record in AngelTrack. Once that's done, the PCR will (in its "Email" feature) offer to email the PDF to that email address.
First, consider using the "Compact" format, available from several different grids available to dispatchers and billers. This format will remove the pagebreaks that are normally inserted between report sections. The pagebreaks improve readability, but obviously make the report consume about twice as much paper.
Second, when printing, use the "Print Options" or "Page Setup" feature to choose four pages per sheet, rather than full size. Some web browsers amd most .PDF readers (such as Acrobat and Nitro) have this capability. Your printer may also offer this option via its printer driver -- meaning the option will be somewhere in the "Printer Setup" menu. The printout will be smaller but, provided your printer is capable of 600dpi, will be perfectly legible and ideally suited for archival purposes. However you won't be able to fax it out, because fax machines are only capable of 100dpi / 200dpi (fine) / 400dpi (superfine).
AngelTrack can download your complete run reports as .PDFs, zipped up for you in batches of 100. Download the zipped batches using the Closed Dispatches grid, burn them to CD, and squirrel the CD away someplace safe.
The run reports contain all dispatch and PCR data, all attached documents, all electronic signatures, and all other attachments such as ECG strips and diagnostic images. They are fully self-contained .PDFs that use no special features, and so they are viewable and printable using any .PDF reader.
It is the QA reviewer's responsibility to determine the actual service level provided, which obviously can differ greatly from the service level requested. Once that determination is made, all of AngelTrack's postprocess workflow treats the dispatch as the level provided rather than the level requested.
QA reviewers can upgrade or downgrade calls as they see fit.
AngelTrack will estimate what service level was provided by examining the PCR records created by the crew, and also the patch levels held by the crew members. This estimate is displayed on the QA Review page as an underline on the appropriate radiobutton. If the QA reviewer chooses a service level other than the one underlined, they should be able to explain why... and should do so in the Billing Notes field.
To learn more about the QA review process, read the QA Review Process Guide.
One of the things AngelTrack considers in estimating the service provided, is the patch levels of all crew members who were aboard the vehicle. If some of the crew members have forgotten to record their certificates in AngelTrack, then AngelTrack does not know that they have patches. As a result it will conclude that only wheelchair service was provided.
Also remember: AngelTrack checks the crew's certificates that were in force on the date of service. It may be necessary for crew members to appropriately backdate their certificate records in AngelTrack, so that they will show up on the date they ran the call. To learn more about certificate tracking in AngelTrack, read the Certificate Tracking Guide.
Use the Medical Director Review Queue, under Supervisor Home, to accomplish that. Your medical director must be granted a login to AngelTrack, and must be tagged in the "Medical director" role.
To learn more, refer to the Medical Director Review Queue Guide.
Your state trauma registry must have a NEMSIS v3.4.0, v3.3.4, or v3.5.0 compatible webservice up and running.
They will issue you a username, a password, and an agency number. Give this information to AngelTrack Support, and they will configure and test your data uploads to your state. Or you can configure the uploads yourself, by visiting the State Upload Status item under Settings. To learn more, read the State Trauma Registry Uploads Guide.
Go here and click your state to see contact information for your trauma registry: NEMSIS 3 State Map
AngelTrack LLC cannot do this for you; they will issue credentials only to providers, who must then relay them to AngelTrack.
All state trauma registries should publish their lists of public health facilities. The list contains each facility's name, address, and its state-assigned ID number. The latter will be included in the NEMSIS uploads which AngelTrack sends up to the trauma registry.
Your state probably has its facility list posted on the NEMSIS website; AngelTrack's facility list importer can retrieve it directly from there. If not, then your state should offer the list as a Microsoft Excel™ spreadsheet, either posted on the NEMSIS website as an auxiliary link, or on the State Health Department website for EMS. AngelTrack can import a facility list as a .CSV, so use Excel to "Save as..." a .CSV, and then import it into AngelTrack using the Facilities List importer. To learn more about the importer, read the Facilities List Importer Guide.
First, verify that the trip is reportable, by opening the Dispatch Edit page, switching to the "Billing" tab, and checking the trauma registry field.
If it is indeed reportable, then go to the Followup, make no changes, and click "Save". Return to the "Billing" tab and you will see that the trip is now marked for re-validation and (afterward) re-upload.
Visit the State Upload Status page (under Settings) and click one of the "Force a revalidation and reupload" buttons -- whichever one corresponds to the date range you require.
You don't have to do anything; AngelTrack retrieves updated schematrons from all states, and applies them during its weekly maintenance windows.
Go to Settings and click the NEMSIS icon to access AngelTrack's State Upload Status page. Find your upload credential and edit it. Use the dropdown to pick which software the state is switching to, and also update your upload username and password.
While you're there, double-check which NEMSIS version the state wishes to receive (most are on v3.4.0).
A trip is emergent if any of the following are true:
This is how AngelTrack implements the CMS regulation which states:
An emergency response is one that, at the time you are called, you respond immediately. A BLS emergency is an immediate emergency response in which you begin as quickly as possible to take the steps necessary to respond to the call.
Visit your cloud server and manually type this URL:
That will load the Terms of Service document that you originally signed when deploying AngelTrack. The necessary HIPAA covenants are in the "HIPAA Assurances" section. Your captured electronic signature will be reproduced at the bottom. You can print out the page and show it to the auditor.
If the auditor requires an authorized signature from AngelTrack LLC also, call AngelTrack support and we will fax one to you.
AngelTrack has a special "Onlooker" security role for this purpose.
You must issue an employee account to your regulator, and add that account to the "Onlooker" role. It needs no other permissions. Your regulator will then login to your AngelTrack cloud server just like an employee... but they will only be able to view a special read-only dispatch board and a read-only live map, showing only those dispatches which are both active and assigned.
HIPAA is sometimes misinterpreted as "no sharing of patient data." For the counterargument, refer to this legal opinion: HIPAA: An Imaginary Barrier to Data Exchange.pdf
AngelTrack continuously updates the odometer reading of all of your vehicles, for use by the fleet maintenance features as well as the fuel tracking features. It does so using the stream of odometer readings submitted by crews as they run calls, purchase fuel, and call in shift start/shift end.
If your vehicles' odometer readings are not automatically updating, then one or more of the following is occurring:
To see which crew members are submitting full proper odometer readings in their calls, versus which are not, open each employee file, switch to the "Statistics" tab, and look for the "Dispatches with bogus odometer readings" metric.
The Fuel Usage Analysis report, under Supervisor home, shows fuel burn rates. This help document explains the various problems that can be identified from the analysis, including examples.
The Vehicle Total Costs report also shows fuel usage, along with other vehicle costs, broken down per mile and per dispatch.
After you meet with your integrator and agree on a deployment schedule, your AngelTrack cloud server will be activated. You can access it, explore the features, and begin configuring your operation. You do not need to pay for a license until you are ready to start booking calls.
Licenses are purchased right inside the product, using Paypal. You can pay with a credit card, or with a paypal balance, or with a direct draft from a linked bank account.
You can also opt in to an automatic subscription -- monthly or annually -- so that you don't have to remember to pay again.
Only for EMS companies operating in Missouri.
Your AngelTrack cloud server already knows your headquarters address and so will add the appropriate sales tax to your license purchase and to your recurring subscription (if any).
When all licenses are exhausted, your AngelTrack cloud server enters the "cooldown period".
During the cooldown period, all features continue to work with just one exception: no new dispatches can be created.
You can still run any dispatches that were already scheduled.
These terms are laid out in the Terms of Service that you will sign when activating your AngelTrack cloud server.
If you do not intend to renew your AngelTrack license, then use the cooldown period to export all data you wish to keep. The cooldown period lasts 30 days. At the end of the cooldown period, your cloud server will be deactivated, and all data and all backups will be permanently destroyed.
As your business grows, you will eventually exceed your current license's call volume limit. The call volume limits for all license sizes are shown on the main website.
When your call volume exceeds your current licenses's limit for two months in a row, we will notify you of a license review. After the third month over the limit, your cloud server will be upgraded as necessary, and all license days remaining will be prorated at the larger license price.
For example, suppose you land a new contract, and proceed to blow the top off your Bronze license. After two months of that, we will notify you of a pending license upgrade. After the third month, you will be upgraded. If you had 90 days of Bronze remaining at that time, then you will have 45 days of Silver remaining after the upgrade.
The same is true in reverse: if your business subdivides or contracts such that you now fit within a smaller license class, we will downgrade your license and prorate all days remaining.
If you wish to lock in today's prices against the possibility that AngelTrack prices will go up, do so by purchasing licenses in advance.
Create your 60-day guarantee by purchasing three months' of licenses up front, giving you 90 days in your license. Then begin a month-to-month subscription. At the end of 30 days, when you have 60 days remaining on your license, your subscription will automatically purchase another 30 days. That will refill your guarantee back to 90 days, so that it always has at least 60 days in it.
Whenever you purchase a license, you are locking that days's prices through any future pro-rate. That means your pro-rate will be calculated using the prices as they were at the time of purchase.
If AngelTrack's prices have since gone down, the pro-rate we will be calculated using whichever prices (original or current) are more favorable to you.
This is one of the benefits of purchasing annual licenses rather than monthly: you lock in the prices for an entire year -- not only the price of your current license size, but also the price of the larger license you will eventually need.
We hope all AngelTrack customers need a pro-rate, because that means business is booming and you are growing. :)
Our secure datacenters, plus our obsession with uptime, guarantees that your AngelTrack service is reliable, fast, and bulletproof. As your employees come and go, they will remember their experience with AngelTrack. We do not want that experience to be tainted by the problems of a non-professional datacenter, because we want them to ask for AngelTrack at their next employer.
Your reseller cannot access your cloud server unless you issue them an account. You would do that if they were also your biller. You might also do that if you call them for support and ask them to take a look at something for you; afterward, you can disable the account again.
The issue is more fully explored in this help document: Reseller Access to Your Cloud Server.
Just ask, and we will promptly reassign you -- just as soon as your desired reseller consents.
You may apply to become an AngelTrack reseller after you meet the following requirements:
Visit the "Diagnostics" page under "Settings" to check the data/time that your data was last backed up.
Backups are stored off-server, in a private data storage cloud.
All of your data has export facilities built right in to AngelTrack's pages. Look for the export icon at the top-right corner of any data grid. Meanwhile, full run reports can be downloaded at any time as .PDFs or as NEMSIS 3 XMLs, including all signatures and attached documents. AngelTrack also has programmatic export options for serving data directly to other software applications.
To learn more, read the Data Lifetime and Export Guide.
Most data is retained for seven years. Some less-important data is discarded earlier. Refer to the Data Lifetime and Export Guide to learn more.
The Heartbeat page under Settings shows the last two minutes of client requests, and who made them.
Remember, with web browsers there is no such thing as a "connection"; there is simply request/reply, request/reply, request/reply. So the only thing your AngelTrack cloud server can show you, is the list of recent requests and who made them.
Every employee's HR record also shows the last date/time they attempted to login, and the last date/time they successfully did so.
Administrators and HR can access the logs from the "Support" page. There is a separate logfile for each day of operation. Every single web request is logged, including the date, time, username, IP address, browser, and requested page. To learn more, read the Data Leak Forensics Guide
When reviewing the logs, remember that the timestamps are in GMT, so you must subtract several hours to convert the timestamps to your local time.
The Customer Portal will accept any access code, and it will show the departures and arrivals boards as usual... however, they won't contain any data unless the access code is correct.
This prevents a password-guessing attack: since there is no way to tell whether an access code is wrong, there is no way to decide when you've guessed right. Incidentally, the Beacon app's tokens use the same principle: anyone can upload a position report for any token, but only AngelTrack knows which tokens are valid.
To learn more about the Customer Portal, read the Customer Portal Guide.
If your suspicions are grave, then do either of these things:
Next, read the Data Breach Forensics Guide.
We greatly desire feature requests from customers, because that lets us know where you are struggling. Every feature request represents a new opportunity for the product to become even more useful and valuable.
Because we hear so many feature requests, we organize them in a master list, which then drives the choice of what will be implemented in each new release.
Items on the list will move to the top -- and therefore be implemented straightaway -- under these circumstances:
Most feature requests are "Wouldn't it be nice if...", and therefore go to the bottom of the list until other customers come to ask for the same thing.
The HR-side Employee Edit page can generate random passwords but not set something specific, because after it saves, the employee must then choose a new password known only to them.
To change your own password to something specific, don't use the HR-side employee editor. Instead, click your initials at the upper-right corner of the page, which will open the Employee Self-Edit page.