The same 1:30 a.m. can describe two different clinical events
When daylight saving time ended on November 1, 2026, clocks moved backward from 2:00 a.m. to 1:00 a.m. local time. For a hospital, hospice, home-health agency, urgent care center, or other healthcare organization operating overnight, the transition can create apparently duplicated EHR timestamps. A medication administered at 1:30 a.m. before the change and an assessment entered at 1:30 a.m. after the change did not occur at the same instant. The distinction matters when someone later reconstructs a clinical timeline.
This is not a new Medicare billing rule or a categorical finding of noncompliance. It is a predictable records-management problem that may affect patient safety reviews, treatment sequencing, claim support, incident investigations, and contractor audits if a system exports timestamps without sufficient context.
Why time-zone information matters
The National Institute of Standards and Technology explains that, on November 1, local clocks repeated the 1:00 a.m. hour. NIST’s time services distribute Coordinated Universal Time (UTC), while operating systems apply local-time and daylight-saving adjustments. An audit record with a UTC time, a time-zone offset, or another unambiguous sequence indicator can help distinguish the repeated local times. A plain-text local timestamp alone may not.
For illustration, 1:30 a.m. Eastern Daylight Time (UTC−04:00) occurred an hour before 1:30 a.m. Eastern Standard Time (UTC−05:00). A clinician reviewing an exported chart might see two entries marked 1:30 a.m., yet the entries occurred one hour apart. The relevant question is how the specific EHR, medication administration system, scheduling tool, or billing platform stores and displays the source timestamp.
Clinical record rules still apply
Hospitals participating in Medicare are subject to medical-record requirements that include appropriately dated, timed, and authenticated entries. CMS guidance emphasizes that accurate dates and times establish clinical timelines and help evaluate patient care. That guidance does not create a special daylight-saving exception or require a particular software architecture. The practical obligation is to retain records that are accurate and defensible under applicable rules.
Separately, the HIPAA Security Rule’s audit-controls standard requires covered entities to implement mechanisms to record and examine activity in information systems containing or using electronic protected health information. Its integrity standard requires policies and procedures protecting electronic PHI against improper alteration or destruction. These standards do not prescribe a universal daylight-saving-time format, but they support examining whether system activity can be reconstructed reliably.
Areas where the repeated hour can complicate an audit
- Medication administration and treatment sequencing: a reviewer may need to distinguish an order, administration, monitoring note, and subsequent reassessment occurring during the two different 1:00 a.m. hours.
- Hospice and home-health records: encounters, after-hours calls, visit documentation, and staff handoffs may rely on time-sensitive notes and system-generated histories.
- Incident reporting: falls, changes in condition, emergency transfers, and notification sequences may look out of order if a report uses local timestamps without offsets.
- Time-based services and billing support: where an applicable code requires actual elapsed time or a documented duration, a duplicated clock-hour display should not substitute for evidence of the time actually furnished.
- Vendor audit exports: the EHR may preserve UTC or offset data internally while a CSV, PDF, or third-party report drops it, creating a misleading timeline.
A narrowly tailored post-transition review
Start with the systems that actually recorded activity between approximately 12:30 a.m. and 3:00 a.m. local time on November 1. Ask the EHR or vendor whether the underlying data preserves UTC, a local time-zone offset, a monotonic event sequence, or comparable information. Test one or two known records without editing them to see whether the printed chart, audit log, and exported report preserve the distinction.
Then reconcile any time-sensitive entries against contemporaneous source material, such as medication administration records, nursing notes, device logs, call records, orders, and shift documentation. If a printed record seems internally inconsistent, preserve the original file and metadata, document the explanation, and use the established amendment or correction workflow where necessary. Do not backdate, silently overwrite, or manufacture a reconstructed timestamp.
For contractor-response purposes, a concise explanatory cover note may be more useful than a bulk export without context. Where records genuinely contain errors, address them accurately rather than implying that the daylight-saving change excuses defects. Legal counsel and appropriate clinical leadership can help distinguish technical display issues from substantive documentation or billing problems.
What to request from your EHR vendor
- The vendor’s description of time-zone and daylight-saving handling for clinical entries, audit logs, printed records, and exports.
- Confirmation of whether original UTC timestamps, offsets, sequence identifiers, and audit histories are retained and retrievable.
- A demonstration using November 1, 2026 test records showing both instances of the repeated hour.
- A documented escalation path for correcting export or display defects without changing original clinical facts.
- A clear division of responsibility among clinical staff, compliance, IT, and outside vendors when an audit requests source data.
For related BOLO analysis, see Healthcare Audits & Investigations, healthcare evidence holds and digital records, and Medicare appeals evidence.
Primary authorities
- NIST: Daylight Saving Time Rules (2026 fall-back and UTC/local-time handling).
- CMS Survey and Certification Letter 08-12 (hospital medical-record entries dated, timed, and authenticated).
- HHS OCR: HIPAA Audit Protocol (45 C.F.R. §§ 164.312(b) and 164.312(c)(1), audit controls and integrity).
- HHS/NIST: HIPAA Security Rule Implementation Guide (activity review and audit controls).
This article provides general compliance information as of November 2, 2026. It does not establish that any particular EHR or provider violated law or payer requirements.