RESOURCES | BLOG
September 14, 2025

HIPAA Compliance Checklist for Cardiology Remote Monitoring

Stay HIPAA-compliant in your cardiology remote monitoring program. Rhythm360 makes ePHI security operational — download the checklist today.

Last updated: September 22, 2026

Key Takeaways

  • Designate a Privacy Officer and Security Officer and confirm your practice’s covered-entity or business-associate status before building any HIPAA program.
  • Perform and document an accurate, recurring risk analysis that inventories every OEM portal, remote-monitoring platform, and RPM billing record holding cardiac ePHI.
  • Implement the full set of administrative, physical, and technical safeguards required by the Security Rule, and document any equivalent alternatives.
  • Execute Business Associate Agreements with every vendor that creates, receives, maintains, or transmits ePHI, and train all workforce members annually with documented completion records.
  • Use Rhythm360 to consolidate Medtronic, Boston Scientific, Abbott, and Biotronik data into a single HIPAA-aligned platform that automates documentation and CPT tracking.

Talk With Rhythm360 About Your Monitoring Program

Designate Leadership and Define HIPAA Scope

The HIPAA Privacy Rule and the Security Rule at 45 CFR Part 164 Subpart C require covered entities to designate a security official responsible for developing and implementing Security Rule policies and procedures. The Privacy Rule’s administrative requirements also expect a designated privacy lead. A cardiology practice qualifies as a HIPAA covered entity when it is a health care provider that transmits health information electronically in connection with a standard transaction, or when it operates a health plan such as Medicare or Medicaid. That status determines which vendors in your workflow are business associates, such as a remote monitoring platform vendor that receives, stores, or transmits cardiac ePHI on the practice’s behalf. It also defines the boundary of HIPAA’s reach, which excludes many organizations and direct-to-consumer wearables used outside a covered-entity program.

  • Confirm whether your practice is a covered entity or business associate. Owner: Privacy Officer. Evidence: Scope determination memo.
  • Designate a Privacy Officer responsible for Privacy Rule compliance. Owner: Practice Administrator. Evidence: Designation letter.
  • Designate a Security Officer responsible for Security Rule compliance under 45 CFR 164.308(a)(2). Owner: Practice Administrator. Evidence: Designation letter.
  • Document which external organizations fall outside HIPAA scope for your practice. Owner: Privacy Officer. Evidence: Scope exclusion memo.

Conduct the Risk Analysis

Once leadership is in place and scope is clear, the next step is a structured risk analysis. The risk analysis is the foundational, recurring step in every HIPAA compliance program. HHS guidance requires an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of all ePHI. In a cardiology practice, ePHI resides in the EHR and also flows through OEM portals for Medtronic, Boston Scientific, Abbott, and Biotronik devices, through remote monitoring platforms, and through RPM billing documentation. In the year to June 30, 2026, all seven OCR investigations that resulted in financial penalties found risk analysis failures. The HIPAA Security Rule does not specify how frequently a risk analysis must be performed. Most practices treat the process as ongoing, with annual review as the practical standard and a refresh when new technology or major workflow changes affect ePHI.

  • Conduct an accurate and thorough risk analysis under 45 CFR 164.308(a)(1)(ii)(A). Owner: Security Officer. Evidence: Risk analysis report.
  • Inventory every system where ePHI resides, including OEM portals for Medtronic, Boston Scientific, Abbott, and Biotronik. Owner: Security Officer. Evidence: Asset inventory.
  • Include remote monitoring platform data in the risk analysis scope. Owner: Security Officer. Evidence: Risk analysis report.
  • Document identified risks and remediation plans under 45 CFR 164.308(a)(1)(ii)(B). Owner: Security Officer. Evidence: Risk management plan.
  • Repeat the risk analysis annually and after any significant technology change. Owner: Security Officer. Evidence: Dated risk analysis reports.

Implement Administrative, Physical, and Technical Safeguards

The Security Rule at 45 CFR Part 164 Subpart C organizes safeguards into administrative, physical, and technical categories. Each category includes required and addressable implementation specifications. Addressable specifications still require a decision and documentation of how you meet the underlying requirement.

Administrative Safeguards

  • Implement a sanction policy for workforce violations under 45 CFR 164.308(a)(1)(ii)(C). Owner: Privacy Officer. Evidence: Sanctions policy.
  • Review information system activity regularly under 45 CFR 164.308(a)(1)(ii)(D). Owner: Security Officer. Evidence: Audit log reviews.
  • Maintain a contingency plan with data backup and disaster recovery under 45 CFR 164.308(a)(7). Owner: Security Officer. Evidence: Contingency plan.

