New pages
(newest | oldest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
- 12:58, 14 April 2010 Copying Existing Fields (hist) [1,317 bytes] Docs root (talk | contribs) (Created page with 'You may <strong>not edit existing fields that come with the iMedConsent program </strong> (with the exception of the three fields mentioned here), but…')
- 12:56, 14 April 2010 Copying Document Activity Profiles (hist) [2,581 bytes] Docs root (talk | contribs) (Created page with 'Anytime you create a ''new'' specialty in iMedConsent that contains consent categories, you must assign a Document Activity Profile (DAP) to it. You will have to create separate…')
- 12:41, 14 April 2010 What You Can Do When You Right Click on a Document (hist) [1,851 bytes] Docs root (talk | contribs) (Created page with 'As an administrative user, there are several functions when right clicking on a '''single document'''. A brief description of each item is as follows: <ul><li>'''''View''''' -…')
- 12:40, 14 April 2010 What is iMedConsent? (hist) [487 bytes] Docs root (talk | contribs) (Created page with '==Description== IMedConsent is a software application designed and created to automate the process associated with medical procedure consent forms to patients seeking treatment a…')
- 12:38, 14 April 2010 "Directions" Field (hist) [1,819 bytes] Docs root (talk | contribs) (Created page with 'Many of the documents under the Tests and Admissions category have a field that prompts for directions to a particular area of your hospital (e.g., same-day surgery). If anyone …')
- 12:37, 14 April 2010 "Additional Information" Screen (hist) [1,120 bytes] Docs root (talk | contribs) (Created page with 'The Additional Information screen (item #17 on the completed consent screen) may be customized by the administrator and may be edited by the end user. Many VA sites are using th…')
- 19:17, 2 April 2010 Generating Reports (hist) [1,326 bytes] Docs root (talk | contribs) (Created page with 'There are currently three reports available in iMedConsent. To open the list of reports, select '''Maintenance -> Reports'''.<br><br> Image:addn_gen_cag_html_131502d5.png<br>…')
- 19:17, 2 April 2010 Sharing and Moving Documents (hist) [737 bytes] Docs root (talk | contribs) (Created page with 'There may be situations where you want a procedure in one specialty to exist in another specialty as well. To “share” this procedure, follow these steps. <ol><li>Right-cl…')
- 19:16, 2 April 2010 Using the Favorites Feature (hist) [1,371 bytes] Docs root (talk | contribs) (Created page with 'The Favorites feature gives the user the ability to focus on those documents that he or she uses frequently. Users can create a list of documents for easy access that is saved un…')
- 19:16, 2 April 2010 Locating the Error Log (generic) (hist) [697 bytes] Docs root (talk | contribs) (Created page with 'If you encounter an iMedConsent error on a workstation and need to call technical support, it is helpful to copy the contents of the Error Log for that workstation. To find the …')
- 19:15, 2 April 2010 Overview of DAP Screen (Generic) (hist) [6,977 bytes] Docs root (talk | contribs) (Created page with '__TOC__ == What are Document Activity Profiles? == Document Activity Profiles (DAPs) provide an extensible and granular way to define behavior of documents throughout the consen…')
- 19:13, 2 April 2010 Creating New Procedures in the Library (hist) [1,300 bytes] Docs root (talk | contribs) (Created page with 'You may create consents for procedures not included in the iMedConsent library. To create a local consent, follow these steps: <ol><li>From the toolbar, click File -> New</li> <…')
- 19:13, 2 April 2010 Creating Parent Templates (hist) [7,083 bytes] Docs root (talk | contribs) (Created page with 'A Parent template drives the look and feel of your consent documents. Child documents (for example, Procedures) will all have the same look if they are attached to the same paren…')
- 19:12, 2 April 2010 Creating New Categories (hist) [1,273 bytes] Docs root (talk | contribs) (Created page with 'Once you create a new Specialty, you must then create a new category if you want to store non-consent documents here. To create a category: <ol><li>From the toolbar, click Ma…')
- 19:12, 2 April 2010 Creating New Specialties (Generic) (hist) [1,009 bytes] Docs root (talk | contribs) (Created page with 'You may create your own specialty in iMedConsent to include local forms and/or consents (Primary Care, for example). To create a specialty: <ol><li>From the toolbar, click Ma…')
- 19:12, 2 April 2010 Creating Signature Fields (hist) [2,268 bytes] Docs root (talk | contribs) (Created page with 'Some facilities want to capture patient and/or witness signatures on their education and other non-consent documents. Administrators may add a signature field to new and existin…')
- 19:11, 2 April 2010 Creating Non-Consent Documents (Generic) (hist) [1,151 bytes] Docs root (talk | contribs) (Created page with 'There may be instances when you will want to add non-consent documents (such as your local forms or new educational documents) to the library in iMedConsent. To add a new docume…')
- 19:11, 2 April 2010 Creating Local Fields (Generic) (hist) [1,242 bytes] Docs root (talk | contribs) (Created page with 'You may create your own local fields for use in consents and non-consent documents. Examples of non-consent documents are your own local forms (Release of Information document), …')
- 19:11, 2 April 2010 Copying Document Activity Profiles (Generic) (hist) [1,947 bytes] Docs root (talk | contribs) (Created page with 'Anytime you create a ''new'' specialty in iMedConsent that contains consent categories, you must assign a Document Activity Profile (DAP) to it. You will have to create separate…')
- 19:10, 2 April 2010 Copying Existing Fields (Generic) (hist) [1,308 bytes] Docs root (talk | contribs) (Created page with 'Please do not edit existing fields that come with the iMedConsent program since they may be linked to a consent or educational document. You may copy an existing field and edit …')
- 19:10, 2 April 2010 Editing the "Directions" Field (hist) [1,835 bytes] Docs root (talk | contribs) (Created page with 'Many of the documents under the <strong>Tests and Admissions</strong> category have a field that prompts for directions to a particular area of your hospital (e.g., same-day surg…')
- 19:10, 2 April 2010 Editing Non-Consent Documents (Generic) (hist) [881 bytes] Docs root (talk | contribs) (Created page with 'The administrator may make permanent changes to non-consent documents. Non-consent documents include: <UL> <LI>Education (Easy Reading and Standard)</li> <LI>Patient Instructions…')
- 19:09, 2 April 2010 Editing the "Additional Information" Screen (Generic) (hist) [1,303 bytes] Docs root (talk | contribs) (Created page with 'The Additional Information screen may be customized by the administrator and may be edited by the end user. You may use this field to add local information to the consent templa…')
- 19:08, 2 April 2010 Editing Document Headers (hist) [510 bytes] Docs root (talk | contribs) (Created page with 'The following are instructions for editing the header, which displays the facility name and address at the top of the consents and other documents (with the exception of Drug Inf…')
- 19:06, 2 April 2010 Contacting Dialog Medical Technical Support (hist) [400 bytes] Docs root (talk | contribs) (Created page with ''''Dialog Medical Customer Support phone numbers:''' :(800) 482-7963 toll free<br> :(770) 982-7851, option 2 '''Fax:''' :(770) 736-5725 '''E-mail Customer support''' :For th…')
- 19:06, 2 April 2010 IMedConsent Customer Support Page (hist) [136 bytes] Docs root (talk | contribs) (Created page with 'See [http://support.dialogmedical.com http://support.dialogmedical.com] for Knowledgebase articles and to submit or review help tickets.')
- 19:06, 2 April 2010 Deleting Unnecessary Files from the iMedConsent Server (hist) [2,806 bytes] Docs root (talk | contribs) (Created page with 'Trace logs, images and completed document files are retained on the server until manually purged by an IT administrator. These files should be removed on a regular basis to fre…')
- 19:05, 2 April 2010 What To Do When There Is an Error in iMedConsent - Locating the Error Log (hist) [715 bytes] Docs root (talk | contribs) (Created page with 'When encountering an iMedConsent error on a workstation, prior to calling technical support, it is helpful to copy the contents of the Error Log for that workstation. To find th…')
- 19:05, 2 April 2010 IMedConsent Security (hist) [6,081 bytes] Docs root (talk | contribs) (Created page with 'This section explains the security roles in iMedConsent, what access each provides and how to administer them. NOTE: The iMedConsent system relies on the local facility system (…')
- 19:04, 2 April 2010 Overview of Field Order and Creating Rules for Normal Documents (hist) [5,346 bytes] Docs root (talk | contribs) (Created page with '== Field Order == After adding text and fields to normal documents, administrative users may want to establish the Field Order. The Field Order represents the order in which t…')
- 19:04, 2 April 2010 Don't Combine Procedures with "Consent for Treatment/Procedure not in Library" (hist) [235 bytes] Docs root (talk | contribs) (Created page with 'It is no longer possible to combine the “Consent for Treatment/Procedure not in Library” with other consent forms. If the user attempts to do so, the following message will …')
- 19:04, 2 April 2010 Blood Product Enhancements (hist) [1,251 bytes] Docs root (talk | contribs) (Created page with 'The “Consent for Blood Products” screens in the consent program have been modified to make them easier to complete. The blood products screen now includes one question with t…')
- 19:03, 2 April 2010 Comments Screen Enhancements (hist) [1,240 bytes] Docs root (talk | contribs) (Created page with 'Previously, the “Comments” section was a free-text area that did not automatically appear in the “Basic” mode. Practitioners had to complete the consent form and then sel…')
- 19:03, 2 April 2010 DAPS 101 (hist) [3,637 bytes] Docs root (talk | contribs) (Created page with ''''''Document Activity Profile''''': A set of rules that defines how documents behave (are processed) in the system <br> Every document in the system is associated to at least 1…')
- 19:03, 2 April 2010 Adding a Signature Field (hist) [1,384 bytes] Docs root (talk | contribs) (Created page with 'To add a prompt for patient, physician or witness signatures, either click the "Insert Field" button to choose an existing signature field in the database or click "Create Field"…')
- 19:02, 2 April 2010 Editing Existing Fields (hist) [426 bytes] Docs root (talk | contribs) (Created page with 'With three exceptions, administrative users may '''''not edit''''' existing fields that come with the iMedConsent program because they are linked to National consents and non-con…')
- 19:02, 2 April 2010 Editing Non-Consent Documents (hist) [942 bytes] Docs root (talk | contribs) (Created page with 'Currently, only the administrator may make permanent changes to the following documents: <UL> <LI> Education (Easy Reading and Standard) <LI> Patient Instructions <LI> Tests and …')
- 19:01, 2 April 2010 Spanish User Interface Feature (hist) [5,096 bytes] Docs root (talk | contribs) (Created page with '==Spanish User Interface Feature == The primary purpose of these multi-lingual changes in the application is to deliver educational documents and completed consent documents in b…')
- 19:00, 2 April 2010 How to Edit Facility Specific Procedure Notes for Consent Documents (hist) [1,298 bytes] Docs root (talk | contribs) (Created page with 'When an iMed Administrator views a consent procedure in “edit” mode, the screen display now appears like this: <br>600px<br><br> Notice the list of se…')
- 19:00, 2 April 2010 Guidelines for Updating Facility Specific Procedure Notes (hist) [2,460 bytes] Docs root (talk | contribs) (Created page with 'The purpose of the Facility Specific Procedure Notes section is to allow facilities to add additional information to individual consent forms. Before asking Specialty Chiefs w…')
- 18:59, 2 April 2010 Chemotherapy Consent Categories Available Under Hematology and Oncology (hist) [1,256 bytes] Docs root (talk | contribs) (Created page with 'New categories now appear under the Hematology and Oncology specialty. '''These categories contain agent-specific consent forms for Chemotherapy (individual agents, combinatio…')
- 18:59, 2 April 2010 Education Documents Enabled with Document Teaching and Assessment Feature (hist) [2,186 bytes] Docs root (talk | contribs) (Created page with 'This new feature, which is available on most education documents (Education – Easy Reading, Education – Standard, and Patient Instructions) enables clinicians and patient edu…')
- 18:59, 2 April 2010 Editing the Additional Information Screen - Please Review (hist) [1,392 bytes] Docs root (talk | contribs) (Created page with 'The Additional Information screen (item #17 on the completed consent screen) may be permanently customized by administrators and individually edited by end users. Text added here…')
- 18:34, 2 April 2010 Sharing (Shadowing) Consent and Non-Consent Forms Across Multiple Specialties (hist) [1,112 bytes] Docs root (talk | contribs) (Created page with 'iMedConsent allows administrators to “share” procedures in multiple specialties. Administrative users can do this with individual documents or as a group. Here are the ste…')
- 18:33, 2 April 2010 Content Request Link Added to the Main Page of iMedConsent (hist) [917 bytes] Docs root (talk | contribs) (Created page with 'A new '''Content Request link''' has been provided on the main page of iMedConsent. When a user clicks this link, the Content Request form is opened in a web browser. The Conten…')
- 18:33, 2 April 2010 Job Monitor and Email Notification System for Monitoring Job Monitor Errors (hist) [1,832 bytes] Docs root (talk | contribs) (Created page with 'The '''Job Monitor''' is a stand-alone application that shows the overall state of iMedConsent jobs going to VistA. It is set to look at the '''''holding to process''''' folder o…')
- 18:32, 2 April 2010 Create DAPs When Adding Local Documents in iMedConsent (hist) [2,045 bytes] Docs root (talk | contribs) (Created page with 'When you add local documents to iMedConsent™ (especially documents with fields in them), Dialog Medical recommends creating unique DAPS for these to make sure they work the way…')
- 18:31, 2 April 2010 Administrative Features Right-Clicking on a Document (hist) [1,852 bytes] Docs root (talk | contribs) (Created page with 'As an administrative user, there are several functions when right clicking on a '''single document'''. A brief description of each item is as follows: <ul><li>'''''View''''' -…')
- 18:31, 2 April 2010 About (hist) [158 bytes] Docs root (talk | contribs) (Created page with 'Selecting About details the current version of iMedConsent running at that facility. The following screen will open:<br><br> Image:About_-_1.JPG<br><br>')
- 18:31, 2 April 2010 Administration (hist) [78 bytes] Docs root (talk | contribs) (Created page with 'Selecting this will take you to the iMedConsent Content Administrator's Guide.')
