IP Library › Granted Patent US 12,294,621
Granted Patent B2
US 12,294,621 · App. 17/872,561 · Granted May 6, 2025

Zero-knowledge environment based networking engine

Inventors: William J. Raduchel (Palo Alto, CA); Art Spivy (Great Falls, VA)
Assignee: eIngot LLC
H04L67/01G06F9/45558G06F21/6218G06Q50/01G16H10/60H04L9/0637H04L63/0428H04L63/062H04L63/08H04L63/102H04L63/12H04L67/12H04L67/306H04W4/21G06F2009/45595H04L9/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,294,621
App. No.
17/872,561
Granted
May 6, 2025
Kind
B2
Abstract

Methods, systems, and apparatus are described providing networking engines. Specifically, the present specification relates to a method for implementing software containers implementing network engines that may be configured to act in a zero-knowledge environment. In such implementations, all information pertaining to the network engine associated with a user that is stored in the container is solely that of a user unless explicitly shared by the user. In some implementations, the containers may be configured to participate in a publish-and-subscribe network in order to share information. In addition, the containers may be provisioned with controls so that global operators may comply with local privacy rules.

Claims (65)

1. A computer-implemented method comprising:

determining a likelihood of a proximate collocation of a user device and a healthcare provider;

in response to the likelihood of proximate collocation satisfying a threshold, calculating at least one metric comprising a likely need to communicate data related to the user to the healthcare provider; and

determining, using the metric, to perform one or more predetermined actions to data related to a user, comprising:

encrypting data related to the user using an encryption key;

generating a hash for at least a portion of the encrypted data, using a hashing algorithm and at least the portion of the encrypted data; and

communicating the encrypted data related to the user between a device of the healthcare provider and the user device;

wherein the hash permits the device of the healthcare provider to confirm authenticity of at least the portion of the data related to the user.

2. The method of claim 1 , wherein determining to perform one or more predetermined actions to the data related to a user comprises:

determining, using user defined security levels, portions of the data related to a user that are authorized to share.

3. The method of claim 1 , wherein the predetermined actions to the data related to a user comprises:

scheduling an appointment;

updating a medical record;

comparing data; or

modifying a user's care plan data.

4. The method of claim 1 , wherein, determining that a user device is proximate to a healthcare provider comprises:

receiving location data that provides a geographic location of a user device corresponding to a user;

obtaining one or more geographic locations of one or more healthcare providers; and

determining that the user device is within a threshold distance of a geographic location of a particular healthcare provider.

5. The method of claim 1 wherein the data related to a user comprises a healthcare identity graph, medical record data, or personal data.

6. The method of claim 1 , comprising transmitting a message that includes the hash to be authenticated in a block chain.

7. The method of claim 1 , comprising transmitting an alert to the user device that the data related to the user has been encrypted.

8. The method of claim 1 , wherein the data related to the user comprises a user's healthcare plan.

9. The method of claim 1 , wherein calculating at least one metric comprises:

accessing a health care network user profile associated with the user of the user device;

accessing a care plan for the user of the user device; and

comparing the user profile, the care plan, and the proximate collocation of the user device and the healthcare provider.

10. The method of claim 3 , comprising in response to determining the user device is proximate to the healthcare provider; and

recording an event in the user's care plan.

11. A system comprising one or more computers and one or more storage devices on which are stored instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising:

determining a likelihood of a proximate collocation of a user device and a healthcare provider;

in response to the likelihood of proximate collocation satisfying a threshold, calculating at least one metric comprising a likely need to communicate data related to the user to the healthcare provider; and

determining, using the metric, to perform one or more predetermined actions to data related to a user, comprising:

encrypting data related to the user using an encryption key;

generating a hash for at least a portion of the encrypted data, using a hashing algorithm and at least the portion of the encrypted data; and

communicating the encrypted data related to the user between a device of the healthcare provider and the user device;

wherein the hash permits the device of the healthcare provider to confirm authenticity of at least the portion of the data related to the user.

12. The system of claim 11 , wherein determining to perform one or more predetermined actions to the data related to a user comprises:

determining, using user defined security levels, portions of the data related to a user that are authorized to share.

13. The system of claim 11 , wherein the predetermined actions to the data related to a user comprises:

scheduling an appointment;

