Atomic items
Section 20 objects, attributes or methods at this source reference.
CHTS requirement clause
2 technical records havebeen identified at this reference: 2 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
CHTS4.6.3.15 · item HistoricDeviceLog(CHF).methodOutput: devices[0..16].device.securityDetails
The hash of the security credentials for each of the Devices in the CHF Historic Device Log. Where a TC Link Key between the CH and the Device with this Device ID had been established previously, this field shall contain a Hash of that TC Link Key. Otherwise this field shall contain an empty string.
HistoricDeviceLog(CHF)methodOutput: devices[0..16].device.securityDetailsDocumented touchpoints
0x00FECHFSRV 8.9CHTS4.6.3.15 · item HistoricDeviceLog(CHF).methodOutput: devices[0..16].device.deviceIdentifier
The device identifiers for each of the Devices in the CHF Historic Device Log.
HistoricDeviceLog(CHF)methodOutput: devices[0..16].device.deviceIdentifierDocumented touchpoints
0x00FECHFSRV 8.9How to read this page
A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.