Difference between revisions of "V11 Note"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 1: Line 1:
Brief steps to create an Allscripts Enterprise EHR v11 Note:
+
__TOC__
 +
 
 +
==Brief steps to create an Allscripts Enterprise EHR v11 Note:==
 
*Create Visit Type & Sub-Type  
 
*Create Visit Type & Sub-Type  
 
*Validate Specialty & Sub-specialty  
 
*Validate Specialty & Sub-specialty  
Line 13: Line 15:
 
==V11.2 Note Changes==
 
==V11.2 Note Changes==
 
[[Changes to v11.2. Note]]
 
[[Changes to v11.2. Note]]
 +
 +
==FAQ==
 +
Q: Is it best practice to bring over all noteforms and note templates from Test to Live or is it best practice to bring over only those note templates and NoteForms that have been tested and the organization has decided to use?
 +
*Only move from Test to Production those note templates the organization will be using and those noteforms the organization may have tweaked and put inside those note templates.
 +
 +
*However the base install of all the noteforms should be installed in Production.  Typically clients do NOT inactivate noteforms they have not tested, because this would limit the noteforms that are pulled into the note for symptom or problem-based forms.

Revision as of 19:31, 23 February 2012

Brief steps to create an Allscripts Enterprise EHR v11 Note:

  • Create Visit Type & Sub-Type
  • Validate Specialty & Sub-specialty
  • Validate all needed Note Sections exist, add as needed
  • Validate Symptom details with existing content or create new
  • Validate Text Templates with existing content or create new
  • Validate Note Form details with existing content or create new
  • Create a Note Input Template
  • Associate Input Template to desired Output Template(s)
  • Create Print Template as desired in Document Admin
  • Setup AutoPrint Defaults as desired

V11.2 Note Changes

Changes to v11.2. Note

FAQ

Q: Is it best practice to bring over all noteforms and note templates from Test to Live or is it best practice to bring over only those note templates and NoteForms that have been tested and the organization has decided to use?

  • Only move from Test to Production those note templates the organization will be using and those noteforms the organization may have tweaked and put inside those note templates.
  • However the base install of all the noteforms should be installed in Production. Typically clients do NOT inactivate noteforms they have not tested, because this would limit the noteforms that are pulled into the note for symptom or problem-based forms.