# US 12,009,073 B2 · Blockchain architecture, system, method and device for facilitating secure medical testing, data collection and controlled distribution using a decentralized health information platform and token ecosystem

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

- Number: US 12,009,073 B2
- Document ID: US12009073B2
- Status: Granted
- Kind: B2
- Application number: 17/322,217
- Filed: 2021-05-17
- Published: 2021-11-11
- Granted: 2024-06-11
- Earliest claimed: 2020-04-22
- Assignees: Atrium Separate IP Holdings Number 4, LLC
- Applicants: Atrium Separate IP Holdings Number 1, LLC
- Inventors: H. Anthony DeRosa-Grund
- Web page: https://patentgrep.com/patent/US12009073B2

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06F 16/289: {Object oriented databases}
- G06F 21/32: using biometric data, e.g. fingerprints, iris scans or voiceprints
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/1235: {with control of digital rights management [DRM]}
- G06Q 20/3823: {combining multiple encryption tools for a transaction}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/383: {Anonymous user system}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/4012: {Verifying personal identification numbers [PIN]}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 20/4015: {using location information}
- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0407: {wherein the identity of one or more communicating identities is hidden (cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00)}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 67/104: Peer-to-peer [P2P] networks
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- G06Q 2220/00: Business processing using cryptography
- G06Q 2220/16: Copy protection or prevention
- H04L 63/126: {the source of the received data}
- H04L 2209/42: Anonymization, e.g. involving pseudonyms
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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)
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A distributed transaction and data storage platform including a distributed notary ledger or blockchain and one or more individual user micro-identifier chains that together enable the secure effectuation and recordation of one or more transactions, and/or storage of data in an automated, real-time, zero-trust, globally data law and privacy law centric manner while maintaining transaction party confidentiality and preventing chain poisoning.

## Claims

### Claim 1

A blockchain platform for recording medical status data of a plurality of users having accounts on the platform, the platform comprising:
a micro-identification blockchain array formed by a stack of a plurality of micro-identification blockchains, wherein each one of the micro-identification blockchains is dedicated to a single one of the users and the one of the micro-identification blockchains stores a native identifier of one of the users, a coded identifier of the one of the users and a set of personal information about the one of the users;
a user device including a user device processor and a device memory storing a medical status application that when executed by the user device processor causes the device to:
record and store biometric data of the user;
receive a test request command from the user via a graphical user interface of the device, the test request identifying a test;
generate a test unique identifier that is associated with the user and the test;
authenticate the identity of the user by determining when if stored biometric data of the user matches current measured biometric data; and
providing the test unique identifier to the user on the device when the stored biometric data of the user matched the current measured biometric data; and
a server including a server processor and a non-transitory computer-readable medium storing at least one platform operating system that when executed by the server processor causes the server to:
receive a medical status transaction request identifying a pending medical status object, the medical status transaction request including the test unique identifier and results of the test, the results of the test indicating a medical status of the user;
determine the micro-identification blockchain dedicated to the user associated with the test unique identifier; and
generate and post the pending medical status object as a single transaction block on the micro-identification blockchain of the user associated with the test unique identifier.

### Claim 2 (depends on 1)

The blockchain platform of claim 1, wherein when executed by the server processor, the at least one operating system causes the server to assign an expiration date to the medical status based on an expected duration of the medical status and when the test was administered.

### Claim 3 (depends on 2)

The blockchain platform of claim 2, wherein the expiration date is calculated by adding an expected duration of the medical status to a time when the test was administered.

### Claim 4 (depends on 3)

The blockchain platform of claim 3, wherein when executed by the device processor, the medical status application causes the user device to generate and provide a reminder message to the user when a current time is within a threshold range of the expiration date, the reminder message identifying the medical status and the expiration date of the medical status.

### Claim 5 (depends on 4)

The blockchain platform of claim 4, wherein when executed by the device processor, the medical status application causes the user device to:
receive a display medical status request command on the user device from the user;
determine whether the current time is before the expiration date;
generate and display a status image indicating the medical status on the user device when the current time is before the expiration date.

