Healthcare Blockchain Cryptosystem — Louis Galterio (US20240070627A1)

ABSTRACT

Abstract

Technologies discussed herein secure access to a Healthcare Blockchain. This apparatus is a collection of hardware and software. It utilizes new to the art encoded firmware specific to a patient or entities' unique identity as collection antennae to bridge to Web3 Blockchain distributed networks. It solves the problems in healthcare technology of incorrect, inconsistent, non-interoperable and disorganized data and patient information. Data normalization and validation, and continued processing occur via two way Oracles. Enablement of best embodiment for a sample use case is included in the Detailed Description and consists of A) Our “Internet of Things” or “IoT” antenna's coupled with software and B) New integrated software built into emergent blockchain tokens, API's, and smart contracts (simultaneously existing as firmware based “Smart Contracts” to pair with software counterparts). These new apparatus components along with various methods, creates our Web3 based Blockchain with integration pathway to Web2 and Web1 applications.

Description

TECHNICAL FIELD

The invention is related to the technical field of Blockchain and Web 3 distributed databases. Blockchain is a distributed electronic ledger running across a world-wide system of internet nodes and functions similar to internet distributed name services.

BACKGROUND THE INVENTION

From a technical perspective, the field of this invention generally relates to blockchain ledger entries (or resources) supported and validated based on consensus protocols. It is focused on the health care technology ecosystem. Due to the generational variation in the use of technology in healthcare, there exist multiple instances of incompatible software systems and incompatible approaches to the format of a standard record designation for patients and entities. There is need for a normalization mechanism that can solve this issue while taking into account the nature of constant change in the industry.

Various web resources may already exists in the public domain, either in the form of publication or usage and act as sources of information or motivation to the inception of the invention. Approaches over time in Web 1 and Web 2, and even from classical programming, were established to address specific problems or within specific software products for unique customers. As healthcare has evolved the need for interoperability of these systems is critical from cost, utilization, and patient safety perspectives.

BRIEF SUMMARY OF THE INVENTION

This introduces concepts further described in the Detailed Description. It is not intended to limit the scope of the claims.

The Healthcare Blockchain Crypto system encompasses integrated mechanisms and bridges software applications. The purpose is to correct health data that is inconsistent, wrong, unsecured, and non-interoperable with multiple technologies.

One object of the invention is to normalize and improve software and hardware incompatibilities within a dynamically changing environment. Another object of the invention is to insure data validation is consensus driven and interoperable across all systems affected so as to solve existing problems. Another object of the invention is to tokenize revenue flow through healthcare software and allocate payments and rewards to patients, payers, providers, and pharmacies in a system where graphene based antenna SIM cards guarantee identity of the actors.

In some embodiments, the present invention comprises telephony s, in other embodiments the present invention hyperlinks to tokenized smart contracts.

BRIEF DESCRIPTION DRAWINGS

FIG. 1 : This figure relates to claims 1 - 8 and lists in table format, the technology innovations created by and within the Healthcare Blockchain Cryptosystem. The apparatus and system is composed of hardware, software, and methods.

FIG. 2 : This figure relates to claim 8 . It is a pictorial representation of the Medical Hub Exchange described in the detailed description.

FIG. 3 : Cross Walked Mapping Entity Systems (Five Lists Notated A-E). This figure relates to claim 7 and illustrates the abundance of key databases and lists in health care that must be treated as joined parameters by providers.

FIG. 4 : This figure relates to both claims

1 and 8 . It shows a high level interactions overview of bi-directional bridging between Physical and Cryptosystem like Metaverse (Mirror Database) and addresses spontaneous smart contract evolution based on natural selection and neuro network programming and networks.

FIG. 5 : This figure presents a pictorial overview of existing Iot (Internet of Things) technology. This figure relates to both claims

1 and 2 .

FIG. 6 : This figure illustrates the “Handshaking Co-Processes”. When interactions occur between the hardware and embedded firmware, this handshaking “co-process” occurs and relates to claim 2 and by extension, to claim 1 as well.

FIG. 7 : This figure illustrates a high level “Process Schematic Flow Overview.” This is a conceptual process diagram and relates to claim 8 and, by extension, claims

1 and 2 .

FIG. 8 : This figure illustrates the “Opportunistic Blockchain Ecosystem.” It illustrates that there are existing tokens, technologies, and other blockchain networks (both in existence and in a conceptual stage) that the healthcare blockchain cryptosystem interfaces with through unique oracle hardware and software bridges and is related to claim 8 .

FIG. 9 : This figure illustrates token classes and positions RHIOCOIN as well as summarizes the creation process of new and emergent tokens derivative to the native RHIOTOKEN. This figure relates to claims

4 and 5 .

FIG. 10 : This overall flowchart process presented as 3 sub-process flowcharts is named “Patient Flowcharts” and relates to claim 5 and by extension, to claim 6 . It presents an initial use case example of the invention related to payments via Claims Processing; Revenue; and Real-time Quality Score Updating on a Blockchain Ledger with details of the steps found in the following DETAILED DESCRIPTION OF THE DRAWINGS section.

FIG. 11 : This figure is a pictorial overview of the Healthcare Designated Record Set as proposed in draft discussion format by the Sequoia Project, October, 2022.

FIG. 12 : This figure is a representative example that illustrates text queries from me and responses from an AI program, ChatGBT. These were created following a request by me to provide required steps necessary to create schematics appropriate for submitting to a material or chip card engineer for development of our physical graphene based antenna. A second example query follows on taking that output and using it to build Solidity code in the blockchain.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 : This figure relates to claims 1 - 8 and lists in table format, the technology innovations created by and within the Healthcare Blockchain Cryptosystem. The apparatus and system is composed of hardware, software, and methods. Concurrent and newly evolved innovations, using coincident sample use cases that naturally potentiate additional innovations are further described in the detailed description under the enablement section of “How to Make and Use” the invention.

FIG. 2 : This figure relates to claims

5 and 8 . It is a pictorial representation of the Medical Hub Exchange described in the detailed description. It represents the following:

Payments and Revenue (POC/POS). This refers to the process of capturing visit charges and diagnostic codes. Real-Time Quality Reporting at “Point of Care” (POC) and “Point of Sale” (POS) where face-sheet data is immediately transmitted to a MIPS Registry and Quality Score is calculated “to date” and scoring is presented to provider. (This is described in detail in FIG. 10 Flowchart and is the last Figure for the Invention). Insurance Options/Payers (CAQH)—The ability to communicate to the patient and provider eligibility, optional plans, estimated price of services, etc. using X.12 Clearinghouse Standards. Business Continuity and Recovery—Options that allow provider, group, or hospital entity or network to recover from Ransom-ware attack, Power outage, or loss of internet by utilizing invention's hardware thumb drive and solar backup.

FIG. 3 : These lists describe various nomenclature that, at times, utilize various words or terms to refer to the same condition, symptom, disease cluster, code classification, electronic health record and Health Information Exchange common fields and many others.

FIGS. 4 - 7 : These Drawings are sufficiently described in the BRIEF DESCRIPTION OF DRAWINGS and no further detail is required.

FIG. 8 : Additional note, our architecture allows the creation of new smart contracts based on evolutionary parameters of natural selection via neuro programming.

