89% of doctors, whilst trying to deliver better and more efficient care, inadvertently break the law and risk huge fines when using their phone for clinical photography. Support doctors and hospitals by giving them PicSafe®. They can comply with privacy regulations while helping save lives and reduce healthcare costs.
Using the default camera app, or the camera built in to messaging apps, almost always results in a breach of privacy regulations.
Express consent isn't documented
Photos are stored on your phone
Photos are auto-uploaded to iCloud
Photos aren't de-identified properly
Lose your phone, lose patient data
Sent insecurely via email or SMS
Doctors often don't get consent, and when they do, they don't record it properly. A whopping 82% of the time, doctors don't document consent when taking a photo. A study among dermatologists revealed that only 2% obtained written consent! While 46% received verbal consent, they failed to document this.
See the "Can't I just infer consent? FAQ for details.
In a 2016 study, 73% of doctors admitted to storing clinical photos among their private photos, while 26% admitted to accidentally having shown a clinical photograph on their phone to friends or family! That's an instant privacy breach.
Even if a doctor "deletes" a photo, on iOS devices it remains in "deleted items" folder for 40 days, and on Android devices it remains in the "trash" folder for 60 days. See the "How do I delete clinical photos I have stored on my photos FAQ.
There are two ways in which you can inadvertently be sending data cross borders:
You should never have patient data on Apple or Google's servers.
Many operate under the assumption that they can merely de-identify the photos by not showing the patients face; however, this is not sufficient. Photos taken on the default camera app (or the camera within messaging apps) contain all sorts of metadata that can be used to identify the patient. See "Am I okay to use the default camera app if I de-identify photos?" in the FAQs for more.
Fortunately, all new iOS and Android phones have some form of a passcode, or facial recognition turned on by default. Unfortunately, between 11% and 15% of iOS devices, and around 33% of Android devices don't have it turned on.
While newer versions of iOS and Android push people into using passcodes, fingerprint scanners or face recognition, sometimes (on some Android devices) these methods are quite easy to "hack". Whether such measures are considered "reasonable" has not been legally tested.
With off-the-shelf data recovery tools, one can recover data on "locked" Android devices reasonably easily.
Sending clinical photos by email, text message, and even WhatsApp is widespread, but it should not be happening!
Email is inherently insecure. Unless you're using a special email encryption service, it's like sending a postcard. Any number of people can view it along the way.
See the Is Sending patient data via email safe? FAQ for more.
Simply put, text messaging is not secure.
See the Is Sending patient data via text message safe? FAQ for more.
Anecdotally, many doctors are using WhatsApp to share patient data.
See the Is Sending patient data via WhatsApp safe? FAQ for more.
"Obtain patient consent in ALL cases before taking clinical photographs"
PicSafe® provides various integration options into third-party medical record systems and storage services.
This allows automatic entry of photos into the appropriate patient's medical record.
If your practice, clinic, or hospital is using a third-party medical record system, to fully automate the process, you may have to lobby the vendor and/or your IT department to provide access. Understandably, access is locked down by default. Even if you can't initially automate the process, PicSafe® provides tools for making it far easier to add photos than when using the default camera on your phone.
For more, see "How do I get photos into the medical record?" in the FAQs.
Use of the camera on phones for clinical photography is so widespread, and the benefits so broadly accepted that it can be considered "standard of care". That means you're...
PicSafe® also uses CBC mode, password stretching with PBKDF2, password salting, random IV, and encrypt-then-hash HMAC. There are no known cases of this encryption having ever been "cracked".
PicSafe® has undertaken independent Vulnerability Assessment and Penetration Testing (VAPT). See the PicSafe® Security page for more.