### Claim 6 (depends on 4)

The blockchain platform of claim 4, wherein when executed by the device processor, the medical status application causes the user device to:
receive display medical status request command on the user device from the user;
determine whether the current time is before the expiration date; and
generate and display a status image indicating that the medical status has expired on the user device when the current time is not before the expiration date.

### Claim 7 (depends on 5)

The blockchain platform of claim 5, wherein when executed by the device processor, the medical status application causes the user device to generate a map indicating a location and one of a plurality of entity statuses of one or more entities, wherein a first of the entity statuses indicates all employees of the entity have a desired medical status and a second of the entity statuses indicates less than all employees of the entity have the desired medical status.

### Claim 8 (depends on 7)

The blockchain platform of claim 7, wherein when executed by the device processor, the medical status application causes the user device to generate a map indicating one or more risk locations where persons having an infectious medical status have visited within a predetermined time period.

### Claim 9 (depends on 1)

The blockchain platform of claim 1, wherein when executed by the device processor, the medical status application causes the user device to:
receive an at-home test request command from the user via the graphical user interface of the user device, the test request identifying an at-home test;
authenticate the identity of the user by determining when the stored biometric data of the user matches current measured biometric data;
continuously monitor that the user stays within a field of view of a camera of the user device from when the identity of the user is authenticated until the at-home test is taken;
visually capture results of the at-home test using images of the user device; and
transmit the results of the at-home test to the operating system for posting onto the micro-identification blockchain of the user.

### Claim 10

A non-transitory computer-readable medium storing a medical status application for verifying medical statuses of a plurality of users using a micro-identification blockchain array formed by a stack of a plurality of micro-identification blockchains, wherein each one of the micro-identification blockchains is dedicated to a single one of the users and the one of the micro-identification blockchains stores a native identifier of one of the users, a coded identifier of the one of the users and a set of personal information about the one of the users, wherein when executed by a processor the medical status application causes the processor to:
record and store biometric data of the user on the medium; receive a test request command from the user via a graphical user interface of the device, the test request identifying a test;
generate a test unique identifier that is associated with the user and the test;
authenticate the identity of the user by determining when the stored biometric data of the user matches current measured biometric data;
provide the test unique identifier to the user on the device when the stored biometric data of the user matched the current measured biometric data; and
transmit a medical status transaction request to an operating system operating the micro-identification array, the medical status transaction request identifying a pending medical status object, the medical status transaction request including the test unique identifier and results of the test, the results of the test indicating a medical status of the user.

### Claim 11 (depends on 10)

The medium of claim 10, wherein when executed by a processor the medical status application causes the processor to assign an expiration date to the medical status based on an expected duration of the medical status and when the test was administered.

### Claim 12 (depends on 11)

The medium of claim 11, wherein the expiration date is calculated by adding an expected duration of the medical status to a time when the test was administered.

### Claim 13 (depends on 12)

The medium of claim 12, wherein when executed by a processor the medical status application causes the processor to generate and provide a reminder message to the user when a current time is within a threshold range of the expiration date, the reminder message identifying the medical status and the expiration date of the medical status.

### Claim 14 (depends on 13)

The medium of claim 13, wherein when executed by a processor the medical status application causes the processor to:
receive a display medical status request command from the user;
determine whether the current time is before the expiration date;
generate and display a status image indicating the medical status on a user device when the current time is before the expiration date.

### Claim 15 (depends on 13)

The medium of claim 13, wherein when executed by a processor the medical status application causes the processor to:
receive display medical status request command from the user;
determine whether the current time is before the expiration date; and
generate and display a status image indicating that the medical status has expired on a user device when the current time is not before the expiration date.

### Claim 16 (depends on 14)

The medium of claim 14, wherein when executed by a processor the medical status application causes the processor to generate a map indicating a location and one of a plurality of entity statuses of one or more entities, wherein a first of the entity statuses indicates all employees of the entity have a desired medical status and a second of the entity statuses indicates less than all employees of the entity have the desired medical status.

