Lesson 6 Flashcards
Workflow Engine is configured to control four patient workspace settings called:
Activity tabs (to the left of the patient chart)
More menu (formerly known as the More Activities or Action menu)
Navigators
Sidebars (when using widescreen view)
Where do you link to a Workflow Engine rule?
Profile
How does the system know which Workflow Engine rule to use?
The Workflow Engine rule linked to the most specific level in the profile hierarchy is the rule that will be consulted.
What are three aspects of a patient encounter that can be altered based on a rule match?
Answers will vary. Some include: Override or Append More Activities menu, Change default activity when a workspace opens, Change available navigators.
True or False. If the patient encounter conditions do not match a Workflow Engine rule the system looks for a rule in the next level of the profile hierarchy.
False. Settings found in the role and compiled profile for the patient encounter will be used. The system will not look for additional Workflow Engine rules at other levels in the profile hierarchy.
True or False. Once a rule matches on conditions and carries out directives, the system always keeps looking for more conditions to evaluate.
False. The system will only continue evaluating the rule if the first set of directives specifies “continue afterwards.
Define Workflow Engine
Each WE rule is composed of a set of conditions (“if” statements) and directives (“then” statements). The conditions evaluate properties about the user, the patient, or the type of encounter (admission, office visit, etc.). After matching on conditions, the directives then arrange the patient workspace.
Define Directive
directives (“then” statements) The “then…” portion of the rule (directives) tells the Workflow Engine what to do if the rule matches the conditions specified in the “If…” portion.
Define Conditions
conditions (“if” statements) The “If…” portion of a rule (condition) specifies which properties and values the “then…” portion applies to. The rows that start with “if” evaluate properties.
Define Property
Property = Relevant Information Every clinical workspace has many properties, such as encounter type, patient age, and provider specialty. Each property used in the Workflow Engine is defined by a property record in the Properties (LRC) master file. Epic programmers build these records. What properties can the Workflow Engine evaluate? Some available properties are Patient • Patient Encounter Department • Patient Encounter Type (e.g. INP, HOV, ED, AMB) • Patient Sex • Patient Age (years) • OB/GYN status • Patient Class Department • Source Encounter Department Specialty • Login Department Specialty Provider • Login provider’s Specialty • Login provider’s Provider Type Appointment • Appointment Visit Type • Is Appt. Scheduled from an Order? Status of Care • Case Progress Status (pre-op, intra-op, post-op, etc.). More properties are added with each new release of Epic software. Conditions use property (LRC) records to form the beginning of a rule.
Define Rule hierarchy
The Workflow Engine rule was created to override those more generic settings when needed.
A profile record can link to a Workflow Engine rule record, and like any other item, the most specific level in a user’s profile hierarchy is the one that will be respected.
In any given workspace, only one Workflow Engine rule will be consulted and used. Regardless of whether or not the patient encounter matches the conditions in that rule, the system does not look any further in the hierarchy for other Workflow Engine rules.
Define Workflow Engine Rule Editor
A type of rule used to define the activities and navigators available when a clinician opens an encounter in the unified clinical workspace. Workflow Engine rules are built in the Workflow Engine Rule Editor.
Define Active rule contact
After making changes in a new inactive contact, you must activate it to make your changes available. You can activate the contact you are editing by clicking Activate on the Workflow Engine Rule Editor toolbar. Only one contact in a rule can be active at a time. Activating a contact automatically deactivates the previous contact that was active.
The relationship between Workflow Engine rules and profiles
A WE rule runs every time a user opens a patient’s chart to allow patient workspaces to be altered in real time to fit users’ workflow needs. Defines the properties of a given field in Hyperspace (for example, recommended, required, or read-only); can be specified for different activities and, for certain purposes, at different levels of the facility structure.
How the Workflow Engine evaluates properties
Workflow Engine uses condition and directive statements to evaluate properties
