| 1 Function | 2 Reference Model | 3 Input/Output Data |
| 4 SubAIMs | 5 JSON Metadata | 6 Profiles |
| 7 Reference Software | 8 Conformance Texting | 9 Performance Assessment |
1 Functions
The HBE Data Processing (AIH-BDP) AIM:
| Receives | AIH Data | From internal Secure Storage. |
| Processing Request | From processes inside the HBE or Third-Party Users. | |
| Confirmation Response | Response to confirmation request. | |
| ARA Data | Anomaly and Risk Alerting Data. | |
| Licence ID | ID of Licence provided by Blockchain. | |
| Produces | AIH Data | To internal Secure Storage or requesting Third-Party Users. |
| Confirmation Request | Request for Confirmation. | |
| Licence Request | Request for Licence related to newly processed AIH Data . |
2 Reference Model
The HBE Data Processing (AIH-BDP) AIM Reference Model is depicted in Figure 1.
Figure 1 – The HBE Data Processing (AIH-BDP) AIM Reference Model
3 Input/Output Data
Table 1 specifies the Input and Output Data of the HBE Data Processing (AIH-BDP) AIM. Links are to the Data Type specifications.
Table 1 – I/O Data of the HBE Data Processing (AIH-BDP) AIM
| Input | Description |
| AIH Data | From internal Secure Storage. |
| Processing Request | From processes inside the HBE or Third-Party Users. |
| Confirmation Response | Blockchain’s response that AIH Data may/may not be used. |
| ARA Data | Anomaly and Risk Alerting Data |
| Licence ID | ID of Licence for newly processed AIH Data. |
| Output | Description |
| AIH Data | To internal Secure Storage or requesting Third-Party Users. |
| Confirmation Request | Request to Blockchain to use AIH Data. |
| Licence Request | Request for Licence related to newly processed AIH Data . |
4 SubAIMs
No SubAIMs
5 JSON Metadata
https://schemas.mpai.community/AIH1/V1.0/AIMs/HBEDataProcessing.json
6 Profiles
No Profiles
7 Reference Software
Under development.
8 Conformance Testing
Table 2 provides the Conformance Testing Method for the HBE Data Processing (AIH-BDP) 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.
Table 2 – Conformance Testing Method for HBE Data Processing (AIH-BDP) AIM
| Receives | AIH Data | Shall validate against AIH Data schema |
| Processing Request | Shall validate against Processing Request schema | |
| Confirmation Response | Shall validate against Confirmation Response schema | |
| ARA Data | Shall validate against ARA Data schema | |
| Licence ID | Shall be a string | |
| Produces | AIH Data | Shall validate against AIH Data schema |
| Confirmation Request | Shall be a string | |
| Licence Request | Shall validate against Licence Request Schema. |
