There are several tabs when creating a new service plan item, here is a summary of them.
|General||All the basic information required such as Name, Position, Category, Start/End Date, Active, and description.|
|Data collection||Configuration required for data collection. Depends on the type of data collection selected.|
|Chart||Configuration required for charts. Includes the Datasets and X/Y Axes details.|
|Objectives||List of objectives for this service plan item and its current progress and monitoring rules.|
|Baselines||List of all baselines collected for this service plan item.|
|Recommendations||All the recommendations given for this service plan item will later be passed on to the rest of the providers associated with the case.|
|Imported Data||Raw data is to be imported into the system. Useful when bringing data from another source other than the platform.|
The actual name of the element of the service plan.
Position of the element inside the service plan.
Category this service plan belongs to, useful if it needs to be changed.
The initial date associated with this element is useful to determine the first day data will be collected or displayed inside a document.
The last date associated with this element is useful to determine the last day data will be collected or displayed inside a document.
If this element is active or not. Useful also prevents the element to appear in other places.
Longer definition of the element, typically a full narrative description.
Data Collection Tab
We have implemented more than 15 data collection methods, please refer to the following table for more details.
|Event Recording||The number of occurrences by a unit of time. Ex: hour, day, week, interval.||Frequency, Count, Rate|
|Time Sampling||Collect data at periodic points in time or time periods rather than on a consistent basis.||Whole Interval, Partial Interval, Momentary Time Sampling|
|Timing||Length of time the behavior, or event occurred.||Duration, Response Latency, Interresponse Time|
|Trial||Several ways to easily record whether a response has been Correct, Incorrect, or there was no response to the test applied.||Discrete Trial Teaching, Incident Teaching, Percentage of Opportunities|
|Task analysis||Task analysis is used to break complex tasks into a sequence of smaller steps or actions.||Forward Chaining, Backward Chaining, Total Task Chaining, Backward Chaining with Leaps Ahead|
- Suggested number of recordings – Expected number of recordings for this element of the service plan. It is a suggestion, so they could go over this number.
- Daily Value – Value calculated for the day, possible choices are: Total or Average.
- Weekly Value – Value calculated for the week, possible choices are: Total or Average.
- Instructions – These instructions notes are given for the user collecting the data, this will be displayed in the datasheet.
- Unit of time – Determines the unit of time of the recording
- Interval Length – Used for interval base collection methods to determine the interval length (in the unit of time)
- Levels – If you would like to personalize the levels of data, you can do so by adding different Labels that will become the legend used.
List of all the datasets to be displayed in the chart.
|Baseline||Expected behavior of data, used for comparative purposes|
|Average||Average of values through a day, week, month, or year|
|Total||The total value of data during a day, week, month, or year|
|Rate||Occurrence of an event during a unit of time|
|Count||The total value of data collected|
|Session count||Count of sessions during a day, week, month, or year|
Other features available such as:
- Show multiple datasets at the set time on the same chart
- Customize X and Y axis (title, color, max value, min value, etc.)
- Customize each dataset (title, color, associated axis, type, etc.)
- Add tags, solid, dashed, and dotted lines
- Show the data in daily, weekly, monthly, or yearly intervals
This will set up and track the progress of this element based on the data available in the system. Each objective has a specific configuration that determines how the system will track the objective.
The name of the objective.
The start date from which this objective will be monitored.
The end date for this objective, after which the next objective in the list will be monitored.
This is the logical representation of the objective, you need to explain in mathematical terms how the objective will be monitored.
Valid End Dates
If all fields above are completed and there is data collected, the Valid End Date will list all dates considered to be valid. This is used to determine the End Date automatically.
This table will represent the data for each interval defined in the Smart Criteria, with different color codes to determine completion.
You can add all the baselines available by clicking “Add Baseline Button”.
The date associated with this baseline.
The value for this baseline.
The period this baseline represents, available options are Day and Week.
If you have existing data collected outside of Office Puzzle, you can import the data for each element in the service plan by simply converting your data to the format “DATE;VALUE”.
You can put the DATE value in any of the following formats:
- MM/DD/YYYY (Ex: 02/10/2023)
- YYYY-MM-DD (Ex: 2023-02-10)
- YYYY/MM/DD (Ex: 2023/02/10)
The value that will be associated with this DATE, this value is expected to be a NUMBER and shouldn’t contain any letters or sign. For example, if your value is 10% the input should be “10”.