System and Method for Generating and Managing Distributed Register Based Entity Networks

There exists a need for a system to authenticate interactions with dynamically varying digital resources linked to distribution devices.

The following presents a summary of certain embodiments of the invention. This summary is not intended to identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present certain concepts and elements of one or more embodiments in a summary form as a prelude to the more detailed description that follows.

Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for generating and managing distributed register based entity networks. The system embodiments may comprise one or more memory devices having computer readable program code stored thereon, a communication device, and one or more processing devices operatively coupled to the one or more memory devices, wherein the one or more processing devices are configured to execute the computer readable program code to carry out the invention. In computer program product embodiments of the invention, the computer program product comprises at least one non-transitory computer readable medium comprising computer readable instructions for carrying out the invention. Computer implemented method embodiments of the invention may comprise providing a computing system comprising a computer processing device and a non-transitory computer readable medium, where the computer readable medium comprises configured computer program instruction code, such that when said instruction code is operated by said computer processing device, said computer processing device performs certain operations to carry out the invention.

In some embodiments, the present invention extracts user information associated with one or more users of an entity from one or more entity data repositories and one or more external systems, sorts the user information to split the user information into one or more levels of data, assigns each of the one or more levels of data to one or more access levels for accessing the user information, generates a validated record comprising the one or more levels of data associated with the one or more access levels for each of the one or more users based on the user information, stores the validated record comprising the one or more levels of data on a distributed register, receives a query associated with the validated record from a user device, and extracts at least a part of the validated record associated with the query from the distributed register and display the at least the part of the validated record on the user device.

In some embodiments, the present invention identifies a type of a user associated with the user device, identifies an access level of the user associated with the user device, and displays a level of data corresponding to the access level of the user.

In some embodiments, the present invention receives a change request associated with a user of the one or more users, validates the change request based on receiving the change request associated with the user, and updates a level of data associated with the user based on validating the change request.

In some embodiments, the present invention receives a request from a first user to generate a report associated with a second user of the one or more users, identifies an access level of the first user, extracts a level of data of the second user corresponding to the access level of the first user; generates the report associated with the second user using the extracted level of data, and display the report to the first user.

In some embodiments, the query is a user verification request.

In some embodiments, the present invention generates one or more digital cards associated with each of the one or more users, wherein the one or more digital cards comprises a mode for accessing at least a part of the validated record associated with each of the one or more users.

In some embodiments, the mode for accessing at least a part of the validated record comprises at least one of a link and a scannable code.

The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Furthermore, when it is said herein that something is “based on” something else, it may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein “based on” means “based at least in part on” or “based at least partially on.” Like numbers refer to like elements throughout.

As described herein, the term “entity” may be any organization that maintains one or more employee records. In some embodiments, the entity may be a financial institution which may include herein may include any financial institutions such as commercial banks, thrifts, federal and state savings banks, savings and loan associations, credit unions, investment companies, insurance companies and the like. In some embodiments, the entity may be a non-financial institution. As described herein, a “user” may be an employee, a customer, or a potential customer of the entity.

A “system environment”, as used herein, may refer to any information technology platform of an enterprise (e.g., a national or multi-national corporation) and may include a multitude of servers, machines, mainframes, personal computers, network devices, front and back end systems, database system and/or the like.

“Distributed register,” as used herein may also be referred to as a “distributed ledger,” as used herein may refer to a structured list of data records that is decentralized and distributed amongst a plurality of computing systems and/or devices. In some embodiments, the distributed ledger may use a linked block structure.

“Linked block,” “linked block structure,” “linked structure,” or “blockchain” as used herein may refer to a data structure which may comprise a series of sequentially linked “blocks,” where each block may comprise data and metadata. The “data” within each block may comprise one or more “data record” or “transactions,” while the “metadata” within each block may comprise information about the block, which may include a timestamp, a hash value of data records within the block, a pointer (e.g., a hash value) to the previous block in the linked block structure, and/or any additional data created by the system of the present invention. In this way, beginning from an originating block (e.g., a “genesis block”), each block in the linked block structure is linked to another block via the pointers within the block headers. If the data or metadata within a particular block in the linked block structure becomes corrupted or modified, the hash values found in the header of the affected block and/or the downstream blocks may become mismatched, thus allowing the system to detect that the data has been corrupted or modified. In some embodiments of the present invention, a user may submit data associated with the creation of a new block associated with the linked block structure. For example, a user may initiate a transaction, where the data associated with the transaction is stored in a new block linked with the transaction.

