Patient encounter data reporting
- • availability of patient outcome data
- • use of data
- • rules
(1)(a) Ambulance services shall report patient encounter data to the electronic emergency medical services data system managed by the Oregon Health Authority for each patient care event in accordance with rules adopted by the authority under ORS 682.017 (Rules).
(b) The authority by rule shall specify the patient encounter data elements to be transferred from the electronic emergency medical services data system to the Oregon Trauma Registry and shall establish the procedures for the electronic transfer of the patient encounter data.
(2)(a) The patient outcome data described in subsection (3) of this section about a patient who an ambulance service transported to a hospital, and that the hospital entered into the Oregon Trauma Registry, must be available to the designated official of the ambulance service that transported the patient.
(b) The authority by rule shall specify the method by which the patient outcome data will be made available to the designated official of an ambulance service.
(3) Patient outcome data includes:
(a) The health outcomes of the patient who was the subject of the prehospital care event from the emergency department or other intake facility of the hospital, including but not limited to:
(A) Whether the patient was admitted to the hospital; and
(B) If the patient was admitted, to what unit the patient was assigned;
(b) The patient’s chief complaint, the diagnosis the patient received in the emergency department or other intake facility and any procedures performed on the patient;
(c) The emergency department or hospital discharge disposition of the patient; and
(d) Demographic or standard health care information as required by the authority by rule.
(4) Data provided pursuant to this section shall be:
(a) Treated as a confidential medical record and not disclosed; and
(b) Considered privileged data under ORS 41.675 (Inadmissibility of certain data provided to peer review body of health care providers and health care groups) and 41.685 (Inadmissibility of certain data relating to emergency medical services system).
(5) Data provided pursuant to this section may be used for quality assurance, quality improvement, epidemiological assessment and investigation, public health critical response planning, prevention activities and other purposes that the authority determines necessary.
(6)(a) A nontransporting prehospital care provider may report patient encounter data to the electronic emergency medical services data system.
(b) A nontransporting prehospital care provider that reports patient encounter data shall comply with the reporting requirements that apply to ambulance services.
(c) The patient outcome data described in subsection (3) of this section must be available to the designated official of the nontransporting prehospital care provider that provided care and reported patient encounter data about the patient.
(7) The authority may adopt rules to carry out this section, including rules to:
(a) Establish software interoperability standards and guidance to assist in reporting the patient encounter data required by this section;
(b) Specify the method by which the patient outcome data will be made available to nontransporting prehospital care providers; and
(c) Define “nontransporting prehospital care provider.” [Formerly 682.037; 2009 c.595 §1072; 2011 c.703 §52; 2017 c.229 §3]
Note: Sections 6 and 7, chapter 229, Oregon Laws 2017, provide:
Sec. 6. Waiver of patient encounter data reporting requirements. The Oregon Health Authority may waive the patient encounter data reporting requirements of ORS 682.056 (Patient encounter data reporting) for an ambulance service that demonstrates to the satisfaction of the authority that the ambulance service is unable to comply with the reporting requirements of ORS 682.056 (Patient encounter data reporting). [2017 c.229 §6]
Sec. 7. Section 6 of this 2017 Act is repealed on December 31, 2021. [2017 c.229 §7]
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.