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

11/9/2010
12:21 PM
50%
50%

Identity Theft Reported By 33% Of Healthcare Organizations

Medical practices lag behind hospitals in nearly every measure of health IT implementation and security, reports HIMSS survey.

Health IT Boosts Patient Care, Safety
(click image for larger view)
Slideshow: Health IT Boosts Patient Care, Safety

A Healthcare Information and Management Systems Society (HIMSS) survey has revealed that 33% of respondents said their organization has had at least one known case of medical identity theft, and that some cases may never be reported.

In addition, only 17% of respondents working for medical practices said they were likely to report an instance of medical identity theft, compared to 38% of those working for a hospital.

These results come from the 2010 HIMSS Security Survey, a report sponsored by Intel and supported by the Medical Group Management Association. The report, published last week, interviewed 272 IT and security professionals at hospitals and medical practices about their readiness for the risks and security challenges they face as their healthcare organizations increasingly use digitized medical records.

The survey also showed that 75% of all respondents stated they perform a risk assessment at their organization, similar to the findings of HIMSS' 2009 survey. However, this year's survey includes a greater representation of medical practices, where 33% report that they do not conduct a risk analysis, compared to only 14% of those who work at a hospital.

The report emphasized that eligible hospitals and professionals seeking to qualify for reimbursements under the Centers for Medicare and Medicaid Services (CMS) electronic health record (EHR) incentive programs must meet meaningful use criteria that not only requires organizations to conduct a risk analysis, but also mandates that they correct all deficiencies identified.

"Without undergoing this process and then using the outcomes to change use of controls and modifications within policies and procedures, organizations will not qualify for the meaningful use incentives. At present, one-quarter of the sample population would not qualify for meaningful use as a result of this area," the report said.

Further highlights of the report include:

-- Hospital workers were more likely to report they had a chief security officer or chief information security officer in place, compared to those working in a medical practice. In fact, 17% of respondents working for medical practices indicated that they handled the security function exclusively by using external resources. None of the respondents from hospitals reported using external resources exclusively.

-- More than half of respondents from hospital organizations reported using two or more types of controls to manage data access, compared to 40% of respondents from medical practices.

-- Almost all of the respondents reported their organization actively works to determine the cause of security breaches, with two-thirds having a plan in place to respond to these threats. However, respondents from hospital organizations were more likely to report they worked to determine the cause of security breaches than respondents in medical practices.

-- About 85% of respondents said that their organization shares patient data in an electronic format. However, 83% of hospital respondents said they'll likely share more data in the future, compared to 77% of their medical practice counterparts.

-- Mobile device encryption, e-mail encryption and single sign-on were most frequently identified by respondents as technologies not currently used at their organizations, but were planned for future implementation. Of those not currently using these technologies, hospitals said they are more likely than medical practices to say they'll install them in the future.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
MoviePass Leaves Credit Card Numbers, Personal Data Exposed Online
Kelly Sheridan, Staff Editor, Dark Reading,  8/21/2019
New FISMA Report Shows Progress, Gaps in Federal Cybersecurity
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7617
PUBLISHED: 2019-08-22
When the Elastic APM agent for Python versions before 5.1.0 is run as a CGI script, there is a variable name clash flaw if a remote attacker can control the proxy header. This could result in an attacker redirecting collected APM data to a proxy of their choosing.
CVE-2019-14751
PUBLISHED: 2019-08-22
NLTK Downloader before 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction.
CVE-2019-9153
PUBLISHED: 2019-08-22
Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to forge signed messages by replacing its signatures with a "standalone" or "timestamp" signature.
CVE-2019-9154
PUBLISHED: 2019-08-22
Improper Verification of a Cryptographic Signature in OpenPGP.js <=4.1.2 allows an attacker to pass off unsigned data as signed.
CVE-2019-9155
PUBLISHED: 2019-08-22
A cryptographic issue in OpenPGP.js <=4.2.0 allows an attacker who is able provide forged messages and gain feedback about whether decryption of these messages succeeded to conduct an invalid curve attack in order to gain the victim's ECDH private key.