### Claim 17 (depends on 16)

The medium of claim 16, wherein when executed by a processor the medical status application causes the processor to generate a map indicating one or more risk locations where persons having an infectious medical status have visited within a predetermined time period.

### Claim 18 (depends on 10)

The medium of claim 10, wherein when executed by a processor the medical status application causes the processor to:
receive an at-home test request command from the user via the graphical user interface of a user device, the test request identifying an at-home test;
authenticate the identity of the user by determining when the stored biometric data of the user matches current measured biometric data;
continuously monitor that the user stays within a field of view of a camera of the user device from when the identity of the user is authenticated until the at-home test is taken;
visually capture results of the at-home test using images of the user device; and
transmit the results of the at-home test to the operating system for posting onto the micro-identification blockchain of the user.

### Claim 19

A method of verifying medical statuses of a plurality of users using a micro-identification blockchain array formed by a stack of a plurality of micro-identification blockchains, wherein each one of the micro-identification blockchains is dedicated to a single one of the users and the one of the micro-identification blockchains stores a native identifier of one of the users, a coded identifier of the one of the users and a set of personal information about the one of the users, the method comprising:
with a medical status application stored on a device memory of a user device:
record and store biometric data of the user;
receive a test request command from the user via a graphical user interface of the device, the test request identifying a test;
generate a test unique identifier that is associated with the user and the test;
authenticate the identity of the user by determining when the stored biometric data of the user matches current measured biometric data; and
provide the test unique identifier to the user on the device when the stored biometric data of the user matched the current measured biometric data; and
with an operating system stored on a server memory of a server:
receive a medical status transaction request identifying a pending medical status object, the medical status transaction request including the test unique identifier and results of the test, the results of the test indicating a medical status of the user;
determine the micro-identification blockchain dedicated to the user associated with the test unique identifier; and
generate and post the pending medical status object as a single transaction block on the micro-identification blockchain of the user associated with the test unique identifier.

### Claim 20 (depends on 19)

The method of claim 19, further comprising, with the server, assigning an expiration date to the medical status based on an expected duration of the medical status and when the test was administered.

### Claim 21 (depends on 20)

The method of claim 20, wherein the expiration date is calculated by adding an expected duration of the medical status to a time when the test was administered.

### Claim 22 (depends on 21)

The method of claim 21, further comprising, with the medical status application, generating and providing a reminder message to the user when a current time is within a threshold range of the expiration date, the reminder message identifying the medical status and the expiration date of the medical status.

### Claim 23 (depends on 22)

The method of claim 22, further comprising, with the medical status application:
receiving a display medical status request command on the user device from the user;
determining whether the current time is before the expiration date;
generating and displaying a status image indicating the medical status on the user device when the current time is before the expiration date.

### Claim 24 (depends on 22)

The method of claim 22, further comprising, with the medical status application:
receiving display medical status request command on the user device from the user;
determining whether the current time is before the expiration date; and
generating and displaying a status image indicating that the medical status has expired on the user device when the current time is not before the expiration date.

### Claim 25 (depends on 23)

The method of claim 23, further comprising, the medical status application, generating a map indicating a location and one of a plurality of entity statuses of one or more entities, wherein a first of the entity statuses indicates all employees of the entity have a desired medical status and a second of the entity statuses indicates less than all employees of the entity have the desired medical status.

### Claim 26 (depends on 25)

The method of claim 25, further comprising, the medical status application, generating a map indicating one or more risk locations where persons having an infectious medical status have visited within a predetermined time period.

### Claim 27 (depends on 19)

The method of claim 19, further comprising, the medical status application:
receiving an at-home test request command from the user via the graphical user interface of the user device, the test request identifying an at-home test;
authenticating the identity of the user by determining when the stored biometric data of the user matches current measured biometric data;
continuously monitoring that the user stays within a field of view of a camera of the user device from when the identity of the user is authenticated until the at-home test is taken;
visually capturing results of the at-home test using images of the user device; and
transmitting the results of the at-home test to the operating system for posting onto the micro-identification blockchain of the user.