# US 2019/0378599 A1 · Zero knowledge multi-party prescription management and drug interaction prevention system

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

- Number: US 2019/0378599 A1
- Document ID: US20190378599A1
- Status: Published application
- Kind: A1
- Application number: 16/004,336
- Filed: 2018-06-08
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Michael A. Amisano; John F. Behnken; Jeb R. Linton; John L. Melchionne; David K. Wright
- Web page: https://patentgrep.com/patent/US20190378599A1

## CPC

- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G06F 16/951: Indexing; Web crawling techniques
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for implementing a secure system to prevent adverse drug interactions and repeat prescriptions, for a patient, in a multi-party computing environment. The method includes receiving a patient identifier from a provider, authenticating an access by the provider, and retrieving a second patient identifier, wherein the second patient identifier corresponds to the received patient identifier, wherein the received patient identifier and the second patient identifier are different. The method further includes receiving an input from the provider that corresponds to the patient identifier, and accessing a database that contains a stored private ID, wherein the stored private ID is a combination of the received patient identifier and the retrieved second patient identifier, and wherein the database includes data relating to the patient. The method includes searching the database to obtain a search result based on the received input from the provider, and transmitting the search result to the provider.

## Claims

### Claim 1

A method comprising:
receiving, by a first computer, a patient identifier from a provider, wherein the patent identifier corresponds to a patient;
authenticating, by the first computer, an access by the provider;
retrieving, by the first computer, a second patient identifier, wherein the second patient identifier corresponds to the received patient identifier, wherein the received patient identifier and the second patient identifier are different;
receiving, by the first computer, an input from the provider that corresponds to the received patient identifier;
accessing, by the first computer, a secure database that contains a stored private identifier (ID), wherein the stored private ID is a combination of the received patient identifier and the retrieved second patient identifier, and wherein the secure database includes data relating to the patient;
searching, by the first computer, the secure database to obtain a search result based on the received input from the provider; and
transmitting, by the first computer, the search result to the provider.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
generating, by the first computer, the second patient identifier based on the received patient identifier;
generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier; and
storing, by the first computer, the generated private ID in the secure database.

### Claim 3 (depends on 2)

The method of claim 2, wherein generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier is accomplished using an oblivious pseudo-random function (OPRF).

### Claim 4 (depends on 1)

The method of claim 1, wherein searching, by the first computer, the secure database to obtain the search result based on the received input from the provider further comprises at least one of the following:
identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database; and
identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database.

### Claim 5 (depends on 4)

The method of claim 4, wherein identifying the contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID, further comprises:
consulting a reference database that comprises a pre-populated table of contraindications for one or more drugs relating to the received input from the provider.

### Claim 6 (depends on 1)

The method of claim 1, wherein searching, by the first computer, the secure database to obtain the search result based on the received input from the provider is done using a private set intersection (PSI) function.

### Claim 7 (depends on 1)

The method of claim 1, wherein transmitting, by the first computer, the search result, further comprises at least one of the following:
in response to identifying a duplication of the received input, from the provider, that corresponds to the private ID in the secure database, returning a collision value to the provider; and
in response to identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, returning a yes value to the provider.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
in response to not identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database and in response to not identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, updating, by the first computer, the secure database to include the received input from the provider that corresponds to the private ID.

### Claim 9

A computer program product, comprising a non-transitory tangible storage device having program code embodied therewith, the program code executable by a processor of a computer to perform a method, the method comprising:
receiving, by a first computer, a patient identifier from a provider, wherein the patent identifier corresponds to a patient;
authenticating, by the first computer, an access by the provider;
retrieving, by the first computer, a second patient identifier, wherein the second patient identifier corresponds to the received patient identifier, wherein the received patient identifier and the second patient identifier are different;
receiving, by the first computer, an input from the provider that corresponds to the received patient identifier;
accessing, by the first computer, a secure database that contains a stored private identifier (ID), wherein the stored private ID is a combination of the received patient identifier and the retrieved second patient identifier, and wherein the secure database includes data relating to the patient;
searching, by the first computer, the secure database to obtain a search result based on the received input from the provider; and
transmitting, by the first computer, the search result to the provider.

### Claim 10 (depends on 9)

The computer program product of claim 9, further comprising:
generating, by the first computer, the second patient identifier based on the received patient identifier;
generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier; and
storing, by the first computer, the generated private ID in the secure database.

### Claim 11 (depends on 10)

The computer program product of claim 10, wherein generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier is accomplished using an oblivious pseudo-random function (OPRF).

### Claim 12 (depends on 9)

The computer program product of claim 9, wherein searching, by the first computer, the secure database to obtain the search result based on the received input from the provider further comprises at least one of the following:
identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database; and
identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database.

### Claim 13 (depends on 9)

The computer program product of claim 9, wherein transmitting, by the first computer, the search result, further comprises at least one of the following:
in response to identifying a duplication of the received input, from the provider, that corresponds to the private ID in the secure database, returning a collision value to the provider; and
in response to identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, returning a yes value to the provider.

### Claim 14 (depends on 9)

The computer program product of claim 9, further comprising:
in response to not identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database and in response to not identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, updating, by the first computer, the secure database to include the received input from the provider that corresponds to the private ID.

### Claim 15

A computer system, comprising:
one or more computer devices each having one or more processors and one or more tangible storage devices; and
a program embodied on at least one of the one or more storage devices, the program having a plurality of program instructions for execution by the one or more processors, the program instructions comprising instructions for:
receiving, by a first computer, a patient identifier from a provider, wherein the patent identifier corresponds to a patient;
authenticating, by the first computer, an access by the provider;
retrieving, by the first computer, a second patient identifier, wherein the second patient identifier corresponds to the received patient identifier, wherein the received patient identifier and the second patient identifier are different;
receiving, by the first computer, an input from the provider that corresponds to the received patient identifier;
accessing, by the first computer, a secure database that contains a stored private identifier (ID), wherein the stored private ID is a combination of the received patient identifier and the retrieved second patient identifier, and wherein the secure database includes data relating to the patient;
searching, by the first computer, the secure database to obtain a search result based on the received input from the provider; and
transmitting, by the first computer, the search result to the provider.

### Claim 16 (depends on 15)

The computer system of claim 15, further comprising:
generating, by the first computer, the second patient identifier based on the received patient identifier;
generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier; and
storing, by the first computer, the generated private ID in the secure database.

### Claim 17 (depends on 16)

The computer system of claim 16, wherein generating, by the first computer, the private ID based on the received patient identifier and the generated second patient identifier is accomplished using an oblivious pseudo-random function (OPRF).

### Claim 18 (depends on 15)

The computer system of claim 15, wherein searching, by the first computer, the secure database to obtain the search result based on the received input from the provider further comprises at least one of the following:
identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database; and
identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database.

### Claim 19 (depends on 15)

The computer system of claim 15, wherein transmitting, by the first computer, the search result, further comprises at least one of the following:
in response to identifying a duplication of the received input, from the provider, that corresponds to the private ID in the secure database, returning a collision value to the provider; and
in response to identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, returning a yes value to the provider.

### Claim 20 (depends on 15)

The computer system of claim 15, further comprising:
in response to not identifying a duplication of the received input from the provider that corresponds to the private ID in the secure database and in response to not identifying a contraindication of the received input, from the provider, with one or more inputs that correspond to the private ID in the secure database, updating, by the first computer, the secure database to include the received input from the provider that corresponds to the private ID.
