Skip to content
English
Sign in
Go to angeltrack.com
  • There are no suggestions because the search field is empty.

State Upload FAQ and Troubleshooting

Frequently asked questions, and troubleshooting advice, for your EMS state trauma registry uploader

Before using this FAQ, please read the State Upload Guide first, as it contains all the basic knowledge for configuring and troubleshooting a state uploader.

Status code -14 "Schematron validation found an error" during DEM upload, with an error message that Agency Name (dAgency.03) does not match the expected value.

This error occurs in states which enforce an exact match between the agency's reported name ("Acme EMS Transport") and the name registered with the state trauma registry ("Acme EMS Transportation").

You can fix it by doing either of these:

  • Change your agency's reported name to match that expected by state, by visiting your Agency Information page under Settings; or

  • Modify the affected state upload credential to specify an override name, matching the one on file at the trauma registry.

Error -3 "Permission denied to this EMS organization"

If AngelTrack's state uploader issues this error code, then contact the trauma registry and double-check that all credential fields in AngelTrack match their expectations. See above for the list of credential fields that must match exactly.

If everything is correct but you still get a -3 permission error, and if the trauma registry is ImageTrend, then you may be seeing a side-effect of a missing DEM permission. Some states do not allow providers to submit DEM data, which is fine, but inside ImageTrend an EMS upload can sometimes issue a supplemental DEM update. (We conjecture that ImageTrend is copying some data from the EMS submission in order to flesh out the DEM data already on file for the provider.) If the provider's account in ImageTrend is marked "no DEM updates allowed", then this supplemental DEM update will fail with a permission error, causing the entire EMS upload to fail with error -3.

To work around this problem, the state must temporarily mark the provider's account as "allow DEM update". Then wait for AngelTrack to successfully upload at least one EMS record. Afterward the state can revoke the permission again.

What are these "Texas Statewide" credentials?

For Texas providers, Texas EMSTR has provisioned some statewide credentials for all providers on AngelTrack. Using one of these statewide credentials will spare you the quarterly hassle of issuing and maintaining an EMSTR webservice credential for your agency.

To make use of an AngelTrack statewide credential, you must perform these steps:

  1. Register your agency with EMSTR.

  2. Establish your agency's IAmOnline credential, and login to the EMSTR portal.

  3. Within the EMSTR portal, sign the Acceptable Use Agreement.

  4. If your AngelTrack server is prompting you to ask your principal employee to sign the latest AngelTrack TOS, then take care of that.

  5. Notify your AngelTrack Support representative that you are provisioned in EMSTR and wish to use an AngelTrack statewide upload credential for your uploads.

These steps are all mandatory. The AngelTrack statewide upload credentials will not work for your agency until all steps are performed.

After you notify us of your request, we will contact EMSTR, and attach your agency to one of AngelTrack's statewide credentials. You will be attached to only one of them, you cannot use the other ones.

How do I set up an upload credential for a county-level registry?

Please visit the Regional Uploads Guide.

Why would AngelTrack say a dispatch is "not a reportable call"?

A dispatch is not reportable if ANY of the following are true:

  • The activation date is more than 730 days (2 years) ago;

  • The jurisdiction state is outside of USA;

  • The call is cancelled, or was delegated to an affiliate;

  • The call is not assigned to a shift;

  • The call's service level provided is configured as "not reportable" in AngelTrack's service level configuration; or

  • The call is not a consummated BLS+ transport and AngelTrack's "NEMSIS criteria" preference setting is set to "Send only BLS+ reports where transport occurred".

Why is the destination hospital saying they aren't receiving our trip data?

If your state runs a hospital bridge to automatically forward your crew's charts to each receiving hospital, the following problems might cause it to fail:

  • AngelTrack might be configured to not upload a chart until after it graduates QA. You can change this behavior by visiting the Preferences page, under Settings.

  • Your state uploader might be paused due to a credential error. You can visit your State Upload Configuration page, under Settings, to check it.

  • Your state upload credential might have a county or city jurisdiction setting that excludes the hospital in question, and so trips bound for that hospital might have no matching credential by which to be uploaded. You can check the state upload status of any trip by opening its run ticket and visiting the Billing tab. You can also review all state upload attempts by looking at the ticket's Journal tab.

  • The charts might have the wrong facility record attached as the destination, causing them to go to the wrong institution.

  • The facility record attached as the destination might have the wrong state code, or no state code, causing the state's back-end system to be unsure where to forward them.

  • AngelTrack's service levels configuration might be set up to consider certain services to be non-reportable.

  • Your crews might be taking too long to finish their charts and submit them to QA, causing the state's back-end system to give up.

(This advice does not apply to the Kno2 integration, which pushes data to hospitals via a completely different route.)