Skip to Main Content

Washington is cracking down on the technology running behind the scenes in health care following a debilitating cyberattack on a health care payments processing company — and it could have major implications for hospitals and the vendors selling crucial IT.

In the weeks since a ransomware attack on Change Healthcare brought pharmacy and hospital payments across the country to a halt, policymakers and lobbyists have raced to cobble together strategies for averting future attacks, ranging from tying federal aid to minimum cybersecurity requirements to new voluntary standards spun up by public-private partnerships.

advertisement

The Change Healthcare attack exposed how security vulnerabilities at a single company could bring down critical technology infrastructure that a vast majority of health care providers and health insurers rely on every day. In the aftermath, federal regulators have come under fire for not being prepared and not acting soon enough, with some lawmakers calling for “tough, mandatory cybersecurity standards for the health care industry” including regular audits.

STAT+ Exclusive Story

STAT+

This article is exclusive to STAT+ subscribers

Unlock this article — and get additional analysis of the technologies disrupting health care — by subscribing to STAT+.

Already have an account? Log in

Already have an account? Log in

Monthly

$39

Totals $468 per year

$39/month Get Started

Totals $468 per year

Starter

$30

for 3 months, then $39/month

$30 for 3 months Get Started

Then $39/month

Annual

$399

Save 15%

$399/year Get Started

Save 15%

11+ Users

Custom

Savings start at 25%!

Request A Quote Request A Quote

Savings start at 25%!

2-10 Users

$300

Annually per user

$300/year Get Started

$300 Annually per user

View All Plans

Get unlimited access to award-winning journalism and exclusive events.

Subscribe

STAT encourages you to share your voice. We welcome your commentary, criticism, and expertise on our subscriber-only platform, STAT+ Connect

To submit a correction request, please visit our Contact Us page.