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 track each PCR for upload to two separate targets: One being your county or state, and the other being a regional trauma registry.
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 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 non-forwarding registry; and
- One of either:
- A state registry; or
- A county registry who forwards to the state.
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 upload 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 State Uploads Guide.
Designation of Non-Forwarding Registry
Each of your state upload 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 credentials and their marks correctly, AngelTrack will do the rest.
Separate Tracking
Your uploads to your county/state are tracked separately from those to the 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. 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.