Smart Forms CLN301 Flashcards
What is a SmartForm?
SmartForms are highly customizable tools that are used to capture discrete clinical data across many of Epic’s applications. SmartForms can be used in a wide variety of activities across Hyperspace from within NoteWriter, custom activities, Navigator sections, and specialty workflows.
Where are SmartForms Used?
SmartForms are useful tools in the NoteWriter, Navigator, ED Manager, Delivery Summary, and many other places in Epic across several applications.
What is a Note template?
Note templates are SmartText records with preconfigured text and Smart tools that can include SmartLinks, SmartLists, SmartPhrases, and SmartBlocks within them. SmartBlocks act as a place holder for text generated by SmartForms documented on in the NoteWriter
Why do the Abdominal Pain and Fever SmartForms open?
HPI SmartForms can, by default, open up a SmartForm based on the chief complaint entered in the Visit Info section. This saves clinicians time because they do not need to manually look up an HPI form related to the patient’s documented chief complaint. Clinicians can add additional complaints in the Add HPI form field.
Why are Fever and Abdominal pain already selected as positive values?
Within the NoteWriter, you’ll see that some items are preselected because they correspond to the same item on a different form within the same note. Data documented within one SmartForm can track across multiple SmartForms based on the context of the documentation. It may be the case where a patient’s fever is an associated symptom of their abdominal pain and vice versa.
What happened to the “Dry” selection when you selected
“Moist”?
In SmartForms, certain values should never be selected with another value because the two choices selected together don’t make sense. Scripting can restrict users from making certain choices that don’t make sense together, and can also provide additional sections of a SmartForm to appear based on selections.
When is a SmartForm the right tool?
Tier 1: Easiest to build and maintain, so are most sustainable
Use existing tools such as partial dictation, Dragon, SmartPhrases, SmartText, and
Foundation System NoteWriter forms. If you end up needing to build a tool, first consider SmartPhrases and SmartTexts.
Tier 2: Flowsheets (fka Documentation Flowsheets) – harder to build and
maintain but can do some things Tier 1 tools can’t
Flowsheets require more planning and setup, but can do some things that
SmartPhrases and SmartTexts can’t do. One benefit of using this tool is the ability to store discrete data.
Tier 3: SmartForms—most challenging to build, but offer benefits not available in the other tools; substantial design time
While SmartText/Phrases can generate a note and doc flowsheets can store discrete
data, SmartForms can do both. In addition…
- Scripting: SmartForms can do things like “set all values to negative” in a way that doc flowsheets and SmartText can’t.
- Images: Only SmartForms can incorporate the use of images.
• Design features: SmartForms can combine features like tri-state controls
(positive/negative buttons), SmartTool-enabled text boxes, buttons, etc.
• Text generation: NoteWriter SmartForms can generate prose text based on selections and free text comments.
Why SmartForms?
SmartForms are flexible, comprehensive, reportable, and contextual.
When should you use a SmartForm for documentation needs?
A SmartForm should be used for documentation when other Epic tools simply do not meet your needs. SmartForms offer things like scripting and image documentation that other SmartTools like SmartText and Flowsheets don’t offer. A SmartForm also offers a way to document and store discrete clinical data.
What does a SmartForm offer that a flowsheet does not?
Flowsheets are restricted in the type of data they can store and where
they can store it. They offer a way to document patient information, but in a different format than a SmartForm. SmartForms offer the ability to script, host images, document very granular patient data, and more. See the table on pages 13 and 14 of this chapter for more details.
Classification
Type of SmartForm
- OB Delivery Record
- HPI
Ensures consistency among
similar SmartForms. Determines which components and data can be used along with other properties.
Layout
Structure of the SmartForm
• Rows
• Cells
Used to organize the
components using a table
Component
Individual piece of content for a cell
Presents the content in various
formats, such as lists (buttons) and check boxes for ease of documentation
A formlet is a grouping of
components that you can configure once and then reuse within multiple SmartForms.
Using formlets can save you
build and maintenance time
SmartData
Element
Data provider
Supplies data that isn’t tracked
in a Chronicles master file.
Context
Level of granularity • Patient • Note • Encounter Used to control the level at which the captured data is stored
Value
The end-user’s selection
Stores response that is selected;
linked to the SmartData element and the context
Name five different pieces that make up a SmartForm:
Classification, Cells, Components, SmartData Elements, Tables, Formlets, Properties, Context, and more.
Define the classification of a SmartForm and what it controls
The classification of a SmartForm forces consistency between forms that are used for a similar purpose. This includes where the form can be used in Hyperspace, the types of components you can add to it, and the context the forms components can be assigned.
Where are SmartData Elements stored and created?
SmartData Elements are stored in the HLX master file and can be created and viewed in the SmartData Manager.
When should you use an Element ID data type SmartData element instead of a Category data type SmartData element for a list component?
Element ID SmartData elements for list components should be used when you need to document the presence or absence of a condition using other, Boolean type SmartData elements. Category SmartData elements for list components should be used for describing the condition.
What are the different options to choose from under the
Layout tab?
Table, Row, Cell, and Formlet
What is a SmartData Identifier for a SmartData Element?
The SmartData Identifier is the external ID of a SmartData Element. This is not the same as its .1 (record ID). It is stored in item 40 of the HLX record. It provides a small amount of information including which type of form an element is meant to be used for.
Where would you store the patient’s emergency contact information?
Patient’s Chart – Patient level context
How would you document the patient’s recovery?
Over multiple episodes – Episode level context
Within which context might you consider storing the functional status of the patient during the 6-week follow-up visit?
Answers may vary. This could be used at an encounter level. However, if the patient had a series of post-transplant visits this could be set up at an episode level as well.
Where in the patient’s paper chart might you find information pertaining to their recovery status?
What master file will you consult to find information to report on?
How might you organize your search to more quickly find this information?
Progress Note, The HLV, Do a data search based on Note Context value records
How can we configure the NoteWriter to fit everyone’s needs?
We can set up Note templates for users and assign them to profiles
Briefly describe the relationship between an Event and a
Check
An event is the trigger action that causes a check to run. The check contains the information needed to verify the event occurred.
Are the same types of components available to add in the Print
Group Designer as are available in the SmartForm Designer?
Which components are available to add in the Print Group
Designer?
NO. THE PRINT GROUP DESIGNER HAS FOUR COMPONENTS AVAILABLE: DATA, HYPERLINK, LABEL, AND SMARTGRID.
Identify the different master files that need to be accessed during SmartForm Print
Group setup: j
SmartForms (LQF), Print Group (LPG), Report (LRP), Profile (LPR). Potentially the Navigator (LVN) and Configuration (VCN) master files as well depending on your customization.