Discussion - Example of a Customized Docuplate

 Pre-Purchase --> Purchase --> Installation --> Advanced User Customization --> General Training  ---> Use/Go Live

 

 

This tutorial is intended to demonstrate some of the issues and steps related to the use of a customized docuplate. A docuplate for Upper Respiratory Infection encounters is utilized. While all clinicians may not treat this condition, we all have had at least some experience dealing with it.

This tutorial is not intended to suggest a particular type or style of documentation for URI encounters, nor is it intended to indicate what specific data elements should be used. This is just one of many ways to create documentation in SOAPware. The greatest strength and weakness of SOAPware is its degree of flexibility to adapt to almost any style.

Some practices have created customized encounter forms for use for particular types of patient visits. For example, here is an example of a very customized paper form that a practice created for their own use.

This turorial is fairly involved and extensive. To see how to just create/store a simple docuplate, see - Docuplates: Speeding up Your Documentation .

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

URIadultForm.jpg

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

What is particularly prudent in this form is that it allows the patient to collect most of the history in the Patient Section. The patient starts by answering the questions, and the clinician can add edits and comments while reviewing with the patient. Learning how to involve the patient, more, in the documentation process is likely to be a key to success in the future. An electronic record makes it much easier to delegate the documentation of the historical information. This is also a key means that successful practices have used to migrate to electronic records while reducing the total amount of time clinicians spend performing documentation.  Let the patient or medical assistant create the bulk of the documentation. (Actually, Instant Medical History software is often a more efficient means to collect the historical, Subjective information than what will be demonstrated here.)

Once the patient has done their part, the clinician reviews the information with the patient and makes appropriate edits. Because the intent of this tutorial is to demonstrate how to create customized workflows within SOAPware, we will assume that the clinician's assistant is usually interacting with the patient while creating the Subjective or historical portion of the encounter/SOAP note documentation within SOAPware.

This demonstration will primarily show how the elements in the above form could be incorporated into a SOAPware encounter docuplate. Having a medical assistant utilize the encounter docuplate combined with them having them update the medical summary will allow for the preferred documentation to be created very efficiently.

 

Example of Completed Paper Encounter Form

Here is an example of how a completed paper form might appear:

 

URIformInked.jpg

 

 

Sometimes the best approach is to begin with the ending. The following are some examples, end results of SOAPware documentation. In this particular example, nothing was typed. All the data entry in this example was via pick lists. However, clinicians can either type or use pick lists in all areas of documentation.

 

Example of Final SOAPware Documentation

Here is one example of how the final documented could appear after creation in SOAPware:

URICustomFinal-D.jpg

 For your convenience, the documentation, above, has been stored in a docuplate - URI-1.

 

Example of Final, Printed Documentation

 Below is one example of how the above documentation could be displayed in a printed/stored format.

URIcustomPrint-D.jpg

 

 

 

The Starting Docuplate - URIcustomA

 

 

URIcus1.jpgURIcus2.jpg

 

 

Overview of Topics in the Discussion in this Section

  1.  URIcustomA is the actual docuplate used.
  2.  URI-1 is a docuplate that was stored as an end point in this discussion, but it could actually be a starter for some URI pateint encounters.
  3. This discussion demonstates some issues to address as clinicians design their own, unique style so that documention can be created with minimal actions.
     

1. Subjective docuplate Customization Demo

  • Pick List method
  • Toggle method
  • Free-text method

 

2. Objective Docuplate Customization Demo

  • Click on Exam and uncheck the systems not to be routinely displayed.
  • Click on each remaining system header and uncheck the exam items not to be routinely displayed.
  • Change the default findings for each exam as desired with discussion of

Pick List method

Free-text method

 

2. Plan/Assessment/Medication Docuplate Customization Demo

  • Create a pick list of most common items when URI docuplate is used.

 

So, this discussion has started by showing an example of the final documentation (i.e. as in docuplate UR!-1). The general process in this discussion will be to continue to work backwards by first showing examples of final documentation; how documentation can be created; and then demonstrating how to create the docuplates and SMARText items that make the creation of the documentation possible.

Hopefully, by the end of this discussion section, you will be able to start with the docuplate URIcustomA; make some clicks and edits; and end with documentation appearing similar to that in URI-1. Along the wey, we will discuss some issues to both use and the creation of this style of docuplates. We suggest following the Path  below by clicking on the link at the bottom of each page.

 

 

 

Notes:

The examples in this tutorial will appear very different with the SMARText items available prior to January, 2009. SOAPware versions previous to January, 2009 will not have all the capabilities demonstrated here. We strongly suggest updating your SMARText items before performing this tutorial. SMARText will continue to be in rapid evolution through 2009 and 2010, so plan to update at least every week or two.

The screen shots and examples in this tutorial will all appear slightly different on your system and over time.

 

 

Path- Subjective Documentation

Copyright © 2008 SOAPware, Inc. All rights reserved. Contact UsNews Blog RSS Feed