Physical Safeguards

  • Apply facility access controls under 45 CFR 164.310(a). Owner: Security Officer. Evidence: Facility security plan.
  • Enforce workstation use and security policies under 45 CFR 164.310(b) and (c). Owner: Security Officer. Evidence: Workstation policy.
  • Implement device and media controls under 45 CFR 164.310(d). Owner: Security Officer. Evidence: Device disposal log.

Technical Safeguards

  • Use unique user identification under 45 CFR 164.312(a)(2)(i). Owner: Security Officer. Evidence: Access control policy.
  • Enable audit controls under 45 CFR 164.312(b). Owner: Security Officer. Evidence: Audit logs.
  • Implement person or entity authentication under 45 CFR 164.312(d). Owner: Security Officer. Evidence: Authentication policy.
  • Encrypt ePHI in transmission under 45 CFR 164.312(e)(2)(ii). Owner: Security Officer. Evidence: Encryption documentation.

Manage Vendors and Workforce Training

Every vendor that creates, receives, maintains, or transmits ePHI on the practice’s behalf is a business associate and requires a signed Business Associate Agreement (BAA). A covered entity can be held liable for a business associate’s HIPAA violation if it knew, or by exercising reasonable diligence should have known, of a pattern of activity constituting a material breach of the BAA. In a cardiology remote monitoring program, that includes OEM portal operators, remote monitoring platform vendors, EHR vendors, and billing services. Workforce training then turns these contractual protections into daily practice.

  • Execute a BAA with every vendor that creates, receives, maintains, or transmits ePHI. Owner: Privacy Officer. Evidence: Signed BAAs.
  • Verify subcontractor BAAs are in place under 45 CFR 164.314(a)(2)(i)(B). Owner: Privacy Officer. Evidence: Subcontractor BAAs.
  • Train all workforce members on HIPAA policies annually under 45 CFR 164.308(a)(5)(i). Owner: Privacy Officer. Evidence: Training log.
  • Document training completion for each workforce member. Owner: Privacy Officer. Evidence: Training records.

Incident Management and Breach Response

The HIPAA Breach Notification Rule requires covered entities to notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery of a breach. The 60-day clock starts on the first day the breach is known or reasonably should have been known, not when the forensic investigation concludes. OSF Healthcare System paid a $552,250 settlement in July 2026 after waiting 110 days to notify HHS and affected individuals following a ransomware breach affecting 53,907 patients. A clear incident plan helps your team act within these timelines.

  • Maintain a breach response plan with named roles and contact paths. Owner: Privacy Officer. Evidence: Breach response plan.
  • Notify affected individuals within 60 days of discovery under 45 CFR 164.404. Owner: Privacy Officer. Evidence: Notification letters.
  • Notify HHS within 60 days for breaches affecting 500 or more individuals under 45 CFR 164.408(b). Owner: Privacy Officer. Evidence: HHS notification.
  • Document the four-factor risk assessment for every incident. Owner: Privacy Officer. Evidence: Risk assessment.
  • Run tabletop exercises annually to rehearse breach response. Owner: Privacy Officer. Evidence: Exercise documentation.

Documentation and Retention Practices

Under 45 CFR 164.316(b)(2)(i), covered entities and business associates must retain all HIPAA Security Rule documentation for six years from the date of creation or the date it was last in effect, whichever is later. HIPAA requires covered entities to retain documentation such as sanctions records, authorization forms, and training documentation for at least six years. Auditors routinely request risk analysis reports, training logs, BAAs, and breach documentation as first-line evidence artifacts.

  • Retain all HIPAA policies and procedures for six years under 45 CFR 164.316(b)(2)(i). Owner: Compliance Officer. Evidence: Document retention log.
  • Retain risk analysis reports for six years. Owner: Security Officer. Evidence: Risk analysis archive.
  • Retain training logs for six years. Owner: Privacy Officer. Evidence: Training archive.
  • Retain BAAs for six years after termination. Owner: Privacy Officer. Evidence: BAA archive.
  • Retain breach documentation for six years. Owner: Privacy Officer. Evidence: Breach archive.

Secure ePHI in Cardiology Remote Monitoring Programs

