IP Library › Granted Patent US 12,505,241
Granted Patent B2
US 12,505,241 · App. 18/190,467 · Granted Dec 23, 2025

System and method for access control to and management of diagnostic 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/6218
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,505,241
App. No.
18/190,467
Granted
Dec 23, 2025
Kind
B2
Abstract

Methods and systems for managing collection of diagnostic data are disclosed. To collect diagnostic data, unmanaged devices may be used. The unmanaged devices may be registered with a data management system. During the registration process, procedures for processing diagnostic data from the unmanaged devices may be established. The procedures may be established based on data collection performance of the unmanaged devices. The procedures may reduce the likelihood of use of diagnostic data that is unreliable. Once obtained, the diagnostic data may be rated for different uses based on the performance of the hardware used to obtain the diagnostic data. Access controls for the diagnostic data may be put in place to manage distribution of the diagnostic data.

Claims (85)

1 . A method for managing data collection for managed devices and unmanaged devices, the method comprising:

obtaining a request for a type of diagnostic data that:

was obtained from an unmanaged device of the unmanaged devices, and

is stored in a data management system;

identifying, based on the request, a record in which diagnostic data of the type of diagnostic data is stored;

obtaining, from the records, access information specifying:

a first entity that initiated obtaining of the diagnostic data, and

a second entity that did not initiate obtaining of the diagnostic data and that attested to utility of the diagnostic data;

making a determination regarding whether an entity that initiated the request is the first entity or the second entity;

in a first instance of the determination where the entity is the first entity or the second entity:

providing the entity that initiated the request access to the diagnostic data to service the request; and

in a second instance of the determination where the entity is not the first entity or the second entity:

denying the entity that initiated the request access to the diagnostic data.

2 . The method of claim 1 , further comprising:

prior to obtaining the request:

obtaining, from the first entity, a request for the diagnostic data;

identifying the second entity based on the diagnostic data;

obtaining, from the second entity, and indication of the utility of the diagnostic data; and

updating the request for the diagnostic data to indicate that the first entity and the second entity are to be provided access to the diagnostic data.

3 . The method of claim 2 , wherein identifying the second entity comprises:

identifying, based on the type of the diagnostic data, at least one first candidate entity;

identifying, based on a type of the first entity, at least one second candidate entity; and

identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity.

4 . The method of claim 3 , wherein identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity comprises:

identifying that the second entity is a member of the at least one first candidate entity and the at least one second candidate entity to determine that the second entity is likely to use the diagnostic data.

5 . The method of claim 4 , wherein the at least one first candidate entity comprises members that each are associated with the type of the diagnostic data, and the at least one second candidate entity comprises members that each are associated with the type of the first entity.

6 . The method of claim 5 , wherein the members of the at least one second candidate entity have a same role.

7 . The method of claim 6 , wherein the members of the at least one first candidate entity have a role that is likely to utilize the diagnostic data in performance of the role.

8 . A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations for managing data collection for managed devices and unmanaged devices, the operations comprising:

obtaining a request for a type of diagnostic data that:

was obtained from an unmanaged device of the unmanaged devices, and

is stored in a data management system;

identifying, based on the request, a record in which diagnostic data of the type of diagnostic data is stored;

obtaining, from the records, access information specifying:

a first entity that initiated obtaining of the diagnostic data, and

a second entity that did not initiate obtaining of the diagnostic data and that attested to utility of the diagnostic data;

making a determination regarding whether an entity that initiated the request is the first entity or the second entity;

in a first instance of the determination where the entity is the first entity or the second entity:

providing the entity that initiated the request access to the diagnostic data to service the request; and

in a second instance of the determination where the entity is not the first entity or the second entity:

denying the entity that initiated the request access to the diagnostic data.

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

prior to obtaining the request:

obtaining, from the first entity, a request for the diagnostic data;

identifying the second entity based on the diagnostic data;

obtaining, from the second entity, and indication of the utility of the diagnostic data; and

updating the request for the diagnostic data to indicate that the first entity and the second entity are to be provided access to the diagnostic data.

10 . The non-transitory machine-readable medium of claim 9 , wherein identifying the second entity comprises:

identifying, based on the type of the diagnostic data, at least one first candidate entity;

identifying, based on a type of the first entity, at least one second candidate entity; and

identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity.

11 . The non-transitory machine-readable medium of claim 10 , wherein identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity comprises:

identifying that the second entity is a member of the at least one first candidate entity and the at least one second candidate entity to determine that the second entity is likely to use the diagnostic data.

12 . The non-transitory machine-readable medium of claim 11 , wherein the at least one first candidate entity comprises members that each are associated with the type of the diagnostic data, and the at least one second candidate entity comprises members that each are associated with the type of the first entity.

13 . The non-transitory machine-readable medium of claim 12 , wherein the members of the at least one second candidate entity have a same role.