A “linked block ledger” may refer to a distributed ledger which uses linked block data structures. Generally, a linked block ledger is an “append only” ledger in which the data within each block within the linked block ledger may not be modified after the block is added to the linked block ledger; data may only be added in a new block to the end of the linked block ledger. In this way, the linked block ledger may provide a practically immutable ledger of data records over time.

“Permissioned distributed ledger” as used herein may refer to a linked block ledger for which an access control mechanism is implemented such that only known, authorized users may take certain actions with respect to the linked block ledger (e.g., add new data records, participate in the consensus mechanism, or the like). Accordingly, “unpermissioned distributed ledger” as used herein may refer to a linked block ledger without an access control mechanism.

“Private distributed ledger” as used herein may refer to a linked block ledger accessible only to users or devices that meet specific criteria (e.g., authorized users or devices of a certain entity or other organization). Accordingly, a “public distributed ledger” is a linked block ledger accessible by any member or device in the public realm. In some embodiments of the present invention, the distributed ledger being described herein may be a permissioned distributed ledger. In some embodiments of the present invention, the distributed ledger being described herein may be a private distributed ledger.

“Node” as used herein may refer to a computing system on which the distributed ledger is hosted. In some embodiments, each node maintains a full copy of the distributed ledger. In this way, even if one or more nodes become unavailable or offline, a full copy of the distributed ledger may still be accessed via the remaining nodes in the distributed ledger system. That said, in some embodiments, the nodes may host a hybrid distributed ledger such that certain nodes may store certain segments of the linked block ledger but not others.

“Consensus,” “consensus algorithm,” or “consensus mechanism” as used herein may refer to the process or processes by which nodes come to an agreement with respect to the contents of the distributed ledger. Changes to the ledger (e.g., addition of data records) may require consensus to be reached by the nodes in order to become a part of the authentic version of the ledger. In this way, the consensus mechanism may ensure that each node maintains a copy of the distributed ledger that is consistent with the copies of the distributed ledger hosted on the other nodes; if the copy of the distributed ledger hosted on one node becomes corrupted or compromised, the remaining nodes may use the consensus algorithm to determine the “true” version of the distributed ledger. The nodes may use various different mechanisms or algorithms to obtain consensus, such as proof-of-work (“PoW”), proof-of-stake (“PoS”), practical byzantine fault tolerance (“PBFT”), proof-of-authority (“PoA”), or the like.

“Smart contract” as used herein may refer to executable computer code or logic that may be executed according to an agreement between parties upon the occurrence of a condition precedent (e.g., a triggering event such as the receipt of a proposed data record). In some embodiments, the smart contract may be self-executing code that is stored in the distributed ledger, where the self-executing code may be executed when the condition precedent is detected by the system on which the smart contract is stored.

A “user interface” is any device or software that allows a user to input information, such as commands or data, into a device, or that allows the device to output information to the user. For example, the user interface includes a graphical user interface (GUI) or an interface to input computer-executable instructions that direct a processing device to carry out specific functions. The user interface typically employs certain input and output devices to input data received from a user or to output data to a user. These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users.

Typically, there is no way to instantly verify employment related information associated with users in real-time. As such, there exists a need for a system that provides a reliable and accurate way of instantaneously verifying employment related information associated with users in real-time. The system of the present invention solves this problem as explained in detail below.

1 FIG. 1 FIG. 100 100 300 200 201 201 301 400 110 100 110 100 400 110 provides a block diagram illustrating a system environmentfor generating and managing distributed register based entity networks, in accordance with an embodiment of the invention. As illustrated in, the environmentincludes a distributed register based entity network generation and management system, entity system, external systems, one or more entity devices, a distributed register, and a computing device system. One or more usersmay be included in the system environment, where the usersinteract with the other entities of the system environmentvia a user interface of the computing device system. In some embodiments, the one or more usersmay be employees of the entity.

200 The entity system(s)may be any system owned or otherwise controlled by an entity to support or perform one or more process steps described herein. In some embodiments, the entity may be any organization that employs one or more employees (e.g., full time employees, part time employees, contractors, sub-contractors, and/or the like). In some embodiments, the entity is a financial institution. In some embodiments, the entity is a non-financial institution.

