1232   EntryID needs clarification

Created: 28 Mar 2014

Status: In Force (green)

Part: Part 7-2 (2010; Edition 2)



Clause: 17


Category: Issue may impact interoperability of implementations of Edition 2


7-2 is not clear on the definition of Entry or EntryID.

In particular, Table 38 confuses Report and Segment.


Add text in

Entry - a set of values added to an event buffer in response to one event notification (including GI or integrity report).

EntryID - a unique identifier for each entry.

Reports with the same sequence number but different subsequence numbers shall use the same EntryID

EntryData[1..n] should be something like EntryData[m..n] to indicate that the entry data is split across segments and the first data unit will not be present in each segment.


17.1 should reflect the definitions above as they apply to log also.

Table 38 describes a transmission unit (segment), not a report. EntryData[1..n] should be EntryData[m..n]. It may be necessary to create a second table showing the format of a segment separately from a complete report.

Discussion Created Status
08 Dec 14 In Force (green)
Proposal accepted as written. 08 Oct 14 Ballot Period
Accepted - the table 38 shall better display that A Report, and an additional table shall better display the segment belonging to A Report.

Reports with the same sequence number but different subsequence numbers (i.e. each segment of A report) shall :
- use the same timeOfEntry (
- use the same EntryID
- use EntryData[k..m]

With EntryData[1..n] containing the data reference DataRef, Value, and ReasonCode of each member of the data-set to be nicluded in the report.
14 Apr 14 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.