IP Library Granted Patent US 12,339,994
Granted Patent B2
US 12,339,994 · App. 18/308,375 · Granted Jun 24, 2025

System and method for managing access control of sensitive data

Inventors: Dharmesh M. Patel (Round Rock, TX); Prem Pradeep Motgi (Austin, TX); Manpreet Singh Sokhi (Santa Clara, CA)
Assignee: Dell Products L.P.
G06F21/6245
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,339,994
App. No.
18/308,375
Granted
Jun 24, 2025
Kind
B2
Abstract

Methods and systems for managing access and control of data are disclosed. To manage access and control, data management system may require registration and verification of devices associated with an individual or other individuals to which control over access may be granted. Data management system may vest control over access to data to the device associated with the individual for which data is stored and progressively vest control over access to data to other devices associated with other individuals as an increasing amount of information indicating the lack of capacity of the individual to authorize access to data.

Claims (104)

1. A method for managing access to privately held health information, the method comprising:

obtaining a request for medical data for a patient, the medical data being part of the privately held health information;

in response to obtaining the request:

identifying a patient device that is designated by the patient;

performing a first consent resolution action with the patient device to attempt to gain a first authorization to disclose the medical data;

in a first instance of the first consent resolution action where the first authorization to disclose the medical data was not obtained:

identifying a verified designee device that is designated by the patient;

performing a second consent resolution action with the verified designee device to attempt to gain a second authorization to disclose the medical data;

in a first instance of the second consent resolution action where the second authorization to disclose the medical data was not obtained:

identifying a verified provider designee device that is designated by the patient;

performing a third consent resolution action with the verified provider designee device to attempt to gain a third authorization to disclose the medical data; and

in a first instance of the third consent resolution action where the third authorization to disclose the medical data was not obtained:

 denying access to the medical data to service the request; and

in a second instance of the third consent resolution action where the third authorization to disclose the medical data was obtained:

 providing the medical data to service the request.

2. The method of claim 1 , wherein performing the third consent resolution action comprises:

requesting the third authorization to disclose the medical data, the request being made to the verified provider designee device;

obtaining a first response indicating whether the third authorization is partially granted by the verified provider designee device;

in an instance of the first response where the third authorization is partially granted by the verified provider designee device:

identifying a second provider designee device designated by the verified provider designee device;

obtaining a second response indicating whether the third authorization is also partially granted by the second provider designee device; and

determining whether the third authorization to disclose the medical data has been granted based on the first response and the second response.

3. The method of claim 2 , wherein verified provider designee device is associated with a primary care physician for the patient, and the second provider designee device is associated with another professional that provides care to the patient.

4. The method of claim 3 , wherein performing the first consent resolution action comprises:

requesting the first authorization to disclose the medical data, the request being made to the patient device;

obtaining a third response indicating whether the first authorization is granted by the patient device; and

determining whether the first authorization to disclose the medical data has been granted based on the third response.

5. The method of claim 4 , wherein performing the second consent resolution action comprises:

requesting the second authorization to disclose the medical data, the request being made to the verified designee device;

obtaining a fourth response indicating whether the second authorization is granted by the verified designee device; and

determining whether the second authorization to disclose the medical data has been granted based on the fourth response.

6. The method of claim 5 , further comprising:

in a second instance of the first consent resolution action where the first authorization to disclose the medical data was obtained:

providing the medical data to service the request.

7. The method of claim 6 , further comprising:

in a second instance of the second consent resolution action where the second authorization to disclose the medical data was obtained:

providing the medical data to service the request.

8. The method of claim 1 , wherein the privately held health information is stored in a private data management system.

9. The method of claim 8 , wherein the request for medical data is obtained from a data consumer system, the data consumer system providing data management services for a healthcare service provider that provides healthcare services for the patient, and the private data management system not being operated for the healthcare service provider.

10. The method of claim 9 , further comprising:

identifying, based on the request, a potential condition that may be afflicting the patient; and

identifying, based on the potential condition, at least one portion of data managed by the data management system that is usable in part for diagnosis of the potential condition.