300 300 300 200 201 201 110 The distributed register based entity network generation and management systemis a system of the present invention for performing one or more process steps described herein. In some embodiments, the distributed register based entity network generation and management systemmay be an independent system. In some embodiments, the distributed register based entity network generation and management systemmay be a part of the entity system. In some embodiments, the external systemsmay be any system associated with other entities that employ one or more employees. In some embodiments, the external systemsmay be any systems that provide information associated with the one or more users.

301 302 303 301 301 300 200 201 400 301 In some embodiments, the distributed registercomprises one or more nodes (e.g., first node, second node, through nth node). In some embodiments, the distributed registermay be a private distributed register associated with the entity. In some embodiments, the distributed registermay be a public distributed register. In some embodiments, one or more of the distributed register based entity network generation and management system, the entity system, the external systems, and the computing device systemmay be one or more nodes of the distributed register.

300 200 400 100 150 150 150 150 300 200 400 150 The distributed register based entity network generation and management system, the entity system, and the computing device systemmay be in network communication across the system environmentthrough the network. The networkmay include a local area network (LAN), a wide area network (WAN), and/or a global area network (GAN). The networkmay provide for wireline, wireless, or a combination of wireline and wireless communication between devices in the network. In one embodiment, the networkincludes the Internet. In general, the distributed register based entity network generation and management systemis configured to communicate information or instructions with the entity system, and/or the computing device systemacross the network.

400 200 110 400 110 400 110 400 300 200 150 400 The computing device systemmay be a system owned or controlled by the entity of the entity systemand/or the user. As such, the computing device systemmay be a computing device of the user. In general, the computing device systemcommunicates with the uservia a user interface of the computing device system, and in turn is configured to communicate information or instructions with the distributed register based entity network generation and management system, and/or entity systemacross the network. In some embodiments of the invention, the computing device systemmay be a mobile device.

2 FIG. 2 FIG. 200 200 220 210 230 200 200 provides a block diagram illustrating the entity system, in greater detail, in accordance with embodiments of the invention. As illustrated in, in one embodiment of the invention, the entity systemincludes one or more processing devicesoperatively coupled to a network communication interfaceand a memory device. In certain embodiments, the entity systemis operated by a first entity, such as a financial institution, while in other embodiments, the entity systemis operated by an entity other than a financial institution.

230 230 220 210 200 200 230 250 270 280 283 283 110 110 270 110 240 250 270 200 200 It should be understood that the memory devicemay include one or more databases or other data structures/repositories. The memory devicealso includes computer-executable program code that instructs the processing deviceto operate the network communication interfaceto perform certain communication functions of the entity systemdescribed herein. For example, in one embodiment of the entity system, the memory deviceincludes, but is not limited to, a distributed register based entity network generation and management application, one or more entity applications, and a data repositorycomprising user data, where the user datacomprises data associated with users(e.g., any data associated with employment associated with the users, personal information, and/or the like). The one or more entity applicationsmay be any applications provided by the entity that allows usersto access information and/or perform one or more actions associated with one or more datafiles of one or more users of the distributed register based entity network created by the system of the present invention. The computer-executable program code of the network server application, the distributed register based entity network generation and management application, the one or more entity applicationto perform certain logic, data-extraction, and data-storing functions of the entity systemdescribed herein, as well as communication functions of the entity system.

240 250 270 280 280 210 300 400 200 300 250 250 300 The network server application, the distributed register based entity network generation and management application, and the one or more entity applicationsare configured to store data in the data repositoryor to use the data stored in the data repositorywhen communicating through the network communication interfacewith the distributed register based entity network generation and management system, and/or the computing device systemto perform one or more process steps described herein. In some embodiments, the entity systemmay receive instructions from the distributed register based entity network generation and management systemvia the distributed register based entity network generation and management applicationto perform certain operations. The distributed register based entity network generation and management applicationmay be provided by the distributed register based entity network generation and management system.

3 FIG. 3 FIG. 300 300 320 310 330 300 300 300 200 300 300 200 provides a block diagram illustrating the distributed register based entity network generation and management systemin greater detail, in accordance with embodiments of the invention. As illustrated in, in one embodiment of the invention, the distributed register based entity network generation and management systemincludes one or more processing devicesoperatively coupled to a network communication interfaceand a memory device. In certain embodiments, the distributed register based entity network generation and management systemis operated by a first entity, such as a financial institution, while in other embodiments, the distributed register based entity network generation and management systemis operated by an entity other than a financial institution. In some embodiments, the distributed register based entity network generation and management systemis owned or operated by the entity of the entity system. In some embodiments, the distributed register based entity network generation and management systemmay be an independent system. In alternate embodiments, the distributed register based entity network generation and management systemmay be a part of the entity system.

