Back to results
US 12,027,244 B2Granted
Healthcare transaction validation via blockchain systems and methods
AssigneeNant Holdings IP, LLC
InventorNicholas J. Witchey
Life of this patent
Estimating the term…
Abstract
Healthcare transaction validation systems and methods are presented. Healthcare transactions associated with a stakeholder are compiled into a chain of healthcare transaction blocks. The chain can be considered a chronicle of person's healthcare path through life. When a transaction is conducted, the corresponding healthcare parameters (e.g., inputs, outputs, clinical evidence, outcomes, etc.) are sent to one or more validation devices. The devices establish a validity of the transaction and generate a new block via a proof-of-work principle. Once the new block has been calculated it can be appended to the stakeholder's health care blockchain.
Claims27
A method of validating healthcare transactions, the method comprising:
- receiving, by a validation client processor, at least one healthcare transaction comprising at least one encrypted pointer to at least one electronic medical record in one or more data formats regarding one or more healthcare actions taken with respect to at least one healthcare stakeholder wherein the at least one encrypted pointer conforms to an address space used by a plurality of distributed nodes across a computer network operable for storing the at least one electronic medical record;
- obtaining, by the validation client processor, a historical block identifier from a healthcare historical blockchain representative of historical healthcare actions taken with respect to the at least one healthcare stakeholder;
- obtaining, by the validation client processor via a healthcare historical blockchain name service (HNS), healthcare transaction data regarding the one or more healthcare actions from the at least one electronic medical record, wherein the healthcare transaction data is obtained based on providing the encrypted pointer to the HNS;
- receiving, by the validation client processor, a validity requirement, wherein the validity requirement describes criteria to be satisfied before a validity block for the healthcare transaction can be generated;
- determining, by the validation client processor, a format of the healthcare transaction data, wherein the validation client processor converts the format of the healthcare transaction data into a presentation format if the healthcare transaction data is not readable;
- generating, by the validation client processor and in accordance with the validity requirement, the validity block for the at least one healthcare transaction, wherein the validity block comprises the at least one healthcare transaction, and wherein the validity block is generated as a function of at least the following healthcare parameters:
- the historical block identifier and the healthcare transaction data;
- after the validity requirement is satisfied, transmitting the validity block to one or more other validation client processors for verification;
- and
- updating the healthcare historical blockchain and a locally stored healthcare historical blockchain with the validity block when a predetermined number of the one or more other validation client processors verify the validity block.
7 more elements
A computer program product for validating at least one healthcare transaction, comprising one or more machine-readable instructions stored in a non-transitory computer readable medium, wherein the one or more machine-readable instructions, upon execution by at least one processor, perform processing comprising:
- receiving, by a validation client processor, at least one healthcare transaction comprising at least one encrypted pointer to at least one electronic medical record in one or more data formats regarding one or more healthcare actions taken with respect to at least one healthcare stakeholder wherein the at least one encrypted pointer conforms to an address space used by a plurality of distributed nodes across a computer network operable for storing the at least one electronic medical record;
- obtaining, by the validation client processor, a historical block identifier from a healthcare historical blockchain representative of historical healthcare actions taken with respect to the healthcare stakeholder;
- obtaining, by the validation client processor via a healthcare historical blockchain name service (HNS), healthcare transaction data regarding the one or more healthcare actions from the at least one electronic medical record, wherein the healthcare transaction data is obtained based on providing the encrypted pointer to the HNS;
- receiving, by the validation client processor, a validity requirement, wherein the validity requirement describes criteria to be satisfied before a validity block for the healthcare transaction is generated;
- determining, by the validation client processor, a format of the healthcare transaction data, wherein the validation client processor converts the format of the healthcare transaction data into a presentation format if the healthcare transaction data is not readable;
- generating, by the validation client processor and in accordance with the validity requirement, the validity block for the at least one healthcare transaction, wherein the validity block comprises the at least one healthcare transaction, and wherein the validity block is generated as a function of at least the following healthcare parameters:
- the historical block identifier and the healthcare transaction data;
- and
- after the validity requirement is satisfied, transmitting the validity block to one or more other validation client processors for validation;
- and
- updating the healthcare historical blockchain and a locally stored healthcare historical blockchain with the validity block when a predetermined number of the one or more other validation client processors verify the validity block.
8 more elements
Dependencies are inferred from the claim text.