FIG. 9 : These Drawings are sufficiently described in the BRIEF DESCRIPTION OF DRAWINGS and no further detail is required.

FIG. 10 : As stated in the BRIEF DESCRIPTION OF THE DRAWINGS section above, this flowchart drawing is broken into 3 sub processes each with their own flowchart: Flowchart “A” addresses Pre-process patient/provider activities; Flowchart “B” addresses Payment/quality measure updating; and Flowchart “C” addresses Post Process Activities using DEA (Data Envelopment Analysis) as a Quality Measure Roadmap with real time populating of provider contracts appending provider experience to their own performance Record keeping.

Processes

A) Pre-process patient/provider activities—FLOWCHART PROCESS “A” B) Payment/quality measure update process—FLOWCHART PROCESS B C) Post Process—DEA Measure Roadmap/contract experience populate—FLOWCHART PROCESS C

Flowchart A) Pre-Process Patient/Provider Activities STEPS as Matched to Drawings

Patient completes doctor or provider encounter (101, 102) Physician or provider that renders care and has a national provider identify number (NPI), reviews/updates/creates Face-sheet and superbill for patient to bring copy to front desk (or front desk receives these documents from a source other than the patient—electronic or medical office personnel) (103)

Contains:

Names of procedures done Requirement for other tests if needed Any referral information Should have diagnosis, procedure, and encounter codes if possible

Patient advances to payment window; starts Payment/metric update process (104-106)

Flowchart B) Payment/Quality Measure Update Process STEPS as Matched to Drawings

Patient presents payment to medical office check-out staff with required documents and antenna card or barcode from mobile device. (201)

Clerk performs data entry for bill settlement to cover payment and to update physician(s), other medical provider(s) (if any) for Face-sheet and super bill measure updates. (202)

Measures populate either directly from superbill and codes or is entered into local program for batch upload to update measures later. (203)

At this point, program processes: (204)

Health Savings Account (HSA) Processing Standard payment processing Discount(s) if any, due to quality measure target attainment or adherence System displays or prints measure dashboard showing progress and eligible patients for goal Shows eligible patients, measures, attribution information for episode Sends to appropriate cryptographic medium such as Blockchain via Oracle <li id

TECHNICAL FIELD

The invention is related to the technical field of Blockchain and Web 3 distributed databases. Blockchain is a distributed electronic ledger running across a world-wide system of internet nodes and functions similar to internet distributed name services.

BACKGROUND THE INVENTION

From a technical perspective, the field of this invention generally relates to blockchain ledger entries (or resources) supported and validated based on consensus protocols. It is focused on the health care technology ecosystem. Due to the generational variation in the use of technology in healthcare, there exist multiple instances of incompatible software systems and incompatible approaches to the format of a standard record designation for patients and entities. There is need for a normalization mechanism that can solve this issue while taking into account the nature of constant change in the industry.

Various web resources may already exists in the public domain, either in the form of publication or usage and act as sources of information or motivation to the inception of the invention. Approaches over time in Web 1 and Web 2, and even from classical programming, were established to address specific problems or within specific software products for unique customers. As healthcare has evolved the need for interoperability of these systems is critical from cost, utilization, and patient safety perspectives.

BRIEF SUMMARY OF THE INVENTION

This introduces concepts further described in the Detailed Description. It is not intended to limit the scope of the claims.

The Healthcare Blockchain Crypto system encompasses integrated mechanisms and bridges software applications. The purpose is to correct health data that is inconsistent, wrong, unsecured, and non-interoperable with multiple technologies.

One object of the invention is to normalize and improve software and hardware incompatibilities within a dynamically changing environment. Another object of the invention is to insure data validation is consensus driven and interoperable across all systems affected so as to solve existing problems. Another object of the invention is to tokenize revenue flow through healthcare software and allocate payments and rewards to patients, payers, providers, and pharmacies in a system where graphene based antenna SIM cards guarantee identity of the actors.

In some embodiments, the present invention comprises telephony s, in other embodiments the present invention hyperlinks to tokenized smart contracts.

BRIEF DESCRIPTION DRAWINGS

FIG. 1 : This figure relates to claims 1 - 8 and lists in table format, the technology innovations created by and within the Healthcare Blockchain Cryptosystem. The apparatus and system is composed of hardware, software, and methods.

FIG. 2 : This figure relates to claim 8 . It is a pictorial representation of the Medical Hub Exchange described in the detailed description.

FIG. 3 : Cross Walked Mapping Entity Systems (Five Lists Notated A-E). This figure relates to claim 7 and illustrates the abundance of key databases and lists in health care that must be treated as joined parameters by providers.

FIG. 4 : This figure relates to both claims

1 and 8 . It shows a high level interactions overview of bi-directional bridging between Physical and Cryptosystem like Metaverse (Mirror Database) and addresses spontaneous smart contract evolution based on natural selection and neuro network programming and networks.

FIG. 5 : This figure presents a pictorial overview of existing Iot (Internet of Things) technology. This figure relates to both claims

1 and 2 .

FIG. 6 : This figure illustrates the “Handshaking Co-Processes”. When interactions occur between the hardware and embedded firmware, this handshaking “co-process” occurs and relates to claim 2 and by extension, to claim 1 as well.

FIG. 7 : This figure illustrates a high level “Process Schematic Flow Overview.” This is a conceptual process diagram and relates to claim 8 and, by extension, claims

1 and 2 .

FIG. 8 : This figure illustrates the “Opportunistic Blockchain Ecosystem.” It illustrates that there are existing tokens, technologies, and other blockchain networks (both in existence and in a conceptual stage) that the healthcare blockchain cryptosystem interfaces with through unique oracle hardware and software bridges and is related to claim 8 .

FIG. 9 : This figure illustrates token classes and positions RHIOCOIN as well as summarizes the creation process of new and emergent tokens derivative to the native RHIOTOKEN. This figure relates to claims

4 and 5 .

FIG. 10 : This overall flowchart process presented as 3 sub-process flowcharts is named “Patient Flowcharts” and relates to claim 5 and by extension, to claim 6 . It presents an initial use case example of the invention related to payments via Claims Processing; Revenue; and Real-time Quality Score Updating on a Blockchain Ledger with details of the steps found in the following DETAILED DESCRIPTION OF THE DRAWINGS section.

FIG. 11 : This figure is a pictorial overview of the Healthcare Designated Record Set as proposed in draft discussion format by the Sequoia Project, October, 2022.

FIG. 12 : This figure is a representative example that illustrates text queries from me and responses from an AI program, ChatGBT. These were created following a request by me to provide required steps necessary to create schematics appropriate for submitting to a material or chip card engineer for development of our physical graphene based antenna. A second example query follows on taking that output and using it to build Solidity code in the blockchain.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 : This figure relates to claims 1 - 8 and lists in table format, the technology innovations created by and within the Healthcare Blockchain Cryptosystem. The apparatus and system is composed of hardware, software, and methods. Concurrent and newly evolved innovations, using coincident sample use cases that naturally potentiate additional innovations are further described in the detailed description under the enablement section of “How to Make and Use” the invention.

FIG. 2 : This figure relates to claims

5 and 8 . It is a pictorial representation of the Medical Hub Exchange described in the detailed description. It represents the following:

