# CMS hospital Conditions of Participation for medical records and emergency preparedness, explained

Two Medicare hospital conditions, 42 CFR 482.24 and 482.15, set the baseline for how an electronic record is authenticated, secured and retained, and how it stays available and shareable when an emergency disrupts operations.

Explainer · Healthcare · Operations & Workforce. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- 42 CFR 482.24 (medical record services) requires a record for every individual evaluated or treated, retention for at least 5 years, authentication of entries, and protection against unauthorized access or alteration.
- 482.24(d) requires hospitals whose electronic systems conform to the content exchange standard at 45 CFR 170.205(d)(2) to send patient event notifications at registration, admission, discharge and transfer.
- 42 CFR 482.15 (emergency preparedness) requires an all-hazards program whose policies include a system of medical documentation that preserves patient information, protects confidentiality, and secures and maintains the availability of records.
- The emergency plan, policies, communication plan and training and testing program are reviewed and updated at least every 2 years; exercises test the plan at least twice per year.
- A CMS proposed rule published November 10, 2026 (CMS-3484-P) would update the fire and power codes referenced in 482.15. Comments are due January 11, 2027.

## Why these two conditions belong together

Conditions of Participation are the requirements hospitals must meet to participate in the Medicare and Medicaid programs [4]. Two of them shape a hospital’s electronic health record more than their titles suggest. The medical records condition at 42 CFR 482.24 governs what goes into the record and how it is authenticated, secured and kept [1]. The emergency preparedness condition at 42 CFR 482.15 requires the hospital to keep records available and shareable when an emergency disrupts normal operations [2]. Neither requires an electronic record: 482.24 allows entries to be authenticated in written or electronic form [1], and CMS said the emergency preparedness rule does not mandate the use of electronic health records [3].

## What 482.24 asks of a record system

The hospital must have a medical record service with administrative responsibility for medical records, and a record must be maintained for every individual evaluated or treated in the hospital, inpatient and outpatient [1]. The standards that bear most directly on an electronic system are these [1]:

- **Integrity and security.** The hospital must use a system of author identification and record maintenance that ensures the integrity of the authentication and protects the security of all record entries.
- **Retention.** Records are retained in their original or legally reproduced form for at least 5 years.
- **Retrieval.** A system of coding and indexing must allow timely retrieval by diagnosis and procedure.
- **Confidentiality.** Information may be released only to authorized individuals, and the hospital must ensure that unauthorized individuals cannot gain access to or alter patient records. Original records are released only under federal or state law, court orders or subpoenas.
- **Authentication.** All entries must be legible, complete, dated, timed and authenticated in written or electronic form by the person responsible. All orders, including verbal orders, are dated, timed and authenticated promptly.
- **Order sets.** Pre-printed and electronic standing orders, order sets and protocols are allowed only if the medical staff and nursing and pharmacy leadership have reviewed and approved them, they are consistent with nationally recognized and evidence-based guidelines, and they are reviewed periodically.
- **Timing.** A medical history and physical examination is completed no more than 30 days before or 24 hours after admission or registration, and placed in the record within 24 hours. The final diagnosis and completion of the record follow within 30 days after discharge.

### Electronic patient event notifications

Paragraph (d) applies only if the hospital uses an electronic medical records system or other electronic administrative system that conforms with the content exchange standard at 45 CFR 170.205(d)(2) [1]. Such a hospital must show that the notification capacity is fully operational and that the system sends notifications with at least the patient’s name, the treating practitioner’s name and the sending institution’s name [1]. Notifications go at the patient’s emergency department registration and inpatient admission, and immediately before or at discharge or transfer. The hospital must make a reasonable effort to reach post-acute care providers and suppliers and the patient’s established primary care practitioner or group, or another practitioner the patient identifies, consistent with law and the patient’s expressed privacy preferences [1]. CMS added these requirements in its May 2020 interoperability and patient access final rule [5].

## What 482.15 asks for continuity

The emergency preparedness condition requires a comprehensive program using an all-hazards approach [2]. The regulation text does not list specific hazards. Four elements carry most of the weight for records and systems:

