Summary

A Visit Schedule is a configurable application specific feature used to define a study calendar with projected visit dates for each patient enrolled in a study. This feature can be used to easily identify any patients that are not adhering to a planned study calendar and assist with the scheduling of patient’s future visits. 

Table of Contents

• relative#
• relative#Name
• relative#Baseline
• relative#BaselineDelta
• relative#BaselineUnit
• relative#Baseline-
• relative#Baseline+
• dateCompletion
• Standard Configuration
• Dynamic Visit Configuration

Design | System

A study specific Visit Schedule can be configured by creating a series of incremental ‘relatives’ in the App Properties Worksheet which represent key values in a study schedule. Each relative can be configured to represent visits or specific data from an application. By creating date relationships between each defining relative an entire Visit Schedule can be created.

A relative property is identified in the Name column (column A) of the Properties Worksheet. Each identified relative is defined in the Value column (column B).

Each relative is assigned a sequential number. This number determines the order in which the relatives are displayed in a Visit Schedule. The sequential relative number is listed directly after the word relative in each property. There are multiple properties to each relative. The following represent the properties used to create a Visit Schedule:

relative#

Defines the absolute path to a data field in an application.

• This will draw the data populated in the field defined within the application

relative#Name

Defines the Display Text/Name of a relative.

• Each Relative Name must be unique within an application
• Every relative must have a Relative Name

relative#Baseline

Defines the primary point of orientation for a relative.

• This must be an absolute path to a date related field from the application

Note: At this time, partial dates are not supported within the Visit Schedule.

relative#BaselineDelta

Defines the incremental distance from the relative#Baseline.

• If the BaselineDelta is 0, the relative represents the Baseline

relative#BaselineUnit

Defines the unit of measure for the incremental distance defined as the BaselineDelta.

Options are

• DAY_OF_MONTH
• WEEK_OF_MONTH
• MONTH
• YEAR

relative#Baseline-

Defines the low end tolerance of a date window projection.

• A relative with a BaselineDelta of 25, a BaselineUnit of DAY_OF_MONTH and a Baseline- of 3 would allow for a visit of 22-25 days after the defined Baseline

relative#Baseline+

Defines the high end tolerance of a date window projection.

• A relative with a BaselineDelta of 25, a BaselineUnit of DAY_OF_MONTH and a Baseline+ of 3 would allow for a visit of 25-28 days after the defined Baseline

dateCompletion

Defines the trigger date for the patient’s exit from the study.

• This must be an absolute path to a date related field from the application
• If the dateCompletion is met the projections for visits after this date will not be calculated

Each relative must have a relative#Name. Any of the other properties can be added or removed based on the need to define the functionality of the Visit Schedule.

Standard Configuration

A standard Visit Schedule would have the following relatives with similar relative properties:

Dynamic Visit Configuration

A Visit Schedule with dynamic visits is possible and would be configured similar to the following. This example has a registration form where the initial surgery is provided and then the first of a set of dynamic visits begins 6 months later and there are follow-up visits of the same form type every 3 months from that point.

Need more help?

Please visit the Fountayn Contact Information page.