Difference between revisions of "Encounter Type"
Jump to navigation
Jump to search
Tyler.Yoder (talk | contribs) |
Onamitihys (talk | contribs) |
||
| Line 2: | Line 2: | ||
| − | == Description == | + | >== Description == |
The Encounter Type dictionary is used to define the types of encounters. | The Encounter Type dictionary is used to define the types of encounters. | ||
All clinical data in TouchWorks must be tied to an encounter. Encounters | All clinical data in TouchWorks must be tied to an encounter. Encounters | ||
can be created by appointments sent via the scheduling interface, notes | can be created by appointments sent via the scheduling interface, notes | ||
created via call processing, and results and transcriptions that come | created via call processing, and results and transcriptions that come | ||
| − | across the interface that are not already tied to an encounter. | + | across the interface that are not already tied to an encounter.<br> |
| − | The following encounter types are used within TouchWorks: | + | The following encounter types are used within TouchWorks:<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 | + | *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> |
*Message—used for patient Notes copied from Mail | *Message—used for patient Notes copied from Mail | ||
| − | *Other—used for results and transcriptions that come across the interface and create an encounter | + | *Other—used for results and transcriptions that come across the interface and create an encounter<br> |
*Telephone Call—used for patient Notes copied from Call Processing | *Telephone Call—used for patient Notes copied from Call Processing | ||
| − | This dictionary is called from: | + | This dictionary is called from:<br> |
| − | Note | + | Note<br> |
| − | Encounter Form Selector | + | Encounter Form Selector<br> |
| − | Encounter Summary< | + | Encounter Summary<br> |
| + | |||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://axyzuhy.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
| + | ---- | ||
| + | =[http://axyzuhy.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
== Definition == | == Definition == | ||
Revision as of 00:25, 18 November 2010
Back to Touchworks v11 Dictionaries
>== Description ==
The Encounter Type dictionary is used to define the types of encounters.
All clinical data in TouchWorks must be tied to an encounter. Encounters
can be created by appointments sent via the scheduling interface, notes
created via call processing, and results and transcriptions that come
across the interface that are not already tied to an encounter.<br>
The following encounter types are used within TouchWorks:<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>
- Message—used for patient Notes copied from Mail
- Other—used for results and transcriptions that come across the interface and create an encounter<br>
- Telephone Call—used for patient Notes copied from Call Processing
This dictionary is called from:<br> Note<br> Encounter Form Selector<br> Encounter Summary<br>
Definition
- 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.
- Name - This is the name that will appear for the end users in the EHR application. This should be unique to prevent confusion.
- 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.
- Inactive - The inactive flag allows you to inactivate or hide an entry.
- 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.
- 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.
- 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.
To Add New Encounter Types
- Login as TWAdmin.
- Go to Dictionaries.
- Select the Encounter Type Dictionary from the dropdown menu.
- Click Add at the bottom of the scree.
- Using the definitions above, fill out the information accordingly.
- Click Save.
