11.3 Reusable Components These data elements represent reusable sets of data that are can be used in any combination across a CDS Knowledge Artifact. 11.3.1 Actions In order to support basic functionality for Actions within the first iteration of the standard, only Notifications and Orders will be supported initially. However, the Action constructs themselves should be built in such a way that they support extension to different action types (such as Fire Event, or Inference) in future iterations. In addition, the Actions should support the ability to capture complex actions, in the same way that Order Sets can capture multiple actions as a group. Section Name & # Data Elements Data Element Descriptions Cardinality Additional Notes Description Action mode Name: Action 1 Action mode describes whether a Single (Multiple) new action sentence is being added, an existing action sentence This is is being refined, or an existing or Description: the consequence of contemplated action sentence a positive evaluation should be discontinued. of the clinical 2 Supporting Evidence See supporting evidence Multiple scenario expression. component. It includes a 3 Supporting Reference See supporting reference Multiple structured action component. that can be enacted Urgency 4 An indicator of the urgency with Single by the user. which the action must be executed. 5 Action Sentence See Action Sentence defined Single 6 Action Text A textual description of the action Single It is permissible for the Action to be performed. Sentence to be empty, and for the formattable (tabs, spaces, etc.). Action Text to constitute the action.
11.3 Reusable Components These data elements represent reusable sets of data that are can be used in any combination across a CDS Knowledge Artifact. 11.3.1 Actions In order to support basic functionality for Actions within the first iteration of the standard, only Notifications and Orders will be supported initially. However, the Action constructs themselves should be built in such a way that they support extension to different action types (such as Fire Event, or Inference) in future iterations. In addition, the Actions should support the ability to capture complex actions, in the same way that Order Sets can capture multiple actions as a group. Section Name & Description # Data Elements Data Element Descriptions Cardinality Additional Notes Name: Action (Multiple) Description: This is the consequence of a positive evaluation of the clinical scenario expression. It includes a structured action that can be enacted by the user. 1 Action mode Action mode describes whether a new action sentence is being added, an existing action sentence is being refined, or an existing or contemplated action sentence should be discontinued. Single 2 Supporting Evidence See supporting evidence component. Multiple 3 Supporting Reference See supporting reference component. Multiple 4 Urgency An indicator of the urgency with which the action must be executed. Single 5 Action Sentence See Action Sentence defined Single 6 Action Text A textual description of the action to be performed. formattable (tabs, spaces, etc.). Single It is permissible for the Action Sentence to be empty, and for the Action Text to constitute the action.
SIFramework_HeD_UC1_CDSArtifactSharing_v1.0.docx