IamResponding receives a transmission of CAD information directly from the CAD, and provides that feed to the field responders of the dispatched using agencies that are using IamResponding. Preferably, this information is transmitted via our CAD Incidents API. However, in the event that the API option is not available, we accept data via SMTP and/or SNPP. Information via SMTP/SNPP is transmitted to IamResponding to a specified address that IamResponding will provide to the dispatch center.
When transmitting via SMTP/SNPP, it is preferred that all of the data be contained within the body of the email. If some of the pertinent information is contained in either the subject line, or an attachment, please advise IamResponding's ECC Integration Team of that. Please note that we do not accept PDF attachments.
If your CAD can send to multiple email addresses for a single department based on incident types (e.g. fire calls vs EMS calls) or unit based dispatching, then IamResponding's team will provide you with multiple email addresses for the differing incident types or units.
Ideally, all data transmissions to IamResponding from CAD will include the following elements:
1. Transmit every possible field from the CAD data. The more information the better from our perspective. Our users will be able to reduce that data to what they need/want on their end via parsing tools that we provide to them. If you have character limits on your outbound feed, please set those as high as you can as we do not have character limits.
2. Transmit every field with every incident notification, even if some fields may be blank for some incidents. This is so that every message received by us is formatted exactly the same.
3. Include field headers/names for each field. If you have character limits that would preclude all fields from being sent, field names/headers can be eliminated as long as you insert what is requested in item 4 below.
4. Where possible, auto-insert a common and consistent field separator between each field. For example, a slash, asterisk, pound sign (hashtag), etc.
5. Where possible, include the Latitude and Longitude coordinates of the incident location. If this is available via your CAD, this helps to ensure greater accuracy when users are mapping the location of the incident via their IamResponding mapping system.
6. Send only one email per dispatch (or one email per dispatch group). This prevents the IamResponding app from activating several times for one dispatch, which can be bothersome for responders.
RapidSOS Integration. IamResponding has an integration with RapidSOS that helps reduce response times by supplementing CAD dispatch data with important additional information
including 911 caller location, telematics, building alarm sensor data and more. This is very similar to the data that you receive via your RapidSOS system or integration. Caller location information supplemented by the RapidSOS integration is very important in reducing emergency response times because it can provide critical location information in incidents that have a poorly addressable or non-addressable location (e.g. incidents on roadways, at apartment complexes, at large school, commercial or athletic complexes, at parks and wooded areas, etc.).
In order for IamResponding’s integration with RapidSOS to work, we need you to include the 911 caller’s phone number in the dispatch feed that you provide to IamResponding, in a consistent format and location within the feed, and in a parsable manner (e.g. with a field name and/or separated by a consistent field separator).
Sample of an ideally formatted dispatch (Bold are the most important fields to transmit) Nature: Cardiac Arrest
Address: 1111 Figueroa Pl
City/Township: Smithville
State: IL
Location Name: College
Comments: 911 caller is with patient, CPR in progress. Caller is unsure what building they are located in.
Latitude: 33.784
Longitude: -118.284
Primary Agency: MFD
Agencies Assigned: MFD, JFD, LFD, FFD
Units: E1, E2, E32, TK3, TK2, R2, C1, C2, C3
Incident ID: 22-001117
Priority: 1
Opened: 12:02:57 12/21/2022
Caller Phone Number: 1 (555) 555-5555
Call Back Name: Mike Heneka