California
STEMI Data Management Requirements.
22 CCR 100148.01
Source text
30 segments
22 CCR 100148.01
22 CCR 100148.01
ยง 100148.01. STEMI Data Management Requirements.
(a)
Data Collection and Reporting Process Requirements.
(1)
LEMSA. The local EMS agency (LEMSA) shall develop and implement a standardized data collection and reporting process for the STEMI critical care system.
(A)
The process shall include the collection of both prehospital STEMI patient care data and general acute care hospital (GACH) STEMI patient care data. The data shall include the elements specified in subdivision (b) and may include additional elements as specified by the LEMSA.
(B)
The LEMSA, in collaboration with STEMI receiving centers and EMS providers, shall develop a process for the sharing of outcome data from the STEMI receiving center to the EMS provider for all transported STEMI patients, including patients who were initially identified as potential STEMI cases but were ultimately not included in the STEMI receiving center's STEMI registry.
(2)
GACHs.
(A)
All STEMI receiving centers and STEMI referring hospitals shall maintain a LEMSA-approved STEMI patient registry (STEMI registry) within which the GACH shall submit STEMI registry data either directly to CEMSIS or to the LEMSA in a manner that is compliant with the Health Insurance Portability and Accountability Act of 1996 (Pub. L. 104-191). When the STEMI registry data is submitted to the LEMSA, the LEMSA shall upload the data to CEMSIS.
(B)
All GACHs that receive STEMI patients via EMS shall participate in the LEMSA data collection process in accordance with LEMSA policies and procedures.
(3)
Timing of submission. Prehospital STEMI patient care data elements and GACH STEMI patient care data elements shall be collected and submitted to the Emergency Medical Services Authority (EMSA), either directly or through the LEMSA in accordance with the LEMSA's data policy, on at least a quarterly basis and within ninety (90) days of patient discharge.
(b)
STEMI Patient Care Data Requirements.
(1)
Prehospital STEMI Patient Care Data Elements.
(A)
Prehospital STEMI patient care data elements selected by the LEMSA shall be compliant with the most current version of the CEMSIS and NEMSIS databases.
(B)
Prehospital STEMI patient care data elements collected by EMS providers and uploaded to CEMSIS shall include the following for any patient with a primary or secondary impression of STEMI:
(i)
EMS electronic patient care record (ePCR) number (NEMSIS element eResponse.03 -- Incident Number; eResponse.04 -EMS Response Number);
(ii)
Receiving facility (NEMSIS element eDisposition.01 Destination/Transferred To, Name; eDisposition.02 Destination/Transferred To, Code);
(iii)
Name: last, first (NEMSIS element ePatient.02 Last Name; ePatient.03 First Name);
(iv)
Date of Birth (NEMSIS element ePatient.17);
(v)
Age (NEMSIS element ePatient.15 Age; ePatient.16 Age Units);
(vi)
Gender (NEMSIS element ePatient.13 Gender);
(vii)
Race. (NEMSIS element ePatient.14 Race);
(viii)
Public Safety Answering Point (PSAP) Call Date/Time (NEMSIS element eTimes.01) for any call processed using Emergency Medical Dispatch (EMD);
(ix)
Unit Notified by Dispatch Date/Time (NEMSIS element eTimes.03);
(x)
Arrived at Patient Date/Time (NEMSIS element eTimes.07);
(xi)
Field electrocardiogram (ECG) Performed (NEMSIS element eProcedures.03);
(xii)
1st ECG Date/Time Procedure Performed (NEMSIS element eProcedures.01);
(xiii)
Unit Left Scene Date/Time (NEMSIS element eTimes.09);
(xiv)
Destination Team Pre-Arrival Alert or Activation (NEMSIS element eDisposition.24);
(xv)
Date/Time of Destination Prearrival Alert or Activation (NEMSIS element eDisposition.25);
(xvi)
Patient Arrived at Destination Date/Time (NEMSIS element eTimes.11).
(2)
GACH STEMI Patient Care Data. The required STEMI patient care data elements are specified in the STEMI Patient Care Data Dictionary (Rev. 11/2025), incorporated by reference, which identifies the minimum data fields required for submission to CEMSIS and ensures statewide consistency in reporting.
Source outline
29 anchors in this source
