Risk

11/16/2010
06:34 PM
50%
50%

Verizon Offers Free Security Credentials To Healthcare Professionals

The credentials meet Level 3 authentication requirements and allow healthcare providers to receive digitized health data from other clinicians securely.

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

Verizon Business is offering 2.3 million licensed healthcare professionals in the U.S. free medical identity credentials to make it easier for clinicians to securely share patient information via Verizon’s own Medical Data Exchange and other e-health platforms.

The credentials can allow healthcare providers to securely receive digitized health data from other clinicians via private inboxes accessed from a new Verizon Medical Data Exchange physician web portal.

Verizon’s multi-factored identity credentials meet Level 3 authentication requirements of the National Institute of Standards and Technology, said Steven Archer, head of Verizon Business Innovation Incubator Group. The security offering allows healthcare providers to comply with provisions of the HITECH Act that require "strong identity" credentials for accessing and sharing patient data starting in mid-2011.

Multi-factored identity credentialing authenticates a user’s ID through several factors, such as user name, password and software token. The Verizon ID credentials available to U.S. healthcare professionals allows up to 15 different form factors to be leveraged, said Archer.

There is currently no universal means of issuing multi-factored identity credentials to U.S. healthcare professionals. Making these security credentials available free to licensed healthcare providers such as doctors, nurse practitioners and physician assistants, will encourage the exchange of patient information, helping clinicians meet the HITECH Act’s meaningful use requirements, said Archer.

Verizon will begin issuing the ID credentials in January.

The multi-factored identity credentials also can be used as a single identity by healthcare professional to securely access other healthcare systems, databases and applications. “This provides a secure path enabling authentication capabilities on other platforms,” said Archer.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Locked device, Ha! I knew there was another way in.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2638
PUBLISHED: 2018-07-16
It was found that the REST API in Infinispan before version 9.0.0 did not properly enforce auth constraints. An attacker could use this vulnerability to read or modify data in the default cache or a known cache name.
CVE-2017-7468
PUBLISHED: 2018-07-16
In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was...
CVE-2018-13387
PUBLISHED: 2018-07-16
The IncomingMailServers resource in Atlassian JIRA Server before version 7.6.7, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3 and from version 7.10.0 before version 7.10.2 allows remote attackers to inject arbitrary HTML or ...
CVE-2018-14071
PUBLISHED: 2018-07-16
The Geo Mashup plugin before 1.10.4 for WordPress has insufficient sanitization of post editor and other user input.
CVE-2018-5229
PUBLISHED: 2018-07-16
The NotificationRepresentationFactoryImpl class in Atlassian Universal Plugin Manager before version 2.22.9 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the name of user submitted add-on names.