https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Larson.Yuill&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T07:29:52ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=Creating_user/provider_in_v11&diff=19228Creating user/provider in v112015-03-31T14:57:54Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:UserManagement|Creating User/Provider in v11]]<br />
== Steps for creating a User/Provider TW account ==<br />
<br />
This is a document used to describe the manual process for creating accounts for Providers that will use note, Rx, charge, order, and etc. utilizing an electronic workflow. I call this the manual process because some of these steps will/can be accomplished using SSMT. It should be understood that although this document will describe all the steps required, it may not drill down to all the details. Additional detailed explanations and screenshots can be added later.<br />
<br />
----<br />
<br />
'''To begin:'''<br />
Log into TWAdmin> TWUser admin> click the Add button.<br />
Usertype dropdown = user/provider> enter Last name> enter First Name> email address> org dropdown = (select the name of the org).<br />
<br />
'''User Details:'''<br />
Enter username> default password> profession> credentials> check the electronic workflow box> finalization authority (provider =8)> <br />
ownership authority (provider =8)(each client will choose the different authority levels based on the role of the user within their own organization, but "8" is fairly standard for a provider)<br />
<br />
'''Provider Detail I:'''<br />
Enter Code (In v10 the code was automatically loaded. In v11 you must assign a unique code to each user. To make it simple and unique, we recommend that you use your orgainizations mnemonic paired with a number i.e. "GHC0001" Galen Healthcare 0001 > Order authority (8)> Primary Specialty> Secondary Specialty> DEA#> DEA expiration> checkbox Billing Provide> checkbox <br />
Schedulable> check the "PCP" box (if primary care)<br />
<br />
'''Provider Detail II:'''<br />
Check the box(s) for prescribe levels 2-4 (as needed),> click “License”> click “add”> select state from the drop down menu> enter License #> enter expiration date> click “OK”> click “cancel”,> enter outbound Dictate ID<br />
<br />
'''Address:''' <br />
If desired fill out the providers address<br />
<br />
'''Security:'''<br />
Highlight “(the name of the org)”> click “Add/Remove” select and highlight security> click the down arrow button> click “OK”<br />
<br />
'''Workplaces:'''<br />
Click “Edit Workspaces” button> click the ellipsis (…) button> click “search”> select the desired workplace (eg.Provider_WP)> click “Save”> click “OK”> Click the “Save button”<br />
<br />
Done with TWAdmin (for now)<br />
<br />
----<br />
<br />
At this stage if you log in as this provider you will get a user agreement message to accept but this is in no way finished for the build. I think this is likely where the separation may be between an IS build for this provider and where "the practice" may finish the build.<br />
<br />
'''Workplaces:'''<br />
Desktop view<br />
Log into TWAdmin> click Work Def Admin on the VTB> in View drop down to Default> search for user> click the down arrow to add the Default clinical desktop view to your user> click save.<br />
<br />
'''Note View:'''<br />
In view, drop down to “Note View”> search for user> click the down arrow> click save. This is for granting note view from the clinical desktop and not to be confused with the view for the note module.<br />
<br />
'''Note (module view):'''<br />
In view, drop down to “Note”> search for the user> click the down arrow> click save. This is needed for the note module and is separate from the note viewer in the clinical desktop.<br />
<br />
'''Worklists:'''<br />
TWAdmin> click Work Def Admin on the VTB> click the “Worklist tab> click the “edit view” button> radio button =“User”> search for user> click Manage Personal tab> select desired worklist by highlighting> click “add to my views”> repeat for all needed> click “close”. (use the description for assistance in determining what to grant each user)<br />
<br />
'''Task Views''':<br />
TWAdmin> Task Admin> Manage personal> click “all”> search for user by Last name, First name> click “OK”> select desired views under Enterprise by highlighting> click “add to my views” (do this for all views needed based on role and site)<br />
<br />
'''Chart Viewer:''' (view for chart NOT desktop views) <br />
TWAdmin> Chart Admin> click “all”> search for user by Last name, First name> click “OK”> highlight “All by section by subsection”> click “set as default”.<br />
<br />
----<br />
<br />
To verify that user was built correctly generally it is advisable to log in as that user perform a quick QA and log out. Then go to TWAdmin> TWuser admin> search for that user> check the box for “require password change”> click “save”. That will force the new user to choose a new password when they themselves sign on. This method of testing is not optimal when building out users on a large scale.<br />
<br />
When creating a large number of users at one time it is best to create "shell users". The shell user is based on role. <br />
For example: "Test1, Nurse" would be a nurse role user set up. This user profile would be built out with all rights, preferences, tasks, views, etc. Once the set up for this role was completed, sign in and testing could be done on the front end. Then that "shell User" profile is copied with the actually user names on the back end or loaded via SSMT.</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Creating_user/provider_in_v11&diff=19227Creating user/provider in v112015-03-31T14:57:05Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:UserManagement|Creating User/Provider in v11]]<br />
== Steps for creating a User/Provider TW account ==<br />
<br />
This is a document used to describe the manual process for creating accounts for Providers that will use note, Rx, charge, order, and etc. utilizing an electronic workflow. I call this the manual process because some of these steps will/can be accomplished using SSMT. It should be understood that although this document will describe all the steps required, it may not drill down to all the details. Additional detailed explanations and screenshots can be added later.<br />
<br />
----<br />
<br />
'''To begin:'''<br />
Log into TWAdmin> TWUser admin> click the Add button.<br />
Usertype dropdown = user/provider> enter Last name> enter First Name> email address> org dropdown = (select the name of the org).<br />
<br />
'''User Details:'''<br />
Enter username> default password> profession> credentials> check the electronic workflow box> finalization authority (provider =8)> <br />
ownership authority (provider =8)(each client will choose the different authority levels based on the role of the user within their own organization, but "8" is fairly standard for a provider)<br />
<br />
'''Provider Detail I:'''<br />
Enter Code (In v10 the code was automatically loaded. In v11 you must assign a unique code to each user. To make it simple and unique, we recommend that you use your orgainizations mnemonic paired with a number i.e. "GHC0001" Galen Healthcare 0001 > Order authority (8)> Primary Specialty> Secondary Specialty> DEA#> DEA expiration> checkbox Billing Provide> checkbox <br />
Schedulable> check the "PCP" box (if primary care)<br />
<br />
'''Provider Detail II:'''<br />
Check the box(s) for prescribe levels 2-4 (as needed),> click “License”> click “add”> select state from the drop down menu> enter License #> enter expiration date> click “OK”> click “cancel”,> enter outbound Dictate ID<br />
<br />
'''Address:''' <br />
If desired fill out the providers address<br />
<br />
'''Security:'''<br />
Highlight “(the name of the org)”> click “Add/Remove” select and highlight security> click the down arrow button> click “OK”<br />
<br />
'''Workplaces:'''<br />
Click “Edit Workspaces” button> click the ellipsis (…) button> click “search”> select the desired workplace (eg.Provider_WP)> click “Save”> click “OK”> Click the “Save button”<br />
<br />
Done with TWAdmin (for now)<br />
<br />
----<br />
<br />
At this stage if you log in as this provider you will get a user agreement message to accept but this is in no way finished for the build. I think this is likely where the separation may be between an IS build for this provider and where "the practice" may finish the build.<br />
<br />
'''Workplaces:'''<br />
Desktop view<br />
Log into TWAdmin> click Work Def Admin on the VTB> in View drop down to Default> search for user> click the down arrow to add the Default clinical desktop view to your user> click save.<br />
<br />
'''Note View:'''<br />
In view, drop down to “Note View”> search for user> click the down arrow> click save. This is for granting note view from the clinical desktop and not to be confused with the view for the note module.<br />
<br />
'''Note (module view):'''<br />
In view, drop down to “Note”> search for the user> click the down arrow> click save. This is needed for the note module and is separate from the note viewer in the clinical desktop.<br />
<br />
'''Worklists:'''<br />
TWAdmin> click Work Def Admin on the VTB> click the “Worklist tab> click the “edit view” button> radio button =“User”> search for user> click Manage Personal tab> select desired worklist by highlighting> click “add to my views”> repeat for all needed> click “close”. (use the description for assistance in determining what to grant each user)<br />
<br />
'''Task Views''':<br />
TWAdmin> Task Admin> Manage personal> click “all”> search for user by Last name, First name> click “OK”> select desired views under Enterprise by highlighting> click “add to my views” (do this for all views needed based on role and site)<br />
<br />
'''Chart Viewer:''' (view for chart NOT desktop views) <br />
TWAdmin> Chart Admin> click “all”> search for user by Last name, First name> click “OK”> highlight “All by section by subsection”> click “set as default”.<br />
<br />
----<br />
<br />
To verify that user was built correctly generally it is advisable to log in as that user perform a quick QA and log out. Then go to TWAdmin> TWuser admin> search for that user> check the box for “require password change”> click “save”. That will force the new user to choose a new password when they themselves sign on. This method of testing is not optimal when building out users on a large scale.<br />
<br />
When creating a large number of users at one time it is best to create "shell users". The shell user is based on role. <br />
For example: "Test1, Nurse" would be a nurse role user set up. This user profile would be built out with all rights, preferences, tasks, views, etc. Once the set up for this role was completed, sign in and testing could be done on the front end. Then that "shell User" profile is copied with the actualy user names on the back end or loaded via SSMT.</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Order_Groups&diff=19157Order Groups2015-03-04T19:11:40Z<p>Larson.Yuill: /* Order Groups */</p>
<hr />
<div>==Order Groups==<br />
<br />
<br />
Order Groups are a new addition to Touchworks EHR in version 11.4.1. They enable users to define a set of favorite orders and save them as an '''Order Group''' folder in the ACI. These folders can be accessed from the My Favorites list, Specialty Favorites and Quicklists. They are not available in Master Search screens. <br />
<br />
<br />
These folders allow users to group all types of common orders in one place for ease of ordering. They can contain items from:<br />
*RX<br />
*Med Admin<br />
*Laboratory<br />
*Radiology<br />
*Procedures<br />
*Immunizations<br />
*Supplies<br />
*Referral/Follow-up<br />
*Instructions<br />
Order Groups are similar to problem based Care Guides but can be grouped based on user preference (by diagnosis, by provider, by visit type etc.) and can be managed by the user through a new page called '''Organize Favorites'''.<br />
<br />
<br />
===Benefits of Using Order Groups===<br />
<br />
<br />
*Order Groups help to optimize the EHR ordering processs by eliminating the clicks required to move from tab to tab while searching for individual items in multiple areas, as common orders are grouped together in one place. <br />
*Order Groups can act as a reminder to the user, of required items (as in age specific immunizations)<br />
*Can be used to facilitate MU2 workflows for CPOE (Core 1) and Patient Education (Core 13).<br />
**MU2 Core 1-CPOE (Computerized provider order entry) requires that 60% of medications, 30% of radiology orders and 30% of Labs be created using the CPOE function. Ordering from an Order Group will meet that requirement.<br />
**MU2 Core 13 Patient Education '''''requires''''' that Instructions be ordered via: '''Order Groups''', CareGuides, Qsets or Info Button.<br />
**By ordering the Education/Instruction orderable from within an Order Group the user will receive MU2 credit. (Ordering Education or Instructions from the ACI will no longer meet the measure.)<br />
*Can be easily built by users in the Organize Favorites section and therefore, can be provider specific<br />
*Can be shared with Clinical Staff to standardize ordering. (Staff will know this is the specific test preferred by their provider)<br />
<br />
<br />
===Building an Order Group===<br />
<br />
<br />
This workflow was shared by Mark H. Pearlman M.D., Sr. Solutions Architect for Allscripts in a Webcast “How to Get an Hour Back In My Day” presented on Feb. 18, 2015 and also detailed in the “Enhancement Supplement-Order Groups” found in Allscripts Product Documentation on Client Connect.<br />
<br />
It is a prerequisite for this workflow that all items to be added to the Order Group exist in the Favorites list.<br />
<br />
<br />
When adding to an order group the process should be to:<br />
#Select the Tab in the ACI that contains one of the orders you wish to include in your Order Group.<br />
#Right Click anywhere in the blank area of the Tab page selected<br />
#Click on '''Organize Favorites''' from the Context Menu [[File: Fav_et_4.png|200px]]<br />
##All orderable items in your My Favorites list and any existing Order Groups will be displayed<br />
#Select '''New Order Group''' (at bottom of page) > A folder is created at bottom of the list<br />
#Click on '''Rename''' > Create a unique name for your Order Group <br />
#Click on '''Close''' [[File: Fav_et_5.png|400px]]<br />
#Right Click anywhere in the blank area of the Tab page selected<br />
#Click on''' Organize Favorites''' from the Context Menu<br />
#Select one or more items by holding down the '''CTRL''' key and clicking on Items<br />
#Click on '''Copy Item''' -''Highly recommended ''<br />
##using Move Item or Drag and Drop will remove the item from the Favorites list and should be used with caution<br />
#From this screen Click on the '''Order Group''' you just created <br />
#Click '''OK'''<br />
##Orders have been added to the Group <br />
#Click '''Close''' <br />
##You are returned to the ACI.<br />
You can now add any additional items from any tab in the ACI <br />
*select the tab containing needed orderables and follow steps 7-13<br />
<br />
<br />
''Note'': The new Order Group is not displayed in ACI until you add an order to it, but it will display in Organize Favorites screen.</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=19146Acronyms, Abbreviations & Other Definitions2015-03-02T19:43:04Z<p>Larson.Yuill: /* C */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry (AKA: Additional Information Question)<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIE - Common Interface Engine - <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CPM- Allscripts Clinical Performance Management software. Used to calculate the data for MU 2 Measures.<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Provider Order Entry, industry term. The electronic entry by a provider of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2015.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of providers in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the providers in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MARS - Meaningful Use Attestation Readiness Service (Allscripts term)<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===U===<br />
*UAT - User Accepted Testing <br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VBC – Value Based Care - A medical service reimbursement structure based on bundle payments or full capitation rather than the traditional fee for service<br />
<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=19145Acronyms, Abbreviations & Other Definitions2015-03-02T19:34:45Z<p>Larson.Yuill: /* Acronyms */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry (AKA: Additional Information Question)<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CPM- Allscripts Clinical Performance Management software. Used to calculate the data for MU 2 Measures.<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Provider Order Entry, industry term. The electronic entry by a provider of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2015.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of providers in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the providers in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MARS - Meaningful Use Attestation Readiness Service (Allscripts term)<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===U===<br />
*UAT - User Accepted Testing <br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VBC – Value Based Care - A medical service reimbursement structure based on bundle payments or full capitation rather than the traditional fee for service<br />
<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=18924Acronyms, Abbreviations & Other Definitions2014-12-12T20:37:38Z<p>Larson.Yuill: </p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry (AKA: Additional Information Question)<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CPM- Allscripts Clinical Performance Management software. Used to calculate the data for MU 2 Measures.<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Provider Order Entry, industry term. The electronic entry by a provider of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2015.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of providers in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the providers in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MARS - Meaningful Use Attestation Readiness Service (Allscripts term)<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===U===<br />
*UAT - User Accepted Testing <br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=18923Acronyms, Abbreviations & Other Definitions2014-12-12T20:22:11Z<p>Larson.Yuill: /* A */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry (AKA: Additional Information Question)<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CPM- Allscripts Clinical Performance Management software. Used to calculate the data for MU 2 Measures.<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Provider Order Entry, industry term. The electronic entry by a provider of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2015.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of providers in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the providers in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MARS - Meaningful Use Attestation Readiness Service (Allscripts term)<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=18922Acronyms, Abbreviations & Other Definitions2014-12-12T20:18:11Z<p>Larson.Yuill: /* M */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CPM- Allscripts Clinical Performance Management software. Used to calculate the data for MU 2 Measures.<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Provider Order Entry, industry term. The electronic entry by a provider of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2015.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of providers in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the providers in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MARS - Meaningful Use Attestation Readiness Service (Allscripts term)<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=18750Acronyms, Abbreviations & Other Definitions2014-09-08T21:14:02Z<p>Larson.Yuill: /* G */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
*GPAC - Galen Partner Advisory Council<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2013.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=18749Acronyms, Abbreviations & Other Definitions2014-09-08T21:10:39Z<p>Larson.Yuill: /* H */</p>
<hr />
<div>{{Toc}}<br />
<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*ABN - Advanced Beneficiary Notice of Noncoverage. See CMS link for additional information.[http://www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf] <br />
<br />
*ACI - [[Add Clinical Item]]<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ACO - [[Accountable Care Organization]]<br />
<br />
*[[ADBR]] - Application Design and Behavior Resource. A tool provided from Allscripts for configuring and troubleshooting.<br />
<br />
*[http://wiki.galenhealthcare.com/Allscripts_ADM_/_TouchChart_/_Scan#Allscripts_ADM_.2F_TouchChart_.2F_Scan ADM] - Allscripts Document Management (formerly known as Scan module)<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - [[Allscripts Enterprise EHR]]<br />
<br />
*AE-PM - Allscripts Enterprise Practice Management<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*ANR - Available Next Release - Allscripts term referring to functionality that exists in a future version<br />
<br />
*AOE - Ask at Order Entry<br />
<br />
*ARN - [[Allscripts Referral Network]]<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*CCHIT - Certification Commission for Health Information Technology- is an independent, not-for-profit group that certifies electronic health records.<br />
<br />
*[[CCI]] - Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CDA - Clinical Document Architecture<br />
<br />
*CCF - Client Confirmation Form<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*CDI - Clinical Documentation Improvement (pertaining to ICD-10 documentation requirements)<br />
<br />
*CDS - Clinical Decision Support<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CEHRT - Certified EHR Technology<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CQM - Clinical Quality Measure<br />
<br />
*CSS - Communications Sub-System (used with Allscripts' Printing Solution)<br />
<br />
*[[Cardiology]] - Specializing in disorders and/or diseases of the cardiovascular system.<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*Dx - is used in medical shorthand to mean "Diagnosis" <br />
<br />
[[#top|Top]]<br />
<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*E/M Coder – Evaluation and Management Coder. Provides decision support for the clinician, assisting in their review of the clinical note when determining the level of service for the encounter. <br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Provider. This is a [[Meaningful Use]] term and refers to a provider who is eligible to participate in the Medicaid or Medicare reimbursement programs.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
*FoS - Term commonly used to a Result Document, but can relate to any Note/Document in Enterprise EHR that is set to 'Finalize on Save.'<br />
*FYI - The FYI button is found on the Patient Banner and is used to place notes related to a patient the way a sticky note could be used on a chart. When there is text/data in the FYI field the button is yellow. <br />
*[[Family_Medicine | Family Medicine]] <br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphical User Interface<br />
<br />
[[#top|Top]]<br />
<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare Procedural Coding System. (Coders refer to it as "Hix Pix".)<br />
<br />
*[[Ncqa | HEDIS]] - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*HF - Hot Fix version<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] - Health Information Exchange<br />
<br />
*HIMMS - Healthcare Information and Management Systems Society<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*HISP - Health Information Service Provider<br />
<br />
*[[HIT]] - Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information usually contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar; the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*[[ICD-9]] - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2013.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] - Integrating the Healthcare Enterprise<br />
<br />
*IMO - Intelligent Medical Object. A privately held company specializing in developing, managing and licensing medical vocabularies. IMO partners with various health care organizations, medical content providers and EHR developers. [http://www.e-imo.com/]<br />
<br />
*IPA - Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA.<br />
<br />
*ISO - International Organization for Standardization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
*LOINC - Logical Observation Identifiers Names and Codes. Applies universal code names and identifiers to medical terminology related to electronic health records. <br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*MAPI - Acronym for clinical data (Meds, Allergies, Problems, Immunizations)<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]] - National Drug Code<br />
<br />
*[[NPI]] - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH - Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP - Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System<br />
<br />
*[[PMT]] - Problem Mapping Tool <br />
<br />
*POC - Point of care (generally referring to in office)<br />
<br />
*[[PQRI]] - Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
*[[Pack_years | Pack Years]]<br />
<br />
*[[Passthrough_Interfaces | Passthrough Interface]]<br />
<br />
*[[Patient_Bridge | Patient Bridge]]<br />
<br />
*[[Pediatrics]]<br />
<br />
*[[Preventative_care | Preventative Care]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*REC - Regional Extension Center: an organization that has received funding under the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to assist health care providers with the selection and implementation of electronic health record (EHR) technology.<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*[[Radiology]]<br />
<br />
*[[Results:_AutoFiler | Results AutoFiler]]<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - [[System Environment Specification (SES)|System Environment Specification]] - Allscripts term<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SNOMED - Systematized Nomenclature of Medicine<br />
<br />
*[[Database / SQL|SQL]] - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TES – Transaction Editing Software<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*Tx - Medical shorthand for treatment<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN – Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18748System Optimization2014-09-08T17:10:05Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size, understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the process to complete one as well as examples on types and levels of optmizations. <br />
<br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:Optimization.Webcast.PDF._09.05.14..pdf|Download slideshow]]<br/><br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
'''Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?'''<br />
<br />
'''A:''' A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediately after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to start is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice alerts there are so many. In the example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
'''Q: We are a small organization, would our practices benefit from doing an optimization?'''<br />
<br />
'''A:''' All organization of any size should perform optimizations on their system. If not a onetime full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
'''Q: What are your suggestions for questions to ask end users as we prepare for an optimization?'''<br />
<br />
'''A:''' Some questions to ask your users are: Are there any bottlenecks that are noticeable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day. These are just a few questions that can be offered. The purpose should be to get your end users also involved and open to the process. <br />
<br />
<br />
'''Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?'''<br />
<br />
'''A:''' Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'hear' them and are performing the system optimizations to improve any issues.<br />
<br />
<br />
'''Q: How do we get a configuration workbook?'''<br />
<br />
'''A:''' Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to particular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what an organization should use for a CW tool and what it should look like.<br />
<br />
<br />
'''Q: How does a Configuration Workbook differ from a change log?'''<br />
<br />
'''A:''' A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involved and should be a document to record not only the system itself but everything surrounding it. For example the system version that is running currently and previously, dates and times of installs, interfaces and the venders involved, any deviation from certified workflows, standardized build pieces, etc. As mentioned there is a Galen blog article regarding this called, "It's All in Your Head" written by Larson Yuill and a link is attached to the slides presented as well as here.<br />
http://blog.galenhealthcare.com/2014/06/16/its-all-in-your-head/</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18747System Optimization2014-09-08T17:02:37Z<p>Larson.Yuill: /* Webcast materials */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the porcess to complete one as well as examples on types of optmizations. <br />
<br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:Optimization.Webcast.PDF._09.05.14..pdf|Download slideshow]]<br/><br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
'''Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?'''<br />
<br />
'''A:''' A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediately after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to start is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice them there are so many. In that example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
'''Q: We are a small organization, would our practices benefit from doing an optimization?'''<br />
<br />
'''A:''' All organization of any size should perform optimizations on their system. If not a onetime full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
'''Q: What are your suggestions for questions to ask end users as we prepare for an optimization?'''<br />
<br />
'''A:''' Some questions to ask your users are: Are there any bottlenecks that are noticeable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day.<br />
<br />
<br />
'''Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?'''<br />
<br />
'''A:''' Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'hear" them and performing the system optimizations to improve any issues.<br />
<br />
<br />
'''Q: How do we get a configuration workbook?'''<br />
<br />
'''A:''' Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to particular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what an organization should use for a CW tool and what it should look like.<br />
<br />
<br />
'''Q: How does a Configuration Workbook differ from a change log?'''<br />
<br />
'''A:''' A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involved and should be a document to record not only the system itself but everything surrounding it. For example the system version that is running currently and previously, dates and times of installs, interfaces and the venders involved, any deviation from certified workflows, standardized build pieces, etc. As mentioned there is a Galen blog article regarding this called, "It's All in Your Head" written by Larson Yuill and a link is attached to the slides presented as well as here.<br />
http://blog.galenhealthcare.com/2014/06/16/its-all-in-your-head/</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=File:Optimization.Webcast.PDF._09.05.14..pdf&diff=18746File:Optimization.Webcast.PDF. 09.05.14..pdf2014-09-08T16:57:49Z<p>Larson.Yuill: System Optimization Webcast slides presented 9/5/2014</p>
<hr />
<div>System Optimization Webcast slides presented 9/5/2014</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18745System Optimization2014-09-08T16:34:59Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the porcess to complete one as well as examples on types of optmizations. <br />
<br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:]]<br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
'''Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?'''<br />
<br />
'''A:''' A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediately after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to start is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice them there are so many. In that example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
'''Q: We are a small organization, would our practices benefit from doing an optimization?'''<br />
<br />
'''A:''' All organization of any size should perform optimizations on their system. If not a onetime full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
'''Q: What are your suggestions for questions to ask end users as we prepare for an optimization?'''<br />
<br />
'''A:''' Some questions to ask your users are: Are there any bottlenecks that are noticeable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day.<br />
<br />
<br />
'''Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?'''<br />
<br />
'''A:''' Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'hear" them and performing the system optimizations to improve any issues.<br />
<br />
<br />
'''Q: How do we get a configuration workbook?'''<br />
<br />
'''A:''' Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to particular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what an organization should use for a CW tool and what it should look like.<br />
<br />
<br />
'''Q: How does a Configuration Workbook differ from a change log?'''<br />
<br />
'''A:''' A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involved and should be a document to record not only the system itself but everything surrounding it. For example the system version that is running currently and previously, dates and times of installs, interfaces and the venders involved, any deviation from certified workflows, standardized build pieces, etc. As mentioned there is a Galen blog article regarding this called, "It's All in Your Head" written by Larson Yuill and a link is attached to the slides presented as well as here.<br />
http://blog.galenhealthcare.com/2014/06/16/its-all-in-your-head/</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18744System Optimization2014-09-08T16:32:16Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
_TOC_<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the porcess to complete one as well as examples on types of optmizations. <br />
<br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:]]<br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
'''Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?'''<br />
<br />
'''A:''' A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediately after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to start is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice them there are so many. In that example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
'''Q: We are a small organization, would our practices benefit from doing an optimization?'''<br />
<br />
'''A:''' All organization of any size should perform optimizations on their system. If not a onetime full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
'''Q: What are your suggestions for questions to ask end users as we prepare for an optimization?'''<br />
<br />
'''A:''' Some questions to ask your users are: Are there any bottlenecks that are noticeable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day.<br />
<br />
<br />
'''Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?'''<br />
<br />
'''A:''' Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'hear" them and performing the system optimizations to improve any issues.<br />
<br />
<br />
'''Q: How do we get a configuration workbook?'''<br />
<br />
'''A:''' Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to particular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what an organization should use for a CW tool and what it should look like.<br />
<br />
<br />
'''Q: How does a Configuration Workbook differ from a change log?'''<br />
<br />
'''A:''' A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involved and should be a document to record not only the system itself but everything surrounding it. For example the system version that is running currently and previously, dates and times of installs, interfaces and the venders involved, any deviation from certified workflows, standardized build pieces, etc. As mentioned there is a Galen blog article regarding this called, "It's All in Your Head" written by Larson Yuill and a link is attached to the slides presented as well as here.<br />
http://blog.galenhealthcare.com/2014/06/16/its-all-in-your-head/</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18743System Optimization2014-09-08T16:26:55Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
_TOC_<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the porcess to complete one as well as examples on types of optmizations. <br />
<br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:]]<br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
""Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?""<br />
<br />
""A:"" A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediately after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to start is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice them there are so many. In that example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
""Q: We are a small organization, would our practices benefit from doing an optimization?""<br />
<br />
""A:"" All organization of any size should perform optimizations on their system. If not a onetime full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
""Q: What are your suggestions for questions to ask end users as we prepare for an optimization?""<br />
<br />
""A:"" Some questions to ask your users are: Are there any bottlenecks that are noticeable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day.<br />
<br />
<br />
""Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?""<br />
<br />
""A:"" Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'hear" them and performing the system optimizations to improve any issues.<br />
<br />
<br />
""Q: How do we get a configuration workbook?""<br />
<br />
""A:"" Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to particular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what an organization should use for a CW tool and what it should look like.<br />
<br />
<br />
""Q: How does a Configuration Workbook differ from a change log?""<br />
<br />
""A:"" A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involved and should be a document to record not only the system itself but everything surrounding it. For example the system version that is running currently and previously, dates and times of installs, interfaces and the venders involved, any deviation from certified workflows, standardized build pieces, etc. As mentioned there is a Galen blog article regarding this called, "It's All in Your Head" written by Larson Yuill and a link is attached to the slides presented as well as here.<br />
http://blog.galenhealthcare.com/2014/06/16/its-all-in-your-head/</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18742System Optimization2014-09-08T16:15:00Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
_TOC_<br />
<br />
==Webcast details==<br />
This webcast was created to help organizations of any size understand the importance of doing a system optimization after go-live. During this webcast listeners heard <br />
what a System Optimization is, why one needs to be performed, the porcess to complete one as well as examples on types of optmizations. <br />
<br />
Originally aired: Friday September 5, 2014<br/><br />
Presenters: Larson Yuill & Melanie Rudd<br />
<br />
<br />
==Webcast materials==<br />
[[Media:]]<br />
Presented 9/5/2014<br />
<br />
==Q&A==<br />
""Q: We are a small organization with just a few providers, what areas should we focus on for quick optimization?""<br />
<br />
""A:"" A good place to start is to do a Tasking-Workflow optimization. It is a great one to start with and results can be see soon after the resolution plan is put into place. Almost immediatley after this objective is decided on your org can begin creating views to capture outstanding tasks, run some reports to see where your numbers are.<br />
Another good place to staert is to optimize system preferences. Users have a tendency to get alert over load. I have heard clients say that their user don’t even notice them there are so many. In that example I gave during the presentation that org was not set up effectively nor were they in compliance with state regulations. <br />
<br />
<br />
""Q: We are a small organization, would our practices benefit from doing an optimization?""<br />
<br />
""A:"" All organization of any size should perform optimizations on thier system. If not a one time full system optimization from top to bottom, a continuous process to effectively maintain your system at peak. <br />
<br />
<br />
""Q: What are your suggestions for questions to ask end users as we prepare for an optimization?""<br />
<br />
""A:"" Some quesations to ask your users are: Are there any bottlenecks that are noticable during a patient visit? Do patients seem to stack up anywhere during the patient visit? Is there something you do on paper still that would improve patient care if it was done within the EHR? Give one example of your most challenging task or responsibility throughout the day.<br />
<br />
<br />
""Q: Do you have any suggestions for end user buy in? Making changes to workflows post go live, when users are still struggling to get familiar with the system?""<br />
<br />
""A:"" Your users are immediately going to feel like the changes are making them spend more time on each task and taking time away from patient care. So making them aware that the org is striving to improve all processes should increase user buy in. Just let them know you 'Hear" them and perfoming the system optimizations to improve any issues.<br />
<br />
<br />
""Q: How do we get a configuration workbook?""<br />
<br />
""A:"" Depending on your software vender you should contact your support or sales representative to supply you with something to get you started. As always you can reach out to Galen for guidance in this area. Galen is working on a CW template now for client use. Allscript Client Connect has several of them that are specific to partifular items. For example, The MU2 Package install has one and it is inclusive of all the items involved in that install. It is a good example of what a organization should use for a CW tool should look like.<br />
<br />
""Q: How does a Configuration Workbook differ from a change log?""<br />
<br />
""A:"" A change log is used to document any changes requested and/or made to the current system at that time. A Configuration Workbook is much more involeved and should be a document to recored not only the system itself but everything surrounding it. For example the system version that is running, dates and times of install, interfaces and what venders,</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=System_Optimization&diff=18741System Optimization2014-09-08T15:22:01Z<p>Larson.Yuill: Created page with "Category:Webcasts _TOC_ ""Webcast details"" This webcast was created to help organizations understand the importance of doing a system optimization after go-live."</p>
<hr />
<div>[[Category:Webcasts]]<br />
_TOC_<br />
<br />
""Webcast details""<br />
This webcast was created to help organizations understand the importance of doing a system optimization after go-live.</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Orderable_Item_Dictionary&diff=16961Orderable Item Dictionary2013-10-30T21:33:47Z<p>Larson.Yuill: </p>
<hr />
<div>==Description==<br />
The Orderable Item Dictionary (OID) is the dictionary that holds a list of the unique order entries. It is used to define items that are ordered through the user interface. This is typically built based on the compendium from your primary vendor, Allscripts delivered items, and may also include tests from your other vendors and/or custom built tests created for an organization or site. Ultimately this is the list of orders that the user will have the ability to order from the [[Add Clinical Item|ACI]] within Enterprise EHR (assuming they are set as orderable and users are allowed to order the test in the OID). There are several different types of orderable items:<br />
<br />
#Rx - Orderable items with an order type of medication are accessible for ordering. The RX 'type' orders are then further separated into two categories. Medications delivered, maintained and enforced via Medi-Span updates and locally/Allscripts defined medications and vaccines. <br />
#Lab/Procedures - Orderable items with an order type of Lab, Other Diagnostics or Clinical Findings are accessible for ordering. <br />
#Imaging - Orderable items with an order type of Diagnostics Imaging are accessible for ordering. <br />
#Follow-Up/Referral - Orderable items with an order type of Follow Up (including Text Reminders) or Referral are accessible for ordering. <br />
#Instructions - Orderable items with an order type of Instructions or Precautions are accessible for ordering.<br />
#Immunizations - Orderable items with an order type of Medications under the medication class Vaccines are accessible for ordering. <br />
#Supplies - Orderable items with an order type of Supplies are accessible for ordering.<br />
#Med Admin - Ordering administration of medications internally (in office).<br />
<br />
There are 2 entry methods to populate the OID:<br />
<br />
#SSMT – Bulk loading. This is very beneficial when dealing with a large number of items. Some configurations pertaining to orderables can ONLY be done in SSMT. <br />
#TWAdmin - This is a more simple or manual process and is a better way to add or modify a few items that don’t need advanced configuration (i.e. assigning certain defaults).<br />
<br />
To learn more about building the OID please refer to [[V11 Order and Result Dictionary Build and Synchronization]].<br />
<br />
'''Version Information'''<br />
*[[Article Creation|Article Created based on version]]: 11.1.1<br />
*[[Article Last Update|Last Updated with version]]: 11.1.7<br />
<br />
==Data Grid & Overview==<br />
The dictionary itself is broken down into 2 main classifications, medication and non-medication orderable items. The main data grid displays the set of items that can be ordered, received as resulted orders, recorded as resulted orders, as well as entries used for the<br />
classification of other orderable items. Entries could include medications, patient instructions, laboratory items, and radiology items.<br />
<br />
[[Image:Orderable Item.jpg]]<br />
<br />
*'''Code''' - the data parameters for the "Code" field indicate that the entry must be unique within the OID and be 10 characters or less. This code is typically obtained from the organization's lab vendor. <br />
*'''Name''' - the "Name" field indicates that dictionary entry name.<br />
*'''Mnemonic''' - the "Mnemonic" field is similar to the "Code" field in that it shares the same data requirements; the entry must be unique to all other order entries and be 10 characters or less.<br />
*'''Inactive''' - the "Inactive" check-box indicates whether or not the orderable item is "Active". A mark in the check-box indicates that the orderable item is inactive. This field also controls the "OID Mode" field in the Initial details section of the OID. (See below)<br />
*'''Enforced''' - the "Enforced" check-box indicates if the entry is included in the configuration of the application and cannot be removed.<br />
<br />
==Initial==<br />
<br />
[[Image:Initial.jpg]]<br />
<br />
This section is for an orderable item’s specific identifying and defining data. (All) <br />
<br />
In Allscripts Enterprise EHR versions earlier than 11.2, only one OCD entry can be linked to one OID entry. With version 11.2 and later, one OCD entry can be linked to multiple OID entries. However, an OID entry can be linked to only one OCD entry.<br />
<br />
When “Recorded Only” is selected in the Orderable Via control, the orderable item is only entered through the Allscripts Enterprise EHR user interface and not sent electronically to a performing location. When this option is selected, then the “Record w/o Ordering” control in the Order Details form defaults to checked, however the control remains enabled for a user to uncheck and actually order the item.<br />
<br />
*'''Display Name''' - indicates the name that displays in the application for the test. If the display name and the order name on the data grid are different, the system will cross reference during an ACI search.<br />
*'''Linked OCD''' - indicates a linked OCD (if exists). Linked OCD will drive modifier behaviors for the lab test.<br />
*'''Orderable check-box''' - indicates whether the dictionary entry is an Orderable Item or a Parent Class.<br />
*'''Complex check-box''' - used for a collection of items that can be performed without ordering. This check-box currently is only supported with the set up of Vital Panels and should not be utilized when building orderable items.<br />
*'''Orderable Via''' - indicates how the item can be ordered (such as, interface or lab).<br />
*'''OID Mode''' - indicates the mode while the item is built. The mode is controlled by the "Inactive" check-box in the OID data grid.<br />
*'''Order Type''' - indicates where this item falls in the hierarchy (display only field). The Order Type is also an indication of where an orderable item can be found in the ACI.<br />
*'''Modifier Picklists''' - organizations can assign up to three modifier picklists to orderable items. Up to three default modifiers from the picklists can be assigned. Modifier picklists allow for documentation of additional information on a particular orderable item. Modifier picklists only allow for entry of information through drop down fields. (see Additional Information Questions as a more flexible alternative)<br />
*'''Required to Save''' — the Required to Save options indicate if this modifier information is required to save.<br />
<br />
==Child Orders==<br />
<br />
This section becomes available when the Complex control in the Initial section is checked indicating that the orderable item is composed of more than one orderable item. Typically, a complex orderable item is a panel for a vital signs panel that contains several singular vital signs orderable items. Currently, the system only supports Complex orders for Vitals. (Complex orderable items)<br />
<br />
==Medication==<br />
<br />
[[Image:Medication.jpg]]<br />
<br />
This section is for data specific to an orderable item of the medication type. (Medication order type only) <br />
<br />
*'''NDC''' - (National Drug Code) Universal standard drugs number that’s defaulted from Medispan.<br />
*'''DDI''' - Medispan internal identifier that is used for drug- drug checking, etc.<br />
*'''Control Substance Code''' - indicates scheduled drugs. Drives narcotic behavior. Choices are: Sched 1-5.<br />
*'''Route of Admin''' - determines the default route to administer the drug. It’s possible to have more than one route of admin (need link to what’s available) from the Sig.<br />
*'''Medication Package Size''' — determines what package size of this the medication to dispense to the patient.<br />
*'''Critical Admin check-box''' – determines if the medication should be considered important when it is overdue.<br />
*'''Keep On Person Prohibited check-box''' — determines if the patient should or should not carry the medication on their person.<br />
*'''GPI, UPC, HRI''' — identifies products. Enabled for user defined products only.<br />
<br />
==Results==<br />
<br />
[[Image:Results.jpg]]<br />
<br />
This section is for associating resultable items with an orderable item that is resultable. (Non-medication order type only) <br />
<br />
The sequence of the items in the grid can be changed using OrderResult - V11 SSMT content category or by selecting a row and dragging it to a new position, above or below, another row. The sequence of items in this grid is the same sequence that the items appear in the Results Item(s) section of the Results tab for the Order Details form.<br />
<br />
*'''RID Selector''' - Clicking on this link will prompt a dialog that allows an administrator to create an association between resultable items and the orderable item.<br />
*'''Results History''' - This check-box indicates whether any historical results for the orderable item should be displayed or suppressed in the Order Details or the Order Viewer.<br />
*'''Resultable Via''' - Controls the method for entering results into the system. The entries in the picklist are described below.<br />
**User - The "user" entry indicates that results for this order can only be entered by a user<br />
**Interface - The "interface" entry indicates that results for this order can only be entered through an interface with an external system. (Note: When sent to interface users will not be able to enter results manually)<br />
**User or Interface - Combination of the options above. This entry allows entry of result data either manually or through an interface with an external system.<br />
<br />
==Instructions==<br />
<br />
[[Image:Instructions.jpg]]<br />
<br />
This section is for adding additional explanatory information about the orderable item for the application user and the patient. (All) <br />
<br />
The information contained in the Order Instructions field populates the Order Instructions control in the Additional Details section of the Order Details form. <br />
<br />
The questions selected in the Additional Information Questions control are added to the Clinical Questions section in the Order Entry tab of the Order Details form for the orderable item, where they are to be answered when the item is ordered. Additional Information Questions can also be added to a higher level class via the OID - Additional Information Questions content category in SSMT<br />
<br />
*'''Order Instructions''' - free text instructions for the lab.<br />
*'''Patient Instructions''' - free text instructions for the patient. If preloaded for the appropriate orderable in the OID these instructions will appear on the requisition if one is generated.<br />
*'''Must Read Order Instructions''' - when checked the "Additional Details" section is expanded in the "Order Details" at the time of order.<br />
*'''Additional Information Questions''' - additional information questions for the lab appear on the Order Detail page. The sequence of additional information questions can be sequenced.<br />
**Additional Information Questions allow for documentation of required information on an orderable item. The options for data entry in these fields include text, picklist, and date/time data. There is no limit to the number of additional information questions that can be associated with an order. <br />
**Additional Information Questions are similar to the Modifier Picklist entries, but the Additional Information Questions are much more flexible in terms of data entry types, number of items that can be associated with an order, and facilitating workflow.<br />
<br />
==Charge/MN==<br />
[[Image:ChargeMN.jpg]]<br />
<br />
This section is for the cost/charge details that may be associated with the orderable item. (All)<br />
<br />
For an order to participate in Medical Necessity Checking when the order is set to never charge, the CPT code needs to be entered in the CPT4 Code field.<br />
<br />
*'''When to Charge''' - Indicates whether or not a charge should apply to an orderable item. The entries are described below.<br />
**Never<br />
**Upon Completion<br />
**On Order<br />
**When Resulted<br />
*'''Charge Code''' - This field becomes available for selection based on the entry that is selected in the "When to Charge" field. The link allows for an administrator to select a charge code from the charge code dictionary. The code(s) designated in this field will be the codes that drop to the encounter form when the criteria of the "When to Charge" field are met. <br />
*'''CPT 4 Code''' - This field is only available when the "When to Charge" field is set to "Never". This is a free text box that can be used to enter the CPT 4 code for the orderable item. The entry in this field will allow for orderable item to participate in Medical Necessity Checking (LMRP). <br />
*'''CPT4 Text''' — Free text for CPT 4 description. This field is strictly for documentation within the OID and has no impact on the end-user.<br />
*'''Admin Initial Charge Code''' - This field only applies to medications and immunizations. The link allows for an administrator to associate an administration code that would drop to the encounter form once the order has met the criteria specified in the "When to Charge" field. <br />
*'''Admin Additional Charge Code''' - Allows for a second administration code which generally applies when multiple immunizations or medications are administered to a patient.<br />
<br />
==Behavior==<br />
<br />
[[Image:Behavior.jpg]]<br />
<br />
This section is for defining conditions that determine the status or action that occurs. (All) <br />
<br />
The Custom Reason for Keeping in Hold For Status control is used to select a specific reason to apply to the hold status of an orderable item. The options in the list are populated by entries in the Order Status Reason dictionary that are assigned to the "Hold For" status.<br />
<br />
The Duplicate Checking Interval control is used to select the period of time in which the system performs a duplicate order check when the same orderable item is ordered more than once. A value entered for this control overrides the setting for the Duplicate Checking Order Interval enterprise/organization preference in the Meds/Orders section of the TW Admin/Preferences workspace.<br />
<br />
*'''Not Applicable if Gender Equals''' - Excludes order from search results when patient is of selected gender. This field is used when a certain test is gender specific and should not be able to be selected for both male and female patients. <br />
*'''Priority Default''' - indicates the default clinical priority for the order (Stat, ASAP, Pre-Op)<br />
*'''Reasons for Needs Info Status''' - organizations can select more than one reason for holding the order in a Needs Info status (example: until consent is obtained). The reason must be met before the order can go to an On Hold status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Reasons for Hold For Status''' - organizations can select more than one reason for holding the order in a Hold For status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Ordering Authority''' — determines the ordering authority level that is required for this order.<br />
*'''Duplicate Check Interval''' - determines the interval for duplicate checking in specified time frame. This value overrides the Duplicate Check system preference.<br />
*'''Auto-complete upon order becoming Active''' - determines if the system automatically completes the order when it becomes Active. This is for orders that do not need to be tracked and results are not expected (such as a procedure).<br />
*'''Always Display Order Detail Upon Selection''' - whether to display the Order Detail page upon selection.<br />
<br />
==Specimen==<br />
<br />
[[Image:Specimen.jpg]]<br />
<br />
This section is for defining the details of orderable items that require a collection be taken from the patient when ordering. (All) <br />
<br />
*'''Specimen Instructions''' – free text instructions for handling the specimen. This information displays on the Order Detail and Specimen Collection pages.<br />
*'''Label Type''' - describes the label type for printing.<br />
*'''List of Valid Clinical Sources''' - describes list of valid source for which to collect the specimen. This is for Charge and Documentation purposes. This can be overridden by the Default Clinical Source can be Overridden option.<br />
*'''List of Valid Specimen Types''' - describes the valid specimen types for this order.<br />
*'''Default Clinical Source can be Overridden''' - determines if the clinical source can be overridden.<br />
*'''Hold for Specimen collection''' - check to activate the order when the specimen collection has been done.<br />
<br />
==Order Mapping==<br />
<br />
This section is for defining the specific sites to which an orderable item is restricted. Limiting the availability of items to specific sites allows for more accurate selection of only those items appropriate to a site items when they are ordered. (Only non-medication order types.) <br />
<br />
==Performing==<br />
<br />
[[Image:Performing.jpg]]<br />
<br />
This section is for defining the method of communicating the order and timeframes for priorities. (All) <br />
<br />
*'''List of Valid Communication Methods''' - describes the valid list of communication methods for the order. Examples are: Instruction,<br />
Procedure, and Rx.<br />
*'''List of Default Communication Methods''' - organizations can select more than one default communication method for the order.<br />
*'''OverDue Interval Routine''' - determines when to consider a Routine order overdue.<br />
*'''OverDue Interval ASAP''' - determines when to consider an ASAP order overdue.<br />
*'''OverDue Interval Stat''' - determines when to consider a Stat order overdue.<br />
*'''OverDue Interval Today''' - determines when to consider an order scheduled to be done on the current day overdue.<br />
*'''Expiration Interval''' - determines when to consider the order expired. Expired orders can be tracked on the Expired Order report.<br />
*'''Overdue Important checkbox''' - when checked a task is generated for the ordering provider if the order is overdue.<br />
*'''Overdue Date and Time Required checkbox''' - determines if an overdue date and time is required when ordering this lab.<br />
*'''Requested Performing Location Identifiers''' - identifies the tests in the appropriate terminology for the performing locations.<br />
<br />
==Identifiers==<br />
<br />
[[Image:Identifiers.jpg]]<br />
<br />
This section is for specific codes that are used to identify and synchronize the orderable items from multiple vendors. (All) <br />
<br />
*'''Mapped Medcin ID''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''HCPCS''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''UPC''' - Universal Product Code. Free text field.<br />
*'''LOINC CODE''' - Local Observation Identifiers Names, a data set for universal lab identifiers.<br />
*'''SNOMED''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
<br />
==Instruction Precaution==<br />
<br />
[[Image:Instruction precaution.jpg]]<br />
<br />
This section is for the details specific to orderable items of the Instruction, Precaution, or Clinical Findings order type. (Instruction, Precaution, or Clinical Findings type orders only) <br />
<br />
*Portions of this article refer to KB article 3108</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_Enterprise_EHR_-_Basic_Order/Results&diff=16371Allscripts Enterprise EHR - Basic Order/Results2013-06-10T16:44:09Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Details==<br />
<br />
This webinar was done May 24th, 2013 by Tony Yelacic and Mary Larson. It covered the basics of creating Orders and Results within the Allscripts Enterprise EHR.<br />
<br />
== Presentation materials ==<br />
<br />
[[Media:Basic Order_Results.ppt | Presentation slides]]<br />
<br />
<br />
<br />
==Questions & Answers from the Webcast==<br />
<br />
'''Q: If I need to create an order that will be used for documentation purposes only, there is no result or charge for it so, is the set up the same?'''<br />
<br />
'''A''': Yes, the basic set up will be the same. However, there are sections in the set up that can be left blank. Those sections are: Results, Charge/MN, Specimen, Performing and Order Mapping. It is important to note that the Behavior section offers a check box to "Automatically Complete Upon the Order Becoming Active" found within that section. That needs to be considered in your build/workflow. The remaining sections should be carefully tested as they may be important factors in meeting the order objective. Keep in mind each new orderable item needs to be properly classify within the OID dictionary hierarchy.<br />
<br />
<br />
'''Q: What if I have a certain orderable test that should only be used by one of the four sites in our organization? How could I set that up?'''<br />
<br />
'''A''': Using the Site Restriction option may work for in this scenario. In the Order Mapping section there is a blue "Site Restriction" set up field. Clicking on that opens the 'assign site' box. The sites that are assigned are the only sites within the organization that will be able to see that orderable item in a search within the ACI. Most important there is a .NET Preference that needs to be set to 'Y' at the enterprise level in order for this restriction to actively work. The preference is found under Order- "Enable Orderable Item Selection by site filtering".<br />
<br />
<br />
'''Q: What do you do when a charge has more than one CPT code associated with a test?'''<br />
<br />
'''A''': Both charge codes can be set to drop automatically by adding them both and separating with a comma. This is done in the 'Charge/MN' section of the orderable item build. <br />
<br />
<br />
'''Q: We have some providers that can never seem to find certain items in the ACI because they don't all refer to an item by the same name. Do we need to create additional test for them?'''<br />
<br />
'''A''': No, creating additional test for that reason is not recommended. You can however help the providers out a bit by entering the non-standard name in the grid. Example: In the grid of the orderable item dictionary the display name might be noted as 'Comprehensive Metabolic Panel' and the name on the grid line (between the code and Mnemonic) could be noted only as 'CMP'. When searching the ACI the provider searches for 'CMP', the search returns 'Comprehensive Metabolic Panel' even though the provider only entered the letters CMP. <br />
It should be noted that the display name is what flows to the requisition, the note outputs and the Order tab. Most importantly, these grid name changes should never be made without consideration to vender compendiums/codes/interfaces etc. <br />
<br />
<br />
==Links==</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_Enterprise_EHR_-_Basic_Order/Results&diff=16370Allscripts Enterprise EHR - Basic Order/Results2013-06-10T16:15:44Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Details==<br />
<br />
This webinar was done May 24th, 2013 by Tony Yelacic and Mary Larson. It covered the basics of creating Orders and Results within the Allscripts Enterprise EHR.<br />
<br />
== Presentation materials ==<br />
<br />
[[Media:Basic Order_Results.ppt | Presentation slides]]<br />
<br />
<br />
<br />
==Questions & Answers from the Webcast==<br />
<br />
'''Q: If I need to create an order that will be used for documentation purposes only, there is no result or charge for it so, is the set up the same?'''<br />
<br />
'''A''': Yes, the basic set up will be the same. However, there are sections in the set up that can be left blank. Those sections are: Results, Charge/MN, Specimen, Performing and Order Mapping. It is important to note that the Behavior section offers a check box to "Automatically Complete Upon the Order Becoming Active" found within that section. That needs to be considered in your build/workflow. The remaining sections should be carefully tested as they may be important factors in meeting the order objective. Keep in mind each new orderable item needs to be properly classify within the OID dictionary hierarchy.<br />
<br />
<br />
'''Q: What if I have a certain orderable test that should only be used by one of the four sites in our organization? How could I set that up?'''<br />
<br />
'''A''': Using the Site Restriction option may work for in this scenario. In the Order Mapping section there is a blue "Site Restriction" set up field. Clicking on that opens the 'assign site' box. The sites that are assigned are the only sites within the organization that will be able to see that orderable item in a search within the ACI. Most important there is a .NET Preference that needs to be set to 'Y' at the enterprise level in order for this restriction to actively work. The preference is found under Order- "Enable Orderable Item Selection by site filtering".<br />
<br />
<br />
'''Q: What do you do when a charge has more than one CPT code assiciated with a test?'''<br />
<br />
'''A''': Both charge codes can be set to drop automatically by adding them both and separating with a comma. This is done in the 'Charge/MN' section of the orderable item build. <br />
<br />
<br />
==Links==</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_Enterprise_EHR_-_Basic_Order/Results&diff=16365Allscripts Enterprise EHR - Basic Order/Results2013-06-05T15:23:33Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Details==<br />
<br />
This webinar was done May 24th, 2013 by Tony Yelacic and Mary Larson. It covered the basics of creating Orders and Results within the Allscripts Enterprise EHR.<br />
<br />
== Presentation materials ==<br />
<br />
[[Media:Basic Order_Results.ppt | Presentation slides]]<br />
<br />
<br />
<br />
==Questions & Answers from the Webcast==<br />
<br />
'''Q: If I need to create an order that will be used for documentation purposes only, there is no result or charge for it so, is the set up the same?'''<br />
<br />
'''A''': Yes, the basic set up will be the same. However, there are sections in the set up that can be left blank. Those sections are: Results, Charge/MN, Specimen, Performing and Order Mapping. It is important to note that the Behavior section offers a check box to "Automatically Complete Upon the Order Becoming Active" found within that section. That needs to be considered in your build/workflow. The remaining sections should be carefully tested as they may be important factors in meeting the order objective. Keep in mind each new orderable item needs to be properly classify within the OID dictionary hierarchy.<br />
<br />
<br />
'''Q: What if I have a certain orderable test that should only be used by one of the four sites in our organization? How could I set that up?'''<br />
<br />
'''A''': Using the Site Restriction option may work for in this scenario. In the Order Mapping section there is a blue "Site Restriction" set up. Clicking on that opens the 'assign site' box. The sites that are assigned are the only sites within the organization that will be able to see that orderable item in a search within the ACI. There is an order preference that needs to be set to 'Y' at the enterprise level in order for this restriction to actively work. The preference is found under Order- "Enable Orderable Item Selection by site filtering".<br />
<br />
<br />
<br />
<br />
==Links==</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_Enterprise_EHR_-_Basic_Order/Results&diff=16364Allscripts Enterprise EHR - Basic Order/Results2013-06-05T15:02:09Z<p>Larson.Yuill: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Details==<br />
<br />
This webinar was done May 24th, 2013 by Tony Yelacic and Mary Larson. It covered the basics of creating Orders and Results within the Allscripts Enterprise EHR.<br />
<br />
== Presentation materials ==<br />
<br />
[[Media:Basic Order_Results.ppt | Presentation slides]]<br />
<br />
<br />
<br />
==Questions & Answers from the Webcast==<br />
<br />
'''Q: If I need to create an order that will be used for documentation puposes only, there is no result or charge for it so, is the set up the same?'''<br />
<br />
'''A''': Yes, the basic set up will be the same. However, there are sections in the set up that can be left blank. Those sections are: Results, Charge/MN, Specimen, Performing and Order Mapping. It is important to note that the Behavior section offers a check box to "Automatically Complete Upon the Order Becoming Active" found within that section. That needs to be considered in your build/workflow. The remaining sections should be carefully tested as they maybe important factors in meeting the order objective. Keep in mind each new orderable item needs to be properly classify within the OID dictionary hierarchy.<br />
<br />
<br />
<br />
<br />
<br />
==Links==</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Summary&diff=16360Clinical Summary2013-05-28T15:56:49Z<p>Larson.Yuill: /* Q & A */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
=='''Overview'''==<br />
This webcast will compare and contrast each of the available Clinical Summaries: RTF, CED, and Structure Note Output. We will demonstrate the available settings related to utilizing the clinical summary, as well as reviewing certain considerations during such setup.<br />
<br />
=='''Documents'''==<br />
Delivered 10/26/2012: [[Media:Clinical_Summary_Webcast_PowerPoint_Final.pdf|Download slideshow]]<br />
<br />
=='''Q & A'''==<br />
<br />
'''Q: We are on 11.2.3 HF 4 and since that upgrade, the patient's pharmacy no longer prints on the CED which, by the way, is called Visit Summary, as well, since the change. IS there a way to force the pharmacy info to print again? Allscripts says no.'''<br />
<br />
'''A:''' No, at this time there is no way to get this to print until Allscripts adds in a fix for it. <br />
<br />
<br />
'''Q: Is it accurate that the RTF cannot be used with a patient portal?'''<br />
<br />
'''A:''' Yes, that is accurate. Only the CED and the Structured notes can be sent to the patient portal at this time. <br />
<br />
<br />
'''Q: If a patient declines the communication, would the people that print the CS know the pt doesn't want it? Would the icon show up?'''<br />
<br />
'''A:''' Yes, once a patient is marked as declined in the patient profile the CS column will display NA to indicate that no clinical summary is wanted for that patient. <br />
<br />
<br />
'''Q: We are not seeing the histories in our CED Clinical Summary (HPI, PMH, Soc Hx and Family Hx), is there a specific setup/configuration needed for these items to show?'''<br />
<br />
'''A:''' Currently being researched.<br />
<br />
<br />
'''Q: Can clinical summaries be invalidated?'''<br />
<br />
'''A:''' Yes, follow the steps below:<br />
# Create RTF/CED Clinical Summary.<br />
# Select Clinical Summary from ChartViewer.<br />
# Click New Task button.<br />
# Send a Go To Note task to someone.<br />
# Go to Current Pt – Active task list.<br />
# Double-click Go TO Note task.<br />
# Click Req Corr button.<br />
# Click Invalidate Checkbox then click OK.<br />
# Go back to Current Pt – Active Task List.<br />
# Double-click the Req Note Admin task<br />
# Click the Invalidate button.<br />
# Click OK.<br />
# Confirm duplicate Clinical Summary no longer displays in ChartViewer.<br />
<br />
<br />
'''Q: Which Clinical Summary do you recommend and why?'''<br />
<br />
'''A:''' The RTF is probably the most user friendly for both the clinics and the patients. The patients like this format as it is easy to read and follow and includes the encounter information. Where the CED includes information about the entire patient record, making it longer and in some cases confusing for the patients. The RTF is clean, simple with clearly defined sections.<br />
<br />
<br />
'''Q: Who should give the clinical summary to the patient and why?'''<br />
<br />
'''A:''' It is recommended that either the nurse of the physician give this to the patient. Reviewing it with the patient and pointing out the pertinent items such as testing that they needs to schedule or that you have scheduled for them as well as future appointments for follow up visits and medication changes, will make the document more valuable and meaningful to them. This is the same process that ER's and Hospitals have been using for years and it really helps the patients understand what is expected of them.<br />
<br />
=='''Links'''==</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=TWUser_Admin&diff=13252TWUser Admin2012-03-21T15:48:41Z<p>Larson.Yuill: </p>
<hr />
<div>==Main Workspace==<br />
[[Image:TWAdmin.jpg]]<br />
<br />
'''User Type''' - Indicates if the user is classified as a User or a User/Provider. In TouchWorks, a '''User''' is anyone with access to the EMR, but isn't necessarily clinical, such as a front desk user. A '''User/Provider''' is a TouchWorks user who has the privileges associated with a user and can additionally prescribe and order, such as a resident or MD.<br />
<br />
'''Last Name''' - the user’s last name<br />
<br />
'''First Name''' - the user’s first name<br />
<br />
'''eMail''' - Indicates the user’s eMail address; this information is required<br />
<br />
'''Organization''' - Indicates the user’s primary organization within TouchWorks<br />
<br />
'''Inactive''' - To deactivate the user, check this option; the user will not be able to log into the system<br />
<br />
===User Details===<br />
[[Image:User Details.jpg]]<br />
<br />
'''User Name''' – usually an abbreviated form of the user’s name, such as Last name and first initial of the first name. In many cases it is a good idea to mirror the user’s user name from other accounts such as Windows.<br />
<br />
'''Password''' – a code unique to that user and known only to them to log into the system. <br />
<br />
'''Default site''' – a physical location that is using the EMR such as a Pediatrics office. Printing defaults are typically assigned by site.<br />
<br />
'''Profession''' – users profession such as Nurse, MD, medical student<br />
<br />
'''Employee #''' - Indicates the employee’s identification at the organization.<br />
<br />
'''Finalization Authority''' – the level at which the user can finalize a document. A user can still create, sign, and save a document even though they do not have a high enough finalization authority. <br />
<br />
'''Credentials''' – the users credentials such as: RN, MD, MA<br />
<br />
'''Ownership Authority''' – the level at which the user can be the Owner of a document. A user can still create and sign a document if they don’t have a high enough Ownership authority. This only grants the level at which a user can be the Owner. <br />
<br />
'''Password Never Expires''' – by checking this box the password for the user does not expire.<br />
<br />
'''Force Password Change''' – by checking this box, the next time the user logs in the system will force the user to change their password.<br />
<br />
'''Physician Homebase User''' - applies to User/Providers only. Indicates whether the user is a Physician Homebase user (and thus, Homebase appears on the horizontal toolbar). <br />
<br />
'''Electronic Workflow''' – by checking this box, the user will participate in the electronic workflow such as electronic signature.<br />
*In order to resolve the issue of Providers not receiving Sign Note tasks in TW, access TWAdmin->TWUser Admin then open the provider in question and make sure the Electronic Workflow box is checked. They'll have to make sure all the Document Types are setup for Electronic Signature as well (vs Electronic Verification or Non Electronic).<br />
<br />
'''Prohibit Task Assignment''' (feature available in 11.2.3) - by checking this box, this will prohibit the users name from appearing in the available list of names when someone is manually creating a task. <br />
*This can prove useful in situations where providers leave an organization and this will prohibit them from receiving manually created tasks. This will not prevent them from receiving system-generated tasks (controlled by Electronic Workflow checkbox).<br />
<br />
===Provider Details I===<br />
[[Image:ProviderDetail_I.jpg]]<br />
<br />
'''Code''' - Unique number that identifies the provider within the TW enterprise. If the EHR system is interfaced with a PM product it is necessary for the provider codes in both systems to match in order for the providers daily schedule to flow from one system into the other.<br />
<br />
'''Mnemonic''' - the unique mnemonic used to identify this user.<br />
<br />
'''Prim. Specialty''' - the provider’s primary specialty. The provider’s specialty<br />
drives the favorites lists the system displays throughout the application.<br />
<br />
'''Sec. Specialty''' - the provider’s secondary specialty.<br />
<br />
'''CME Pilot #''' - The provider’s id used with the PIER program. This field is no longer used as the program is no longer active.<br />
<br />
'''Ordering Authority''' - the provider’s ordering authority. A provider’s ordering<br />
authority must be at least as high as the ordering authority associated with the item in the<br />
Orderable Item dictionary.<br />
<br />
'''Credentials''' - the provider’s medical credentials.<br />
<br />
'''DEA #''' - the provider's DEA number (that is, the number that the Drug<br />
Enforcement Authority assigns for prescribing controlled substances, and is unique to<br />
each provider).<br />
<br />
'''DEA Exp Date''' - this is the expiration date for the DEA number.<br />
<br />
'''Billing Provider''' - by checking this field the provider will show as a<br />
billing provider on the Encounter Form in the charge module.<br />
<br />
'''PCP''' - this is for a primary care physician. This value is not used in the current version of TouchWorks.<br />
<br />
'''Schedulable''' - When checked, the provider’s schedule can be displayed on the Schedule page.<br />
<br />
'''Secure Schedule''' - When checked, the system creates a code for this provider.<br />
TouchWorks users who want to view this provider’s schedule must have that code.<br />
<br />
'''Don’t Generate “Send Charge” Tasks''' - When checked, this indicates that Submit<br />
Encounter Form tasks will not be generated for this provider when patients are arrived.<br />
<br />
'''Show Optional Clinical Message''' - When checked, this indicates<br />
clinical messages are displayed to the provider on login.<br />
<br />
===Provider Detail II===<br />
[[Image:ProviderDetail_II.jpg]]<br />
<br />
'''Prescribing Authority Levels''' – [[DEA Schedule]] - Check the schedules for which the<br />
provider is qualified to prescribe drugs.<br />
<br />
'''License''' - select this to add a state license number for this provider.<br />
You must specify the state, the ID number, and the expiration date.<br />
<br />
'''Rx Supervision Required''' - select this option if prescriptions for this provider must be<br />
approved, such as a resident.<br />
<br />
'''Alt License''' - the license number that prints on the script for Nurse<br />
Practitioners.<br />
<br />
'''UPIN''' - the provider's unique personal identification number (UPIN). This is a<br />
number assigned by Medicare and is unique to each provider.<br />
<br />
'''Signature Image''' - the path to the image of the provider’s signature as it<br />
should appear on prescriptions when they are faxed to pharmacies.<br />
<br />
'''Def CC Method''' - the provider’s default method for carbon copies.<br />
Select Envelope, Fax, Print, or Review Task. This can be overridden this value in the<br />
application.<br />
<br />
'''NPI''' - National Provider Identifier<br />
<br />
'''Outbound ID''' - Specifies the identifier used in the Dictate product for providers that will<br />
be generating dictations. This identifier is recognized by the TouchWorks Dictate module<br />
and the transcription service.<br />
<br />
'''License''' - Click this button to adjust the number of Dictate licenses available<br />
across the set of providers that are using the Dictate product.<br />
<br />
'''Recording Format''' - the recording format for transcription files.<br />
<br />
'''Transcribe Difficulty''' - the dictating provider’s dictation’s degree of<br />
transcribing difficulty (due to accent, etc.). It must be set to a value from 1.0 to 9.9; the<br />
default value is 1.0.<br />
<br />
===Address===<br />
[[Image:Address.jpg]]<br />
<br />
'''Address''' - the user’s mailing address. Two lines are provided.<br />
<br />
'''City''' - the user’s city.<br />
<br />
'''State''' - the user’s state.<br />
<br />
'''Zip Code''' - the user’s zip code.<br />
<br />
'''Home Phone''' - the user’s home phone number.<br />
<br />
'''Fax #''' - the user’s fax number.<br />
<br />
===Security===<br />
[[Image:TWUA_Security.jpg]]<br />
<br />
'''Add/Remove Organization''' - Click this button grant or remove access to an<br />
organization within the enterprise.<br />
<br />
'''Add/Remove Security Classifications''' - Click this button to grant or security classifications.<br />
<br />
'''Grant Enterprise Access''' - Click this button to grant access to all organizations in the enterprise.<br />
<br />
===Workplaces===<br />
[[Image:Workplaces.jpg]]<br />
<br />
'''Edit Workspaces''' - Click this button to make changes to the workspace configuration for this user.<br />
<br />
===iHealth===<br />
[[Image:IHealth.jpg]]<br />
<br />
'''Activate option''' —When checked, indicates that the provider uses Medem to correspond<br />
with patients.<br />
<br />
'''iHealth Practice ID''' —Indicates the practice ID assigned by Medem.<br />
<br />
'''iHealth Provider ID''' —Indicates the provider’s ID assigned by Medem.<br />
<br />
'''iHealth Administration ID''' —Indicates the administration ID assigned by Medem.<br />
<br />
'''iHealth Target''' —Leave this set to Medem.<br />
<br />
''this information is referenced in the Allscripts Knowledge Base''<br />
<br />
===Physician Homebase===<br />
[[Image:PhysicianHomebase.jpg]]<br />
<br />
'''Linked to PMS option''' —When checked, indicates whether the user corresponds to a user<br />
in a practice management system.<br />
<br />
'''Practice/Department''' —If you have checked the Linked to PMS option, then indicate<br />
the user’s specified practice or department in that outside system.<br />
<br />
'''Provider Name''' — If you have checked the Linked to PMS option, then indicate the<br />
user’s name in that outside system.<br />
<br />
''this information is referenced in the Allscripts Knowledge Base''</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Extract_and_Load_via_SSMT&diff=13247Extract and Load via SSMT2012-03-20T21:47:53Z<p>Larson.Yuill: </p>
<hr />
<div>__TOC__<br />
==Description==<br />
The Starter Set Migration Tool ('''SSMT''') is an Allscripts provided tool that allows clinics to extract and load the data in their Allscripts Enterprise EHR. Three common uses are:<br />
# To move data from one database to another<br />
# To load data from a spreadsheet to a database<br />
# To extract data, edit it, and then load it back<br />
<br />
This tool should only be used by persons who understands how and when to use SSMT and always adhere to the Allscripts documented process when utilizing this tool.<br />
<br />
'''Warning''':<br />
Ensure that you complete a database [[SQL Backup]] prior to loading any data through SSMT. The tool is pretty robust, <br />
but human error or program bugs could create a mess. Completing a backup first takes only a few minutes and could save <br />
hours of time if something does happen.<br />
<br />
==Excel Formatting Tips==<br />
[[Excel]]<br />
<br />
==New SSMT released 1/12/2012- v2.2. HF 1==<br />
SSMT Version v2.2. HF 1 contains several changes (these can also be found on Supportforce> Production Documentation> SSMT and CMT category:<br />
* Removed "Security Code Name" field from content category "Task Name" in SSMT.* Added Specimen Type category <br />
* SSMT Installer allows clients to install a clinical and/or framework database that is not named "Works" and "IDXwf."<br />
* SSMT - "Favorites: Vaccines" creates and load a new entry successfully.<br />
* SSMT "Favorites: Medication" - The sublist of Users should be in alphabetical order by displayed user name.<br />
* Using SSMT to copy Task Views can corrupt the Task Views if the view (1) contains a Task Type with a name that has parentheses [such as 'Mng Chg Edits (Manage Charge Edits)'] or (2) contains many entries for a single filter in the view. <br />
* SSMT - Should be able to extract, edit, and load Note Definitions successfully.You are now able to extract and edit the "SectionDisplayName" column; change the "Default Action" column to "1" for all of the Assessment and Active Problems; and then load Note Definitions successfully.<br />
* SSMT content category "Clinical Desktop Views - Users" extracts the correct information for users and set users defaults appropriately.<br />
* SSMT is removing the entry from "NeedsInfoDEList" using the "OID - Orderable Item" content category.<br />
* SSMT content category "Favorites: Problem Based - Meds" - Should be able to remove items.You are now able to successfully remove favorite items using SSMT content category "Favorites: Problem Based &#8211; Meds".<br />
* The SSMT content category "OID_OCD Mapping" will now correctly overwrite existing OCD mappings in the OID and delete existing OCD mappings in the OID (this is equivalent to "unmapping" an item).<br />
* SSMT - The Suffix and Prefix fields are displaying in the wrong fields for Referring Provider.<br />
* Inactivate existing pre-11.2 favorites in an 11.2 environment using SSMT.<br />
<br />
==Access SSMT and Enter Database Login==<br />
<br />
1. Navigate to SSMT through Internet Explorer. Use the following URL and Replace Server Name with the web server name or IP provided by Tech or TOps:<br />
http://Server Name/TouchWorks/imps/ssmt/ssmt.asp<br />
<br />
2. Gather the following information from the Tech or TOps:<br />
* Clinical DB Server:<br />
* Clinical DB: (usually 'Works')<br />
* Clinical DB User: (usually 'sa')<br />
* Clinical DB Password:<br />
<br />
[[Image:SSMT2.jpg|frame]]<br />
<br />
IDX Web FrameWork<br />
* FW DB Server: (usually same as Clinical DB Server)<br />
* FW DB: (usually 'IDXwf')<br />
* FW DB User: (usually 'sa') FW DB Password: (usually same as Clinical DB Password)<br />
<br />
3. After logging in, check the header to be sure that you are in the correct Database and Framework.<br />
<br />
[[Image:SSMT3.jpg]]<br />
<br />
4. Select a content category from the drop down menu. The name here should match the name in the Build Workbook EXACTLY<br />
<br />
[[Image:SSMT4.jpg]]<br />
<br />
==Extract Data==<br />
<br />
5. The Show Database calls box should remain unchecked unless you are using it for troubleshooting<br />
<br />
6. ALWAYS check show headers when extracting data<br />
<br />
<br />
[[Image:SSMT6.jpg]]<br />
<br />
7. Extract Data by clicking on the Extract data button in the lower left hand corner of the screen<br />
<br />
[[Image:SSMT7.jpg]]<br />
<br />
*This is what your screen will look like<br />
<br />
[[Image:SSMT8.jpg]]<br />
<br />
8. Open Excel<br />
<br />
9. Delete any headers existing in Excel<br />
<br />
10. Reformat all Excel worksheets as Text BEFORE loading extracted data to Excel<br />
The Excel default is General which strips leading 0’s so if extracted data is loaded into Excel before the cells are reformatted, it strips the zeros and does not “remember” they were there so formatting the cells to text ''after'' importing the extracted data will not work. Forgetting to change the cell format to text BEFORE pasting the data into Excel will cause problems in the application<br />
a) Click in the upper left hand corner of the screen to select all cells<br />
b) Right click and select format cells<br />
c) In the Format cells Dialog box select “Text” and click on OK<br />
<br />
[[Image:Ssmt9.jpg]]<br />
<br />
<br />
[[Image:SSMT10.jpg]]<br />
<br />
11. Navigate back to SSMT<br />
<br />
12. Click inside the large data field and use CTRL-A to SELECT ALL (including headers) <br />
<br />
13. CTRL-C to copy<br />
<br />
[[Image:SSMT11.jpg]]<br />
<br />
14. Navigate back to Excel<br />
<br />
15. Put your cursor in the very first cell of the Excel spreadsheet<br />
<br />
16. CTRL-V to paste the data into Excel (including headers)<br />
<br />
[[Image:SSMT12.jpg]]<br />
<br />
<br />
Check all cells for #####<br />
<br />
17. Do a find for # and reformat any column containing ##### to General<br />
<br />
a) Select the header of the column containing ####<br />
<br />
b) Right click and select format cells as General<br />
<br />
The #### means the data is too large for the cell. If the data is loaded into SSMT without changing the format of these columns to General the #### will be loaded in place of the data and cause problems in the application<br />
<br />
18. Done<br />
<br />
==Load Data==<br />
# Select a content category from the Go Live Weekend Configuration Guide. Find the same category in the BW extractions worksheet tabs. The category names should match exactly. If they do not, extract the same category with SSMT and make sure the headers match.<br />
# '''Verify the blank Excel worksheet was reformatted to text BEFORE the extracted data was pasted in'''<br />
#:The Excel default is General which strips leading 0’s so if extracted data is loaded into Excel before the cells are reformatted, it strips the zeros and does not “remember” they were there so formatting the cells to text ''after'' importing the extracted data will not work. Forgetting to change the cell format to text BEFORE pasting the data into Excel will cause problems in the application.<br />
#:Check each worksheet by clicking in the upper right-hand corner to select all cells and then right-clicking to format cells. You should see either no selection highlighted (because the sheet was formatted as text and then some columns were changed to general to fix ####) or Text highlighted. There is no way to tell if cells were formatted to text before or after importing the extracted data except to check with whoever extracted it. <br />
# '''Check all cells for #####'''<br />
#: Do a find for # and reformat any column containing ##### to General.<br />
#: Select the header of the column containing ####.<br />
#: Right click and select format cells as general.<br />
#:(#### means that the data is too large for the cell)<br />
# '''Modify Categories with Create (Y N) Column'''<br />
#: If the category has a column labeled "Create (Y N)" or something similar, change all these values to Y. load the data via SSMT (see details below), ignore the errors that say “No Record Found to Update”. Change all the Create (Y N) values back to N and load again. This should return no errors.<br />
# '''During GoLive, Try to avoid moving unwanted inactive items created in test to production'''<br />
#: Have a discussion with the client to identify these items because some inactive items may still be wanted in test. For the unwanted inactivated items created in test, make a back-up copy of the BW then delete the unwanted items from the BW before loading to prod via SSMT.<br />
# Navigate back to SSMT<br />
# Select the content category you will be loading from the drop down menu. The name here should match the name of the Excel worksheet exactly.<br />
# In the SSMT Window, use CTRL-A to select all, then hit delete. This ensures that there are no empty spaces in the SSMT data window that could throw off the Data you are loading.<br />
# Navigate back to your excel document. In Excel, you want to select all of your Data, but not the headers and no empty column. Grap starting from cell A2, even if there is no data in that cell and drag to grab all columns with data and '''NO MORE THAN 700 ROWS of DATA''' (SSMT can only move 65K of data at a time)<br />
# Use Ctrl-C to copy the Data<br />
# Navigate back to SSMT<br />
# put cursor into the SSMT Data Field<br />
# Use CTRL-A to select all<br />
# Use CTRL-V to paste data from excel.<br />
#* Note: using Ctrl-A then Ctrl- V helps ensure that you do not have any blank spaces in the data field that will distort your data.<br />
# Click on Load Data in lower left.<br />
<br />
*When [[Load Menus|loading menus]] the Server IIS Services MUST be restarted after the load for menus to appear and full privileges must be given to 'twappadmin'.<br />
<br />
==Error Messages==<br />
The SSMT tool returns various error messages. Here is a page dedicated to [[SSMT Error Messages]]<br />
<br />
==Content Categories==<br />
Below is list of content categories used to to migrate or update data via SSMT. Select the Spreadsheet name for a more in-depth description.<br />
* [[SSMT: Users / Providers]] - This is the spreadsheet used to load and manage user and provider accounts.<br />
* [[SSMT: User Security Classifications]] - This is the spreadsheet used to assign security classifications to user.<br />
* [[SSMT: RID - Resultable Item Dictionary]] - This is the spreadsheet that is used to load the result definitions from various lab vendors. <br />
* [[SSMT: OID - Orderable Item Dictionary ]] - This spreadsheet used to load Order Level items for various vendors.<br />
* [[SSMT: Order Performing Facility Identifiers]] - This spreadsheet is used to synchronize multiple vendors.<br />
* [[SSMT: OID - Order Defaults - Req Perf Location / Site]] - This is the spreadsheet that is used to set defaults on a [[Site]] or [[Requested Performing Location]] level. This can set various default behaviors such as charge behavior, order detail, and much, much more. <br />
* [[SSMT: OID - Order Defaults - Insurance/PatientLocation/Site]] - This is the spreadsheet used to specify orderable behavior on the insurance, patient location, or [[site]] level. It is used to set defaults such as the Default [[Requested Performing Location]], [[Requested Performing Location]] Picklist, Internal/External Required behavior, Referred to Vendor Org required behavior, Referred to Location Site Required behavior, and Referred to Provider Required behavior.<br />
<br />
* [[SSMT: Charge Codes]] - This spreadsheet is used to load or edit Charge Codes within TouchWorks<br />
* [[SSMT: Document Type]] - This is the spreadsheet used to upload or edit documents within TouchWorks<br />
<br />
* [[SSMT: Orderable Item Favorites | SSMT: Favorites Orderable Items <Order Type>]] - Used to load/edit/copy orderable items favorites. The various Order Types (Lab, Imaging, Supplies, etc)</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Flowsheets&diff=12825Flowsheets2012-02-21T21:46:29Z<p>Larson.Yuill: </p>
<hr />
<div>___TOC___<br />
<br />
==Introduction==<br />
When selected, the system displays a selected flowsheet using data from the selected patient’s record. Flowsheets are categorized by specialty. The flowsheets linked to the provider's primary specialty will display in the Flowsheets section of the Clinical Desktop.<br />
<br />
== Building Flowsheets ==<br />
<br />
Flowsheets can consist of Items from the OID and/or Medcin Findings. If building flowsheets using ONLY Medcin Findings data elements, then skip to step 5. For items built from the OID follow these steps:<br />
<br />
=== Step 1: Map out all items needed in the flowsheet ===<br />
<br />
When building flowsheets using the OID, it’s important to map out all of the possible answers the client would like for each data element and how the client would like those answers (free-text/numeric/date/picklist). In order to obtain the possible answers for each item, a clinical person will most-likely need to be consulted. For this article, we will use an Anticoagulation Flowsheet as an example. The data elements we will use and their possible answer types are listed below:<br />
<br />
*Indication for Treatment: (Free Text)<br />
*Duration of Treatment: (Free Text)<br />
*PT: (Result from either interface or user manually enters)<br />
*INR: (Result from either interface or user manually enters)<br />
*Date of Last treatment: (date)<br />
*Current Dose: (Types of Warfarin/Coumadin doses; Possible Answers: 1MG, 2MG, 2.5 MG, 3 MG, 4 MG, 5 MG, 6 MG, 7.5 MG, and 10 MG)<br />
*Dose Changed: (Possible Answers: Yes/No)<br />
*New Dose: (Types of Warfarin/Coumadin doses; Possible Answers: 1MG, 2MG, 2.5 MG, 3 MG, 4 MG, 5 MG, 6 MG, 7.5 MG, and 10 MG)<br />
*Next Follow-up: (Date)<br />
*Comments: (Free Text)<br />
<br />
=== Step 2: Create Answers and Answer Picklists === <br />
For our example, the answers/picklist we will need to create that do NOT already exist in the Answer dictionary is the dosages. The Yes/No picklist already exists in the Answer dictionary and as a picklist.<br />
<br />
# Once you have mapped out the possible answers, you need to go to the Answer dictionary. <br />
# If the answers exists (yes/No, etc), then use those answers to create a picklist in the Answer dictionary for the data element in the flowsheet. <br />
## If the answer does not exist, decide if the answer can be entered into an existing node in the answer dictionary or if a new node needs to be created.<br />
### If a node needs to be created, select the word "Answer" and click the Add button to the left. <br />
### Type the name of the node (try to make this generic, i.e. if this is dosages of coumadin in mg, you may want to name the node "dosages" so it can house multiple dosages not just those related to Coumadin)<br />
## Select the node that will house the answers and click the Add button to the right.<br />
## Enter the Code, Name, and Mnemonic. The Name should be how you want the answer to display. (i.e. Code=OneMG, Name=1 MG, Mnemonic=OneMG)<br />
##Continue the last two steps until all answers for this node are entered. <br />
# After all answers are created in the right nodes, click the Picklist button.<br />
#* Existing picklists will display.<br />
# Create any new picklists by clicking "Add Picklist" and naming the picklist after the result item (i.e. Coumadin Dosages).<br />
# Once the picklist is created, assign answers to the picklist by selecting the picklist and clicking Add Entry. Add all items that apply to this specific picklist. You may have to create multiple picklists.<br />
#* Note, you should NOT create a new picklist for Yes/No as one already exists.<br />
<br />
=== Step 3: Verify and Create New RID (Resultable Item Dictionary) Items ===<br />
Once all Answer Picklists have been created, the results should be linked to the correct Answer Picklists. In some cases, the results may already exist.<br />
# Prior to creating a new result, you should confirm that result does not already exist from another flowsheet. Search for the item (i.e. Search for Indication for treatment).<br />
# If the item is a new result, then click the Add button.<br />
#* Note, if the item already exists, move onto the next result to see if it is in the RID until you have either confirmed/created all results are in the RID<br />
# Enter the Code, Name, and Mnemonic (ie. Code = IndicForTre; Name = Indication for Treatment; Mnemonic = IndicForTre)<br />
# Fill-in information within the result:<br />
#* Display Name (i.e. Indication for Treatment: )<br />
#* Answer Data Type (i.e. Free Text/Date/Numeric/Picklist)<br />
#* If you choose Date as the Answer Data Type, you will also be able to choose any date restrictions (i.e. Future Dates, Fuzzy Dates, etc.)<br />
#* If you choose Free Text as the Answer Data Type, you will also be able to choose the Number of Characters and Number of Lines to display.<br />
#* If you choose Numeric as the Answer Data Type, you will also be able to indicate a maximum and minimum value.<br />
#* If you choose Picklist, you will have to select the Picklist you created in Step 2 or one of the existing picklists (i.e. Yes/No)<br />
<br />
<br />
An optional step may be to review all potentially equivalent results in the RID that will be used in the flowsheet (i.e. PT and INR). If multiple vendors are used, then there could be multiple INR's and PT's (from Sunquest, Labcorp, Quest, etc.). Use the <br />
"Considered Equivalent Only for Flowsheet Graph" option in the RID for all existing items that could be considered equivalent<br />
<br />
=== Step 4: Create a New OID (Orderable Item Dictionary) item for the Flowsheet ===<br />
The common place to store flowsheets within the OID is the Clinical Findings category under Non-Medications. <br />
<br />
# Select the Clinical Findings category under Non-Medication Orders.<br />
# Click the Add button.<br />
# Fill-in the Code, Name, and Mnemonic (i.e. Code = AnticoFS; Name = Anticoagulation Flowsheet; Mnemonic = AnticoFS)<br />
# Now fill-in fields within the orderable item in the Initial section:<br />
#* Displays Name (i.e. Anticoagulation Flowsheet)<br />
#* Check the Orderable checkbox (This will be unchecked after the Flowsheet is tested)<br />
#* Orderable via (User Only or User or Interface - The option here depends on whether results coming over the interface are being used in this flowsheet. In our example, we would choose User Only because the PT and INR orders will be pulled into our flowsheet seperately)<br />
#* OID Mode (Active - The order must be active in orde to be able to link it to a flowsheet)<br />
#* Order Type (Defaults to Clinical Findings)<br />
# In the Results section, you will need to use the RID selector to select the results created in Step 3.<br />
#* The items we would bring into our flowsheet for the example would be: Indication for Treatment, Duration of Treatment, Current Dose, Dose Change, New Dose, Next Follow-up, and Comments.<br />
# Choose the Resultable Via to be User Only since none of our resultable items are coming from the interface. <br />
<br />
<br />
<b><u>Order Panels:</u></b><br />
<br />
In some cases it may be necessary to create order panels for equivalent results that are coming through the interface. If you have used the function in the RID “Considered equivalent only for flowsheet graph” and tied the resultables what will happen is when ONE of those is resulted it will duplicate the results for each of those line items in the flowsheet. For example let’s say that patient A goes to LabCorp and has the INR checked and resulted. When you look at the flowsheet not only does a line item show for INR with the results, but you will see two additional lines on the flowsheet for the Quest INR and the Sunquest INR with the results for INR in them. Basically the same result will be seen in triplicate. <br />
<br />
<br />
<b>How to avoid this: </b> Create a new special order in the OID called “[Flowsheet Name] Panel” (i.e. Anticoagulation Flowsheet Panel) and we attach to that orderable only ONE resultable representing each order that we want on the flowsheet. So for instance in our Anticoagulation Flowsheet Panel order we only attach the one result for the Labcorp INR (and leave out the additional two from Quest and Sunquest), and we the one result for the Labcorp PT. We still use the “equivalent” function, but now regardless which result comes back – whether it’s for LabCorp, Cerner, or Quest we only have ONE line that shows on the flowsheet.<br />
<br />
=== Step 5: Create the Flowsheet and Assign it to the Correct Specialties ===<br />
Flowsheets are built withing PAT by Category in the Flowsheets Category. This menu item is normally found in PhysAdmin. The final step will be to add the Orderable Items to the flowsheet. Remember, Medcin Findings items can also be added to flowsheets.<br />
<br />
[[Image:flowsheetLT.jpg]]<br><br />
<br />
To build a new flowsheet, follow these steps:<br><br />
# Go to PhysAdmin<br><br />
# Select “PAT by category”<br />
# Select “flowsheets"<br />
# Select a specialty (Remember that only users assigned to this specialty will see the flowsheet)<br />
# Hit “new”<br />
# Enter a name for the flowsheet in the “name” field (i.e. Anticoagulation)<br />
# Determine the following parameters (These parameters can also be set at the Clinical Desktop level):<br />
#*Chrono Sort - descending or ascending<br />
#*Blank rows - hide or show (recommend setting this to “hide”, which will only show rows that contain data. This makes the flowsheet easier to read)<br />
#*View - date sequence or date/time (recommend date sequence as date/time tends to be confusing to look at)<br />
# Click “link” to link flowsheet to appropriate ICD9 (i.e. Diabetes).<br />
#* Note, you do not have to link a flowsheet to an ICD9 code.<br />
# Click “add item” to add an item from the Orderable Item Dictionary. <br />
#* Remember the item must be “active” and orderable in order to select it.<br />
#* In our example we would select Anticoagulation Flowsheet and Anticoagulation Flowsheet Panel using the arrows to add them to the flowsheet. <br />
# Click “Ok” to see the items that have been added to the flowsheet. <br />
#* They may appear as folders with multiple analytes (results) inside each folder. To see all of the analytes, click the + sign next to the folder to expand.<br />
# Click “add findings”, to add Medcin items to the flowsheet (if required). <br />
#* Adding Medicin is particularly useful when certain items are being documented within a V11 note that also need to be tracked via a flowsheet. For example, if a provider checks a renal patient for "pitting edema", then documents the result at numerous visits using the Medcin term “pitting edema”, adding this same Medcin item to the flowsheet will allow the answer to post to the flowsheet as well.<br />
# Select the “preview” tab to see the flowsheet from the end user perspective.<br />
# Return to the “build” tab. If an item needs to be removed, this can be done by highlighting the item and hitting the “remove” button. Items can also be moved up by highlighting the item and hitting the up arrow next to the “remove” button.<br />
# Save the flowsheet by clicking the “save” button. It shold now be visible to the users assigned to the specialty associated with the new flowsheet.<br />
<br />
=== Step 6: Testing and Final Revisions ===<br />
All flowsheets should be tested before moving to Production. Once testing and revisions are complete, remove the check in the Orderable checkbox for the Flowsheet in the OID.<br />
<br />
=== Setting Flowsheet Defaults for Users ===<br />
"User/Providers" that have been assigned a primary specialty in TWAdmin> UserAdmin> will automatically have flowsheets defaulted accordingly that assigned specialty. However, "User" must also have specialties assigned to them as well in order for thier flowsheets to default. That can be done in TWAdmin> Preferences> General> User and the preference is "DefaultSpecialtyID".<br />
<br />
== Troubleshooting ==<br />
'''Eliminating equivalent RID rows in a flowsheet:''' <br />
How to avoid duplicated rows in your flowsheet that are created by using the "Considered equivalent only for flowsheet graph:" is by creating an additional orderable item for the purpose of flowsheet display. <br />
<br />
For example let’s take CAD (coronary artery disease) flowsheet – on this flowsheet you would want to include total cholesterol when you build this in Phys Admin. The logical thing seems to be to go to Phys Admin search for Total Cholesterol and add that orderable item to your flowsheet. If you are working with multiple lab vendors chances are you will have several versions of cholesterol resultable mapped to that order – one for each of your lab vendors:<br />
<br> - Cholesterol for LabCorp<br />
<br> - Chol for Cerner<br />
<br> - Cholesterol, Total for Quest<br />
<br />
If you have used the function in the RID “Considered equivalent only for flowsheet graph” and tied the three cholesterol resultables mentioned above what will happen is when ONE of those is resulted it will duplicate the results for each of those line items in the flowsheet. For example let’s say that patient A goes to LabCorp and has the Cholesterol checked and resulted. When you look at the flowsheet not only does a line item show for Cholesterol with the results, but you will see two additional lines on the flowsheet for Chol and Cholesterol, Total with the results for Cholesterol in them. Basically the same result will be seen in triplicate.<br />
<br />
'''How to avoid this:'''<br />
Instead of going into Phys Admin and adding the different orderables to the flowsheet we create a new special order in the OID (and this is what we attach in Phys Admin to our flowsheet). We call it “CAD Panel” and we attach to that orderable only ONE resultable representing each order that we want on the flowsheet. So for instance in our CAD Panel Order we only attach the one result of “Cholesterol” (and leave out the additional two - Chol and Cholesterol, Total). We still use the “equivalent” function, but now regardless which result comes back – whether it’s for LabCorp, Cerner, or Quest we only have ONE line that shows on the flowsheet.<br />
<br />
<br />
[[Common Flowsheets]]<br />
<br />
[[Flowsheet Q and A]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Orderable_Item_Dictionary&diff=12493Orderable Item Dictionary2012-02-01T18:01:33Z<p>Larson.Yuill: </p>
<hr />
<div>==Description==<br />
The Orderable Item Dictionary (OID) is the dictionary that holds a list of the unique Order entries. This is typically built based on the compendium from you primary vendor, Allscripts delivered items and may also include tests from your other vendors and/or custom built tests created for an Organization or Site. Ultimately this is the list of Orders that the user will have the ability to Order from the ACI within Enterprise EHR (assuming they are set as Orderable and Users are allowed to order the test in the OID). <br />
<br />
To learn more about building the OID please refer to [[V11 Order and Result Dictionary Build and Synchronization]].<br />
<br />
'''Version Information'''<br />
*[[Article Creation|Article Created based on version]]: 11.1.1<br />
*[[Article Last Update|Last Updated with version]]: 11.1.7<br />
<br />
==Data Grid & Overview==<br />
The dictionary itself is broken down into 2 main classifications, medication and non-medication orderable items. The main data grid displays the set of items that can be ordered, received as resulted order, recorded as resulted orders, as well as entries used for the<br />
classification of other orderable items. Entries could include medications, patient instructions, laboratory items, and radiology items.<br />
<br />
[[Image:Orderable Item.jpg]]<br />
<br />
*'''Code''' - the data parameters for the "Code" field indicate that the entry must be unique within the OID and be 10 characters or less. This code is typically obtained from the organization's lab vendor. <br />
*'''Name''' - the "Name" field indicates that dictionary entry name.<br />
*'''Mnemonic''' - the "Mnemonic" field is similar to the "Code" field in that it shares the same data requirements; the entry must be unique to all other order entries and be 10 characters or less.<br />
*'''Inactive''' - the "Inactive" check-box indicates whether or not the orderable item is "Active". A mark in the check-box indicates that the orderable item is inactive. This field also controls the "OID Mode" field in the Initial details section of the OID. (See below)<br />
<br />
==Initial==<br />
<br />
[[Image:Initial.jpg]]<br />
<br />
*'''Display Name''' - indicates the name that displays in the application for the test. If the display name and the code name on the data grid are differant, the system will cross reference during an ACI search.<br />
*'''Linked OCD''' - indicates a linked OCD (if exists). Linked OCD will drive modifier behaviors for the lab test.<br />
*'''Orderable check-box''' - indicates whether the dictionary entry is an Orderable Item or a Parent Class.<br />
*'''Complex check-box''' - used for a collection of items that can be performed without ordering. This check-box currently is only supported with the set up of Vital Panels and should not be utilized when building orderable items.<br />
*'''Orderable Via''' - indicates how the item can be ordered (such as, interface or lab).<br />
*'''OID Mode''' - indicates the mode while the item is built. The mode is controlled by the "Inactive" check-box in the OID data grid.<br />
*'''Order Type''' - indicates where this item falls in the hierarchy (display only field). The Order Type is also an indication of where an orderable item can be found in the ACI.<br />
*'''Modifier Picklists''' - organizations can assign up to three modifier picklists to orderable items. Up to three default modifiers from the picklists can be assigned. Modifier picklists allow for documentation of additional information on a particular orderable item. Modifier picklists only allow for entry of information through drop down fields. (see Additional Information Questions as a more flexible alternative)<br />
*'''Required to Save''' — the Required to Save options indicate if this modifier information is required to save.<br />
<br />
==Medication==<br />
<br />
[[Image:Medication.jpg]]<br />
<br />
*'''NDC''' - (National Drug Code) Universal standard drugs number that’s defaulted from Medispan.<br />
*'''DDI''' - Medispan internal identifier that is used for drug- drug checking, etc.<br />
*'''Control Substance Code''' - indicates scheduled drugs. Drives narcotic behavior. Choices are: Sched 1-5.<br />
*'''Route of Admin''' - determines the default route to administer the drug. It’s possible to have more than one route of admin (need link to what’s available) from the Sig.<br />
*'''Medication Package Size''' — determines what package size of this the medication to dispense to the patient.<br />
*'''Critical Admin check-box''' – determines if the medication should be considered important when it is overdue.<br />
*'''Keep On Person Prohibited check-box''' — determines if the patient should or should not carry the medication on their person.<br />
*'''GPI, UPC, HRI''' — identifies products. Enabled for user defined products only.<br />
<br />
==Results==<br />
<br />
[[Image:Results.jpg]]<br />
<br />
*'''RID Selector''' - Clicking on this link will prompt a dialog that allows an administrator to create an association between resultable items and the orderable item.<br />
*'''Results History''' - This check-box indicates whether any historical results for the orderable item should be displayed or suppressed in the Order Details or the Order Viewer.<br />
*'''Resultable Via''' - Controls the method for entering results into the system. The entries in the picklist are described below.<br />
**User - The "user" entry indicates that results for this order can only be entered by a user<br />
**Interface - The "interface" entry indicates that results for this order can only be entered through an interface with an external system. (Note: When sent to interface users will not be able to enter results manually)<br />
**User or Interface - Combination of the options above. This entry allows entry of result data either manually or through an interface with an external system.<br />
<br />
==Instructions==<br />
<br />
[[Image:Instructions.jpg]]<br />
<br />
*'''Order Instructions''' - free text instructions for the lab.<br />
*'''Patient Instructions''' - free text instructions for the patient. If preloaded for the appropriate orderable in the OID these instructions will appear on the requisition if one is generated.<br />
*'''Must Read Order Instructions''' - when checked the "Additional Details" section is expanded in the "Order Details" at the time of order.<br />
*'''Additional Information Questions''' - additional information questions for the lab appear on the Order Detail page. The sequence of additional information questions can be sequenced.<br />
**Additional Information Questions allow for documentation of required information on an orderable item. The options for data entry in these fields include text, picklist, and date/time data. There is no limit to the number of additional information questions that can be associated with an order. <br />
**Additional Information Questions are similar to the Modifier Picklist entries, but the Additional Information Questions are much more flexible in terms of data entry types, number of items that can be associated with an order, and facilitating workflow.<br />
<br />
==Charge/MN==<br />
[[Image:ChargeMN.jpg]]<br />
<br />
*'''When to Charge''' - Indicates whether or not a charge should apply to an orderable item. The entries are described below.<br />
**Never<br />
**Upon Completion<br />
**On Order<br />
**When Resulted<br />
*'''Charge Code''' - This field becomes available for selection based on the entry that is selected in the "When to Charge" field. The link allows for an administrator to select a charge code from the charge code dictionary. The code(s) designated in this field will be the codes that drop to the encounter form when the criteria of the "When to Charge" field are met. <br />
*'''CPT 4 Code''' - This field is only available when the "When to Charge" field is set to "Never". This is a free text box that can be used to enter the CPT 4 code for the orderable item. The entry in this field will allow for orderable item to participate in Medical Necessity Checking (LMRP). <br />
*'''CPT4 Text''' — Free text for CPT 4 description. This field is strictly for documentation within the OID and has no impact on the end-user.<br />
*'''Admin Initial Charge Code''' - This field only applies to medications and immunizations. The link allows for an administrator to associate an administration code that would drop to the encounter form once the order has met the criteria specified in the "When to Charge" field. <br />
*'''Admin Additional Charge Code''' - Allows for a second administration code which generally applies when multiple immunizations or medications are administered to a patient.<br />
<br />
==Behavior==<br />
<br />
[[Image:Behavior.jpg]]<br />
<br />
*'''Not Applicable if Gender Equals''' - Excludes order from search results when patient is of selected gender. This field is used when a certain test is gender specific and should not be able to be selected for both male and female patients. <br />
*'''Priority Default''' - indicates the default clinical priority for the order (Stat, ASAP, Pre-Op)<br />
*'''Reasons for Needs Info Status''' - organizations can select more than one reason for holding the order in a Needs Info status (example: until consent is obtained). The reason must be met before the order can go to an On Hold status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Reasons for Hold For Status''' - organizations can select more than one reason for holding the order in a Hold For status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Ordering Authority''' — determines the ordering authority level that is required for this order.<br />
*'''Duplicate Check Interval''' - determines the interval for duplicate checking in specified time frame. This value overrides the Duplicate Check system preference.<br />
*'''Auto-complete upon order becoming Active''' - determines if the system automatically completes the order when it becomes Active. This is for orders that do not need to be tracked and results are not expected (such as a procedure).<br />
*'''Always Display Order Detail Upon Selection''' - whether to display the Order Detail page upon selection.<br />
<br />
==Specimen==<br />
<br />
[[Image:Specimen.jpg]]<br />
<br />
*'''Specimen Instructions''' – free text instructions for handling the specimen. This information displays on the Order Detail and Specimen Collection pages.<br />
*'''Label Type''' - describes the label type for printing.<br />
*'''List of Valid Clinical Sources''' - describes list of valid source for which to collect the specimen. This is for Charge and Documentation purposes. This can be overridden by the Default Clinical Source can be Overridden option.<br />
*'''List of Valid Specimen Types''' - describes the valid specimen types for this order.<br />
*'''Default Clinical Source can be Overridden''' - determines if the clinical source can be overridden.<br />
*'''Hold for Specimen collection''' - check to activate the order when the specimen collection has been done.<br />
<br />
==Performing==<br />
<br />
[[Image:Performing.jpg]]<br />
<br />
*'''List of Valid Communication Methods''' - describes the valid list of communication methods for the order. Examples are: Instruction,<br />
Procedure, and Rx.<br />
*'''List of Default Communication Methods''' - organizations can select more than one default communication method for the order.<br />
*'''OverDue Interval Routine''' - determines when to consider a Routine order overdue.<br />
*'''OverDue Interval ASAP''' - determines when to consider an ASAP order overdue.<br />
*'''OverDue Interval Stat''' - determines when to consider a Stat order overdue.<br />
*'''OverDue Interval Today''' - determines when to consider an order scheduled to be done on the current day overdue.<br />
*'''Expiration Interval''' - determines when to consider the order expired. Expired orders can be tracked on the Expired Order report.<br />
*'''Overdue Important checkbox''' - when checked a task is generated for the ordering provider if the order is overdue.<br />
*'''Overdue Date and Time Required checkbox''' - determines if an overdue date and time is required when ordering this lab.<br />
*'''Requested Performing Location Identifiers''' - identifies the tests in the appropriate terminology for the performing locations.<br />
<br />
==Identifiers==<br />
<br />
[[Image:Identifiers.jpg]]<br />
<br />
*'''Mapped Medcin ID''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''HCPCS''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''UPC''' - Universal Product Code. Free text field.<br />
*'''LOINC CODE''' - Local Observation Identifiers Names, a data set for universal lab identifiers.<br />
*'''SNOMED''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
<br />
==Instruction Precaution==<br />
<br />
[[Image:Instruction precaution.jpg]]<br />
<br />
*Portions of this article refer to KB article 3108</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Orderable_Item_Dictionary&diff=12492Orderable Item Dictionary2012-02-01T17:49:26Z<p>Larson.Yuill: </p>
<hr />
<div>==Description==<br />
The Orderable Item Dictionary (OID) is the dictionary that holds a list of the unique Order entries. This is typically built based on the compendium from you primary vendor, Allscripts delivered items and may also include tests from your other vendors and/or custom built tests created for an Organization or Site. Ultimately this is the list of Orders that the user will have the ability to Order from the ACI within Enterprise EHR (assuming they are set as Orderable and Users are allowed to order the test in the OID). <br />
<br />
To learn more about building the OID please refer to [[V11 Order and Result Dictionary Build and Synchronization]].<br />
<br />
'''Version Information'''<br />
*[[Article Creation|Article Created based on version]]: 11.1.1<br />
*[[Article Last Update|Last Updated with version]]: 11.1.7<br />
<br />
==Data Grid & Overview==<br />
The dictionary itself is broken down into 2 main classifications, medication and non-medication orderable items. The main data grid displays the set of items that can be ordered, received as resulted order, recorded as resulted orders, as well as entries used for the<br />
classification of other orderable items. Entries could include medications, patient instructions, laboratory items, and radiology items.<br />
<br />
[[Image:Orderable Item.jpg]]<br />
<br />
*'''Code''' - the data parameters for the "Code" field indicate that the entry must be unique within the OID and be 10 characters or less. This code is typically obtained from the organization's lab vendor. <br />
*'''Name''' - the "Name" field indicates that dictionary entry name.<br />
*'''Mnemonic''' - the "Mnemonic" field is similar to the "Code" field in that it shares the same data requirements; the entry must be unique to all other order entries and be 10 characters or less.<br />
*'''Inactive''' - the "Inactive" check-box indicates whether or not the orderable item is "Active". A mark in the check-box indicates that the orderable item is inactive. This field also controls the "OID Mode" field in the Initial details section of the OID. (See below)<br />
<br />
==Initial==<br />
<br />
[[Image:Initial.jpg]]<br />
<br />
*'''Display Name''' - indicates the name that displays in the application for the lab test.<br />
*'''Linked OCD''' - indicates a linked OCD (if exists). Linked OCD will drive modifier behaviors for the lab test.<br />
*'''Orderable check-box''' - indicates whether the dictionary entry is an Orderable Item or a Parent Class.<br />
*'''Complex check-box''' - used for a collection of items that can be performed without ordering. This check-box currently is only supported with the set up of Vital Panels and should not be utilized when building orderable items.<br />
*'''Orderable Via''' - indicates how the item can be ordered (such as, interface or lab).<br />
*'''OID Mode''' - indicates the mode while the item is built. The mode is controlled by the "Inactive" check-box in the OID data grid.<br />
*'''Order Type''' - indicates where this item falls in the hierarchy (display only field). The Order Type is also an indication of where an orderable item can be found in the ACI.<br />
*'''Modifier Picklists''' - organizations can assign up to three modifier picklists to orderable items. Up to three default modifiers from the picklists can be assigned. Modifier picklists allow for documentation of additional information on a particular orderable item. Modifier picklists only allow for entry of information through drop down fields. (see Additional Information Questions as a more flexible alternative)<br />
*'''Required to Save''' — the Required to Save options indicate if this<br />
modifier information is required to save.<br />
<br />
==Medication==<br />
<br />
[[Image:Medication.jpg]]<br />
<br />
*'''NDC''' - (National Drug Code) Universal standard drugs number that’s defaulted from Medispan.<br />
*'''DDI''' - Medispan internal identifier that is used for drug- drug checking, etc.<br />
*'''Control Substance Code''' - indicates scheduled drugs. Drives narcotic behavior. Choices are: Sched 1-5.<br />
*'''Route of Admin''' - determines the default route to administer the drug. It’s possible to have more than one route of admin (need link to what’s available) from the Sig.<br />
*'''Medication Package Size''' — determines what package size of this the medication to dispense to the patient.<br />
*'''Critical Admin check-box''' – determines if the medication should be considered important when it is overdue.<br />
*'''Keep On Person Prohibited check-box''' — determines if the patient should or should not carry the medication on their person.<br />
*'''GPI, UPC, HRI''' — identifies products. Enabled for user defined products only.<br />
<br />
==Results==<br />
<br />
[[Image:Results.jpg]]<br />
<br />
*'''RID Selector''' - Clicking on this link will prompt a dialog that allows an administrator to create an association between resultable items and the orderable item.<br />
*'''Results History''' - This check-box indicates whether any historical results for the orderable item should be displayed or suppressed in the Order Details or the Order Viewer.<br />
*'''Resultable Via''' - Controls the method for entering results into the system. The entries in the picklist are described below.<br />
**User - The "user" entry indicates that results for this order can only be entered by a user<br />
**Interface - The "interface" entry indicates that results for this order can only be entered through an interface with an external system. (Note: When sent to interface users will not be able to enter results manually)<br />
**User or Interface - Combination of the options above. This entry allows entry of result data either manually or through an interface with an external system.<br />
<br />
==Instructions==<br />
<br />
[[Image:Instructions.jpg]]<br />
<br />
*'''Order Instructions''' - free text instructions for the lab.<br />
*'''Patient Instructions''' - free text instructions for the patient. If preloaded for the appropriate orderable in the OID these instructions will appear on the requisition if one is generated.<br />
*'''Must Read Order Instructions''' - when checked the "Additional Details" section is expanded in the "Order Details" at the time of order.<br />
*'''Additional Information Questions''' - additional information questions for the lab appear on the Order Detail page. The sequence of additional information questions can be sequenced.<br />
**Additional Information Questions allow for documentation of required information on an orderable item. The options for data entry in these fields include text, picklist, and date/time data. There is no limit to the number of additional information questions that can be associated with an order. <br />
**Additional Information Questions are similar to the Modifier Picklist entries, but the Additional Information Questions are much more flexible in terms of data entry types, number of items that can be associated with an order, and facilitating workflow.<br />
<br />
==Charge/MN==<br />
[[Image:ChargeMN.jpg]]<br />
<br />
*'''When to Charge''' - Indicates whether or not a charge should apply to an orderable item. The entries are described below.<br />
**Never<br />
**Upon Completion<br />
**On Order<br />
**When Resulted<br />
*'''Charge Code''' - This field becomes available for selection based on the entry that is selected in the "When to Charge" field. The link allows for an administrator to select a charge code from the charge code dictionary. The code(s) designated in this field will be the codes that drop to the encounter form when the criteria of the "When to Charge" field are met. <br />
*'''CPT 4 Code''' - This field is only available when the "When to Charge" field is set to "Never". This is a free text box that can be used to enter the CPT 4 code for the orderable item. The entry in this field will allow for orderable item to participate in Medical Necessity Checking (LMRP). <br />
*'''CPT4 Text''' — Free text for CPT 4 description. This field is strictly for documentation within the OID and has no impact on the end-user.<br />
*'''Admin Initial Charge Code''' - This field only applies to medications and immunizations. The link allows for an administrator to associate an administration code that would drop to the encounter form once the order has met the criteria specified in the "When to Charge" field. <br />
*'''Admin Additional Charge Code''' - Allows for a second administration code which generally applies when multiple immunizations or medications are administered to a patient.<br />
<br />
==Behavior==<br />
<br />
[[Image:Behavior.jpg]]<br />
<br />
*'''Not Applicable if Gender Equals''' - Excludes order from search results when patient is of selected gender. This field is used when a certain test is gender specific and should not be able to be selected for both male and female patients. <br />
*'''Priority Default''' - indicates the default clinical priority for the order (Stat, ASAP, Pre-Op)<br />
*'''Reasons for Needs Info Status''' - organizations can select more than one reason for holding the order in a Needs Info status (example: until consent is obtained). The reason must be met before the order can go to an On Hold status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Reasons for Hold For Status''' - organizations can select more than one reason for holding the order in a Hold For status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Ordering Authority''' — determines the ordering authority level that is required for this order.<br />
*'''Duplicate Check Interval''' - determines the interval for duplicate checking in specified time frame. This value overrides the Duplicate Check system preference.<br />
*'''Auto-complete upon order becoming Active''' - determines if the system automatically completes the order when it becomes Active. This is for orders that do not need to be tracked and results are not expected (such as a procedure).<br />
*'''Always Display Order Detail Upon Selection''' - whether to display the Order Detail page upon selection.<br />
<br />
==Specimen==<br />
<br />
[[Image:Specimen.jpg]]<br />
<br />
*'''Specimen Instructions''' – free text instructions for handling the specimen. This information displays on the Order Detail and Specimen Collection pages.<br />
*'''Label Type''' - describes the label type for printing.<br />
*'''List of Valid Clinical Sources''' - describes list of valid source for which to collect the specimen. This is for Charge and Documentation purposes. This can be overridden by the Default Clinical Source can be Overridden option.<br />
*'''List of Valid Specimen Types''' - describes the valid specimen types for this order.<br />
*'''Default Clinical Source can be Overridden''' - determines if the clinical source can be overridden.<br />
*'''Hold for Specimen collection''' - check to activate the order when the specimen collection has been done.<br />
<br />
==Performing==<br />
<br />
[[Image:Performing.jpg]]<br />
<br />
*'''List of Valid Communication Methods''' - describes the valid list of communication methods for the order. Examples are: Instruction,<br />
Procedure, and Rx.<br />
*'''List of Default Communication Methods''' - organizations can select more than one default communication method for the order.<br />
*'''OverDue Interval Routine''' - determines when to consider a Routine order overdue.<br />
*'''OverDue Interval ASAP''' - determines when to consider an ASAP order overdue.<br />
*'''OverDue Interval Stat''' - determines when to consider a Stat order overdue.<br />
*'''OverDue Interval Today''' - determines when to consider an order scheduled to be done on the current day overdue.<br />
*'''Expiration Interval''' - determines when to consider the order expired. Expired orders can be tracked on the Expired Order report.<br />
*'''Overdue Important checkbox''' - when checked a task is generated for the ordering provider if the order is overdue.<br />
*'''Overdue Date and Time Required checkbox''' - determines if an overdue date and time is required when ordering this lab.<br />
*'''Requested Performing Location Identifiers''' - identifies the tests in the appropriate terminology for the performing locations.<br />
<br />
==Identifiers==<br />
<br />
[[Image:Identifiers.jpg]]<br />
<br />
*'''Mapped Medcin ID''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''HCPCS''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''UPC''' - Universal Product Code. Free text field.<br />
*'''LOINC CODE''' - Local Observation Identifiers Names, a data set for universal lab identifiers.<br />
*'''SNOMED''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
<br />
==Instruction Precaution==<br />
<br />
[[Image:Instruction precaution.jpg]]<br />
<br />
*Portions of this article refer to KB article 3108</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Orderable_Item_Dictionary&diff=12491Orderable Item Dictionary2012-02-01T17:42:10Z<p>Larson.Yuill: </p>
<hr />
<div>==Description==<br />
The Orderable Item Dictionary (OID) is the dictionary that holds a list of the unique Order entries. This is typically built based on the compendium from you primary vendor, but may also include other tests from your other vendors and/or custom built tests created for an Organization or Site. Ultimately this is the list of Orders that the user will have the ability to Order from within Enterprise EHR (assuming they are set as Orderable and Users are allowed to order the test in the OID). <br />
<br />
To learn more about building the OID please refer to [[V11 Order and Result Dictionary Build and Synchronization]].<br />
<br />
'''Version Information'''<br />
*[[Article Creation|Article Created based on version]]: 11.1.1<br />
*[[Article Last Update|Last Updated with version]]: 11.1.7<br />
<br />
==Data Grid & Overview==<br />
The dictionary itself is broken down into 2 main classifications, medication and non-medication orderable items. The main data grid displays the set of items that can be ordered, received as resulted order, recorded as resulted orders, as well as entries used for the<br />
classification of other orderable items. Entries could include medications, patient instructions, laboratory items, and radiology items.<br />
<br />
[[Image:Orderable Item.jpg]]<br />
<br />
*'''Code''' - the data parameters for the "Code" field indicate that the entry must be unique within the OID and be 10 characters or less. This code is typically obtained from the organization's lab vendor. <br />
*'''Name''' - the "Name" field indicates that dictionary entry name.<br />
*'''Mnemonic''' - the "Mnemonic" field is similar to the "Code" field in that it shares the same data requirements; the entry must be unique to all other order entries and be 10 characters or less.<br />
*'''Inactive''' - the "Inactive" check-box indicates whether or not the orderable item is "Active". A mark in the check-box indicates that the orderable item is inactive. This field also controls the "OID Mode" field in the Initial details section of the OID. (See below)<br />
<br />
==Initial==<br />
<br />
[[Image:Initial.jpg]]<br />
<br />
*'''Display Name''' - indicates the name that displays in the application for the lab test.<br />
*'''Linked OCD''' - indicates a linked OCD (if exists). Linked OCD will drive modifier behaviors for the lab test.<br />
*'''Orderable check-box''' - indicates whether the dictionary entry is an Orderable Item or a Parent Class.<br />
*'''Complex check-box''' - used for a collection of items that can be performed without ordering. This check-box currently is only supported with the set up of Vital Panels and should not be utilized when building orderable items.<br />
*'''Orderable Via''' - indicates how the item can be ordered (such as, interface or lab).<br />
*'''OID Mode''' - indicates the mode while the item is built. The mode is controlled by the "Inactive" check-box in the OID data grid.<br />
*'''Order Type''' - indicates where this item falls in the hierarchy (display only field). The Order Type is also an indication of where an orderable item can be found in the ACI.<br />
*'''Modifier Picklists''' - organizations can assign up to three modifier picklists to orderable items. Up to three default modifiers from the picklists can be assigned. Modifier picklists allow for documentation of additional information on a particular orderable item. Modifier picklists only allow for entry of information through drop down fields. (see Additional Information Questions as a more flexible alternative)<br />
*'''Required to Save''' — the Required to Save options indicate if this<br />
modifier information is required to save.<br />
<br />
==Medication==<br />
<br />
[[Image:Medication.jpg]]<br />
<br />
*'''NDC''' - (National Drug Code) Universal standard drugs number that’s defaulted from Medispan.<br />
*'''DDI''' - Medispan internal identifier that is used for drug- drug checking, etc.<br />
*'''Control Substance Code''' - indicates scheduled drugs. Drives narcotic behavior. Choices are: Sched 1-5.<br />
*'''Route of Admin''' - determines the default route to administer the drug. It’s possible to have more than one route of admin (need link to what’s available) from the Sig.<br />
*'''Medication Package Size''' — determines what package size of this the medication to dispense to the patient.<br />
*'''Critical Admin check-box''' – determines if the medication should be considered important when it is overdue.<br />
*'''Keep On Person Prohibited check-box''' — determines if the patient should or should not carry the medication on their person.<br />
*'''GPI, UPC, HRI''' — identifies products. Enabled for user defined products only.<br />
<br />
==Results==<br />
<br />
[[Image:Results.jpg]]<br />
<br />
*'''RID Selector''' - Clicking on this link will prompt a dialog that allows an administrator to create an association between resultable items and the orderable item.<br />
*'''Results History''' - This check-box indicates whether any historical results for the orderable item should be displayed or suppressed in the Order Details or the Order Viewer.<br />
*'''Resultable Via''' - Controls the method for entering results into the system. The entries in the picklist are described below.<br />
**User - The "user" entry indicates that results for this order can only be entered by a user<br />
**Interface - The "interface" entry indicates that results for this order can only be entered through an interface with an external system. (Note: When sent to interface users will not be able to enter results manually)<br />
**User or Interface - Combination of the options above. This entry allows entry of result data either manually or through an interface with an external system.<br />
<br />
==Instructions==<br />
<br />
[[Image:Instructions.jpg]]<br />
<br />
*'''Order Instructions''' - free text instructions for the lab.<br />
*'''Patient Instructions''' - free text instructions for the patient. If preloaded for the appropriate orderable in the OID these instructions will appear on the requisition if one is generated.<br />
*'''Must Read Order Instructions''' - when checked the "Additional Details" section is expanded in the "Order Details" at the time of order.<br />
*'''Additional Information Questions''' - additional information questions for the lab appear on the Order Detail page. The sequence of additional information questions can be sequenced.<br />
**Additional Information Questions allow for documentation of required information on an orderable item. The options for data entry in these fields include text, picklist, and date/time data. There is no limit to the number of additional information questions that can be associated with an order. <br />
**Additional Information Questions are similar to the Modifier Picklist entries, but the Additional Information Questions are much more flexible in terms of data entry types, number of items that can be associated with an order, and facilitating workflow.<br />
<br />
==Charge/MN==<br />
[[Image:ChargeMN.jpg]]<br />
<br />
*'''When to Charge''' - Indicates whether or not a charge should apply to an orderable item. The entries are described below.<br />
**Never<br />
**Upon Completion<br />
**On Order<br />
**When Resulted<br />
*'''Charge Code''' - This field becomes available for selection based on the entry that is selected in the "When to Charge" field. The link allows for an administrator to select a charge code from the charge code dictionary. The code(s) designated in this field will be the codes that drop to the encounter form when the criteria of the "When to Charge" field are met. <br />
*'''CPT 4 Code''' - This field is only available when the "When to Charge" field is set to "Never". This is a free text box that can be used to enter the CPT 4 code for the orderable item. The entry in this field will allow for orderable item to participate in Medical Necessity Checking (LMRP). <br />
*'''CPT4 Text''' — Free text for CPT 4 description. This field is strictly for documentation within the OID and has no impact on the end-user.<br />
*'''Admin Initial Charge Code''' - This field only applies to medications and immunizations. The link allows for an administrator to associate an administration code that would drop to the encounter form once the order has met the criteria specified in the "When to Charge" field. <br />
*'''Admin Additional Charge Code''' - Allows for a second administration code which generally applies when multiple immunizations or medications are administered to a patient.<br />
<br />
==Behavior==<br />
<br />
[[Image:Behavior.jpg]]<br />
<br />
*'''Not Applicable if Gender Equals''' - Excludes order from search results when patient is of selected gender. This field is used when a certain test is gender specific and should not be able to be selected for both male and female patients. <br />
*'''Priority Default''' - indicates the default clinical priority for the order (Stat, ASAP, Pre-Op)<br />
*'''Reasons for Needs Info Status''' - organizations can select more than one reason for holding the order in a Needs Info status (example: until consent is obtained). The reason must be met before the order can go to an On Hold status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Reasons for Hold For Status''' - organizations can select more than one reason for holding the order in a Hold For status. This field is used on the WorkList page. Users can filter orders by status.<br />
*'''Ordering Authority''' — determines the ordering authority level that is required for this order.<br />
*'''Duplicate Check Interval''' - determines the interval for duplicate checking in specified time frame. This value overrides the Duplicate Check system preference.<br />
*'''Auto-complete upon order becoming Active''' - determines if the system automatically completes the order when it becomes Active. This is for orders that do not need to be tracked and results are not expected (such as a procedure).<br />
*'''Always Display Order Detail Upon Selection''' - whether to display the Order Detail page upon selection.<br />
<br />
==Specimen==<br />
<br />
[[Image:Specimen.jpg]]<br />
<br />
*'''Specimen Instructions''' – free text instructions for handling the specimen. This information displays on the Order Detail and Specimen Collection pages.<br />
*'''Label Type''' - describes the label type for printing.<br />
*'''List of Valid Clinical Sources''' - describes list of valid source for which to collect the specimen. This is for Charge and Documentation purposes. This can be overridden by the Default Clinical Source can be Overridden option.<br />
*'''List of Valid Specimen Types''' - describes the valid specimen types for this order.<br />
*'''Default Clinical Source can be Overridden''' - determines if the clinical source can be overridden.<br />
*'''Hold for Specimen collection''' - check to activate the order when the specimen collection has been done.<br />
<br />
==Performing==<br />
<br />
[[Image:Performing.jpg]]<br />
<br />
*'''List of Valid Communication Methods''' - describes the valid list of communication methods for the order. Examples are: Instruction,<br />
Procedure, and Rx.<br />
*'''List of Default Communication Methods''' - organizations can select more than one default communication method for the order.<br />
*'''OverDue Interval Routine''' - determines when to consider a Routine order overdue.<br />
*'''OverDue Interval ASAP''' - determines when to consider an ASAP order overdue.<br />
*'''OverDue Interval Stat''' - determines when to consider a Stat order overdue.<br />
*'''OverDue Interval Today''' - determines when to consider an order scheduled to be done on the current day overdue.<br />
*'''Expiration Interval''' - determines when to consider the order expired. Expired orders can be tracked on the Expired Order report.<br />
*'''Overdue Important checkbox''' - when checked a task is generated for the ordering provider if the order is overdue.<br />
*'''Overdue Date and Time Required checkbox''' - determines if an overdue date and time is required when ordering this lab.<br />
*'''Requested Performing Location Identifiers''' - identifies the tests in the appropriate terminology for the performing locations.<br />
<br />
==Identifiers==<br />
<br />
[[Image:Identifiers.jpg]]<br />
<br />
*'''Mapped Medcin ID''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''HCPCS''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
*'''UPC''' - Universal Product Code. Free text field.<br />
*'''LOINC CODE''' - Local Observation Identifiers Names, a data set for universal lab identifiers.<br />
*'''SNOMED''' - This field is automatically populated when an orderable item is mapped to an OCD.<br />
<br />
==Instruction Precaution==<br />
<br />
[[Image:Instruction precaution.jpg]]<br />
<br />
*Portions of this article refer to KB article 3108</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Patient_banner&diff=12385Patient banner2012-01-18T22:12:12Z<p>Larson.Yuill: </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 is sent from the the PM or IDX application 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 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.'''<br />
<br />
'''Note: If the xml values are edited, but the change is not immediately reflected in the patient banner, please review the permmissions for CustomBanner.xml and confirm that 'Everyone' has access to the file.'''<br />
<br />
[[Image:patientbannerpermissions.jpg]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Implementation_Lessons_Learned&diff=12383Implementation Lessons Learned2012-01-18T22:01:03Z<p>Larson.Yuill: </p>
<hr />
<div>'''Implementation Lessons Learned'''<br />
<br />
==Things clients wished they would have realized earlier in the implementation process==<br />
<br />
* Expect that you will make changes to build as you go. No matter how much research you did, how many meetings you held, or who provided input you will make changes to your build as your organization matures it's use of the EHR. <br />
<br />
==Things that worked out well for clients==<br />
<br />
* Solid base of Super Users with strong skill sets and good knowledge of the application<br />
<br />
* Go-live support is a must<br />
<br />
* Sites where the clinic manager was involved the adoption and implementation was a bigger success <br />
<br />
* Pre-go-live meetings are beneficial to discuss what to expect with the groups as well as review workflows<br />
<br />
* Mini-go-live 1 week prior to Go-live with real patients (2 or 3) this gives a chance to work out any major bugs early. <br />
<br />
* Combined training for clinical staff and providers (this depends on who you ask)<br />
<br />
* An EHR weekly communication is vital to keep the organization informed<br />
<br />
* Including screen shots in communications and training materials was helpful<br />
<br />
* Post go-live visits are crucial to perform post go-live optimizations or assess for advanced training needs.<br />
<br />
* Obtaining input from clinical staff during the build process created a tremendous amount of ownership and buy-in<br />
<br />
* Spending the time to load historical information on patients was very useful in assisting staff to learn how to navigate<br />
<br />
* Allowing for different learning styles; Captivate sessions, class room sessions, handouts, etc.<br />
<br />
* Keeping operations informed throughout the process<br />
<br />
* Holding a launch event prior to implementation to showcase the project and what to expect with the EHR<br />
<br />
* Requiring providers to sign a commitment letter to use the EHR<br />
<br />
* Creating a escalation ticket process for clinics during go-live works great to identify immediate tickets needs<br />
<br />
* Flexibiity of team <br />
<br />
==Things that didn't work well for clients==<br />
<br />
* An interactive Captivate training session<br />
<br />
* Make sure your executive leadership meeting content is clear<br />
<br />
* Not addressing equipment needs early in the project<br />
<br />
* Expecting perfection sets everyone up for failure<br />
<br />
* Communication among team members and home base was not the best<br />
<br />
* Need many different communication methods<br />
<br />
* Not documenting current and future state workflows<br />
<br />
* Not having someone with a clinical background on the project or training team</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Build_Flowsheets&diff=11369Build Flowsheets2011-07-06T20:21:34Z<p>Larson.Yuill: /* Build a new Flowsheet */</p>
<hr />
<div>Rows from Upgrade Build Workbook_Phase 1.xls:<br />
<br />
Define Result items that should be considered equivalent when included in a flowsheet.<br />
<br />
Review flowsheets that contain Medcin Findings and build corresponding clinical forms.<br />
<br />
==Flowsheet Overview==<br />
<br />
Flowsheets serve as a convenient tool for looking at patient data over time and analyzing trends<br />
<br />
*Columns – represent an interval of time (for example: a week or a day) (month, year?)<br />
*Rows – represent selected clinical data (for example: vital signs or lab results) (Medcin findings?)<br />
<br />
<br />
[[Image:Flowsheet.jpg]]<br />
<br />
==Access Flowsheet Builder==<br />
<br />
Login to TouchWorks using a TW Administrative account (TWAdmin)<br />
#Change the workplace from TWAdmin to Phys Admin<br />
#Expand the By Category menu item in the VTB<br />
#Select Flowsheets<br />
<br />
[[Image:Access_Flowsheet_Builder_75.jpg]]<br />
<br />
==Flowsheets are organized by Specialty==<br />
<br />
Allscripts docs containd the text:<br />
<br />
"Grouping Flowsheets in folders makes locating, selecting and managing patient data easier. For example, an organization might want to group their Flowsheets by problem, protocol, physician or department."<br />
<br />
"By grouping Flowsheets in categories (that is, folders), clinicians are able to access and manage patient data effectively. For example: an organization might group their Flowsheets by problem, protocol, provider, or department."<br />
<br />
(Need more informantion about "grouping Flowsheets by problem, protocol, physician or department")<br />
<br />
(Allscripts Documentation does not mention "Unassigned" category. I added the section below to clarify the Unassigned category.)<br />
<br />
* The default category in the Specialty dropdown is 'Unassigned'<br />
<br />
* 'Unassigned' displays any flowsheets not assigned to a specialty<br />
<br />
[[Image:Unassigned.jpg]] <br />
<br />
* Select 'Family Medicine' from the Specialty dropdown<br />
<br />
[[Image:Family_Medicine.jpg]]<br />
<br />
* The list of flowsheets linked to 'Family Medicine' appears<br />
<br />
* Select 'Asthma'<br />
<br />
[[Image:Asthma.jpg]]<br />
<br />
* The build items for the 'Asthma' flowsheet are displayed (make this image smaller)<br />
<br />
[[Image:View_Flowsheet.jpg]]<br />
<br />
* To see how the flowsheet will look select 'preview'<br />
<br />
[[Image:preview.jpg]] (same image as above but with preview selected)<br />
<br />
* Flowsheets can be linked to one or more Specilties.<br />
<br />
* Select a flowsheet and use the add and delete buttons to assign specialties<br />
<br />
* Flowsheets can be linked to one or more diagnosis as well.<br />
<br />
* Select a flowsheet and use the link and unlink buttons to assign problems.<br />
<br />
* It is important to note that if a patient does not have any of the listed diagnoses entered onto the chart, then the staff/provider will be unable to access this flowsheet. For that reason, it is not normally recommended to link diagnoses to a flowsheet.<br />
<br />
==Build a new Flowsheet ==<br />
<br />
# Select the Specialty to which the new Flowsheet will belong.<br />
# Click the New button.<br />
# Enter the Name of the new Flowsheet.<br />
# Link the Flowsheet to a problem or problems if necessary.<br />
# To add an orderable item, click Add Item.<br />
# Select a Classification to browse or use the Search field.<br />
# To add a Medcin Finding, click Add Findings.<br />
# Select a Classification of findings or use the Search field.<br />
# When finished adding the desired items, Preview the Flowsheet.<br />
# If changes need to be made to the order in which any item presents in the flowsheet, highlight the item and use the up and down arrows located in the bottom right of build box.<br />
# Once you are satisfied with the Flowsheet, click Save to make available to users or:<br />
# Click Save as Draft to keep hidden from users until it can be competed later.<br />
<br />
Follow steps 3-9 to edit existing Flowsheets. <br />
<br />
[[Image:Build_Flowsheet.jpg]]<br />
<br />
(Rebuild this image to improve resolution, make 10% smaller to fit image and instructions on same screen)<br />
<br />
"A PDF version of the above steps and image can be found On the Allscripts<br />
Knowledge Base. On the TouchWorks V11 Resources Page, under the Implementation Documents<br />
section, click Allscripts Red Lessons."<br />
(This text is from the bottom of the doc and is not correct for the internal KB)<br />
(need access to client KB to confirm path)<br />
<br />
==Add Orderable Item to a Flowsheet==<br />
To add orderable items to a Flowsheet, do the following: <br />
<br />
#On the Flowsheet Builder page, select the appropriate Flowsheet. <br />
#Click Add Item. The system displays the Orderable Item Search page. <br />
#You can search for the appropriate orderable items by using one of the following methods: <br />
#*Classification/Sub-classification search <br />
#*Master dictionary search <br />
#*Description search <br />
#Select the appropriate items from the Orderable Items list, and then click the right arrow to move them to the Selected Orderable Items list. <br />
#Click OK. <br />
<br />
==Additional Resources==<br />
*KB Article #3946 – Configuration Guide Topics – Building Flowsheets.pdf (4 page guide on building flowsheets)<br />
*KB Article #3133 – ITT Flowsheet Builder.pdf (12 page guide on building flowsheets)<br />
(Accessable to clients?)<br />
<br />
==View Flowsheet in user interface==<br />
<br />
#Navigate to the Clinical Desktop<br />
#Select HMP<br />
#Change the View to Flowsheets<br />
#Select Proper Specialty<br />
#Select Desired Flowsheet<br />
<br />
(rebuild this image to include number labels, consider increasing crop to include CDT context)<br />
<br />
[[Image:flowsheet in user interface.jpg]]</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Additional_Information_Configuration&diff=11361Additional Information Configuration2011-06-30T14:03:43Z<p>Larson.Yuill: /* Definition */</p>
<hr />
<div>=Definition=<br />
Order(able) item questions, additional information questions, "AOEs" and order entry questions are all terms used by 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 />
This dictionary can be extracted and maintained via SSMT. It is important to note that the answers included in any picklist for these additional information question are found in a separate dictionary called "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 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>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=Additional_Information_Configuration&diff=11360Additional Information Configuration2011-06-30T14:02:03Z<p>Larson.Yuill: /* Definition */</p>
<hr />
<div>=Definition=<br />
Order(able) item questions, additional information questions, "AOEs" and order entry questions are all terms used by 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 />
This dictionary can be extracted and maintained via SSMT. It is important to note that the answers included in any picklist for these additional information question are a separate dictionary called "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 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>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=EMR_Success_Factors&diff=11359EMR Success Factors2011-06-30T13:41:40Z<p>Larson.Yuill: </p>
<hr />
<div>== Steps to make the EMR a success! ==<br />
<br />
<br />
*Exceptional project management and control<br />
**Ongoing meetings with [[EMR Committee]]<br />
**Establish champions of the EMR<br />
**Set realistic project management processes<br />
**Gather appropriate data and perform necessary research<br />
<br />
*Effective communication<br />
**Remind people of the benefits and convenience of an EMR<br />
**Make sure everyone understand the reason for the change<br />
**Welcome constructive ideas, reward positive suggestions and discourage any negative attitude or discussion<br />
**Communicate throughout implementation process of steps taken<br />
**Check in with staff regularly to offer validation of concerns<br />
**Communicate ongoing support plan<br />
**Communicate with providers and staff what is required to get the job done<br />
<br />
*Goals Specified<br />
**Completely understand the current workflow of the office<br />
**Set specific goals for desired outcomes<br />
**Success must be defined ahead of time (i.e., [[EHR Metrics]] to measure ROI, etc.)<br />
<br />
*Strategy for entering the practice’s old data<br />
**How are you going to add old medications, problems, and allergies?<br />
**Define Scanning strategy<br />
**Full comprehension of project complexity<br />
**Strong project management team<br />
**Obtain providers commitment to complete assigned tasks in a timely manner<br />
**Provide users with short overview<br />
**Understanding what to expect <br />
**Determine need for temporary staffing<br />
<br />
*Training is crucial<br />
**Demo days<br />
**Two-to-Four hour training sessions<br />
**Conduct dry runs/Mock Training<br />
**Train super users<br />
**Accessible training materials (webcasts, e-learning)<br />
<br />
*Go Live Armed<br />
**Schedule fewer patients<br />
**Commit resources</div>Larson.Yuillhttps://wiki.galenhealthcare.com/index.php?title=EMR_Success_Factors&diff=11358EMR Success Factors2011-06-30T13:40:54Z<p>Larson.Yuill: </p>
<hr />
<div>== Steps to make the EMR a success! ==<br />
<br />
<br />
*Exceptional project management and control<br />
**Ongoing meetings with [[EMR Committee]]<br />
**Establish champions of the EMR<br />
**Set realistic project management processes<br />
**Gather appropriate data and perform necessary research<br />
<br />
*Effective communication<br />
**Remind people of the benefits and convenience of an EMR<br />
**Make sure everyone understand the reason for the change<br />
**Welcome constructive ideas, reward positive suggestions and Discourage any negative attitude or discussion<br />
**Communicate throughout implementation process of steps taken<br />
**Check in with staff regularly to offer validation of concerns<br />
**Communicate ongoing support plan<br />
**Communicate with providers and staff what is required to get the job done<br />
<br />
*Goals Specified<br />
**Completely understand the current workflow of the office<br />
**Set specific goals for desired outcomes<br />
**Success must be defined ahead of time (i.e., [[EHR Metrics]] to measure ROI, etc.)<br />
<br />
*Strategy for entering the practice’s old data<br />
**How are you going to add old medications, problems, and allergies?<br />
**Define Scanning strategy<br />
**Full comprehension of project complexity<br />
**Strong project management team<br />
**Obtain providers commitment to complete assigned tasks in a timely manner<br />
**Provide users with short overview<br />
**Understanding what to expect <br />
**Determine need for temporary staffing<br />
<br />
*Training is crucial<br />
**Demo days<br />
**Two-to-Four hour training sessions<br />
**Conduct dry runs/Mock Training<br />
**Train super users<br />
**Accessible training materials (webcasts, e-learning)<br />
<br />
*Go Live Armed<br />
**Schedule fewer patients<br />
**Commit resources</div>Larson.Yuill