Difference between revisions of "V11 Specialty Favorites"
(Touchworks EHR v11 Specialty Build) |
|||
Line 1: | Line 1: | ||
In the context of Touchworks EHR version 11, the build for specialty content becomes a great way to promote enterprise standardization and unity. Allscripts delivers content by specialty. I found it useful to query out the data from the database to begin the customization to meet our needs. We found that delivery of a Specialty favorites list containing input from several individuals, was the way to go from a build standpoint. Even if it contains hundreds of entries I personally don't use, the active searching brings it down to just a few entries with only 3 or 4 keystrokes. | In the context of Touchworks EHR version 11, the build for specialty content becomes a great way to promote enterprise standardization and unity. Allscripts delivers content by specialty. I found it useful to query out the data from the database to begin the customization to meet our needs. We found that delivery of a Specialty favorites list containing input from several individuals, was the way to go from a build standpoint. Even if it contains hundreds of entries I personally don't use, the active searching brings it down to just a few entries with only 3 or 4 keystrokes. | ||
+ | |||
+ | Here are some SQL queries that were helpful in the process: | ||
+ | |||
+ | [[Image:Immun favs by specialty.sql]] | ||
+ | [[Image:Med Hx Favorites by specialty.sql]] | ||
+ | [[Image:med favs by specialty.sql]] | ||
+ | [[Image:Med allergen favs by specialty.sql]] | ||
+ | [[Image:Med Admin Favorites by specialty.sql]] | ||
+ | [[Image:immun hx favs by specialty.sql]] | ||
+ | [[Image:immun favs by specialty.sql]] | ||
+ | [[Image:allergen hx favs by specialty.sql]] |
Revision as of 13:41, 30 August 2007
In the context of Touchworks EHR version 11, the build for specialty content becomes a great way to promote enterprise standardization and unity. Allscripts delivers content by specialty. I found it useful to query out the data from the database to begin the customization to meet our needs. We found that delivery of a Specialty favorites list containing input from several individuals, was the way to go from a build standpoint. Even if it contains hundreds of entries I personally don't use, the active searching brings it down to just a few entries with only 3 or 4 keystrokes.
Here are some SQL queries that were helpful in the process:
File:Immun favs by specialty.sql File:Med Hx Favorites by specialty.sql File:Med favs by specialty.sql File:Med allergen favs by specialty.sql File:Med Admin Favorites by specialty.sql File:Immun hx favs by specialty.sql File:Immun favs by specialty.sql File:Allergen hx favs by specialty.sql