Flight Vector to ESO Mapping

Below is the mapping of fields in Flight Vector to ESO XML fields.

Settings and fixed/blank fields

ESO field	Flight Vector source	What the user sees in the app
PatientCareRecordID	Hardcoded blank	No visible FV field for this by default
Guid	CAD setting	Misc Settings -> ESO GUID
TypeOfServiceRequested	Hardcoded blank unless overridden	No default visible FV field
TypeOfDispatchDelay	Hardcoded blank unless overridden	No default visible FV field
TypeOfResponseDelay	Hardcoded blank unless overridden	No default visible FV field
TypeOfSceneDelay	Hardcoded blank unless overridden	No default visible FV field
TypeOfTransportDelay	Hardcoded blank unless overridden	No default visible FV field
TypeOfTurnaroundDelay	Hardcoded blank unless overridden	No default visible FV field
ResponseModeToScene	Hardcoded blank unless overridden	No default visible FV field
ComplaintReportedByDispatch	Hardcoded blank unless overridden	No default visible FV field
EmdPerformed	Hardcoded blank unless overridden	No default visible FV field
DestinationZoneNumber	Hardcoded blank unless overridden	No default visible FV field
IncidentPatientDisposition	Hardcoded blank unless overridden	No default visible FV field
TransportModeToScene	Hardcoded blank unless overridden	No default visible FV field
DateTimeFireControlled	Hardcoded blank	No visible FV field
BeginningOdometerReading	Hardcoded 0	No operator-entered field; always starts at zero

 

 

Mileage and calculated route fields

These are computed from the mission flight plan.

ESO field	Flight Vector source	What the user sees in the app
OnSceneOdometerReading	Calculated mileage from start of route through the pickup/scene waypoint	Derived from route mileage; not usually a standalone labeled field
PatientDestinationOdometerReading	Calculated mileage from start of route through the dropoff/destination waypoint	Derived from route mileage to destination
EndingOdometerReading	Total calculated route mileage	Usually recognized more as Total Miles in reports, not an odometer box

 

 

Mission and time fields

XML field	Flight Vector source	What the user sees in the app
DateTimeIncidentOrOnset	request.Time	Usually Time, Request Time, or Original Call Date/Time
PSAPCall	request.911CallTime	911 Call Time
DateTimeDispatchNotified	Request time type Crew Confirm; if missing, fallback Launch Page	Usually Crew Conf. Page, fallback Launch Page
DateTimeUnitNotifiedByDispatch	Same as above	Same label as above
DateTimeUnitEnRoute	First flight-plan waypoint departure time	Departure from base/first waypoint; effectively the first Dep time in the route
DateTimeUnitArrivedOnScene	Pickup waypoint arrival time	Arrival at Scene / pickup waypoint
DateTimeUnitAtPatient	Arrive Bedside request time; if missing, same as scene arrival	Arrive Bedside
DateTimeTransferOfPatientCare	Depart Bedside request time; if missing, dropoff departure time	Depart Bedside
DateTimeUnitLeftScene	Pickup waypoint departure time	Departure from Scene / pickup waypoint
DateTimePatientArrivedAtDestination	Dropoff waypoint arrival time	Arrival at Receiver / Destination
DateTimeUnitCleared	Dropoff departure time if present, else request close time	Usually understood as Closed, or clear-from-destination timing
DateTimeUnitBackInService	Same source as DateTimeUnitCleared	Back-in-service timing; stock ESO maps it from the same value
DateTimeUnitCancelled	Request close time, but only if disposition type is cancelled	Mission Disposition = cancelled, with the mission Closed time
DateTimeUnitBackAtHomeLocation	Last waypoint arrival if last waypoint is an asset/base; else close time	Return-to-base/home arrival in the route
PatientDOB	Patient transfer item DOB	Date of Birth
DateTimeInitialResponderArrivedOnScene	Same as pickup waypoint arrival time	Arrival at Scene
DateTimeLastUnitCleared	Same source as DateTimeUnitCleared	Final clear/close timing

 

 

Mission identifier and aircraft fields

XML field	Flight Vector source	What the user sees in the app
IncidentNumber	Request/patient identifier from request.Number, sometimes patient-leg numbering	Usually Request Number
EmsUnitVehicleNumber	request.AircraftNNumber	Usually Tail, N Number, or Aircraft NNumber
EmsUnitCallSign	request.AircraftCallSign	Call Sign
VehicleDispatchLocation	Name of the first flight-plan waypoint, if that waypoint is an asset/base	Usually recognized as the departure Base or first asset waypoint name
VehicleDispatchGpsLocation.Lat	Latitude of first asset/base waypoint	Base/asset map coordinates, not usually a dedicated mission field label
VehicleDispatchGpsLocation.Long	Longitude of first asset/base waypoint	Base/asset map coordinates, not usually a dedicated mission field label

 

 

Patient fields

XML field	Flight Vector source	What the user sees in the app
PatientLastName	Patient transfer item last name	Last Name
PatientFirstName	Patient transfer item first name	First Name
PatientSSN	Patient transfer item SSN	SSN

 

 

Scene fields

These come from the mission leg Scene location.

ESO field	Flight Vector source	What the user sees in the app
SceneGpsLocation.Lat	Scene latitude	Scene -> Latitude
SceneGpsLocation.Long	Scene longitude	Scene -> Longitude
IncidentLocationName	scene.m_Name	Scene -> Description
IncidentAddress1	scene.GetStreetAddress()	Scene street address, often shown as Location or address under Scene
IncidentCity	Scene city	Scene -> City
IncidentCounty	Scene county	Scene -> County
IncidentState	Scene state	Scene -> State
IncidentZip	Scene ZIP	Scene -> Zip

 

 

Destination / receiver fields

These come from the mission leg Receiver contact. In Flight Vector this may be shown as Receiver, Receiving Facility, or Destination depending on screen.

XML field	Flight Vector source	What the user sees in the app
DestinationName	Receiver name	Receiver, Receiving Facility, or Destination; often effectively the hospital/facility name
DestinationAddress1	Receiver street address	Receiver/Destination address
DestinationCity	Receiver city	City under receiver/destination
DestinationCounty	Receiver county	County under receiver/destination
DestinationState	Receiver state	State under receiver/destination
DestinationZip	Receiver ZIP	Zip under receiver/destination
DestinationGpsLocation.Lat	Receiver location latitude	Receiver/Destination map location latitude
DestinationGpsLocation.Long	Receiver location longitude	Receiver/Destination map location longitude

Where Times are Located in FVCAD

• Settings → Request Times

  

• When you select ‘Request Times’, it will open the screen below. Notice the ‘System Name’ dropdown. This is how you will define the times for the following connections in ESO: (Flight Vector Time (ESO Time))

  - Crew Confirm (DateTimeDispatchNotified)

  - Crew Confirm (DateTimeUnitNotifiedByDispatch)

  - Arrive Bedside (DateTimeUnitAtPatient)

  - Depart Bedside (DateTimeTransferOfPatientCare)

  

• The following times are located in the transport plan:

  

• The close time will be shown in the history, similar to the example shown below.