| 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 Authentication and Access Control (AIH-AAC) AIM:
| Receives | AAC Parameters | Parameter set containing Authentication and Access Control data. |
| Produces | AAC Token | Token enabling an End-User and Third Party User to access the HBE. |
2 Reference Model
The Authentication and Access Control (AIH-AAC) AIM Reference Model is depicted in Figure 1.
Figure 1 – The Authentication and Access Control (AIH-AAC) AIM Reference Model
3 Input/Output Data
Table 1 specifies the Input and Output Data of the Authentication and Access Control (AIH-AAC) AIM. Links are to the Data Type specifications.
Table 1 – I/O Data of the Authentication and Access Control (AIH-AAC) AIM
| Input | Description |
| AAC Parameters | Parameter set containing Authentication and Access Control data, that depends on the Access Control types used by the HBE. |
| Output | Description |
| AAC Token | Token representing an authorisation level enabling an End-User and Third Party User to access the HBE. |
4 SubAIMs
No SubAIMs
5 JSON Metadata
https://schemas.mpai.community/AIH1/V1.0/AIMs/AuthenticationAndAccessControl.json
6 Profiles
No Profiles
7 Reference Software
Under development.
8 Conformance Testing
Table 2 provides the Conformance Testing Method for the Authentication and Access Control (AIH-AAC) 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 AIH-AAC AIM
| Receives | AAC Parameters | Shall validate against the AAC Parameters schema |
| Produces | AAC Token | Shall validate against the AAC Token schema |