Cardiology remote monitoring programs create ePHI across a wider attack surface than a standard medical practice. Telemetry from pacemakers, ICDs, implantable loop recorders, and remote physiologic monitors is identifiable electronic PHI and must be protected throughout its journey from the device to the practice. When a patient’s device transmits data through a manufacturer’s network such as Medtronic, Boston Scientific, Abbott, or Biotronik, and then through a remote monitoring platform before reaching the practice, each company handling that data functions as a business associate and requires a signed BAA. RPM billing documentation is also ePHI. That includes records for CPT 93297 (implantable cardiovascular physiologic monitor) and CPT 93298 (subcutaneous cardiac rhythm monitor or implantable loop recorder), each billable once per 30 days, as well as CPT 99454 (RPM device supply with daily recordings or programmed alerts, requiring a minimum of 16 days of data per 30-day period). All of this documentation must be secured and retained accordingly.

  • Inventory every OEM portal where cardiac device data resides, including Medtronic, Boston Scientific, Abbott, and Biotronik. Owner: Device Technician. Evidence: Portal inventory.
  • Eliminate shared logins across OEM portals. Owner: Security Officer. Evidence: Access control policy.
  • Secure unstructured PDFs downloaded from OEM portals. Owner: Security Officer. Evidence: Data handling policy.
  • Include remote monitoring platform data in the risk analysis. Owner: Security Officer. Evidence: Risk analysis report.
  • Secure RPM billing documentation for CPT 93297, 93298, and 99454. Owner: Billing. Evidence: Billing documentation policy.
  • Verify CPT 93297 and 93298 are each billed once per 30 days per patient for the correct device type. Owner: Billing. Evidence: Billing audit log.
  • Document device-specific CPT pairings to prevent device-type mismatch denials. Owner: Billing. Evidence: CPT mapping document.

See How Rhythm360 Secures Cardiac ePHI

HIPAA Requirements and Penalties for 2026

On March 24, 2026, HHS published a final rule adopting national HIPAA standards for health care claims attachments transactions and electronic signatures. The rule takes effect May 23, 2026, with a compliance deadline of May 26, 2028. It applies to all HIPAA covered entities that conduct standard electronic transactions and directly affects vendors, clearinghouses, and business associates supporting claims processing workflows. HHS has signaled it intends to resume progress toward finalizing the January 2021 HIPAA Privacy Rule proposed rule. A pending HHS rule would significantly update the HIPAA Security Rule, but HHS moved it to its Long-Term Actions agenda with July 2027 as the anticipated timeframe for final action. The existing Security Rule remains fully enforceable in the interim.

For 2026, HIPAA Tier 1 (lack of knowledge) violations carry a minimum penalty of $145 and a maximum of $73,011 per violation, with a calendar-year cap of $2,190,294. Tier 4 violations involving willful neglect that is not corrected within 30 days carry a minimum of $73,011 and a maximum of $2,190,294 per violation. The calendar-year cap is $2,190,294 for all tiers. OCR’s recent enforcement activity, including the seven investigations noted earlier and the OSF settlement, shows particular focus on risk analysis and timely breach notification.

Understand the Five Basic HIPAA Rules

The five main HIPAA rules are the Privacy Rule, the Security Rule, the Transactions and Code Sets Rule, the Enforcement Rule, and the Breach Notification Rule. Some sources list the Unique Identifiers Rule in place of the Breach Notification Rule. The Privacy Rule governs permitted uses and disclosures of PHI. The Security Rule governs ePHI safeguards through administrative, physical, and technical requirements. The Breach Notification Rule requires notification within 60 days of discovery. The Enforcement Rule governs civil money penalties and complaint resolution. The Transactions and Code Sets Rule governs electronic data interchange standards, including the claims attachment standards finalized in March 2026.

Who Falls Outside HIPAA Protection

HIPAA protections apply only to PHI held by covered entities and their business associates. Individuals whose health information is held by life insurers, workers’ compensation carriers, most schools and school districts, or most law enforcement agencies are generally outside HIPAA scope. Consumer-facing health and wellness wearables such as smartwatches, fitness trackers, and direct-to-consumer monitoring devices are typically not deployed by covered entities and generally are not business associates, so HIPAA does not apply to them. HIPAA applies to covered entities such as health care providers, health plans, and health care clearinghouses, and to their business associates. A cardiology practice functions as a covered entity, and a remote monitoring platform that receives cardiac device data on the practice’s behalf functions as a business associate.

Make This Checklist Operational With Rhythm360

Rhythm360 is a vendor-neutral, HIPAA-aligned, cloud-based platform built for the operational reality of cardiology remote monitoring. It consolidates data from Medtronic, Boston Scientific, Abbott, and Biotronik portals into a single source of truth. That consolidation eliminates the fragmented OEM portal workflow that creates ePHI data silos and compliance gaps. Rhythm360 provides bi-directional EHR integration with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7. It delivers auditable documentation, automated CPT code tracking for device-specific billing cycles, and a secure mobile app for reviewing transmissions and signing reports from anywhere. Practices using Rhythm360 have reported up to an 80% reduction in critical alert response times and up to a 300% increase in revenue capture through stronger billing documentation. Other platforms exist in this space, including Murj, Implicity, Rhythm Management Group, and Octagos.

