https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Charlie.Morris&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T08:13:22ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=SSMT:_Clinical_Desktop_Views_-_Users&diff=12251SSMT: Clinical Desktop Views - Users2011-12-21T21:02:53Z<p>Charlie.Morris: Created page with "== Description == This category allows you to assign clinical desktop views to users as well as set the default clinical desktop view for a user. == Columns == '''Username:'''D..."</p>
<hr />
<div>== Description ==<br />
This category allows you to assign clinical desktop views to users as well as set the default clinical desktop view for a user.<br />
<br />
<br />
== Columns ==<br />
'''Username:'''Determines which user account will be affected by the row.<br />
<br />
'''View Name''' Determines which clinical desktop view will be associated with the preceeding user account.<br />
<br />
'''Site''' This is only used for personal views. By adding a site here, you can determine which clincal desktop views will be associated with a user while logged into a certain site.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=CAH&diff=12250CAH2011-12-21T20:55:39Z<p>Charlie.Morris: Created page with "A Critical Access Hospital (CAH) is a hospital certified to receive cost-based reiumbursement from Medicare. The reimbursement that CAH's receive is intended to improve their fin..."</p>
<hr />
<div>A Critical Access Hospital (CAH) is a hospital certified to receive cost-based reiumbursement from Medicare. The reimbursement that CAH's receive is intended to improve their financial performance, preventing hospital closures.To receive CAH status, a hospital must be located over 35 miles from another hospital or 15 miles from another hopsital in mountainous terrain or areas with only secondary roads. <br />
<br />
The benefits of CAH Status include: cost-based medicare reimbursement, CAH network with an acute care hospital for suppport, access to Flex Program money, and flexible staffing and services</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=HIT&diff=12249HIT2011-12-21T20:48:56Z<p>Charlie.Morris: Created page with "Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally conta..."</p>
<hr />
<div>Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally contained in a patients chart on a computer, rather than on paper.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Display_Names&diff=10937SSMT: Display Names2011-03-31T15:44:54Z<p>Charlie.Morris: </p>
<hr />
<div>== Description ==<br />
The SSMT: Display Names content category allows you to manage the display names tied to entries in several different dictionaries. The basic structure is the same for each dictionary. <br />
<br />
<br />
The dictionaries that can be managed include:<br />
*Additional Information<br />
*Document Type<br />
*ICD9 Diagnosis<br />
*Medication<br />
*Orderable Item<br />
*Problem<br />
<br />
<br />
----<br />
<br />
<br />
*'''Dictionary Name:''' Name of the dictionary that houses the entry. One of the 6 listed above.<br />
<br />
*'''Entry Name:''' Unique entry name from the affected dictionary.<br />
<br />
*'''Display Name:''' The name that will display in the front end of the application.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Display_Names&diff=10936SSMT: Display Names2011-03-31T15:43:44Z<p>Charlie.Morris: Created page with " == Description == The SSMT: Display Names content category allows you to manage the display names tied to entries in several different dictionaries. The basic structure is the s..."</p>
<hr />
<div><br />
== Description ==<br />
The SSMT: Display Names content category allows you to manage the display names tied to entries in several different dictionaries. The basic structure is the same for each dictionary. <br />
<br />
The dictionaries that can be managed include:<br />
-Additional Information<br />
-Document Type<br />
-ICD9 Diagnosis<br />
-Medication<br />
-Orderable Item<br />
-Problem<br />
<br />
*'''Dictionary Name:''' Name of the dictionary that houses the entry. One of the 6 listed above.<br />
<br />
*'''Entry Name:''' Unique entry name from the affected dictionary.<br />
<br />
*'''Display Name:''' The name that will display in the front end of the application.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Division&diff=10935SSMT: Division2011-03-31T15:14:51Z<p>Charlie.Morris: </p>
<hr />
<div>==Description==<br />
The Division SSMT content category can be used to assist in managing the entries in the Division dictionary. The Division dictionary in most cases is provided by the PMS and in some cases kept synchronized via dictionary interfaces with the PMS. It is almost always the case that the entry code, name, and mnemonic values for your Division entries will need to match what is in the PMS or centralized billing system.<br />
<br />
----<br />
<br />
*'''Entry Code:''' Unique code that needs to be matched up to the PMS.<br />
<br />
*'''Division Name:''' A text description of the Division. Usually this description is the name that the client uses for the division.<br />
<br />
*'''Entry Mnemonic:''' Unique mneumonic that needs to be matched up the PMS. This is often identical to the Entry Code.<br />
<br />
*'''Inactive:''' Y/N. Set to Y to inactivate an existing Division. Otherwise, set to N.<br />
<br />
*'''Create:''' Y/N. Set to Y to create a new Division. Set to N to edit an existing Division.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Division&diff=10934SSMT: Division2011-03-31T15:00:46Z<p>Charlie.Morris: Created page with "==Description== The Division SSMT content category can be used to assist in managing the entries in the Division dictionary. The Division dictionary in most cases is provided by..."</p>
<hr />
<div>==Description==<br />
The Division SSMT content category can be used to assist in managing the entries in the Division dictionary. The Division dictionary in most cases is provided by the PMS and in some cases kept synchronized via dictionary interfaces with the PMS. It is almost always the case that the entry code, name, and mnemonic values for your Division entries will need to match what is in the PMS or centralized billing system.<br />
<br />
<br />
----<br />
<br />
*'''Entry Code:'''</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Task_View-Setup&diff=10931SSMT: Task View-Setup2011-03-30T20:30:18Z<p>Charlie.Morris: </p>
<hr />
<div>== Description ==<br />
The Task View-Setup content category is used for editing the configuration of the actual task view. It only contains a few basic rows and can be helpful in moving task views from one environemnt to another. Because task view names cannot be truly changed, this category can be used to "rename" views by duplicating a row and changing the name cell. The "View Definition" field conatins the technical details of the view's filters. BE WARNED: complex task views can max out the excel field and cause major problems during loading. Make sure that parts of the definition string have not been truncated by excell. This category should only be used to edit or move task views with limited numbers of filters.<br />
<br />
----<br />
<br />
*'''Name:''' Name of the task view. This will display in the application and is the only unique id for the task view. It cannot be truly changed once it has been saved.<br />
<br />
*'''Owner:''' This is the username of the person who created the task view from the front end.<br />
<br />
*'''View Definition:''' Techincal description of the view. Basically this field displays the database logic for the task view filters. Complex filters can exceed the cell character limit of excell. Be very careful that parts of this string are not truncated during the copy and paste from ssmt into excell. <br />
<br />
*'''Sort String:''' Can be used to set the order in which the task views display in the application.<br />
<br />
*'''Description:''' Text that displays in the "descrption" field.<br />
<br />
*'''Default:''' Flags that item as the default task view.<br />
<br />
*'''System View:''' If Y, this view is an enterprise view and could be assigned to any user. If N, then it will be a person view available only to the owner.<br />
<br />
*'''Required:''' If Y, this view will be automatically assigned to all users.<br />
<br />
*'''Inactive:''' Allows for the inactivation of task views. If set to Y, the view will be inactivated and it will no longer extract from ssmt. If set to N, then it will continue to be active. Set to N, unless you want it inactivated.<br />
<br />
*'''Security Code:''' Allows you to attach a task view to a certain security classification. <br />
<br />
*'''Create:''' Set to Y for new entries. Set to N if editing an existing entry.<br />
<br />
'''Back to [[SSMT]] main page</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Task_View-Setup&diff=10930SSMT: Task View-Setup2011-03-30T20:17:49Z<p>Charlie.Morris: </p>
<hr />
<div>== Description ==<br />
The Task View-Setup content category is used for editing the configuration of the actual task view. It only contains a few basic rows and can be helpful in moving task views from one environemnt to another. Because task view names cannot be truly changed, this category can be used to "rename" views by duplicating a row and changing the name cell. The "View Definition" field conatins the technical details of the view's filters. BE WARNED: complex task views can max out the excel field and cause major problems during loading. Make sure that parts of the definition string have not been truncated by excell. This category should only be used to edit or move task views with limited numbers of filters.<br />
<br />
----<br />
<br />
*'''Name:''' Name of the task view. This will display in the application and is the only unique id for the task view. It cannot be truly changed once it has been saved.<br />
<br />
*'''Owner:''' This is the username of the person who created the task view from the front end.<br />
<br />
*'''View Definition:''' Techincal description of the view. Basically this field displays the database logic for the task view filters. Complex filters can exceed the cell character limit of excell. Be very careful that parts of this string are not truncated during the copy and paste from ssmt into excell. <br />
<br />
*'''Sort String:''' Can be used to set the order in which the task views display in the application.<br />
<br />
*'''Description:''' Text that displays in the "descrption" field.<br />
<br />
*'''Default:''' Flags that item as the default task view.<br />
<br />
*'''System View:''' If Y, this view is an enterprise view and could be assigned to any user. If N, then it will be a person view available only to the owner.<br />
<br />
*'''Required:''' If Y, this view will be automatically assigned to all users.<br />
<br />
*'''Inactive:''' Allows for the inactivation of task views. If set to Y, the view will be inactivated and it will no longer extract from ssmt. If set to N, then it will continue to be active. Set to N, unless you want it inactivated.<br />
<br />
*'''Security Code:''' Allows you to attach a task view to a certain security classification. <br />
<br />
*'''Create:''' Set to Y for new entries. Set to N if editing and existing entry.<br />
<br />
'''Back to [[SSMT]] main page</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Task_View-Setup&diff=10929SSMT: Task View-Setup2011-03-30T20:12:42Z<p>Charlie.Morris: </p>
<hr />
<div>== Description ==<br />
The Task View-Setup content category is used for editing the configuration of the actual task view. It only contains a few basic rows and can be helpful in moving task views from one environemnt to another. Because task view names cannot be truly changed, this category can be used to "rename" views by duplicating a row and changing the name cell. The "View Definition" field conatins the technical details of the view's filters. BE WARNED: complex task views can max out the excel field and cause major problems during loading. Make sure that parts of the definition string have not been truncated by excell. This category should only be used to edit or move task views with limited numbers of filters.<br />
<br />
----<br />
<br />
*'''Name:''' Name of the task view. This will display in the application and is the only unique id for the task view. It cannot be truly changed once it has been saved.<br />
<br />
*'''Owner:''' This is the username of the person who created the task view from the front end.<br />
<br />
*'''View Definition:''' Techincal description of the view. Basically this field displays the database logic for the task view filters. Complex filters can exceed the cell character limit of excell. Be very careful that parts of this string are not truncated during the copy and paste from ssmt into excell. <br />
<br />
*'''Sort String:''' Can be used to set the order in which the task views display in the application.<br />
<br />
*'''Description:''' Text that displays in the "descrption" field.<br />
<br />
*'''Default:''' Flags that item as the default task view.<br />
<br />
*'''System View:''' If Y, this view is an enterprise view and could be assigned to any user. If N, then it will be a person view available only to the owner.<br />
<br />
*'''Required:''' If Y, this view will be automatically assigned to all users.<br />
<br />
*'''Inactive:''' Allows for the inactivation of task views. If set to Y, the view will be inactivated and it will no longer extract from ssmt. If set to N, then it will continue to be active. Set to N, unless you want it inactivated.<br />
<br />
*'''Security Code:''' Allows you to attach a task view to a certain security classification. <br />
<br />
*'''Create:''' Set to Y for new entries. Set to N if editing and existing entry.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Task_View-Setup&diff=10928SSMT: Task View-Setup2011-03-30T19:37:04Z<p>Charlie.Morris: Created page with "== Description == The Task View-Setup content category is used for editing the configuration of the actual task view. It only contains a few basic rows and can be helpful in movi..."</p>
<hr />
<div>== Description ==<br />
The Task View-Setup content category is used for editing the configuration of the actual task view. It only contains a few basic rows and can be helpful in moving task views from one environemnt to another. Because task view names cannot be truly changed, this category can be used to "rename" views by duplicating a row and changing the name cell. The "View Definition" field conatins the technical details of the view's filters. BE WARNED: complex task views can max out the excel field and cause major problems during loading. Make sure that parts of the definition string have not been truncated by excell. This category should only be used to edit or move task views with limited numbers of filters.</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=SSMT&diff=10927SSMT2011-03-30T19:22:53Z<p>Charlie.Morris: </p>
<hr />
<div>__TOC__<br />
<br />
==Introduction==<br />
* [[Extract and Load via SSMT]]<br />
* [[Excel Formatting for SSMT]]<br />
<br />
==SSMT Content Categories==<br />
* [[SSMT: Additional Information|Additional Information]]<br />
* [[SSMT: Allergen|Allergen]]<br />
* [[SSMT: Answer|Answer]]<br />
* [[SSMT: Answer Class|Answer Class]]<br />
* [[SSMT: Billing Area|Billing Area]]<br />
* [[SSMT: Body Site|Body Site]]<br />
* [[SSMT: Call Processing|Call Processing]]<br />
* [[SSMT: Charge Codes|Charge Codes]]<br />
* [[SSMT: Charge Groups (ICD9)|Charge Groups (ICD9)]]<br />
* [[SSMT: Charge Groups (Procedure)|Charge Groups (Procedure)]]<br />
* [[SSMT: Charge Groups (Visit)|Charge Groups (Visit)]]<br />
* [[SSMT: ChargeMap BillableProvider|ChargeMap BillableProvider]]<br />
* [[SSMT: Chart View - Sections|Chart View - Sections]]<br />
* [[SSMT: Chart View - Users| Chart View - Users]]<br />
* [[SSMT: CPT4 Modifier|CPT4 Modifier]]<br />
* [[SSMT: CPT4 Modifier Groups|CPT4 Modifier Groups]]<br />
* [[SSMT: Document Security Codes|Document Security Codes]]<br />
* [[SSMT: Document Type|Document Type]]<br />
* [[SSMT: Encounter Status|Encounter Status]]<br />
* [[Edit Personal Favorites - SSMT|Editing Personal Favorites]]<br />
* [[SSMT Error Messages|Error Messages]]<br />
* [[SSMT: Menu|Menu]]<br />
* [[SSMT: OID - Additional Information Questions|OID - Additional Information Questions]]<br />
* [[OID - Order Defaults - Insurance]]<br />
* [[SSMT: OID - Order Defaults - Req Perf Location / Site|OID - Order Defaults - Req Perf Location / Site]] <br />
* [[SSMT: OID - Order Defaults - Insurance/PatientLocation/Site|OID - Order Defaults - Insurance/PatientLocation/Site]] <br />
* [[SSMT: OID - Orderable Item Dictionary |OID - Orderable Item Dictionary ]]<br />
** [[OID SSMT Extraction|OID Extraction]]<br />
* [[SSMT: OID OCD Mapping|OID_OCD Mapping]]<br />
* [[SSMT: OrderResults-v11|OrderResults - v11]]<br />
* [[SSMT: Order Modifiers|Order Modifiers]]<br />
* [[SSMT: Order Performing Facility Identifiers|Order Performing Facility Identifiers]]<br />
* [[SSMT: Order Questions|Order Questions]] <br />
* [[SSMT: Pharmacy|Pharmacy]]<br />
* [[SSMT: Performing Location|Performing Location]]<br />
* [[SSMT: Remove Reason|Remove Reason]]<br />
* [[SSMT: Results Where Performed Identifiers|Results Where Performed Identifiers]]<br />
* [[SSMT: RID - Resultable Item Dictionary|RID - Resultable Item Dictionary]]<br />
* [[SSMT: RID - Reference Range|RID - Reference Range]] <br />
* [[SSMT: Site Location|Site Location]]<br />
* [[SSMT: Specimen Source|Specimen Source]]<br />
* [[SSMT: Task View-Setup]]<br />
* [[SSMT: Task View-Users|Task View-Users]]<br />
* [[SSMT: Team|Team]]<br />
* [[SSMT: TW .NET Preferences|TW .NET Preferences]]<br />
* [[SSMT: User Security Classifications|User Security Classifications]]<br />
* [[SSMT: Users / Providers|Users / Providers]]<br />
* [[SSMT: Worklist Views - Users|Worklist Views - Users]]</div>Charlie.Morrishttps://wiki.galenhealthcare.com/index.php?title=Dragon_Overview&diff=8925Dragon Overview2010-07-07T14:33:54Z<p>Charlie.Morris: </p>
<hr />
<div>==Overview==<br />
Versions 9 and 10 of Dragon Naturally Speaking are a huge improvement over previous versions. Coupled with 2GB of RAM, it spits out complex medical terms with remarkable speed and accuracy.<br />
Since Dragon is licensed by user, not by device, there is great flexibility in its deployment.<br />
Multiple customers are experimenting with using [[roaming profiles]] so that the doc's can dictate in exam rooms with the patient along with other Dragon workstations in the office.<br />
In addition to the many [[fundamental Dragon commands]], using the built in templating features of Dragon can be a nice compliment to using text templates and illustrates a powerful application of [[custom Dragon voice commands]]. This allows more granular personalization without adding clutter to the EHR.<br />
One customer, who was not intending to use Dragon on a large scale, saw the demand for it spread like wildfire. After individual doc's started purchasing it on their own, the IS department realized that they needed to roll it out enterprise wide. Now the vast majority of doc's are using it as a full replacement for dictation and transcription costs have been nearly eliminated.<br />
<br />
One area where Dragon does not perform well is in sections of the note that require the inclusion of people's names or proper nouns in general. In these rare circumstances traditional dictation may work best. Dragon does however offer some functions to make the process of incorporating [[proper nouns in Dragon's vocabulary]] a bit easier.<br />
<br />
Of course not all note sections are well suited for Dragon. In areas where capturing discrete data is desired, the use of Medcin templates would be required.<br />
<br />
==Dragon as a prelude to EHR adoption==<br />
<br />
Dragon can be used as an effective way to begin an EHR deployment by allowing the physicians to get an early taste of success.<br />
<br />
6-8 weeks prior to going live with the EHR, the doc's are provided with a Philips Speech Mike and Dragon. In one small practice, all 5 physicians were using Dragon for all of their dictations within a week.<br />
<br />
==Dragon and Citrix==<br />
<br />
We’re using Citrix to present TouchWorks to the users. Because of the resource requirements for Dragon (2GB+ RAM), we decided to install it locally on the client PC’s and access the EHR through Citrix.<br />
<br />
Although using Dragon directly in the application works ok, the accuracy and consistency is better when using the dictation box. Unfortunately when using the EHR in Citrix and Dragon locally on the PC, the ‘Transfer’ button in the Dictation Box is not able to determine where in the application to put the dictated text. The Phillips SpeechMike can be configured to solve this problem of getting the dictated text from the Dictation Box into the TouchWorks application with minimal effort.<br />
<br />
First configure the SpeechMike’s Fast Forward button so that the following commands are issued: - Ctrl-A, Ctrl-C, Tab, Tab, Enter<br />
<br />
This selects the text from the dictation box, copies it to the clipboard, and then closes the dictation box <br />
<br />
So the entire workflow would be something like this.<br />
Press the ‘Insert Overwrites’ button on the microphone to bring up the dictation box <br />
Press the record button to dictate <br />
Press the fast forward button<br />
Click in the appropriate field in the EHR<br />
Using the microphone say "paste that"<br />
<br />
Of course you can always dictate directly into TouchWorks, but the commands don’t seem to work as consistently as they do in the Dictation Box.<br />
<br />
Special Thanks to Melissa Heath for the workflow and programming!</div>Charlie.Morris