https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Tyler.Yoder&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T01:34:49ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=MU2_e-Referrals_Are_you_Ready%3F&diff=18902MU2 e-Referrals Are you Ready?2014-11-09T03:51:23Z<p>Tyler.Yoder: /* Q&A */</p>
<hr />
<div>[[Category:Webcasts]]<br />
<br />
==Webcast Details==<br />
<br />
Considerations, configuration, testing, & demo from Galen SMEs who have implemented eReferrals.<br />
<br />
<br />
Originally aired: <br />
Friday, October 17, 2014<br />
Presenters: Laura Gold and Tyler Yoder<br />
<br />
==Webcast Materials==<br />
[[Media:EReferrals_Are_you_Ready_PowerPoint_PDF.pdf|e-Referrals Are you Ready? pdf]]<br />
<br />
<br />
==Q&A==<br />
<br />
'''Q. On the Galen website where can we review the recording of this presentation? I would like to share this with my team.<br />
<br />
'''A.''' The slide deck is posted above, but to view the recording, please contact our sales team at sales@galenhealthcare.com<br />
<br />
<br />
'''Q. We are getting the task but not the SOC doc from other providers, so when we open the task there is nothing attached. Im wondering if it could be an issue in our configuration?<br />
<br />
'''A.''' This could be being controlled by the Verify CED Document preference. If this preference is set to No, the incoming CED will not generate a task & require verification, & will file directly into the chart. If other types of documents are being attached & not being received, this could be an interface problem where the attachments are not making it through the interface, so yes, this sounds like it could be a configuration issue & would require some investigation.<br />
<br />
<br />
'''Q. All of our messages are coming into EHR as Match Patient even though Recipient is identified. Is that how they will always come into EHR as a match patient?<br />
<br />
'''A.''' No. The CED Match Patient task is generated when you receive a referral for a patient that is not in your system, or there is something in the incoming patient demographic info that does not match up with the corresponding patient in your system.<br />
<br />
<br />
'''Q. If you unlink the referring provider dictionary entry from the TW User entry, does that impact Charge? We were told that in order for charges to cross from EHR to PM correctly, that the provider had to be linked as a referring provider.<br />
<br />
<br />
'''A.''' This depends on how your charge interface is setup & whether it requires the referring provider info to be entered into the encounter form to flow successfully through the interface to your PM system. Insurance companies ultimately control this, because they dictate whether they will pay a claim if the referring provider info is missing from the claim. We have seen both cases with clients who always required referring provider, & other clients who did not require the referring provider to be entered & just trusted their billers/coders to catch it & enter it for those insurances that require it.<br />
<br />
<br />
'''Q. As a shared Org can we still send ereferrals to other orgs and just not have it count in the reporting?<br />
<br />
'''A.''' If you keep thw TWProvider & Referring Provider dictionaries linked, these referrals between your orgs will be considered internal & not count towards your MU reporting. If you unlink the dictionaries, or if you refer to an OUTSIDE org, there is no way to exclude the e-referrals from your MU reporting that we know of.<br />
<br />
<br />
'''Q. When reading the final rule for Core Measure 15 in the Allscripts config guide, it states that "If the receiving provider already has access to the CEHRT...this transaction can be included in the denominator and numerator... But CMS rule also states that the referral must take place between providers with different billing indentities, so in our case we have providers with personal NPIs but bill under a group NPI what impact does that have on the Num/Den? We set up our providers as a sub set of providers in the Referral dictionary in order that they may qualify as external however they are still internal providers as well.<br />
<br />
'''A.''' Coming shortly....stay tuned.<br />
<br />
<br />
'''Q. Is it accurate that you need language, race and ethnicity on file prior to sending an e-referral?<br />
<br />
'''A.''' Yes. It is also required by Core Measure 3 for MU.<br />
<br />
<br />
'''Q. Can you attached unverified results if desired?<br />
<br />
'''A.''' We have a theory, but are testing to provide you with an accurate answer. Stay tuned...<br />
<br />
<br />
'''Q. Is there an easy way to obtain direct IDs for outside providers?<br />
<br />
'''A.''' In our experience, Allscripts could not provide us with direct IDs for any of the outside providers our clients referred to, so we had to cold call every practice & ask for direct IDs, which usually took a lot of explanation or being transferred to someone else or their EHR team.<br />
<br />
<br />
'''Q. How does it work when you refer to a an out of town speciality group? If they don't know which provider in the group will be seeing the patient when the referral is sent?<br />
<br />
'''A.''' You can add an entry (Practice name) to the Referring Provider dictionary & select the "Is practice" or "Is agency" field for the entry. A practice or an agency can have a direct ID, so if your organization would like to refer to a practice instead of a specific provider at the practice, this would be the way to set it up. Then in the Receipient field of the referral order, you would search for & select the Practice name that was added to the Referring Provider dictionary.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=MU2_e-Referrals_Are_you_Ready%3F&diff=18901MU2 e-Referrals Are you Ready?2014-11-09T03:50:24Z<p>Tyler.Yoder: /* Q&A */</p>
<hr />
<div>[[Category:Webcasts]]<br />
<br />
==Webcast Details==<br />
<br />
Considerations, configuration, testing, & demo from Galen SMEs who have implemented eReferrals.<br />
<br />
<br />
Originally aired: <br />
Friday, October 17, 2014<br />
Presenters: Laura Gold and Tyler Yoder<br />
<br />
==Webcast Materials==<br />
[[Media:EReferrals_Are_you_Ready_PowerPoint_PDF.pdf|e-Referrals Are you Ready? pdf]]<br />
<br />
<br />
==Q&A==<br />
<br />
'''Q. On the Galen website where can we review the recording of this presentation? I would like to share this with my team.<br />
<br />
'''A.''' The slide deck is posted above, but to view the recording, please contact our sales team at sales@galenhealthcare.com<br />
<br />
<br />
'''Q. We are getting the task but not the SOC doc from other providers, so when we open the task there is nothing attached. Im wondering if it could be an issue in our configuration?<br />
<br />
'''A.''' This could be being controlled by the Verify CED Document preference. If this preference is set to No, the incoming CED will not generate a task & require verification, & will file directly into the chart. If other types of documents are being attached & not being received, this could be an interface problem where the attachments are not making it through the interface, so yes, this sounds like it could be a configuration issue & would require some investigation.<br />
<br />
<br />
'''Q. All of our messages are coming into EHR as Match Patient even though Recipient is identified. Is that how they will always come into EHR as a match patient?<br />
<br />
'''A.''' No. The CED Match Patient task is generated when you receive a referral for a patient that is not in your system, or there is something in the incoming patient demographic info that does not match up with the corresponding patient in your system.<br />
<br />
<br />
'''Q.''' If you unlink the referring provider dictionary entry from the TW User entry, does that impact Charge? We were told that in order for charges to cross from EHR to PM correctly, that the provider had to be linked as a referring provider.<br />
<br />
<br />
'''A.''' This depends on how your charge interface is setup & whether it requires the referring provider info to be entered into the encounter form to flow successfully through the interface to your PM system. Insurance companies ultimately control this, because they dictate whether they will pay a claim if the referring provider info is missing from the claim. We have seen both cases with clients who always required referring provider, & other clients who did not require the referring provider to be entered & just trusted their billers/coders to catch it & enter it for those insurances that require it.<br />
<br />
<br />
'''Q. As a shared Org can we still send ereferrals to other orgs and just not have it count in the reporting?<br />
<br />
'''A.''' If you keep thw TWProvider & Referring Provider dictionaries linked, these referrals between your orgs will be considered internal & not count towards your MU reporting. If you unlink the dictionaries, or if you refer to an OUTSIDE org, there is no way to exclude the e-referrals from your MU reporting that we know of.<br />
<br />
<br />
'''Q. When reading the final rule for Core Measure 15 in the Allscripts config guide, it states that "If the receiving provider already has access to the CEHRT...this transaction can be included in the denominator and numerator... But CMS rule also states that the referral must take place between providers with different billing indentities, so in our case we have providers with personal NPIs but bill under a group NPI what impact does that have on the Num/Den? We set up our providers as a sub set of providers in the Referral dictionary in order that they may qualify as external however they are still internal providers as well.<br />
<br />
'''A.''' Coming shortly....stay tuned.<br />
<br />
<br />
'''Q. Is it accurate that you need language, race and ethnicity on file prior to sending an e-referral?<br />
<br />
'''A.''' Yes. It is also required by Core Measure 3 for MU.<br />
<br />
<br />
'''Q. Can you attached unverified results if desired?<br />
<br />
'''A.''' We have a theory, but are testing to provide you with an accurate answer. Stay tuned...<br />
<br />
<br />
'''Q. Is there an easy way to obtain direct IDs for outside providers?<br />
<br />
'''A.''' In our experience, Allscripts could not provide us with direct IDs for any of the outside providers our clients referred to, so we had to cold call every practice & ask for direct IDs, which usually took a lot of explanation or being transferred to someone else or their EHR team.<br />
<br />
<br />
'''Q. How does it work when you refer to a an out of town speciality group? If they don't know which provider in the group will be seeing the patient when the referral is sent?<br />
<br />
'''A.''' You can add an entry (Practice name) to the Referring Provider dictionary & select the "Is practice" or "Is agency" field for the entry. A practice or an agency can have a direct ID, so if your organization would like to refer to a practice instead of a specific provider at the practice, this would be the way to set it up. Then in the Receipient field of the referral order, you would search for & select the Practice name that was added to the Referring Provider dictionary.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Security_Levels&diff=15856Security Levels2012-12-27T20:46:15Z<p>Tyler.Yoder: /* Finalization Authority */</p>
<hr />
<div>__TOC__<br />
<br />
=='''Overview'''==<br />
Refers to the '''Ownership Authority''' and '''Finalization Authority''' levels set for each user.<br />
<br />
===Ownership Authority===<br />
Ownership Authority is used to determine who can own a specific Note. In order for the user to own a note, the note must have an ownership value at or less than the value assigned to this user. <br />
<br />
===Finalization Authority===<br />
This allows the user to finalize a note, where the note has a finalization value at or less than the value assigned to this user. Note finalization value is set in document type dictionary. (The purpose of this functionality is for the provider to be notified if/when a user makes an amendment to a finalized note. He would receive a task if this action occurred to resign the note).<br />
<br />
If a user has the correct authorities to own a note, but not finalize a note, the document type can be configured to automatically prompt the user to send a co-sign note task to a user who has the proper finalization authority. This is generally used for mid-level providers who see their own patients and write their own notes, but their organization requires their notes to be co-signed by an attending provider.<br />
<br />
==Links==<br />
Back to [[Security]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Task_Dictionary_Setup&diff=15855Task Dictionary Setup2012-12-27T20:33:08Z<p>Tyler.Yoder: /* Task Name Dictionary Configuration */</p>
<hr />
<div>__TOC__<br />
<br />
=Description=<br />
The Task Name dictionary is used to indicate the name assigned to a task. Names are used to track tasks within TouchWorks. This dictionary contains some enforced entries delivered by Allscripts, as well as new tasks added by a system administrator.<br />
<br />
=Definition=<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
* '''Task Action''' - Task Action determines the location a user may create that task from. Some examples are:<br />
{| {{table cellspacing=10}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action:'''<br />
| align="center" style="background:#f0f0f0;"|'''Creation Location:'''<br />
|-<br />
| Authorize Order||AuthenticateOrder||<br />
|-<br />
| Review Charges||ChgWorksEncounterForm||<br />
|-<br />
| Sign Note||DWNote||<br />
|-<br />
| Verify Results||ResultsVerifyBatch||<br />
|-<br />
| <br />
|}<br />
''Note: Once the task action is linked to a task and saved, it is permanent and cannot be changed later.''<br />
<br />
* '''Default Overdue Time Priorities''' - These define the time priorities for which the task becomes overdue if not completed within the default time interval assigned to the priority.<br />
* '''Delegate''' - Non-Delegated tasks are tasks organized and worked by a user from their “My Active Task” view. Delegated tasks are tasks created by a user, but worked by someone else. These tasks do NOT display on the “My Active Task” view for the user, so a separate task view must be created to view and work delegated tasks.<br />
* '''Copy to Note Options''' <br />
* '''Complete the Task when Copy to Note'''- If checked, the task will be marked as completed when the task is copied to a note. <br />
* '''Default Encounter''' - If selected, this type of encounter will be created by default, and the note will be linked to this encounter.<br />
* '''Default Note Type''' - If selected, this type of note will be created by default<br />
<br />
=Task Name Dictionary Configuration=<br />
# Login as TWAdmin.<br />
# Go to the Dictionaries VTB, and select the '''Task Name''' Dictionary from the drop down menu.(From here, tasks can be edited or created.) <br />
# To create a new task, click "Add" at the bottom of the screen, and enter appropriate code, name, and mnemonic.<br />
# Select appropriate Task Action and assign overdue times as seen fit.<br />
# Click Save when finished.<br />
<br />
[[Image:Task Name Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Task_Dictionary_Setup&diff=15854Task Dictionary Setup2012-12-27T20:32:50Z<p>Tyler.Yoder: /* Task Name Dictionary Configuration */</p>
<hr />
<div>__TOC__<br />
<br />
=Description=<br />
The Task Name dictionary is used to indicate the name assigned to a task. Names are used to track tasks within TouchWorks. This dictionary contains some enforced entries delivered by Allscripts, as well as new tasks added by a system administrator.<br />
<br />
=Definition=<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
* '''Task Action''' - Task Action determines the location a user may create that task from. Some examples are:<br />
{| {{table cellspacing=10}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action:'''<br />
| align="center" style="background:#f0f0f0;"|'''Creation Location:'''<br />
|-<br />
| Authorize Order||AuthenticateOrder||<br />
|-<br />
| Review Charges||ChgWorksEncounterForm||<br />
|-<br />
| Sign Note||DWNote||<br />
|-<br />
| Verify Results||ResultsVerifyBatch||<br />
|-<br />
| <br />
|}<br />
''Note: Once the task action is linked to a task and saved, it is permanent and cannot be changed later.''<br />
<br />
* '''Default Overdue Time Priorities''' - These define the time priorities for which the task becomes overdue if not completed within the default time interval assigned to the priority.<br />
* '''Delegate''' - Non-Delegated tasks are tasks organized and worked by a user from their “My Active Task” view. Delegated tasks are tasks created by a user, but worked by someone else. These tasks do NOT display on the “My Active Task” view for the user, so a separate task view must be created to view and work delegated tasks.<br />
* '''Copy to Note Options''' <br />
* '''Complete the Task when Copy to Note'''- If checked, the task will be marked as completed when the task is copied to a note. <br />
* '''Default Encounter''' - If selected, this type of encounter will be created by default, and the note will be linked to this encounter.<br />
* '''Default Note Type''' - If selected, this type of note will be created by default<br />
<br />
=Task Name Dictionary Configuration=<br />
# Login as TWAdmin.<br />
# Go to the Dictionaries VTB, and select the Task Name Dictionary from the drop down menu.(From here, tasks can be edited or created.) <br />
# To create a new task, click "Add" at the bottom of the screen, and enter appropriate code, name, and mnemonic.<br />
# Select appropriate Task Action and assign overdue times as seen fit.<br />
# Click Save when finished.<br />
<br />
[[Image:Task Name Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Answer&diff=15853Answer2012-12-27T20:24:33Z<p>Tyler.Yoder: /* Description */</p>
<hr />
<div>[[Category:Allscripts_Enterprise_EHR_Dictionaries]]<br />
__TOC__<br />
<br />
=Description=<br />
The Answer dictionary allows you to enter fields that are available within TouchWorks. You must find the corresponding Answer list in order to add answers. Adding entries to this dictionary allows for answers to be added to a picklist, which can then be tied to an additional information question. These answers then appear in a dropdown in the front end in any order that specific picklist is associated with.<br />
<br />
=Definition=<br />
<br />
[[Image:Answer1.jpg]]<br />
<br />
* '''[[Adding Items]]''' - Items can be added to an answer set (as seen in the left pane) or a new answer set can be created.<br />
* '''[[Picklist]]''' - Used to create picklists, which can then be attached to questions, located in the Additional Information dictionary, when the "answer data type" for a given question is defined as "picklist".</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Additional_Information_Configuration&diff=15852Additional Information Configuration2012-12-27T20:14:34Z<p>Tyler.Yoder: /* Definition */</p>
<hr />
<div>=Definition=<br />
Order(able) item questions, additional information questions, "AOEs", clinical questions and order entry questions are all terms used by clients and consultants to refer to entries in the [[Additional Information]] dictionary. These questions are used in orders to elaborate and give more specific details for the order. Additional information questions can range from asking the source for a fluid cytology, to asking the manufacturer and model # of a device like a pacemaker for a device check, or to asking the reason for a referral/follow up when a physician orders a follow up or referral for a patient. Below you can see an example of an order with multiple additional information questions. Some of these questions have picklists associated with them while others have a free text box associated with them.<br />
<br />
The '''Additional Information''' dictionary can be extracted and maintained via [[SSMT]]. It is important to note that the answers included in any picklist for these additional information questions are found in a separate dictionary called the [[Answer]] dictionary. <br />
<br />
[[Image:Additional info example.jpg]]<br />
<br />
=Additional Information Question Configuration=<br />
To properly build additional information questions, it is imperative to understand all the parts that make up the questions, and how they work. It is easiest to work backwards when building these questions.<br />
<br />
* First, build the answers to the questions in the [[Answer]] dictionary.<br />
* Second, build the picklist (if needed) with the answers.<br />
* Third, build the additional info question in the [[Additional Information]] dictionary.<br />
* Fourth, add the picklist to the question (if appropriate).<br />
* Fifth, add the additional information question to the order. This can be done within the application as described below, or using [[SSMT: OID - Additional Information Questions]].<br />
<br />
<br />
=Building the Answer Dictionary=<br />
To add entries to the [[Answer]] dictionary:<br />
*Login as TWAdmin.<br />
*Go to "Dictionaries" in the vertical tool bar.<br />
*Find the dictionary named [[Answer]].<br />
<br />
On the left, you will see answer groupings. I suggest creating a unique grouping to contain the answers for each question. Name them something unique and according to your clients naming convention, so you can easily identify them when building your picklist. To add a unique grouping:<br />
*Click "Answer" at the top of the left column in the dictionary.<br />
*Click Add.<br />
*Name your grouping.<br />
To add answers to the grouping:<br />
*Select the grouping.<br />
*Click Add.<br />
*Add your answer. The code and mnemonic can be whatever you choose. The name should be exactly how you want the answer to appear in the order on the front end.<br />
*Click Save.<br />
[[Image:Answer Dictionary.jpg]]<br />
<br />
To create a picklist containing the answers:<br />
*Click Picklist at the bottom of the answer dictionary.<br />
[[Image:Picklist Banner.jpg]]<br />
*Click Add Picklist, and name the picklist something unique to the question being answered.<br />
*Click add entries.<br />
[[Image:Answer Picklist.jpg]]<br />
*Find your answers on the left, and click add. Once done, ok, then click close.<br />
[[Image:Add entries to picklist.jpg]]<br />
<br />
=Building the Additional Information Question=<br />
* Login as TWAdmin.<br />
* Go to "Dictionaries" in the vertical tool bar.<br />
* Find the dictionary named [[Additional Information]].<br />
* Click Add.<br />
* Name your question with a code, mnemonic, and name according to your client's naming convention.<br />
[[Image:Addtl info dictionary.jpg]]<br />
* Under Detail 1:<br />
**The display name: exactly how the question will display in the order.<br />
**The answer data type: the type of answer you want tied to the question. This can be date/time, numeric values, a picklist or a free text box. Each answer type has its own special charateristics that need to be appropriately selected also.<br />
**Default value: the answer you want the question to automatically default to, if you want it to have a default answer.<br />
[[Image:Addtl info detail 1.jpg]]<br />
* Under Detail 2:<br />
**The answer will default section: where you set the behavior for how the default answer to the question behaves, if applicable.<br />
**This question is: where you can set if the question is required before saving the order, or if it goes into a "needs info" or "on hold" status if the question isnt answered when ordered.<br />
**Exclude question if patient sex is: where you can set if the question applies only to a certain gender.<br />
**Appear in note text for order: if this box is checked, the question and answer will display with the order in the plan section of the note.<br />
**Minimum and maximimum applicable age: where you can set to include or exclude the question based on the patient's age.<br />
[[Image:Addtl info detail 2.jpg]]<br />
<br />
* Under detail 3: <br />
**This is where you can set the behavior of what happens next, if the answer entered is a certain value. You can set the system to ask another additional info question if the answer is a certain value. You can also set the system to ask another additional info question if the answer entered does not match a certain value.<br />
[[Image:Addtl info detail 3.jpg]]<br />
<br />
* Once all the correct information has been entered, click Save.<br />
<br />
= Adding the additional information question to the order=<br />
* Login as TWAdmin.<br />
* Go to "Dictionaries" in the vertical tool bar.<br />
* Find the [[Orderable Item Dictionary]].<br />
* Click Search, and search for the order you want to apply the additional information question(s) to.<br />
* Highlight that order, scroll down to the instructions section, and click the link "Additional information questions".<br />
[[Image:OID.jpg]]<br />
* Search for the additional information question(s) you want to be tied to the order, and click the down arrow to add it to the order.<br />
* Click Ok.<br />
[[Image: OID OEQ.jpg]]<br />
* Click Save.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Patient_banner&diff=15851Patient banner2012-12-27T20:02:17Z<p>Tyler.Yoder: /* Description */</p>
<hr />
<div>=Description=<br />
The patient banner is the information bar across the top of the clinical desktop that displays a patient's information as selected by the organization. The information that displays derives from the the patient's demographics in the PM application which is sent via an interface. These fields can include the patient's Medical Record Number (MRN), Date of Birth (DOB), Age, Sex, Email, Primary Care Physician (PCP), Primary Insurance (PriIns), Home Phone Number (HPhone), Allergies, Directives, Security, FYI comments, Note, Nicknames (AKA), Work Phone, Social Security Number, and other information as the client sees fit.<br />
<br />
=Restrictions=<br />
The patient banner will only display 9 fields if the screen resolution of the workstation running Touchworks is 800x600.<br />
<br />
=Patient Banner Configuration=<br />
To set up what information will be displayed on the patient banner:<br />
# Login as TWAdmin<br />
# Select the Utilities VTB<br />
# Select the Patient Banner Setup HTB<br />
# Add or remove appropriate fields<br />
# Save.<br />
<br />
[[Image:patientbanner.jpg]]<br />
<br />
<br />
<br />
If checked, the "Display Patient Info in the Banner" checkbox at the bottom will insert an "i" icon on the patient banner that will display the patient's demographic information in a new window when clicked.<br />
<br />
<br />
=Troubleshooting=<br />
<br />
<br />
'''Problem''' <br />
<br />
Patient Banner configuration is inconsistent between users.<br />
<br />
To the user, it appears that some users see a different banner configuration that others. For example, one user may see the field name 'DOB' in the banner, and another user would not see this field name.<br />
<br />
<br />
'''Cause'''<br />
<br />
When using multiple web servers, it is possible for the patient banner configuration to be out of synch.<br />
<br />
<br />
<br />
'''Solution'''<br />
<br />
Using TWAdmin, login directly to each web servers dedicated IP address or name (e.g ASWEB1 and ASWEB2 instead of the virtual name 'ASWEB' and configure the banner as it should appear.<br />
<br />
<br />
<br />
'''Issue'''<br />
<br />
I would like the patient banner fields to display something different, for example Other2 to say C Phone<br />
<br />
'''Solution'''<br />
<br />
Navigate to the folder C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\Works\Working\CustomBanner.xml <br />
<br />
Open the file with a program that will allow you to edit the xml. <br />
<br />
Change the value in between the <label> </label> tags to whatever you want. For example Other2 to Cellphone.<br />
<br />
'''Note: This file must be copied to each web server! It may also get overwritten with upgrades so keep a backup of the XML file handy to reapply.'''<br />
<br />
'''Note: If the xml values are edited, but the change is not immediately reflected in the patient banner, please review the permissions for CustomBanner.xml and confirm that 'Everyone' has access to the file.'''<br />
<br />
[[Image:patientbannerpermissions.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Allergen_Reaction&diff=15850Allergen Reaction2012-12-27T19:56:41Z<p>Tyler.Yoder: /* Definition */</p>
<hr />
<div>[[Category:Allscripts_Enterprise_EHR_Dictionaries]]<br />
__TOC__<br />
=Description=<br />
The Allergen Reaction dictionary contains the list of possible allergic reactions when adding an allergy to a patient. This dictionary is not enforced and can be added and edited as desired.<br />
<br />
To add a reaction to a patient profile, find the allergy in the ACI, right click on the allergy, and click edit. The allergen details window will appear, and a reactions box wll appear in this window. To add a reaction for the allergy selected, click on the binoculars.<br />
<br />
[[Image:Allergen Reaction Details.jpg]]<br />
<br />
=Definition=<br />
[[Image:Allergen Reaction.JPG]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
<br />
==To Add New Allergen Reactions==<br />
* Login as '''TWAdmin'''.<br />
* Go to '''Dictionaries''', and select the '''Allergen Reaction''' Dictionary from the dropdown menu.<br />
* Click '''Add''' at the bottom of the screen.<br />
* Using the definitions above, fill out the information accordingly.<br />
* Click '''Save'''.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Encounter_Type&diff=15849Encounter Type2012-12-27T19:55:18Z<p>Tyler.Yoder: /* To Add New Encounter Types */</p>
<hr />
<div>__TOC__<br />
[[Category:Allscripts_Enterprise_EHR_Dictionaries]]<br />
== Description ==<br />
The Encounter Type dictionary is used to define the various types of encounters.<br />
All clinical data in TouchWorks must be tied to an encounter. Encounters<br />
can be created by appointments sent via the scheduling interface, notes<br />
created via call processing, and unsolicited results and transcriptions that come<br />
across the interface that are not already tied to an encounter.<br> <br />
The following encounter types are used within TouchWorks:<br><br />
<br />
*Appointment—default used for appointments that come across the scheduling interface; a specific encounter type can be entered in the Scheduling application and sent across the scheduling interface<br><br />
*Message—used for patient Notes copied from Mail <br />
*Other—used for results and transcriptions that come across the interface and create an encounter<br><br />
*Telephone Call—used for patient Notes copied from Call Processing <br />
<br />
This dictionary is called from:<br><br />
Note<br><br />
Encounter Form Selector<br><br />
Encounter Summary<br><br />
<br />
== Definition ==<br />
[[Image:Encounter_Type1.jpg]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
<br />
* '''Can Submit Charges for the Encounter Type''' -enables this encounter type to be selected when TouchWorks prompts for which encounter to enter the charges. This can be used to enable any non-appointment encounter type to be available to any user within Charge, when launching the encounter selector from within charge, only encounters with this flag are selectable.<br />
* '''Linked Appointment''' - indicates whether this encounter type is linked to an appointment from the practice management system. If so, Submit Enc Form tasks will be created once the patient has been arrived.<br />
<br />
==To Add New Encounter Types==<br />
* Login as '''TWAdmin'''.<br />
* Go to '''Dictionaries''', and select the '''Encounter Type''' Dictionary from the dropdown menu.<br />
* Click '''Add''' at the bottom of the screen.<br />
* Using the definitions above, fill out the information accordingly.<br />
* Click '''Save'''.<br />
[[Image:Encouter Type Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Encounter_Type&diff=15848Encounter Type2012-12-27T19:54:48Z<p>Tyler.Yoder: /* To Add New Encounter Types */</p>
<hr />
<div>__TOC__<br />
[[Category:Allscripts_Enterprise_EHR_Dictionaries]]<br />
== Description ==<br />
The Encounter Type dictionary is used to define the various types of encounters.<br />
All clinical data in TouchWorks must be tied to an encounter. Encounters<br />
can be created by appointments sent via the scheduling interface, notes<br />
created via call processing, and unsolicited results and transcriptions that come<br />
across the interface that are not already tied to an encounter.<br> <br />
The following encounter types are used within TouchWorks:<br><br />
<br />
*Appointment—default used for appointments that come across the scheduling interface; a specific encounter type can be entered in the Scheduling application and sent across the scheduling interface<br><br />
*Message—used for patient Notes copied from Mail <br />
*Other—used for results and transcriptions that come across the interface and create an encounter<br><br />
*Telephone Call—used for patient Notes copied from Call Processing <br />
<br />
This dictionary is called from:<br><br />
Note<br><br />
Encounter Form Selector<br><br />
Encounter Summary<br><br />
<br />
== Definition ==<br />
[[Image:Encounter_Type1.jpg]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
<br />
* '''Can Submit Charges for the Encounter Type''' -enables this encounter type to be selected when TouchWorks prompts for which encounter to enter the charges. This can be used to enable any non-appointment encounter type to be available to any user within Charge, when launching the encounter selector from within charge, only encounters with this flag are selectable.<br />
* '''Linked Appointment''' - indicates whether this encounter type is linked to an appointment from the practice management system. If so, Submit Enc Form tasks will be created once the patient has been arrived.<br />
<br />
==To Add New Encounter Types==<br />
* Login as '''TWAdmin'''.<br />
* Go to '''Dictionaries''', and select the '''Encounter Type''' Dictionary from the dropdown menu.<br />
* Click '''Add''' at the bottom of the scree.<br />
* Using the definitions above, fill out the information accordingly.<br />
* Click '''Save'''.<br />
[[Image:Encouter Type Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Encounter_Type&diff=15847Encounter Type2012-12-27T19:53:55Z<p>Tyler.Yoder: /* Description */</p>
<hr />
<div>__TOC__<br />
[[Category:Allscripts_Enterprise_EHR_Dictionaries]]<br />
== Description ==<br />
The Encounter Type dictionary is used to define the various types of encounters.<br />
All clinical data in TouchWorks must be tied to an encounter. Encounters<br />
can be created by appointments sent via the scheduling interface, notes<br />
created via call processing, and unsolicited results and transcriptions that come<br />
across the interface that are not already tied to an encounter.<br> <br />
The following encounter types are used within TouchWorks:<br><br />
<br />
*Appointment—default used for appointments that come across the scheduling interface; a specific encounter type can be entered in the Scheduling application and sent across the scheduling interface<br><br />
*Message—used for patient Notes copied from Mail <br />
*Other—used for results and transcriptions that come across the interface and create an encounter<br><br />
*Telephone Call—used for patient Notes copied from Call Processing <br />
<br />
This dictionary is called from:<br><br />
Note<br><br />
Encounter Form Selector<br><br />
Encounter Summary<br><br />
<br />
== Definition ==<br />
[[Image:Encounter_Type1.jpg]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
<br />
* '''Can Submit Charges for the Encounter Type''' -enables this encounter type to be selected when TouchWorks prompts for which encounter to enter the charges. This can be used to enable any non-appointment encounter type to be available to any user within Charge, when launching the encounter selector from within charge, only encounters with this flag are selectable.<br />
* '''Linked Appointment''' - indicates whether this encounter type is linked to an appointment from the practice management system. If so, Submit Enc Form tasks will be created once the patient has been arrived.<br />
<br />
==To Add New Encounter Types==<br />
* Login as '''TWAdmin'''.<br />
* Go to '''Dictionaries'''.<br />
* Select the '''Encounter Type''' Dictionary from the dropdown menu.<br />
* Click '''Add''' at the bottom of the scree.<br />
* Using the definitions above, fill out the information accordingly.<br />
* Click '''Save'''.<br />
[[Image:Encouter Type Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Allergen_Reaction_Details.jpg&diff=12282File:Allergen Reaction Details.jpg2011-12-30T19:40:07Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Allergen_Reaction&diff=12281Allergen Reaction2011-12-30T19:39:51Z<p>Tyler.Yoder: /* Description */</p>
<hr />
<div>__TOC__<br />
<br />
Back to [[TouchWorks V11 Dictionaries]]<br />
=Description=<br />
The Allergen Reaction dictionary contains the list of possible allergic reactions when adding an allergy to a patient. This dictionary is not enforced and can be added and edited as desired.<br />
<br />
To add a reaction to a patient profile, find the allergy in the ACI, right click on the allergy, and click edit. The allergen details window will appear, and a reactions box wll appear in this window. To add a reaction for the allergy selected, click on the binoculars.<br />
<br />
[[Image:Allergen Reaction Details.jpg]]<br />
<br />
=Definition=<br />
[[Image:Allergen Reaction.JPG]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=CPT4_Modifier&diff=12279CPT4 Modifier2011-12-30T19:21:47Z<p>Tyler.Yoder: </p>
<hr />
<div>Back to [http://wiki.galenhealthcare.com/Allscripts_Enterprise_EHR_Dictionaries Allscripts Enterprise EHR Dictionaries]<br />
<br />
<br />
== Description ==<br />
The CPT4 Modifier dictionary contains modifiers valid for E/M coding and<br />
procedures. The CCI Modifier checkbox enables that modifier to be a selectable<br />
option/modifier when the CCI Edits option has been enabled. This<br />
modifier would be selectable in the CCI edits page to apply if a CCI edit is<br />
detected by the edit tables, provided by 3M. The organization will need to synchronize changes between these<br />
two systems after the initial load. This dictionary is called from:<br />
TouchWorks Charge Encounter Form<br />
TouchWorks Charge PDA Encounter Form<br />
<br />
<br />
== Definition ==<br />
<br />
[[Image:CPT4_Modifier1.jpg]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
* '''Modifier Type'''- Defines whether the modifier can be used with a visit charge code, procedure charge code, or both.<br />
<br />
<br />
== Modifiers & Definitions ==<br />
<br />
*21 - Prolonged evaluation and management services<br />
*22 - Unusual procedureal services<br />
*23 - Unusual anesthesia<br />
*24 - Unrelated evaluation and management service by the same physician during a postoperative period<br />
*25 - Significant, separately identifiable E/M svc. by the same physician on same day of the procedure or other service<br />
*26 - Professional component<br />
*27 - Multiple outpatient hospital E/M encounters on the same date<br />
*32 - Mandated services<br />
*47 - Anesthesia by surgeon<br />
*50 - Bilateral procedure<br />
*51 - Multiple procedures<br />
*52 - Reduced services<br />
*53 - Discontinued procedure (in-patient/office only)<br />
*54 - Surgical care only<br />
*55 - Postoperative management only<br />
*56 - Preoperative management only<br />
*57 - Decision for surgery<br />
*58 - Staged or related procedure or service by the same physician during the postoperative period<br />
*59 - Distinct procedural service<br />
*62 - Two surgeons<br />
*63 - Procedure performed on infants less than 4 kg.<br />
*66 - Surgical team<br />
*73 - Discontinued out-patient hospital/ASC procedure prior to the administration of anesthesia<br />
*74 - Discontinued out-patient hospital/ASC procedure after administration of anesthesia<br />
*76 - Repeat procedure by same physician<br />
*77 - Repeat procedure by another physician<br />
*78 - Return to the operating room for a related procedure during the postoperative period<br />
*79 - Unrelated procedure or service by the same physician during the posoperative period<br />
*80 - Assistant surgeon<br />
*81 - Minimum assistant surgeon<br />
*82 - Assistant surgeon (when qualified resident surgeon not available)<br />
*90 - Reference (outside)laboratory<br />
*91 - Repeat clinical diagnostic laboratory test<br />
*AS - Physician assistant, nurse practioner or clinical nurse specialist srevices for assistant at surgery</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Create_Edit_Task_Views&diff=11313Create Edit Task Views2011-06-20T19:04:03Z<p>Tyler.Yoder: /* Add Tasks to Views - Edit/Create Views */</p>
<hr />
<div>==High Level Process for Upgrades==<br />
There are several new Tasks in v11<br />
# Review the new tasks that come delivered with v11<br />
#* Review default over due time settings and modify if desired<br />
# Review current task views and add new tasks to the appropriate views<br />
# Determine if any new task views need to be created<br />
#* Create new teams for new views if needed <br />
#* Assign any new task views to the appropriate users<br />
<br />
==Recommendations==<br />
* The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below <br />
* Create a task view for 'All tasks created by me today' Useful for finding misplaced tasks<br />
* Notify training team of work around for [[Authorize Order Tasks not in Patient Worklist]]<br />
* Create a task view for all 'Clinical Future Tasks'. This is useful when a clinical user (e.g. MA or RN) terminates and the user account is inactivated, yet the user still has inactive future tasks that will need to be worked by someone upon activation of the future tasks. <br />
* Create a 'Lab Order Feedback' task view for organizations who have a two-way lab interface. This view is useful for communicating necessary lab order changes between clinical and IT/IS staff when lab results are stuck in the interface.<br />
<br />
==Review New V11 Tasks==<br />
* A Microsoft Excel spreadsheet describing all tasks is available from the Allscripts Knowledge Base: kb.allscripts.com doc # 3350. It does not indicate which tasks are new in v11<br />
* The spreadsheet can be filtered or sorted by module to focus on only the modules the client has<br />
* The following link goes to a Wiki version sorted by Module: [[v11 Tasks]]<br />
* See also [[11.x to 11.2 Incorporate new 11.2 Tasks]]<br />
<br />
==Edit Tasks==<br />
Tasks come delivered with preset overdue limits and other settings and most should not need modification.<br />
<br />
Dictionaries > Task Name dictionary<br />
<br />
The following settings can be modified:<br />
<br />
'''Task Action''' Grayed out in v11.1.7<br />
<br />
'''Delegate''' Check this box to prevent the task type from showing up in "My Active Tasks". <br />
This is useful for tasks that are not going to be worked by a provider, but instead by a nurse or an MA. An example would be "Call in Failed Rx". It is important to remember to build a task view to capture these delegated tasks, or else, they will not be seen by anyone.<br />
<br />
'''Default OverDue Time By priority'''<br />
* Default time until task is flagged as overdue. A different time can set for each priority level.<br />
* In the example below, the task 'Call Back' will become overdue if not completed within '1 Day' (24 hours). If the user creating a 'Call Back' task selects the Priority 'ASAP' the task will become overdue in 6 hours. If 'Urgent', 60 minutes.<br />
* The times are defaults and can be edited by the user when creating individual tasks<br />
[[Image:Edit Task.jpg]]<br />
<br />
'''Copy To Note Options'''<br />
<br />
Available for the following Tasks:<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action '''<br />
| align="center" style="background:#f0f0f0;"|'''Task Name'''<br />
|-<br />
| Miscellaneous||Call Back<br />
|-<br />
| Miscellaneous||Follow Up<br />
|-<br />
| Miscellaneous||Health Maintenance Alert<br />
|-<br />
| Miscellaneous||Hospital Calls<br />
|-<br />
| Process Note||Medical Problem or Complaint<br />
|-<br />
| Miscellaneous||Medication Renewal<br />
|-<br />
| Miscellaneous||Patient Arrived<br />
|-<br />
| Miscellaneous||Personal<br />
|-<br />
| Process Note||Referral Follow Up<br />
|-<br />
| Process Result||Result Follow Up<br />
|-<br />
| <br />
|}<br />
<br />
* Complete the Task when Copy to Note - This option will automatically complete the task once it has been copied to note.<br />
* Default Encounter Type - Complete this option to select which encounter type the newly created note will attach to when "copy to note" is checked for a given task type<br />
* Default Note Type - This option will automatically open a pre-determined note type when "copy to note" is checked for a given task type<br />
<br />
==Task Views Overview==<br />
* Enterprise task views can be created and assigned to multiple users.<br />
* One or more personal views can be created for each individual user.<br />
* A user can access their personal and/or assigned enterprise views via dropdown.<br />
* One of these views must be designated as the default display. <br />
* Enterprise views and default views should be created and assigned based on roles.<br />
* Personal views should be used only to accommodate a user's personal preferences.<br />
<br />
==Add Tasks to Views - Edit/Create Views==<br />
# 'TWAdmin' VTB > 'Task Admin' HTB ><br />
# Select 'Enterprise Views' or 'Personal Views' tab<br />
# The 'View:' field displays the name of the task view being created, edited or deleted.<br />
# To edit or delete existing views, click 'Go' to see all existing views and select a view to edit. To find a specific view, type the ''beginning'' of the name into the 'View' field and click 'Go'.<br />
# To create a new view, click 'New'. '''One should note that once the view is named and saved, the name cannot be changed.'''<br />
# Always enter a description of the view.<br />
[[Image:start.jpg]]<br />
<br />
===Configure one or more filters to limit the tasks displayed===<br />
Filters can be utilized to return smaller lists of tasks related to specific activities and roles. These filters are how the system will determine which specific tasks to show in a task view. For example, to isolate "Verify Result" tasks for a given provider, filter by "Assigned to", select the provider name, arrow over, then filter by the task type "verify results", arrow over then filter by task status of "active" and "in progress" to see all Verify Results tasks that are Active or In Progress for the referenced provider. By utilizing the filter function, larger task lists are broken down into smaller more manageable lists for the end user<br />
<br />
#Use the left and right buttons to add or remove filters from the view<br />
#Multiple values can be selected for the same filter<br />
#:[[Image:multiple values.jpg]]<br />
<br />
'''Filters:'''<br />
<br />
*'''Assigned To''' displays only tasks assigned to the user or users selected<br />
**The Team option will return tasks assigned to a particular team<br />
**The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below.<br />
<br />
*'''Created''' displays only tasks created on a certain day or range of days.<br />
<br />
*'''Created By''' displays only tasks created by the user or users selected.<br />
<br />
*'''Delegated''' displays only delegated tasks. Example: The view Cardiology Billing might be Created By = [select cardiology providers], Delegated = Y, Task = Adjust Charges (as long as this task type has the "delegated" box checked, all "Adjust Charges" tasks will show up in the view for the providers selected in the view.<br />
<br />
*'''Overdue''' displays only overdue tasks.<br />
<br />
*'''Patient''' displays only tasks related to the patient in context or to an alphabetical range of patients<br />
<br />
*'''Priority''' displays only tasks with the selected priority or priorities.<br />
<br />
*'''Status''' displays only tasks with the selected status or statuses.<br />
<br />
When filtering for tasks with status "Active", "In Progress" must also be selected because "In Progress" tasks are active tasks that are currently being worked.<br />
<br />
*'''Task''' displays only the task types selected.<br />
<br />
===Configure one or more sorts to organize the tasks displayed===<br />
Note: Sorts will be executed in order.<br />
<br />
==Assign Views to Users==<br />
This can be done manually or through SSMT. When assigning a large amount of views SSMT is the preferred method.<br />
<br />
===Manual===<br />
Assign view to 1 user and workflow test before assigning to multiple users <br />
# Select 'Manage Personal' tab<br />
# Select a user from the 'Views For:' dropdown or click 'All' to search all users.(who are the users in the dropdown?)<br />
#:[[Image:select user.jpg]]<br />
# To Add enterprise task views to the user, select the view in the lower table and click 'Add to My Views'.<br />
# To Remove views from a user, select the view in the upper table and click "Remove"<br />
#* If the selected view is a personal view, the system will display a warning before deleting the view.<br />
# Select the default view for the user by selecting a view from the upper table and clicking 'Set as Default'.<br />
#* The view selected as default cannot be removed. To remove the default view, make another view the default.<br />
#:[[Image:taskg.jpg]]<br />
<br />
===SSMT===<br />
Task views can be assigned to multiple users using SSMT Category: 'Task View-Users'<br />
*'*HDRAUsername' is the user (?)<br />
*'Name' is the task view<br />
*'Task Owner' is (?)<br />
*'IsDefault' must be Y or N. Only one row per user can be Y<br />
*'Create (Y N)' must be set to Y for added rows<br />
To copy task views from one user to another<br />
#Sort the exported list by '*HDRAUsername'<br />
#Identify a user who already has the task view or views to be assigned to the new user. This will usually be a user with the same role.<br />
#Copy the rows for the views to be assigned<br />
#Do not copy rows for views already assigned to the new user (?)<br />
#Add the copied rows to the spreadsheet<br />
#Change '*HDRAUsername' to the new username<br />
#If 'Task Owner' = username, change it to the new user name<br />
#Change 'Create (Y N)' to Y only for the rows that were added<br />
<br />
For SSMT basics see [[SSMT]]<br />
<br />
==Create Teams as Users==<br />
The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams.<br />
<br />
The advantage to this approach has to do with the way the drop down lists work on the New Task page. The team drop down shows all entries in the Team dictionary. The user drop down is a favorites list and only shows the values that have been searched for by that user. If you have the same set of teams at each site, it’ll turn into quite a long list of teams and be very difficult to select. The only time we suggest using teams is for central teams that are used system wide. Other than that it’s much better to use the user concept and define a naming convention that is consistent and easy to train users on how to search for their specific teams.<br />
<br />
===High Level Process===<br />
Example: New World Health has a dermatology practice with three front desk staff.<br />
# Create false user 'NWH Dermatology,Front Desk'<br />
# Create task view 'Dermatology Front Desk'. Set filter 'Assigned To' to 'NWH Dermatology,Front Desk'<br />
# Assign task view 'Dermatology Front Desk' to the three front desk staff<br />
# Add user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk.<br />
<br />
===Detailed Steps===<br />
'''Create False User'''<br />
# VTB: TWUser Admin > HTB User Admin<br />
# User Type: User<br />
# Last Name: NWH Dermatology<br />
# First Name: Front Desk<br />
# Email: email@email.com<br />
# Organization: Select the Organization the (team?) belongs to<br />
# User Name: NWHDermatologyFrontDesk (no spaces)<br />
# Default Site: Select the Site the (team?) belongs to<br />
# Password: password<br />
# Profession: Other<br />
# Save<br />
<br />
'''Create Task View'''<br />
# VTB: Task Admin > HTB Enterprise Views<br />
# Click 'New'.<br />
# View: Dermatology Front Desk<br />
# Description: All tasks assigned to the false user 'NWH Dermatology,Front Desk'<br />
# Assigned To: User: NWH Dermatology,Front Desk<br />
# Status: Active, In Progress<br />
# Save<br />
<br />
'''Assign View to Team'''<br />
<br />
Assign view: 'Dermatology Front Desk' to the three front desk staff<br />
<br />
(Copy and edit [[#Assign Views to Users|Assign Views to Users]] to make specific to Creating Teams as Users and specific to this example)<br />
<br />
'''Add False User to Favorites'''<br />
<br />
Add the user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk<br />
# Navigate to the Physician Admin Menu by using the drop-down in the top right hand corner of the screen<br />
#:[[Image:Patpref1.jpg]]<br />
# Expand the “By Category” Menu<br />
#:[[Image:Patpref2.jpg]]<br />
# Select Favorites<br />
#:[[Image:Patpref3.jpg]]<br />
# Expand 'User Favorites'. ''This is the list of people users choose from when assigning tasks''<br />
#:[[Image:User Favorites.jpg]]<br />
# Select 'Master Favorites' if all members of a specialty (Dermatology) will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select Group: Dermatology (Specialties must be mapped to Groups?)<br />
#:[[Image:By Specialty.jpg]]<br />
# Select 'Personal Favorites' if only some users will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select a user who will need to assign tasks from the 'For:' dropdown (Group should be grayed out when personal is selected?)<br />
#:[[Image:By User.jpg]]<br />
# Add the user 'NWH Dermatology,Front Desk' to 'User Favorites' list for the selected user<br />
#* Search for the user 'NWH Dermatology,Front Desk'<br />
#* Click on the user 'NWH Dermatology,Front Desk' in the left pane to add it to the user favorites in the right pane<br />
#:[[Image:Add Team to User Favorites.jpg]]<br />
#Save<br />
#Saved Successfully will appear for a second in the upper right hand corner of your screen<br />
#:[[Image:Patpref9.jpg]]<br />
<br />
'''Test'''<br />
# Login as a user who needs to assign tasks to the dermatology front desk team<br />
# Create a new task and assign it to NWH Dermatology,Front Desk<br />
# Login as a member of the dermatology front desk team, navigate to tasks and select view 'Dermatology Front Desk'<br />
# The task should be present</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Create_Edit_Task_Views&diff=11312Create Edit Task Views2011-06-20T19:03:47Z<p>Tyler.Yoder: /* Add Tasks to Views - Edit/Create Views */</p>
<hr />
<div>==High Level Process for Upgrades==<br />
There are several new Tasks in v11<br />
# Review the new tasks that come delivered with v11<br />
#* Review default over due time settings and modify if desired<br />
# Review current task views and add new tasks to the appropriate views<br />
# Determine if any new task views need to be created<br />
#* Create new teams for new views if needed <br />
#* Assign any new task views to the appropriate users<br />
<br />
==Recommendations==<br />
* The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below <br />
* Create a task view for 'All tasks created by me today' Useful for finding misplaced tasks<br />
* Notify training team of work around for [[Authorize Order Tasks not in Patient Worklist]]<br />
* Create a task view for all 'Clinical Future Tasks'. This is useful when a clinical user (e.g. MA or RN) terminates and the user account is inactivated, yet the user still has inactive future tasks that will need to be worked by someone upon activation of the future tasks. <br />
* Create a 'Lab Order Feedback' task view for organizations who have a two-way lab interface. This view is useful for communicating necessary lab order changes between clinical and IT/IS staff when lab results are stuck in the interface.<br />
<br />
==Review New V11 Tasks==<br />
* A Microsoft Excel spreadsheet describing all tasks is available from the Allscripts Knowledge Base: kb.allscripts.com doc # 3350. It does not indicate which tasks are new in v11<br />
* The spreadsheet can be filtered or sorted by module to focus on only the modules the client has<br />
* The following link goes to a Wiki version sorted by Module: [[v11 Tasks]]<br />
* See also [[11.x to 11.2 Incorporate new 11.2 Tasks]]<br />
<br />
==Edit Tasks==<br />
Tasks come delivered with preset overdue limits and other settings and most should not need modification.<br />
<br />
Dictionaries > Task Name dictionary<br />
<br />
The following settings can be modified:<br />
<br />
'''Task Action''' Grayed out in v11.1.7<br />
<br />
'''Delegate''' Check this box to prevent the task type from showing up in "My Active Tasks". <br />
This is useful for tasks that are not going to be worked by a provider, but instead by a nurse or an MA. An example would be "Call in Failed Rx". It is important to remember to build a task view to capture these delegated tasks, or else, they will not be seen by anyone.<br />
<br />
'''Default OverDue Time By priority'''<br />
* Default time until task is flagged as overdue. A different time can set for each priority level.<br />
* In the example below, the task 'Call Back' will become overdue if not completed within '1 Day' (24 hours). If the user creating a 'Call Back' task selects the Priority 'ASAP' the task will become overdue in 6 hours. If 'Urgent', 60 minutes.<br />
* The times are defaults and can be edited by the user when creating individual tasks<br />
[[Image:Edit Task.jpg]]<br />
<br />
'''Copy To Note Options'''<br />
<br />
Available for the following Tasks:<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action '''<br />
| align="center" style="background:#f0f0f0;"|'''Task Name'''<br />
|-<br />
| Miscellaneous||Call Back<br />
|-<br />
| Miscellaneous||Follow Up<br />
|-<br />
| Miscellaneous||Health Maintenance Alert<br />
|-<br />
| Miscellaneous||Hospital Calls<br />
|-<br />
| Process Note||Medical Problem or Complaint<br />
|-<br />
| Miscellaneous||Medication Renewal<br />
|-<br />
| Miscellaneous||Patient Arrived<br />
|-<br />
| Miscellaneous||Personal<br />
|-<br />
| Process Note||Referral Follow Up<br />
|-<br />
| Process Result||Result Follow Up<br />
|-<br />
| <br />
|}<br />
<br />
* Complete the Task when Copy to Note - This option will automatically complete the task once it has been copied to note.<br />
* Default Encounter Type - Complete this option to select which encounter type the newly created note will attach to when "copy to note" is checked for a given task type<br />
* Default Note Type - This option will automatically open a pre-determined note type when "copy to note" is checked for a given task type<br />
<br />
==Task Views Overview==<br />
* Enterprise task views can be created and assigned to multiple users.<br />
* One or more personal views can be created for each individual user.<br />
* A user can access their personal and/or assigned enterprise views via dropdown.<br />
* One of these views must be designated as the default display. <br />
* Enterprise views and default views should be created and assigned based on roles.<br />
* Personal views should be used only to accommodate a user's personal preferences.<br />
<br />
==Add Tasks to Views - Edit/Create Views==<br />
# 'TWAdmin' VTB > 'Task Admin' HTB ><br />
# Select 'Enterprise Views' or 'Personal Views' tab<br />
# The 'View:' field displays the name of the task view being created, edited or deleted.<br />
# To edit or delete existing views, click 'Go' to see all existing views and select a view to edit. To find a specific view, type the ''beginning'' of the name into the 'View' field and click 'Go'.<br />
# To create a new view, click 'New'. '''One should note that once the view is named and saved, the name cannot be changed.'''# Always enter a description of the view.<br />
[[Image:start.jpg]]<br />
<br />
===Configure one or more filters to limit the tasks displayed===<br />
Filters can be utilized to return smaller lists of tasks related to specific activities and roles. These filters are how the system will determine which specific tasks to show in a task view. For example, to isolate "Verify Result" tasks for a given provider, filter by "Assigned to", select the provider name, arrow over, then filter by the task type "verify results", arrow over then filter by task status of "active" and "in progress" to see all Verify Results tasks that are Active or In Progress for the referenced provider. By utilizing the filter function, larger task lists are broken down into smaller more manageable lists for the end user<br />
<br />
#Use the left and right buttons to add or remove filters from the view<br />
#Multiple values can be selected for the same filter<br />
#:[[Image:multiple values.jpg]]<br />
<br />
'''Filters:'''<br />
<br />
*'''Assigned To''' displays only tasks assigned to the user or users selected<br />
**The Team option will return tasks assigned to a particular team<br />
**The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below.<br />
<br />
*'''Created''' displays only tasks created on a certain day or range of days.<br />
<br />
*'''Created By''' displays only tasks created by the user or users selected.<br />
<br />
*'''Delegated''' displays only delegated tasks. Example: The view Cardiology Billing might be Created By = [select cardiology providers], Delegated = Y, Task = Adjust Charges (as long as this task type has the "delegated" box checked, all "Adjust Charges" tasks will show up in the view for the providers selected in the view.<br />
<br />
*'''Overdue''' displays only overdue tasks.<br />
<br />
*'''Patient''' displays only tasks related to the patient in context or to an alphabetical range of patients<br />
<br />
*'''Priority''' displays only tasks with the selected priority or priorities.<br />
<br />
*'''Status''' displays only tasks with the selected status or statuses.<br />
<br />
When filtering for tasks with status "Active", "In Progress" must also be selected because "In Progress" tasks are active tasks that are currently being worked.<br />
<br />
*'''Task''' displays only the task types selected.<br />
<br />
===Configure one or more sorts to organize the tasks displayed===<br />
Note: Sorts will be executed in order.<br />
<br />
==Assign Views to Users==<br />
This can be done manually or through SSMT. When assigning a large amount of views SSMT is the preferred method.<br />
<br />
===Manual===<br />
Assign view to 1 user and workflow test before assigning to multiple users <br />
# Select 'Manage Personal' tab<br />
# Select a user from the 'Views For:' dropdown or click 'All' to search all users.(who are the users in the dropdown?)<br />
#:[[Image:select user.jpg]]<br />
# To Add enterprise task views to the user, select the view in the lower table and click 'Add to My Views'.<br />
# To Remove views from a user, select the view in the upper table and click "Remove"<br />
#* If the selected view is a personal view, the system will display a warning before deleting the view.<br />
# Select the default view for the user by selecting a view from the upper table and clicking 'Set as Default'.<br />
#* The view selected as default cannot be removed. To remove the default view, make another view the default.<br />
#:[[Image:taskg.jpg]]<br />
<br />
===SSMT===<br />
Task views can be assigned to multiple users using SSMT Category: 'Task View-Users'<br />
*'*HDRAUsername' is the user (?)<br />
*'Name' is the task view<br />
*'Task Owner' is (?)<br />
*'IsDefault' must be Y or N. Only one row per user can be Y<br />
*'Create (Y N)' must be set to Y for added rows<br />
To copy task views from one user to another<br />
#Sort the exported list by '*HDRAUsername'<br />
#Identify a user who already has the task view or views to be assigned to the new user. This will usually be a user with the same role.<br />
#Copy the rows for the views to be assigned<br />
#Do not copy rows for views already assigned to the new user (?)<br />
#Add the copied rows to the spreadsheet<br />
#Change '*HDRAUsername' to the new username<br />
#If 'Task Owner' = username, change it to the new user name<br />
#Change 'Create (Y N)' to Y only for the rows that were added<br />
<br />
For SSMT basics see [[SSMT]]<br />
<br />
==Create Teams as Users==<br />
The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams.<br />
<br />
The advantage to this approach has to do with the way the drop down lists work on the New Task page. The team drop down shows all entries in the Team dictionary. The user drop down is a favorites list and only shows the values that have been searched for by that user. If you have the same set of teams at each site, it’ll turn into quite a long list of teams and be very difficult to select. The only time we suggest using teams is for central teams that are used system wide. Other than that it’s much better to use the user concept and define a naming convention that is consistent and easy to train users on how to search for their specific teams.<br />
<br />
===High Level Process===<br />
Example: New World Health has a dermatology practice with three front desk staff.<br />
# Create false user 'NWH Dermatology,Front Desk'<br />
# Create task view 'Dermatology Front Desk'. Set filter 'Assigned To' to 'NWH Dermatology,Front Desk'<br />
# Assign task view 'Dermatology Front Desk' to the three front desk staff<br />
# Add user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk.<br />
<br />
===Detailed Steps===<br />
'''Create False User'''<br />
# VTB: TWUser Admin > HTB User Admin<br />
# User Type: User<br />
# Last Name: NWH Dermatology<br />
# First Name: Front Desk<br />
# Email: email@email.com<br />
# Organization: Select the Organization the (team?) belongs to<br />
# User Name: NWHDermatologyFrontDesk (no spaces)<br />
# Default Site: Select the Site the (team?) belongs to<br />
# Password: password<br />
# Profession: Other<br />
# Save<br />
<br />
'''Create Task View'''<br />
# VTB: Task Admin > HTB Enterprise Views<br />
# Click 'New'.<br />
# View: Dermatology Front Desk<br />
# Description: All tasks assigned to the false user 'NWH Dermatology,Front Desk'<br />
# Assigned To: User: NWH Dermatology,Front Desk<br />
# Status: Active, In Progress<br />
# Save<br />
<br />
'''Assign View to Team'''<br />
<br />
Assign view: 'Dermatology Front Desk' to the three front desk staff<br />
<br />
(Copy and edit [[#Assign Views to Users|Assign Views to Users]] to make specific to Creating Teams as Users and specific to this example)<br />
<br />
'''Add False User to Favorites'''<br />
<br />
Add the user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk<br />
# Navigate to the Physician Admin Menu by using the drop-down in the top right hand corner of the screen<br />
#:[[Image:Patpref1.jpg]]<br />
# Expand the “By Category” Menu<br />
#:[[Image:Patpref2.jpg]]<br />
# Select Favorites<br />
#:[[Image:Patpref3.jpg]]<br />
# Expand 'User Favorites'. ''This is the list of people users choose from when assigning tasks''<br />
#:[[Image:User Favorites.jpg]]<br />
# Select 'Master Favorites' if all members of a specialty (Dermatology) will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select Group: Dermatology (Specialties must be mapped to Groups?)<br />
#:[[Image:By Specialty.jpg]]<br />
# Select 'Personal Favorites' if only some users will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select a user who will need to assign tasks from the 'For:' dropdown (Group should be grayed out when personal is selected?)<br />
#:[[Image:By User.jpg]]<br />
# Add the user 'NWH Dermatology,Front Desk' to 'User Favorites' list for the selected user<br />
#* Search for the user 'NWH Dermatology,Front Desk'<br />
#* Click on the user 'NWH Dermatology,Front Desk' in the left pane to add it to the user favorites in the right pane<br />
#:[[Image:Add Team to User Favorites.jpg]]<br />
#Save<br />
#Saved Successfully will appear for a second in the upper right hand corner of your screen<br />
#:[[Image:Patpref9.jpg]]<br />
<br />
'''Test'''<br />
# Login as a user who needs to assign tasks to the dermatology front desk team<br />
# Create a new task and assign it to NWH Dermatology,Front Desk<br />
# Login as a member of the dermatology front desk team, navigate to tasks and select view 'Dermatology Front Desk'<br />
# The task should be present</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Create_Edit_Task_Views&diff=11311Create Edit Task Views2011-06-20T19:02:56Z<p>Tyler.Yoder: /* Add Tasks to Views - Edit/Create Views */</p>
<hr />
<div>==High Level Process for Upgrades==<br />
There are several new Tasks in v11<br />
# Review the new tasks that come delivered with v11<br />
#* Review default over due time settings and modify if desired<br />
# Review current task views and add new tasks to the appropriate views<br />
# Determine if any new task views need to be created<br />
#* Create new teams for new views if needed <br />
#* Assign any new task views to the appropriate users<br />
<br />
==Recommendations==<br />
* The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below <br />
* Create a task view for 'All tasks created by me today' Useful for finding misplaced tasks<br />
* Notify training team of work around for [[Authorize Order Tasks not in Patient Worklist]]<br />
* Create a task view for all 'Clinical Future Tasks'. This is useful when a clinical user (e.g. MA or RN) terminates and the user account is inactivated, yet the user still has inactive future tasks that will need to be worked by someone upon activation of the future tasks. <br />
* Create a 'Lab Order Feedback' task view for organizations who have a two-way lab interface. This view is useful for communicating necessary lab order changes between clinical and IT/IS staff when lab results are stuck in the interface.<br />
<br />
==Review New V11 Tasks==<br />
* A Microsoft Excel spreadsheet describing all tasks is available from the Allscripts Knowledge Base: kb.allscripts.com doc # 3350. It does not indicate which tasks are new in v11<br />
* The spreadsheet can be filtered or sorted by module to focus on only the modules the client has<br />
* The following link goes to a Wiki version sorted by Module: [[v11 Tasks]]<br />
* See also [[11.x to 11.2 Incorporate new 11.2 Tasks]]<br />
<br />
==Edit Tasks==<br />
Tasks come delivered with preset overdue limits and other settings and most should not need modification.<br />
<br />
Dictionaries > Task Name dictionary<br />
<br />
The following settings can be modified:<br />
<br />
'''Task Action''' Grayed out in v11.1.7<br />
<br />
'''Delegate''' Check this box to prevent the task type from showing up in "My Active Tasks". <br />
This is useful for tasks that are not going to be worked by a provider, but instead by a nurse or an MA. An example would be "Call in Failed Rx". It is important to remember to build a task view to capture these delegated tasks, or else, they will not be seen by anyone.<br />
<br />
'''Default OverDue Time By priority'''<br />
* Default time until task is flagged as overdue. A different time can set for each priority level.<br />
* In the example below, the task 'Call Back' will become overdue if not completed within '1 Day' (24 hours). If the user creating a 'Call Back' task selects the Priority 'ASAP' the task will become overdue in 6 hours. If 'Urgent', 60 minutes.<br />
* The times are defaults and can be edited by the user when creating individual tasks<br />
[[Image:Edit Task.jpg]]<br />
<br />
'''Copy To Note Options'''<br />
<br />
Available for the following Tasks:<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action '''<br />
| align="center" style="background:#f0f0f0;"|'''Task Name'''<br />
|-<br />
| Miscellaneous||Call Back<br />
|-<br />
| Miscellaneous||Follow Up<br />
|-<br />
| Miscellaneous||Health Maintenance Alert<br />
|-<br />
| Miscellaneous||Hospital Calls<br />
|-<br />
| Process Note||Medical Problem or Complaint<br />
|-<br />
| Miscellaneous||Medication Renewal<br />
|-<br />
| Miscellaneous||Patient Arrived<br />
|-<br />
| Miscellaneous||Personal<br />
|-<br />
| Process Note||Referral Follow Up<br />
|-<br />
| Process Result||Result Follow Up<br />
|-<br />
| <br />
|}<br />
<br />
* Complete the Task when Copy to Note - This option will automatically complete the task once it has been copied to note.<br />
* Default Encounter Type - Complete this option to select which encounter type the newly created note will attach to when "copy to note" is checked for a given task type<br />
* Default Note Type - This option will automatically open a pre-determined note type when "copy to note" is checked for a given task type<br />
<br />
==Task Views Overview==<br />
* Enterprise task views can be created and assigned to multiple users.<br />
* One or more personal views can be created for each individual user.<br />
* A user can access their personal and/or assigned enterprise views via dropdown.<br />
* One of these views must be designated as the default display. <br />
* Enterprise views and default views should be created and assigned based on roles.<br />
* Personal views should be used only to accommodate a user's personal preferences.<br />
<br />
==Add Tasks to Views - Edit/Create Views==<br />
# 'TWAdmin' VTB > 'Task Admin' HTB ><br />
# Select 'Enterprise Views' or 'Personal Views' tab<br />
# The 'View:' field displays the name of the task view being created, edited or deleted.<br />
# To edit or delete existing views, click 'Go' to see all existing views and select a view to edit. To find a specific view, type the ''beginning'' of the name into the 'View' field and click 'Go'.<br />
# To create a new view, click 'New'. One should note that once the view is named and saved, the name cannot be changed.<br />
# Always enter a description of the view.<br />
[[Image:start.jpg]]<br />
<br />
===Configure one or more filters to limit the tasks displayed===<br />
Filters can be utilized to return smaller lists of tasks related to specific activities and roles. These filters are how the system will determine which specific tasks to show in a task view. For example, to isolate "Verify Result" tasks for a given provider, filter by "Assigned to", select the provider name, arrow over, then filter by the task type "verify results", arrow over then filter by task status of "active" and "in progress" to see all Verify Results tasks that are Active or In Progress for the referenced provider. By utilizing the filter function, larger task lists are broken down into smaller more manageable lists for the end user<br />
<br />
#Use the left and right buttons to add or remove filters from the view<br />
#Multiple values can be selected for the same filter<br />
#:[[Image:multiple values.jpg]]<br />
<br />
'''Filters:'''<br />
<br />
*'''Assigned To''' displays only tasks assigned to the user or users selected<br />
**The Team option will return tasks assigned to a particular team<br />
**The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below.<br />
<br />
*'''Created''' displays only tasks created on a certain day or range of days.<br />
<br />
*'''Created By''' displays only tasks created by the user or users selected.<br />
<br />
*'''Delegated''' displays only delegated tasks. Example: The view Cardiology Billing might be Created By = [select cardiology providers], Delegated = Y, Task = Adjust Charges (as long as this task type has the "delegated" box checked, all "Adjust Charges" tasks will show up in the view for the providers selected in the view.<br />
<br />
*'''Overdue''' displays only overdue tasks.<br />
<br />
*'''Patient''' displays only tasks related to the patient in context or to an alphabetical range of patients<br />
<br />
*'''Priority''' displays only tasks with the selected priority or priorities.<br />
<br />
*'''Status''' displays only tasks with the selected status or statuses.<br />
<br />
When filtering for tasks with status "Active", "In Progress" must also be selected because "In Progress" tasks are active tasks that are currently being worked.<br />
<br />
*'''Task''' displays only the task types selected.<br />
<br />
===Configure one or more sorts to organize the tasks displayed===<br />
Note: Sorts will be executed in order.<br />
<br />
==Assign Views to Users==<br />
This can be done manually or through SSMT. When assigning a large amount of views SSMT is the preferred method.<br />
<br />
===Manual===<br />
Assign view to 1 user and workflow test before assigning to multiple users <br />
# Select 'Manage Personal' tab<br />
# Select a user from the 'Views For:' dropdown or click 'All' to search all users.(who are the users in the dropdown?)<br />
#:[[Image:select user.jpg]]<br />
# To Add enterprise task views to the user, select the view in the lower table and click 'Add to My Views'.<br />
# To Remove views from a user, select the view in the upper table and click "Remove"<br />
#* If the selected view is a personal view, the system will display a warning before deleting the view.<br />
# Select the default view for the user by selecting a view from the upper table and clicking 'Set as Default'.<br />
#* The view selected as default cannot be removed. To remove the default view, make another view the default.<br />
#:[[Image:taskg.jpg]]<br />
<br />
===SSMT===<br />
Task views can be assigned to multiple users using SSMT Category: 'Task View-Users'<br />
*'*HDRAUsername' is the user (?)<br />
*'Name' is the task view<br />
*'Task Owner' is (?)<br />
*'IsDefault' must be Y or N. Only one row per user can be Y<br />
*'Create (Y N)' must be set to Y for added rows<br />
To copy task views from one user to another<br />
#Sort the exported list by '*HDRAUsername'<br />
#Identify a user who already has the task view or views to be assigned to the new user. This will usually be a user with the same role.<br />
#Copy the rows for the views to be assigned<br />
#Do not copy rows for views already assigned to the new user (?)<br />
#Add the copied rows to the spreadsheet<br />
#Change '*HDRAUsername' to the new username<br />
#If 'Task Owner' = username, change it to the new user name<br />
#Change 'Create (Y N)' to Y only for the rows that were added<br />
<br />
For SSMT basics see [[SSMT]]<br />
<br />
==Create Teams as Users==<br />
The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams.<br />
<br />
The advantage to this approach has to do with the way the drop down lists work on the New Task page. The team drop down shows all entries in the Team dictionary. The user drop down is a favorites list and only shows the values that have been searched for by that user. If you have the same set of teams at each site, it’ll turn into quite a long list of teams and be very difficult to select. The only time we suggest using teams is for central teams that are used system wide. Other than that it’s much better to use the user concept and define a naming convention that is consistent and easy to train users on how to search for their specific teams.<br />
<br />
===High Level Process===<br />
Example: New World Health has a dermatology practice with three front desk staff.<br />
# Create false user 'NWH Dermatology,Front Desk'<br />
# Create task view 'Dermatology Front Desk'. Set filter 'Assigned To' to 'NWH Dermatology,Front Desk'<br />
# Assign task view 'Dermatology Front Desk' to the three front desk staff<br />
# Add user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk.<br />
<br />
===Detailed Steps===<br />
'''Create False User'''<br />
# VTB: TWUser Admin > HTB User Admin<br />
# User Type: User<br />
# Last Name: NWH Dermatology<br />
# First Name: Front Desk<br />
# Email: email@email.com<br />
# Organization: Select the Organization the (team?) belongs to<br />
# User Name: NWHDermatologyFrontDesk (no spaces)<br />
# Default Site: Select the Site the (team?) belongs to<br />
# Password: password<br />
# Profession: Other<br />
# Save<br />
<br />
'''Create Task View'''<br />
# VTB: Task Admin > HTB Enterprise Views<br />
# Click 'New'.<br />
# View: Dermatology Front Desk<br />
# Description: All tasks assigned to the false user 'NWH Dermatology,Front Desk'<br />
# Assigned To: User: NWH Dermatology,Front Desk<br />
# Status: Active, In Progress<br />
# Save<br />
<br />
'''Assign View to Team'''<br />
<br />
Assign view: 'Dermatology Front Desk' to the three front desk staff<br />
<br />
(Copy and edit [[#Assign Views to Users|Assign Views to Users]] to make specific to Creating Teams as Users and specific to this example)<br />
<br />
'''Add False User to Favorites'''<br />
<br />
Add the user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk<br />
# Navigate to the Physician Admin Menu by using the drop-down in the top right hand corner of the screen<br />
#:[[Image:Patpref1.jpg]]<br />
# Expand the “By Category” Menu<br />
#:[[Image:Patpref2.jpg]]<br />
# Select Favorites<br />
#:[[Image:Patpref3.jpg]]<br />
# Expand 'User Favorites'. ''This is the list of people users choose from when assigning tasks''<br />
#:[[Image:User Favorites.jpg]]<br />
# Select 'Master Favorites' if all members of a specialty (Dermatology) will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select Group: Dermatology (Specialties must be mapped to Groups?)<br />
#:[[Image:By Specialty.jpg]]<br />
# Select 'Personal Favorites' if only some users will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select a user who will need to assign tasks from the 'For:' dropdown (Group should be grayed out when personal is selected?)<br />
#:[[Image:By User.jpg]]<br />
# Add the user 'NWH Dermatology,Front Desk' to 'User Favorites' list for the selected user<br />
#* Search for the user 'NWH Dermatology,Front Desk'<br />
#* Click on the user 'NWH Dermatology,Front Desk' in the left pane to add it to the user favorites in the right pane<br />
#:[[Image:Add Team to User Favorites.jpg]]<br />
#Save<br />
#Saved Successfully will appear for a second in the upper right hand corner of your screen<br />
#:[[Image:Patpref9.jpg]]<br />
<br />
'''Test'''<br />
# Login as a user who needs to assign tasks to the dermatology front desk team<br />
# Create a new task and assign it to NWH Dermatology,Front Desk<br />
# Login as a member of the dermatology front desk team, navigate to tasks and select view 'Dermatology Front Desk'<br />
# The task should be present</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Create_Edit_Task_Views&diff=11310Create Edit Task Views2011-06-20T18:59:51Z<p>Tyler.Yoder: </p>
<hr />
<div>==High Level Process for Upgrades==<br />
There are several new Tasks in v11<br />
# Review the new tasks that come delivered with v11<br />
#* Review default over due time settings and modify if desired<br />
# Review current task views and add new tasks to the appropriate views<br />
# Determine if any new task views need to be created<br />
#* Create new teams for new views if needed <br />
#* Assign any new task views to the appropriate users<br />
<br />
==Recommendations==<br />
* The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below <br />
* Create a task view for 'All tasks created by me today' Useful for finding misplaced tasks<br />
* Notify training team of work around for [[Authorize Order Tasks not in Patient Worklist]]<br />
* Create a task view for all 'Clinical Future Tasks'. This is useful when a clinical user (e.g. MA or RN) terminates and the user account is inactivated, yet the user still has inactive future tasks that will need to be worked by someone upon activation of the future tasks. <br />
* Create a 'Lab Order Feedback' task view for organizations who have a two-way lab interface. This view is useful for communicating necessary lab order changes between clinical and IT/IS staff when lab results are stuck in the interface.<br />
<br />
==Review New V11 Tasks==<br />
* A Microsoft Excel spreadsheet describing all tasks is available from the Allscripts Knowledge Base: kb.allscripts.com doc # 3350. It does not indicate which tasks are new in v11<br />
* The spreadsheet can be filtered or sorted by module to focus on only the modules the client has<br />
* The following link goes to a Wiki version sorted by Module: [[v11 Tasks]]<br />
* See also [[11.x to 11.2 Incorporate new 11.2 Tasks]]<br />
<br />
==Edit Tasks==<br />
Tasks come delivered with preset overdue limits and other settings and most should not need modification.<br />
<br />
Dictionaries > Task Name dictionary<br />
<br />
The following settings can be modified:<br />
<br />
'''Task Action''' Grayed out in v11.1.7<br />
<br />
'''Delegate''' Check this box to prevent the task type from showing up in "My Active Tasks". <br />
This is useful for tasks that are not going to be worked by a provider, but instead by a nurse or an MA. An example would be "Call in Failed Rx". It is important to remember to build a task view to capture these delegated tasks, or else, they will not be seen by anyone.<br />
<br />
'''Default OverDue Time By priority'''<br />
* Default time until task is flagged as overdue. A different time can set for each priority level.<br />
* In the example below, the task 'Call Back' will become overdue if not completed within '1 Day' (24 hours). If the user creating a 'Call Back' task selects the Priority 'ASAP' the task will become overdue in 6 hours. If 'Urgent', 60 minutes.<br />
* The times are defaults and can be edited by the user when creating individual tasks<br />
[[Image:Edit Task.jpg]]<br />
<br />
'''Copy To Note Options'''<br />
<br />
Available for the following Tasks:<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action '''<br />
| align="center" style="background:#f0f0f0;"|'''Task Name'''<br />
|-<br />
| Miscellaneous||Call Back<br />
|-<br />
| Miscellaneous||Follow Up<br />
|-<br />
| Miscellaneous||Health Maintenance Alert<br />
|-<br />
| Miscellaneous||Hospital Calls<br />
|-<br />
| Process Note||Medical Problem or Complaint<br />
|-<br />
| Miscellaneous||Medication Renewal<br />
|-<br />
| Miscellaneous||Patient Arrived<br />
|-<br />
| Miscellaneous||Personal<br />
|-<br />
| Process Note||Referral Follow Up<br />
|-<br />
| Process Result||Result Follow Up<br />
|-<br />
| <br />
|}<br />
<br />
* Complete the Task when Copy to Note - This option will automatically complete the task once it has been copied to note.<br />
* Default Encounter Type - Complete this option to select which encounter type the newly created note will attach to when "copy to note" is checked for a given task type<br />
* Default Note Type - This option will automatically open a pre-determined note type when "copy to note" is checked for a given task type<br />
<br />
==Task Views Overview==<br />
* Enterprise task views can be created and assigned to multiple users.<br />
* One or more personal views can be created for each individual user.<br />
* A user can access their personal and/or assigned enterprise views via dropdown.<br />
* One of these views must be designated as the default display. <br />
* Enterprise views and default views should be created and assigned based on roles.<br />
* Personal views should be used only to accommodate a user's personal preferences.<br />
<br />
==Add Tasks to Views - Edit/Create Views==<br />
# 'TWAdmin' VTB > 'Task Admin' HTB ><br />
# Select 'Enterprise Views' or 'Personal Views' tab<br />
# The 'View:' field displays the name of the task view being created, edited or deleted.<br />
# To edit or delete existing views, click 'Go' to see all existing views and select a view to edit. To find a specific view, type the ''beginning'' of the name into the 'View' field and click 'Go'.<br />
# To create a new view, click 'New'.<br />
# Always enter a description of the view.<br />
[[Image:start.jpg]]<br />
<br />
===Configure one or more filters to limit the tasks displayed===<br />
Filters can be utilized to return smaller lists of tasks related to specific activities and roles. These filters are how the system will determine which specific tasks to show in a task view. For example, to isolate "Verify Result" tasks for a given provider, filter by "Assigned to", select the provider name, arrow over, then filter by the task type "verify results", arrow over then filter by task status of "active" and "in progress" to see all Verify Results tasks that are Active or In Progress for the referenced provider. By utilizing the filter function, larger task lists are broken down into smaller more manageable lists for the end user<br />
<br />
#Use the left and right buttons to add or remove filters from the view<br />
#Multiple values can be selected for the same filter<br />
#:[[Image:multiple values.jpg]]<br />
<br />
'''Filters:'''<br />
<br />
*'''Assigned To''' displays only tasks assigned to the user or users selected<br />
**The Team option will return tasks assigned to a particular team<br />
**The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams. see [[#Create Teams as Users|Create Teams as Users]] below.<br />
<br />
*'''Created''' displays only tasks created on a certain day or range of days.<br />
<br />
*'''Created By''' displays only tasks created by the user or users selected.<br />
<br />
*'''Delegated''' displays only delegated tasks. Example: The view Cardiology Billing might be Created By = [select cardiology providers], Delegated = Y, Task = Adjust Charges (as long as this task type has the "delegated" box checked, all "Adjust Charges" tasks will show up in the view for the providers selected in the view.<br />
<br />
*'''Overdue''' displays only overdue tasks.<br />
<br />
*'''Patient''' displays only tasks related to the patient in context or to an alphabetical range of patients<br />
<br />
*'''Priority''' displays only tasks with the selected priority or priorities.<br />
<br />
*'''Status''' displays only tasks with the selected status or statuses.<br />
<br />
When filtering for tasks with status "Active", "In Progress" must also be selected because "In Progress" tasks are active tasks that are currently being worked.<br />
<br />
*'''Task''' displays only the task types selected.<br />
<br />
===Configure one or more sorts to organize the tasks displayed===<br />
Note: Sorts will be executed in order.<br />
<br />
==Assign Views to Users==<br />
This can be done manually or through SSMT. When assigning a large amount of views SSMT is the preferred method.<br />
<br />
===Manual===<br />
Assign view to 1 user and workflow test before assigning to multiple users <br />
# Select 'Manage Personal' tab<br />
# Select a user from the 'Views For:' dropdown or click 'All' to search all users.(who are the users in the dropdown?)<br />
#:[[Image:select user.jpg]]<br />
# To Add enterprise task views to the user, select the view in the lower table and click 'Add to My Views'.<br />
# To Remove views from a user, select the view in the upper table and click "Remove"<br />
#* If the selected view is a personal view, the system will display a warning before deleting the view.<br />
# Select the default view for the user by selecting a view from the upper table and clicking 'Set as Default'.<br />
#* The view selected as default cannot be removed. To remove the default view, make another view the default.<br />
#:[[Image:taskg.jpg]]<br />
<br />
===SSMT===<br />
Task views can be assigned to multiple users using SSMT Category: 'Task View-Users'<br />
*'*HDRAUsername' is the user (?)<br />
*'Name' is the task view<br />
*'Task Owner' is (?)<br />
*'IsDefault' must be Y or N. Only one row per user can be Y<br />
*'Create (Y N)' must be set to Y for added rows<br />
To copy task views from one user to another<br />
#Sort the exported list by '*HDRAUsername'<br />
#Identify a user who already has the task view or views to be assigned to the new user. This will usually be a user with the same role.<br />
#Copy the rows for the views to be assigned<br />
#Do not copy rows for views already assigned to the new user (?)<br />
#Add the copied rows to the spreadsheet<br />
#Change '*HDRAUsername' to the new username<br />
#If 'Task Owner' = username, change it to the new user name<br />
#Change 'Create (Y N)' to Y only for the rows that were added<br />
<br />
For SSMT basics see [[SSMT]]<br />
<br />
==Create Teams as Users==<br />
The team list is at the enterprise level and for large organizations can become long and difficult to navigate through when assigning tasks. For this situation, a false user can be created in place of a team. This allows users to select from user favorites instead of searching through the entire list of teams.<br />
<br />
The advantage to this approach has to do with the way the drop down lists work on the New Task page. The team drop down shows all entries in the Team dictionary. The user drop down is a favorites list and only shows the values that have been searched for by that user. If you have the same set of teams at each site, it’ll turn into quite a long list of teams and be very difficult to select. The only time we suggest using teams is for central teams that are used system wide. Other than that it’s much better to use the user concept and define a naming convention that is consistent and easy to train users on how to search for their specific teams.<br />
<br />
===High Level Process===<br />
Example: New World Health has a dermatology practice with three front desk staff.<br />
# Create false user 'NWH Dermatology,Front Desk'<br />
# Create task view 'Dermatology Front Desk'. Set filter 'Assigned To' to 'NWH Dermatology,Front Desk'<br />
# Assign task view 'Dermatology Front Desk' to the three front desk staff<br />
# Add user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk.<br />
<br />
===Detailed Steps===<br />
'''Create False User'''<br />
# VTB: TWUser Admin > HTB User Admin<br />
# User Type: User<br />
# Last Name: NWH Dermatology<br />
# First Name: Front Desk<br />
# Email: email@email.com<br />
# Organization: Select the Organization the (team?) belongs to<br />
# User Name: NWHDermatologyFrontDesk (no spaces)<br />
# Default Site: Select the Site the (team?) belongs to<br />
# Password: password<br />
# Profession: Other<br />
# Save<br />
<br />
'''Create Task View'''<br />
# VTB: Task Admin > HTB Enterprise Views<br />
# Click 'New'.<br />
# View: Dermatology Front Desk<br />
# Description: All tasks assigned to the false user 'NWH Dermatology,Front Desk'<br />
# Assigned To: User: NWH Dermatology,Front Desk<br />
# Status: Active, In Progress<br />
# Save<br />
<br />
'''Assign View to Team'''<br />
<br />
Assign view: 'Dermatology Front Desk' to the three front desk staff<br />
<br />
(Copy and edit [[#Assign Views to Users|Assign Views to Users]] to make specific to Creating Teams as Users and specific to this example)<br />
<br />
'''Add False User to Favorites'''<br />
<br />
Add the user 'NWH Dermatology,Front Desk' to the list of favorite users for all users that will assign tasks to the dermatology front desk<br />
# Navigate to the Physician Admin Menu by using the drop-down in the top right hand corner of the screen<br />
#:[[Image:Patpref1.jpg]]<br />
# Expand the “By Category” Menu<br />
#:[[Image:Patpref2.jpg]]<br />
# Select Favorites<br />
#:[[Image:Patpref3.jpg]]<br />
# Expand 'User Favorites'. ''This is the list of people users choose from when assigning tasks''<br />
#:[[Image:User Favorites.jpg]]<br />
# Select 'Master Favorites' if all members of a specialty (Dermatology) will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select Group: Dermatology (Specialties must be mapped to Groups?)<br />
#:[[Image:By Specialty.jpg]]<br />
# Select 'Personal Favorites' if only some users will need to assign tasks to the 'NWH Dermatology,Front Desk' team<br />
#* Select a user who will need to assign tasks from the 'For:' dropdown (Group should be grayed out when personal is selected?)<br />
#:[[Image:By User.jpg]]<br />
# Add the user 'NWH Dermatology,Front Desk' to 'User Favorites' list for the selected user<br />
#* Search for the user 'NWH Dermatology,Front Desk'<br />
#* Click on the user 'NWH Dermatology,Front Desk' in the left pane to add it to the user favorites in the right pane<br />
#:[[Image:Add Team to User Favorites.jpg]]<br />
#Save<br />
#Saved Successfully will appear for a second in the upper right hand corner of your screen<br />
#:[[Image:Patpref9.jpg]]<br />
<br />
'''Test'''<br />
# Login as a user who needs to assign tasks to the dermatology front desk team<br />
# Create a new task and assign it to NWH Dermatology,Front Desk<br />
# Login as a member of the dermatology front desk team, navigate to tasks and select view 'Dermatology Front Desk'<br />
# The task should be present</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:OID_OEQ.jpg&diff=9895File:OID OEQ.jpg2011-01-03T18:05:36Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:OID.jpg&diff=9894File:OID.jpg2011-01-03T18:04:53Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Addtl_info_detail_3.jpg&diff=9893File:Addtl info detail 3.jpg2011-01-03T18:04:35Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Addtl_info_detail_2.jpg&diff=9892File:Addtl info detail 2.jpg2011-01-03T18:04:08Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Addtl_info_detail_1.jpg&diff=9891File:Addtl info detail 1.jpg2011-01-03T18:03:45Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Addtl_info_dictionary.jpg&diff=9890File:Addtl info dictionary.jpg2011-01-03T18:03:02Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Add_entries_to_picklist.jpg&diff=9889File:Add entries to picklist.jpg2011-01-03T18:02:28Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Answer_Picklist.jpg&diff=9888File:Answer Picklist.jpg2011-01-03T18:01:55Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Picklist_Banner.jpg&diff=9887File:Picklist Banner.jpg2011-01-03T18:01:24Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Answer_Dictionary.jpg&diff=9886File:Answer Dictionary.jpg2011-01-03T18:00:13Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Additional_info_example.jpg&diff=9885File:Additional info example.jpg2011-01-03T17:59:39Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Additional_Information_Configuration&diff=9884Additional Information Configuration2011-01-03T16:43:20Z<p>Tyler.Yoder: Created page with "=Definition= Order item questions, additional information questions, and order entry questions are all terms used my clients and consultants to refer to entries in the "Additiona..."</p>
<hr />
<div>=Definition=<br />
Order item questions, additional information questions, and order entry questions are all terms used my clients and consultants to refer to entries in the "Additional Information" dictionary. These are questions used in orders to elaborate and give more specific details for the order. Additional information questions can range from asking the source for a fluid cytology, to asking the manufacturer and model # of a device like a pacemaker for a device check, or to asking the reason for referral/follow up when a physician orders a follow up or referral for a patient. Below you can see an example of an order with multiple additional information questions. Some of these questions have picklist associated with them while others have a free text box associated with them.<br />
<br />
[[Image:Additional info example.jpg]]<br />
<br />
<br />
=Additional Information Question Configuration=<br />
To properly build additional information questions, it is imperative to understand all the parts that make up the questions, and how they work. It is easiest to work backwards when building these questions.<br />
<br />
* First, build the answers to the questions in the "Answer" dictionary.<br />
* Second, build the picklist (if needed) with the answers.<br />
* Third, build the additional info question in the "Additional Information" dictionary.<br />
* Fourth, add the picklist to the question (if appropriate).<br />
* Fifth, add the additional info question to the order.<br />
<br />
<br />
=Building the Answer Dictionary=<br />
To add entries to the "Answer" dictionary:<br />
*Login as TWAdmin.<br />
*Go to "Dictionaries" in the vertical tool bar.<br />
*Find the dictionary named "Answer."<br />
<br />
On the left, you will see answer groupings. I suggest creating a unique grouping to contain the answers for each question. Name them something unique and according to your clients naming convention, so you can easily identify them when building your picklist. To add a unique grouping:<br />
*Click "Answer" at the top of the left coulumn in the dictionary.<br />
*Click Add.<br />
*Name your grouping.<br />
To add answers to the grouping:<br />
*Select the grouping.<br />
*Click Add.<br />
*Add you answer. The code and mnemonic can be whatever. The name should be exactly how you want the answer to appear in the order on the front end.<br />
*Click Save.<br />
[[Image:Answer Dictionary.jpg]]<br />
<br />
To create picklist containing the answers:<br />
*Click picklist at the bottom of the answer dictionary.<br />
[[Image:Picklist Banner.jpg]]<br />
*Click Add Picklist, and name the picklist something unique to the question being answered.<br />
*Click add entries.<br />
[[Image:Answer Picklist.jpg]]<br />
*Find your answers on the left, and click add. Once done, ok, then click close.<br />
[[Image:Add entries to picklist.jpg]]<br />
<br />
=Building the Additional Information Question=<br />
* Login as TWAdmin.<br />
* Go to "Dictionaries" in the vertical tool bar.<br />
* Find the dictionary named "Additional Information."<br />
* Click Add.<br />
* Name your questions with a code, mnemonic, and name according to your client's naming convention.<br />
[[Image:Addtl info dictionary.jpg]]<br />
* Under detail 1:<br />
- The display name: exactly how the question will display in the order.<br />
- The answer data type: is the type of answer you want tied to the question. This <br />
can be date/time, numeric values, a picklist, or a free text box. Each answer <br />
type has its own special charateristics that need to be appropriately selected <br />
also.<br />
- Default value: is the answer you want the question to automatically default to, <br />
if you want it to have a default answer.<br />
[[Image:Addtl info detail 1.jpg]]<br />
* Under detail 2:<br />
- The answer will default section: is where you set the behavior for how the default answer to the question behaves, if <br />
applicable.<br />
- This question is: is where you can set if the question is required before saving the order, or if it goes into a "needs <br />
info" or "on hold" status if the question isnt answered when ordered.<br />
- Exclude question if patient sex is: where you can set if the question applies only to a certain gender.<br />
- Appear in note text for order: if this box is checked, the question and answer will display with the order in the plan <br />
section of the note.<br />
- Minimum and maximimum applicable age: where you can set to include or exclude the question based on the patient's age.<br />
[[Image:Addtl info detail 2.jpg]]<br />
<br />
* Under detail 3: <br />
- This is where you can set the behavior of what happens next, if the answer entered is a certain value. You can set the <br />
system to ask another additional info question if the answer is a certain value. You can also set the system to ask another <br />
additional info question if the answer entered does not match a certain value.<br />
[[Image:Addtl info detail 3.jpg]]<br />
<br />
* Once all the correct information has been entered, click save.<br />
<br />
= Adding the additional information question to the order=<br />
* Login as TWAdmin.<br />
* Go to "Dictionaries" in the vertical tool bar.<br />
* Find the dictionary named "Orderable Item."<br />
* Click search, and search for the order you want to apply the additional information question(s) to.<br />
* Highlight that order, scroll down to the instructions section, and click the link "Additional information questions."<br />
[[Image:OID.jpg]]<br />
* Search for the additional info question(s) you want to be tied to the order, and click the down arrow to add it to the order.<br />
* Click ok.<br />
[[Image: OID OEQ.jpg]]<br />
* Click save.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Task_Name_Dictionary.jpg&diff=9126File:Task Name Dictionary.jpg2010-08-24T13:24:30Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Task_Dictionary_Setup&diff=9125Task Dictionary Setup2010-08-24T13:24:09Z<p>Tyler.Yoder: </p>
<hr />
<div>__TOC__<br />
<br />
=Description=<br />
The Task Name dictionary is used to indicate the name assigned to a task. Names are used to track tasks within TouchWorks. This dictionary contains some enforced entries delivered by Allscripts, as well as new tasks added by a system administrator.<br />
<br />
=Definition=<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
* '''Task Action''' - Task Action determines the location a user may create that task from. Some examples are:<br />
{| {{table cellspacing=10}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action:'''<br />
| align="center" style="background:#f0f0f0;"|'''Creation Location:'''<br />
|-<br />
| Authorize Order||AuthenticateOrder||<br />
|-<br />
| Review Charges||ChgWorksEncounterForm||<br />
|-<br />
| Sign Note||DWNote||<br />
|-<br />
| Verify Results||ResultsVerifyBatch||<br />
|-<br />
| <br />
|}<br />
''Note: Once the task action is linked to a task and saved, it is permanent and cannot be changed later.''<br />
<br />
* '''Default Overdue Time Priorities''' - These define the time priorities for which the task becomes overdue if not completed within the default time interval assigned to the priority.<br />
* '''Delegate''' - Non-Delegated tasks are tasks organized and worked by a user from their “My Active Task” view. Delegated tasks are tasks created by a user, but worked by someone else. These tasks do NOT display on the “My Active Task” view for the user, so a separate task view must be created to view and work delegated tasks.<br />
* '''Copy to Note Options''' <br />
* '''Complete the Task when Copy to Note'''- If checked, the task will be marked as completed when the task is copied to a note. <br />
* '''Default Encounter''' - If selected, this type of encounter will be created by default, and the note will be linked to this encounter.<br />
* '''Default Note Type''' - If selected, this type of note will be created by default<br />
<br />
=Task Name Dictionary Configuration=<br />
# Login as TWAdmin.<br />
# Go to the Dictionaries VTB.<br />
# Select the Task Name Dictionary from the drop down menu.(From here, tasks can be edited or created.) <br />
# To create a new task, click "Add" at the bottom of the screen, and enter appropriate code, name, and mnemonic.<br />
# Select appropriate Task Action and assign overdue times as seen fit.<br />
# Click Save when finished.<br />
<br />
[[Image:Task Name Dictionary.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Task_Dictionary_Setup&diff=9124Task Dictionary Setup2010-08-24T13:23:02Z<p>Tyler.Yoder: Created page with '__TOC__ =Description= The Task Name dictionary is used to indicate the name assigned to a task. Names are used to track tasks within TouchWorks. This dictionary contains some en…'</p>
<hr />
<div>__TOC__<br />
<br />
=Description=<br />
The Task Name dictionary is used to indicate the name assigned to a task. Names are used to track tasks within TouchWorks. This dictionary contains some enforced entries delivered by Allscripts, as well as new tasks added by a system administrator.<br />
<br />
=Definition=<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. If an item is inactivated, users would not have the ability to select the allergen in the future, although any patients with the allergen defined would remain viewable. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
* '''Task Action''' - Task Action determines the location a user may create that task from. Some examples are:<br />
{| {{table cellspacing=10}}<br />
| align="center" style="background:#f0f0f0;"|'''Task Action:'''<br />
| align="center" style="background:#f0f0f0;"|'''Creation Location:'''<br />
|-<br />
| Authorize Order||AuthenticateOrder||<br />
|-<br />
| Review Charges||ChgWorksEncounterForm||<br />
|-<br />
| Sign Note||DWNote||<br />
|-<br />
| Verify Results||ResultsVerifyBatch||<br />
|-<br />
| <br />
|}<br />
''Note: Once the task action is linked to a task and saved, it is permanent and cannot be changed later.''<br />
<br />
* '''Default Overdue Time Priorities''' - These define the time priorities for which the task becomes overdue if not completed within the default time interval assigned to the priority.<br />
* '''Delegate''' - Non-Delegated tasks are tasks organized and worked by a user from their “My Active Task” view. Delegated tasks are tasks created by a user, but worked by someone else. These tasks do NOT display on the “My Active Task” view for the user, so a separate task view must be created to view and work delegated tasks.<br />
* '''Copy to Note Options''' <br />
* '''Complete the Task when Copy to Note'''- If checked, the task will be marked as completed when the task is copied to a note. <br />
* '''Default Encounter''' - If selected, this type of encounter will be created by default, and the note will be linked to this encounter.<br />
* '''Default Note Type''' - If selected, this type of note will be created by default<br />
<br />
=Task Name Dictionary Configuration=<br />
# Login as TWAdmin.<br />
# Go to the Dictionaries VTB.<br />
# Select the Task Name Dictionary from the drop down menu.(From here, tasks can be edited or created.) <br />
# To create a new task, click "Add" at the bottom of the screen, and enter appropriate code, name, and mnemonic.<br />
# Select appropriate Task Action and assign overdue times as seen fit.<br />
# Click Save when finished.<br />
<br />
[[Image:Task Name.jpg]]</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Patientbanner.jpg&diff=9123File:Patientbanner.jpg2010-08-24T13:19:53Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Patient_banner&diff=9122Patient banner2010-08-24T13:19:18Z<p>Tyler.Yoder: </p>
<hr />
<div>=Description=<br />
The patient banner is the information bar across the top of the clinical desktop that displays a patient's information as selected by the organization. This can include the patient's Medical Record Number (MRN), Date of Birth (DOB), Age, Sex, Email, Primary Care Physician (PCP), Primary Insurance (PriIns), Home Phone Number (HPhone), Allergies, Directives, Security, FYI comments, Note, Nicknames (AKA), Work Phone, Social Security Number, and other information as the client sees fit.<br />
<br />
=Restrictions=<br />
The patient banner will only display 9 fields if the screen resolution of the workstation running Touchworks is 800x600.<br />
<br />
=Patient Banner Configuration=<br />
To set up what information will be displayed on the patient banner:<br />
# Login as TWAdmin<br />
# Select the Utilities VTB<br />
# Select the Patient Banner Setup HTB<br />
# Add or remove appropriate fields<br />
# Save.<br />
<br />
[[Image:patientbanner.jpg]]<br />
<br />
<br />
<br />
If checked, the "Display Patient Info in the Banner" checkbox at the bottom will insert an "i" icon on the patient banner that will display the patient's demographic information in a new window when clicked.<br />
<br />
<br />
=Troubleshooting=<br />
<br />
<br />
'''Problem''' <br />
<br />
Patient Banner configuration is inconsistent between users.<br />
<br />
To the user, it appears that some users see a different banner configuration that others. For example, one user may see the field name 'DOB' in the banner, and another user would not see this field name.<br />
<br />
<br />
'''Cause'''<br />
<br />
When using multiple web servers, it is possible for the patient banner configuration to be out of synch.<br />
<br />
<br />
<br />
'''Solution'''<br />
<br />
Using TWAdmin, login directly to each web servers dedicated IP address or name (e.g ASWEB1 and ASWEB2 instead of the virtual name 'ASWEB' and configure the banner as it should appear.<br />
<br />
<br />
<br />
'''Issue'''<br />
<br />
I would like the patient banner fields to display something different, for example Other2 to say C Phone<br />
<br />
'''Solution'''<br />
<br />
Navigate to the folder C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\Works\Working\CustomBanner.xml <br />
<br />
Open the file with a program that will allow you to edit the xml. <br />
<br />
Change the value inbetween the <label> </label> tags to whatever you want. For example Other2 to Cellphone.<br />
<br />
'''Note: This file must be copied to each web server! It may also get overwritten with upgrades so keep a backup of the XML file handy to reapply.'''</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Patient_Security_Access_Groups&diff=8744Patient Security Access Groups2010-06-09T19:25:18Z<p>Tyler.Yoder: </p>
<hr />
<div>==Patient Security Access Groups==<br />
<br />
While others can be created, three specific patient security access groups are pre-delived by Allscripts. These are: <br><br />
<br />
1. '''Employee & Family Patient Access Groups''' - used to place employees and their family members (usually upon request of the employee) behind security, requiring anyone without this security code to break glass to access their records.<br />
<br />
2. '''Restricted Patient Access Group''' - used for the general public who request their records are kept secure from other records. Only users with the Restricted Security code have access without having to break glass. <br />
<br />
3. '''VIP Patient Access Group''' - used for high profile patients such as celebrities, governmental officials, etc. Only users with the VIP Patient Access Security code have access without having to break glass.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Patient_Security_Access_Groups&diff=8743Patient Security Access Groups2010-06-09T19:22:57Z<p>Tyler.Yoder: </p>
<hr />
<div>'''Patient Security Access Groups'''<br />
<br />
There are three specific patient security access groups: <br><br />
<br />
1. Employee & Family Patient Access Groups - used to place employees and their family members (usually upon request of the employee) behind security, requiring anyone without this security code to break glass to access their records.<br />
<br />
2. Restricted Patient Access Group - used for the general public who request their records are kept secure from other records. Only users with the Restricted Security code have access without having to break glass. <br />
<br />
3. VIP Patient Access Group - used for high profile patients such as celebrities, governmental officials, etc. Only users with the VIP Patient Access Security code have access without having to break glass.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Patient_Security_Access_Groups&diff=8742Patient Security Access Groups2010-06-09T19:18:08Z<p>Tyler.Yoder: </p>
<hr />
<div>'''Patient Security Access Groups'''<br />
<br />
There are three specific patient security access groups: <br />
1. Employee & Family Patient Access Groups - used to place employees and their family members (usually upon request of the employee) behind security, requiring anyone without this security code to break glass to access their records.<br />
<br />
2. Restricted Patient Access Group - used for the general public who request their records are kept secure from other records. Only users with the Restricted Security code have access without having to break glass. <br />
<br />
3. VIP Patient Access Group - used for high profile patients such as celebrities, governmental officials, etc. Only users with the VIP Patient Access Security code have access without having to break glass.</div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=File:Encouter_Type_Dictionary.jpg&diff=8741File:Encouter Type Dictionary.jpg2010-06-09T19:06:49Z<p>Tyler.Yoder: </p>
<hr />
<div></div>Tyler.Yoderhttps://wiki.galenhealthcare.com/index.php?title=Encounter_Type&diff=8740Encounter Type2010-06-09T19:06:07Z<p>Tyler.Yoder: </p>
<hr />
<div>Back to [http://wiki.galenhealthcare.com/TouchWorks_V11_Dictionaries Touchworks v11 Dictionaries]<br />
<br />
<br />
== Description ==<br />
The Encounter Type dictionary is used to define the types of encounters.<br />
All clinical data in TouchWorks must be tied to an encounter. Encounters<br />
can be created by appointments sent via the scheduling interface, notes<br />
created via call processing, and results and transcriptions that come<br />
across the interface that are not already tied to an encounter.<br> <br />
The following encounter types are used within TouchWorks:<br><br />
<br />
*Appointment—default used for appointments that come across the scheduling interface; a specific encounter type can be entered in the Scheduling application and sent across the scheduling interface<br><br />
*Message—used for patient Notes copied from Mail <br />
*Other—used for results and transcriptions that come across the interface and create an encounter<br><br />
*Telephone Call—used for patient Notes copied from Call Processing <br />
<br />
This dictionary is called from:<br><br />
Note<br><br />
Encounter Form Selector<br><br />
Encounter Summary<br><br />
<br />
== Definition ==<br />
[[Image:Encounter_Type1.jpg]]<br />
<br />
* '''Code''' - The Code is a unique identifier that must be supplied. This is not displayed in the product and is used for identification purposes only.<br />
* '''Name''' - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.<br />
* '''Mnemonic''' - This is not required, but it used as a secondary identifier. This does not appear in the product and unless you have another use for it, the recommendation would be to make this the same as the code.<br />
* '''Inactive''' - The inactive flag allows you to inactivate or hide an entry. <br />
* '''Enforced''' - The enforced flag designates whether a dictionary item is required and cannot be changed. In most cases, this comes predefined by Allscripts and should not be selected for new entries. If an entry is enforced, it cannot be modified or inactivated.<br />
<br />
* '''Can Submit Charges for the Encounter Type''' -enables this encounter type to be selected when TouchWorks prompts for which encounter to enter the charges. This can be used to enable any non-appointment encounter type to be available to any user within Charge, when launching the encounter selector from within charge, only encounters with this flag are selectable.<br />
* '''Linked Appointment''' - indicates whether this encounter type is linked to an appointment from the practice management system. If so, Submit Enc Form tasks will be created once the patient has been arrived.<br />
<br />
==To Add New Encounter Types==<br />
* Login as '''TWAdmin'''.<br />
* Go to '''Dictionaries'''.<br />
* Select the '''Encounter Type''' Dictionary from the dropdown menu.<br />
* Click '''Add''' at the bottom of the scree.<br />
* Using the definitions above, fill out the information accordingly.<br />
* Click '''Save'''.<br />
[[Image:Encouter Type Dictionary.jpg]]</div>Tyler.Yoder