11. The method of claim 10 , wherein identifying the at least one portion of the data comprises:

performing a look up using a type of the potential condition as a key to obtain an identifier for the at least one portion of the data,

wherein the data is stored in a searchable format keyed to different types of potential conditions.

12. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations for managing access to privately held health information, the operations comprising:

obtaining a request for medical data for a patient, the medical data being part of the privately held health information;

in response to obtaining the request:

identifying a patient device that is designated by the patient;

performing a first consent resolution action with the patient device to attempt to gain a first authorization to disclose the medical data;

in a first instance of the first consent resolution action where the first authorization to disclose the medical data was not obtained:

identifying a verified designee device that is designated by the patient;

performing a second consent resolution action with the verified designee device to attempt to gain a second authorization to disclose the medical data;

in a first instance of the second consent resolution action where the second authorization to disclose the medical data was not obtained:

identifying a verified provider designee device that is designated by the patient;

performing a third consent resolution action with the verified provider designee device to attempt to gain a third authorization to disclose the medical data; and

in a first instance of the third consent resolution action where the third authorization to disclose the medical data was not obtained:

 denying access to the medical data to service the request; and

in a second instance of the third consent resolution action where the third authorization to disclose the medical data was obtained:

 providing the medical data to service the request.

13. The non-transitory machine-readable medium of claim 12 , wherein performing the third consent resolution action comprises:

requesting the third authorization to disclose the medical data, the request being made to the verified provider designee device;

obtaining a first response indicating whether the third authorization is partially granted by the verified provider designee device;

in an instance of the first response where the third authorization is partially granted by the verified provider designee device:

identifying a second provider designee device designated by the verified provider designee device;

obtaining a second response indicating whether the third authorization is also partially granted by the second provider designee device; and

determining whether the third authorization to disclose the medical data has been granted based on the first response and the second response.

14. The non-transitory machine-readable medium of claim 13 , wherein verified provider designee device is associated with a primary care physician for the patient, and the second provider designee device is associated with another professional that provides care to the patient.

15. The non-transitory machine-readable medium of claim 14 , wherein performing the first consent resolution action comprises:

requesting the first authorization to disclose the medical data, the request being made to the patient device;

obtaining a third response indicating whether the first authorization is granted by the patient device; and

determining whether the first authorization to disclose the medical data has been granted based on the third response.

16. The non-transitory machine-readable medium of claim 12 , wherein the operations further comprise:

identifying, based on the request, a potential condition that may be afflicting the patient; and

identifying, based on the potential condition, at least one portion of data managed by a data management system that is usable in part for diagnosis of the potential condition.

17. A data processing system, comprising:

a processor; and

a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations for managing access to privately held health information, the operations comprising:

obtaining a request for medical data for a patient, the medical data being part of the privately held health information;

in response to obtaining the request:

identifying a patient device that is designated by the patient;

performing a first consent resolution action with the patient device to attempt to gain a first authorization to disclose the medical data;

in a first instance of the first consent resolution action where the first authorization to disclose the medical data was not obtained:

identifying a verified designee device that is designated by the patient;

performing a second consent resolution action with the verified designee device to attempt to gain a second authorization to disclose the medical data;

in a first instance of the second consent resolution action where the second authorization to disclose the medical data was not obtained:

 identifying a verified provider designee device that is designated by the patient;

 performing a third consent resolution action with the verified provider designee device to attempt to gain a third authorization to disclose the medical data; and

 in a first instance of the third consent resolution action where the third authorization to disclose the medical data was not obtained:

 denying access to the medical data to service the request; and

 in a second instance of the third consent resolution action where the third authorization to disclose the medical data was obtained:

 providing the medical data to service the request.

18. The data processing system of claim 17 , wherein performing the third consent resolution action comprises:

requesting the third authorization to disclose the medical data, the request being made to the verified provider designee device;

obtaining a first response indicating whether the third authorization is partially granted by the verified provider designee device;

in an instance of the first response where the third authorization is partially granted by the verified provider designee device:

