Table Description
Condition Set : Allows for conditions to be grouped together.

Conditional logic can be used to filter data such that it does not appear to a user, for example, recommended activities displayed in an outcome plan can be filtered such that only particular recommendations are displayed if configured conditions are met. A condition can be based on gender, age, a rule set, a factor score or a factor classification. Conditions can be grouped together into sets, for example, a condition set can contain a condition for gender and a condition for age. This entity stores conditions which have been grouped together.

Example

An outcome plan is created for James Smith, Linda Smith and their child Robert to identify and address their issues. James Smith is classified as having a Need in Substance Abuse. Adolescent Substance Abuse Treatment and Adult Inpatient Substance Abuse Treatment has been configured as recommendations for clients classified as having a Need in Substance Abuse. A condition has been associated with Adolescent Substance Abuse Treatment such that it is only recommended if the client is between the ages of 16 and 18. A condition set has been associated with Adult Inpatient Substance Abuse Treatment such that it is only recommended to male clients over the age of 18. Based on this condition, Adult Inpatient Substance Abuse Treatment is recommended for James as he is over the age of 18 and is a male.

Relationship Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions.
Model Details
Location in Model: Logical View::MetaModel::Curam::Condition::Entity::ConditionSet
Controlling File: AssessmentPlanning\model\AssessmentPlanning.emx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (5)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
conditionSetIDkeynoThe primary key for the condition set entity. The key is auto generated based on the CONDITBO key server configuration.INTERNAL_ID SVR_INT64
namedetailsnoThe name of the condition set.CONDITION_NAME SVR_STRING<100>
descriptiondetailsyesA description of the condition set.CONDITION_DESCRIPTION SVR_STRING<1000>
conjunctiondetailsnoLogical rules conjunction for the condition set. The following rule conjunction values are available: 1. And: all conditions inside the condition set must succeed for the condition set to succeed. 2. Or: at least one of the conditions inside the condition set must succeed for the condition set to succeed.CONDITION_SET_CONJUNCTIONConditionSetConjunctionSVR_STRING<10>
recordStatusdetailsnoThe record status of the condition set record, used for logical deleting condition set records.RECORD_STATUS_CODERecordStatusSVR_STRING<10>
Foreign Keys (5)
ChildParent
ActivityAdminConditionLink.conditionSetIDConditionSet.conditionSetID
ConditionSetLink.childConditionSetIDConditionSet.conditionSetID
ConditionSetLink.parentConditionSetIDConditionSet.conditionSetID
ExpectedOutcomeConditionLink.conditionSetIDConditionSet.conditionSetID
RecommendationConditionLink.conditionSetIDConditionSet.conditionSetID
Operations (4)
OperationStereotypeOptionsDescriptionSQL
insertinsertAUTO_ID: conditionSetID
AUTO_ID_KEY: CONDITBO
Standard Operation 
modifymodifyOPTIMISTIC_LOCKING: yes
Standard Operation 
readread Standard Operation 
searchByStatusreadmulti Searches for condition sets by record status, used to list all the active conditions. 
Related Pages (13)