Payments and Revenue (POC/POS). This refers to the process of capturing visit charges and diagnostic codes. Real-Time Quality Reporting at “Point of Care” (POC) and “Point of Sale” (POS) where face-sheet data is immediately transmitted to a MIPS Registry and Quality Score is calculated “to date” and scoring is presented to provider. (This is described in detail in FIG. 10 Flowchart and is the last Figure for the Invention). Insurance Options/Payers (CAQH)—The ability to communicate to the patient and provider eligibility, optional plans, estimated price of services, etc. using X.12 Clearinghouse Standards. Business Continuity and Recovery—Options that allow provider, group, or hospital entity or network to recover from Ransom-ware attack, Power outage, or loss of internet by utilizing invention&#39;s hardware thumb drive and solar backup.

FIG. 3 : These lists describe various nomenclature that, at times, utilize various words or terms to refer to the same condition, symptom, disease cluster, code classification, electronic health record and Health Information Exchange common fields and many others.

FIGS. 4 - 7 : These Drawings are sufficiently described in the BRIEF DESCRIPTION OF DRAWINGS and no further detail is required.

FIG. 8 : Additional note, our architecture allows the creation of new smart contracts based on evolutionary parameters of natural selection via neuro programming.

FIG. 9 : These Drawings are sufficiently described in the BRIEF DESCRIPTION OF DRAWINGS and no further detail is required.

FIG. 10 : As stated in the BRIEF DESCRIPTION OF THE DRAWINGS section above, this flowchart drawing is broken into 3 sub processes each with their own flowchart: Flowchart “A” addresses Pre-process patient/provider activities; Flowchart “B” addresses Payment/quality measure updating; and Flowchart “C” addresses Post Process Activities using DEA (Data Envelopment Analysis) as a Quality Measure Roadmap with real time populating of provider contracts appending provider experience to their own performance Record keeping.

Processes

A) Pre-process patient/provider activities—FLOWCHART PROCESS “A” B) Payment/quality measure update process—FLOWCHART PROCESS B C) Post Process—DEA Measure Roadmap/contract experience populate—FLOWCHART PROCESS C

Flowchart A) Pre-Process Patient/Provider Activities STEPS as Matched to Drawings

Patient completes doctor or provider encounter (101, 102) Physician or provider that renders care and has a national provider identify number (NPI), reviews/updates/creates Face-sheet and superbill for patient to bring copy to front desk (or front desk receives these documents from a source other than the patient—electronic or medical office personnel) (103)

Contains:

Names of procedures done Requirement for other tests if needed Any referral information Should have diagnosis, procedure, and encounter codes if possible

Patient advances to payment window; starts Payment/metric update process (104-106)

Flowchart B) Payment/Quality Measure Update Process STEPS as Matched to Drawings

Patient presents payment to medical office check-out staff with required documents and antenna card or barcode from mobile device. (201)

Clerk performs data entry for bill settlement to cover payment and to update physician(s), other medical provider(s) (if any) for Face-sheet and super bill measure updates. (202)

Measures populate either directly from superbill and codes or is entered into local program for batch upload to update measures later. (203)

At this point, program processes: (204)

Health Savings Account (HSA) Processing Standard payment processing Discount(s) if any, due to quality measure target attainment or adherence System displays or prints measure dashboard showing progress and eligible patients for goal Shows eligible patients, measures, attribution information for episode Sends to appropriate cryptographic medium such as Blockchain via Oracle Patient has account reduced or pays standard rate as displayed by price list determined by combination of fee&#39;s required and offset by patient adherence and payer recommendations. Patient can see activity since last visit, increased healthy profile as determined by plan/doctor

Flowchart C) Post Process—DEA Measure Roadmap/Contract Population STEPS as Matched to Drawings

Parallel populate/Data Envelopment Analysis (DEA) driver with visual or chart output (302)

Parallel populate—Path A (303A) or Path B (303B)

Path A—Measure Roadmap—Mapping software version or charted—provider preference (304A)

Based on contract milestones illustrated as color-coded topography: (305A)

RED—Due GREEN—Attained YELLOW—Optional and potentially significant to clinical care; revenue optimization; contract term achievement; or any combination; can be dynamically set.

Path B—DEA Experience Database population for future contract formation or evidence (304B)

Accumulation of experience (305B) Determine ongoing and new best practices (305B) Assign to Tax Id that bills (TIN) in combination with NPI&#39;s that are rendering or by Group. Lists terms Creates Report Cards Display varying scenarios and goals with patient attribution classification; account for variations if patient changes demographics during reporting period Bundled episode rates Can be local or virtual

Bi-Directional External Samples:

Quality Measure Data Bank—fed by National Quality Forum (NQF) Rural Healthnet Consortia—vendor neutral archive Payer Agreement Contractual Database QPP, PARS, eCQM and AHRQ government databases NCQA, HEDIS IQR and OQR QECP Data QCDR shared measures API Library 837 files and claims Virtual Group entities to account for LCD and RCD—CAQH CORE JCAHO, Leapfrog, Other

Endpoint Processing Output for Flowchart Process “C”—Forwards to the Suncoast RHIO consortium based repository. This repository contains tools for standardization of key patient data needed for quality measurement and assists in fostering ongoing standardization of data for measures. It has other development tools such as libraries of data elements that allow new electronic measures to be captured, calculated, and reported for use by clinicians and consumers.

This supports alignment of measures across 3 rd parties for access and reporting needs using API libraries (Application Programming Interfaces)—code that allows unlike computer software to communicate and pass parameters to each other and do not lose meaning in transition; provides for aggregating and linking “Value Based Data” for payments and care, data transparency, data consolidation, and alignment across payers.

FIG. 11 : Pictorial representation representing the Healthcare Designated Record Set. This figure relates to claim 9 and illustrates fields that would be weighted in the blockchain ledger file based standard designated record set. Similar to FIG. 3 , this standardized weighted file incorporates lists that describe various nomenclature that, utilize various words or terms to refer to the same condition, symptom, disease cluster, code classification, electronic health record and Health Information Exchange common fields, the patient record, and many others.

FIG. 12 : These Drawings are sufficiently described in the BRIEF DESCRIPTION OF DRAWINGS and no further detail is required.

BEST MODE FOR CARRYING OUT THE INVENTION

This topic is fully covered in the Detailed Description. In short, in some embodiments, the apparatus of the present Healthcare Cryptosystem invention comprises linked and encoded SIM and eSIM cards in 5G mobile phones, in other embodiments the apparatus of the present invention comprises web based portal logins with hyperlinks, and in further embodiments, the apparatus of the present invention comprises linked and encoded SIM and eSIM cards in non 5G mobile cell phones which are also linked to hardware antennae radio devices.

DETAILED DESCRIPTION OF THE INVENTION

Introduction to Detailed Description: The Blockchain Healthcare Cryptosystem invention is an apparatus working within an apparatus based system. The Britannica Dictionary entry of “Apparatus” begins with two definitions: 1) a tool or piece of equipment used for specific activities; 2) the organization or system used for doing or operating something. Deeper dives into the word from other reference sources mention the words “machine”, “means”, and sometimes “software.”

