Entity [Collection Task]

Entity [Collection Task]

Comment

Description: Child-specific due item generated from a schedule, event, or follow-up rule. Usage: This transactional and auditable record is used in the 05 Collection and Evidence subject area as the authoritative representation of collection task data. It owns or classifies Collection Task has Questionnaire Sessions, Collection Task creates Notification Intents; is referenced through Collection Definition has Tasks, Child has Collection Tasks.


Name

Comment

Collection Task ID

Description: Stable system identifier for a Collection Task record. Usage: Used as the conceptual primary identifier and as the stable reference from relationships to Collection Task. Required for every record.

Due At

Description: Business value storing due at for the Collection Task record. Usage: Used by services, rules, search, reporting, or audit processing that operates on Collection Task records. Optional and recorded only when known or applicable.

Expires At

Description: Timestamp recording when the expires event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Optional and recorded only when known or applicable.

Priority8

Description: Ordering value used to sort or prioritize Collection Task records. Usage: Used by evaluation, ranking, threshold, explanation, and quality-control logic; it must not be presented as clinical certainty unless explicitly validated. Optional and recorded only when known or applicable.

Status13

Description: Lifecycle or workflow status of the Collection Task record. Usage: Used to gate workflow transitions, exclude inactive or incomplete records, support operations dashboards, and preserve processing history. Required for every record.

Deduplication Key

Description: Stable key used to prevent creation or delivery of logically duplicate work. Usage: Used by services, rules, search, reporting, or audit processing that operates on Collection Task records. Optional and recorded only when known or applicable.

Created At4

Description: Timestamp recording when the created event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Required for every record.

Completed At3

Description: Timestamp recording when the completed event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Optional and recorded only when known or applicable.