By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
Health Works CollectiveHealth Works CollectiveHealth Works Collective
  • Health
    • Mental Health
  • Policy and Law
    • Global Healthcare
    • Medical Ethics
  • Medical Innovations
  • News
  • Wellness
  • Tech
Search
© 2023 HealthWorks Collective. All Rights Reserved.
Reading: Tactical Mobile Device Security Measures to Meet HIPAA Compliance
Share
Notification Show More
Font ResizerAa
Health Works CollectiveHealth Works Collective
Font ResizerAa
Search
Follow US
  • About
  • Contact
  • Privacy
© 2023 HealthWorks Collective. All Rights Reserved.
Health Works Collective > eHealth > Medical Records > Tactical Mobile Device Security Measures to Meet HIPAA Compliance
Medical RecordsMobile Health

Tactical Mobile Device Security Measures to Meet HIPAA Compliance

onlinetech
onlinetech
Share
6 Min Read
Smartphone Security
SHARE

Mobile devices are becoming ubiquitous in the healthcare industry – from quickly filing e-prescriptions to collecting and sending patient health information (PHI) directly to an EHR/EMR (electronic health or medical record) system, the use of smartphones, tablets and other portable devices is changing the quality of patient care for the better across the nation.

Mobile devices are becoming ubiquitous in the healthcare industry – from quickly filing e-prescriptions to collecting and sending patient health information (PHI) directly to an EHR/EMR (electronic health or medical record) system, the use of smartphones, tablets and other portable devices is changing the quality of patient care for the better across the nation.

But when it comes to securing your mobile devices and meeting strict HIPAA compliance standards, physicians and other healthcare professionals may not realize the security precautions they need to take to prevent a data breach and HIPAA violation.

One example of recommended best practices can be found in Yale University’s HIPAA guide for mobile device security (intended for its covered components, such as the Schools of Medicine, Health Services, etc.) including:

More Read

data security
More New PCI DSS 3.0 Requirements: Control Access, Two-Factor Authentication and POS Security
Perpetuating the Steve Jobs Legacy
How a VNA Unifies Clinical Data Throughout an Enterprise
Wearable Computers, Biosensors and Sanity
The Importance Of Medical Labels And Supplement Labels
Smartphone Security

Smartphone Security

  • Passwords – Yale recommends users have a password with a minimum of four characters. They also recommend implementing a lock-out setting after 10 failed attempts to enter a password.
  • Encryption – Data must be encrypted at rest and in transit, including backup data.
  • Message Storage – The storage limit is capped at 200 messages at one time or 14 days of messages.
  • Applications – All applications that create, store, access, send or receive PHI must meet HIPAA security standards. Yale also has a Security Design Review service that can check out any custom developed apps for compliance (although the website really needs to update its language regarding Application Service Providers and the required SAS 70 Type II documentation – SSAE 16/SOC 1 have since replaced the SAS 70 standard).
  • Software – Apply security updates frequently and use the most recent OS available.
  • Remote management and Tracking – Mobile devices must have a remote deletion and tracking feature or you have to sign up for a service that can wipe it if it is stolen or lost. For the iPhone, that can mean installing the Find My iPhone app. Yale provides a comprehensive  guide to locating and wiping iPhones, Blackberrys (read this, grammar nerds) and other smartphone devices.
  • No Circumvention – This refers to protecting the security of mobile devices by prohibiting users from using unauthorized software and hardware, etc.
  • Wireless – Yale requires the use of VPN services when using digital cellular to connect to the Yale network and if not using one of Yale’s cell carriers. For Bluetooth™, passwords or PINs are required to secure connections.
  • Thumb drives and Other Portable Media Devices – Storing PHI is prohibited unless the devices meet the Yale encryption standards.
  • File-sharing – Users that need to send or exchange PHI outside of the network have to use a secure file transfer tool, or secure file transfer protocol (SFTP).
  • Servers – Naturally Yale recommends using their IT department-owned servers to store all PHI. Their requirements are aligned with the HIPAA breach notification rules that require reports of data breaches if it affects 500 or more patients.
  • Privacy Filters – Computer screens that display PHI must have privacy filters installed if they’re viewable by the public.
  • Device Disposal – When upgrading or getting rid of your mobile devices, you must first securely destroy or delete PHI.
  • Email – Configuring email accounts to auto-forward to a non-Yale email account is prohibited if the email account may have PHI in its inbox.

This is a great start when it comes to documenting and specifying the security measures your organization needs to take, but don’t just copy and paste these policies. Every company has different needs that require a customized plan to keep PHI safe.

Also, not every device is created equal. Last year, BGR.com found a major security flaw in the security lock design of AT&T’s Samsung Galaxy S II cellphone that left it open to a simple workaround, allowing users to bypass the PIN or unlock feature. If you tap the lock button to wake it, wait for it to time out and go black, then tap the lock button again, the phone is suddenly accessible and the PIN rendered useless.

Make sure you know your device and its features, and deploy similar security measures as found above to stay compliant even on the go.

For more on IT security and best practices, read HIPAA Compliant IT Security and Best Practices. Or for more about smartphone security, read Mobile Security: How Safe is Your Data?

References:
Yale University’s HIPAA Security Updates and Reminders
Major Security Flaw Lets Anyone Bypass AT&T Samsun Galaxy S II Security

  

TAGGED:HIPAA violationsmobile devices
Share This Article
Facebook Copy Link Print
Share

Stay Connected

1.5kFollowersLike
4.5kFollowersFollow
2.8kFollowersPin
136kSubscribersSubscribe

Latest News

contamination
Batch Failures And The Hidden Costs Of Contamination
Health Infographics
October 21, 2025
Medication Management For Seniors
Simplifying Medication Management For Seniors
Infographics Senior Care
October 21, 2025
Guide To Pursuing a Career in Nursing as a Foreigner in the USA
Collaboration Is the Prescription for Better Patient Care
Health
October 20, 2025
Epidemiological Health Benefits
Personal and Epidemiological Health Benefits of Blood Pressure Management
Health
October 13, 2025

You Might also Like

Mobile Health

3 Factors Fueling Growth in Mobile Health Apps

January 11, 2012
Patient Record on Parking
Mobile HealthRemote DiagnosticsTechnology

The Case for Patient Video in Doctors Visits: Take a Selfie and Call Me In the Morning

August 28, 2015
BusinessMedical RecordsNews

Stage 2 of Meaningful Use Delayed to 2014

December 2, 2011

Wanted: Electronic Health Records

August 23, 2012
Subscribe
Subscribe to our newsletter to get our newest articles instantly!
Follow US
© 2008-2025 HealthWorks Collective. All Rights Reserved.
  • About
  • Contact
  • Privacy
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?