Class: Condition_node

Description of: Condition_node

Class steward is Patient Care
Interested committees Orders/Observation
An action which is an Assessment that defines the status of a condition thread at a given point in time. Condition thread is defined by service event relationships between condition_nodes.

OpenIssue: Definition needs further work. Use of the word thread needs to be re-examines. The committee should consider defining the thread as a separate recursion. Get an example.

Attribute definitions for: Condition_node

actual_resolution_dttm

The date/time that the condition was actually resolved.

employment_related_ind

An indication that the diagnosis is employment related.

Rationale: To replace attribute previously inherited by Diagnosis from Patient_clinical_item

OpenIssue: Should this be handled as an explicit diagnosis in Health_issue or should it be deleted completely, or does this require longitudinal linkage through Condition_node?

estimated_resolution_dttm

The estimated date/time for resolving the stated condition.

OpenIssue: Is this a kind of a goal or not?

life_cycle_status_dttm

This field indicates the effective date/time of the current condition life cycle status.

lifecycle_status_cd

This field indicates the effective date/time of the current condition life cycle status.

OpenIssue: Accept attribute description of life_cycle_status_cd. Redefine life_cycle_start_dttm.

management_discipline_cd

The category of caregiver with interest in a specific condition thread (e.g., nursing, medicine, respiratory therapy, dietary, etc.). This is a repeating field to allow identification of all disciplines who may have interest in this condition.

Rationale: 2.3 definition was wrong.

OpenIssue: Has to be multiple, and how can we indicate when a particular category initiates or withdraws their indicated interest.

onset_dttm

This field contains the date/time when the condition actually began as determined by the caregiver.

OpenIssue: This and the Condition_code.onset_time_text attribute need to be considered in a new either/or data type (precise or imprecise) for a dual kind of time.

onset_time_txt

This field allows for a textual and imprecise representation of the time when the condition began.

OpenIssue: This and Condition_node.onset_dttm attribute need to be considered in a new either/or data type (precise or imprecise) for a dual kind of time

ranking_amt

This field is used to rank this condition when placing multiple conditions on an ordered list.

OpenIssue: Issue of ranking and priority needs remodeling-both need to be considered as single chang; should this be numeric attribute type? People are uncomfortable with the issue of ranking and priority. Need to consider this attribute with problem_list_priority.

Association definitions for: Condition_node

specified_in (0,1) :: Episode :: specfies (0,n)