Epic Care Ambulatory 400 Latest Update with Verified Solutions

Epic Care Ambulatory 400 Latest Update with Verified Solutions Ease of Configuration Flowsheets are built in Hyperspace and are fairly intuitive to build and edit. Discrete Documentation Flowsheets are composed of rows. Each row tracks an individual, discrete piece of information. Each row allows a specific type of data entry, such as free text, numeric, selection list, or date/time. Visit-level Data Information filed in flowsheets is specific to the visit. You can configure a flowsheet to allow either multiple readings during a single visit or only one reading per visit. Embed in a navigator section You can embed commonly used flowsheet forms (templates) into navigators. Doing so prevents your users from needing to leave the navigator to go to the flowsheets activity. Data is reviewable elsewhere Data entered in flowsheets can be retrieved and reviewed in many other tools, such as review flowsheets, print groups, SmartLinks, Reporting Workbench, Clarity, and BestPractice Advisories. View trending across visits You can configure review flowsheets to display data form the same flowsheets across multiple (even unrelated) visits. If a visit is part of an episode, you can review values from other visits in the episode alongside the data from the current visit. This helps clinicians observe trends and spot potential problems without having to hunt for data. Shared Documentation If a specific flowsheet row is used by more than one type of provider ( for example, a physical therapist and a physical medicine & rehab physician), data from all those providers is displayed side-by-side when reviewing that data. Cascading flowsheet Flowsheets can be set up to start with a small number of data entry rows and expand based on values entered. For example, entering Yes in a row could cause other rows to cascade in. Template Seen as a "tab" in the flowsheet activity. Row Data is documented here. Group Used to organize individual documentation rows. Detail Report Provides clinicians extra details about the row they are documenting in, like minimum and maximum values, and who documented on the row last. Flowsheet Groups Record that organizes flowsheet rows Flowsheet Rows Record where data is recorded. Designed to hold specific data. Flowsheet Template Record that organizes flowsheet groups. Used to group similar categories of documentation together. Appears as a tab in the flowsheet activity. Table of Contents Topics are listed here within flowsheet templates to make it easier for clinicians to navigate flowsheet groups. When clinicians are documenting flowsheet information in the Flowsheets activity, they can click on a topic within this section to expand the groups within it and jump directly to the first group in the topic. Row Types Defines the purpose for a record. Ex: Flowsheet Group, Properties, Data, etc. Value Types Defines the information you are entering in a row. Changes based on what selection is made for row types. Group Form Located in a flowsheet group record where you can specify all the rows that should normally show up in the group by default. Topic Column Organizes similar groups together under the table of contents in a flowsheet template. Flowsheet A customizable documentation tool typically used in specialties that need to capture a wide variety of information discretely. Warning Minimum/Maximum If a user enters a value less than or greater than the _______________ set in the row record, the value will be flagged as abnormal. Minimum/Maximum Values If a user enters a numeric value _______________ less/higher than what is listed in the ______________ field within the row record, they will receive an error message and cannot file the data. Procedure Record This is the most specific level of the procedure hierarchy. This record is part of the EAP master file. Procedure Category Record This record is used to group together similar procedures that share common settings. It is part of the EDP master file. System Definitions The record is used to configure system-wide settings and acts as a catch all for order defaults. It is always record 1 in the LSD master file. EMP 450 Category List A list of In Basket classes to which the user is assigned. These classes typically correspond to the user's function or duties within your facility. Classifications options are set up as a category list (I EMP 450). Enter or completion match to a classification from this category list. Class Message single message to a group of recipients Pool Message When a user sends an In Basket message to a pool, the message is available for all members of the pool to see, and any member can act on it. However, there is only one "copy" of the message available to all members of the pool. When someone is acting on the message, it is essentially checked out and unavailable to other members. Thus, only one member at a time can act on the message. Once the message is completed by one member of the pool, the message is no longer available to other members of the pool. registry record These records are defined by a set of inclusion rules and metrics that determine the patients who should be included in the registry and the information about each patient that should be collected. Flowsheet editor The activity used to build review flowsheets synopsis view Review tool that allows clinicians to visually compare data in both a grid and a graphical format on the same screen synopsis view section print group records (LPG), defines how a view's clinical data is arranged, appears as a folder, built in Clinical Admin synopsis view section part Synopsis flowsheets(FSH), define the actual data that appears in each view section (medications, notes, procedures, result components, (doc) flowsheets, visit information (vitals), Smart data elements, transplant information, questionnaire and order specific question/answers), Built in hyperspace using flowsheet editor (FSH) What defines the specific data you want to appear, based on what you entered in the source field. If the source is for medications, the what would be a specific medication record Source determines the type of data that appears in the view section and where the system looks for this data. Options available as sources depend on flowsheet type. Procedure Category (EDP) used to group together similar procedures that share common settings Procedure (EAP) The most specific level of the procedure hierarchy System Definitions (LSD) used to configure system-wide settings and acts as a catch all for order defaults Order Composer Configuration (OCC) Controls display item, item control and summary item Display Item controls the items that display in the order composer when ordering the procedure (status, priority, class, reason for exam, schedule instructions, comments, & last resulted) Item Control Used to make an field required, recommended or just blank when empty (Order Class) Summary Items drives what values pulls into the summary sentence (Normal/Future/ Standing Status & Priority) Result Component A record in the Result Component (LRR) master file. Component-based tests and procedures are made up of result components Lab-related SmartLink Allowed Order Class field drives which order classes can be found under the selection button for all procedures linked to this category. In order to specify an order class as the default or as a button in the order composer, it must be listed as an option here Functional type Restricts the activities/scenarios in which a SmartText may be used. A functional type must be specified in the SmartText Record. An example is MR Charting. historical immunization An immunization that a clinician is documenting that was completed prior to the current encounter. Preference List Composer The activity used to create composer-based preference lists. Anything that is ordered & will have an order composer( Medications, Labs & Referrals) FAM Preference List Preference list containing Facility Administered Medications (FAMs), also known as Clinic-Administered Medications. Preference List Editor Editor based list; All other types(non-orders) (diagnoses, reason for visit, level of service) Preference List A set of frequently used orders. SmartSet A documentation template. A group of orders and other elements, such as notes, chief complaints, SmartGroups, and levels of service, that are commonly used together to document a specific type of visit. SmartGroup A reusable group of orders and documentation elements, such as a chief complaint or level of service, which can be used in Protocol-based SmartSets and Order Sets. SmartGroup Panel (order group) A group of orders often ordered together. In Epic, order groups can be created so that these orders can be added to a treatment plan in one action. Section Individual building block of a navigator topic. Examples of sections include Progress Notes and Medication Documentation. Subsection Referred to as a SmartGroup by end users Order-Specific Questions Used to capture additional information which needs to be sent to an ancillary service in conjunction with an order. Additional data captured in scheduling or clinical lab questionnaires can also be sent as part of an outgoing order message. BPA criteria Best Practice Advisory records used to evaluate patient specific data (medication, diagnosis, & past procedures) BPA SmartSet Base Best Practice Advisory records used to control when a SmartSet should display based on the conditions or linked criteria records BPA SmartSet Suggestion Best Practice Advisory records used to evaluate non-patient specific data (encounter type, provider type or department specialty) EOW Master File In Basket message master file where In Basket messages are stored as a record. Message Type drives what folder the message will appear in; mapped to message type definitions Epic Wide Settings Level affects all users; recommended to map most message types to message type definitions at this level; easiest to update and maintain