I present the invention as an apparatus because the make-up fits this description. The invention has at its core a graphene carbon allotrope material based chip encoded with the capability to absorb standard integrated Fourier Transform integrated biofeedback signals from skin temperature, circulatory/muscular rhythm, and unique person “positive ID” capable EEG brain waves. The material approach can work with other carbon allotropes or in combination with others. (Examples of carbon allotropes are graphite, carbon nanotubes, and diamonds.) It is also capable of transmitting signals. As such, it performs as an antenna. It is capable of being encoded on a debit or credit card, a SIM, or other physical media. With the evolution of SIM into eSIM, my coding works on a virtualized card as well. The invention also has firmware and software encoding processes that sync from the graphene material to my blockchain and reverse and allows the hardware to be integrated as a portal into it. I call the blockchain the healthcare cryptosystem network and the material acts as a blockchain oracle within the concepts of IoT or the “Internet of Things.” It pairs by bridging between physical antennae on the material and syncing with coded antennae pairs within the software architecture and distributed network nodes.

Viewing this apparatus as the keystone unit which is replicated across a distributed network in a mechanical, machine-like approach, the cryptosystem is thereby created. I consider both the individual keystone components and the system they exist on as one. As in a stem cell of a living organism, the cell alone has no context without duplication, multi-cell self-generating emergent properties, and differentiation in the organism based on locality and need. These concepts are built into the cryptosystem.

I combine together hardware, software, and blockchain code and processes specific to the Healthcare technology sector. I optimize the distributed server network by defining a multi-level ledger known in the industry as a distributed “Designated Record Set” that incorporates UMLS (Unified Medical Language System) Metathesaurus reconciliations, HL7 (Health Level 7) standards including FHIR and CCDA, X.12 EDI, and USCDI (United States Core Data for Interoperability) data elements within a blockchain consensus validation protocol which I call PoP or “Proof of Patient.”

This combination of standard based entities working with the new processes invented herein is the core unit of the Blockchain Healthcare Cryptosystem. As mentioned, I call these units the “keystone” components and they are duplicated across the system. However, even as this unit is complete in and of itself, it allows for API or other portal-like standards based peripheral connectors of hardware or software for ancillary add on functional entities or programs. These can be produced by third parties using readily available components or with the assistance of Artificial ChapGBT-like Intelligence applied to my “How to Build” approach. In fact, a significant portion of “Component Summary Description Topic 2 on Blockchains” in this detailed description is written describing third party blockchains and how they help formulate and interact with the healthcare cryptosystem blockchain.

In figures accompanying this invention, I use AI generated responses to define the steps necessary to create schematics that are usable by the average CHIP designer and producer to create components. It is my view that ChatGBT-like statements of design can be viewed by many as only regurgitated processes based on already existing known approaches from human records and therefore may not meet the unique and innovative patentability requirements of a new invention. However, it is the bridge between the components and the overall organization of them that only a human can create as I have done and present. There has been progress towards the use of AI in chip design. Researchers at DeepMind are utilizing generative AI neural networking with reinforced learning in AI chip design. It streamlines the human process and reduces the time investment but does not eliminate the human element.

The success of my healthcare focused system is not defined by the efficiency of the intersystem processes but rather by the emergent capabilities triggered by events performed by doctors as the components of the design, and acknowledgement of the ever-changing touch of humanity.

I use the same approach in presenting to the reader of “How to Build” in the creation of an Etherium ERC20 Token. In my provisional application which is referenced in the Application Data Sheet, I had originally included a step by step program code file to create a token for a “GO” compiler. It became quite clear to me that this token creation process is not unique and anyone can find the steps to build one. I therefore suggest that a program such as ChatGBT be utilized to find common ways to create the token and I have removed that figure from this non-provisional patent application but have retained the steps involved in this detailed description.

As an analogy to a “Swiss Army Knife” or a “Black Box” tool kit for adding peripheral components, at the core, I view this working apparatus as the designated holder of the representation of a healthcare patient designated record set. It is an inventory of everything discrete in healthcare built into a ledger (open or closed) that doubles as an actionable tool and updates all related ledgers in real time upon any transaction (Read, Update, Add, Delete) done upon any part of it. Once built and populated, it always exists. In one embodiment, it fits onto existing computer networked servers in the IPFS distributed server environment as well as proprietary networks with the proper API&#39;s. There is no need for further discrete collection processes; it builds upon itself. I expand upon embodiment below.

The reader will find throughout these writings that I interchangeably use the pronouns “I” and “we” in my descriptions. The invention and concept is submitted and owned by me as an individual and not a group or company. This is referenced in the Application Data Sheet. However, I also hold the title of president of a company known as Suncoast RHIO in Florida and in the preferred embodiment and proof of concept, as with other embodiments described, Suncoast RHIO will be the organization that will be used to demonstrate the first working use-case.

This description will lay out the details of the Blockchain Healthcare Cryptosystem invention with its emergent-capable software, servers, and methods with example through preferred embodiment of a common “use case”. Healthcare is a complex environment addressed by the invention. Healthcare and the technology that supports it as well as the functionality of this invention are meant to work by drawing from the seamless utilization of interacting components. The description begins with an introductory approach that includes a best mode embodiment. This embodiment is at first presented in summary form and briefly mentions other embodiments that can be used. It is later expanded upon in the Detailed Description in step by step format.

After the summary of the preferred embodiment, this Detailed Description of the Invention is then broken down into two Division Segments with the first (Division Segment 1) being the invention itself and a healthcare industries&#39; historical “Deep Dive” that led to the software architecture. This is complete with its own Table of contents and is then followed Division Segment 2, which is the step by step detail oriented segment of the best mode embodiment mentioned and addresses how to make and use the embodiment as well as other component technologies that would support other embodiments.

This is a technical invention which aligns to new and unique apparatus tools and business systems and methods for healthcare operations. The physical innovations are explained in detail. The invention also leverages human organizational components that work together to form an improved Health Care System segmented by demographics and local or regionalized social determinants of health.

The issues that the invention addresses surround the difficulty in dealing with existing multiple incompatible software systems, inaccurate patient identification, ransomware, and incompatible approaches. These issues are due to a lack of a format for a standard record designation for patients and entities which we address and normalize via the Web3 Blockchain approach. This apparatus along with systems and methods works as a cohesive mechanism and solves these issues while at the same time taking into account the nature of constant change in the industry. The best mode embodiment is therefore applied to an example of a high priority use case and it can be utilized by researchers or government entities and consumers in transactions with their providers. Other embodiments are applicable to expanded patient use and to providers and payers.

The technological components of the invention that are useful, novel, and non-obvious, are made up from A) Our “Internet of Things” or “IoT” antenna&#39;s and chips created and coupled with paired software on the blockchain and B) new and integrated software built into our emergent blockchain tokens, API&#39;s, and smart contracts (which can simultaneously exist as firmware based “Smart Contracts” for the pairing). Together, these technological components complete the apparatus’.

