Acceptable Use Policy
Effective Date: 1 October 2019
ACCEPTABLE USE POLICY
- Unacceptable Use. Vendor requires that all customers and other users of Vendor’s cloud-based service (the “Service”) conduct themselves with respect for others. In particular, observe the following rules in your use of the Service:
- Abusive Behavior: Do not harass, threaten, or defame any person or entity. Do not contact any person who has requested no further contact. Do not use ethnic or religious slurs against any person or group.
- Privacy: Do not violate the privacy rights of any person. Do not collect or disclose any personal address, social security number, or other personally identifiable information without each holder’s written permission. Do not cooperate in or facilitate identity theft.
- Intellectual Property: Do not infringe upon the copyrights, trademarks, trade secrets, or other intellectual property rights of any person or entity. Do not reproduce, publish, or disseminate software, audio recordings, video recordings, photographs, articles, or other works of authorship without the written permission of the copyright holder.
- Hacking, Viruses, & Network Attacks: Do not access any computer or communications system without authorization, including the computers used to provide the Service. Do not attempt to penetrate or disable any security system. Do not intentionally distribute a computer virus, launch a denial of service attack, or in any other way attempt to interfere with the functioning of any computer, communications system, or website. Do not attempt to access or otherwise interfere with the accounts of other users of the Service.
- Spam: Do not send bulk unsolicited e-mails (“Spam”) or sell or market any product or service advertised by or connected with Spam. Do not facilitate or cooperate in the dissemination of Spam in any way. Do not violate the CAN-Spam Act of 2003.
- Fraud: Do not issue fraudulent offers to sell or buy products, services, or investments. Do not mislead anyone about the details or nature of a commercial transaction. Do not commit fraud in any other way.
- Violations of Law: Do not violate any law.
- Consequences of Violation. Violation of this Acceptable Use Policy (this “AUP”) may lead to suspension or termination of the user’s account or legal action. In addition, the user may be required to pay for the costs of investigation and remedial action related to AUP violations. Vendor reserves the right to take any other remedial action it sees fit.
- Reporting Unacceptable Use. Vendor requests that anyone with information about a violation of this AUP report it via e-mail to the following address: finance@andinorms.nl. Please provide the date and time (with time zone) of the violation and any identifying information regarding the violator, including e-mail or IP (Internet Protocol) address if available, as well as details of the violation.
- Revision of AUP. Vendor may change this AUP at any time by posting a new version on this page and sending the user written notice thereof. The new version will become effective on the date of such notice.
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.