Rhythm360
Rhythm360

The table below summarizes key capabilities to consider when evaluating a cardiac remote monitoring platform for HIPAA compliance and operational fit.

Attribute Rhythm360
Vendor-neutral OEM integration Medtronic, Boston Scientific, Abbott, Biotronik
EHR integration Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health via HL7
HIPAA compliance Cloud-based, HIPAA-aligned platform
Mobile access Secure mobile app for reviewing transmissions and signing reports

Request a Rhythm360 Platform Walkthrough

Download a Working Version of This Checklist

Use a structured checklist to turn these requirements into daily tasks. The HIPAA compliance checklist is available as a PDF and as a spreadsheet template, with every item tagged by owner and evidence so it can be assigned to a named individual and filed as an audit artifact on day one.

Get the HIPAA Checklist Template From Rhythm360

Frequently Asked Questions

How Do 2026 HIPAA Changes Affect Cardiology Practices?

HHS published a final rule on March 24, 2026, adopting national standards for health care claims attachments transactions and electronic signatures. The rule takes effect May 23, 2026, with a compliance deadline of May 26, 2028. It applies to all covered entities conducting standard electronic transactions and directly affects vendors and business associates supporting claims workflows. HHS has also signaled intent to finalize the January 2021 Privacy Rule proposed rule, which would shorten the individual access request response window from 30 to 15 days and ease care-coordination disclosure requirements. A proposed Security Rule overhaul remains delayed, with July 2027 as the current target for final action, so the existing Security Rule remains fully enforceable.

How Are HIPAA Penalties Structured in 2026?

HIPAA penalty tiers are adjusted annually for inflation. For 2026, Tier 1 violations involving lack of knowledge carry a minimum of $145 and a maximum of $73,011 per violation. Tier 2 violations involving reasonable cause carry a minimum of $1,461 and a maximum of $73,011. Tier 3 violations involving willful neglect corrected within 30 days carry a minimum of $14,602 and a maximum of $73,011. Tier 4 violations involving willful neglect that is not corrected within 30 days carry a minimum of $73,011 and a maximum of $2,190,294. The calendar-year cap is $2,190,294 for all tiers. OCR’s recent enforcement activity highlights the importance of documented risk analysis and timely breach notification.

How Do the Five HIPAA Rules Work Together?

The five main HIPAA rules are the Privacy Rule, the Security Rule, the Transactions and Code Sets Rule, the Enforcement Rule, and the Breach Notification Rule. The Privacy Rule governs permitted uses and disclosures of PHI, including the minimum necessary standard and individual rights of access. The Security Rule governs ePHI safeguards through administrative, physical, and technical requirements codified at 45 CFR Part 164 Subpart C. The Breach Notification Rule requires covered entities to notify affected individuals, HHS, and in some cases the media within 60 days of discovering a breach. The Enforcement Rule governs civil money penalties, complaint handling, and corrective action plans. The Transactions and Code Sets Rule governs electronic data interchange standards, including the claims attachment standards finalized in March 2026.

Which Data and Organizations Are Outside HIPAA?

HIPAA protections apply only to PHI held by covered entities such as health care providers, health plans, and health care clearinghouses, and by their business associates. Individuals whose health information is held by life insurers, workers’ compensation carriers, most schools and school districts, or most law enforcement agencies are generally not protected by HIPAA. Consumers using direct-to-consumer wearables, fitness apps, or health monitoring devices not deployed by a covered entity also fall outside HIPAA’s scope. In those cases, the FTC Health Breach Notification Rule and state laws such as Washington’s My Health My Data Act may apply instead.

Conclusion: Turn Your Checklist Into Daily Practice

A generic HIPAA compliance checklist leaves your cardiac remote monitoring program exposed. This checklist focuses on the reality of PHI moving through Medtronic, Boston Scientific, Abbott, and Biotronik portals, remote monitoring platforms, and RPM billing documentation for CPT 93297, 93298, and 99454. Every item is tagged by owner and evidence so it is audit-ready on day one. Rhythm360 helps make this checklist operational by consolidating OEM portal data, automating documentation, and delivering the auditable evidence trail that payer audits and OCR investigations expect.

Partner With Rhythm360 on HIPAA-Ready Remote Monitoring

Read Next

Related posts