identifying a second provider designee device designated by the verified provider designee device;

obtaining a second response indicating whether the third authorization is also partially granted by the second provider designee device; and

determining whether the third authorization to disclose the medical data has been granted based on the first response and the second response.

19. The data processing system of claim 18 , wherein verified provider designee device is associated with a primary care physician for the patient, and the second provider designee device is associated with another professional that provides care to the patient.

20. The data processing system of claim 19 , performing the first consent resolution action comprises:

requesting the first authorization to disclose the medical data, the request being made to the patient device;

obtaining a third response indicating whether the first authorization is granted by the patient device; and

determining whether the first authorization to disclose the medical data has been granted based on the third response.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: PATEL, DHARMESH M.; MOTGI, PREM PRADEEP; SOKHI, MANPREET SINGH
To: DELL PRODUCTS L.P.
Reel/Frame 063546/0969 →
Continuity (1)
Related Publication 20240362358A1 · Oct 31, 2024
References Cited (82)
US 6606620B1 · Sundaresan · 2003 [cited by applicant]
US 8117235B1 · Barta · 2012 [cited by applicant]
US 8255948B1 · Black et al. · 2012 [cited by applicant]
US 8495720B2 · Counterman · 2013 [cited by applicant]
US 9361428B2 · Bessette · 2016 [cited by applicant]
US 9571890B1 · Diamondstein · 2017 [cited by applicant]
US 9781097B2 · Grajek et al. · 2017 [cited by applicant]
US 10042993B2 · Beigi · 2018 [cited by applicant]
US 10073948B2 · Cohen et al. · 2018 [cited by applicant]
US 10157275B1 · Venkatasamy et al. · 2018 [cited by applicant]
US 10170203B1 · Blechman · 2019 [cited by examiner]
US 10462142B2 · Pattar et al. · 2019 [cited by applicant]
US 10701056B2 · Murthy · 2020 [cited by applicant]
US 10904237B2 · Murthy et al. · 2021 [cited by applicant]
US 11010392B1 · Hirsch et al. · 2021 [cited by applicant]
US 11094402B2 · Brown et al. · 2021 [cited by applicant]
US 11217331B2 · Vishnubhatla et al. · 2022 [cited by applicant]
US 11405189B1 · Bennison · 2022 [cited by applicant]
US 11631401B1 · Nudd · 2023 [cited by applicant]
US 11763821B1 · McNair · 2023 [cited by applicant]
US 11849069B1 · Can · 2023 [cited by applicant]
US 12135708B2 · Chermside · 2024 [cited by applicant]
US 20030046401A1 · Abbott · 2003 [cited by applicant]
US 20050160166A1 · Kraenzel · 2005 [cited by applicant]
US 20080154961A1 · Dougall · 2008 [cited by applicant]
US 20080275701A1 · Wu et al. · 2008 [cited by applicant]
US 20090171692A1 · Zilberman et al. · 2009 [cited by applicant]
US 20100169304A1 · Hendricksen et al. · 2010 [cited by applicant]
US 20110131174A1 · Birch et al. · 2011 [cited by applicant]
US 20120265771A1 · Suh · 2012 [cited by applicant]
US 20140181673A1 · Work · 2014 [cited by applicant]
US 20140201199A1 · Hajaj · 2014 [cited by applicant]
US 20140207885A1 · Baker et al. · 2014 [cited by applicant]
US 20140344288A1 · Evans · 2014 [cited by applicant]
US 20150169574A1 · Bau et al. · 2015 [cited by applicant]
US 20150199268A1 · Davis et al. · 2015 [cited by applicant]
US 20150356127A1 · Pierre et al. · 2015 [cited by applicant]
US 20160006839A1 · Sawazaki · 2016 [cited by applicant]
US 20160164813A1 · Anderson · 2016 [cited by applicant]
US 20160231928A1 · Lewis et al. · 2016 [cited by applicant]
US 20160232159A1 · Parikh · 2016 [cited by applicant]
US 20160306812A1 · McHenry et al. · 2016 [cited by applicant]
US 20170013047A1 · Hubbard · 2017 [cited by applicant]
US 20170068784A1 · Sullivan · 2017 [cited by examiner]
US 20170262164A1 · Jain · 2017 [cited by applicant]
US 20170365101A1 · Samec et al. · 2017 [cited by applicant]
US 20180121502A1 · Prieur · 2018 [cited by applicant]
US 20180189352A1 · Ghafourifar · 2018 [cited by applicant]
US 20180203612A1 · Kats et al. · 2018 [cited by applicant]
US 20190012931A1 · Candelore · 2019 [cited by applicant]
US 20190279744A1 · Howley et al. · 2019 [cited by applicant]
US 20190297035A1 · Fox et al. · 2019 [cited by applicant]
US 20190325036A1 · Edge · 2019 [cited by applicant]
US 20200110882A1 · Ripolles Mateu et al. · 2020 [cited by applicant]
US 20200226216A1 · Marin et al. · 2020 [cited by applicant]
US 20200258516A1 · Khaleghi · 2020 [cited by applicant]
US 20200364358A1 · Karia · 2020 [cited by examiner]
US 20210056131A1 · Ackermann et al. · 2021 [cited by applicant]
US 20210065203A1 · Billigmeier et al. · 2021 [cited by applicant]
US 20210256534A1 · An · 2021 [cited by applicant]
US 20210390196A1 · Lavine et al. · 2021 [cited by applicant]
US 20220261152A1 · Jude et al. · 2022 [cited by applicant]
US 20220293087A1 · Kumar · 2022 [cited by applicant]
US 20220334719A1 · Thrane · 2022 [cited by applicant]
US 20220366131A1 · Ekron · 2022 [cited by applicant]
US 20230061725A1 · Khan · 2023 [cited by applicant]
US 20230068099A1 · Abramenko et al. · 2023 [cited by applicant]
US 20230137931A1 · Song · 2023 [cited by applicant]
US 20230221911A1 · Bandameedipalli · 2023 [cited by applicant]
CN 202058147U · 2011 [cited by applicant]
CN 115292285A · 2022 [cited by applicant]
JP 4808173B2 · 2011 [cited by applicant]
JP 2015106406A · 2015 [cited by applicant]
WO 2023220948A1 · 2023 [cited by applicant]
Page, Sébastien, “How to move your Health data from one iPhone to another,” iDB, Web Page <https://www.downloadblog.com/2016/10/13/health-data-importer-makes-moving-your-health-data-from-one-iphone-to-another-a-breeze/>… [cited by applicant]
“MyChart,” Web Page <https://www.mychart.org/> accessed on Oct. 30, 2022 (6 Pages). [cited by applicant]
Xu, Jie, et al., “Federated learning for healthcare informatics,” Journal of Healthcare Informatics Research 5 (2021): 1-19. (19 Pages). [cited by applicant]
Naz, Sadaf, et al., “A comprehensive review of federated learning for COVID-19 detection,” International Journal of Intelligent Systems 37.3 (2022): 2371-2392. (22 Pages). [cited by applicant]
Prasser, Fabian, et al., “Efficient and effective pruning strategies for health data de-identification,” BMC medical Informatics and decision making 16.1 (2016): 1-14. (14 Pages). [cited by applicant]
“FollowMyHealth®,” Allscripts Healthcare Solutions Inc, Google Play Store, Web Page <https://play.google.com/store/apps/details?id=com.jardogs.fmhmobile&hl=en_US&gl=US> accesed on Jan. 8, 2023 (4 Pages). [cited by applicant]
Balaskas, Georgios, et al., “An end-to-end system for transcription, translation, and summarization to support the co-creation process. A Health Cascade Study”, ACM Petra '23, published Aug. 10, 2023, pp. 625-631. (Year… [cited by applicant]
D. Fedasyuk and I. Lutsyk, “Tools for adaptation of a mobile application to the needs of users with cognitive impairments,” 2021 IEEE 16th International Conference on Computer Sciences and Information Technologies (CSIT… [cited by applicant]