IP Library › Granted Patent US 12,243,655
Granted Patent B2
US 12,243,655 · App. 18/446,961 · Granted Mar 4, 2025

System, method and apparatus for real-time access to networked radiology data

Inventor: Fawzi Shaya (Wixom, MI)
Assignee: Smart Solutions IP, LLC
G16H80/00A61B5/0022A61B5/746G06F3/0482G16H30/20G16H40/20H04L63/0428H04W12/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,243,655
App. No.
18/446,961
Granted
Mar 4, 2025
Kind
B2
Abstract

A method for generating DICOM images as part of a real-time virtual medical consultation includes receiving, by a handheld patient device associated with a patient, a DICOM image associated with the patient generated by a diagnostic device, encrypting, by the handheld patient device, the DICOM image and linking the encrypted DICOM image to a unique patient identifier associated with the patient, wherein the handheld patient device is one of a tablet computer and a smartphone, and transmitting, by the handheld patient device, the encrypted DICOM image to a server configured to provide a DICOM viewer option within a secure telemedicine platform accessible by a medical professional and executed by the server.

Claims (41)

1. A method comprising:

receiving, by a server, an encrypted DICOM image from a handheld computing device that is encrypted by the handheld computing device and linked to a unique patient identifier associated with a patient by the handheld computing device, the handheld computing device being one of a tablet computer and a smartphone;

receiving, by the server, an entered patient identifier from a healthcare provider computing device associated with a healthcare provider;

comparing, by the server, the entered patient identifier to the unique patient identifier;

restricting, by the server, the healthcare provider computing device from retrieving the encrypted DICOM image if the entered patient identifier is not equal to the unique patient identifier; and

permitting, by the server, the healthcare provider computing device to retrieve the encrypted DICOM image if the entered patient identifier is equal to the unique patient identifier.

2. The method of claim 1 , wherein the DICOM image is generated by a diagnostic device.

3. The method of claim 1 , wherein the unique patient identifier is comprised of one of a numeric identifier or an alphanumeric identifier.

4. The method of claim 1 , wherein the handheld computing device receives the DICOM image from a diagnostic device.

5. The method of claim 4 , wherein the diagnostic device is one of an electrocardiograma pulse oximeter, a blood pressure cuff, a spirometer, a sphygmomanometer, a weight scale, a stethoscope, a blood chemistry analyzer, a microscope, an ultrasounds probe, a glucometer, a Horus Scope, a prothrombin time and international normalized ratio (PT/INR) machine, a medication station, an abdominal probe, a vascular access probe, an endocavity probe, an ophthalmology probe, a proscope, a thermometer, and a remotely-controlled 360 degree high definition camera.

6. The method of claim 1 , wherein the handheld computing device is associated with the patient.

7. The method of claim 1 , wherein the DICOM image is encrypted using a hypertext transfer protocol secure method.

8. The method of claim 1 , wherein the server is remote from the healthcare provider computing device.

9. A system comprising:

a handheld computing device that receives a DICOM image from a diagnostic device, encrypts the DICOM image, and links the DICOM image to a unique patient identifying associated with a patient, the handheld computing device being one of a tablet computer and a smartphone; and

a server comprising:

data processing hardware; and

memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:

receiving the encrypted DICOM image from the handheld computing device;

receiving an entered patient identifier from a healthcare provider computing device associated with a healthcare provider;

comparing the entered patient identifier to the unique patient identifier;

restricting the healthcare provider computing device from retrieving the encrypted DICOM image if the entered patient identifier is not equal to the unique patient identifier; and

permitting the healthcare provider computing device to retrieve the encrypted DICOM image if the entered patient identifier is equal to the unique patient identifier.

10. The system of claim 9 , wherein the handheld computing device is remote from the diagnostic device.

11. The system of claim 9 , wherein the diagnostic device is one of an electrocardiograma pulse oximeter, a blood pressure cuff, a spirometer, a sphygmomanometer, a weight scale, a stethoscope, a blood chemistry analyzer, a microscope, an ultrasounds probe, a glucometer, a Horus Scope, a prothrombin time and international normalized ratio (PT/INR) machine, a medication station, an abdominal probe, a vascular access probe, an endocavity probe, an ophthalmology probe, a proscope, a thermometer, and a remotely-controlled 360 degree high definition camera.

12. The system of claim 9 , wherein the unique patient identifier is comprised of one of a numeric identifier or an alphanumeric identifier.

13. The system of claim 9 , wherein the server is part of a cloud computing system.

14. The system of claim 9 , wherein the server is remote from the healthcare provider computing device.

