Electronic health record data block chain system

Abstract

An electronic health record (EHR) data blockchain system configured to allow a plurality of entities (e.g., pharmaceutical industry entities and consumers that may act as data, services, product providers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR data patient portal (e.g., EHR-Data-PP) to provide centralized locations for messages and subsequent edits, such as to provide for the provision of the EHR patient transaction blockchain (e.g., EHR-DATA-BC) to the EHR patient transaction blockchain (e.g., EHR-DATA-BC) and the EHR data patient portal (e.g., EHR-Data-PP). Therefore, consistent message data can be presented. The EHR data blockchain system may include an EHR data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR data API may access and retrieve patient identifiable information (PII) and generate a non-patient identifiable single-purpose patient ID (SPPID) for a particular patient. An EHR patient transaction blockchain API (e.g., EHR-DATA-BC-API) may: store SPPID, store specific discrete data for a patient retrieved from EHR, execute smart contracts, and control performance of digital currency transfers, among other functions.

Description

technical field [0001] The present disclosure relates generally to blockchain-enabled patient data systems, and more particularly to blockchain-enabled patient data systems configured to facilitate anonymous patient data transactions between multiple entities. Patient Data System. Background technique [0002] In traditional electronic patient record systems, the system is configured according to a conventional client-server model, where messages are sent to a server and the server sends a response according to standards and formats issued by the National Council of Prescription Drug Programs (NCPDP). Often, clients and servers may have inappropriate databases such as Database and MS database. Also, every message sent and received is logged by both client and server. Often, discrepancy may arise between the client and the server regarding the actual content of the message due to system issues or the like. [0003] In particular, pharmacy patient information messages m...

AI Technical Summary

Problems solved by technology

When each entity in the chain edits the message, add additional complexity that may result in additional message discrepancies

This can result in multiple databases with messages of differing message integrity

Such discrepancies lead to wasted effort, time and money devoted to resolving discrepancies

[0004] Furthermore, the availability of complete patient-identifiable data stored in databases invites the potential and increased likelihood of HIPPA violations and incorrect handling of such data

Multiple systems may be required to monitor prescriptions, provide edits, provide quotes, determine drug eligibility, identify fulfillment options, and finalize pricing, wasting valuable resources, adding complexity, and incurring excess costs

Images