Granted Patent B2

US 12,613,991 · App. 18/533,157 · Granted Apr 28, 2026

Inventors: Alan Bachmann (Cranberry Township, GA); Mayurkumar Mevada (Hanover Park, IL); Brian J. Gamage (Canton, GA)

Assignee: CVS Pharmacy, Inc.

G06F21/6245

Abstract

Claims (84)

1 . A system, comprising:

one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to:

generate a graphical user interface including a plurality of types of private information describing health providers accepted for verifying identities of the health providers for a plurality of healthcare applications;

receive, via the graphical user interface, a selection of at least one type of private information of the plurality of types of private information of a health provider from a computing system of the health provider to use to verify an identity of the health provider;

receive private information of the type from the computing system;

issue a credential that verifies an identity of the health provider based on the type selected and a verification of the private information of the health provider; and

add the credential to a credential store of the computing system, the credential store to verify the identity of the health provider with the plurality of healthcare applications.

2 . The system of claim 1 , wherein the instructions cause the one or more processors to:

generate a request to add the credential to a blockchain, the request comprising the credential and an address of the health provider; and

transmit the request to at least one node of a blockchain network to add the credential to the blockchain.

3 . The system of claim 1 , wherein the instructions cause the one or more processors to:

identify that the credential is expired or a requirement is breached;

update the credential store to revoke the credential responsive to an identification that the credential is expired or the requirement is breached; and

push a notification that the credential is expired to at least one application that relied on the credential responsive to the identification that the credential is expired or the requirement is breached.

4 . The system of claim 1 , wherein the instructions cause the one or more processors to:

receive a request to extend the credential that verifies the identity of the health provider;

generate a second credential that verifies the identity of the health provider;

append the credential with the second credential in the credential store to maintain a credential history of the health provider.

5 . The system of claim 1 , wherein the instructions cause the one or more processors to:

receive an accountability request from an application responsive to the system of the health provider sending a request to the application to implement a service of the application;

provide, responsive to a reception of the accountability request, the credential to the application;

generate a second credential of a contract between the health provider and the application; and

append the second credential to the credential in the credential store.

6 . The system of claim 1 , wherein the instructions cause the one or more processors to:

verify the private information received from the system;

generate an identifier for the health provider of the system responsive to the verification of the private information; and

add the identifier and the credential to the credential store.

7 . The system of claim 1 , wherein the instructions cause the one or more processors to:

add the credential to the credential store at a first point in time;

generate a plurality of credentials at a plurality of times after the first point in time; and

append the plurality of credentials to the credential store without removing existing credentials of the credential store to maintain a history of a reputation of the health provider.

8 . The system of claim 1 , wherein the instructions cause the one or more processors to:

perform an attestation algorithm or a zero-knowledge proof algorithm to verify the private information of the health provider; and

generate the credential responsive to the verification of the private information with the attestation algorithm or the zero-knowledge proof algorithm.

9 . The system of claim 1 , wherein the instructions cause the one or more processors to:

issue the credential to verify the identity of the health provider with the plurality of healthcare applications;

issue a second credential to verify the identity of the health provider with only one application of the plurality of healthcare applications based on at least one requirement of the one application; and

add the second credential to the credential store.

10 . The system of claim 1 , wherein the instructions cause the one or more processors to:

tokenize the private information of the health provider to generate a plurality of tokens; and

transfer the plurality of tokens and the credential from the credential store of the health provider to a second credential store of a second health provider.

11 . The system of claim 1 , wherein the instructions cause the one or more processors to:

generate a value for the credential based on the selection of at least one type of private information, wherein the value indicates a level of verification of the private information and is based on an amount of the private information;

add the value for the credential to the credential store;

determine an adjustment to the value, the adjustment comprising an increase or a decrease to the value;

adjust the value based on the adjustment; and

add the adjusted value for the credential to the credential store.

12 . The system of claim 1 , wherein the instructions cause the one or more processors to:

determine, based on the type of the private information selected, a level of specificity of the private information; and

generate the credential based on the level of specificity of the type of the private information.

13 . The system of claim 1 , wherein the instructions cause the one or more processors to:

retrieve a plurality of credentials of the health provider, comprising the credential, from the credential store;

generate a history that indicates changes to the plurality of credentials of the health provider over time; and

provide the history to the computing system.

14 . A method, comprising:

generating, by one or more processing circuits, a graphical user interface including a plurality of types of private information describing health providers accepted for verifying identities of the health providers for a plurality of healthcare applications;

receiving, via the graphical user interface, by the one or more processing circuits, a selection of at least one type of private information of the plurality of types of private information of a health provider from a computing system of the health provider to use to verify an identity of the health provider;

receiving, by the one or more processing circuits, private information of the type from the computing system;

issuing, by the one or more processing circuits, a credential that verifies an identity of the health provider based on the type selected and a verification of the private information of the health provider; and

adding, by the one or more processing circuits, the credential to a credential store of the computing system, the credential store to verify the identity of the health provider with the plurality of healthcare applications.

15 . The method of claim 14 , comprising:

generating, by the one or more processing circuits, a request to add the credential to a blockchain, the request comprising the credential and an address of the health provider; and

transmitting, by the one or more processing circuits, the request to at least one node of a blockchain network to add the credential to the blockchain.

16 . The method of claim 14 , comprising:

identifying, by the one or more processing circuits, that the credential is expired or a requirement is breached;

updating, by the one or more processing circuits, the credential store to revoke the credential responsive to an identification that the credential is expired or the requirement is breached; and

pushing, by the one or more processing circuits, a notification that the credential is expired to at least one application that relied on the credential responsive to the identification that the credential is expired or the requirement is breached.

17 . The method of claim 14 , comprising:

receiving, by the one or more processing circuits, a request to extend the credential that verifies the identity of the health provider;

generating, by the one or more processing circuits, a second credential that verifies the identity of the health provider; and

appending, by the one or more processing circuits, the credential with the second credential in the credential store to maintain a credential history of the health provider.

18 . The method of claim 14 , comprising:

adding, by the one or more processing circuits, the credential to the credential store at a first point in time;

generating, by the one or more processing circuits, a plurality of credentials at a plurality of times after the first point in time; and

appending, by the one or more processing circuits, the plurality of credentials to the credential store without removing existing credentials of the credential store to maintain a history of a reputation of the health provider.

19 . The method of claim 14 , comprising:

performing, by the one or more processing circuits, an attestation algorithm or a zero-knowledge proof algorithm to verify the private information of the health provider; and

generating, by the one or more processing circuits, the credential responsive to the verification of the private information with the attestation algorithm or the zero-knowledge proof algorithm.

20 . One or more computer readable media storing instructions thereon that, when executed by one or more processors, cause the one or more processors to:

generate a graphical user interface including a plurality of types of private information describing health providers accepted for verifying identities of the health providers for a plurality of healthcare applications;

receive, via the graphical user interface, a selection of at least one type of private information of the plurality of types of private information of a health provider from a computing system of the health provider to use to verify an identity of the health provider;

receive private information of the type from the computing system;

issue a credential that verifies an identity of the health provider based on the type selected and a verification of the private information of the health provider; and

add the credential to a credential store of the computing system, the credential store to verify the identity of the health provider with the plurality of healthcare applications.

Assignments (1)

Continuity (1)

References Cited (283)