1. Functions 2. Reference Model 3. Input/Output Data
4. Functions of AI Modules 5. Input/output Data of AI Modules 6. AIW, AIMs, and JSON Metadata

1. Functions

  1. The End User
    1. Registers with the Health Back End.
    2. Uses Health Devices to collect various types of Health Data.
    3. Provides a Model Licence to each Health Data collected.
    4. Requests the Health Front End to Process AIH Data.
    5. Sends AIH Data to the Health Back End.
    6. Requests The Back End to Process AIH Data.
  2. The Health Front End
    1. Stores AIH Data as combination of Model Licence and Health Data.
    2. Processes AIH Data.
    3. Adds Anomaly and Risk Alerting (ARA) Data, if present, to each AIH Data.
    4. Receives requests for trained NN Models from Health Back End.
    5. Sends its trained NN Models to the Health Back End for Federated Learning.

The End User owning the Front End is not bound by the Model Licence.

2. Reference Model

Figure 1 depicts the Reference Architecture of the Health Front End (AIH-HFE).

Figure 1 – Reference Model of the Health Front End (AIH-HFE) AIW

The HFE workflow develops as follows

  1. End User registers with HFE and HBE.
  2. End User acquire Health Data with a Health Device.
  3. End User attaches Model Licence to Health Data.
  4. Model Licencing stores AIH Data (including Health Data and Model Licence).
  5. End User process AIH Data locally.
  6. End User stores AIH Data to HFE.
  7. End User process AIH Data remotely.
  8. HFE receives Federated Learn request.
  9. HFE sends NN Model to HBE.

3. Input/Output Data

Table 2 specifies the Input and Output Data.

Table 1 – I/O Data of Health Front End

Input Description
Register Request Data to request to Register.
Register Response Data in response to a request to Register.
Federated Learn Request Request to provide an NN Model.
AIH Data Process Request End User’s Request to process specific AIH Data
AIH Data Process Response End User’s Request to process specific AIH Data
Health Data Data from End User’s health device.
Model Licence Data Describing End User’s Licensing Terms and Conditions.
AIH Data AIH Data to be stored.
Output Description
Register Request Data to request to Register.
AIH Data Process Request End User’s Request to process specific AIH Data.
AIH Data Process Response Response to End User’s Request to process specific AIH Data.
Federated Learn Response Response to the request to provide an NN Model.
AIH Data AIH Data retrieved.

4. Functions of AI Modules

Table 2 specifies the Function of the AI Modules.

Table 2 – Functions of Health Front End AI Modules

AI Module Description
Model Licensing AIM adding Model Licence to Health Data.
AIH Data Processing Processes AIH Data.
Anomaly and Risk Alerting Discovers Anomalies and signals Risks in AIH Data.
Storage Stores and retrieves AIH Data.

5. Input/output Data of AI Modules

Table 2 specifies the Function of the AI Modules.

Table 3 – Functions of Health Front End AI Modules

Acronym AI Module Receives Produces
AIH-MDL Model Licensing Health Data AIH Data
Model Licence
AIH-HDP AIH Data Processing Federated Learn Request Federated Learn Response
AIH Data Process Request AIH Data Process Response
AIH Data Process Response AIH Data Process Request
Health Data
Model Licence
AIH-ARA Anomaly and Risk Alerting AIH Data ARA Data
Register Request
Register Response
AIH-STR Storage AIH Data Process Request AIH Data Process Response
AIH Data AIH Data

6. AIW, AIMs, and JSON Metadata

Table 4 provides the links to the AIW and AIM specifications and to the JSON syntaxes. AIMs/1 indicates that the column contains Composite AIMs and AIMs indicates that the column contains their Basic AIMs.

Table 4 – AIW, AIMs, and JSON Metadata

AIW AIMs Name JSON
AIH-HFE Health Front End X
AIH-MDL Model Licensing X
AIH-HFP AIH Data Processing X
AIH-ARA Anomaly and Risk Alerting X
AIH-STR Storage X