Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance
1 Functions
The AIH Data Processing (AIH‑HDP) AIM performs one or more processing functions on AIH Data:
| Receives | Licence Confirm Response | Response to request to confirm Licence ID. |
| Blockchain Licence Response | Response to Blockchain Licence Request. | |
| Federated Learn Response | Response to Federated Learn Request. | |
| AIH Data Process Response | Health Back End’s response to request to Process AIH Data. | |
| AIH Data | AIH Data. | |
| AIH Data Process Request | Request to Health Back End to Process AIH Data. | |
| Register Request | Request to register with the Health Secure Platform. | |
| Register Response | Health Back End’s response to Register Request. This data is received only by an AIH Data Processing Instance of the Health Front End. | |
| ARA Data | Anomaly and Risk Alert Data. | |
| Produces | Licence Confirm Request | Request to Blockchain to confirm Licence ID. |
| Blockchain Licence Request | Request to Blockchain to create Smart Contract. | |
| Federated Learn Request | Request to provide trained NN Model. | |
| AIH Data Store Request | Request to store AIH Data. | |
| AIH Data Process Response | Response to AIH Data Process Request. | |
| AIH Data | Processed AIH Data. | |
| Register Request | Request to Health Back End to register. This data is provided only by an AIH Data Processing Instance of the Health Front End. | |
| Register Response | Response to Register Request. This data is provided only by an AIH Data Processing Instance of the Health Back End. |
2 Reference Model
Figure 1 depicts the Reference Model of the AIH Data Processing (AIH‑HDP) AIM.
Figure 1 – AIH Data Processing (AIH‑HDP) AIM Reference Model
3 I/O Data
Table 1 specifies the Input and Output Data of the AIH Data Processing (AIH‑HDP) AIM. An Input marked Optional need not be supplied for the AIM to run: the AIH Data Processing AIM of the Health Front End and that of the Health Back End do not receive the same Inputs.
| Input | Description |
|---|---|
| Licence Confirm Response | Response to request to confirm Licence ID. Optional. |
| Blockchain Licence Response | Response to Blockchain Licence Request. Optional. |
| Federated Learn Response | Response to Federated Learn Request. This data is provided only by an AIH Data Processing Instance of the Health Back End. Optional. |
| AIH Data Process Response | Health Back End’s response to request to Process AIH Data. Optional. |
| AIH Data | AIH Data. |
| AIH Data Process Request | Request to Health Back End to Process AIH Data. |
| Register Request | Request to register with the Health Secure Platform. |
| Register Response | Health Back End’s response to Register Request. This data is received only by an AIH Data Processing Instance of the Health Front End. Optional. |
| ARA Data | Anomaly and Risk Alert Data. |
| Output | Description |
| Licence Confirm Request | Request to Blockchain to confirm Licence ID. |
| Blockchain Licence Request | Request to Blockchain to create Smart Contract. |
| Federated Learn Request | Request to provide trained NN Model. This data is provided only by an AIH Data Processing Instance of the Health Back End. |
| AIH Data Store Request | Request to store AIH Data. |
| AIH Data Process Response | Response to AIH Data Process Request. |
| AIH Data | Processed AIH Data. |
| Register Request | Request to Health Back End to register. This data is provided only by an AIH Data Processing Instance of the Health Front End. |
| Register Response | Response to Register Request. This data is provided only by an AIH Data Processing Instance of the Health Back End. |
4 SubAIMs
No SubAIMs.
5 JSON Metadata
https://schemas.mpai.community/AIH1/V1.1/AIMs/AIHDataProcessing.json
6 Profiles
No Profiles.
7 Reference Software
Under development.
8 Conformance Testing
Table 2 provides the Conformance Testing Method for the AIH Data Processing (AIH‑HDP) AIM.
If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema, if present, and conform with the Qualifier, if present.
| Receives | Licence Confirm Response | Shall validate against Licence Confirm schema. |
| Blockchain Licence Response | Shall validate against Blockchain Licence schema. | |
| Federated Learn Response | Shall validate against Federated Learn schema. | |
| AIH Data Process Response | Shall validate against AIH Data Process schema. | |
| AIH Data | Shall validate against AIH Data schema. | |
| AIH Data Process Request | Shall validate against AIH Data Process schema. | |
| Register Request | Shall validate against Register schema. | |
| Register Response | Shall validate against Register schema. | |
| ARA Data | Shall validate against ARA Data schema. | |
| Produces | Licence Confirm Request | Shall validate against Licence Confirm schema. |
| Blockchain Licence Request | Shall validate against Blockchain Licence schema. | |
| Federated Learn Request | Shall validate against Federated Learn schema. | |
| AIH Data Store Request | Shall validate against AIH Data Store schema. | |
| AIH Data Process Response | Shall validate against AIH Data Process schema. | |
| AIH Data | Shall validate against AIH Data schema. | |
| Register Request | Shall validate against Register schema. | |
| Register Response | Shall validate against Register schema. |
9 Performance Assessment
Not part of this specification.
