---
title: Split State Uploads / RAC / Regional Uploads
description: If you must upload PCR data to a regional registry in addition to your county or state registry, AngelTrack can do it automatically.
---

[Skip to content](https://support.angeltrack.com/help/regionaluploads.htm#main-content)

English

Show submenu for translations

![A.400x400.png\]](https://support.angeltrack.com/hs-fs/hubfs/A.400x400.png?height=40&name=A.400x400.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- Go to angeltrack.com

 Go to angeltrack.com

 AngelTrack Knowledge Base

- There are no suggestions because the search field is empty.

1. [AngelTrack Knowledge Base](https://support.angeltrack.com/help?hsLang=en)
2. [Supervisors](https://support.angeltrack.com/help/supervisors?hsLang=en)
3. [Compliance](https://support.angeltrack.com/help/supervisors?hsLang=en#compliance)

# Split State Uploads / RAC / Regional Uploads

## If you must upload PCR data to a regional registry in addition to your county or state registry, AngelTrack can do it automatically.

AngelTrack can handle all of our data reporting and upload requirements to counties, regions, cities, RACs, and hospitals.

### Regional Non-Forwarding Registries

A **non-forwarding registry** is a receiver of NEMSIS or NFIRS data who does *not* forward it to the state in a manner fulfilling your normal obligations. An example of this is a RAC registry in Texas. Anything you upload to a non-forwarding registry must *also* be uploaded separately to your county or state.

Whereas a **forwarding registry**, such as a county in California, forwards all data to the state, such that any upload to the county will *also* satisfy your state reporting requirements.

AngelTrack can automatically manage the upload of each trip's data to:

- One state or state-forwarding registry; and
- As many non-state/non-forwarding registries and other endpoints as you require.

Exactly which registry each dispatch goes to, depends on its service level, jurisdiction state, jurisdiction county, and origin city, according to the criteria you specify in your outflow credentials.

Typically you will have a statewide credential plus maybe a regional non-forwarding credential, but you could also have per-county credentials that forward to (or go directly to) the state. To learn more about this, please visit the [Outflows Guide](https://support.angeltrack.com/help/outflows.htm?hsLang=en).

### Designation of Non-Forwarding Registry

Each of your outflow credentials has a flag indicating whether it satisfies your county/state upload requirement.

A credential for your state, or for a county who forwards to your state, which therefore satisfies the upload requirement, should be marked **☑ This is the main state registry, or it auto-forwards my data to it**.

Whereas a credential for a regional non-forwarding registry should not be so marked.

Once you arrange your outflow credentials and their marks correctly, AngelTrack will do the rest.

### Separate Tracking

Your uploads to your county/state are tracked separately from those to any regional registry, even though the exact same data is being sent to each. For example, suppose dispatch 12345 passes QA, passes schematron validation, and is now ready for upload. AngelTrack will send it to the jurisdictional target first (county or state) to satisfy your obligations, and then it will send it to any regional registry who fits the criteria (service + state + county + city match).

One upload might succeed while the other might fail. You will see these activities in the journal, and on the "Outflows" tab of the respective dispatch. Any errors are also reported with the associated credentials.

### Regional Schematrons Not Supported

You cannot specify a different schematron for a regional registry.

There can be *per-county* schematrons, and a *statewide* schematron, plus the built-in *national* schematron, but *regional* registries span multiple counties and so cannot also impose a schematron. That means the registional registry's data requirements must conform to your state and any jurisdiction county.

- [General Topics](https://support.angeltrack.com/help/general-topics?hsLang=en#main-content)

    - [Configuration](https://support.angeltrack.com/help/general-topics?hsLang=en#configuration)
    - [Integrations](https://support.angeltrack.com/help/general-topics?hsLang=en#integrations)
    - [State and County Uploads](https://support.angeltrack.com/help/general-topics?hsLang=en#state-and-county-uploads)
- [Dispatch](https://support.angeltrack.com/help/dispatch?hsLang=en#main-content)

    - [Basic Dispatch](https://support.angeltrack.com/help/dispatch?hsLang=en#basic-dispatch)
    - [Schedules and Recurrences](https://support.angeltrack.com/help/dispatch?hsLang=en#schedules-and-recurrences)
    - [Connections to Billing](https://support.angeltrack.com/help/dispatch?hsLang=en#connections-to-billing)
    - [Advanced Topics and Tips](https://support.angeltrack.com/help/dispatch?hsLang=en#advanced-topics-and-tips)
    - [Vertex AI Dispatch Planner](https://support.angeltrack.com/help/dispatch?hsLang=en#vertex-ai-dispatch-planner)
- [Supervisors](https://support.angeltrack.com/help/supervisors?hsLang=en#main-content)

    - [Fleet](https://support.angeltrack.com/help/supervisors?hsLang=en#fleet)
    - [Compliance](https://support.angeltrack.com/help/supervisors?hsLang=en#compliance)
- [Billing](https://support.angeltrack.com/help/billing?hsLang=en#main-content)

    - [Invoicing](https://support.angeltrack.com/help/billing?hsLang=en#invoicing)
    - [Pricing and Contracts](https://support.angeltrack.com/help/billing?hsLang=en#pricing-and-contracts)
    - [Coding, Claims, and Clearinghouse](https://support.angeltrack.com/help/billing?hsLang=en#coding-claims-and-clearinghouse)
    - [Prior Authorization and PCS](https://support.angeltrack.com/help/billing?hsLang=en#prior-authorization-and-pcs)
    - [Billing Workflow](https://support.angeltrack.com/help/billing?hsLang=en#billing-workflow)
    - [Payments and EOBs](https://support.angeltrack.com/help/billing?hsLang=en#payments-and-eobs)
    - [Facility and Patient Records](https://support.angeltrack.com/help/billing?hsLang=en#facility-and-patient-records)
- [QA Review](https://support.angeltrack.com/help/qa-review?hsLang=en)
- [Salesperson](https://support.angeltrack.com/help/salesperson?hsLang=en)
- [Human Resources](https://support.angeltrack.com/help/human-resources?hsLang=en#main-content)

    - [Timeclock](https://support.angeltrack.com/help/human-resources?hsLang=en#timeclock)
    - [Schedules and Vacations](https://support.angeltrack.com/help/human-resources?hsLang=en#schedules-and-vacations)
- [Crew Members](https://support.angeltrack.com/help/crew-members?hsLang=en#main-content)

    - [Report Completion](https://support.angeltrack.com/help/crew-members?hsLang=en#report-completion)
    - [Documents](https://support.angeltrack.com/help/crew-members?hsLang=en#documents)
- [Fire](https://support.angeltrack.com/help/fire?hsLang=en)
- [IT](https://support.angeltrack.com/help/it?hsLang=en#main-content)

    - [Data Protection](https://support.angeltrack.com/help/it?hsLang=en#data-protection)
    - [Troubleshooting](https://support.angeltrack.com/help/it?hsLang=en#troubleshooting)
- [Miscellaneous](https://support.angeltrack.com/help/miscellaneous?hsLang=en#main-content)

    - [Articles for patients and facilities](https://support.angeltrack.com/help/miscellaneous?hsLang=en#articles-for-patients-and-facilities)
- [Report Builder](https://support.angeltrack.com/help/report-builder?hsLang=en#main-content)

    - [Walkthroughs](https://support.angeltrack.com/help/report-builder?hsLang=en#walkthroughs)
    - [Built-In Reports](https://support.angeltrack.com/help/report-builder?hsLang=en#built-in-reports)

[![Chill listening crop-3](https://support.angeltrack.com/hs-fs/hubfs/A.400x400.png?width=40&height=40&name=A.400x400.png "Chill listening crop-3")](https://support.angeltrack.com/help/index.htm?hsLang=en)

AngelTrack Support Home

Copyright © 2026, AngelTrack LLC