Service Level Agreement
Effective Date: 1 October 2019
SERVICE LEVEL AGREEMENT
Data entered by the customer that accumulate during use of System will be stored on a server in ISO 270001 certified storage facilities by Siteground.
The Vendor does not inspect or analyze the data entered by the customer, and therefore the Vendor does not have any awareness about the contents, quantity, value or use of your data. Further, the Vendor can have no knowledge about the correctness, validity, completeness or legality of the entered data.
The Vendor does not influence, process or transform the data that are entered by the customer.
The customer’s data will be handled with full confidentiality.
Entered passwords are never stored in plain text, but in an obfuscated way, which means that not even the Vendor has knowledge about them.
The Vendor guarantees an up-time of System of 99.9% per month. Additional interruptions in the customer’s local internet connection are outside of the Vendor’s influence.
The Vendor takes best commercial precautions to secure customer’s data against data loss. The Vendor stores daily, weekly, monthly and yearly backups of customer’s data in one off-site location, to which the Vendor has direct access.
The Vendor cannot exclude the possibility of accidental, catastrophic server problems. In such an event, the Vendor will employ best commercial efforts to restore the latest full and available backup and System within the shortest time possible. However, this recovery time can take up to 72 hours and the client will be regularly informed about the progress of restoration.
To allow the Vendor to continuously improve the System, the customer agrees to notify the Vendor about any observed irregularities in the performance of the System in a timely manner.
The System is provided “as is” and “as available” without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the Vendor or the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software. Without limiting the generality of the foregoing, the Vendor does not present or warrant that: (a) customer’s use of System will meet the customer’s requirements and (b) customer’s use of System will be uninterrupted, timely, secure or free from error.
Help on the ANDI Norms Template Editor
On the results page, there is a button that allows exports of the data and the norms directly to an MS Word file. This file contains a draft of a test report that can be edited by you to get it into its final form. The ANDI team has developed this to save valuable time of error-prone copying, pasting, and deleting that is common practice among non-ANDI users.
The standard report format provided by ANDI Norms can be copied and adjusted while retaining full functionality. This is accomplished with templates. A template is ordinary text, such as "The T score was 37." But how do we get the correct value for this patient instead of 37? This is done by using special codes, in this case, we would write "The T score was {{T}}." So, we have double curly brackets. The {{T}} part will now by replaced by the actual T score for this patient. Other options are {{IQ}}, {{W}}, {{z}}, {{p}}, all of which echoing the headers of the results table. Also available are {{raw}} for the raw score on the test, {{perc}} for percentile, and several other test variables.
You need to do one more thing, namely to tell the system of which test you want the T-score to be shown, as there may be many in the results table. This is done by preceding each variable with the test code. For example, the code for the AVLT trials 1 tm 5 total score is: AVLT__total_1_to_5. So, the full coded sentence above would be "The T score was {{AVLT__total_1_to_5.T}}.", where we use the dot notation to glue the T to the varialbe, much like web addresses. Now, the system knows you the AVLT T score.
For more complex descriptions, several aspects of a test can be mentioned, such as
On the 'AVLT Total trial 1 to 5' ({{AVLT__total_1_to_5.description}}) the score is
{{AVLT__total_1_to_5.select T }} (T-score: {{AVLT__total_1_to_5.T}}).
One can avoid having to repeat the longish test code by using the #with construction, as follows:
{{#with AVLT__total_1_to_5}}
On the 'AVLT Total trial 1 to 5' ({{description}}) the score is
{{select T }} (T-score: {{T}}).{{/if}}
{{/with}
Now, everything between {{#with AVLT__total_1_to_5}} and {{/with}} will automatically
be interpreted as belong to the AVLT__total_1_to_5 test.
You may have noticed the {{select T}} construction. Here, select is a so called 'helper'. The select
helper selects an adjective from very low to very high according to well established standards based on the T score.
So, if T is 35, {{select T}} would be replaced by 'low'. Actually, the default language is Dutch, so it would say
'laag'. For English, write {{select_en T}} to get 'low'. You can also specify your own adjectives and even alter
the criteria for when to call something 'low', 'average', etc.
Another helper that is used a lot is {{round T}}. By default, T is a precise value with many decimals, which are usually unwanted in a report. By writing {{round T}}, we get a nice rounded value.
A common practice for a clinician is to have a long document with short sentences and paragraphs for each test, say for a hundred common tests. If a test battery contains only twelve tests, all not-used sentences are removed and only the relevant ones retained. In a template this is accomplished automatically by using the #if construction. We could, for example, write:
{{#if AVLT__total_1_to_5}}
On the 'AVLT Total trial 1 to 5', the T score is {{round AVLT__total_1_to_5.T}}).
{{/if}}
Now, this sentences would only be shown ('printed') if the AVLT__total_1_to_5 test was actually in the results
table. If not, it is simply ignored. So, if you write out a well-crafted paragraph for a test and put it between
and {{#if}} and an {{/if}}, it is only shown if the test was in fact used. This can also be done with a 'comment',
which is a clinical observation you can add in the extra columns in the Scores page. If you write
{{#if comment}}({{comment}}).{{/if}}, the text with comment will only be shown if there is in fact
a comment present. E.g., you write {{#if comment}}(learning curve: {{comment}}).{{/if}}, to show the
learning curve of the AVLT, but only for cases where you actually recorded it. If the cell in the column is blank
the whole bit would be ignored.
You can define an unlimited number of templates, e.g., in different languages like Dutch, English, Polish, etc. Notice, however that names and descriptions and other language-specific aspects are only available in Dutch and English. In the future, we are likely to expand the number of languages supported, if there is a demand for this.
There are many more possiblities than covered, which will be documented in a user manual (to be written). The template system used by ANDI Norms is based on the Handlebars template library, which includes excellent documentation.