Part 2 retained electronic-record sealed container

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

Live 42 CFR 2.19(b)(2)(iii) requires the retained portable device or original-and-backup electronic media to be sealed in a container with any equipment needed to read or access the information. The container must bear the prescribed former-program, legal-authority, and outside retention-date label and be held by a responsible person in a protective environment. Section 2.16 supplies the governing security procedures.

Package the usable archive

The electronic-retention procedure includes equipment needed for access. Inventory devices, cables, adapters, readers, hardware tokens, manuals, software media, licenses, formats, checksums, and recovery instructions while storing decryption tools separately as required.

Use the prescribed label

Identify the program name, citation to the statute, regulation, court order, or other retention authority, and a date no later than the required end. Match the label to the inventory, authority calculation, custody log, and final-action calendar.

Protect the container over time

Apply physical and environmental protection along with § 2.16 safeguards. Address seals, tamper checks, access, fire, water, humidity, temperature, pests, power, media aging, moves, disasters, succession, incidents, inspection cadence, and evidence.

Package a self-contained, readable archive

Inventory encrypted media, backup, cables, adapters, readers, hardware tokens, power supplies, manuals, data dictionaries, schema, file formats, software installers, licenses, integrity values, and recovery instructions. Include only what the future responsible person needs to retrieve lawful records; store decryption tools separately as paragraph (b)(2)(iv) requires.

Test the complete package before sealing. A readable device today may fail after operating systems, connectors, credentials, or vendor services disappear. Record the tested equipment, software version, sample, operator, date, result, and any dependency outside the container.

Use the required label without exposing patients

Populate the former program name, exact statute, regulation, court order, or other legal retention authority, and a date no later than the required end. Link the label to a protected inventory, authority calculation, hold record, responsible person, and final-action calendar.

Avoid patient names, diagnoses, SUD language beyond what the prescribed label requires, or detailed contents on external warehouse labels. Use a neutral container identifier and protect the crosswalk.

Seal, receive, and control openings

Choose a container suitable for the media, equipment, duration, handling, and environmental risk. Record container and seal identifiers, contents, counts, packer, verifier, date, condition, destination, receipt, and responsible person. Use tamper evidence proportionate to risk.

Require identity, lawful purpose, approval, access log, media and equipment checkout, secure workspace, copy control, return, integrity check, and resealing for every opening. Investigate broken seals, missing parts, changed contents, failed decryption, or undocumented access.

Protect the environment and long-term usability

Address theft, fire, water, temperature, humidity, dust, pests, magnetism where relevant, shock, power, media aging, physical security, visitor and vendor access, facility closure, relocation, and disaster. Inspect at a defined interval and after any event.

Test access and readability at a risk-based cadence without leaving clear-text copies. Maintain replacement reader equipment, updated instructions, responsible-person and successor contacts, and separate decryption capability. Record every migration or media refresh as a controlled archive change.

Reach the final date deliberately

Notify the responsible person before the labeled end, recheck authority and holds, authorize sanitization, inventory all media and equipment, apply section 2.16 procedures, verify non-retrievability, retire keys and temporary copies, preserve evidence, and close the container record.

Prepare a lawful retrieval procedure

Define who can request records, how identity and authority are verified, which privacy and legal owner approves access, where the container may be opened, who handles media and equipment, how decryption tools arrive separately, what copies may be created, and when everything returns or is sanitized. Use neutral communications while request authority is unresolved.

For each retrieval, record requester, purpose, authority, record scope, approval, container and seal status, media, equipment, key or tool use, clear-text copies, disclosure, receipt, return, resealing, and cleanup. A future request should not force the custodian to invent an access workflow during a deadline.

Example

Ten sealed electronic containers are inspected. Seven contain complete media and equipment, exact label, seal log, protected environment, access list, inspection, custodian, and final date; three omit a required reader. Readiness is 7 of 10 containers.

Sealed-container checklist

• package encrypted media, backup, readers, adapters, software, formats, and instructions;
• test a complete retrieval before sealing and record all external dependencies;
• apply the prescribed authority and outside-date label with a protected crosswalk;
• identify and reconcile container, seal, contents, condition, custody, and receipt;
• control opening, copying, return, resealing, environment, inspection, and migration; and
• recheck authority, sanitize all components, retire keys, and document final closure.

The container must preserve both confidentiality and future usability. A sealed but unreadable archive cannot meet the retained-record purpose.