ATCEMS Performance Dashboard > Response Interval Compliance > Performance Measure Definition: Response Interval Performance
Performance Measure Definition: Response Interval Performance
Description: This indicator measures percentage of incidents for which the City of Austin and Travis County meet response interval goals. It is limited to unscheduled responses received through the 911 communications system, and incidents where initial triage is conducted by ATCEMS personnel. Incidents receiving a response from only ESD ambulances (i.e., no ATCEMS response) are not included in this measure.
Desired Outcome: Arrive quickly to EMS calls with ambulances, supervisors, or other ATCEMS ALS equipped resources.
Relevance: Customers have an expectation for a quick response to their emergency. ATCEMS measures the overall percentage of calls to which we arrive on time.
Measure Domain: Operations
Type of Measure: Process
Operational Specifications
Formula Description: Count of incidents where ATCEMS met or exceeded response time goals, divided by the count of all qualifying incidents.
The resulting measure is expressed as a percentage.
Unit of Analysis: Incident
Population: 
  • Numerator: Incidents where ATCEMS met response time goals, and ATCEMS Communications personnel conduct initial incident triage.
  • Denominator: All incidents where ATCEMS Communications personnel conduct initial incident triage.
Measure Frequency: Monthly
Minimum Population/Sample: No minimum
Performance Standard: Meet response time goals for 90% of all incidents
Acceptable Quality Level: Reliability may not fall below 87% for more than two consecutive months or any three months in a year without special cause.
Interval Description: Response Interval begins with the earliest recorded time that a call is answered, and ends when the first ATCEMS unit is recorded in CAD as arrived on scene or staging nearby, if applicable.
Reporting Values: Percent of incidents meeting goal. Fractile response times may also be reported if requested.
Aggregation
  • Temporal aggregations (month, hour of day, etc.) are based on the date/time of earliest recorded call pickup.
  • Geographic aggregation is based on incident location
Stratification
  • Service Zone (city, county)
  • Incident Response Priority
  • City of Austin Council District
Limitations: This measure is limited to incidents received through the 911 system, where ATCEMS communicated with the primary reporting party for purposes of incident triage and provision of pre-arrival instructions, when appropriate.
Incidents reported by other public safety agencies (including requests for assistance) are excluded from this measure.
Related Measures: None
Notes: ESD 2 (Pflugerville Fire Department) began deploying ambulances to respond to medical incidents within its district in January 2017.  These incidents are excluded from ATCEMS performance reporting.
ESD incident filtering is performed by ETL processes.
Reporting
ATCEMS Open Performance Dashboard
City of Austin Open Data Portal
Travis County Performance Dashboard
  • Medium: Web site charts [http://www.austintexas.gov/department/performance-indicators] contained in section “Key Result Area: Emergency Response.”
  • Orientation: External
  • Format: Line chart of monthly values, beginning October 2010.
  • Update Frequency: Monthly
  • Data Source: Open Data table [EMS – Incidents by Month]
City of Austin Performance Measure Database
  • Performance Measures:
  1. 1405 - Percent of potentially life-threatening calls (priority 1) responded to within 9 minutes and 59 seconds within the City of Austin
  2. 8228 - Percent of priority one through five calls responded to on time within the City of Austin and Travis County
  3. 8229 - Percent of priority 1 through 5 calls responded to on time within the City of Austin
  • Orientation: External
  • Aggregation Level: Month
  • Update Frequency: Monthly

References
Interlocal Agreement Between the City of Austin and Travis County for Emergency Medical Services (Fiscal Year 2014)
Metadata
Development Status: Currently reporting
Definition Version: Version D
Revision Date: 2017-01-12
Revised By: David Andersen