1897   Data-change and data-update inclusion bitstring bits set in a report

Created: 28 Nov 2023

Status: Drafting Implementation

Part: Part 7-2 (2020; Edition 2.1)

Links:

Page: 53

Clause: 6.3.3.3

Paragraph: Reason for inclusion in reports (ReasonForInclusio

Issue

It is stated in the standard that ‘data-change’ and ‘data-update’ are mutually exclusive of each other.

It is also mentioned in 17.2.3.2.3.2 that it is preferable to send only a single report when changes meet more than one TrgOps criteria.

However, both data-change and data-update can happen within same scan cycle and will generate a report with both inclusion bits set. e.g. BCR common data class.

Proposal

Allow data-change and data-update ReasonForInclusion bits to be set within a same report for same data object when client has enabled both trigger options.

Discussion Created Status
append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"

with
"for each particular data attribute as specified in Table 5."
13 Feb 24 Drafting Implementation
Accepted.
What is meant is:
'data-change' and 'data-update' are mutually exclusive of each other for each particular data attribute as specified in Table 5.
Proposed change : append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"

with
"for each particular data attribute as specified in Table 5."
19 Dec 23 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1