In some embodiments, the apparatus of the present Healthcare Cryptosystem invention comprises linked and encoded SIM cards in 5G mobile phones, in other embodiments the apparatus of the present invention comprises web based portal logins with hyperlinks, and in further embodiments, the apparatus of the present invention comprises linked and encoded SIM and eSIM cards in non 5G mobile cell phones which are also linked to hardware antennae radio devices, and in further embodiments, the apparatus of the present invention comprises blockchain tokens generated by the present invention&#39;s smart contracts which are encoded on graphene chip cards and synced to Web3 based distributed networks and file systems using healthcare HL7 standards, and in further embodiments, the apparatus is comprised of hardware, systems, and methods which in part, can be applicable to the finance industry (Reference to claim 7 ).

Preferred Mode Embodiment Summary (Detail Steps are found in Division Segment 2).

The use case focuses on healthcare payments with real time provider quality scoring.

1) Build a standard ERC20 Ethernet Token. 2) Build and incorporate Web3 network file on IPFS with blockchain domain name. 3) Program Smart Contract coding on both virtual metaverse-like web and encoded physical antennae chip. 4) Use API bridges between environments in the form of SIM Oracle on 5G mobile. 5) Collect patient consent and upload health record to doctor and hospital cohort. 6) Complete provider encounter and payment with SIM phone with face-sheet data. 7) Provider billing utilizes this blockchain via FHIR through HIE. 8) Tokenized data performs through Suncoast RHIO oversight, pharmacies, payers and in Metaverse mirror database element for consensus. 9) Tokens use smart contract to interface with CMS and Suncoast RHIO Qualified CMS MIPS Registry for quality score results. 10) Validation of data with our new and unique PoP protocol (patient, provider, pharmacy, payer) after traditional PoS is performed. 11) Reward of network tokens backed by commodities or Fedcoin. (FedNow) 12) Patient balance reduced and provider balance increased in distributed ledger. 13) Provider contracts with payers and others updated on this blockchain. 14) All participating providers can now view up-to-date elements of every patient regardless of location.

As mentioned above, a quick summary of alternate embodiments of this use case includes A) Suncoast RHIO portal login with direct SSO bridge connection via hyperlinks to IPFS through distributed Metamask Wallet; B) Direct graphene antenna card without SIM on non 5G mobile with HoneyBadger BFT radio device; C) use of Emergent Seed (ours) smart contract token and Generica Tokens with optimizing Opportunistic Blockchain to RHIOTOKEN (ours) and creating new and adaptive RHIOCOIN upon validation.

As summary reference of USPTO classes and keywords, the following is provided with fields gleaned from USPTO classes that are related the application but not in total: Cryptography (Class 713); Virtual Machine Control (Class 718); Multicomputer Data Transfer (Class 709); Database Management (Class 706); and Operator Interface as related to Smart Contracts and Tokens, and Crypto Coins (related to automatically generation of column and field layouts in electronic documents for external (human) and internal (API and Oracle) operators (Class 715). Keywords within the patent application such as Health Care Management (USPTO Class/subclass 705/002); Insurance (USPTO Class/subclass 705/004); Discounts and Incentives for use in creation of personal concierge plans (USPTO Class/subclass 705/014); and Electronic Shopping so as to match systems and methods to consumers and for network emergent token creation and processing by smart contract (USPTO Class/subclass 705/026).

Divisions and Segments

This next section is an expanded overall invention description covering history, current need, and technical architecture and is made up of Division Segments. 1) The overall description is presented in High Level and Moderate Level; 2) Detailed technological step by step embodiment description mentioned earlier and deep dive description of other components of the invention illustrates use in other embodiments.

Overall Document Layout:

Division Segment 1=Detailed Description Overview;

Division Segment 2=Step-by-Step detail of best mode and other embodiments;

Division Segment are presented in:

Section A=High Level Section B=Moderate Level with 4 Parts within these Sections

Note, only Division Segment 1 contains a Table of Contents

Division Segment 1

Table of Contents

Detailed Description Overview; Section “A”— High Level, Parts 1 through 4:

Part 1—Preamble to the Main Section, What is the Invention?

Part 2—Component Discussion

Part 3—The Road Before, Leading to the Current “As Is” State

Part 4—Moving Towards Solutions Description; Section “B”—Moderate Level, Parts 1 through 4:

Part 1—The Architectural Perspective

Part 2−Conceptual Architecture

Part 3—Patentability Proposal Overview

Part 4—Innovation and Government/Payer Readiness

End of Table of Contents

Part 1—Preamble to the Main Section, What is the Invention?—High Level

Jim Cramer of Wall Street and media fame once responded to an AARP interview question on financial matters. He was asked to address what else, beyond sound investing was an important message that Jim wanted to convey to readers. His answer was, “I got hurt this year. I hurt my back. I wasn&#39;t able to walk for four days. I had thought I was indestructible, and I didn&#39;t have a plan for not being indestructible. I did have health insurance, but I think that people have to be mindful that nothing works unless they are in good health. So, sacrifice everything first to be in good health, everything. That should be your number one priority, because money you can make or lose, and hopefully make. But if you do not take care of your health, then it&#39;s all over. I can&#39;t help you”. (AARP Bulletin, December 2021, page 14)

This invention lays out a solution that addresses the problematic U.S. healthcare domain of technology related systems of computers and software that are incompatible, dysfunctional, inaccurate, and unreliable. It addresses the need for people, companies, government, medical providers, and others to pay for healthcare, track it, keep it protected and secure, and optimize it as one unified system replacing disparate islands of contradicting information. The major issues requiring attention are information overload; disparity in data approach across care settings; inconsistent processes; and lack of secure and reliable record keeping.

Too much accessible yet globally incompatible information, replete with non-conforming access mechanisms, is demanding people&#39;s attention today. Taken as a whole, interactions over so many “un-synchronized” computers, telephones, smart phones, and other units, involve using unnatural interfaces and they produce over-stimulation and wrong results. This is often followed by anxiety, especially when one&#39;s health or the health of loved ones being cared for, hangs in the balance of performing technical steps as system interactions in the correct way. We all live within our own current understanding of the larger pie that overlaps across many more systems that were once barely manageable. Now, with constant change, the normal activities of living that are dependent on these systems of care have become unmanageable; especially when the delivery of care expands beyond the locality of the patient and involve social and demographic aspects and technology adeptness.

At a high level, this invention can be reduced, summarized, and described as a combination of two interacting categories: 1) a Technical Invention−new software and new IoT firmware embedded devices, and 2) a Process and business method to integrate and manage them. From an introductory perspective, we combine new Blockchain and Metaverse related software to match to real world existing healthcare systems and applications already in use. We do this with new and unique Internet of Things (lot) Antenna technology working in concert with mapping software. The antennae exist as both physical antennas on credit or debit cards for example and have programmed paired antennae and synced counterparts in a virtual and mixed reality programmed into a mirrored networked Web3 database arrangement. The Metaverse referred to is also called a mirror database as described below but at a conceptual level, Metaverse in the context of the invention, is the collection of one focused electronic atmosphere around the physical world. So, it may include social media, Blockchain Web3 networks, gaming systems, and electronic news and groups. To see how items that are represented in digital form in this electronic atmosphere around us, we can see how both negative and positive reactions in the physical world of social media are born in this atmosphere, or are inherited from the physical into the electronic human centered atmosphere, manipulated or normalized there, and then sent back to physical life where they have real physical effects for example. (Pokemon-Go, Jetpack, Digital Clothes)