14 . The non-transitory machine-readable medium of claim 13 , wherein the members of the at least one first candidate entity have a role that is likely to utilize the diagnostic data in performance of the role.

15 . 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 data collection for managed devices and unmanaged devices, the operations comprising:

obtaining a request for a type of diagnostic data that:

was obtained from an unmanaged device of the unmanaged devices, and

is stored in a data management system;

identifying, based on the request, a record in which diagnostic data of the type of diagnostic data is stored;

obtaining, from the records, access information specifying:

a first entity that initiated obtaining of the diagnostic data, and

a second entity that did not initiate obtaining of the diagnostic data and that attested to utility of the diagnostic data;

making a determination regarding whether an entity that initiated the request is the first entity or the second entity;

in a first instance of the determination where the entity is the first entity or the second entity:

providing the entity that initiated the request access to the diagnostic data to service the request; and

in a second instance of the determination where the entity is not the first entity or the second entity:

denying the entity that initiated the request access to the diagnostic data.

16 . The data processing system of claim 15 , wherein the operations further comprise:

prior to obtaining the request:

obtaining, from the first entity, a request for the diagnostic data;

identifying the second entity based on the diagnostic data;

obtaining, from the second entity, and indication of the utility of the diagnostic data; and

updating the request for the diagnostic data to indicate that the first entity and the second entity are to be provided access to the diagnostic data.

17 . The data processing system of claim 16 , wherein identifying the second entity comprises:

identifying, based on the type of the diagnostic data, at least one first candidate entity;

identifying, based on a type of the first entity, at least one second candidate entity; and

identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity.

18 . The data processing system of claim 17 , wherein identifying the second entity based on the at least one first candidate entity and the at least one second candidate entity comprises:

identifying that the second entity is a member of the at least one first candidate entity and the at least one second candidate entity to determine that the second entity is likely to use the diagnostic data.

19 . The data processing system of claim 18 , wherein the at least one first candidate entity comprises members that each are associated with the type of the diagnostic data, and the at least one second candidate entity comprises members that each are associated with the type of the first entity.

20 . The data processing system of claim 19 , wherein the members of the at least one second candidate entity have a same role.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2023
From: PATEL, DHARMESH M.; MOTGI, PREM PRADEEP; SOKHI, MANPREET SINGH
To: DELL PRODUCTS L.P.
Reel/Frame 063232/0295 →
Continuity (1)
Related Publication 20240330494A1 · Oct 3, 2024
References Cited (93)
US 6606620B1 · Sundaresan · 2003 [cited by applicant]
US 7028049B1 · Shelton · 2006 [cited by examiner]
US 8117235B1 · Barta · 2012 [cited by applicant]
US 8255948B1 · Black et al. · 2012 [cited by applicant]
US 9361428B2 · Bessette · 2016 [cited by applicant]
US 9571890B1 · Diamondstein · 2017 [cited by applicant]
US 10073948B2 · Cohen et al. · 2018 [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 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 20040117215A1 · Marchosky · 2004 [cited by examiner]
US 20050160166A1 · Kraenzel · 2005 [cited by applicant]
US 20050165627A1 · Fotsch · 2005 [cited by examiner]
US 20050203771A1 · Achan · 2005 [cited by examiner]
US 20080154961A1 · Dougall · 2008 [cited by applicant]
US 20080275701A1 · Wu et al. · 2008 [cited by applicant]
US 20090171692A1 · Zilberman · 2009 [cited by examiner]
US 20090300170A1 · Bhame · 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 20140245398A1 · Son · 2014 [cited by applicant]
US 20140288947A1 · Simpson · 2014 [cited by applicant]
US 20140344288A1 · Evans · 2014 [cited by applicant]
US 20150067176A1 · Dubois · 2015 [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 20160087976A1 · Kaplan · 2016 [cited by applicant]
US 20160112208A1 · Williams · 2016 [cited by examiner]
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 20170078195A1 · Raman · 2017 [cited by applicant]
US 20170262164A1 · Jain · 2017 [cited by applicant]
US 20170288867A1 · Collier · 2017 [cited by examiner]
US 20170330297A1 · Cronin · 2017 [cited by examiner]
US 20170365101A1 · Samec et al. · 2017 [cited by applicant]
US 20180068108A1 · Fish · 2018 [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 20190079855A1 · Dewitt · 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 20200100724A1 · Golay · 2020 [cited by examiner]
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 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 20220059216A1 · Lewis · 2022 [cited by applicant]
US 20220078007A1 · Reddem · 2022 [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]
US 20230223142A1 · Joao · 2023 [cited by examiner]
US 20230319026A1 · Waltermann · 2023 [cited by applicant]
US 20240177815A1 · Bilal · 2024 [cited by examiner]
US 20250017547A1 · Raveendranath · 2025 [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]
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]
Page, Sébastien, “How to move your Health data from one iPhone to another,” iDB, Web Page <https://www.idownloadblog.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]
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]
“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]