15. A server comprising:

data processing hardware; and

memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:

receiving, by a server, an encrypted DICOM image from a handheld computing device that is encrypted by the handheld computing device and linked to a unique patient identifier associated with a patient by the handheld computing device, the handheld computing device being one of a tablet computer and a smartphone;

receiving, by the server, an entered patient identifier from a healthcare provider computing device associated with a healthcare provider;

comparing, by the server, the entered patient identifier to the unique patient identifier;

restricting, by the server, the healthcare provider computing device from retrieving the encrypted DICOM image if the entered patient identifier is not equal to the unique patient identifier; and

permitting, by the server, the healthcare provider computing device to retrieve the encrypted DICOM image if the entered patient identifier is equal to the unique patient identifier.

16. The server of claim 15 , wherein the unique patient identifier is comprised of one of a numeric identifier or an alphanumeric identifier.

17. The server of claim 15 , wherein the DICOM image is generated by a diagnostic device.

18. The server of claim 17 , wherein the diagnostic device is one of an electrocardiograma pulse oximeter, a blood pressure cuff, a spirometer, a sphygmomanometer, a weight scale, a stethoscope, a blood chemistry analyzer, a microscope, an ultrasounds probe, a glucometer, a Horus Scope, a prothrombin time and international normalized ratio (PT/INR) machine, a medication station, an abdominal probe, a vascular access probe, an endocavity probe, an ophthalmology probe, a proscope, a thermometer, and a remotely-controlled 360 degree high definition camera.

19. The server of claim 15 , wherein the server is part of a cloud computing system.

