Capabilities
Capabilities | Supported |
Connector Capabilities | |
Read | Yes |
Backfill | No |
Bidirectional Capabilities | |
Incident Create | Coming soon |
Incident Update | Coming soon |
Narrative Update | Coming soon |
Write-back to QED is coming soon. It will let GovWorx create incidents, update incidents and add narrative in QED.
Overview
This is an API integration. QED does not use the GovWorx Data Agent. Nothing is installed on your network. QED sends incident data to GovWorx over a secure internet connection.
QED sends a complete snapshot of the incident each time it changes. This covers entry, update, dispatch, unit status, disposition and close. GovWorx stores every snapshot.
GovWorx sends the incident to CommsCoach when the incident first closes. GovWorx keeps later changes to a closed incident, and CommsCoach keeps the first closed snapshot.
How It Works
GovWorx creates the QED connection for your agency.
GovWorx issues a credential for your agency and shares it through a secure channel.
QED sends each incident snapshot to GovWorx.
GovWorx maps QED identifiers to GovWorx values, such as personnel, radio units, incident types, priorities and dispositions.
For the endpoint, authentication and message format, see the GovWorx developer documentation.
Standard Data Fields
These are the standard data fields GovWorx reads from QED. The tables below show each GovWorx field and the QED field it comes from. The names are the qed-native names. QED maps its own fields to NENA EIDO before it sends the nena-eido format.
Note: Additional fields are considered enhancement requests.
Incident fields
GovWorx field | QED source | Notes |
Incident ID |
| CAD record key. Required. |
Incident Number |
| Required. |
Incident Type |
| Uses incidentType when incidentTypeName is empty. GovWorx also reads incidentTypeCode, which is required, and maps it to a GovWorx incident type. |
Priority |
| GovWorx maps the QED value to a GovWorx priority. |
Incident Date |
| Required, with a time zone offset. |
Call Received Time |
| QED does not send a separate pickup time. |
Closed At |
| Present only on a closed incident. |
Call Taker ID |
| Uses operator when operatorPersonnel is empty. GovWorx maps the ID to a GovWorx user. |
Call Position |
| The call taking workstation. |
Caller Name |
| |
Caller Number |
| Uses e911PhoneNumber when reportingPersonPhone is empty. |
Location |
| GovWorx builds the location from these parts. |
Additional Context |
| Added as labeled lines in that order. |
Case Number |
| The agency-specific case number. |
Agency Type |
| |
Response Area |
| |
Disposition |
| GovWorx reads dispositionCode and keeps disposition as the label. GovWorx maps the code to a GovWorx disposition. |
Agency |
| GovWorx uses the first one available, in that order. Required. |
Notes
GovWorx field | QED source | Notes |
Note Text |
| incidentDescription is also read as a note. |
Note By |
| Uses userId when enteredById is empty. GovWorx keeps enteredBy as the display name. |
Note Time |
|
Responders and units
GovWorx field | QED source | Notes |
Unit Name |
| A unit needs a unitId for GovWorx to record its status. |
Personnel ID |
| Also read from dispatchResponders.dispatchPersonnel. GovWorx maps the ID to a GovWorx user. |
Dispatched At |
| GovWorx also accepts DISP. The earliest time is used. |
Enroute At |
| GovWorx also accepts RESP. |
Arrived At |
| GovWorx also accepts ONLOC. |
Cleared At |
| GovWorx also accepts CLEAR. |
Need Help?
If you need assistance, contact the GovWorx Technical Services team or email [email protected].
