User Tools
userzone:definitions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
userzone:definitions [2014/10/20 14:47] Matijs [Track fields] More about aboointment fields |
userzone:definitions [2020/03/12 12:06] (current) |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| The above values are default specified by HL7 and usually different for each specific medical area. Most projects do not use all these fields. | The above values are default specified by HL7 and usually different for each specific medical area. Most projects do not use all these fields. | ||
| - | ==== Appointment filters ==== | + | ==== Appointment filter ==== |
| - | Appointment filters are used to link appointments to specific appointment track fields by selecting these filters in the definition of the appointment track field. (You will only see them once the first filter has been defined in Setup => Agenda => Agenda filters.) | + | Appointment filter are used to link appointments to specific appointment track fields by selecting these filters in the definition of the appointment track field. (You will only see them once the first filter has been defined in Setup => Agenda => Agenda filters.) |
| There exist multiple types of appointment filters, e.g. filters on appointment activity and procedure and on appointment subject. Filters can be combined in AND and OR filters. Also it has been made easy to create new filters. | There exist multiple types of appointment filters, e.g. filters on appointment activity and procedure and on appointment subject. Filters can be combined in AND and OR filters. Also it has been made easy to create new filters. | ||
| Line 105: | Line 105: | ||
| ==== Track fields ==== | ==== Track fields ==== | ||
| - | A track can have one or more track fields that can contain data that explains the assignment of the track to the respondent. Example fields are a description, some date or a list of choices stating that a track is assigned to e.g. the right side of the respondents body or the left side. Track fields can have mandatory answers or can be optional. All the values entered for track fields are bundled together to form a track description, unless you define the field not to show this information. | + | A track can have one or more track fields that can contain data that explains the assignment of the track to the respondent. Example fields are a description, some date or a list of choices stating that a track is assigned to e.g. the right side of the respondents body or the left side. Track fields can be mandatory or optional and they can be read-only or editable. All the values entered for track fields are bundled together to form a track description, unless you define the field not to be added to the track description. |
| - | The most advanced type of track field is the **appointment field**. Appointments fields can be automatically filled using Appointment filters. You can even specify the field to automatically create a new track if an appointment matches the filter (and the patient does not have an existing unfinished track of that type.) | + | The most advanced type of track field is the **appointment field**. Appointments fields can be automatically filled using Appointment filters. You can even specify the field to automatically create a new track if an appointment matches the filter (and the patient does not have an existing unfinished track of that type). |
| - | Appointment fields can also be used to fill other fields, e.g. setting teh value of the location or attendant using the corresponding fields from the appointment. | + | Appointment fields can also be used to fill other fields, e.g. setting the value of the location or attendant using the corresponding fields from the appointment. |
| Projects can define their own track field types. | Projects can define their own track field types. | ||
userzone/definitions.1413809237.txt.gz · Last modified: 2020/03/12 12:08 (external edit)