updating a medical record;

comparing data; or

modifying a user's care plan data.

14. The system of claim 11 , wherein, determining that a user device is proximate to a healthcare provider comprises:

receiving location data that provides a geographic location of a user device corresponding to a user;

obtaining one or more geographic locations of one or more healthcare providers; and

determining that the user device is within a threshold distance of a geographic location of a particular healthcare provider.

15. The system of claim 11 wherein the data related to the user comprises a healthcare identity graph, medical record data, or personal data.

16. One or more non-transitory computer storage media encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform operations comprising:

determining a likelihood of a proximate collocation of a user device and a healthcare provider;

in response to the likelihood of proximate collocation satisfying a threshold, calculating at least one metric comprising a likely need to communicate data related to the user to the healthcare provider; and

determining, using the metric, to perform one or more predetermined actions to data related to a user, comprising:

encrypting data related to the user using an encryption key;

generating a hash for at least a portion of the encrypted data, using a hashing algorithm and at least the portion of the encrypted data; and

communicating the encrypted data related to the user between a device of the healthcare provider and the user device;

wherein the hash permits the device of the healthcare provider to confirm authenticity of at least the portion of the data related to the user.

17. The system of claim 11 , comprising transmitting an alert to the user device that the data related to the user has been encrypted.

18. The system of claim 11 , wherein the data related to the user comprises a user's healthcare plan.

19. The system of claim 11 , wherein calculating at least one metric comprises:

accessing a health care network user profile associated with the user of the user device;

accessing a care plan for the user of the user device; and

comparing the user profile, the care plan, and the proximate collocation of the user device and the healthcare provider.

20. The system of claim 13 , comprising in response to determining the user device is proximate to the healthcare provider; and

