Difference between revisions of "Database merge fields"
Jump to navigation
Jump to search
(Created page with ''''Database merge fields''' are simply ways to pull in certain database fields directly into the text template. This is useful when you have a portion of a template that changes…') |
|||
| Line 7: | Line 7: | ||
If we setup the text template including the following merge fields: ~FName LName~ is a ~Age~ ~Sex~ who presents today for routine follow up. | If we setup the text template including the following merge fields: ~FName LName~ is a ~Age~ ~Sex~ who presents today for routine follow up. | ||
| − | When the template is called or appears in the Note the result will be: GALEN TEST is a 27 yo male who presents | + | When the template is called or appears in the Note the result will be: GALEN TEST is a 27 yo male who presents today for routine follow up. |
Latest revision as of 01:03, 18 March 2010
Database merge fields are simply ways to pull in certain database fields directly into the text template. This is useful when you have a portion of a template that changes with every patient or visit and cannot be account for with a static reference or reasonable multiple choice options. Fields such as name, age, sex, and encounter date are examples of available database merge fields.
Example:
Our patient's name is GALEN TEST and he was born in 1982.
If we setup the text template including the following merge fields: ~FName LName~ is a ~Age~ ~Sex~ who presents today for routine follow up.
When the template is called or appears in the Note the result will be: GALEN TEST is a 27 yo male who presents today for routine follow up.