20. The server of claim 15 , wherein the server is remote from the healthcare provider computing device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2025
From: SHAYA, MARY ELIAS
To: SMART SOLUTIONS IP, LLC
Reel/Frame 071006/0435 →
Continuity (10)
Continuation 18146140 · Dec 23, 2022
Continuation 17122474 · Dec 15, 2020
Continuation 16990074 · Aug 11, 2020
Continuation 16818243 · Mar 13, 2020
Continuation 16209064 · Dec 4, 2018
Continuation In Part 15784876 · Oct 16, 2017
Continuation In Part 15158007 · May 18, 2016
Continuation In Part 13165052 · Jun 21, 2011
Provisional Application 61369461 · Jul 30, 2010
Related Publication 20240186025A1 · Jun 6, 2024
References Cited (84)
US 5961446A · Beller et al. · 1999 [cited by applicant]
US 5987519A · Peifer et al. · 1999 [cited by applicant]
US 5997476A · Brown · 1999 [cited by applicant]
US 6038469A · Karlsson et al. · 2000 [cited by applicant]
US 6064968A · Schanz · 2000 [cited by applicant]
US 6112224A · Peifer et al. · 2000 [cited by applicant]
US 6366871B1 · Geva · 2002 [cited by applicant]
US 6369847B1 · James et al. · 2002 [cited by applicant]
US 6409660B1 · Sjoqvist · 2002 [cited by applicant]
US 6610010B2 · Sjoqvist · 2003 [cited by applicant]
US 6640239B1 · Gidwani · 2003 [cited by applicant]
US 6820057B1 · Loch et al. · 2004 [cited by applicant]
US 7158861B2 · Wang et al. · 2007 [cited by applicant]
US 7222054B2 · Geva · 2007 [cited by applicant]
US 7232220B2 · Franz et al. · 2007 [cited by applicant]
US 7257158B1 · Figueredo et al. · 2007 [cited by applicant]
US 7283153B2 · Provost et al. · 2007 [cited by applicant]
US 7412396B1 · Haq · 2008 [cited by applicant]
US 7425977B2 · Sakai · 2008 [cited by applicant]
US 7520611B2 · Franz et al. · 2009 [cited by applicant]
US 7618368B2 · Brown · 2009 [cited by applicant]
US 7624028B1 · Brown · 2009 [cited by applicant]
US 7650291B2 · Rosenfeld et al. · 2010 [cited by applicant]
US 7657444B2 · Yu · 2010 [cited by applicant]
US 7761261B2 · Shmueli et al. · 2010 [cited by applicant]
US 7761312B2 · Brown · 2010 [cited by applicant]
US 7815282B2 · Hibbard et al. · 2010 [cited by applicant]
US 9210200B1 · Chapweske et al. · 2015 [cited by applicant]
US 20010044586A1 · Ferek-Petric · 2001 [cited by applicant]
US 20020065682A1 · Goldenberg · 2002 [cited by applicant]
US 20020091659A1 · Beaulieu et al. · 2002 [cited by applicant]
US 20020118809A1 · Eisenberg · 2002 [cited by applicant]
US 20030028399A1 · Davis et al. · 2003 [cited by applicant]
US 20030069752A1 · LeDain et al. · 2003 [cited by applicant]
US 20040078219A1 · Kaylor et al. · 2004 [cited by applicant]
US 20040240752A1 · Dobbs · 2004 [cited by examiner]
US 20050246185A1 · Brown · 2005 [cited by applicant]
US 20060036134A1 · Tarassenko et al. · 2006 [cited by applicant]
US 20060074709A1 · McAllister · 2006 [cited by applicant]
US 20060122466A1 · Nguyen-Dobinsky et al. · 2006 [cited by applicant]
US 20060143043A1 · McCallie et al. · 2006 [cited by applicant]
US 20060173267A1 · Chiang et al. · 2006 [cited by applicant]
US 20060230072A1 · Partovi · 2006 [cited by examiner]
US 20060271400A1 · Clements et al. · 2006 [cited by applicant]
US 20070016449A1 · Cohen et al. · 2007 [cited by applicant]
US 20070073520A1 · Bleines · 2007 [cited by applicant]
US 20070100666A1 · Stivoric et al. · 2007 [cited by applicant]
US 20070130287A1 · Kumar et al. · 2007 [cited by applicant]
US 20070192140A1 · Gropper · 2007 [cited by examiner]
US 20070192910A1 · Vu et al. · 2007 [cited by applicant]
US 20080095079A1 · Barkley et al. · 2008 [cited by applicant]
US 20080113621A1 · Parthasarathy · 2008 [cited by applicant]
US 20080002674A1 · Ferren et al. · 2008 [cited by applicant]
US 20080275311A1 · Haq · 2008 [cited by applicant]
US 20090012373A1 · Raij et al. · 2009 [cited by applicant]
US 20090093688A1 · Mathur · 2009 [cited by applicant]
US 20090112070A1 · Lin et al. · 2009 [cited by applicant]
US 20090146822A1 · Soliman · 2009 [cited by applicant]
US 20090149767A1 · Rossetti · 2009 [cited by applicant]
US 20090167842A1 · Sandhu · 2009 [cited by applicant]
US 20090240525A1 · Sadler et al. · 2009 [cited by applicant]
US 20090264712A1 · Baldus et al. · 2009 [cited by applicant]
US 20090313076A1 · Schoenberg · 2009 [cited by applicant]
US 20100030580A1 · Salwan · 2010 [cited by applicant]
US 20100079281A1 · Drake · 2010 [cited by applicant]
US 20100128104A1 · Fabregat et al. · 2010 [cited by applicant]
US 20100137693A1 · Porras et al. · 2010 [cited by applicant]
US 20100205541A1 · Rapaport et al. · 2010 [cited by applicant]
US 20100325209A1 · Thapa · 2010 [cited by applicant]
US 20110010200A1 · Firozvi et al. · 2011 [cited by applicant]
US 20110015494A1 · Spaulding · 2011 [cited by applicant]
US 20110106557A1 · Gazula · 2011 [cited by applicant]
US 20110126127A1 · Mariotti et al. · 2011 [cited by applicant]
US 20110145016A1 · Eshraghian · 2011 [cited by examiner]
US 20110251960A1 · Holla · 2011 [cited by examiner]
US 20140244296A1 · Linn et al. · 2014 [cited by applicant]
US 20150149565A1 · Ahmed · 2015 [cited by applicant]
US 20160037057A1 · Westin et al. · 2016 [cited by applicant]
US 20180247029A1 · Fish et al. · 2018 [cited by applicant]
US 20190356479A1 · Grimme · 2019 [cited by applicant]
WO 0147418A1 · 2001 [cited by applicant]
S. Mohammed, J. Fiaidhi and L. Yang, “Developing multitier lightweight techniques for protecting medical images within ubiquitous environments,” Proceedings. Second Annual Conference on Communication Networks and Servic… [cited by examiner]
Bluegiga Technologies “Bluetooth® Health Device Profile” Aug. 2009, https://www.semiconductorstore.com/pdf/NewSite/Bluegiga /Bluegiga <https://www.semiconductorstore.com/pdf/NewSite/Bluegiga/Bluegiga> Bluetooth Health D… [cited by applicant]
“Application of Portable CDA for Secure Clinical-document Exchange”, Huang, et al., J Med Syst (2010) 34:531-539 (Year: 2010). [cited by applicant]