330 330 320 310 300 300 330 340 350 360 370 380 385 390 330 340 350 360 370 380 385 320 300 300 It should be understood that the memory devicemay include one or more databases or other data structures/repositories. The memory devicealso includes computer-executable program code that instructs the processing deviceto perform one or more operations described herein and also to operate the network communication interfaceto perform certain communication functions of the distributed register based entity network generation and management systemdescribed herein. For example, in one embodiment of the distributed register based entity network generation and management system, the memory deviceincludes, but is not limited to, a network provisioning application, a data extraction application, an artificial intelligence engine, a separation application, an access application, a distributed register application, and a centralized data repositorycomprising data processed or accessed by one or more applications in the memory device. The computer-executable program code of the network provisioning application, the data extraction application, the artificial intelligence engine, the separation application, the access application, and the distributed register applicationmay instruct the processing deviceto perform certain logic, data-processing, and data-storing functions of the distributed register based entity network generation and management systemdescribed herein, as well as communication functions of the distributed register based entity network generation and management system.

340 350 360 370 380 385 390 310 200 400 340 350 360 370 380 385 200 400 390 340 350 360 370 380 385 340 350 360 370 380 385 5 FIG. The network provisioning application, the data extraction application, the artificial intelligence engine, the separation application, the access application, and the distributed register applicationare configured to invoke or use the data in the data repositorywhen communicating through the network communication interfacewith the entity system, and/or the computing device system. In some embodiments, the network provisioning application, the data extraction application, the artificial intelligence engine, the separation application, the access application, and the distributed register applicationmay store the data extracted or received from the entity system, and the computing device systemin the centralized data repository. In some embodiments, the network provisioning application, the data extraction application, the artificial intelligence engine, the separation application, the access application, and the distributed register applicationmay be a part of a single application. The functionalities of the network provisioning application, the data extraction application, the artificial intelligence engine, the separation application, the access application, and the distributed register applicationare explained in greater detail in.

4 FIG. 1 FIG. 400 400 provides a block diagram illustrating a computing device systemofin more detail, in accordance with embodiments of the invention. However, it should be understood that a mobile telephone is merely illustrative of one type of computing device systemthat may benefit from, employ, or otherwise be involved with embodiments of the present invention and, therefore, should not be taken to limit the scope of embodiments of the present invention. Other types of computing devices may include portable digital assistants (PDAs), pagers, mobile televisions, cameras, video recorders, audio/video player, radio, GPS devices, wearable devices, Internet-of-things devices, augmented reality devices, virtual reality devices, automated teller machine devices, electronic kiosk devices, or any combination of the aforementioned.

400 410 420 436 440 460 415 450 480 475 410 400 410 400 410 410 410 420 410 422 422 400 Some embodiments of the computing device systeminclude a processorcommunicably coupled to such devices as a memory, user output devices, user input devices, a network interface, a power source, a clock or other timer, a camera, and a positioning system device. The processor, and other processors described herein, generally include circuitry for implementing communication and/or logic functions of the computing device system. For example, the processormay include a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and/or other support circuits. Control and signal processing functions of the computing device systemare allocated between these devices according to their respective capabilities. The processorthus may also include the functionality to encode and interleave messages and data prior to modulation and transmission. The processorcan additionally include an internal data modem. Further, the processormay include functionality to operate one or more software programs, which may be stored in the memory. For example, the processormay be capable of operating a connectivity program, such as a web browser application. The web browser applicationmay then allow the computing device systemto transmit and receive web content, such as, for example, location-based content and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like.

410 460 150 460 476 474 472 410 474 472 150 400 400 The processoris configured to use the network interfaceto communicate with one or more other devices on the network. In this regard, the network interfaceincludes an antennaoperatively coupled to a transmitterand a receiver(together a “transceiver”). The processoris configured to provide signals to and receive signals from the transmitterand receiver, respectively. The signals may include signaling information in accordance with the air interface standard of the applicable cellular system of the wireless network. In this regard, the computing device systemmay be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the computing device systemmay be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like.