Our mapping approach utilizes both “list based” conjunctive database processing as well as traditional electronic virtual “GPS like” mapping software. Just as our IoT antennae exist in pairs with one in physical existence and the other in 3D print code that is executed into our “Metaverse like” electronic world copy, we integrate our physical and virtual antenna pairs the same. We utilize the built in semi-conductor processing capability and also integrate that code as a part of the smart contracts. This brings the contract software to an object inheritance state with this advanced antenna embedded code. It allows the smart contracts and the antennae and all electronic connections to the antennae, to be located and matched. In the physical world, GPS radio locates and confirms antenna location, frequency, and attributes with our antenna graphene spliced material tagging resources and matching to their virtual world counter parts. Internally, the GPS process is simply replaced by coded programs acting as GPS cloned processors similar to orbiting satellites but now in our electronic atmosphere. Because we use blockchain, we apply the same type of validation in segment blocks on a ledger where instead of validating financial transactions as is done in a Bitcoin or similar currency reconciliation, we are validating the proper contracts and that their tags are correct and we do not perform the commit portion of the match until validation of the matched antennae by our own PoP (Proof of Patient) protocol. Tags are key to our process and the antenna material is the actual portal key to our Metaverse like Mirror-verse-More on this later.

The inventory of parts are: IoT devices and IOMT (Internet of Medical Things) used as Blockchain Oracles with entry trigger points; “ Web 3” influenced programs and software in the form of Blockchain smart contracts and “wallets”; Health Level 7 assigned Object Identifiers (HL7 OID&#39;s); emergent and unique “seed” blockchain tokens and; the human element of localized organizations.

We introduce our own unique “Blockchain Tokens” that interface independently and execute computer programs. This also means, our primary token when launched, creates other “template driven” and pre-defined tokens as well as new emergent tokens when conditions warrant. The generation of these “new” tokens and contracts is triggered by the events surrounding token transportation through ever changing cells of locality as opposed to “set in stone” expectations of functionality. This is similar to the natural and unique formation of snow crystals (snowflakes), where no two are alike through the dynamic climate of a storm. In our case, new tokens do evolve similar to natural processes. Some may ask, “Why have smart contracts always being newly created in an ongoing emergent process?” The answer lies in the inherent evolutionary mutation rules of nature. Rather than create contracts to attempt covering every unanticipated arrival of a new use case, our approach creates random contracts that sit in wait for appropriate use cases to process; if none arrive, it deletes the obsolete ones with time and use parameter settings. More detail on this process follows in the “Moderate Level Listing of Major Components” Section “B” and in the “ Division Segment 2, Building the Best Use Preferred Embodiment.” A summary listing of innovations of the invention can be found in FIG. 1 , and relates inclusively to claims 1 through 9 .

Inclusive with “Smart Contracts” and “Oracle” technology is software and firmware that uploads health data from traditional systems. Programs perform normalization calculations in a database mirrored in a Web 3 superstructure and download the normalized data back to target systems and on people&#39;s devices. The primary Blockchain token is designated the “RHIOCOIN” and it triggers the referenced emergent coins later detailed. RHIOCOIN represents more than a single program. (Note, this proposal is not a proposal for a cryptographic currency such as Bitcoin, even though it can act as a medium of exchange; instead the system augments medical providers’, their facilities’, and patient records and payments using many forms of tokens and currency and other “trade-based-mediums-of-exchange” including up and coming CBDC&#39;s (Central Bank Digital Currencies).

Our integrated system represents the genesis of an interdependent blockchain working within the standardized platforms of Ethereum, Cardano, Polkadot, Secret (formerly known as Enigma and aimed at bringing privacy to Smart Contract platforms), Bitcoin, and others. The result is a Healthcare Cryptosystem that in itself acts as the architecture exhibiting various degrees of plasticity. This plasticity is derived from the RHIOCOIN token through repeatable processes over time. It is therefore a dynamically perpetuating process with coins—or Tokens, and contracts re-emerging constantly anew through natural and mechanical change that is represented from the “parent” data. Along with all of the components, the RHIOCOIN represents an integral entity that forms the keystone of our blockchain based healthcare cryptosystem. RHIOCOIN is the “seed” token that results in the formation and the content needed for all of the secondary tokens databases formed in our self-configuring system.

RHIOCOIN is derived from the term RHIO which is an acronym for a “Regional Health Information Organization.” In our context, a RHIO acts as a human support entity organization as well as a blockchain with a dual job to monitor though governance and to perform actions to insure mining and minting occur through automated and human coupled processes. The RHIOCOIN domain is www.RHIOCOIN.Crypto. The website for this domain is under construction on the “IPFS” distributed file system using the “MetaMask” secure distributed wallet though many of the most common wallets are supported. The building of the RHIOCOIN; it&#39;s secondary layer of support tokens (Generica; HealtheHub; EmergentSeed.crypto; StemToken.crypto; and RHIOToken); other 3 rd party tokens; Non-Fungible Tokens (NFT&#39;s and nested NFT&#39;s); RHIO&#39;s own “Smart Contracts”; the HL7 FHIR and OID (Object Identifiers) with X.12 mappings; the trigger points; the built-in medical quality measure comparative analytics tool; the firmware and hardware entities based on IoT mappings (the “Internet of Things”); the software and hardware Oracles; and more, are all defined in the detail of the embodiment section (Division Segment 2).

CLAIMS

Claims ( 9 )

What is claimed is:

1 . A healthcare blockchain network apparatus comprising firmware, software, and hardware and characterized by easy-to-use by public consumer held distributed IoT (Internet of Things) SIM, eSIM, and/or credit/debit card based antennae graphene DNA and EEG FFT encoded chip cards, potentially in organization with other carbon allotrope materials, and acting within and as mobile cell phone based blockchain oracles of said apparatus; and with synced paired metaverse-like modeled Mirror-Base Web3 environment platform of parallel coded antennae; a distributed network; smart blockchain contracts; and unique PoP consensus protocol, so as to immutably record, track, sync, correct, secure, and reconcile disparate computer based health record physical components using VM, VT, Virtual Floating Desktops to health payment systems, and transactions of payments in a new and unique way insuring accurate patient identify and payment, patient safety, optimal health component(s) utilization, and usefulness.

2 . An apparatus according to claim 1 , in which said graphene chip cards encoded with said DNA and EEG potentiate signal capture and synchronization through physical proximity to a human brain via ear when using said SIM phone card method whereas electrical skin impedance as sensed by said FFT antenna bridges FFT Transform to blockchain meta-layer via RHIOTOKEN and derivative precious metal and diamond commodity backed RHIOCOINS over air gaps whereas said antennae captures impedance levels through heat and blood flow.

3 . An apparatus according to claim 1 , in which natural selection based emergent smart contracts comprised of neural network inspired software and said oracle hardware antennae evolve in real time within said web3 healthcare blockchain Mirror-Base utilizing new and novel healthcare cryptosystem blockchain through unique “API&#39;s” programming and oracles of said non-obvious emergent smart contracts as bridges to old, existing, and future—yet to be invented, blockchain projects.

4 . An apparatus oracle according to claim 2 , in which a PoP consensus protocol of said blockchain acts to validate records though proof of patient; proof of provider; and proof of pharmacy after proof of stake is performed using cryptocurrency rewards for participants of said commodity backed coins, or Central Bank Digital Currency backed, or Fiat backed in RHIOCOIN (RHC) of said blockchain.

5 . An apparatus and system according to claim 4 in which real time payments and receipts in said multiple currencies and wallets for healthcare services are made to healthcare providers and linked to real time quality scoring matched to medical procedures, utilization, and results derived from statistical Data Envelopment Analysis with Best Case analytics based on mapping to desired subjective outcome parameters via the said healthcare cryptosystem native derived RHIOTOKEN and derivatives as acting units of Tokenization on the said blockchain smart contracts and deriving said RHIOCOINs as liquid representations of value representing provider fees, prices, claims, and insurer benefits that can be traded, gifted, received for said validation rewards, and purchased at any time for said payment to providers for services and other uses.

6 . A distributed apparatus with systems and methods where according to claim 5 the said resultant token based smart contract coin of value backed by said physical commodities and said government backed cryptocurrency and physical fiat is secondarily limited against inflation by binding issuance and contract rules of promissory estoppel pegged to and consistent with the purchasing power of said units of currency at time of issuance and such that especially when used in said meta-verse-like healthcare cryptocurrency electronic layer where correcting of bad data is performed, and where said cryptocurrency tokens and coins remain liquid and where asset devaluation is averted avoiding currency pitfalls found in physical financial fiat systems without said promissory estoppel constraints that avoid systematic financial risk.

7 . An apparatus according to claim 6 whereas linkage of said encoded smart contract graphene based oracle antenna chip and paired Web3 software coded Oracle antenna token act as one for synchronization and whereas bridge approach between said Web1 and Web2 applications to Web3 environments matches said bridge approach to and from physical to virtual assets and where said approach is transportable to additional industries beyond healthcare such as banking.

8 . An apparatus according to claim 4 comprised of all US national and global international identifiable healthcare entity matching in HL7 protocol to FHIR protocol and USCDI found in certified EHR and/or open source electronic health products in the corresponding said blockchain medium additionally allowing patient access to every encounter in the longitudinal record in real time.

9 . A dynamically generated standardized blockchain ledger formatted file according to claim 8 and representing a “Standard Designated Record Set” of a patient health record standard derived from an algorithm weighing HL7, US ONC Standards, FHIR, UM LS, EDI X.12, and USCDI.

US18/452,594

2022-08-22

2023-08-21

Healthcare Blockchain Cryptosystem

Abandoned

US20240070627A1

( en )

Priority Applications (1)

Application Number

Priority Date

Filing Date

Title

US18/452,594

US20240070627A1

( en )

2022-08-22

2023-08-21

Healthcare Blockchain Cryptosystem

Applications Claiming Priority (2)

Application Number

Priority Date

Filing Date

Title

US202263373099P

2022-08-22

2022-08-22

US18/452,594

US20240070627A1

( en )

2022-08-22

2023-08-21

Healthcare Blockchain Cryptosystem

Publications (1)

Publication Number

Publication Date

US20240070627A1

true

US20240070627A1 ( en )

2024-02-29

Family

ID=90001365

Family Applications (1)

Application Number

Title

Priority Date

Filing Date

US18/452,594

Abandoned

US20240070627A1

( en )

2022-08-22

2023-08-21

Healthcare Blockchain Cryptosystem

Country Status (1)

Country

Link

US

( 1 )

US20240070627A1

( en )

Cited By (18)

* Cited by examiner, † Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20230319144A1

( en )

*

2022-02-28

2023-10-05

CEO Vision, Inc (dba Croquet Studios)

Systems and methods for providing secure portals between virtual worlds

US20240029034A1

( en )

*

2022-07-20

2024-01-25

Bank Of America Corporation

Generating Smart Contracts for Electronic Notarization Using Synthetically Generated Invisible Fingerprint Metadata

US20240095730A1

( en )

*

2022-09-20

2024-03-21

Veiovia Limited

Externally validated proof of work for appending a block record to a blockchain with a data broker server

US20240154808A1

( en )

*

2022-11-03

2024-05-09

Change Healthcare Holdings, Llc

Systems and methods of trace id validation and trust

US20240413999A1

( en )

*

2023-01-04

2024-12-12

Fortior Solutions, Llc

Technologies for creating non-fungible tokens for electronic health records

US20250022293A1

( en )

*

2021-11-09

2025-01-16

Industry-Academic Cooperation Foundation, Yonsei University

Management system for generating and distributing cell image-based nft

US12235984B1

( en )

*

2023-05-30

2025-02-25

MediMint, LLC

Patient-empowered data management: a secure blockchain architecture with decentralized ownership

CN119599168A

( en )

*

2024-11-05

2025-03-11

杭州医数链科技有限公司

Batch intelligent management method and device for digital supply chain of medical instruments

US20250103696A1

( en )

*

2023-09-25

2025-03-27

Asahi Kasei Microdevices Corporation

Certification system, certification method, and computer readable recording medium

US20250139125A1

( en )

*

2023-03-24

2025-05-01

TRETE Inc.

Dual ledger syncing

CN120632949A

( en )

*

2025-06-05

2025-09-12

北京碳珣科技有限公司

Natural carbon asset full life cycle monitoring method and system based on blockchain technology

WO2025188698A1

( en )

*

2024-03-07

2025-09-12

Shelterzoom Corp.

Web-based electronic medical record database backup, business continuity &amp; cyber resilience during emr downtime

US20250292295A1

( en )

*

2024-03-15

2025-09-18

Lifeguard Health Networks, Inc.

System and method for therapeutic event management and value attribution (proof of value) in decentralized health information network

CN120893968A

( en )

*

2025-07-09

2025-11-04

北京恒源新能科技有限公司

A digital management platform system for multi-party collaboration in new energy projects

CN121567478A

( en )

*

2026-01-22

2026-02-24

昆明理工大学

Extra-high voltage equipment full-chain data trusted sharing system based on block chain

WO2026085013A1

( en )

*

2024-10-14

2026-04-23

Etfinanical, Llc

Systems and methods for a lifetime exchange traded fund

US20260120890A1

( en )

*

2024-10-25

2026-04-30

Oracle International Corporation

Efficient querying with diversely encoded clinical data

US20260212413A1

( en )

*

2023-03-24

2026-07-23

TRETE Inc.

Transaction flow with master account ledger and escrow ledger interaction

Citations (2)

* Cited by examiner, † Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20180279884A1

( en )

*

2017-03-29

2018-10-04

Texas Instruments Incorporated

Multi-person vital signs monitoring using millimeter wave (mm-wave) signals

US11443838B1

( en )

*

2022-02-23

2022-09-13

Carlsmed, Inc.

Non-fungible token systems and methods for storing and accessing healthcare data

2023

2023-08-21

US

US18/452,594

patent/US20240070627A1/en

not_active

Abandoned

Patent Citations (2)

* Cited by examiner, † Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20180279884A1

( en )

*

2017-03-29

2018-10-04

Texas Instruments Incorporated

Multi-person vital signs monitoring using millimeter wave (mm-wave) signals

US11443838B1

( en )

*

2022-02-23

2022-09-13

Carlsmed, Inc.

Non-fungible token systems and methods for storing and accessing healthcare data

Cited By (23)

* Cited by examiner, † Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20250022293A1

( en )

*

2021-11-09

2025-01-16

Industry-Academic Cooperation Foundation, Yonsei University

Management system for generating and distributing cell image-based nft

US20230319144A1

( en )

*

2022-02-28

2023-10-05

CEO Vision, Inc (dba Croquet Studios)

Systems and methods for providing secure portals between virtual worlds

US12609990B2

( en )

*

2022-02-28

2026-04-21

CEO Vision, Inc

Systems and methods for providing secure portals between virtual worlds

US20240029034A1

( en )

*

2022-07-20

2024-01-25

Bank Of America Corporation

Generating Smart Contracts for Electronic Notarization Using Synthetically Generated Invisible Fingerprint Metadata

US20240095730A1

( en )

*

2022-09-20

2024-03-21

Veiovia Limited

Externally validated proof of work for appending a block record to a blockchain with a data broker server

US12211039B2

( en )

*

2022-09-20

2025-01-28

Veiovia Limited

Externally validated proof of work for appending a block record to a blockchain with a data broker server

US20240154808A1

( en )

*

2022-11-03

2024-05-09

Change Healthcare Holdings, Llc

Systems and methods of trace id validation and trust

US20240413999A1

( en )

*

2023-01-04

2024-12-12

Fortior Solutions, Llc

Technologies for creating non-fungible tokens for electronic health records

US20250139125A1

( en )

*

2023-03-24

2025-05-01

TRETE Inc.

Dual ledger syncing

US20260212413A1

( en )

*

2023-03-24

2026-07-23

TRETE Inc.

Transaction flow with master account ledger and escrow ledger interaction

US12682398B2

( en )

*

2023-03-24

2026-07-14

TRETE Inc.

Dual ledger syncing

US20250265365A1

( en )

*

2023-05-30

2025-08-21

MediMint, LLC

Patient-empowered data management having a secure blockchain architecture with decentralized ownership

US12235984B1

( en )

*

2023-05-30

2025-02-25

MediMint, LLC

Patient-empowered data management: a secure blockchain architecture with decentralized ownership

US20250103696A1

( en )

*

2023-09-25

2025-03-27

Asahi Kasei Microdevices Corporation

Certification system, certification method, and computer readable recording medium

US12423193B1

( en )

2024-03-07

2025-09-23

Shelterzoom Corp.

Web-based electronic medical record database backup, business continuity and cyber resilience during EMR downtime

WO2025188698A1

( en )

*

2024-03-07

2025-09-12

Shelterzoom Corp.

Web-based electronic medical record database backup, business continuity &amp; cyber resilience during emr downtime

US20250292295A1

( en )

*

2024-03-15

2025-09-18

Lifeguard Health Networks, Inc.

System and method for therapeutic event management and value attribution (proof of value) in decentralized health information network

WO2026085013A1

( en )

*

2024-10-14

2026-04-23

Etfinanical, Llc

Systems and methods for a lifetime exchange traded fund

US20260120890A1

( en )

*

2024-10-25

2026-04-30

Oracle International Corporation

Efficient querying with diversely encoded clinical data

CN119599168A

( en )

*

2024-11-05

2025-03-11

杭州医数链科技有限公司

Batch intelligent management method and device for digital supply chain of medical instruments

CN120632949A

( en )

*

2025-06-05

2025-09-12

北京碳珣科技有限公司

Natural carbon asset full life cycle monitoring method and system based on blockchain technology

CN120893968A

( en )

*

2025-07-09

2025-11-04

北京恒源新能科技有限公司

A digital management platform system for multi-party collaboration in new energy projects

CN121567478A

( en )

*

2026-01-22

2026-02-24

昆明理工大学

Extra-high voltage equipment full-chain data trusted sharing system based on block chain

Similar Documents

Publication

Publication Date

Title

US11628351B2

( en )

2023-04-18

Blockchain

US20250094496A1

( en )

2025-03-20

Blockchain System

US12020178B2

( en )

2024-06-25

Method and apparatus for information representation, exchange, validation, and utilization through digital consolidation

Amir Latif et al.

2022

RETRACTED ARTICLE: A remix IDE: smart contract-based framework for the healthcare sector by using Blockchain technology

Leeming et al.

2019

A ledger of me: personalizing healthcare using blockchain technology

Al-Quayed et al.

2023

Towards a secure technology-driven architecture for smart health insurance systems: An empirical study

US12517919B2

( en )

2026-01-06

Contextual Orchestration and Scoped Memory Protocol with Decentralized Memory Wallet for adaptive artificial intelligence systems

Fang

2021

Commercially successful blockchain healthcare projects: a scoping review

Esmaeilzadeh

2023

Evolution of health information sharing between health care organizations: potential of nonfungible tokens

Urkude et al.

2021

Anatomy of blockchain implementation in healthcare

Sharma et al.

2021

Applicability of blockchain technology in healthcare industry: applications, challenges, and solutions

Shruthi et al.

2023

Medical data asset management and an approach for disease prediction using blockchain and machine learning

AU2020101898A4

( en )

2020-09-24

MHOC- Blockchain Technology: Medicine and Healthcare Observation Care using Blockchain Technology

Gomase et al.

2025

Effective integration of artificial intelligence and blockchain technologies for empowerment of drug discovery and development

US20240086790A1

( en )

2024-03-14

Data gyro bulb for illuminating and analyzing differences between metrics and targets over sequences to assess, alert, and achieve and maintain targeted states

Das et al.

2023

Unleashing the Potentials of Blockchain Technology for Healthcare Industries

Mubaslat

2018

Demonstrating the Functionality and Efficacy of Blockchain-based System in Healthcare Using Simulation Tools

Goli et al.

2024

The Problem of Payments in E-Health and E-Prescriptions Systems

CA3208087A1

( en )

2022-07-21

Systems and methods for healthcare interoperability

Langley et al.

2018

Blockchains, property rights and health technology assessment in the pharmaceutical and device (s) industries

Southey et al.

2023

Why healthcare needs blockchain

Raad et al.

2024

Fraud detection in supplementary health insurance based on smart contract in blockchain‎ network

Choudhury et al.

2023

Blockchain Applications in Healthcare: Innovations and Practices

Teles

2018

Data protection with Ethereum blockchain

Borse et al.

2022

Application of Blockchain Technology to Make Smart Cities Smarter

Legal Events

Date

Code

Title

Description

2023-12-04

STPP

Information on status: patent application and granting procedure in general

Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION

2025-05-30

STPP

Information on status: patent application and granting procedure in general

Free format text : NON FINAL ACTION MAILED

2025-12-12

STCB

Information on status: application discontinuation

Free format text : ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

2025-12-16

STCB

Information on status: application discontinuation

Free format text : ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

Related documents

• A Review of Blockchain Applications and Healthcare Informatics#679192
• Blockchain Technology In Healthcare: Potential Benefits And Barriers In Health Informatics#1237094
• Security and Privacy of Technologies in Health Information Systems: A Systematic Literature Review#964725
• Blockchain Applications in Core Healthcare Services: Patient Data, Research, and Institutional Processes.#1148
• Scalability Challenges in Healthcare Blockchain System—A Systematic Review#340970