(Informative)

1     Introduction 2     Actors 3     Services

1        Introduction

The Health Secure Platform specifies the architecture of a platform offering health-related services enabling the following functionalities:

  1. End Users use AIH-HSP Apps running on their Health Front Ends to acquire and uniquely identify Health Data.
  2. Health Data, combined with an associated Model Licence, is uniquely identified and called AIH Data.
  3. AIH Data is processed by the Front End in an instance of the MPAI-specified AI Framework (MPAI-AIF).
  4. The Health Front End processes AIH Data using AI Modules (AIM) downloaded from the MPAI Store.
  5. Neural Networks in AIMs continually learn while making inferences on AIH Data.
  6. Un-processed and Processed AIH Data may be uploaded to the Health Back End.
  7. The Health Back End stores the Model Licence as a Smart Contract on a Blockchain associated with the Health Back End.
  8. The ID of the Smart Contract ID is added to the AIH Data.
  9. The Smart Contract governs the use of the AIH Data stored on the Health Back End.
  10. Depending on the relevant Smart Contract, an instance of AIH Data stored on the Health Back End may be processed by the Health Back End itself and Third-Party Users.
  11. The Health Back End may process End Users’ AIH Data in its local instance of the AI Framework.
  12. A rich AIH Taxonomy is used to identify:
    1. AIH Data Classes (currently: ECG, EEG, Genomics, and Medical Images).
    2. AIH Data Users (currently: End User, Non-Profit Entity, Profit Entity, Clinical Entity, Authorised Entity, Caregiver)
    3. AIH Data Statuses (currently, Anonymised, Pseudonymised, Identified)
    4. AIH Data Usages (currently, Unrestricted, Pseudonymised, Anonymised, Research, Patient use, Health care)
    5. AIH Data Processing Types (currently: ECG, EEG, Genomics, and Medical Images).
    6. Anonymisation/De-Identification Algorithms
    7. Anomaly Types.

Figure 1 graphically depicts the elements of the AI for Health – Secure Platform.

Figure 1 – General Model of AIH-SHP V1.0

Operation of an implementation of an AIF instance is required to be Zero Trust. Technical Specification: AI Framework (MPAI-AIF) V3.0 provides a set of requirements that aa Zero Trust implementation of an AIF instance is expected to be satisfied..

2        Actors and Data

The Health Secure Platform identifies and recognises the following types of User and Data:

  1. Users
    1. End User: a User that
      1. Acquires Health Data with their Health Front End
      2. Produces uniquely identified AIH Data composed of uniquely identified Health Data and uniquely identified Model Licence..
      3. Processes AIH Data their with their Health Front Ends.
      4. Sends AIH Data to a Health Back End.
      5. Controls and audits the access and processing of their AIH Data by any Third-Party User based on the terms of the said Smart Contract.
    2. Health Back End: a User that
      1. Receives AIH Data from Health Front Ends.
      2. Converts the Model Licence of received AIF Data to a Smart Contract on a Blockchain.
      3. Adds the Smart Contract ID to a new version of the AIH Data.
      4. Stores and processes AIH Data based on the Smart Contract  licence.
    3. Third-Party User, a User that represents a qualified third-party entity identified by the MPAI AIH Taxonomy (e.g., hospitals, research centres, caretakers) that accesses and processes AIH Data on the Health Back End based on the sub-licensing clauses of the Smart Contract between the End User and the Back End. Licensing terms appear on  approved templates verified for consistency, legal compliance, and technical security before release.
  2. Data
    1. Health Data: collected by the End User with Health Devices.
    2. AIH Data: locally processed, and uploaded  by End Users to the Back End, and stored, processed, and sublicensed  by the the Back End to Third-Party-Users based on the Terms specified by the relevant Smart Contract licence.

3        Services

The Health Secure Platform is composed of a set of distributed components and services:

  1. The Front End, the End User’s personal gateway to their external biometric sensors and any AIH Data that:
    1. Captures End User’s Health Data, e.g., from Google Fit and Apple Health, and external biometric sensors that capture Health Data.
    2. Locally stores AIH Data in a “Secure Data Vault” controlled by the End User.
    3. AI processes AIH Data using standard AIMs and AIWs downloaded from the MPAI-Store performing the computational operations on the End User’s AIH Data, including transformations, training, and inferences.
    4. Alerts the End-User about any deviation of the value of the AIH Data that may be caused, e.g., by disease, injury, or chronic conditions.
    5. Uploads the processed AIH Data to the Back End.
  2. The AIH Back End, composed of a set of tools that implement the necessary services
    1. Securely stores, de-identifies and anonymises AIH Data, controls entity authentication and access to data, and licenses and audits the access to Back End AIH Data.
    2. Gathers anonymised data from End Users and acts as a broker gateway between Third-Part Entities requesting access to AIH Data and its providers.
    3. Grants access rights without referring to the identity of the End Users providing the data. The Back End may only grant the Third-Party User the rights to process AIH Data that the Back End has been specifically granted by the relevant End User.
  3. Blockchain enables the system’s transparency and auditability. Each provision of and access to AIH Data requires the emission of a license in the form of a Smart Contract that is stored on the Blockchain. The Smart Contract contains information about:
    1. The parties, e.g., the End User sending AIH Data and the Back End, and any future Third-Party User requesting access to and processing of AIH Data.
    2. The Type of Third-Party User (per the MPAI-AIH Taxonomy).
    3. The AIH Data and AIH Models to be used.
    4. The Rights granted to use the AIH Data:
      1. Type of use of the AIH Data (per the MPAI-AIH Taxonomy).
      2.  Type of use of the processed AIH Data (per the MPAI-AIH Taxonomy).
    5. The duration of the Licence.
  4. The AI Services offered by the Back End can be used directly to process the AIH Data on the Front End and extract the specific knowledge sought by the End User or Third-Party Users based on the Licence. These services are selected from those available from the MPAI Store and may be orchestrated to produce specific analyses for the Third-Party Users that request access to AIH Data. By means of data processing, AI services enable specific and customised training of Machine Learning Models to identify and assist in the identification of medical diagnosis and prognosis.
  5. The AI Federated Learning System (FLS) orchestrates the learning of a central model for medical diagnosis and prognosis, namely by working as a medical anomaly detection tool, receiving Neural Network Model weights data from the Front End and using it under the terms of the Smart Contract that was established between the End User and the Back End. When an improved model is obtained by the FLS, this is uploaded to the MPAI-Store.