Loading...
Recommendations
Explore
Template Server Cache Deployment
The following diagram depicts template caching using the Template Server Cache Path preference.
Template Server Cache Deployment
NextGen® Enterprise EHR Template Editor Help, 8.3.1
Template Caching Workflows
This section provides flowcharts that show how the most recent cache file is identified and how the Template Server Cache option is used. Parent topic: Template Caches
NextGen® Enterprise EHR Template Editor Help, 8.3.1
Cache an Individual Template
To cache a specific template, you must access the Template Cache Generator from Template Editor. Open the template you want to cache. From the Tools menu, select Create Cache, and then select This Template. The NextGen Template Cache Generator window opens. You do not need to enter any information. The template is cached in the Template Server Cache path designated in Templates Preferences in the System Administrator application. Parent topic: Template Caches
NextGen® Enterprise EHR Template Editor Help, 8.3.1
Universal Preferences for Template Caches
Set up the applicable cache paths under Templates Universal Preferences in the System Administrator application. If you have more than one database, set up separate path locations for caching the template files for each database. Preference Description Template Cache Path Enter the directory path to be used to store template files that are cached. Note: You can designate the directory to be used to store cached files in your ngconfig.ini file instead of the Template Cache Path. If you choose that option, do not enter this preference. Template Server Cache Path Enter the directory path to be used to store template files that are cached using the Template Cache Generator. CAUTION: You must enter this path to run the Template Cache Generator. If this path is missing, the cache file is created in the Template Cache Path. Note: NextGen Healthcare recommends that you use the Template Server Cache Path if you have a large number of systems running against your database. It reduces the load on
NextGen® Enterprise EHR Template Editor Help, 8.3.1
Accessing the Most Recent Cache File
When a user accesses a template, the system compares the time stamp of the local cache file to the time stamp of the template in the database. If the files are not in sync, the system compares the time stamp of the local cache file to the time stamp in the shared cache directory. If the local cache file is older than the server cache file, the server cache file is written to the local cache directory. If the server cache file is older than the local cache file, the local cache file is written to the local cache directory and pushed up to the shared cache directory. The following diagram depicts this template caching process. Parent topic: Template Caches
NextGen® Enterprise EHR Template Editor Help, 8.3.1
On-demand Template Caching
You can perform manual template caching if you need to do the following: Cache a selected NextGen® Enterprise EHR to regenerate the cache. A locked-down template cannot be modified and saved, so automatic caching does not take place. Cache all templates when there is a new Template Editor version or patch or NextGen® Enterprise EHR upgrade. You can select options in Template Editor to do the following: Cache an individual template. Cache all templates or only templates with cache time stamps that are not current. The Template Cache Generator is used to process on-demand template caching. Parent topic: Template Caches See also Cache an Individual Template Cache Multiple Templates
NextGen® Enterprise EHR Template Editor Help 8
Template Server Cache Deployment
The following diagram depicts template caching using the Template Server Cache Path preference. Parent topic: Template Caches
