US-12619966-B2 - System and method for data provider tracking and monetization

US12619966B2US 12619966 B2US12619966 B2US 12619966B2US-12619966-B2

Abstract

A data provider tracking and monetization system is disclosed that can provide data aggregation infrastructure, tracking, and monetization. The present disclosure achieves the technological advantage of organizing data that is received from multiple data providers for a single person to provide any missing data. The data providers can be tracked via the provision of their data, such that they can be incentivized for providing the data. The present disclosure improves traditional systems by generating a data structure that includes metadata to identify data providers and data requestors to minimize network congestion, uncategorized data, and stale data that ravages traditional systems. Further by publishing the transactions on a distributed ledger, such as a blockchain, the request for data and all of the contributions thereto provide an open, verifiable, and immutable record of the transaction.

Inventors

Ronald R. Austring
Kenneth A. Hill, SR.

Assignees

SYNERIO TECHNOLOGIES, INC.

Dates

Publication Date: 20260505
Application Date: 20201125

Claims (20)

1 . A method of providing real-time patient data royalty calculation by a computing system, the computing system including one or more processors configured to execute computer program instructions, comprising: spawning a first computer process configured to execute a first set of computer program instructions of the computer program instructions; spawning, concurrently with the spawning of the first computer process, a second computer process configured to execute a second set of computer program instructions of the computer program instructions, wherein a combination of the first set of computer program instructions and the second set of computer program instructions is configured to perform the steps of the method of providing real-time patient data royalty calculation; receiving a request having one or more patient data parameters from a client via an encrypted network; generating a version node as a child of an instance node, via a utility, having one or more property operations related to a patient and a data-provider-id identifying each of one or more data providers of the one or more property operations; organizing, via a global person record node hierarchy having a plurality of nodes, data received from the one or more data providers responsive to the request, wherein the organizing includes: identifying, via the utility, missing data in a property collection associated with the patient and created from the request using the one or more property operations; retrieving, via the utility, the missing data from one or more other property collections associated with the patient and created from the request using the one or more property operations; adding, via the utility, the retrieved missing data to the property collection; and annotating the property collection with a property operation identifying the data provider that provided the missing data; tracking, via the utility, the one or more data providers, the data-provider-id of each of the one or more data providers, and the data provided, and appending metadata identifying the origin of the provided data into one of the plurality of nodes based on the annotated property collection; calculating, via one or more processors, fixed or variable royalties based upon data category, data size, request attributes payable to each of the one or more data providers, the utility, and the patient, based on a royalty scheme; and paying the royalty amounts to each of the one or more data providers, the utility, and the patient.
2 . The method of claim 1 , wherein the royalty scheme is based on characteristics of the data-consumer consuming the data.
3 . The method of claim 2 , wherein the characteristics include a payment method, data volume, location, contract type.
4 . The method of claim 1 , wherein the instance node and the version node is stored on a blockchain.
5 . The method of claim 1 , wherein the royalty scheme is based on, an entity type of the data being consumed.
6 . The method of claim 1 , wherein the royalty scheme is based on a computation-provider result.
7 . The method of claim 1 , wherein the royalty scheme is based on the size of the data being consumed.
8 . The method of claim 1 , wherein the royalty amount is calculated using an equal percentage.
9 . The method of claim 1 , wherein the royalty amount is calculated using a weighted percentage based on a weighted multiplier.
10 . The method of claim 9 , wherein the weighted multiplier is based on the correlation of an entity type and a property collection category.
11 . A system for providing real-time patient data royalty calculation, comprising: a memory storing one or more patient data parameters; and a processor operably coupled to the memory and configured to execute machine-readable instructions, wherein the configuration of the processor to execute the machine-readable instructions includes configuration to spawn a first computer process configured to execute a first set of instructions of the machine-readable instructions and to spawn a second computer process configured to execute a second set of instructions of the machine-readable instructions, wherein the first computer process and the second computer process are spawned concurrently, wherein a combination of the first set of computer program instructions and the second set of computer program instructions is configured to perform program steps comprising: receiving a request having one or more patient data parameters from a client via an encrypted network; generating a version node as a child of an instance node, via a utility, having one or more property operations related to a patient and a data-provider-id identifying each of one or more data providers of the one or more property operations; organizing, via a global person record node hierarchy having a plurality of nodes, data received from the one or more data providers responsive to the request, wherein the organizing includes: identifying, via the utility, missing data in a property collection associated with the patient and created from the request using the one or more property operations; retrieving, via the utility, the missing data from one or more other property collections associated with the patient and created from the request using the one or more property operations; adding, via the utility, the retrieved missing data to the property collection; and annotating the property collection with a property operation identifying the data provider that provided the missing data; tracking, via the utility, the one or more data providers, the data-provider-id of each of the one or more data providers, and the data provided, and appending metadata identifying the origin of the provided data into one of the plurality of nodes based on the annotated property collection; calculating, via one or more processors, fixed or variable royalties based upon data category, data size, request attributes payable to each of the one or more data providers, the utility, and the patient, based on a royalty scheme; and paying the royalty amounts to each of the one or more data providers, the utility, and the patient.
12 . The system of claim 11 , wherein the royalty scheme is based on characteristics of the data-consumer consuming the data.
13 . The system of claim 12 , wherein the characteristics include a payment method, data volume, location, contract type.
14 . The system of claim 11 , wherein the instance node and the version node is stored on a blockchain.
15 . The system of claim 11 , wherein the royalty scheme is based on, an entity type of the data being consumed.
16 . The system of claim 11 , wherein the royalty scheme is based on a computation-provider result.
17 . The system of claim 11 , wherein the royalty scheme is based on the size of the data being consumed.
18 . The system of claim 11 , wherein the royalty amount is calculated using an equal percentage.
19 . The system of claim 11 , wherein the royalty amount is calculated using a weighted percentage based on a weighted multiplier.
20 . The system of claim 19 , wherein the weighted multiplier is based on the correlation of an entity type and a property collection category.

