<-Scope       Go to ToC       References ->

Capitalised Terms used in this Technical Specification have the meaning defined in Table 1. Lower-case Terms have the meaning commonly defined for the context in which they are used. For instance, Table 1 defines Licence but does not define licence.

A dash “-” preceding a Term in Table 1 indicates the following readings according to the font:

  1. Normal font: the Term in the table without a dash and preceding the one with a dash should be read before that Term. For example, “AIH Model” and “- Instance” will yield “AIH Model Instance”.
  2. Italic font: the Term in the table without a dash and preceding the one with a dash should be read after that Term. For example, “AI Health (AIH) Data” and “- Processed” will yield “Processed AI Health (AIH) Data”.

Other Capitalised terms have been defined by other MPAI Technical Specifications. All MPAI-defined Terms are accessible online.

Table 1 – General MPAI-AIF terms

Term Definition
Access The process of a User or a Service to perform a data operation or function on the Health Secure Platform.
AI Framework (AIF) The environment where AIWs are executed.
AI Health (AIH) Data Health-related data entering the Health Secure Platform.
– Anonymisation A mechanism that protects private or sensitive data by erasing or encrypting identifiers that connect an individual to stored data.
– De-identification A mechanism that breaks the link between data and the individual with whom the data is initially associated. It is a type of data anonymization.
– Processed AIH Data that have undergone processing by an AIH Data Processing AIM designed to perform transformative procedures such as extract features, assess disease evolution, etc.
AI Module (AIM) A processing element receiving AIM-specific Inputs and producing AIM-specific Outputs according to according to its Function. An AIM may be an aggregation of AIMs.
AIH Model An AIM trained model for processing AIH Data.
–  Instance A local End User instance of the AIH model.
AI Workflow (AIW) A structured aggregation of AIMs implementing a Use Case receiving AIW-specific inputs and producing AIW-specific inputs according to its Function.
Health Secure Platform The ICT platform offering AIH services.
–  Back End The part of the Health Secure Platform collecting, storing, and processing health data, and carrying out Federated Learning functions on the AI Models from the Front-end.
–  Front-End The end-user devices collecting and processing personal health data and updating the AI Models received from the Health Secure Platform Back End.
AIH Processing Taxonomy The recognised set of processing that the Health Secure Platform Back End can execute.
Anonymisation The process of removing or transforming personally identifiable information (PII) from data to make it impossible to identify an individual, even with additional information.
Audit Process that determines if the services are safeguarding licencing and maintaining data integrity and privacy.
Authentication Process of verifying and attesting the identification of a User or a Service.
Blockchain A shared immutable ledger stored on a peer-to-peer network of computers.
External Communication Set of services to communicate to a platform other than the Health Secure Platform.
External Source A platform other than the Health Secure Platform from which the Health Secure Platform Back End may collect subsidiary data for the integration of relevant information for health-related predictions.
Federated Learning System (FLS) The AIW system aggregating the data describing each of the Health Secure Model Instances for the update of a global Model for AIH system-wide distribution.
Licence Document that creates a bond between a User, their AIH Data, the Health Secure Platform Back Ends, and any Third-Party User expressed by the conditions that regulate the access to that data.
Personally Identifiable Information (PII) Any data that can be used to distinguish or trace an individual’s identity, either alone or when combined with other information.
Provenance A record trail that accounts for the origin of a piece of data (in a database, document, or repository) together with an explanation of how and why it got to the present place
Pseudonymisation The processing of personal data in such a way that the data can no longer be attributed to a specific individual without the use of additional information, provided that this additional information is kept separately and is subject to technical and organisational measures to ensure non-attribution.
Secure Data Vault A repository that holds several types of data in an encrypted format. Access to the data is controlled by the user through the presentation of appropriate credentials.
Service Software functionality, or a set of software functionalities, such as the retrieval of specified information or the execution of a set of operations.
Smart Contract A Program stored on a Blockchain that runs when activated by an external entity, e.g., a User or another Smart Contract.
Time series Data A collection of data points collected over time (e.g., heartbeats /minute, brain electrical activity, electrocardiogram, etc.).
Token A Data Type, e.g., name, password, biometrics, etc.
User Any entity involved in or accessing the Health Secure Platform.
– End  The holder of an Health Secure Platform Front-End instance.
– Third-Party An Entity – excluding the AIH System and the End User – accessing the Health Secure Platform Back End to process some stored AIH data.

<-Scope       Go to ToC       References ->