There are several configuration options to allow ClinSpark to decide what is considered as the datapoint collection time. Click on each option to read more. For more details, please refer to the ClinSpark Timing Variables article.
The system will record the time of data collection for the Form, when the user hits the “Save” button. This is a very common scenario to record data collection time for Forms that do not have a specific datetime type of field, where user can specifically record the data collection time (as described in Scenario 2). Hitting the “Save” button will record the system date/time automatically. Users cannot modify this timestamp.
The time when the user hits the “Save” button is also known as Transaction Time.
When you are designing Forms for Timed Activity Plans, you may include a datetime type of field and enable the “Capture Time” setting, which will allow the user to record the time of when the data on the Form was collected.
When the datetime type field with “Capture Time” setting enabled exists within the Form, the system will use the value recorded in this field to report the data collection time. If there is more than one datetime field with “Capture Time” setting enabled in the same Form, then the earliest date/time will be used by the system as the data collection time.
If a datetime type field with “Capture Time” enabled does not exist within the Form, then the system will use the time the user hits “Save” button to record data collection time (Scenario 1).
For rare cases, where the data entry and/or save was delayed and no datetime type field is available within the Form, there is the Collection Time option.
This allows the user to use the Form Actions menu > Collection Time, to record the actual date and time when the data was collected and prevent the system from recording timing deviations/recalculations, when they did not happen.
When the “Collection Time” option is used, the system will report this manually entered date and time as the data collection time.