400 436 440 436 434 432 410 As described above, the computing device systemhas a user interface that is, like other user interfaces described herein, made up of user output devicesand/or user input devices. The user output devicesinclude a display(e.g., a liquid crystal display or the like) and a speakeror other audio device, which are operatively coupled to the processor.

440 400 110 400 110 480 The user input devices, which allow the computing device systemto receive data from a user such as the user, may include any of a number of devices allowing the computing device systemto receive data from the user, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s). The user interface may also include a camera, such as a digital camera.

400 475 400 475 475 476 474 472 400 475 400 The computing device systemmay also include a positioning system devicethat is configured to be used by a positioning system to determine a location of the computing device system. For example, the positioning system devicemay include a GPS transceiver. In some embodiments, the positioning system deviceis at least partially made up of the antenna, transmitter, and receiverdescribed above. For example, in one embodiment, triangulation of cellular signals may be used to identify the approximate or exact geographical location of the computing device system. In other embodiments, the positioning system deviceincludes a proximity sensor or transmitter, such as an RFID tag, that can sense or be sensed by devices known to be located proximate a merchant or other location to determine that the computing device systemis located proximate these known devices.

400 415 400 400 450 410 The computing device systemfurther includes a power source, such as a battery, for powering various circuits and other devices that are used to operate the computing device system. Embodiments of the computing device systemmay also include a clock or other timerconfigured to determine and, in some cases, communicate actual or relative time to the processoror one or more other devices.

400 420 410 420 420 The computing device systemalso includes a memoryoperatively coupled to the processor. As used herein, memory includes any computer readable medium (as defined herein below) configured to store data, code, or other information. The memorymay include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memorymay also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like.

420 410 400 420 422 421 424 423 424 421 434 110 200 300 420 400 423 150 421 300 110 300 424 200 421 110 300 200 424 The memorycan store any of a number of applications which comprise computer-executable instructions/code executed by the processorto implement the functions of the computing device systemand/or one or more of the process/method steps described herein. For example, the memorymay include such applications as a conventional web browser application, a distributed register based entity network generation and management application, entity application, an SMS application, or the like. In some embodiments, the entity applicationmay be an online banking application. The distributed register based entity network generation and management applicationmay comprise instructions to a graphical user interface (GUI) on the displaythat allows the userto interact with the entity system, the distributed register based entity network generation and management system, and/or other devices or systems. The memoryof the computing device systemmay comprise a Short Message Service (SMS) applicationconfigured to send, receive, and store data, information, communications, alerts, and the like via the wireless network. In some embodiments, the distributed register based entity network generation and management applicationprovided by the distributed register based entity network generation and management systemallows the userto access the distributed register based entity network generation and management system. In some embodiments, the entity applicationprovided by the entity systemand the distributed register based entity network generation and management applicationallow the userto access the functionalities provided by the distributed register based entity network generation and management systemand the entity system. In some embodiments, the entity applicationmay be an online banking application.

420 400 400 400 400 The memorycan also store any of a number of pieces of information, and data, used by the computing device systemand the applications and devices that make up the computing device systemor are in communication with the computing device systemto implement the functions of the computing device systemand/or the other systems described herein.

5 FIG. 500 505 280 283 provides a block diagram illustrating a process flowfor generating and managing distributed register based entity networks, in accordance with an embodiment of the invention. As shown in block, the system extracts user information associated with one or more users of an entity from one or more entity data repositories and one or more external systems. The one or more entity data repositories (e.g., data repositorywith user data) comprise information associated with one or more users (e.g., employees) of the entity. The one or more external systems may be any systems external to the entity that provide information associated with the one or more users. In some embodiments, the external systems may be associated with other entities associated with historical employment of the users and/or the like. Examples of external systems may include, but are not limited to, historical employers, insurance agencies, entities that issue certifications, awards, and/or the like, benefit providers, etc. The user information extracted from the one or more entity data repositories and/or the one or more external systems may comprise personal information, compensation information, employment information, historical employment information, benefits related information, work related information, work achievement related information (e.g., awards, certifications, and/or the like). In some embodiments, the user information may comprise information received from one or more users. In such embodiments, the system may communicate with external systems to validate the user information provided by the one or more users.

