Go To AIH-HSP Data Types

1 Definition 2 Functional Requirements 3 Syntax 4 Semantics 5    Conformance Testing 6     Performance Assessment

1 Definition

The Request to the Auditing AIM to Audit the Processing of AIH Data or the Response from the Auditing AIM.

2 Functional Requirements

Audit Request includes:

  1. User ID
  2. Time
  3. Processing Types for which infringement is sought.

Audit Response includes a list of

  1. AIH Data ID
  2. Date
  3. Infringing Processing Type

3 Syntax

https://schemas.mpai.community/AIH1/V1.0/data/Audit.json

4 Semantics

Label Description
Header Audit Header – Standard “AIH-ADT-Vx.y”
MInstanceID Identifier of M-Instance.
AuditID Identifier of Audit Request.
AuditTime Time of Audit Request.
Audit Data in Audit
– Request If Request
  – UserID ID of User for which Audit is requested.
  – AuditPeriod Period of time for which Audit is requested.
  – Processing Types For which infringement is sought.
– Response If response
  – AIHData[] Data of the set of Affected AIH Data IDs
    – ProcessingTypes[] Set of Processing performed
      – ProcessingType Type of infringing  Processing Types
      – ProcessTime Date of infringing Processing.
      – AIHDataID AIH Data affected by infringing Processing.
DataXMData Information about this AIH Data Instance.
DescrMetadata Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with Audit (AIH-ADT) if:

  1.  Its JSON Object validates against its JSON Schema.
  2. Any included  JSON Object validates against its JSON Schema.
  3. All Data in the JSON Object:
    1. Have the specified Data Types.
    2. Conform with the Qualifiers signaled in their JSON Schemas.

6     Performance Assessment

Go To AIH-HSP Data Types