Description

CROSS REFERENCE TO RELATED APPLICATIONS The present application claims priority to U.S. Provisional Application Ser. No. 63/080,412, filed on Sep. 18, 2020, entitled “PATIENT DATA PROVISION, CONSUMPTION, AND ROYALTY PROCESSING SYSTEM,” and U.S. Provisional Application Ser. No. 63/110,807, filed on Nov. 6, 2020, entitled “DATA PROVIDER TRACKING AND MONETIZATION SYSTEM,” the entirety of both provisional applications is incorporated herein by reference. TECHNICAL FIELD The present disclosure generally relates to patient data processing systems, and more specifically to patient data processing systems configured to track data and exchange currency between multiple entities. BACKGROUND Numerous healthcare providers participate in each phase of care. Healthcare service providers, including pharmacies, physicians, hospitals, laboratories, clinics, medical institutions, and regulatory agencies that develop clinical standards of care, historically have operated their own data systems, typically according to unique and different formats and processes. A network of three database components aggregate and maintain patient data from a plurality of sources. The three database components include a structured healthcare database called electronic patient outcome data (“EPO data”); an electronic pharmacy record (“ePR”) database; and an electronic patient outcome record (“EPOR”) database that is populated by data from the EPO data and ePR databases. A patient's private information, including the patient's name, address, phone number, social security number, insurance information, medical history, clinical information, and other relevant information, can be stored in an Electronic Health Record (EHR) database, such as an Electronic Patient Outcome Record (EPOR), Solid POD, XML, file, or other suitable data storage element. Often times a “complete” picture of a patient is not realizable due to different “holes” in a patient's EPO data. These holes exist because typically, each generator of patient data specializes in only its particular area and has no means to consume and provided data from other generator of patient data for a particular patient. No data structure has been proffered to handle all of the disparate data generated by various data generators for a patient. Even more difficult would be to incorporate non-healthcare data in an attempt to generate a “complete” picture of a person that extends beyond a patient. Further, there has been no incentive for patient data generators to share their data with others. The sharing of data has an inherent cost associated with the maintenance and transfer of that data. With tightening budgets and diminishing support, even in-person requests for medical records can take months to acquire. SUMMARY The present disclosure achieves technical advantages as a data provider tracking and monetization systems adapted to provide data aggregation infrastructure, tracking, and monetization. The present disclosure achieves the technological advantage of organizing data that is received from multiple data providers for a single person to provide any missing data. The data providers can be tracked via the provision of their data, such that they can be incentivized for providing the data. The present disclosure improves traditional systems by generating a data structure that includes metadata to identify data providers and data requestors to minimize network congestion, uncategorized data, and stale data that ravages traditional systems. Further by publishing the transactions on a distributed ledger, such as a blockchain, the request for data and all of the contributions thereto provide an open, verifiable, and immutable record of the transaction. Such record can be easily audited to ensure compliance with various laws and regulations. In particular, the present disclosure improves the performance of traditional systems by facilitating settlement between the data-consumer and the data-provider that can result in the exchange of a digital currency (Bitcoin SV), cryptocurrency (e.g., Bitcoin®, etc.), utility tokens (e.g., EHRCash™) vouchers, wire transfers, ACH transactions, or other suitable currency, between the parties involved in the patient data request and provisioning. The present disclosure can eliminate the need for standard accounting processes (e.g., invoicing, statements, accounts receivable and accounts payable) in order to transfer money between data exchange partners. Advantageously, the present disclosure advances the state of the art by providing various algorithms implemented by one or more processors that can calculate fixed and variable royalties based upon data category, data size, request attributes, or other relevant thresholds or metrics. The present disclosure can implement an EHR data blockchain system (including an EHR Data API and an EHR transaction blockchain) that can provide a centralized patient data processing location that creates transparency, immutable verificati