- **The plan.** It is based on a documented facility-based and community-based risk assessment and addresses continuity of operations, including delegations of authority and succession plans. It is reviewed and updated at least every 2 years [2].
- **Policies and procedures.** Among other things, they must address “a system of medical documentation that preserves patient information, protects confidentiality of patient information, and secures and maintains the availability of records” [2]. They also cover tracking on-duty staff and sheltered patients, and arrangements with other hospitals to receive patients if operations are limited or stop [2].
- **The communication plan.** It includes primary and alternate means of communicating with staff and emergency management agencies; a method for sharing information and medical documentation with other providers to maintain continuity of care; a means of releasing patient information during an evacuation as permitted under 45 CFR 164.510(b)(1)(ii); and a means of sharing a patient’s general condition and location as permitted under 45 CFR 164.510(b)(4) [2].
- **Training and testing.** Training at least every 2 years, with documentation. Exercises twice a year: an annual full-scale community-based exercise, or a facility-based functional exercise when no community exercise is accessible, plus a second exercise that may be a tabletop. The hospital analyzes its response to drills, exercises and real events and revises the plan as needed. An actual emergency that activates the plan exempts the hospital from its next required full-scale or functional exercise [2].

A hospital in a health system may take part in a unified and integrated emergency preparedness program, provided each separately certified facility participates in developing it, is able to use it and complies with it, and has its own documented facility-based risk assessment [2].

## How the rules got here

CMS created the emergency preparedness requirements in a final rule effective November 15, 2016, which providers had to implement by November 15, 2017 [3]. Responding to comments on health information exchange, CMS said it was not mandating the use of electronic health records through that rule [3]. The rule’s benefits discussion cited Presidential Policy Directive 8, whose threats include cyber-attacks along with terrorism, pandemics and natural disasters [3].

A 2019 final rule, effective November 29, 2019, changed the program review requirement for most providers from annual to at least every 2 years, kept annual review for long-term care facilities, and moved training to every 2 years after initial training [4].

## What is proposed now

On November 10, 2026, CMS published a proposed rule to reduce regulatory burden across Medicare and Medicaid providers (file code CMS-3484-P) [6]. For hospitals, it would update the codes referenced in 482.15(e) and (h): the 2024 editions of the Life Safety Code (NFPA 101) and the Health Care Facilities Code (NFPA 99) in place of the 2012 editions, and the 2022 edition of NFPA 110 in place of the 2010 edition. It would add the phrase “install and maintain” to the power systems standard and replace “emergency generator” with “emergency power supply” [6]. Separately, it would require informed consent before the collection, storage, donation, transfer, banking or release of birth tissues, documented consistent with the medical records requirement at 482.24(c)(4)(v) [6]. Comments are due January 11, 2027 [6]. As checked on November 14, 2026, these are proposals, and the eCFR text, up to date as of November 12, 2026, does not include them [1] [2].

## Where the two conditions meet

Read together, the conditions ask a hospital to keep its records secure and authenticated in normal operations, and still available and shareable when normal operations stop. In our view, a hospital that depends on an electronic record should be able to show surveyors how it meets the documentation policy in 482.15(b)(5) during a system outage, how its communication plan shares records with receiving facilities, and how its exercises have tested both. Downtime procedures, offline copies and exercise scenarios built around a system failure are ways to do that; the regulation does not require any particular one.

This explainer describes the regulations; it is not legal advice, and hospitals should confirm with counsel and their accrediting organization how the conditions apply to them.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. Electronic Code of Federal Regulations. 42 CFR 482.24, Condition of participation: Medical record services. <https://www.ecfr.gov/current/title-42/section-482.24> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 42 CFR 482.15, Condition of participation: Emergency preparedness. <https://www.ecfr.gov/current/title-42/section-482.15> Checked November 14, 2026.
3. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). Emergency Preparedness Requirements for Medicare and Medicaid Participating Providers and Suppliers (final rule, 81 FR 63860). <https://www.govinfo.gov/content/pkg/FR-2016-09-16/html/2016-21404.htm> Checked November 14, 2026.
4. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). Regulatory Provisions To Promote Program Efficiency, Transparency, and Burden Reduction (final rule, 84 FR 51732). <https://www.govinfo.gov/content/pkg/FR-2019-09-30/html/2019-20736.htm> Checked November 14, 2026.
5. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). Interoperability and Patient Access (final rule, 85 FR 25510). <https://www.govinfo.gov/content/pkg/FR-2020-05-01/html/2020-05050.htm> Checked November 14, 2026.
6. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). Medicare and Medicaid Programs; Cutting Administrative Requirements for Excellence in Patient Care (proposed rule, 91 FR 72634). <https://www.govinfo.gov/content/pkg/FR-2026-11-10/html/2026-22812.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/cms-hospital-cops-medical-records-and-emergency-preparedness-explained>
Publisher: Moraph Insights
