| 1 Definition | 2 Functional Requirements | 3 Syntax | 4 Semantics | 5 Conformance Testing | 6 Performance Assessment |
1 Definition
ECG Object is a Data Type combining ECG Data and the ECG Qualifier specified by MPAI-TFA V1.5, which provides additional information on the ECG Data for potential use by a machine.
2 Functional Requirements
ECG Object includes:
- ECG Data, conveyed inline, by URI with its length, or by identifier.
- ECG Qualifier.
3 Syntax
https://schemas.mpai.community/AIH1/V1.1/data/ECGObject.json
4 Semantics
| Label | Description |
| Header | ECG Object Header, Standard “AIH-ECO-Vx.y” |
| ECGObjectID | Identifier of ECG Object. |
| MInstanceID | Identifier of M-Instance. |
| UEnvironment | Identifier of U-Environment. |
| EndUserID | Identifier of End User. |
| EndDeviceID | Identifier of End Device. |
| ECGObjectTime | Time of ECG Object. |
| ECGData | ECG Data. |
| – DataLength | Length of Data in bytes. |
| – DataURI | URI of Data. |
| – Data | Data. |
| – DataID | Identifier of Data. |
| ECGDataQualifier | See ECGQualifier. |
| DataXMData | Data Exchange Metadata. |
| DescrMetadata | Descriptive Metadata. |
5 Conformance Testing
A Data instance Conforms with ECG Object (AIH-ECO) if:
- Its JSON Object validates against its JSON Schema.
- Any included JSON Object validates against its JSON Schema.
- All Data in the JSON Object:
- Have the specified Data Types.
- Conform with the Qualifiers signaled in their JSON Schemas.