ATCEMS Performance Dashboard > Stroke Bundle Completion per Quarter > Performance Measure Definition: Stroke Alert Patient Count
Performance Measure Definition: Stroke Alert Patient Count

Description: Count of patients contacted by ATCEMS personnel who are documented as meeting Stroke Alert criteria.
Desired Outcome:  Not applicable
Relevance:  This measure provides context for rate-based indicators describing ATCEMS management of Stroke Alert patients.
Measure Domain: Clinical Care
Type of Measure:  Output

Operational Specifications
Formula Description:  Count of all patients encountered by ATCEMS personnel documented as meeting Stroke Alert criteria.
Unit of Analysis:  Patient contacts
Population:
  • Numerator: All patients encountered by ATCEMS personnel for whom a Stroke Alert is called.
  • Denominator:  Not applicable
Measure Frequency:  Quarterly
Minimum Population/Sample:  None
Performance Standard:  Not applicable
Acceptable Quality Level:  Not applicable
Interval Description:  Not applicable
Reporting Value(s):  Count of Stroke Alert patients encountered by ATCEMS personnel.
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: May stratify by demographic, geographic, chronologic, or other factors as needed.
Limitations:  None
Related Measures:  None
Notes:  None

Reporting
ATCEMS Open Performance Dashboard
City of Austin Open Data Portal


References
Office of the Medical Director, Austin/Travis County EMS System (2016).  “Clinical Standard CS-7: Definition of a Patient.” Austin-Travis County Emergency Medical Service System Clinical Operating Guidelines version 021716.
Office of the Medical Director, Austin/Travis County EMS System (2016).  “Clinical Standard CS-34: Stroke Alert Criteria.” Austin-Travis County Emergency Medical Service System Clinical Operating Guidelines version 021716.

Metadata 
Development Status: Actively reporting 
Definition Version: Version A
Revision Date: 2017-03-07
Revised By: David Andersen