Abstract: A system and method of electronic health record data qualification is presented. A Qualification List can be used in the practical application of data qualification that uses a predefined list of data to determine if the current values of input fields, which correspond to properties of the predefined list, match any item in the list according to the value of a ‘compare mnemonic’ (e.g., EQ, NE, GT, LT, GE, LE) of the corresponding input field. The system can advantageously override established processing flows by inverting determination values to direct the processing of the acquired data. Advantageously, the system can provide context for the values by retrieving data within an execution context, thereby acting as a gatekeeper to direct subsequent processing.

Abstract: A system and method of immutable electronic health record data storage is presented. The present disclosure provides for a system integrated into a practical application with meaningful limitations to provide a system having an ‘immutable data storage protocol’ used to capture database operations on an immutable ledger. The protocol can consist of one or more ‘operation codes.’ The immutable electronic health record data storage system can provide a blockchain, transaction blockchain API, a blockchain writer API, a formatting module, and a messaging module, among others, that can format, process, and store data according to an immutable data storage protocol.

Abstract: A system and method for execution context processing with addressable universal data location that can address, process, and standardize data contained in different types of memory structures is presented. The present disclosure provides for an addressable data locator system called an Execution Context Property Path (XPP) that can access a ‘property’ within a ‘Property Collection,’ a ‘property’ within a graph of nested ‘Property Collections,’ or a ‘property’ within an array of ‘Property Collections.’ An execution context is a dynamic system that can change the processing logic and data requirements of functions at runtime by passing a ‘function’ a reference to an ‘execution context’ object and have the function retrieve the data items it needs through the ‘execution context’ object. For example, when new ‘input data’ is received on a listener, the listener can spawn a new thread and an ‘execution context’ object to manage the processing of the ‘input data.

Abstract: A system and method for electronic health record permissioning and monetization that can grant or deny access to patient data and pay one or more entities for access to the data is presented. The present disclosure provides for a system configured to provide a patient the ability to: ‘grant,’ ‘deny,’ ‘update,’ and ‘revoke’ the permission to read data for a specific entity, and specific properties within that entity, from their personal data records (e.g., an electronic health record, a Global Patient Record (GPR), pharmaceutical records, demographic records, financial records, criminal records, or other suitable personal information). A Data-Read-Permission request can be a ‘Property Collection’ (PC) containing specific properties that describe the read permission rights and an amount the Data-Client is willing to offer for the Data-Read-Permission rights. This PC can be written as part of a blockchain transaction (TX1), which can be issued by the Data-Client.

Abstract: A system and method for electronic health record permissioning and monetization that can grant or deny access to patient data and pay one or more entities for access to the data is presented. The present disclosure provides for a system configured to provide a patient the ability to: ‘grant,’ ‘deny,’ ‘update,’ and ‘revoke’ the permission to read data for a specific entity, and specific properties within that entity, from their personal data records (e.g., an electronic health record, a Global Patient Record (GPR), pharmaceutical records, demographic records, financial records, criminal records, or other suitable personal information). A Data-Read-Permission request can be a ‘Property Collection’ (PC) containing specific properties that describe the read permission rights and an amount the Data-Client is willing to offer for the Data-Read-Permission rights. This PC can be written as part of a blockchain transaction (TX1), which can be issued by the Data-Client.

Abstract: A system and method of immutable electronic health record data storage is presented. The present disclosure provides for a system integrated into a practical application with meaningful limitations to provide a system having an ‘immutable data storage protocol’ used to capture database operations on an immutable ledger. The protocol can consist of one or more ‘operation codes.’ The immutable electronic health record data storage system can provide a blockchain, transaction blockchain API, a blockchain writer API, a formatting module, and a messaging module, among others, that can format, process, and store data according to an immutable data storage protocol.

Abstract: A system and method of property collection management and architecture that can organize patient data while maintaining context is presented. The present disclosure provides for a database system implementing a ‘Property Collection’ as a collection of ‘property name’ and ‘property value’ pairs, which are used to describe a ‘data entity.’ Further, the present disclosure can provide for historical access to data to track data changes. The present disclosure solves the technological problem of accessing data having differing data for the same person. The immutable electronic health record data storage system solves the aforementioned technological problem by providing a blockchain, transaction blockchain API, serialization module, and a deserialization module, among others that can format, process, and store data in a Global Patient Record (GPR).

Abstract: A patient data provision, consumption, and royalty processing system is disclosed that can facilitate patient data distribution and royalty payment. An EHR Data Utility can transfer patient clinical and pharmaceutical data from an EPOR database from data providers to data consumers with real-time (sub-millisecond delay), secure access. Only the data requested can be provided with each request. The present disclosure can facilitate settlement between the data consumer and the data provider that can result in the exchange of digital currency (Bitcoin SV), cryptocurrency (e.g., Bitcoin®, etc.), utility tokens (such as 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.

Abstract: An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities that can act as data, service, product providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR Data API can access and retrieve patient identifiable information (PII) and generate a non-patient-identifiable Single Purpose Patient ID (SPPID) for a particular patient. The EHR patient transaction blockchain API (e.g., EHR-DATA-BC-API) can store the SPPID, store particular, discrete data retrieved from the EHR for a patient, execute smart contracts, and control the execution of digital currency transfers, among other functions.

Abstract: An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities and healthcare providers that can act as data, service, product and service providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR data blockchain system can provide workflow on the blockchain that can utilize smart contracts to define workflow processes, expected outcomes, and financial costs. When a prescription transaction is complete, it will result in the settlement of each of the smart contracts that were added to the prescription workflow.