recording an event in the user's care plan.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2022
From: RADUCHEL, WILLIAM J.; SPIVY, ART
To: EINGOT LLC
Reel/Frame 060607/0753 →
Continuity (3)
Continuation 16827329 · Mar 23, 2020
Continuation 15896347 · Feb 14, 2018
Related Publication 20230010452A1 · Jan 12, 2023
References Cited (236)
US 5995943A · Bull et al. · 1999 [cited by applicant]
US 6338039B1 · Lonski et al. · 2002 [cited by applicant]
US 6463417B1 · Schoenberg · 2002 [cited by applicant]
US 6747561B1 · Reeves · 2004 [cited by applicant]
US 6845448B1 · Chaganti et al. · 2005 [cited by applicant]
US 6988075B1 · Hacker · 2006 [cited by applicant]
US 7466235B1 · Kolb et al. · 2008 [cited by applicant]
US 7617114B1 · Tooke, III · 2009 [cited by applicant]
US 7664753B2 · Shelton · 2010 [cited by applicant]
US 7693838B2 · Morgan et al. · 2010 [cited by applicant]
US 7848937B2 · Schoenberg · 2010 [cited by applicant]
US 8086570B2 · Kawabe et al. · 2011 [cited by applicant]
US 8155977B2 · Schoenberg · 2012 [cited by applicant]
US 8327456B2 · Jones et al. · 2012 [cited by applicant]
US 8370895B2 · DiCrescenzo et al. · 2013 [cited by applicant]
US 8600776B2 · Raduchel · 2013 [cited by applicant]
US 8626523B1 · Mack et al. · 2014 [cited by applicant]
US 8758238B2 · Clapp · 2014 [cited by applicant]
US 8844058B2 · Vera et al. · 2014 [cited by applicant]
US 8868437B2 · Menschik et al. · 2014 [cited by applicant]
US 8955102B1 · Harding · 2015 [cited by examiner]
US 9122562B1 · Stickle · 2015 [cited by applicant]
US 9262743B2 · Heins · 2016 [cited by examiner]
US 9426157B2 · D'Angelo et al. · 2016 [cited by applicant]
US 9489486B2 · Raduchel · 2016 [cited by applicant]
US 9619616B2 · Raduchel · 2017 [cited by applicant]
US 9686356B2 · Raduchel · 2017 [cited by examiner]
US 9721228B2 · Cort · 2017 [cited by examiner]
US 9867085B2 · Suni · 2018 [cited by applicant]
US 9939981B2 · Varadharajan et al. · 2018 [cited by applicant]
US 9946585B1 · Wookey et al. · 2018 [cited by applicant]
US 10044507B2 · Raduchel · 2018 [cited by applicant]
US 10063380B2 · Brandwine et al. · 2018 [cited by applicant]
US 10078728B2 · Raduchel · 2018 [cited by applicant]
US 10182103B2 · Koushik et al. · 2019 [cited by applicant]
US 10187260B1 · Chen et al. · 2019 [cited by applicant]
US 10231077B2 · Raduchel · 2019 [cited by applicant]
US 10255093B2 · Yan · 2019 [cited by applicant]
US 10277705B2 · Clavera et al. · 2019 [cited by applicant]
US 10339573B1 · Wookey et al. · 2019 [cited by applicant]
US 10346149B1 · Wookey et al. · 2019 [cited by applicant]
US 10387857B2 · Kim et al. · 2019 [cited by applicant]
US 10411975B2 · Martinez et al. · 2019 [cited by applicant]
US 10425411B2 · Huang · 2019 [cited by applicant]
US 10447524B1 · Bono et al. · 2019 [cited by applicant]
US 10469472B2 · Main et al. · 2019 [cited by applicant]
US 10530837B2 · Bala et al. · 2020 [cited by applicant]
US 10554753B2 · Tormasov · 2020 [cited by examiner]
US 10582340B2 · Botti et al. · 2020 [cited by applicant]
US 10601960B2 · Raduchel · 2020 [cited by examiner]
US 10693647B2 · Raduchel · 2020 [cited by applicant]
US 10726119B2 · Feroz et al. · 2020 [cited by applicant]
US 10742520B2 · Frost · 2020 [cited by applicant]
US 10818385B2 · Raduchel · 2020 [cited by applicant]
US 11233841B2 · Wei et al. · 2022 [cited by applicant]
US 11244261B2 · To et al. · 2022 [cited by applicant]
US 11283753B1 · Wolfe et al. · 2022 [cited by applicant]
US 11399079B2 · Raduchel · 2022 [cited by applicant]
US 11531768B2 · Unagami · 2022 [cited by examiner]
US 11637703B2 · Raduchel · 2023 [cited by applicant]
US 11893129B2 · Raduchel · 2024 [cited by applicant]
US 11907397B2 · Raduchel · 2024 [cited by applicant]
US 12058266B2 · Raduchel · 2024 [cited by applicant]
US 20010047281A1 · Keresman, III et al. · 2001 [cited by applicant]
US 20020010679A1 · Felsher · 2002 [cited by applicant]
US 20020013517A1 · West et al. · 2002 [cited by applicant]
US 20020016821A1 · Son et al. · 2002 [cited by applicant]
US 20020042725A1 · Mayaud · 2002 [cited by applicant]
US 20020042884A1 · Wu et al. · 2002 [cited by applicant]
US 20020059082A1 · Moczygemba · 2002 [cited by applicant]
US 20030074248A1 · Braud et al. · 2003 [cited by applicant]
US 20030110242A1 · Brown et al. · 2003 [cited by applicant]
US 20030140044A1 · Mok et al. · 2003 [cited by applicant]
US 20030191669A1 · Fitzgerald · 2003 [cited by applicant]
US 20030195774A1 · Abbo · 2003 [cited by applicant]
US 20030212581A1 · Adolph et al. · 2003 [cited by applicant]
US 20030233342A1 · Vadrot · 2003 [cited by applicant]
US 20040070615A1 · Duke et al. · 2004 [cited by applicant]
US 20040111291A1 · Dust et al. · 2004 [cited by applicant]
US 20040148194A1 · Wellons et al. · 2004 [cited by applicant]
US 20040260577A1 · Dahlin et al. · 2004 [cited by applicant]
US 20050038670A1 · Takkar et al. · 2005 [cited by applicant]
US 20050125252A1 · Schoenberg · 2005 [cited by applicant]
US 20050283383A1 · Zammit · 2005 [cited by applicant]
US 20060026042A1 · Awaraji et al. · 2006 [cited by applicant]
US 20060106646A1 · Squilla et al. · 2006 [cited by applicant]
US 20060106836A1 · Masugi et al. · 2006 [cited by applicant]
US 20070006325A1 · Gargaro · 2007 [cited by applicant]
US 20070027721A1 · Hasan et al. · 2007 [cited by applicant]
US 20070061170A1 · Lorsch · 2007 [cited by applicant]
US 20070078677A1 · Hofstetter · 2007 [cited by applicant]
US 20070123754A1 · Cuddihy et al. · 2007 [cited by applicant]
US 20070138253A1 · Libin et al. · 2007 [cited by applicant]
US 20080009344A1 · Graham et al. · 2008 [cited by applicant]
US 20080010091A1 · Kim et al. · 2008 [cited by applicant]
US 20080034019A1 · Cisler et al. · 2008 [cited by applicant]
US 20080109651A1 · Duda et al. · 2008 [cited by applicant]
US 20080177569A1 · Chen et al. · 2008 [cited by applicant]
US 20080290159A1 · Bartley, Sr. et al. · 2008 [cited by applicant]
US 20090012817A1 · Squires et al. · 2009 [cited by applicant]
US 20090037224A1 · Raduchel · 2009 [cited by applicant]
US 20090044259A1 · Bookman et al. · 2009 [cited by applicant]
US 20100070296A1 · Massoumi et al. · 2010 [cited by applicant]
US 20110040586A1 · Murray et al. · 2011 [cited by applicant]
US 20110041168A1 · Murray et al. · 2011 [cited by applicant]
US 20110085667A1 · Berrios · 2011 [cited by examiner]
US 20110161172A1 · Lee · 2011 [cited by applicant]
US 20110208559A1 · Fontoura · 2011 [cited by applicant]
US 20110258441A1 · Ashok · 2011 [cited by applicant]
US 20120030231A1 · Cropper · 2012 [cited by applicant]
US 20120042000A1 · Heins · 2012 [cited by examiner]
US 20120078660A1 · Mangicaro et al. · 2012 [cited by applicant]
US 20120089678A1 · Cort · 2012 [cited by examiner]
US 20120123798A1 · Lanzalotti · 2012 [cited by applicant]
US 20120126948A1 · Brunski · 2012 [cited by applicant]
US 20130018855A1 · Eshghi et al. · 2013 [cited by applicant]
US 20130205022A1 · Kagan et al. · 2013 [cited by applicant]
US 20130268284A1 · Heck · 2013 [cited by applicant]
US 20130339155A1 · Yerli · 2013 [cited by applicant]
US 20130346518A1 · Soundararajan · 2013 [cited by applicant]
US 20130346569A1 · Smirh et al. · 2013 [cited by applicant]
US 20140081669A1 · Raduchel · 2014 [cited by applicant]
US 20140095286A1 · Drewry · 2014 [cited by examiner]
US 20140095319A1 · Bruns et al. · 2014 [cited by applicant]
US 20140108049A1 · Fuhrmann et al. · 2014 [cited by applicant]
US 20140195255A1 · Ghosh et al. · 2014 [cited by applicant]
US 20140310063A1 · Freeman · 2014 [cited by applicant]
US 20140372748A1 · Dixon · 2014 [cited by applicant]
US 20150046192A1 · Raduchel · 2015 [cited by applicant]
US 20150142986A1 · Reznik · 2015 [cited by applicant]
US 20150213206A1 · Amarasingham et al. · 2015 [cited by applicant]
US 20160050272A1 · Raduchel · 2016 [cited by examiner]
US 20160063215A1 · Zamer · 2016 [cited by examiner]
US 20160292370A1 · Saric · 2016 [cited by applicant]
US 20170011172A1 · Raduchel · 2017 [cited by applicant]
US 20170032092A1 · Mink · 2017 [cited by applicant]
US 20170161439A1 · Raduchel · 2017 [cited by applicant]
US 20170331630A1 · Raduchel · 2017 [cited by applicant]
US 20180026991A1 · Bhamidipati et al. · 2018 [cited by applicant]
US 20180039737A1 · Dempers · 2018 [cited by examiner]
US 20180053200A1 · Cronin et al. · 2018 [cited by applicant]
US 20180067664A1 · Denischenko et al. · 2018 [cited by applicant]
US 20180157700A1 · Roberts · 2018 [cited by examiner]
US 20180183595A1 · Raduchel · 2018 [cited by applicant]
US 20190027234A1 · Raduchel · 2019 [cited by applicant]
US 20190208354A1 · Raduchel · 2019 [cited by applicant]
US 20190253523A1 · Raduchel · 2019 [cited by examiner]
US 20190287663A1 · Raduchel · 2019 [cited by applicant]
US 20200050774A1 · Raduchel · 2020 [cited by applicant]
US 20200236198A1 · Raduchel · 2020 [cited by examiner]
US 20200313856A1 · Basu · 2020 [cited by examiner]
US 20200313889A1 · Raduchel · 2020 [cited by applicant]
US 20230010452A1 · Raduchel · 2023 [cited by examiner]
US 20230099208A1 · Raduchel et al. · 2023 [cited by applicant]
US 20240097908A1 · Raduchel · 2024 [cited by applicant]
CN 1348130 · 2002 [cited by applicant]
CN 1650305 · 2005 [cited by applicant]
CN 101742960 · 2010 [cited by applicant]
CN 102231708 · 2011 [cited by applicant]
CN 102790761 · 2012 [cited by applicant]
CN 103140870 · 2013 [cited by applicant]
CN 103237041 · 2013 [cited by applicant]
CN 103259735 · 2013 [cited by applicant]
EP 2341479 · 2011 [cited by applicant]
GB 2369205 · 2002 [cited by applicant]
WO WO2016025619 · 2016 [cited by applicant]
Extended European Search Report in European Appln No. 24168125.3, dated Oct. 28, 2024, 10 pages. [cited by applicant]
Baig, Edward C., “Amazon exec: Alexa should be able to talk to Siri,” USA Today, Jun. 7, 2017, URL <https://www.usatoday.com/story/tech/columnist/baig/2017/06/07/amazons-exec-alexa-should-able-talk-siri/102594930/>, 3 p… [cited by applicant]
Batz et al., “P2P applied in CMS for advertising,” 2009 Fourth International Conference on Digital Information Management, 2009, 1-8. [cited by applicant]
Bauer et al., “A Comparison of users' perceptions of and willingness to use Google, Facebook, and Google+ single-sign-on functionality,” in Proceedings of the 2013 ACM workshop on Digital identity management *DIM '13). … [cited by applicant]
Bitcoin.org [online], “VerifyMessage,” accessed on Oct. 20, 2016, via Internet Archive: Wayback Machine URL <https://web.archive.org/web/20160328185839/bitcoin.org/en/developer-reference#verifymessage>, 2 pages. [cited by applicant]
Brown, “SEC 2: Recommended Elliptic Curve Domain Parameters,” Standars for Efficient Cryptography, Jan. 27, 2010, 37 pages. [cited by applicant]
ChicagoTribune.com [online], “Pharmacies miss half of dangerous drug combinations,” Dec. 15, 2016, retrieved from URL <https://www.chicagotribune.com/investigations/ct-drug-interactions-pharmacy-met-20161214-story.html>… [cited by applicant]
CN Office Action in Chinese Application No. 200880022802.5, dated May 24, 2011, 9 pages (with English translation). [cited by applicant]
CN Office Action in Chinese Application No. 201580042948.6, dated Apr. 16, 2020, 11 pages (with English Translation). [cited by applicant]
CN Office Action in Chinese Application No. 201580064014.2, dated Apr. 16, 2020, 37 pages (with English Translation). [cited by applicant]
CN Office Action in Chinese Appln. No. 201580064014.2, dated Dec. 9, 2020, 23 pages ( with English translation). [cited by applicant]
CN Office Action in Chinese Appln. No. 201580064014.2, dated Mar. 3, 2021, 24 pages (with English translation). [cited by applicant]
CN Office Action issued in CN201210112416.3 on Sep. 22, 2014, with English Translation, 20 pages. [cited by applicant]
developer.bitcoin.org [online], “Transactions,” Oct. 20, 2016, retrieved from URL <https://developer.bitcoin.org/devguide/transactions.html>, 12 pages. [cited by applicant]
Developers.Coinbase.com [online], “API Key Authentication,” accessed on Oct. 20, 2016, retrieved from URL <https://developers.coinbase.com/docs/wallet/api-key-authentication>, 5 pages. [cited by applicant]
docs.docker.com [online], “Content trust in Docker,” accessed on Dec. 22, 2016, retrieved from URL <https://docs.docker.com/engine/security/trust/content_trust/>, 11 pages. [cited by applicant]
Dwork et al., “The Algorithmic Foundations of Differential Privacy,” Foundations and Trends in Theoretical Computer Science, 2014, 9(3-4):211-407. [cited by applicant]
Eastlake et al., “US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF),” IETF, May 2011, 127 pages. [cited by applicant]
Ethereum.org [online], “Ethereum” available on or before Oct. 21, 2016, via Internet Archive: Wayback Machine URL <https://web.archive.org/web/20161020205038/https://www.ethereum.org/>, 11 pages. [cited by applicant]
European Extended Search Report in European Application No. 15831680.2, dated Mar. 5, 2018, 6 pages. [cited by applicant]
European Extended Search Report in European Application No. 18754556.1, dated Jan. 30, 2020, 9 pages. [cited by applicant]
Extended European Search Report in European Appln. 20170489.7, dated Dec. 23, 2020, 9 pages. [cited by applicant]
FDA.gov [online], “Unique Device Identification—UDI,” available on or before Oct. 2, 2016, via Internet Archive: Wayback Machine URL <https://web.archive.org/web/20161002233424/http://fda.gov/MedicalDevices/DeviceRegula… [cited by applicant]
Feige et al., “Zero-knowledge proofs of identity”, J. Cryptology, 1:77-94, 1988. [cited by applicant]
HL7.org [online], “HL7 Messaging Standard Version 2.3,” Oct. 12, 2016, retrieved from URL <http://www.hl7.org/implement/standards/product_brief.cfm?product_id=140>, 3 pages. [cited by applicant]
IN Office Action in Indian Appln. No. 201747000095, dated Dec. 31, 2020, 9 pages. [cited by applicant]
IN Office Action in Indian Appln. No. 201747018225, dated Feb. 23, 2021, 8 pages. [cited by applicant]
Indian Office Action in Indian Application No. 8383/DELNP/2009, dated Jun. 22, 2018, 8 pages. [cited by applicant]
Kansagara et al., “Risk Prediction Models for Hospital Readmission: A Systematic Review,” JAMA, Oct. 2011, 306(15):1688-1698. [cited by applicant]
Kemoni, “The Impact of Records Centres on the Management of Public Sector Records in Kenya,” dated Apr. 1998, 13 pages. [cited by applicant]
Krawczyk et al., “HMAC:Keyed-Hashing for Message Authentication,” IETF, Feb. 1997, 11 pages. [cited by applicant]
Murphy et al., “Electronic Trigger-Based Intervention to Reduce Delays in Diagnostic Evaluation for Cancer: A Cluster Randomized Controlled Trial,” Journal of Clinical Oncology, Nov. 2015, 33(31):3560-3567. [cited by applicant]
Nakamoto, “Bitcoin: A Peer-to-Peer Electronic Cash System,” Bitcoin, 2008, 9 pages. [cited by applicant]
NCQA.org [online], “HEDIS 2017 Measures,” available on or before Aug. 3, 2016, via Internet Archive: Wayback Machine URL <https://web.archive.org/web/20160701093843/https://www.ncqa.org/hedis-quality-measurement/hedis-m… [cited by applicant]
Neng-Wen Wang, Yueh-Min Huang, “A novel software key container in on-line media services,” Computers & Electrical Engineering, 2009, 35(2):370-5. [cited by applicant]
New Concept on Hospital Reformation, Yan Huizhong China Medical Technology Press, Dec. 1992, pp. 242-247, 10 pages (with English translation). [cited by applicant]
OAuth.net [online], “OAuth 2.0,” accessed on Oct. 20, 2016, retrieved from URL <https://oauth.net/2/>, 3 pages. [cited by applicant]
Office Action issue in U.S. Appl. No. 14/824,828 on Dec. 3, 2015, 21 pages. [cited by applicant]
Office Action issued in U.S. Appl. No. 14/824,828 on Jun. 9, 2016, 24 pages. [cited by applicant]
PCT International Search Report and Written Opinion in International Application No. PCT/US2015/044887, mailed Mar. 3, 2016, 16 pages. [cited by applicant]
PCT International Preliminary Report on Patentability for Application No. PCT/US2018/018507, dated Aug. 29, 2019, 10 pages. [cited by applicant]
PCT International Preliminary Report on Patentability in International Application No. PCT/US2015/056961, dated Apr. 25, 2017, 11 pages. [cited by applicant]
PCT International Search Report and the Written Opinion for Application No. PCT/US08/69228, dated Sep. 10, 2008, 15 pages. [cited by applicant]
PCT International Search Report and Written Opinion in International Application No. PCT/US2015/056961, mailed Jan. 11, 2016, 12 pages. [cited by applicant]
PCT International Search Report and Written Opinion in International Application No. PCT/US2018/018507, dated Mar. 12, 2018, 12 pages. [cited by applicant]
PCT Notification Concerning Transmittal of International Preliminary Report on Patentability for Application No. PCT/US2008/069228, dated Jan. 5, 2010, 11 pages. [cited by applicant]
Peterson et al., “A Blockchain-Based Approach to Health Information Exchange Networks,” Department of Health and Human Services, accessed on Oct. 20, 2016, 10 pages. [cited by applicant]
RedHat.com [online], “Container Image Signing,” Jul. 22, 2016, retrieved from URL <http://rhelblog.redhat.com/2016/07/22/container-image-signing/>, 6 pages. [cited by applicant]
Roseberry, “Can Any Bluetooth Enabled Cell Phone Be Used as a Modem?,” Jul. 2006, Retrieved from URL: <mobileoffice.about.com/od/usingyourphone/f/bluetoothphones.htm>. [cited by applicant]
Scheepers, “Virtualization and Containerization of Application Infrastructure: A Comparison,” 2014, University of Twente, 7 pages. [cited by applicant]
Shamir, “How to Share a Secret,” Communications of the ACM, Nov. 1979, 22(11):612-613. [cited by applicant]
Shrier et al., Blockchain and Health IT: Algorithms, Privacy, and Data, Department of Health and Human Services, Aug. 8, 2016, 14 pages. [cited by applicant]
Stewart et al., “A preliminary look at duplicate testing associated with lack of electronic health record interoperability for transferred patients,” Journal of the American Medical Informatics Association, May 2010, 17… [cited by applicant]
Turnbill, James, “The Docker Book,” Aug. 4, 104, The Docker Book v1.0.7 (8f1618c), p. 1-280. [cited by applicant]
Turner et al., “Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms,” IETF, Mar. 2011, 7 pages. [cited by applicant]
U.S Non-Final Office Action for U.S. Appl. No. 14/523,110, dated Jul. 8, 2016, 14 pages. [cited by applicant]
U.S. Final Office Action for U.S. Appl. No. 12/167,746, dated May 5, 2011, 10 pages. [cited by applicant]
U.S. Final Office action for U.S. Appl. No. 14/083,691 on Mar. 24, 2016, 16 pages. [cited by applicant]
U.S. Final Office Action for U.S. Appl. No. 14/083,691, dated Mar. 30, 2015, 12 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 12/167,746, dated Oct. 12, 2010, 12 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 14/083,691, dated Mar. 27, 2014, 13 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 14/083,691, dated Jul. 17, 2015, 10 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 14/083,691, dated Oct. 23, 2014, 16 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 15/435,150, dated Feb. 26, 2018, 18 pages. [cited by applicant]
U.S. Non-Final Office Action for U.S. Appl. No. 16/432,382, dated Jul. 8, 2019, 27 pages. [cited by applicant]
U.S. Notice of Allowance for U.S. Appl. No. 12/167,746, dated Jul. 29, 2013, 13 pages. [cited by applicant]
U.S. Notice of Allowance for U.S. Appl. No. 14/083,691, dated Jun. 17, 2016, 11 pages. [cited by applicant]
Umberson et al., “Social Relationships and Health: A Flashpoint for Health Policy,” Journal of Health and Social Behavior, 2010, 51(Suppl):S54-S66. [cited by applicant]
Zhao et al., “Study on Virtualization Technology of Programmable Routers” J. Chongqing Post and Telecomm,. Uni., Feb. 28, 2013, 20-3 and 29. [cited by applicant]
CN Office Action in Chinese Application 201880022485.0 dated Feb. 27, 2023, 29 pages (with English translation). [cited by applicant]