Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

HHS Committee Sanctions Health IT Security Proposal

Contentious debate over how patients can opt out of data sharing nearly derailed the Department of Health and Human Services group's recommendations.




Slideshow: Who's Who In Healthcare IT
(click for larger image and for full photo gallery)
Devan McGraw and Paul Egerman, chair and co-chair, respectively, of the Department of Health and Human Services' Health IT Policy Committee's privacy and security team, entered the full committee's August meeting looking for approval of the letter and recommendations they put together over the summer. And while they got that approval in the end, it was only after more than 30 minutes of contentious debate, led on the other side by Neal Calman, MD, president and CEO of the Institute for Family Health.

The debate broke down as follows: among other things, the recommendations stated that if a provider uses a health information exchange (HIE) to share data that meets meaningful use requirements, the provider must also offer patients a choice of opting out of that exchange. As an alternative, the provider would be required to offer direct point-to-point exchange with any other parties needing to receive that patient's data.

Calman said repeatedly this would constitute an undue burden on providers and that they should be able to inform patients of how their practice shares data -- perhaps through an HIE -- and then leave the decision of whether or not to patronize that practice with the patient.

"So you are saying I can opt out of using any exchanges, but I can't say to a patient, 'This is the way we do business and, if you don't like it, you have to go elsewhere'? I can do that for every other aspect of my practice -- the way we deal with emergency calls, my hours, whether I use nurse practicioners -- but if someone wants to opt out of my data exchange program, I have to offer them another alternative?" asked Calman.

McGraw, director of the Center for Democracy & Technology, Egerman, software entrepreneur, and Christine Bechtel, VP of the National Partnership for Women & Families, gave spirited defenses of the recommendations. Eventually, the debate became mired down in the minutiae of terms like health information organization (HIO) and organized health care arrangement (OHCA), with each side questioning and stipulating what those terms meant and how each was treated under both the law and meaningful use. Terms like "business associate agreement" and "covered entity" were also discussed, debated and parsed.

The conversation even touched on the idea that the governance composition of an HIE might place it under different legal requirements for sharing information. For example, if providers participate in an HIE composed only of other providers, they would need less additional consent from patients for participation, but if the governance included non-providers or non-covered entities, other consent "triggers" could be tripped.

Though Calman, Judy Faulkner (CEO, Epic), Michael Klag (Johns Hopkins University, Bloomberg School of Public Health), and Marc Probst (CIO, InterMountain Healthcare) all expressed concerns during the debate, none voted no or abstained. Thus, the recommendations passed with the full, though seemingly lukewarm, approval of the full committee.

Anthony Guerra is the founder and editor of healthsystemCIO.com, a site dedicated to serving the strategic information needs of healthcare CIOs. He can be reached at [email protected]

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
News
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
News
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
News
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: "Elon, I think our cover's been blown."
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27400
PUBLISHED: 2021-04-22
HashiCorp Vault and Vault Enterprise Cassandra integrations (storage backend and database secrets engine plugin) did not validate TLS certificates when connecting to Cassandra clusters. Fixed in 1.6.4 and 1.7.1
CVE-2021-29653
PUBLISHED: 2021-04-22
HashiCorp Vault and Vault Enterprise 1.5.1 and newer, under certain circumstances, may exclude revoked but unexpired certificates from the CRL. Fixed in 1.5.8, 1.6.4, and 1.7.1.
CVE-2021-30476
PUBLISHED: 2021-04-22
HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Vault’s GCP auth method. Fixed in 2.19.1.
CVE-2021-22540
PUBLISHED: 2021-04-22
Bad validation logic in the Dart SDK versions prior to 2.12.3 allow an attacker to use an XSS attack via DOM clobbering. The validation logic in dart:html for creating DOM nodes from text did not sanitize properly when it came across template tags.
CVE-2021-27736
PUBLISHED: 2021-04-22
FusionAuth fusionauth-samlv2 before 0.5.4 allows XXE attacks via a forged AuthnRequest or LogoutRequest because parseFromBytes uses javax.xml.parsers.DocumentBuilderFactory unsafely.