New pages
(newest | oldest) View (newer 20 | older 20) (20 | 50 | 100 | 250 | 500)
- 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…')