|
Comment |
Description: Deduplicated request to notify a caregiver, separate from delivery. Usage: This transactional and auditable record is used in the 08 Notifications and Operations subject area as the authoritative representation of notification intent data. It owns or classifies Notification Intent has Deliveries; is referenced through User has Notification Intents, Child has Notification Intents, Recommendation creates Notification Intents, Collection Task creates Notification Intents. |
|
Name |
Comment |
|
Notification Intent ID |
Description: Stable system identifier for a Notification Intent record. Usage: Used as the conceptual primary identifier and as the stable reference from relationships to Notification Intent. Required for every record. |
|
Notification Type2 |
Description: Controlled classification value for notification type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Source Type |
Description: Discriminator identifying the business object that caused the record to be created. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Source Reference6 |
Description: Traceable reference used to locate, correlate, or audit the source reference. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Optional and recorded only when known or applicable. |
|
Priority10 |
Description: Ordering value used to sort or prioritize Notification Intent 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. |
|
Earliest Send At |
Description: Timestamp recording when the earliest send event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Optional and recorded only when known or applicable. |
|
Expires At2 |
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. |
|
Deduplication Key2 |
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 Notification Intent records. Optional and recorded only when known or applicable. |
|
Status19 |
Description: Lifecycle or workflow status of the Notification Intent record. Usage: Used to gate workflow transitions, exclude inactive or incomplete records, support operations dashboards, and preserve processing history. Required for every record. |
|
Payload JSON |
Description: Flexible structured payload used by workers or delivery channels without changing the core schema. Usage: Used for extensible PoC data and asynchronous processing while stable, frequently queried concepts remain modeled as first-class attributes and relationships. Optional and recorded only when known or applicable. |
|
|
|