510 As shown in block, the system sorts the user information to split the user information into one or more levels of data. The system may sort the user information into one or more levels of data based on the nature of data (e.g., sensitive information, confidential information, private information, public information, and/or the like). For example, the system may classify employment history, certifications, skill set, and/or the like associated with a user as level ‘1’ information. In another example, the system may classify compensation related information, benefits related information, awards, and/or the like associated with the user as level ‘2’ information. In another example, the system may classify personal details (Social Security Number, Tax Identification Number, dependent information, etc.), emergency contacts, and/or the like as level ‘3’ information.

515 As shown in block, the system assigns each of the one or more levels of data to one or more access levels for accessing the user information. One or more users of entity may be associated with hierarchical structure associated with the entity and the one or more access levels may be based on the hierarchical structure. For example, users from human resources may have different levels of access (may have all levels of access) compared to users from technology department associated with an entity (may have access to only level ‘1’ information from the above example).

520 505 As shown in block, the system generates a validated record comprising the one or more levels of data associated with the one or more access levels for each of the one or more users based on the user information. The validated record generated by the system comprises authenticated and verified information. For example, the system may validate the user information described in blockfrom multiple sources for generating the validated record.

525 301 As shown in block, the system stores the validated record comprising the one or more levels of data on a distributed register (e.g., distributed register), thereby providing a layer of security to avoid inaccurate information from entering into one or more validated records of the one or more users.

530 As shown in block, the system receives a query associated with the validated record from a user device. In some embodiments, the query may be a user verification request (e.g., background check). In some embodiments, the query may be a report associated with skillset of a user. In some embodiments, the query may be associated with generation of a resume. In some embodiments, the query may be generation of a reference associated with a user.

535 As shown in block, the system extracts at least a part of the validated record associated with the query from the distributed register and display at least the part of the validated record on the user device. In some embodiments, the system may identify a type of a user associated with the user device, identify an access level of the user associated with the user device, and display a level of data corresponding to the access level of the user while addressing the query.

In some embodiments, the system may receive a request from a first user to generate a report associated with a second user of the one or more users, identify an access level of the first user, extract a level of data of the second user corresponding to the access level of the first user, generate the report associated with the second user using the extracted level of data, and display the report to the first user.

The system may generate entity networks for multiple entities with multiple validate records for each of the one or more users associated with each of the multiple entities. In some embodiments, the validated records may be transmitted from one entity to another entity. For example, if a user who was previously employed by an entity ‘A’ moves to an entity ‘B,’ the validated record may be automatically updated with information associated with the entity ‘B’ and ownership of the validated record may also be transferred from entity ‘A’ to entity ‘B.’ In some embodiments, the system may identify a type of a user associated with the user device, identify an access level of the user associated with the user device, and display a level of data corresponding to the access level of the user while addressing the query.

In some embodiments, the system may receive a change request associated with a user of the one or more users, validate the change request based on receiving the change request associated with the user, and update a level of data associated with the user based on validating the change request. For example, the system may receive a request to add a certification to a validated record of a user and the system may communicate with external systems to validate the certification before updating the validated record of the user.

In some embodiments, the system may generate one or more digital cards associated with each of the one or more users, wherein the one or more digital cards comprises a mode for accessing at least a part of the validated record associated with each of the one or more users. The mode for accessing at least a part of the validated record comprises at least one of a link and a scannable code that will allow anyone with the digital card to access at least a part of the validated record stored on the distributed register. In some embodiments, the one or more digital cards may be transferrable to other devices via a Near Field Communication technology, and/or the like. In some embodiments, the system may generate the one or more digital cards based on directly extracting data from the distributed register.

As will be appreciated by one of skill in the art, the present invention may be embodied as a method (including, for example, a computer-implemented process, a business process, and/or any other process), apparatus (including, for example, a system, machine, device, computer program product, and/or the like), or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, and the like), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium.

Any suitable transitory or non-transitory computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples of the computer readable medium include, but are not limited to, the following: an electrical connection having one or more wires; a tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, radio frequency (RF) signals, or other mediums.

Computer-executable program code for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++, or the like. However, the computer program code for carrying out operations of embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages.

Embodiments of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable program code portions. These computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the code portions, which execute via the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the code portions stored in the computer readable memory produce an article of manufacture including instruction mechanisms which implement the function/act specified in the flowchart and/or block diagram block(s).

The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the code portions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block(s). Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention.

As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function.

Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another.

While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.