Blockchain-based healthcare security and interoperability
Encrypting and decrypting information blocks in the healthcare system through multidimensional blockchain technology and smart contracts, solving the problem of information silos, improving the security and interoperability of information, and reducing system costs and patient risks.
Patent Information
- Application Number
- CN202080009729.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-01-18
- Filing Date
- 2020-01-16
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2040-01-16
AI Technical Summary
Due to privacy regulations and business value restrictions, healthcare information systems have led to information silos, reducing the interoperability and security of information, increasing system costs and patient risks, and limiting the efficiency and efficacy of medical treatment.
The method implemented through processors uses multidimensional blockchain technology to encrypt the decryption and linking of information blocks in the healthcare system, ensuring the security and integrity of information, while improving information sharing and interoperability between entities, using smart contracts Manage information interfaces and data sharing, and comply with legal and business guidelines.
The security and interoperability of healthcare information is achieved, ensuring the availability and consistency of information among different entities, reducing system costs, and improving treatment efficiency and patient safety.
Smart Images

Figure CN113302872B_ABST
Abstract
Description
Technical Field
[0001] The subject matter disclosed herein relates to security of healthcare systems and interoperability of healthcare systems. Background Art
[0002] Healthcare information systems face compliance challenges that limit interoperability. For example, stored information may be subject to various privacy regulations, such as the Health Insurance Portability and Accountability Act (HIPAA). The privacy provisions of HIPAA establish national standards for protecting personal medical records and other personal health information when healthcare transactions are conducted electronically. These regulations may cover privacy (e.g., which entities can access the information), content (which information can be accessed by authorized entities), security (how to protect information from being accessed by unauthorized entities when stored and during electronic communications), and integrity (the accuracy and authenticity of the information). In addition, information with commercial value may be protected by organizational policies that may restrict sharing of information with third parties (e.g., as a trade secret and / or for business or commercial reasons). Regulations such as the EU General Data Protection Regulation may also affect information collection, storage, sharing, and communication. These regulations have affected the information available to healthcare market participants and have led to the creation of organizational "data silos", in which the information available to entities is isolated, even when it may be useful on the system (e.g., for another non-competitive entity). This compartmentalization of information has resulted in increased system costs (e.g., costs to medical providers to consider treatment alternatives), increased risks to patients (e.g., due to drug interactions, prescription abuse, etc.), and limited efficacy of outcome-based medical treatments or remedies (e.g., making it more difficult and expensive to determine when a desired outcome has been achieved or to compare metrics among approaches to achieving similar outcomes). Therefore, methods that address one or more of the above issues are needed that will help facilitate the security of healthcare information while increasing interoperability among market participants. Summary of the invention
[0003] In some embodiments, a processor-implemented method may include: in response to a transaction conducted at a first time, receiving, at a first entity, an encrypted information block related to the transaction from one or more second entities, wherein each encrypted information block is received from a different second entity and each encrypted information block includes at least one sub-block that can be decrypted by the first entity; decrypting the decryptable sub-block by the first entity; enhancing, by the first entity, a multidimensional block chain, wherein the multidimensional block chain is enhanced with a multidimensional block, the multidimensional block being formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity; and enabling at least one of the one or more second entities to access the multidimensional block chain.
[0004] On the other hand, a server for a first entity may include: a memory, a communication interface, and a processor coupled to the memory and the communication interface. In some embodiments, the processor may be configured to: in response to a transaction conducted at a first time, receive, at the first entity, through the communication interface, an encrypted information block related to the transaction from one or more second entities, wherein each encrypted information block is received from a different second entity and each encrypted information block includes at least one sub-block that can be decrypted by the first entity; decrypt the decryptable sub-block by the first entity; enhance, by the first entity, a multidimensional block chain residing in the memory, wherein the multidimensional block chain is enhanced with a multidimensional block, the multidimensional block being formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity; and enable at least one of the one or more second entities to access the multidimensional block chain.
[0005] On the other hand, an apparatus may include: a device for receiving, at a first entity, encrypted information blocks related to a transaction conducted at a first time from one or more second entities, wherein each encrypted information block is received from a different second entity and each encrypted information block includes at least one sub-block that can be decrypted by the first entity; a device for decrypting the decryptable sub-block by the first entity; a device for enhancing a multidimensional block chain by the first entity, wherein the multidimensional block chain is enhanced with a multidimensional block, the multidimensional block being formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity; and a device for enabling at least one of the one or more second entities to access the multidimensional block chain.
[0006] In some embodiments, a non-transitory computer-readable medium may include executable instructions to configure a processor to: in response to a transaction conducted at a first time, receive, at the first entity through the communication interface, an encrypted information block related to the transaction from one or more second entities, wherein each encrypted information block is received from a different second entity and each encrypted information block includes at least one sub-block that can be decrypted by the first entity; decrypt the decryptable sub-block by the first entity; enhance, by the first entity, a multidimensional block chain residing in the memory, wherein the multidimensional block chain is enhanced with a multidimensional block, the multidimensional block being formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity; and enable at least one of the one or more second entities to access the multidimensional block chain.
[0007] The disclosed methods may be performed by one or more computers (including servers, cloud-based systems, etc.) using a computer-readable medium or a computer-readable memory. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings.
[0009] Figure 1A A schematic block diagram illustrating the operation of a conventional healthcare information system is shown.
[0010] Figure 1B A conventional implementation of a contract associated with a traditional blockchain system is shown.
[0011] Figure 2 An exemplary electronic health record (EHR) is shown, illustrating some exemplary data fields in the record.
[0012] Figure 3 An exemplary medication information record (DIR) is shown.
[0013] Figure 4 An exemplary health transaction record (HTR) is shown.
[0014] Figure 5A An exemplary HTR information block including a plurality of sub-blocks is shown.
[0015] Figure 5B An EHR information block, a DIR information block and an HTR information block are shown depicting some sub-blocks associated with the information block.
[0016] Fig. 6A The transaction flow associated with a multi-dimensional block is shown.
[0017] Figure 6B An exemplary Merkle tree associated with a multi-dimensional blockchain is shown, the multi-dimensional blockchain including a plurality of data records that may be associated with different respective blockchains.
[0018] Figure 6C An exemplary architecture of a system that facilitates security and interoperability of healthcare information is shown.
[0019] Fig.6D is a visual depiction of multi-dimensional blocks that may be associated with exemplary automated outcome-based contract fulfillment.
[0020] Figure 7 A flow chart illustrating an exemplary method for facilitating security and interoperability of healthcare information.
[0021] Figure 8 Smart contracts associated with the smart contract layer are shown.
[0022] Fig. 9 An exemplary computer that can facilitate security and improve interoperability in a healthcare system is shown. DETAILED DESCRIPTION
[0023] The disclosed embodiments of the present invention facilitate the security of healthcare systems while improving the integrity and interoperability of healthcare systems.
[0024] Figure 1A A schematic block diagram illustrating the operation of a conventional healthcare information system 100 is shown. A healthcare transaction may involve several entities, each of which may have some information related to the transaction that may be used to complete the transaction. Therefore, in conventional systems, some limited information may be exchanged between the transaction entities in order to complete the transaction. As used herein, the term "entity" may refer to an individual (such as a patient or patient group) / organization or a participant participating in the healthcare market on behalf of the individual / group / organization and / or a computing system and information system (e.g., hardware and / or software) associated with the individual / group / organization. For example, a computing system associated with one entity may process information and / or exchange information with computing systems associated with other entities. The exchange of information between entities may be conducted in a secure manner (e.g., using encryption) over a secure communications network and / or over the Internet.
[0025] An entity, such as a patient (not shown in FIG. 1 ), may seek treatment for a medical condition afflicting the patient from another entity, such as a healthcare provider (HCP) 120. Based on the patient's health information 125, which may be maintained by the HCP 120 (or obtained by the HCP 120 from the patient), the HCP 120 may determine patient insurance and treatment information 124. As shown in FIG. 1 , the HCP 120 may send the patient insurance and treatment information 124 to a payer / insurance company (hereinafter referred to as a "payer") 140. The insurance-related and treatment information 124 may include patient identification (ID) information, insurance plan information, group ID information for recommended treatments, and the like. However, the patient insurance and treatment information 124 may not include the patient's family history and / or other patient information that may not be relevant to coverage and / or cost determinations, and / or may be blocked (e.g., by regulation) from being shared with the payer 140.
[0026] The payer 140 may compare the received insurance-related information 124 with information in a plan / coverage database 145 to determine coverage for the patient. Based on the coverage information, the payer 140 may update a transaction information database 147 and provide the HCP 120 with patient coverage-related information 142. The coverage-related information may include approval / denial information, coverage information related to the proposed treatment, and cost- and payment-related information, such as patient copayments, billing codes, etc. If the payer denies approval, or the coverage for the proposed treatment is insufficient and / or does not meet the patient's cost criteria, the HCP may propose a revision, which may result in further exchange of information between the HCP 120 and the payer 140.
[0027] In addition, when prescribing a recommended treatment, the HCP 120 may also send treatment information 123 to a drug provider and / or medical device provider (PMDP) 130. The treatment information 123 may include information related to the medical condition that troubles the patient, other drugs that the patient is using. However, the treatment information 123 may not include any personally identifiable information (PII) related to the patient. In response, the PMDP 130 may send a drug / device overview and safety information 132 to the HCP 120. The drug / device overview and safety information may include information about drug properties, such as dosage, mode of administration, absorption, metabolism, duration of action, toxicity, and interactions with food or other drugs. Upon receiving the drug / device overview and safety information 132, the HCP may prescribe drugs and / or medical devices, or may revise the prescription based on the drug / device overview and safety information 132. The interaction between HCP 120 , payor 140 , and PMDP 130 may continue until HCP 120 completes a treatment plan that is (a) acceptable to the patient, (b) meets safety and efficacy considerations, and (c) can be covered and / or approved by payor 140 .
[0028] Therefore, conventional healthcare information systems have several disadvantages. Although each entity obtains and maintains information that may be relevant to running its business, only very little of the information is shared (e.g., due to legal, privacy and / or business considerations), and when information is shared, the information is usually fragmented, without context and may be unavailable. For example, HCP 120 may not provide details of adverse drug reactions to PMDP 130. For another example, when HCP 120 provides adverse drug reaction information to PMDP 130, the information may not include non-PII demographic information (e.g., the patient's age, location, medical conditions, etc.), so the information may have limited value to PMDP 130. In addition, in some cases, when an entity (e.g., a patient) reports an adverse drug reaction, the adverse drug reaction may be verified by another entity (e.g., HCP 120) to determine whether the adverse event is attributable to a prescribed drug. Verification (which may involve additional entities) may introduce additional complexity, which may further delay reporting and / or create additional silos, further limiting the usefulness of the information (eg, to PMDP 130).
[0029] In addition, because information is divided and can be provided on a temporary basis, it may be troublesome to aggregate the received information with the information stored by the receiving entity. In addition, because each entity can index information in different ways, it may be difficult or impossible for the receiving entity (or the sending entity) to bind the received (or sent) information to the origin of the transmitted information (e.g., stored by the sending entity) recorded information. For example, if HCP 120 provides adverse drug reaction information to PMDP 130 at a certain point in time, even when the information can be legally shared, HCP 120 and / or PMDP 130 may also be difficult to obtain additional patient or patient medical condition information related to adverse drug reaction. For example, the division of information can prevent or limit PMDP 130 from accessing to aggregate demographic information that can be used for customized drug utilization. For another example, when formulating a prescription or treatment plan, the patient or HCP 120 may not be able to obtain the cost of various treatment alternatives. For another example, HCP 120 and / or payer 140 may be difficult to determine that the patient abuses the prescription.
[0030] Many modern machine learning (ML) and other artificial intelligence (AI) systems process large amounts of data to identify hazards, recognize patterns that lead to desired outcomes, etc., which can lead to increased efficiency, reduced costs, and / or better outcomes. The siloing and compartmentalization of information also limits the applicability of such ML and AI techniques, leading to inefficiencies.
[0031] Some attempts to improve the efficiency of healthcare delivery focus on outcome-based approaches. Payers 140 may associate reimbursement with the achievement of some agreed outcomes. For example, an outcome-based contract may specify that the HCP 120 will be reimbursed at an agreed rate based on the patient's blood pressure being reduced to a certain defined range within a certain time period. In conventional systems, tracking and managing such outcome-based contracts may be very difficult because several information exchanges may be required between the HCP 120 and the payer 140, each of which complies with legal, regulatory, privacy, and business-related guidelines.
[0032] Figure 1B The conventional implementation of contracts associated with traditional block chain systems is shown. Figure 1B As shown, program code may implement a contract 156 between entity A 163 and entity B 165. In conventional systems, information may be exchanged between entity A 163 and entity B 165 separately (e.g., as described above with respect to Figure 1A 156), the program code associated with contract 156 can then use this information to implement the contract. Conventional implementations have several disadvantages. First, in conventional implementations, the program code associated with contract 156 may be bound to an entity (e.g., entity A 163) and therefore may not be used to implement other contracts related to other entities (e.g., not involving entity A).
[0033] Furthermore, in conventional systems, program code associated with a contract is specific to the two entities associated with the contract. Thus, if another entity, such as entity C 167, is to be associated with contract 156, then in conventional systems, additional code associated with the following items is typically added to relate to entity C 167: (a) Appendix 1 152 (to reflect the interaction between entity A 163 and entity C 167, and (b) Appendix 2 154 (to reflect the interaction between entity B 165 and entity D 169). Therefore, as the number of entities associated with a contract increases, the complexity of the system increases dramatically, thereby increasing the cost of contract management (coding costs, maintenance costs, etc.), while also increasing the possibility of errors and making contract changes difficult or impractical. In addition, because information is shared externally between entities, the possibility of errors and / or data inconsistencies is greatly increased. In addition, in many conventional systems where a contract is used with multiple instances of an entity (e.g., hundreds of patients associated with an HCP who are being treated for a certain condition), the contract is often repeated between these instances. Therefore, contract changes (e.g., indicating approval of a new drug to treat a condition) may not be easy and may take a long time to propagate in the system, thereby limiting the practicality of the platform. In the above cases, manual approval or manual intervention is often the norm, negating the advantages of the contract management platform. Although the use of a block chain to store health-related information can be beneficial for ensuring the integrity and authenticity of the stored information, conventional technologies do not address the problem of information partitioning, complexity, or do not ensure that different entities have a coherent and consistent view of the stored transactions, which is not conducive to interoperability.
[0034] The disclosed embodiments of the present invention are beneficial to the security of the healthcare system while improving the integrity and interoperability of the healthcare system. Some disclosed technologies are beneficial to timely exchange of appropriate data (e.g., in compliance with legal, privacy and business guidelines) to appropriate entities (e.g., authorized entities associated with the transaction) (e.g., at the time of the transaction), while being beneficial to a consistent and coherent view of information across healthcare market entities. Part of the reason for being beneficial to interoperability is that multiple entities associated with the transaction may be able to bind the information shared during the transaction to the transaction using an agreed reference. The reason for being beneficial to consistency and coherence is that the data recorded locally may correspond to the reference data and the reference data view of each entity (or the part of the reference data that can be viewed by the entity) is consistent with the data view of another authorized entity. In some embodiments, the reference data may be based on a distributed ledger and / or in the form of a distributed ledger. In some embodiments, the distributed ledger may be accessed by authorized entities, and the view of the distributed ledger of each entity may comply with legal, privacy, business and / or contractual obligations.
[0035] In some embodiments, in response to a transaction conducted at a first time, a first entity (e.g., a drug provider) may receive an encrypted information block related to the transaction from one or more second entities (e.g., a healthcare provider and / or an insurance provider and / or a patient). Each encrypted information block may be received from a different second entity, and each encrypted information block may include at least one sub-block that can be decrypted by the first entity. The first entity (e.g., a drug provider) may decrypt one or more of the received decryptable sub-blocks. In some embodiments, the first entity may also enhance a multidimensional block chain with a multidimensional block. A multidimensional block may be formed by linking at least one encrypted information block in the encrypted information block received from the one or more second entities to a current block added to a block chain, the block chain being associated with a transaction in which the block chain is maintained by the first entity. The first entity (e.g., a drug provider) may enable at least one second entity (e.g., a healthcare provider and / or an insurance provider and / or a patient) to access the multidimensional block chain.
[0036] The sub-blocks (in the received encrypted block) that are decryptable by the first entity may include or point to information that is viewable by the first entity (e.g., in compliance with legal, privacy, and / or business guidelines). Conversely, information outside of the decryptable sub-blocks may not be viewable by the first entity (e.g., a drug provider), but may be available to a second entity (e.g., a healthcare provider) that transmits the corresponding encrypted block. In addition, each encrypted block received by the first entity may: (i) be related to a transaction, and / or (ii) form part of a corresponding block chain maintained by the second entity (e.g., a healthcare provider) that transmits the corresponding encrypted block. In some embodiments, the current block added to the block chain maintained by the first entity may also include sub-blocks, each sub-block having information that is decryptable by the corresponding second entity, while information outside of the corresponding sub-block may not be viewable by the second entity. The term "sub-block" indicates a portion of a data record or block that is decryptable by one or more specific entities. Thus, a coherent and consistent view of a transaction may be obtained by a market entity while maintaining compliance with legal, privacy, and / or other regulatory and business considerations and improving data integrity.
[0037] As used herein, the term "block chain" refers to a growable list of records or "information blocks" or "blocks" where the blocks are linked using cryptographic techniques. Each block includes a cryptographic hash of the previous block, a timestamp, and transaction data. The current block added to the block chain is also referred to as the head of the block chain. A cryptographic hash function maps data of any size to a fixed-size bit string, which is called a "hash". A hash function can be deterministic (the same input will produce the same output) and can be a one-way function that cannot be reversed (i.e., the original data input is determined from the hash value). The transaction data of a block can be represented as a Merkle tree root hash. The term "Merkle tree" or "hash tree" is used to refer to a tree in which each leaf node is marked with a hash of the transaction data and each non-leaf node is marked with a cryptographic hash of the tag associated with its child node. The block header of a block to be added to the block chain may include a hash reference to the previous block header and a hash reference to the root of the Merkle tree containing the transaction data. Blockchain improves data integrity because changes to data in the block chain result in inconsistencies in one or more of the hash references. The term "record" or "data record" is also used to indicate non-final data to be added to the block chain. Once a data record has been verified and completed, it can be added to the block chain and form a block in the block chain.
[0038] The term "multidimensional block chain" is used to refer to a sequence of multidimensional records (also referred to as multidimensional blocks), wherein each multidimensional record includes two or more data records. In some cases, each data record in the data records of the dimensions forming the multidimensional block chain can form a block in a different block chain associated with a certain entity. Therefore, in some embodiments, the multidimensional block may include data records in each dimension, wherein the data records corresponding to the dimension can form a block in different conventional block chains associated with the corresponding entity. For example, a multidimensional block may include an EHR data record as one dimension, a DIR data record as another dimension, and a transaction data record as a third dimension. In addition, in some cases, the EHR data records associated with the multidimensional block (in the multidimensional block chain) can form blocks separately in different EHR block chains (i.e., different from the multidimensional block chain). Similarly, in some cases, the DIR data records and transaction data records associated with the multidimensional block can each form blocks in different DIR block chains (e.g., associated with PMDP 130) and transaction record block chains (e.g., associated with payer 140). Therefore, in some cases, data records in the context of a multidimensional block chain may correspond to blocks in different conventional block chains. In some cases, each data record in a multidimensional block (e.g., associated with a dimension) may correspond to a corresponding block in a different conventional block chain, form a part of the corresponding block, and / or originate from the corresponding block. A multidimensional block may include an encrypted hash, a timestamp, and data of a previous multidimensional block. The data of a multidimensional block may include a hash of the individual data records that make up the multidimensional block. In some embodiments, a consensus mechanism between entities may be used to confirm the correctness of the data in the proposed multidimensional block before the multidimensional block is submitted and locked.
[0039] Thus, a multidimensional block may include two or more encrypted data records, each of which may be associated with a different entity (e.g., in a healthcare market). As described above, data records in a multidimensional block may be individually formed into blocks in different block chains, each of which may be associated with a different entity. Each encrypted data record may be decryptable by a corresponding associated entity (e.g., a data record owner). In addition, an encrypted data record may include a portion (referred to as a "sub-block") that may be decryptable (or may have been decryptable) by at least one other specific entity other than the encrypted data record owner. For example, when forming a corresponding multidimensional block, a sub-block may have been decryptable by at least one other different entity (other than the data record owner). In some embodiments, when forming a multidimensional block, the sub-block may be individually encrypted and made available to another entity along with information for decrypting the sub-blocks. Thus, a multidimensional block may facilitate the availability of transaction data to multiple entities associated with a healthcare market, while providing a coherent and consistent view of the data to authorized market entities, complying with regulations, business guidelines and / or contractual obligations, and improving data integrity. The entity may also ensure data relevance with a corresponding block in a locally maintained blockchain (e.g., data relevance of a record associated with a dimension of a multidimensional block in a multidimensional blockchain). In an embodiment, when information is exchanged between two entities using sub-blocks, the information exchanged via the decryptable sub-blocks may be based on an information interface between the two entities. In some embodiments, when exchanging information (e.g., when a multidimensional block is formed), each entity may encrypt a block associated with a local blockchain maintained by the entity while generating sub-blocks that can be decrypted by the other entity. The information interface may be based on a smart contract associated with the blockchain.
[0040] The term "smart contract" is used to refer to program code or logic associated with a blockchain or blockchain platform. A "smart contract" may encode rules or agreements between two or more entities related to data sharing, transactions, access, contract performance, etc. A smart contract may be based on a contract between two or more entities and / or an agreement related to a multi-dimensional blockchain platform. For example, a "smart contract" program code associated with a multi-dimensional blockchain may process a transaction request and determine the validity of the transaction based on program logic.
[0041] Figure 2 An EHR 200 is shown showing some exemplary data fields in a record. In some embodiments, the EHR 200 may include information about a patient. The fields shown in the EHR 200 are exemplary only, and the EHR 200 may include various other additional fields based on laws, standards, HCPs, and / or industry practices, etc. The EHR may include fields that are different (fewer or more) than those shown with respect to the exemplary EHR 200.
[0042] For example, Figure 2 As shown, EHR 200 may include basic profile information 230 about the patient, which may change relatively little. Basic profile information 230 may include family history 205, date of birth (DOB) 220, blood type 225, etc. Family history 205 may include maternal history 210 and paternal history 215. In some embodiments, EHR 200 may be created and / or maintained by HCP 120 based on information from the patient.
[0043] The EHR 200 may also include other data fields, such as a diagnosis 235 (e.g., for a current illness), a diagnosis code 240 (which may be a standardized code for a diagnosis, such as an International Classification of Diseases (ICD) code), a treatment code 245 (which may be a standardized code used to describe a treatment, such as a Current Procedural Terminology (CPT) code), a prescription code 250 for any prescriptions, and the like. The prescription code 250 may also include a medication 255 (e.g., the name of the medication), a dosage 260 (strength and frequency), and a duration 265 (the length of time the medication is to be taken). In some cases, the EHR 200 may also include other fields and / or subfields, such as an indication of whether the prescription is a new prescription or a refill.
[0044] In some embodiments, the patient's EHR 200 may be stored as a blockchain, for example, by the HCP 120, and each transaction between the HCP 120 and the patient may form part of an EHR information block in the EHR blockchain. In the following description, when the EHR is maintained as a blockchain, then the EHR information record 200 may also be referred to as an EHR block 200. The EHR block 200 may therefore form a block in the EHR blockchain. When an EHR block 200 is to be added to the EHR blockchain, some of the data in the EHR block 200 that is added to the EHR blockchain may depend on other entities. For example, a treatment code 245 for a diagnosis may require approval and / or verification from a payer 140 ( Figure 2 As another example, a medication warning label (not shown) may form part of the EHR block 200. Figure 2 ) may use input and / or approval from PMDP 130 and / or payer 140 before EHR block 200 is added to the EHR block chain.
[0045] In some embodiments, diagnosis 235, diagnosis code 240, treatment code 245, prescription code 250, along with data fields medication 255, dosage 260, and duration 265, may be used to form sub-block 280. Sub-block 280 is merely an example of some information that may be shared with another specific entity. Generally speaking, the information used to form a sub-block from data records or blocks in a locally maintained blockchain (e.g., an EHR blockchain) may depend on regulations (e.g., healthcare and / or privacy regulations), laws governing information sharing (determining information that entities can or cannot share), business guidelines (e.g., trade secrets or sensitive information), and / or contractual obligations (e.g., between or with entities sharing information). In some embodiments, the data in sub-block 280 may be shared by an entity such as HCP 120 with another healthcare market entity such as payer 140 to complete a transaction. However, the patient profile information associated with the basic profile information 230 may be considered private (e.g., based on legal, privacy, and / or business guidelines), and the first entity (e.g., HCP 120) may not wish to share the basic profile information 230, or may wish to limit the shared portions of the basic profile information 230.
[0046] Thus, in some embodiments, the data used to form the sub-block 280 may be encrypted separately. In some embodiments, the encryption of the data forming the sub-block 280 may be based on any suitable encryption method, including symmetric key encryption techniques (where entities such as the HCP 120 and the payer 140 share a secret key), such as techniques based on the Advanced Encryption Standard (AES) or variations thereof. The sub-block 280 may be encrypted (e.g., by the HCP 120) before being shared with another entity (e.g., the payer 140). The other entity (e.g., the payer 140) may be able to decrypt the sub-block 280, for example, using the shared key.
[0047] In addition, the data in the EHR 200 may also be separately encrypted by the HCP 120 using any secure encryption technique to form the EHR block 200. For example, the data in the EHR block 200 may be separately encrypted using different keys so that it can be decrypted by the HCP 120 and obtained by the HCP, but cannot be viewed by any other entity. Thus, an encrypted EHR block 200 to be added to the EHR block chain by a first entity (e.g., HCP 120) may be encrypted prior to sharing such that: (i) a portion of the information is separately encrypted (e.g., in a sub-block 280) and can be decrypted by another entity (e.g., payer 140); and (ii) information outside the sub-block 280 cannot be decrypted or accessed by other entities and remains private to the HCP 120. Thus, in some embodiments, based on the EHR data record, data elements that may be formed may include: (a) an encrypted sub-block 280 (e.g., when a multidimensional block is formed) that includes information in the fields diagnosis 235, diagnosis code 240, treatment code 245, prescription code 250, medication 255, dosage 260, and duration 265, which may be capable of being decrypted by a designated entity; and (b) an encrypted EHR block 200, which may include all information in the EHR record (including EHR information present within sub-block 280, as well as EHR information from outside of sub-block 280) and is capable of being decrypted by the HCP 120 (EHR owner) but not by any other entity.
[0048] Thus, in some embodiments, other entities (e.g., payor 140) may be able to decrypt information in sub-block 280, but will not be able to decrypt encrypted information associated with EHR block 200. In some embodiments, an encrypted EHR block 200 from a first entity (e.g., HCP 120) may include information that can be used to form multiple sub-blocks, where each sub-block (e.g., sub-block 280) may be decryptable by a different second entity (e.g., payor 140).
[0049] Figure 3 An exemplary medication information record (DIR) is shown. In some embodiments, DIR 300 may include information about a medication. The fields shown in DIR 300 are exemplary only, and DIR 300 may include various other fields based on laws, standards, industry practices, etc. In addition, the DIR may include fields that are different (fewer or more) than those fields shown with respect to the exemplary DIR 300.
[0050] The DIR 300 may include various data fields, including a formulary schedule 305, which may list approved prescription drugs (e.g., generic drugs and brand name drugs) associated with a therapeutic category. For example, a payer for a patient (such as payer 140) may cover and / or request the use of drugs included in the formulary schedule. The DIR 300 may also include various other data fields, including a price 325, which may list the price (such as the list price or the negotiated price) at which the drug is available. The formulary schedule 305 may also include a repeating payer-i field 310-i (1≤i≤n) with information about the payer. In addition, each payer listed in the payer-i field 310-i may include information about a corresponding drug level in a repeating level j field 310-j (1≤j≤m). The drug level lists various levels of equivalent drugs, which may depend on the formulary schedule and the payer. For example, for the prescribing schedule specified in prescribing schedule 305 and the payer specified in payer 1310-1, a level 1 315-1 drug may be a cheaper generic drug, while a level 2 315-2 drug may be a more expensive generic drug, and a level 3 315-3 drug may be a brand name drug. In addition, each level-j field 310-j may include a repeated indication-k field 310-k (1≤k≤s) having information about the medical condition for which the prescribing schedule has been approved for use (e.g., approved by a regulatory agency such as the Food and Drug Administration (FDA) and / or payer 1310-1).
[0051] In addition, if Figure 3 As shown, DIR 300 may include various other fields, including efficacy 327 (which may be a measure of the therapeutic effect on a medical condition), safety 330 (e.g., drug interactions, toxicity, contraindications, etc.), route of administration 335 (e.g., topical, oral, intravenous, etc.), mechanism of action (MOA) 340 (which may identify the biochemical interactions through which a drug induces a pharmacological effect), side effects 345 (e.g., secondary effects), etc.
[0052] In some embodiments, the DIR 300 for a patient may be stored as part of a DIR block chain by an entity such as a PMDP 130. In the following description, when the DIR is maintained as a block chain, the DIR information record 300 may also be referred to as a DIR block 300. The DIR block 300 may therefore form a block in the DIR block chain. When a DIR block 300 is to be added to the DIR block chain, some of the data in the DIR information block 300 added to the DIR block chain may depend on verification by other entities. For example, the information in the prescription list 305 associated with the payer (e.g., payer 140) specified in the payer 1310-1 may form part of the DIR block 300 and may depend on verification by the payer (e.g., payer 140) before the DIR block 300 is added to the DIR block chain.
[0053] In some embodiments, for a transaction conducted at a certain point in time, information in the data field prescription list 305, payee 1310-1, level information in each field in the level-j field 310-j associated with the payee in payee 1310-1, and information in each field in the indication-k field 310-k associated with each level-j field may be used to form a sub-block 385. However, information related to other payees in the payee-i field 310-i (2≤i≤n) may not form part of the sub-block 385 because the information may be confidential (e.g., between each payee in the payee-i (2≤i≤n) and the PMDP 130), and the PMDP 130 may not wish to and / or may be contractually blocked from sharing information related to the payee with other payees. The sub-block 385 is merely an example of some information that may be shared with another specific entity. Generally speaking, information used to form sub-blocks from data records or blocks in a locally maintained blockchain (e.g., DIR 300) may depend on regulations (e.g., healthcare and / or privacy regulations), laws governing information sharing (determining what information entities can or cannot share), business guidelines (e.g., trade secrets or sensitive information), and / or contractual obligations (e.g., between or with entities sharing information).
[0054] Thus, in some embodiments, the data in sub-block 385 may be encrypted separately. In some embodiments, the data in sub-block 385 may be encrypted based on any suitable encryption technique, including symmetric key encryption, based on a secret key shared with another entity (e.g., payee 140 identified in payee 1310-1 field) prior to sharing. The other entity (e.g., payee 140) may be able to decrypt sub-block 385, for example, based on the shared key.
[0055] In addition, if Figure 3As shown, another sub-block 380 may be formed by the DIR 300. The sub-block 380 may include fields such as efficacy 327, safety 330, route of administration 335, mechanism of action (MOA) 340, side effects 345, etc. The sub-block 380 is only an example of some information that can be shared with another specific entity. As described above, the information used to form the sub-block 380 according to the data record or block (e.g., DIR 300) in the locally maintained block chain may depend on regulations (e.g., health care and / or privacy regulations), laws governing information sharing (determining the information that an entity can or cannot share), business guidelines (e.g., trade secrets or sensitive information) and / or contractual obligations (e.g., between or with entities sharing information). The sub-block 380 may be encrypted separately using a secret key shared with another entity (e.g., PMDP 130). PMDP 130 may therefore be able to use the secret shared key to decrypt and view the information in the sub-block 380.
[0056] In addition, the data in the DIR block 300 may also be separately encrypted by the first entity (e.g., PMDP 130) using any secure encryption technology, so that the data can be decrypted by the first entity (e.g., PMDP 130) and obtained by the first entity, but cannot be viewed by other entities (e.g., HCP 120 and / or payer 140). Thus, in some embodiments, based on the DIR data record, data elements that may be formed may include: (a) an encrypted sub-block 385 (e.g., when a multidimensional block is formed), which includes information in the prescription summary table 305, the payer 1310-1, the level information in each field of the level-j field 310-j associated with the payer in the payer 1310-1, and the information in each field of the indication-k field 310-k associated with each level-j field; (b) an encrypted sub-block 380 (e.g., when a multidimensional block is formed), which includes information in efficacy 327, safety 330, route of administration 335, mechanism of action (MOA) 340, side effects 345; and (c) an encrypted DIR block 300, which may include all information in the DIR record 300 (including DIR information also present in sub-blocks 380 and 385, as well as DIR information from outside sub-blocks 380 and 385), and is capable of being decrypted by PMDP 130 (block owner) but not by any other entity.
[0057] Thus, the encrypted sub-blocks 380 and 385 that may be formed by the PMDP 130 may be decryptable by the HCP 120 and the payer 140, respectively. In addition, the PMDP 130 may encrypt the DIR block 300 so that entities other than the PMDP 130 may not be able to view the information in the DIR block 300. In some embodiments, the encrypted DIR information block 300 from a first entity (e.g., PMDP 130) may include information that can be used to form multiple sub-blocks (e.g., 380 and 385), each of which may be decryptable by a different second entity (e.g., by the HCP 120 and the payer 140, respectively).
[0058] Figure 4 An exemplary health transaction record (HTR) 400 is shown. Figure 4 As shown, HTR 400 may include treatment-related information and cost-related information about a patient at a certain point in time. The fields shown in HTR 400 are merely exemplary, and HTR 400 may include various other fields based on laws, standards, industry practices, etc. In addition, the HTR may include fields that are different from (fewer or more than) those fields shown with respect to the exemplary HTR 400.
[0059] In some embodiments, HTR 400 may be maintained by an entity such as payer 140. HTR 400 may include various data fields, including patient 425 (e.g., patient ID), cost 405, which may represent the cost associated with the transaction. Cost 405 may include payer cost 410 (e.g., for payer 140), drug cost 415 (e.g., the cost of the prescription drug), HCP cost (cost borne by the healthcare provider), and patient cost 425. Patient cost 425 may depend on patient copayment 430, out-of-pocket limit 435, and deductible 440, which may depend on the patient's health insurance coverage and the patient's previous transactions.
[0060] In some embodiments, HTR 400 may also include various other fields, including diagnosis 445 (for the patient's medical condition), diagnosis code 450 (e.g., for the current medical condition), treatment code 455 (e.g., a CPT code or another standardized code used to describe the treatment), repeating fields medication codes 460-1, 460-2, ... (which can be standardized codes for identifying prescribed medications), and procedure code 465 (which is used to describe a medical procedure associated with the treatment of the medical condition).
[0061] In some embodiments, the HTR 400 for a patient at a certain point in time may be stored as a block chain by an entity such as a payer 140. In the following description, when the HTR is maintained as a block chain, the HTR information record 400 may also be referred to as an HTR block 400. The HTR block 400 may therefore form a block in the HTR block chain. For example, data related to a transaction between an HCP 120 and a patient and / or a patient and a payer 140 may form part of an HTR block 400 in the HTR block chain. When an HTR block 400 is to be added to the HTR block chain, some of the data in the HTR block 400 added to the HTR block chain may depend on verification by other entities. For example, the information in the diagnosis 445 may be verified by the HCP 120 before the HTR block 400 is added to the HTR block chain.
[0062] In some embodiments, for a transaction at a certain point in time, information in data fields diagnosis 445, diagnosis code 450, treatment code 455, and repeating fields medication code 460-1, 460-2, etc. may form part of sub-block 485. Sub-block 485 may be shared with PMDP 130 to determine whether the drug is approved for use in the diagnosis, to determine safety (e.g., drug interactions), etc.
[0063] In some embodiments, the information in the fields patient ID 425 and copayment 430 may be used to form another sub-block 480. Sub-block 480 may be shared with HCP 120 and may facilitate determining copayment information about the transaction. Sub-blocks 480 and 485 are merely examples for illustrating information that may be shared by payer 140 with specific entities. In general, the information used to form sub-blocks from data records or blocks in a locally maintained blockchain (e.g., HTR 400) may depend on regulations (e.g., healthcare and / or privacy regulations), laws governing information sharing (determining what information entities can or cannot share), business guidelines (e.g., trade secrets or sensitive information), and / or contractual obligations (e.g., between or with entities sharing information).
[0064] Thus, in some embodiments, the data in sub-blocks 480 and 485 may be encrypted separately. In some embodiments, the data in sub-block 485 may be encrypted based on any suitable encryption technique (including symmetric key encryption) based on a secret key shared with PMDP 130 before sharing. PMDP 130 may be able to decrypt sub-block 485 based on a secret key shared between PMDP 130 and payer 140. In addition, sub-block 480 may be encrypted separately based on a different secret key shared with HCP 120. HCP 120 may be able to decrypt and view the information in sub-block 480 using a secret key shared between HCP 120 and payer 140. In addition, the data in HTR information block 400 may also be encrypted separately by the first entity (e.g., payer 140) using any secure encryption technique, so that the data may be able to be decrypted by payer 140 and may be obtained by the payer, but cannot be viewed by HCP 120 and / or PMDP 130.
[0065] Thus, in some embodiments, based on the HTR data record, data elements that may be formed may include: (a) an encrypted sub-block 480 (e.g., when a multidimensional block is formed) that includes information in the fields patient ID 425 and co-payment 430; (b) an encrypted sub-block 485 (e.g., when a multidimensional block is formed) that includes information in the fields diagnosis 445, diagnosis code 450, treatment code 455, and repeated fields medication code 460-1, 460-2; and (c) an encrypted HTR block 400 that may include all information in the HTR record 400 (including HTR information that is also present within sub-blocks 480 and 485, as well as HTR information from outside sub-blocks 480 and 485) and is capable of being decrypted by payer 140 (HTR block owner) but not by any other entity. Thus, in some embodiments, an encrypted HTR information block 400 from a first entity (e.g., payer 140) may include information that can be used to form multiple sub-blocks (e.g., 480 and 485), each of which may be capable of being decrypted by a different second entity (e.g., by HCP 120 and PMDP 130, respectively).
[0066] Figure 5A An exemplary EHR information block 540 is shown including sub-blocks 480 and 485. The EHR information block 540 may be added to an EHR blockchain 545 maintained by a first entity such as payer 140. In some embodiments, the block 540 may be encrypted by payer 140 so that it may be decrypted and read by payer 140 (but not by other entities).
[0067] In some embodiments, sub-blocks 480 in EHR information block 540 may be encrypted by payer 140 using symmetric key encryption based on a secret shared key with another entity, such as HCP 120. HCP 120 may use the shared key to decrypt sub-block 480. However, HCP 120 may not be able to decrypt information in block 540 outside of sub-block 480.
[0068] In addition, sub-block 485 in HTR information block 540 may be encrypted by payer 140 using symmetric key encryption based on a secret shared key with an additional entity such as PMDP 130. PMDP 130 may use the shared key to decrypt sub-block 485. However, PMDP 130 may not be able to decrypt information in block 540 outside of sub-block 485.
[0069] Figure 5B An EHR information block 520, a DIR information block 520, and an HTR information block 540 are shown depicting some sub-blocks associated with the information block.
[0070] like Figure 5B As shown, current information block 540 added to HTR blockchain 545 maintained by payer 140 may include information that can be used to form sub-blocks 480 and 485. As described above, sub-block 480 may be decryptable by HCP 120, while sub-block 485 may be decryptable by PMDP 130. Also as described above, block 540 may be encrypted solely by payer 140 and may not be decryptable by entities other than payer 140 (e.g., to comply with legal, privacy, contractual, and / or business guidelines).
[0071] like Figure 5B As shown, an exemplary EHR information block 520 may include information that can be used to form a sub-block 280. The EHR information block 520 may be added to an EHR block chain 525 maintained by the HCP 120. In some embodiments, the sub-block 280 in the EHR information block 540 may be encrypted using symmetric key encryption (e.g., by the HCP 120) based on a secret shared key with the first entity payer 140. The payer 140 may decrypt the sub-block 280 using the shared key. As described above, the HCP 120 may also decrypt the sub-block 480 using a secret key shared with the payer 140. In addition, the information in the block 520 may be encrypted solely by the HCP 120, and the information may not be decrypted by other entities outside the HCP 120 (e.g., to comply with legal, privacy, contractual and / or business guidelines).
[0072] In addition, if Figure 5BAs shown, an exemplary DIR information block 530 may include a sub-block 385. The DIR information block 530 may be added to a DIR block chain 535 maintained by another second entity, such as PMDP 130. In some embodiments, the sub-block 385 in the DIR information block 530 may be encrypted by PMDP 130 using symmetric key encryption based on a secret shared key with payee 140. Payee 140 may decrypt sub-block 385 using the shared key. PMDP 130 may also decrypt sub-block 485 using a secret key shared with payee 140. In addition, the information in block 530 may be encrypted solely by PMDP 130, and the information may not be decryptable by other entities outside of PMDP 130 (e.g., to comply with legal, privacy, contractual, and / or business guidelines).
[0073] exist Figure 5B , the information interface 524 between the payer 140 and the HCP 120 may include information shared using sub-blocks 460 and 280. Therefore, both the HCP 120 and the payer 140 may decrypt information in the information interface (e.g., information interface 524) between the two entities (HCP 120 and the payer 140). Similarly, the information interface 534 between the first entity payer 140 and the second entity PMDP 130 may include information shared using sub-blocks 385 and 485, and the information in the information interface 534 may be decrypted by both PMDP 130 and the payer 140.
[0074] Fig. 6A A transaction flow 600 associated with a multi-dimensional block is shown. Fig. 6A For exemplary purposes only, and for ease of explanation, some of the steps between two entities in the transaction flow associated with block 540 are outlined. Additional steps to obtain a multidimensional block may follow a similar pattern. Fig. 6A In the example, the sub-blocks shown and the fields described are examples only to illustrate the process flow and information that can be shared. In general, the information used to form sub-blocks from data records or blocks in the locally maintained blockchain may depend on regulations (e.g., healthcare and / or privacy regulations), laws governing information sharing (determining what information entities can or cannot share), business guidelines (e.g., trade secrets or sensitive information), and / or contractual obligations (e.g., between or with entities sharing information). When the data record has been verified and completed, the final data record can be added as a block to the local blockchain.
[0075] Fig. 6A An HTR blockchain 545 is shown, which may be maintained by a first entity such as payer 140. Fig. 6A In the process, data record 540 will be added to block chain 545. Fig. 6AAlso shown is an EHR blockchain 525 currently having record 520 at the head of the blockchain and a DIR blockchain 535 currently having record 530 at the head of the blockchain. In some embodiments, blockchains 525 and 535 may be maintained by second entities HCP 120 and PMDP 130, respectively. Fig. 6A In some embodiments, when a transaction request is submitted, the latest block from each blockchain may be submitted to form a multi-dimensional blockchain.
[0076] In some embodiments, updates made to a traditional blockchain (e.g., one of blockchains 525, 535, or 545) by a corresponding entity (e.g., one of HCP 120, PMDP 130, or payer 140, respectively) that includes information from another entity and / or involves other entities may be verified by one or more other entities before being submitted (e.g., locally in blockchain 525, 535, or 545 and / or in an associated multidimensional blockchain). In some embodiments, each field associated with information blocks 520, 530, and / or 540 may have a unique global field id that may uniquely identify the field to the multidimensional blockchain system and / or associated entities when information related to the field is shared between entities.
[0077] In some embodiments, when a record such as record 540 is to be added to a block chain maintained by an entity, the entity (e.g., payer 140) may send a transaction request to a related entity (e.g., HCP 120 and / or PMDP 130). In some embodiments, the transaction request may be placed in a request pool. In some embodiments, various entities HCP 120, PMDP 130, payer 140, etc. may form part of a permissioned block chain platform. In a permissioned block chain platform, a trusted entity may form a platform and invite other trusted entities to join the network. In some embodiments, a permissioned block chain platform may also be private. In some embodiments, a permissioned block chain platform may support multidimensional blocks. Rules related to accessing a multidimensional block chain and adding blocks to a multidimensional block chain, program code for determining contracts (e.g., smart contracts) between entities, updated verification, etc. may be determined by an entity associated with the permissioned block chain platform.
[0078] If the payer 140 is authorized to access and update the platform, then in some embodiments, when a data record 540 is to be added, the payer 140 may fork and encrypt a sub-block 480, which in some cases may include information from a portion of the data record 540. The information in the sub-block 480 may then be decrypted and read by the HCP 120. In some embodiments, a symmetric encryption algorithm may be used to encrypt the sub-block 480.
[0079] As mentioned above, in the following description, for ease of explanation, it is first considered that two data records 520 and 540 come from block chains 525 and 545, respectively. Fig. 6A As shown, forking action 605 may cause data record 540 to fork and form forked sub-block 480. In some embodiments, forking action 605 may be used as a trigger to initiate multidimensional block formation. The sub-block forking action may include duplication and encryption of some subset of the data in the data record or block of the local blockchain (e.g., using a secret key shared with another entity) to form a sub-block (e.g., sub-block 480). In some embodiments, the sub-block may be replicated in memory. For example, the sub-block may reside in a memory used to form a multidimensional block (e.g., multidimensional block 610). Sub-block replication in memory may facilitate speed, storage, and complete removal of replicated objects (e.g., when multidimensional block formation is complete). Information associated with the original local block (e.g., local block 540) is not affected by the forking action (e.g., forking action 605).
[0080] For example, forking 605 may result in sub-chunks 480 being copied, split from block 480, and encrypted separately. The encryption key may be shared with HCP 120 and may take the form of, and / or be included as part of, an authorization code sent from a first entity (payer 140) to a second entity (HCP 120) over a secure channel. HCP 120 may decrypt sub-chunks 480 using the authorization code received from payer 140. In some embodiments, sub-chunks 480 may be copied in memory. Copying of sub-chunks in memory may facilitate speed, storage, and complete removal of copied objects (e.g., when multi-dimensional chunk formation is complete).
[0081] In addition, if Fig. 6A As shown, when the HCP 120 submits the data record 520, the forking action 607 may also fork the data record 520 and form a forked sub-block 280. In some embodiments, the forking action 607 may cause the sub-block 280 to be copied, split from the data record 520, and encrypted separately. The encryption key may be shared with the payee 140 and may take the form of an authorization code and / or be included as part of the authorization code that is sent from the HCP 120 to the payee 140 via a secure channel. The payee 140 may decrypt the sub-block 280 using the authorization code received from the HCP 120.
[0082] In some embodiments, after verification, the information in sub-blocks 280 and 480 that form the information interface between data records 520 and 540 may be incorporated into records 520 and / or 540 (e.g., by filling and / or updating in appropriate fields in records 520 and / or 540). For example, the HCP 120 may obtain the co-payment 230 and the patient ID 425 upon decrypting and reading sub-block 480. Similarly, the payer 140 may obtain the diagnosis code 240, the treatment code 245, the prescription code, etc. upon decrypting and reading sub-block 480. However, the information outside of sub-block 280 in block 520 may remain private to the HCP 120. Similarly, the information outside of sub-block 480 in block 540 may remain private to the payer 140. As previously described, the information interface between entities may depend on laws (e.g., privacy, data sharing, healthcare, business, competition), contractual obligations between entities (e.g., entered by the entities), and / or business considerations (e.g., trade secrets, etc.). Thus, the above examples are merely exemplary, and the actual data shared and / or included in the data records, blocks, and sub-blocks may differ from these examples.
[0083] In some embodiments, the information in sub-blocks 480 and / or 280 may be verified, and after successful verification, the updated data record 520 and the updated data record 540 may be linked to obtain an unlocked multidimensional block 610. In some embodiments, the updated records 520 and 540 and the multidimensional block 610 may be retained in an unlocked form (not yet submitted to any block chain) at this stage. The term "unlocked" is used to indicate that the information in the multidimensional block 610 is not the final version and may change as the transaction proceeds to completion. For example, if it is determined that the information in the sub-blocks 480 and / or 280 is incorrect or invalid (as further described below), the transaction may be rejected. In some embodiments, the updated records 520 and / or 540 may be rehashed after linking. The multidimensional block (unlocked or locked) may include data and a timestamp. The data may include data records 520, 530, and / or 540. The timestamp determines the order in which the multidimensional blocks (once verified and completed) are linked.
[0084] In some embodiments, HCP 120 and / or payer 140 and / or other authorized entities associated with the blockchain may determine whether the information in the decrypted sub-block corresponds to information associated with blocks 520 and / or 540, respectively. Consensus techniques may confirm the correctness of the transactions that make up the multidimensional block. In some embodiments, consensus techniques such as Byzantine Fault Tolerance (BFT) or variations thereof such as redundant BFT or some other voting-based consensus techniques may be used to determine whether blocks 520 and 540 may be used to form multidimensional block 610. Consensus is reached when an authorized entity (e.g., payer 140) or some specified number (e.g., majority) of entities validates a transaction or block.
[0085] If the consensus technique confirms that the transaction is correct, a first instance of the (unlocked) multidimensional block 610 may be formed. On the other hand, if, for example, the patient identified in patient ID 425 in block 480 does not match the patient ID (e.g., in block 280), the transaction may be considered incorrect and the block addition request may be rejected. In some embodiments, the platform or each entity may maintain a log of rejected transactions for traceability and debugging purposes. The log may indicate a reason or code associated with the transaction rejection.
[0086] In some embodiments, the consensus layer may include consensus technology, and may interact with the smart contract layer to establish transaction correctness and / or validity. In some embodiments, each update performed by a corresponding entity (e.g., HCP 120, PMDP 130, or payer 140) to a traditional block chain (e.g., one of block chains 200, 300, or 400) may be verified by a smart contract program code associated with a multidimensional block chain. The smart contract program code may reflect agreements related to data sharing, authentication, payment, etc. between entities. The smart contract layer may be viewed as an automated tool that promotes interaction between entities without manual intervention. In some embodiments, the smart contract layer may initiate an action based on rules associated with one or more contracts and when those rules have been met. Each update performed to a multidimensional block chain and / or the passage of time and / or other events may trigger an action performed by the smart contract layer.
[0087] The linking of updated records (e.g., updated records 520 and updated records 540) may be performed based on predefined rules agreed upon by entities (e.g., HCP 120 and payer 140). In some embodiments, the linking of blocks (e.g., updated blocks 520 and updated blocks 540) may be performed based on a smart contract associated with a multi-dimensional blockchain. After linking, updated blocks 520 and updated blocks 540 may be rehashed. As described above, linking may allow an entity to associate information in its blockchain with information in a blockchain maintained by another entity. In addition, an entity may be able to determine one or more transactions associated with information in a particular block maintained by the entity. Thus, two or more entities may have a coherent and consistent view of transactions associated with blocks in different blockchains.
[0088] Therefore, the embodiments disclosed in the present invention are conducive to: (a) authenticating transactions; (b) protecting transaction integrity, (c) maintaining transaction provenance; (d) complying with legal, privacy and business guidelines when sharing information; (e) providing context for data maintained by the organization. For example, an organization may be able to determine the source or transaction of external data received by the organization. As another example, the multi-dimensional block chain may facilitate PMDP 130 to analyze and evaluate efficacy, efficacy, and dosage information based on actual patient prescriptions using real world evidence (RWE). For example, HCPs can share efficacy, efficacy, dosage information and some demographic information (e.g., age, location (zip code), medical conditions, diagnosis, etc.) with PMDP 130 without providing any personally identifiable or sensitive information about the patient. To date, such RWE information is difficult to obtain (due to legal, privacy and other issues) and difficult to analyze (because when obtained, the information obtained is usually fragmented and has no context - that is, lacks demographic information and / or other useful information). In some embodiments, a smart contract layer may be used to manage information interfaces / data sharing so that data shared with participants can be timely, entity-specific, and compliant with laws, privacy regulations, and / or contractual obligations while adhering to business-related considerations.
[0089] exist Fig. 6A , updates to data records corresponding to multiple dimensions of a multidimensional block are shown. However, in some embodiments, a new multidimensional block may be formed with updates to data records for a single dimension, while substantive information associated with other dimensions may remain unchanged. For example, drug-related information associated with a drug prescribed to a patient may be updated in a new multidimensional block (e.g., by PMDP 130) without updating EHR data 520 or payer transaction records 140.
[0090] like Fig. 6A As shown, multidimensional block 610 can be an unlocked block, which can be a non-final version and can still be modified. Multidimensional block 610 can include a link between updated data record 520 and updated data record 540. Sub-blocks 280 and 480 can form an information interface between records 520 and 540. In some embodiments, the information interface can be defined and / or managed by the smart contract layer. For example, for a certain transaction type, the information to be shared between entities (such as, in sub-block 280 and / or sub-block 480) can be specified and verified by program code in the smart contract layer associated with the multidimensional block chain.
[0091] Fig. 6A The multidimensional block 610 is shown to be further enhanced by a series of transformations, for example by adding another dimension based on the record 530 (this may follow the process described above for the multidimensional block 610). Fig. 6AIn, at each iteration, the information interface between the two entities (two dimensions in the multidimensional block) is shown as being addressed. For example, in subsequent iterations (e.g., after forming the unlocked multidimensional block 510), the payer 140 may fork sub-block 485 from the data record 540, and the PMDP 130 may fork sub-block 385 from the data record 530. As described above, in some embodiments, sub-block 485 may be copied and encrypted separately with a key that can be shared with the PMDP 130 (e.g., by an authorization code). Similarly, sub-block 385 may be copied and encrypted separately with a key that can be shared with the payer 140 (e.g., by an authorization code). After verification, blocks 530 and 540 may be linked and re-hashed. Because the data in the further updated block 540 may have changed, the link from block 520 to the newly updated block 540 may also be updated.
[0092] Figure 6B An exemplary Merkle tree 622 is shown associated with a multi-dimensional block chain including data records 520, 530, and 540. Figure 6B In the example Merkle tree 622, an exemplary Merkle tree is associated with a multidimensional block chain, which includes multiple data records, each of which may be associated with a different respective block chain. Merkle tree 625 is only one example, and other forms may be used as appropriate. In some embodiments, when verified and completed, data records 520, 530, and / or 540 may form blocks in corresponding different block chains (e.g., in block chains 525, 535, and / or 545, respectively). When in an unlocked state, the exemplary Merkle tree 622 and the data in records 520, 530, and 540 may not be verified and / or be a non-final version. As shown in FIG. Figure 6B As shown, hash C 631 can be obtained by using a cryptographic hash function on data record 520. Cryptographic hash functions are deterministic (produce the same output for the same input data), computationally cheap (use resources to produce output for a given input), anti-imagery (difficult to determine the input from the output), and collision resistant (usually produce different outputs for different inputs). Similarly, hash D 633, hash E 635, and hash F 637 can be obtained by using appropriate cryptographic hash functions on data records 530, 540, and D4, respectively. Figure 6B In the example, record D4 is used to show some other (e.g., patient) records, but is not related to Fig. 6A. Cryptographic hash functions 631, 633, 635, and 639 may be specific to entities HCP 120, PMDP 130, payer 140, and an entity associated with D4, respectively. Thus, HCP 120 (but not PMDP 130, payer 140, or an entity associated with D4) may be able to decrypt data record 520. Conversely, data records 530, 540, and D4 may be decrypted by PMDP 130, payer 140, and an entity associated with D4 (but not by any other entity).
[0093] In addition, hash A 627 may be obtained by applying an appropriate cryptographic hash function to a combination of hash C 631 and hash D 633, while hash B 629 may be obtained by applying an appropriate cryptographic hash function to a combination of hash E 635 and hash F 637. Finally, top hash 625 may be obtained by applying an appropriate cryptographic hash function to a combination of hash A 627 and hash B 629. Data associated with hash C 631 (output of hash (520)), hash D 633 (output of hash (530)), hash E 635 (output of hash (540)), hash F 637 (output of hash (D4)) may be shared between authorized entities (e.g., by entities forming a multidimensional block) without compromising the security of data records 520, 530, 540, or D4. Similarly, hash A 627, hash B 629, and top hash 625 may also be shared.
[0094] See also Fig. 6A , each iteration / step can be continued with an unlocked block. In some embodiments, when the information exchange related to the transaction is completed and the transaction has been verified by the consensus layer and / or the smart contract layer, blocks 520, 530 and / or 540 can be rehashed (as appropriate), linked updated and locked, and the multidimensional block can also be locked and submitted as multidimensional block 655 ( Figure 6C ). Thus, an entity may be able to verify multi-dimensional blocks (e.g., final blocks 520, 530, and 540) associated with local blocks (e.g., final blocks 520, 530, and 540). Figure 6C The integrity of the final multidimensional block 655 in the local block is associated with the conventional local block chain (e.g., block chains 525, 525 and 545). Figure 6CAs shown, multidimensional blocks 655 may include verified and final data records 520, 530, and 540, which may correspond to final information blocks 520, 530, and 540 in corresponding different local blockchains 525, 535, and 545, respectively. In some embodiments, each multidimensional block may include a block header with a timestamp, a top hash 625, information related to previous blocks, a pointer to the root of the Merkle tree 625, and other appropriate information. The hash reference may take the form of a uniform resource locator (URL) and / or a local (entity-specific) address on a private permissioned blockchain platform.
[0095] Figure 6C An exemplary architecture of a system 650 that is conducive to the security and interoperability of healthcare information is shown. In some embodiments, the system 650 may be based on the use of multidimensional blocks, which may be based on different blocks maintained by various entities in the system. In some embodiments, the system 650 may include a private permission block chain platform. In some embodiments, the system 650 may take the form of a cloud-based system. A cloud-based system refers to applications, services, and / or other resources (including hardware resources) that are available through a network (e.g., the Internet). A cloud-based system may be based on underlying hardware and software resources and may be public (e.g., available to everyone on a computational basis), private (e.g., limited to an organization), or hybrid (using some combination of public and private clouds).
[0096] The exemplary system 650 may include various entities. These entities may be represented by a server (hardware and / or software), which in some cases may be cloud-based. For example, the HCP 120, PMDP 130, and / or payer 140 may include a server and / or run on a cloud-based platform including a virtual machine (VM).
[0097] Figure 6C An HTR blockchain 545 is shown, which may be coupled to and maintained by a first entity such as payee 140 . Figure 6C Also shown is an EHR blockchain 525 having block 520 at the head of the blockchain and a DIR blockchain 535 having block 530 at the head of the blockchain. In some embodiments, blockchains 525 and 535 may be maintained by second entities HCP 120 and PMDP 130, respectively.
[0098] like Figure 6CAs shown, HCP 120, PMDP 130 and / or payer 140 may interact with authentication layer 680. Authentication layer 660 may include functionality for identifying and managing (adding, registering, and deleting) system entities during operation. In addition, the authentication layer may include functionality for verifying permissions associated with operations on the multi-dimensional block chain (adding new blocks, creating links, etc.). Authentication layer 660 may interact with consensus layer 670, which may include functionality for determining the order of transactions and verifying the correctness of a set of transactions associated with a block.
[0099] In some embodiments, consensus layer 670 may confirm the correctness of the transactions that make up the multidimensional block. In some embodiments, consensus techniques such as Byzantine Fault Tolerance (BFT) or its variants such as redundant BFT or some other voting-based consensus techniques may be used to determine whether a multidimensional block 610 ( Fig. 6A ). When a specified authorized entity or some specified number of entities (e.g., a majority) validates a transaction or block, a consensus may be reached on the validity and / or finality associated with the transaction or block. In some embodiments, the consensus layer 670 may interact with the smart contract layer 680 and call functions in the smart contract layer to verify the correctness of a set of ordered transactions associated with a block.
[0100] The smart contract layer 680 may include program codes that implement logic associated with the block chain. For example, a "smart contract" program code associated with a multidimensional block chain may process a transaction request and determine the validity of the transaction based on program logic. The logic may depend on the rules agreed upon by the entity with respect to transactions associated with the block chain. For example, due to incompatibility between two or more drugs prescribed to a patient, the smart contract layer 680 may reject a transaction (e.g., from the HCP 120). The smart contract may operate at the verification time and submission time before the block is submitted. In some embodiments, the smart contract layer 680 may determine and / or verify the information interface between entities associated with the multidimensional block chain. For example, the smart contract layer 680 may encode rules or protocols between two or more entities regarding data sharing, transactions, etc., which may be based on real-world contracts between these entities. In some embodiments, each update made to a traditional blockchain (e.g., one of blockchains 625, 635, or 645) by a corresponding entity (e.g., HCP 120, PMDP 130, or payer 140) may also be verified by a smart contract layer 680 associated with the multidimensional blockchain. In some embodiments, verification, completion, and linking of blocks may be performed based on smart contracts associated with the multidimensional blockchain. In some embodiments, smart contract program code may be triggered by one or more events associated with the platform, such as time, a request to add a block from one or more entities, and / or a specific request associated with a contract (e.g., identified by a contract ID), etc.
[0101] Figure 6C A submitted and locked multidimensional block 655 is shown, in which information from sub-blocks 480, 280, 380 and 385 has been shared by corresponding authorized related entities. In addition, the multidimensional block 655 includes links between blocks 540, 530 and / or 520. The multidimensional block 655 may partially represent an overall view of the transaction at a certain point in time, because it may include real-world physical states associated with drugs (use, effects, etc.), patients (medical conditions, treatments, effects) and costs at that point in time. The multidimensional block 655 may include links to previous blocks in the block chain. The verified and final multidimensional block 655 may include final data records 520, 530 and 540, which may correspond to the final information blocks 520, 530 and 540 in the corresponding different local blockchains 525, 535 and 545, respectively.
[0102] Fig.6D is a visual depiction of a multi-dimensional block that may be associated with an exemplary automated outcome-based contract performance. In some embodiments, a smart contract layer may facilitate automated outcome-based contract performance based on a multi-dimensional block chain.
[0103] like Fig.6D As shown, a three-dimensional (3D) block chain 690 may include a sequence of 3D blocks, wherein each 3D block includes an EHR data record, a DIR data record, and an HTR data record. Figure 6C A data record DIR p 692 is shown which may form part of a multidimensional block and be associated with a particular drug (e.g., drug p). Fig.6D In, the multidimensional block including the record DIRp 692 may represent a multidimensional block formed at the following times: (a) at a certain point in time, when a patient is first diagnosed with a certain condition, and (b) when a medical provider begins treatment via a specific medication. For example, treatment start date, diagnosis code, medication fields may be shared between entities and identify the multidimensional block including the record DIR p 692. As described above, the data shared between entities may depend on laws (e.g., privacy, data sharing, healthcare, business, competition), contractual obligations between entities (e.g., entered by the entities), and / or business considerations (e.g., trade secrets, etc.). Therefore, the examples discussed here are merely exemplary, and the actual data shared and / or included in the data records, blocks, and sub-blocks may differ from these examples.
[0104] Because a single drug (e.g., drug p) can treat many patients, many EHR blocks including a 3D block including an EHR q block 694 can form a multidimensional block chain associated with drug p along the EHR axis. Similarly, a single drug (e.g., drug p) can be associated with many transactions. Therefore, many HTR blocks including a 3D block associated with an HTR r block 696 can form a multidimensional block chain associated with drug p along the HTR axis.
[0105] The outcome-based contract between the HCP 120 and the payer 140 may specify that when a condition is met in the submitted multidimensional block, the payer 140 will make a payment to the HCP 120. For example, the condition may specify one of: (i) the value of a certain health parameter; or (ii) the improvement of a certain health parameter of a patient over a certain period of time when the patient is treated with a certain medication. In some embodiments, the contract terms may be encoded as a smart contract, and the smart contract may automatically initiate payment when the condition is met, as further described below.
[0106] When treatment for a patient is initiated and a prescription is submitted for the patient, a request may be made to the network to connect the EHR information block for the patient, the DIR information block for the prescribed drug, and the transaction information block, and to initiate a multidimensional block chain by forming an initial multidimensional (3D) block (such as a 3D block including DIR p data record 692).
[0107] At a certain point in time, when a 3D block such as 3D block 698 is submitted together with an EHR block (associated with 3D block 698) indicating that the value of the health parameter has been met or the expected improvement of the health parameter has been obtained during the treatment with the drug, then the smart contract can determine whether the result is within a specified time period and automatically initiate an action. These actions may include one or more of the following: indicating that the contract is completed, sending a notification to an entity associated with the contract, initiating a transaction to trigger payment from the payer 140 to the HCP 120, determining and / or recording parameters associated with the contract (e.g., length of time, initial and final values of relevant health parameters, number of visits, dosage, etc.). In some embodiments, the transaction triggering payment may include triggering payment to ensure the smart contract code of traceability. The time period can be determined, for example, based on the time elapsed, by the difference between the timestamp associated with the submitted 3D block 698 at the end of treatment and the timestamp associated with the initial multidimensional block (e.g., genesis block) when treatment begins in the multidimensional block chain.
[0108] See also Figure 6CIn some embodiments, the smart contract layer 680 may also be implemented on each dimension of the multidimensional blockchain to ensure that the multidimensional blocks are constructed correctly. In the above example, the smart contract layer may ensure that each multidimensional block in the blockchain is associated with the same patient, diagnosis and medication and / or contract ID (e.g., between HCP 120 and payer 140) based on the EHR.
[0109] In some embodiments, when a drug is prescribed to a patient (who may be an entity) in system 650, smart contract layer 680 can check with payer 140 for patient coverage and drug eligibility, and can also request patient approval and agreement on price. After a secure agreement is reached on eligibility and price, construction of the multidimensional block can be initiated.
[0110] In some embodiments, the holistic view enabled by the multidimensional block chain can be conducive to the use of machine learning and AI technologies based on RWE. For example, pharmaceutical companies and medical device providers may have very limited access to data outside clinical trials. In some embodiments, by associating demographic information related to drug prescriptions (which may be included in EHR sub-blocks that comply with regulatory and business guidelines), pharmaceutical companies and medical device providers may be able to understand the impact of drugs on different demographic groups, change dosages, monitor adverse outcomes, etc. This data correlation (e.g., via a multidimensional block chain) can enable preventive measures (e.g., reducing or increasing dosages, identifying previously unknown drug interactions, etc.), which can reduce patient risks, increase safety and health outcomes, while also reducing costs. In addition, due to the limited sharing of information between entities, patient privacy between patients and other entities can be maintained. In addition, even when routing payments between entities, the use of smart contracts in conjunction with multidimensional block chains can also be conducive to maintaining contract confidentiality between entities.
[0111] Figure 7 A flow chart of an exemplary method 700 that facilitates security and interoperability of healthcare information is shown. In some embodiments, the method 700 may use a multi-dimensional blockchain, which may be based on different blockchains maintained by various entities in the system. In some embodiments, the method 7000 may be run on a private permissioned blockchain platform, which may take the form of a cloud-based system in some cases. The method 700 may be performed by a processor, a computer, or a network of computers such as a distributed computing system, a server (hardware and software) (including an application server), and a cloud-based system.
[0112] In some embodiments, method 700 may be performed at a first entity. For example, the first entity may include at least one server or computer system associated with at least one of a drug provider or a medical device provider such as PMDP 130. In some embodiments, the first entity may interact with one or more second entities. The second entity may include one or more servers or computer systems associated with a healthcare provider (such as HCP 120) or an insurance provider (such as payer 140) or a patient. In some embodiments, the first entity and the one or more second entities may form a computing node in a distributed computing system, and the multidimensional block chain may form a part of a licensed private block chain platform (such as licensed private block chain platform 650).
[0113] In some embodiments, when an entity, such as a first entity, initiates a transaction to add a block to a locally maintained blockchain, method 700 may be called. Adding a block to a local blockchain may involve input from one or more other entities, and the permissioned private blockchain platform 650 may call method 700.
[0114] In some embodiments, in step 710, the first entity may receive an encrypted information block related to the transaction from one or more second entities in response to a transaction conducted at the first time. Each encrypted information block may be received from different second entities, and each encrypted information block may include at least one sub-block that can be decrypted by the first entity. In some embodiments, for each encrypted information block received by the first entity, the corresponding sub-block that can be decrypted by the first entity may be based on the information interface between the first entity and the corresponding second entity. The information interface between the first entity and the corresponding second entity may be determined based on a predefined rule that manages the interaction between the first entity and the corresponding second entity. In some embodiments, the information interface between the first entity and the corresponding second entity may be determined by a smart contract associated with a multidimensional block chain (e.g., based on the smart contract layer 680). In some embodiments, a smart contract may be associated with a multidimensional block chain and form a part of a licensed private block chain platform. In some embodiments, a smart contract may reflect an agreement related to information sharing, privacy, and contractual obligations between entities associated with a licensed private block chain platform.
[0115] In some embodiments, in step 720, the first entity may decrypt the sub-block that can be decrypted by the first entity. In some embodiments, to decrypt the sub-block, the first entity may receive a corresponding authorization code from the one or more second entities associated with the received encrypted information block, and use the received authorization code to decrypt the decryptable sub-block. In some embodiments, decryption of the sub-block by the first entity may be based on a key securely shared with the corresponding second entity. For example, when the sub-block is encrypted by a particular second entity, the first entity may decrypt the sub-block using a key shared with or received from the second entity. In some embodiments, the shared key may be securely received by the first entity as part of the authorization code.
[0116] In step 730, the first entity may enhance the multidimensional block chain. The multidimensional block chain may be enhanced with a multidimensional block, formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, which is added to a block chain associated with the transaction and maintained by the first entity. Enhancement may include adding a multidimensional block to an existing block chain, or adding a first multidimensional block to a multidimensional block chain structure (such as, adding a multidimensional block to a newly created multidimensional block chain). In some embodiments, the current block may include one or more sub-blocks, wherein each sub-block in the current block may be based on an information interface between a first entity and a corresponding second entity, and may be capable of being decrypted by a corresponding second entity. For example, the content of a sub-block j in the current block may be based on an information interface between a first entity and a corresponding second entity such as a second entity j, and the sub-block j may be capable of being decrypted by a second entity j.
[0117] In some embodiments, enhancement may include adding a new multidimensional block to a multidimensional block chain. The multidimensional block chain may be stored and enabled to be accessed by one or more second entities associated with a licensed private block chain platform. In some embodiments, enhancing a multidimensional block chain with a multidimensional block (e.g., multidimensional block 655) may include determining the validity of data associated with one or more sub-blocks (e.g., sub-blocks 280, 380, 385, 480, and / or 485). In some embodiments, the validity may be determined in part by a smart contract layer (e.g., smart contract layer 680) associated with a licensed private block chain platform. For example, the smart contract layer (e.g., smart contract layer 680) may request verification from one or more entities in an entity associated with a licensed private block chain platform. In some embodiments, the smart contract layer (e.g., smart contract layer 680) may determine one or more entities authorized to verify data associated with one or more sub-blocks, and request verification from the one or more authorized entities. In some embodiments, the validity of data associated with one or more sub-blocks may be based on consensus technology. In some embodiments, Byzantine Fault Tolerance (BFT) techniques may be used to determine validity and / or reach consensus. In some embodiments, when the multidimensional blockchain is enhanced with multidimensional blocks, the first entity may trigger at least one smart contract associated with the permissioned private blockchain platform. In some embodiments, the first entity may receive an indication of the completion of one or more contract milestones and / or one or more contract results between the first entity and the one or more second entities from the smart contract based on information associated with the multidimensional blockchain.
[0118] In some embodiments, when a multidimensional blockchain is enhanced with multidimensional blocks, a smart contract layer (e.g., smart contract layer 680) may evaluate conditions associated with a contract between entities associated with a licensed private blockchain platform and determine whether a contract milestone has been met (e.g., a contract milestone between an HCP 120 and a payer 140 to determine whether a health parameter meets a certain expected standard within a certain period of time since the start of treatment), whether an expected contract outcome has been met (e.g., health parameters are maintained within a certain period of time), whether another contract-related event has occurred, etc. In some embodiments, upon determining that one or more contract events related to a contract have occurred, the smart contract layer (e.g., smart contract layer 680) may perform one or more actions as described in the contract. For example, a smart contract layer (e.g., smart contract layer 680) may: (a) report contract-related events to authorized entities of interest (e.g., such as parties to a contract); (b) report contract-related data, such as health parameters, cost metrics, and / or performance parameters (as authorized by the contract) to appropriate entities; (c) automatically initiate actions, such as invoicing, approval, payment, reporting, etc., without human intervention; and (d) store information about contract-related events and associate actions taken with respect to contract-related events with the corresponding contracts.
[0119] In addition, in some embodiments, the smart contract layer (e.g., smart contract layer 680) may initiate other actions to analyze the data and identify risks and / or other factors that may affect treatment, outcomes, etc. In some embodiments, the smart contract layer (e.g., smart contract layer 680) may initiate or be used to initiate machine learning tools and AI techniques based on the RWE associated with the multidimensional blockchain. For example, a particular drug (DIR) may be associated with multiple patients, and each DIR data record for the drug associated with a multidimensional block in the multidimensional blockchain may include some non-personal demographic information (age, medical condition, zip code, other drugs being prescribed, etc.) about the patient to whom the drug has been prescribed (e.g., received via an EHR block). In some embodiments, (e.g., the data in the multidimensional blockchain has been appropriately validated using functionality associated with the smart contract layer before the multidimensional block is submitted) when a specified number of transactions related to the drug have occurred and / or a specified period of time has passed (e.g., since the introduction of the drug or the last machine learning run), the smart contract layer (e.g., smart contract layer 680) may initiate machine learning based on the DIR data records associated with the drug for multiple patients. Machine learning may be able to predict the potential risks (medical conditions, side effects, drug interactions, etc.) associated with a drug or improve the awareness of the potential risks, and / or identify situations where the drug efficacy is higher than the standard, customize the dosage, etc. Therefore, pharmaceutical companies and medical device providers (e.g., PMDP130) may be able to understand the effects of drugs on different demographic groups, change dosages, monitor adverse outcomes, etc. This data correlation (e.g., via a multidimensional block chain) may enable preventive measures to be taken (e.g., reduce or increase dosages, identify previously unknown drug interactions, etc.), which may reduce patient risks, increase safety and health outcomes, while also reducing costs. In addition, in the case of DIR records that can be determined to be associated with a specific prediction, an entity (e.g., PMDP 130) may use a corresponding multidimensional block (e.g., associated with those DIRs) to further verify the prediction (e.g., to determine whether further research is needed).
[0120] In step 740, the first entity may enable at least one of the one or more second entities to access the multidimensional block chain. In some embodiments, the multidimensional block may be encrypted based on a cryptographic hash function (e.g., as relative to Figure 6BThe method 700 is described above and stores a multidimensional block chain including the multidimensional block to enable access to the multidimensional block, and the multidimensional block has access permissions that enable access by the one or more second entities. For example, the multidimensional block chain may be stored in a memory coupled to a processor or computer system that performs the method 700. In some embodiments, the multidimensional block may be stored in a cloud-based storage device and enabled to be accessed by appropriate entities associated with the licensed private block chain platform. As described above, although entities associated with the licensed private block chain platform may be able to verify the integrity of the information associated with the enhanced multidimensional block, data records (e.g., data records 520, 530, and 540) that may be associated with a particular entity may remain private to those entities. In addition, as described above, a multidimensional block (e.g., multidimensional block 655) may include links between local data records (e.g., data records 520, 530, and 540), which may form blocks in corresponding different local block chains (e.g., 525, 535, and 545, respectively) in some cases.
[0121] Figure 8 Smart contracts associated with a smart contract layer (e.g., smart contract layer 680) are shown. Figure 8As shown, smart contract 1810 can be implemented to reflect the agreement between the contract entities payer 140, patient 805 and HCP 120. Smart contract 2820 can be implemented to reflect the agreement between payer 140 and PMDP 130. Smart contract 3830 can be implemented to reflect the agreement between PMDP 130 and patient 805, while smart contract 4840 can be implemented to reflect the agreement between PMDP 130 and HCP 120. In some embodiments, smart contracts (e.g., smart contract 1810, smart contract 2820, smart contract 3830 and smart contract 4840) can be stored in a contract database. In some embodiments, each smart contract (e.g., smart contract 1810, smart contract 2820, smart contract 3830 and smart contract 4840) may include a program code having rules for evaluating data associated with a multidimensional block in a multidimensional block chain. In some embodiments, the smart contract layer (e.g., smart contract layer 680) can (on behalf of the receiving entity) decrypt the information in one or more sub-blocks, and make a determination based on the code / rules associated with the corresponding smart contract. For example, an entity may delegate some functions to the smart contract layer, or the smart contract layer may act as an agent of the entity when the entity is authorized. In some embodiments, one or more entities may share information securely with the smart contract layer for data verification and / or contract management. The smart contract layer (e.g., smart contract layer 680) may mark data errors, ensure the consistency of data reported by an entity to other entities associated with a licensed private block chain platform, perform data verification, specify and / or monitor information interfaces and / or data sharing between entities to ensure that authorized data is shared. For example, the smart contract layer (e.g., smart contract layer 680) may use global field IDs and / or known correlations between fields to ensure that the data reported by an entity to other entities for transactions is consistent. As an example, the smart contract layer 680 may ensure that the information (e.g., blood pressure) in the medical parameter fields reported by HCP 120 to patients 805 and payers 140 is consistent.
[0122] Due to the information sharing of sub-blocks on the permission-based private blockchain platform, the smart contract layer (e.g., smart contract layer 680) may be able to implement contracts between multiple entities, such as smart contracts 1 810 between entity payers 140, patients 805, and HCP 120. As described above, conventional systems may not be able to implement contracts between more than two entities. In addition, the multidimensional block chain ensures the data security of data records associated with a particular entity (so that the data records cannot be decrypted by other unauthorized entities). In addition, because the final data blocks (e.g., 520, 530, and 540) in different local blockchains (e.g., 525, 535, and 545, respectively) correspond to the data records in the final multidimensional block (e.g., multidimensional block 655), the entities associated with the permission-based private blockchain platform (e.g., HCP 120, PMDP 130, and payer 140) share a consistent and coherent view of information, which can be easily associated with the local blockchain. The smart contract layer (e.g., smart contract layer 680) may also facilitate rapid system updates because the same contract may apply to a class of entities (e.g., patients 805) when applicable. Thus, for example, an update to smart contract 1810 to reflect payer 140 approval of a new drug for a medical condition would be quickly available to all patients associated with smart contract 1810 (e.g., patients similar to patient 805 associated with payer 140 and treated for a medical condition by HCP 120). Furthermore, the impact of smart contract changes is local. Changes to smart contract 4840 between PMDP 130 and HCP 120 will only affect the entities involved. In conventional systems, changes to smart contract 4840 between PMDP 130 and HCP 120 may affect only the entities involved. In conventional systems, changes to smart contract 4840 may be localized due to other contracts / entities (e.g., such as Figure 1B The Appendix described in the Appendix may be linked to a contract between two entities, so the chain reaction may affect other entities / contracts.
[0123] In some embodiments, as described above, the smart contract layer (e.g., smart contract layer 680) can evaluate the contract periodically (e.g., at specified time intervals) and / or upon occurrence of contract-related events (e.g., transactions and / or multidimensional block additions), upon entity request, and / or as agreed to by the entities associated with the contract. For example, the smart contract layer 680 can evaluate conditions associated with the smart contract 1810 between the HCP 120, the payer 140, and the patient 105. In the above example, the smart contract 1810 can indicate: (a) information authorized to be shared between the entities (e.g., using sub-blocks); (b) specifying contract milestones (e.g., contract milestones between the HCP 120 and the payer 140 to determine whether a health parameter of the patient 805 meets a certain expected standard within a certain period of time since the start of treatment); (c) specifying criteria for contract fulfillment; and (d) specifying actions to be initiated upon contract / milestone fulfillment.
[0124] For example, a milestone in the smart contract 1 may specify that the blood pressure of the patient 805 decreases below a certain range within a period of time, and specify a first payment from the payer 140 to the HCP 120 when the milestone is met within a certain period of time. In addition, if the blood pressure range of the patient 805 remains within a specified range for a certain period of time, the smart contract 1 may specify an additional payment from the payer 140 to the HCP 120. When the HCP 120 submits the data record (with the appropriate sub-blocks that can be decrypted by the payer 140), the smart contract 1 can determine the time elapsed since the start of treatment (e.g., based on the timestamps associated with the corresponding multidimensional blocks associated with the patient 805 and the HCP 120) and check the blood pressure range. If the milestone has been met, the smart contract 1 can report the milestone to the entity, save the information associated with the milestone, generate an invoice with the appropriate information, and initiate payment from the payer 140 to the HCP 120. At a subsequent time, smart contract 1 may determine that patient 805's blood pressure range has remained within a specified range (e.g., based on a timestamp associated with a corresponding multidimensional block associated with patient 805 and HCP 120), report the result to the entity, save information associated with the result determination, generate an invoice, report, etc. with appropriate information, and initiate another payment from payer 140 to HCP 120.
[0125] In some embodiments, upon determining that one or more contractual events associated with a contract have occurred, the smart contract layer (e.g., smart contract layer 680) may perform one or more actions as described in the contract. For example, the smart contract layer (e.g., smart contract layer 680) may: (a) report the contract associated with the event to an authorized entity of interest (e.g., such as a contract party); (b) report contract-related data, such as health parameters, cost indicators, and / or performance parameters (as authorized by the contract) to the appropriate entity; (c) automatically initiate actions, such as invoicing, approval, payment, reporting, etc., without human intervention; (d) store information about contract-related events and associate actions taken with contract-related events with corresponding contracts; and / or (e) launch tools (e.g., machine learning, etc.) to analyze data associated with the multi-dimensional blockchain.
[0126] Fig. 9An exemplary computer 900 that can be beneficial to the security of the healthcare system and improve interoperability is shown. In some embodiments, the computer 900 can host and / or interact with a licensed private block chain platform. In some embodiments, the exemplary computer 900 can be a server, or a server (e.g., an application server) running for one or more entities (such as, HCP 120, PMDP 130 and / or payer 140). In some embodiments, the computer 900 can implement method 700 and / or other technologies disclosed herein. In some embodiments, the computer 900 can form a part of a distributed computing system that can implement a licensed private block chain platform. In some embodiments, the distributed computing system and / or the computer 900 can be cloud-based.
[0127] In some embodiments, the computer 900 / processor 950 may be capable of processing transaction requests, including requests related to adding blocks to a blockchain (including a multi-dimensional blockchain). In addition, the computer 900 / processor 950 may be capable of running encryption and / or decryption algorithms, obtaining hashes of information blocks, verifying hashes, performing digital signatures, and may be capable of performing and / or supporting various methods for improving security and facilitating authentication. Authentication may refer to both: verifying the integrity of stored information (e.g., in a block in a blockchain to determine any unauthorized changes), and ensuring that entities accessing a licensed private blockchain platform are trusted and have permission to perform any requested transactions. In some embodiments, the computer 900 / processor 950 may also enhance (create or add to) a blockchain (including enhancing a multi-dimensional blockchain with a multi-dimensional block) with a new block. In some embodiments, the computer 900 / processor 950 may also store and execute smart contracts associated with the blockchain to implement agreements between entities (e.g., HCP 120, PMDP 130, payer 140 and / or patient) related to privacy, information sharing, contract enforcement, etc.
[0128] In some embodiments, the computer 900 / processor 750 may be capable of analyzing and using machine learning techniques to determine the relationship between various health parameters. For example, the computer 900 / processor 950 may include one or more neural network processors, and / or a distributed processor that can be configured as a neural network and / or can execute software to model and / or simulate neural networks, which can be used to implement machine learning. For example, the PMDP 130 can use RWE information based on machine learning techniques available through multidimensional blocks (e.g., demographic information, side effects, drugs used in combination with a specified drug of interest, treatment results, etc.) to customize the use of drugs. For example, machine learning can be used to determine effective doses, target drugs based on demographic characteristics, improve drug interaction information, improve safety, determine the relative efficacy of various modes of administration, etc. As described above, the PMDP 130 may not be able to obtain this information outside of clinical trials, thereby hindering or severely limiting the use of machine learning and AI technologies.
[0129] In some embodiments, the computer 900 can be coupled to other computers using a communication / network interface 902, which can include wired (e.g., Ethernet including Gigabit Ethernet) and wireless interfaces. The wireless interface can be based on: a wireless wide area network (WWAN) standard, such as a cellular standard, including 3G, 4G, and 5G standards; an IEEE 802.11x standard, which is commonly referred to as Wi-Fi.
[0130] The computer 900 may include a memory 904, which may include one or more of the following: read-only memory (ROM), programmable read-only memory (PROM), various types of random access memory (RAM), non-volatile RAM, etc. The memory 904 may be implemented within the processor 950 or external to the processor 950. As used herein, the term "memory" refers to any type of long-term memory, short-term memory, volatile memory, non-volatile memory, or other memory, and is not limited to any particular type of memory or any number of memories, or any type of medium on which memory is stored.
[0131] The memory may include a cache memory, a main memory, and an auxiliary memory. The auxiliary memory may include a computer-readable medium 920. The computer-readable medium may include a magnetic and / or optical medium, which may be a removable medium in some cases. The removable medium may include an optical disc such as a compact disc (CD), a laser disc, a digital video disc (DVD), a Blu-ray disc, and other optical media, and also includes a USB drive, a flash drive, a solid-state drive, a memory card, etc. The computer 900 may also include a storage device 960, which may include a hard drive, a solid-state drive (SSD), a flash memory, other non-volatile storage devices, and a cloud-based storage device.
[0132] The communications / network interface 902, storage 960, memory 904, and computer readable media 920 may be coupled to the processor 950 using connections 906, which may take the form of a bus, wire, fiber, link, or the like.
[0133] The methods described herein can be implemented in various ways depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the processor 950 can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), neural network processors (NNPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.
[0134] For firmware and / or software implementations, the methods may be implemented using microcode, routines, functions, and firmware and / or software that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions may be used to implement the methods described herein. For example, the software may be stored in storage device 960 and / or on a removable computer-readable medium. The program code may reside on computer-readable medium 920, storage device 960, and / or memory 904, and may be read and executed by processor 950.
[0135] If implemented in firmware and / or software, these functions may also be stored as one or more instructions or codes in the computer-readable medium 920, storage device 960, and / or memory 904. Examples include computer-readable media encoded with data structures and computer programs. For example, the computer-readable medium 920 may include program code stored thereon, which may include program code supporting methods for facilitating the security of the healthcare system and improving system interoperability, including supporting multi-dimensional blockchains, smart contracts, consensus determination, and performing other functions associated with the permissioned private blockchain platform as described herein.
[0136] Processor 950 may be implemented using a combination of hardware, firmware, and software. In some embodiments, computer 900 may be coupled to a display to facilitate viewing the GUI and interacting with administrators and other users.
[0137] Although the present disclosure has been described in conjunction with specific embodiments for illustrative purposes, the present disclosure is not limited thereto. Various adjustments and modifications may be made to the present disclosure without departing from the scope of the present disclosure. Therefore, the essence and scope of the appended claims should not be limited by the foregoing description.
Claims
1. A method implemented by a processor, the method include: In response to a transaction conducted at a first time, receiving at a first entity from one or more second entities encrypted blocks of information related to the transaction, wherein each encrypted block of information is received from a different second entity and each encrypted block of information includes at least one sub-block capable of being decrypted by the first entity; decrypting, by the first entity, the decryptable sub-block; enhancing, by the first entity, a multidimensional blockchain, wherein the multidimensional blockchain is enhanced with a multidimensional block, the multidimensional block being formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a blockchain associated with the transaction and maintained by the first entity, wherein the multidimensional block comprises a data record in each dimension, wherein the data records corresponding to a dimension form a block in a different blockchain associated with the corresponding second entity; as well as At least one second entity of the one or more second entities is enabled to access the multi-dimensional block chain.
2. The method of claim 1, wherein for each received encrypted information block, the corresponding sub-block that can be decrypted by the first entity is based on an information interface between the first entity and a corresponding second entity. 3 . The method of claim 2 , wherein the information interface between the first entity and the corresponding second entity is determined based on predefined rules governing interactions between the first entity and the corresponding second entity.
4. The method of claim 2, wherein the information interface between the first entity and the corresponding second entity is determined by a smart contract associated with the multi-dimensional blockchain.
5. The method of claim 1, wherein enabling access to the multi-dimensional blockchain include: encrypting the multidimensional block based on a hash function; as well as The multi-dimensional block chain including the multi-dimensional blocks having access permissions enabling access by the one or more second entities is stored.
6. The method of claim 1, wherein decrypting the sub-block include: receiving, by the first entity, a corresponding authorization code from the one or more second entities associated with the received encrypted information block; as well as The decryptable sub-block is decrypted using the received authorization code.
7. The method of claim 1, wherein the current block comprises one or more sub-blocks, wherein each sub-block in the current block is based on an information interface between the first entity and a corresponding second entity and can be decrypted by the corresponding second entity.
8. The method of claim 1, wherein the first entity comprises at least one server associated with at least one of a pharmaceutical provider or a medical device provider.
9. The method of claim 1, wherein the one or more second entities include one or more servers associated with at least one of a healthcare provider or an insurance provider or a patient.
10. The method of claim 1, wherein the first entity and the one or more second entities are computing nodes in a distributed computing system, and the multi-dimensional blockchain forms part of a permissioned private blockchain platform.
11. The method according to claim 10, further comprising: include: Upon augmenting the multi-dimensional blockchain with the multi-dimensional block, at least one smart contract associated with the permissioned private blockchain platform is triggered by the first entity.
12. The method according to claim 11, further comprising: include: Based at least in part on information associated with the multi-dimensional blockchain, an indication is received from the smart contract to complete one or more contractual milestones between the first entity and the one or more second entities.
13. A server for a first entity, the server include: Memory, communication interface, and a processor coupled to the memory and the communication interface, wherein the processor is configured to: In response to a transaction conducted at a first time, receiving at the first entity, via the communication interface, from one or more second entities, encrypted blocks of information related to the transaction, wherein each encrypted block of information is received from a different second entity and each encrypted block of information includes at least one sub-block capable of being decrypted by the first entity; decrypting, by the first entity, the decryptable sub-block; enhancing, by the first entity, a multidimensional block chain residing in the memory, wherein the multidimensional block chain is enhanced with a multidimensional block formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity, wherein the multidimensional block includes a data record in each dimension, wherein the data records corresponding to a dimension form a block in a different block chain associated with the corresponding second entity; as well as At least one second entity of the one or more second entities is enabled to access the multi-dimensional block chain.
14. The server of claim 13, wherein for each received encrypted information block, the corresponding sub-block that can be decrypted by the first entity is based on an information interface between the first entity and a corresponding second entity.
15. The server of claim 14, wherein the information interface between the first entity and the corresponding second entity is determined based on predefined rules governing interactions between the first entity and the corresponding second entity.
16. The server of claim 14, wherein the information interface between the first entity and the corresponding second entity is determined by a smart contract associated with the multi-dimensional blockchain.
17. The server of claim 13, wherein to enable access to the multi-dimensional block chain, the processor is configured to: encrypting the multi-dimensional block based on a hash function; and The multidimensional block chain including the multidimensional block is stored in the memory.
18. The server of claim 13, wherein to decrypt the sub-block, the processor is configured to: receiving, by the first entity, a corresponding authorization code from the one or more second entities associated with the received encrypted information block; and The decryptable sub-block is decrypted using the received authorization code.
19. The server of claim 13, wherein the current block comprises one or more sub-blocks, wherein each sub-block in the current block is based on an information interface between the first entity and a corresponding second entity and can be decrypted by the corresponding second entity.
20. The server of claim 13, wherein the first entity comprises at least one server associated with at least one of a pharmaceutical provider or a medical device provider.
21. The server of claim 13, wherein the one or more second entities include one or more servers associated with at least one of a healthcare provider or an insurance provider or a patient.
22. The server of claim 21, wherein the first entity and the one or more second entities are computing nodes in a distributed computing system, and the multi-dimensional blockchain forms part of a permissioned private blockchain platform.
23. The server of claim 22, wherein the processor is further configured to: Upon augmenting the multi-dimensional blockchain with the multi-dimensional block, at least one smart contract associated with the permissioned private blockchain platform is triggered.
24. The server of claim 22, wherein the processor is further configured to: Based at least in part on information associated with the multi-dimensional blockchain, an indication is received from a smart contract to complete one or more contractual milestones between the first entity and the one or more second entities.
25. A non-transitory computer readable medium comprising executable instructions to configure a processor to: In response to a transaction conducted at a first time, receiving at a first entity, via a communication interface, from one or more second entities, encrypted blocks of information related to the transaction, wherein each encrypted block of information is received from a different second entity and each encrypted block of information includes at least one sub-block capable of being decrypted by the first entity; decrypting, by the first entity, the decryptable sub-block; enhancing, by the first entity, a multidimensional block chain residing in a memory, wherein the multidimensional block chain is enhanced with a multidimensional block formed by linking at least one of the encrypted information blocks received from the one or more second entities to a current block, the current block being added to a block chain associated with the transaction and maintained by the first entity, wherein the multidimensional block includes a data record in each dimension, wherein the data records corresponding to a dimension form a block in a different block chain associated with the corresponding second entity; as well as At least one second entity of the one or more second entities is enabled to access the multi-dimensional block chain.
