# US 2020/0402624 A1 · Electronic Healthcare Record Data Blockchain System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0402624 A1
- Document ID: US20200402624A1
- Status: Published application
- Kind: A1
- Application number: 16/906,946
- Filed: 2020-06-19
- Published: 2020-12-24
- Earliest claimed: 2019-06-19
- Assignees: Electronic Health Record Data, Inc.
- Applicants: Electronic Health Record Data, Inc.
- Inventors: Ronald Raymond Austring; Kenneth A. Hill, SR.; Brad T. Crosslin; Clinton S. Ferguson, III
- Web page: https://patentgrep.com/patent/US20200402624A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06Q 50/265: {Personal security, identity or safety}
- G07F 11/10: two or more magazines having a common delivery chute
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0414: {during transmission, i.e. party's identity is protected against eavesdropping, e.g. by using temporary identifiers, but is known to the other party or parties involved in the communication}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- G06Q 10/10: Office automation; Time management
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 30/0222: {During e-commerce, i.e. online transactions}
- G06Q 2220/00: Business processing using cryptography
- H04L 2209/42: Anonymization, e.g. involving pseudonyms
- H04L 2209/88: Medical equipments
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

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

## Claims

### Claim 1

A system for providing blockchain-based patient transactions, the system comprising:
one or more computer-readable storage media configured to store a blockchain;
a data Application Programming Interface (API) system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the data API system to:
receive a request for a new blockchain transaction related to a patient,
initiate a patient lookup query to determine whether a patient electronic health record exists,
generate a single purpose patient ID (SPPID) associated with the patient electronic health record;
a client computer programmed to execute computer program instructions that, when executed, cause the client computer to:
receive a patient lookup query related to a patient from a client to determine whether the patient's electronic health record exists,
receive the SPPID to initiate a new blockchain transaction related to the patient on the blockchain without patient-identifying information,
determine whether an entity operating the client computer can provide data, products and/or services related to a blockchain transaction; and
a blockchain API system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the blockchain API system to:
generate the blockchain transaction and read and write records to and from the blockchain, and
associate one or more smart contracts with the blockchain transaction.

### Claim 2 (depends on 1)

The system of claim 1, wherein the smart contract exchanges digital currency between the parties involved in the smart contract.

### Claim 3 (depends on 2)

The system of claim 2, wherein the digital currency includes utility tokens or vouchers.

### Claim 4 (depends on 1)

The system of claim 1, wherein the SPPID cannot be used to write information to the blockchain after a patient blockchain transaction is completed.

### Claim 5 (depends on 1)

The system of claim 1, wherein the blockchain API system can generate a notification when the blockchain transaction is generated.

### Claim 6 (depends on 1)

The system of claim 1, wherein the blockchain API system can transmit the notification to one or more providers.

### Claim 7 (depends on 1)

The system of claim 1, wherein the client computer can provide information to the blockchain API system regarding data, products and/or services related to the blockchain transaction.

### Claim 8 (depends on 1)

The system of claim 1, wherein the blockchain API system edits the blockchain transaction on the blockchain.

### Claim 9

A method of providing blockchain-based electronic health record data patient transactions, the method being implemented by a server system comprising one or more processors executing computer program instructions that, when executed, perform the method, the method comprising:
associating a single purpose patient ID (SPPID) with the electronic health record;
providing the SPPID to the client so the client can initiate a new blockchain patient transaction related to the patient on the blockchain without patient-identifying information;
receiving a patient transaction from a pharmacy;
writing the patient transaction to the blockchain;
notifying one or more client devices of the patient transaction;
receiving one or more offers for data, products, or services related to the patient transaction;
generating a smart contract related to the patient transaction and the one or more offers; and
modifying the patient transaction based on the execution of the smart contract.

### Claim 10 (depends on 9)

The method of claim 9, wherein the smart contract exchanges digital currency between the parties involved in the smart contract.

### Claim 11 (depends on 10)

The method of claim 10, wherein the digital currency includes utility tokens or vouchers.

### Claim 12 (depends on 9)

The method of claim 9, wherein the SPPID cannot be used to write information to the blockchain after the patient blockchain transaction is completed.

### Claim 13 (depends on 9)

The method of claim 9, further comprising generating a notification when the patient transaction is generated.

### Claim 14 (depends on 13)

The method of claim 13, further comprising transmitting the notification to one or more providers.

### Claim 15 (depends on 9)

The method of claim 9, wherein the patient transaction is modified on the blockchain.

### Claim 16 (depends on 15)

The method of claim 15, wherein the patient transaction is modified on the blockchain in real-time.

### Claim 17

A system for providing electronic health record data for blockchain-based patient transactions, the system comprising:
one or more computer-readable storage media configured to store a blockchain;
a data Application Programming Interface (API) system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the data API system to:
receive a request for a new blockchain transaction related to a patient,
retrieve the patient electronic health record from one or more databases, and
generate a single purpose patient ID (SPPID) associated with the patient electronic health record; and
a blockchain API system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the blockchain API system to:
generate the blockchain transaction and read and write records to and from the blockchain, and
associate one or more smart contracts with the blockchain transaction.

### Claim 18 (depends on 17)

The system of claim 17, wherein the smart contract exchanges digital currency between the parties involved in the smart contract.

### Claim 19 (depends on 18)

The system of claim 18, wherein the digital currency includes utility tokens or vouchers.

### Claim 20 (depends on 17)

The system of claim 17, wherein the blockchain API system edits the prescription transaction on the blockchain based on input from one or more providers.
