These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Ambulance Dispatch System
- Data model and import order
The tables behind Ambulance Dispatch System
Ambulance Dispatch System ships with 15 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 15
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Load intake and authorizations
Loads identifies the transport; Authorizations links purpose, version and signed evidence through Load.
Crew credentials and assignments
Team members links to Users through User. Crew credentials links through team member; load assignments links through Load and Driver.
Stops and dispatch follow-up
Load stops links through Load and assigned crew. Dispatch tasks links through Load and assigned to.
Run notes and vital signs
Run notes links through load stop and Author. Vital signs links through load stop and recorded by.
Samples and medical dispensations
Samples links through load stop. Medical dispensations links through load stop and authorized by.
Service charges and settlements
Service charges links through load stop; Settlements links through Load. Exchange rates supplies read-only effective rates separately.
Every table, by feature
- Load intake and authorizations3
- Crew credentials and assignments5
- Stops and dispatch follow-up4
- Run notes and vital signs4
- Samples and medical dispensations5
- Service charges and settlements5
- Loads
Load identity and authorization status
Linked to Team members - Team members
Dispatch staff and crew
Linked to Users
- Team members
Dispatch staff and crew
Linked to Users - Users
Users
Linked to Users - Crew credentials
Verified crew credentials
Linked to Team members - Load assignments
Crew assignment intervals
Linked to Loads, Team members - Loads
Load identity and authorization status
Linked to Team members
- Load stops
Load stop visits and service episodes
Linked to Loads, Team members - Dispatch tasks
Follow-up dispatch tasks
Linked to Loads, Team members - Loads
Load identity and authorization status
Linked to Team members - Team members
Dispatch staff and crew
Linked to Users
- Run notes
Attributed run documentation
Linked to Load stops, Team members - Vital signs
Measured vital-sign readings
Linked to Load stops, Team members - Load stops
Load stop visits and service episodes
Linked to Loads, Team members - Team members
Dispatch staff and crew
Linked to Users
- Samples
Samples and their processing state
Linked to Load stops - Medical dispensations
Medication dispensations with lot and quantity
Linked to Load stops, Team members - Load stops
Load stop visits and service episodes
Linked to Loads, Team members - Team members
Dispatch staff and crew
Linked to Users - Crew credentials
Verified crew credentials
Linked to Team members
- Service charges
Service charges for load stops
Linked to Load stops - Settlements
Settlements received
Linked to Loads - Load stops
Load stop visits and service episodes
Linked to Loads, Team members - Loads
Load identity and authorization status
Linked to Team members - Exchange rates
Read-only effective exchange rates for this app.
Keys and references
Preserve the existing Id values and the exact reference targets during migration. Exchange rates uses ID. Keep Loads.record number recognizable to the operating team. A person’s display name can change, so resolve team members.User to the correct Users identity rather than joining by name.
Users.User references Users itself. Resolve that account reference with the platform’s existing user identities before loading dependent team members records. Keep load assignments.Driver and load stops.assigned crew distinct: assignment history and the person on a particular stop are related operational facts.
Authorizations.Status and Loads.authorization status use different value sets. Settlements references the load directly, while service charges references a stop. Report their amounts as separate aggregates. Exchange rates has Currency, effective from and Rate; importing it does not assign a currency to another table’s amount.
Migration order
- Resolve Users identities and their User references, then import team members.
- Import Loads with Owner references and recognizable record number values.
- Import Authorizations, crew credentials and load assignments against the resolved loads and people.
- Import load stops, then run notes, vital signs, Samples, medical dispensations and service charges using the correct load stop references.
- Import dispatch tasks and Settlements against Loads; reconcile their assigned to and financial source references. Keep exchange rates under its read-only source process.
- Compare source counts and selected reference chains, then rehearse ordinary role access and financial subtotals before cutover.
Set up Ambulance Dispatch System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.