Release of June 2022 lh_concentration is optional,when date_received is equal or after 01 April 2021 and:
|
Release of November 2021 See details on the following page: |
Release September 2021: See details on the following page: What's new in Lab Results CSV/XML import files as of 28 September 2021? |
Release June 2021: New Target Compounds and Endogenous Reference Compounds are available in IRMS details tab for the Sample Received after 01 May 2021: Target Compounds with Specific Code between brackets:
Endogenous Reference Compound with Specific Code between brackets:
CF_unit[index] is removed from Presence of confounding factors. ERC2 is added(Optional). |
Release 04 May 2021: For samples that triggered an Atypical Passport Finding Confirmation request (ATPF-CPR) notification, it is mandatory to indicate whether the Testing Authority (TA) has approved the confirmation procedure or not when:
For confirmations requests that are not approved by the TA one of the following reasons must be provided:
|
Release 13 April 2021: New mandatory Confounding Factors added to the system with Specific Code between brackets:
|
For the latest files see the attached file.
Mandatory Fields |
|||
Field | Column header | Description | Update Lab Results |
Sample Code |
sample_code |
This is the identifying number on the sample collection kit. The sample code must be unique in combination with the sample type, the Lab name and the Date received by the Lab. Example: |
MANDATORY for Update . No update allowed. |
Sample Type | sample_type |
This specifies the type of sample analyzed. Possible values: "dried_blood_spot" |
MANDATORY No update allowed. |
Date Received by Lab | date_received |
This specifies the date that the sample was received by the laboratory (yyyy-MM-dd) Example: |
MANDATORY No update allowed |
Sample Collection Authority | sca |
Short name of the ADO organization in charge of the Sample Collection. For the codes see the download centre on our website. Example: |
|
Testing Authority | ta |
This field contains the short-name identifier of the Testing Agency, which is generally the laboratory's customer. This is a mandatory field for samples reported after January 1st 2015. (ADAMS Release 4.0) Example: |
|
Test Type | test_type |
This field is used to indicate whether the sample was collected in- or out-of-competition. Example: |
|
Sport | sport_code |
This field is used to report the sport of the athlete who contributed the sample. The WADA sport identifier code must be used in this field, not the sport's name. For the codes see the download centre on our website. |
|
Sport discipline | discipline_code |
This sport discipline's specific code. For the codes see the download centre on our website. |
|
Test result | test_result |
|
If an invalid Test result transition is proposed, then the record is rejected. |
Specific Gravity | specific_gravity |
On the UI this corresponds with the field Sample Specific Gravity (Initial Testing Procedure). value (eg. 1.025) with 3 digits after comma Example: |
|
Sample Specific Gravity (Confirmation Procedure) | sample_specific_gravity_cp |
Introduced in ADAMS Release 7 May 2019 A value indicating the Sample Specific Gravity (Confirmation Procedure) for Urine sample. value (eg. 1.025) with 3 digits after comma Min - Max: [1.001 - 1.050] For samples with a date_received that is equal to or later than 1 March 2019 AND with a Test result = AAF/ATF, it is mandatory to provide a value for the Sample Specific Gravity (Confirmation Procedure). This is for Urine A/B/B1/B2 samples. For Samples with date_received is equal to or later than 1 April 2021 , it is mandatory to provide a value when sample Type is Urine and sample A/B is B or B2. Example: |
|
Validity | valid |
urine sample validity. For samples with a date_received on or after 16 March 2016 the validity status is calculated automatically based on the provided microbial contamination markers (any values included in the column 'valid' will be disregarded). For samples with a date_received before 16 March 2016 the validity column remains mandatory. Example: |
|
Steroid profile variables (Code) | Steroid_profile_variable_code[index] |
Specific code of the steroid profile variable.This field is mandatory for results received after January 1st 2014 Current codes are: androsterone, epitestosterone, 5b-androstanediol, 5a-androstanediol, testosterone, etiocholanolone, T/E. |
SP variables can always be added (even if the result is 'locked'). The Specific Gravity is mandatory when an SP variable assumes a value. |
Steroid profile variables (Value) | Steroid_profile_variable_value[index] |
Decimal value or integer with 2 significant digits as per ADAMS settings for each variable. For samples with a received date after 1 Jan 2016, a value of '-2' will be allowed for Epitestosterone. Example: |
|
Confirmed specific gravity | confirmed_specific_gravity |
This field is mandatory for Urine samples with a date received after 1 Jan 2016 When the user is confirming the result, the Specific Gravity must be confirmed. This is mandatory. Example: |
|
Date of Sample Collection | sample_collection_date |
This field contains the sample collection date (yyyy-MM-dd) This field is mandatory for samples with a date received after 1 Jan 2016. Example: |
Mandatory No update allowed. |
Microbial contamination parameters, and confirmation |
ratio_5aand_a ratio_5band_etio ratio_freet_totalt ratio_5aand_a_confirmed ratio_5band_etio_confirmed |
These fields become effective for Urine samples (type 'A') with a date received after 16 March 2016. ratio_5aand_a and ratio_5band_etio refer to 5aAND/A or 5βAND/Etio and are both mandatory for the screening procedure. ratio_freet_totalt refers to "Free T/total T", which is not-mandatory. All are decimal values Similar for the confirmed values: ratio_5aand_a_confirmed, ratio_5band_etio_confirmed (ratio_freet_totalt doesn't require confirmation) For samples other than type 'A' the microbial contamination parameters details are optional. |
|
Suspicious SP confirmation request status |
confirmation_request_status samplea_inadequate_volume normal_athlete_profile valid_teratio_firsttest irms_method_unavailable other_reason |
These fields become effective as per 16 March 2016 and apply to Urine samples with a date received between 1 Jan 2016 and 1 April 2021. The confirmation request status is mandatory for a Suspicious Steroidal Passport under certain conditions. The selection options are boolean values (true/false) |
|
ATPF-CPR confirmation request status |
confirmation_request_status See_APMU_report TUE Multiple_AAFs Previous_samples_with_EtG_and_negative_IRMS_results APMU_Report_txt |
This fields become effective as per 4 May 2021 and apply to urine samples with date received after 1st April 2021. The confirmation request status is mandatory for a Atypical Passport Finding under certain conditions. Confirmation_Request status: The selection options are boolean values (true/false). |
|
Presence of confounding factors |
CF_code[index] CF_presence[index] CF_conc[index] CF_unit[index]
|
For Confounding factors:
"CF_conc” is mandatory when “CF_presence” is True. Example: |
|
Confirmation of the presence of confounding factors |
CF_presence_confirmed[index] CF_conc_confirmed[index] |
For Confounding factors:
“CF_conc_confirmed” is mandatory when “CF_presence_confirmed” is True. Example: |
|
IRMS Target Compounds |
TC_variable_code[index] TC_variable_d_value[index] TC_variable_u_value[index] |
These fields become effective as per 16 March 2016 and apply to Urine samples with a date received after 1 Jan 2016. TC_variable_code[index]: specific code of the IRMS Target_Compound variable. If Lab results are entered after the start date of the TD2016EAAS & TD2016IRMS Reporting in Jan 2016 AND the analysis_attribute = IRMS in the file, then at least one TC should be present in the Import file. Index should not have a limit. Current possible values with the specific code between brackets: testosterone (T), epitestosterone (E), androsterone (A), etiocholanolone (Etio), "5α-androstane-3α,17β-diol" (5aAdiol), "5β-androstane-3α,17β-diol" (5bAdiol), 19-NA (19-NA), formestane (formestane), boldenone (boldenone), boldenone metabolites (boldenonemet), other TC (other-TC). When Date_ Received is equal to or greater then 01-May-2021 then the new Target Compounds are available with Specific code between brackets :
TC_variable_d_value[index]: δ (0/00) decimal value or integer (as per ADAMS settings for each variable). Mandatory if a TC_code is included for the same index. TC_variable_u_value[index]: uc (0/00) decimal value or integer (as per ADAMS settings for each variable). Mandatory if a TC_code is included for the same index. |
|
Endogenous Reference Compounds |
ERC_variable_code ERC_variable_d_value ERC_variable_u_value ERC2_variable_code ERC2_variable_d_value ERC2_variable_u_value |
These fields become effective as per 16 March 2016 and apply to Urine samples with a date received after 1 Jan 2016. ERC_variable_code: specific code of the Endogenous Reference Compound variable for IRMS. Can only be present if the analysis_attribute = IRMS; If nothing is entered in IRMS details only, then the default is PD. Possible values:
A new Endogenous Reference Compounds with Specific Code between brackets is available when Date_ Received is equal or greater than 01-May-2021 :
ERC_variable_d_value: δ(0/00) decimal value or integer (as per ADAMS settings for the variable). Mandatory if the analysis_attribute = IRMS is included. If there is no ERC-code then it is assumed that it is for PD. ERC_variable_u_value: uc (0/00) decimal value or integer (as per ADAMS settings for the variable). Mandatory if the analysis_attribute = IRMS is included. If there is no ERC-code then it is assumed that it is for PD. ERC2_variable_code is optional. Example: |
|
Overall IRMS conclusion |
irms_conclusion |
This variable becomes effective as per release 4.7.0
This field is mandatory if analysis_attribute = IRMS and the date_received is after 1 Jan 2016 (TDEAAS date) and creation_date is after 16 March 2016 (IRMS-details tab launch date). |
|
Optional Fields |
|||
Field | Column header | Description | Update Lab Results |
Results Management Authority |
rma |
This field contains the short-name identifier of the Results Management Authority, which will follow up on the result with the Results Management. This is an optional field for samples reported after January 1st 2015. (ADAMS Release 4.0) Example: |
|
Sample A or B | sampleAB |
Allowable values: A, B, B1, B2 . If left blank, then sample A will be assumed. It is possible to specify the values "B1" and "B2" for samples reported after January 1st 2015. (ADAMS Release 4.0) Example: |
MANDATORY No update allowed |
Test Result reason | test_result_reason |
The reason substantiating the result selected. (This text will be added to the activity generated at creation) Example: |
|
Analysis Details / Explanation | analysis_details |
This field is used to provide any relevant information concerning the analyses performed by the laboratory or specific observations made. Example: |
Free text (in case of a partially submitted ATF, this text can also be updated when the record is 'locked') |
Dried Blood Spot analysis type details | DBS_analysis_type_details |
This field is used to provide any relevant information concerning the analyses performed by the laboratory or specific observations made. |
|
Lab Internal Reference Number | lin |
This field is used to record the internal sample code assigned to the sample upon receipt by the laboratory. Example: |
|
Mission Order Number | mo_number |
This field is used to record the mission order/ sample collection order number (if available). Example: |
|
Date of Analysis Report | analysis_report_date |
This field contains the date that the sample analysis results were reported to the TA. (yyyy-MM-dd) Example: |
|
Country (of Sample Collection) | country |
This field contains the country code of where the sample was collected. It can be provided in either 2-character ISO format or 3-character Olympic format. For the codes see the download centre on our website. Example: |
|
Region (of Sample Collection) | region |
This field contains an ISO code identifying the region within the country of sample collection. For the codes see the download centre on our website. Example: |
|
City (of Sample Collection) | city |
This field contains the city where the sample was collected. Example: |
|
Athlete Gender | gender |
This field specifies the gender of the athlete who provided the sample. Empty means 'X' Example: |
|
Screen T/E Ratio | te_ratio |
This field specifies the T/E ratio analyzed in the sample. Decimal value with max. 2 digits after the decimal point. Any extra digits will be discarded when saving the results (do not include any other modifier such as ":1"). Only for the import of results received before January 1st 2014. Example: |
|
pH | ph |
This field specifies the pH analyzed in the sample. Decimal value with max. 2 digits after the decimal point. Any extra digits will be discarded when saving the results. Example: |
|
Special type of analysis | analysis_attribute |
Default is blank. Multiple types are allowed but need to be separated by a '|'. For Urine: As of January 2016 the name will change for GHRF (GHRH/GHS/GHRP) [ code GH ] into GHRF (GHS/GHRP) [ internal code remains GH ] ; also we will add a new attribute GHRF (GHRH) [ internal code GHRH ] For Blood: Example: as of Jan 2016: GHRH "hGH|Other", "hGH Markers" "hGH|EPOb|hGH Markers" |
The new value overwrites the old value, even if the old value has multiple attributes. |
Send notification of results to | send_result_to |
This field specifies the short name of the organization(s) to be notified of the result. For the codes see the download centre on our website. Example: |
The new value overwrites the old value. Even if the old value has multiple organization names e.g. FINA|CCES and the new value is NADA, the entire FINA|CCES will be replaced by NADA. |
Name of the competition | competition_name |
In case the test_type is 'IC' (in-competition): free text Example: |
|
LH-Analysis |
lh_analysis lh_concentration lh_adj_concentration lh_lod |
or Urine samples A, B, B1, B2 it is optional to provide the LH-Analysis details: lh_analysis : value can be either Negative, PAAF, ATF or blank. Blank value implies that No LH-Analysis was performed. lh_adj_concentration: numeric value - positive integer or a decimal with 1 digit after decimal point. It is mandatory for sample A when date_received is equal or after 01 April 2021 and:
Example: "0.2" "1.9" "2" "0" "8" |
Applicable to Urine samples A, B, B1, B2. The new value in the file overwrites the old value in the database. It not available on the Lock Results. |
Prohibited substance |
prohibited_substance[index] |
The specific substance code has to be used. For the codes see the download centre on our website. The index is a number ranging from 1 to 10. A maximum number of 10 prohibited substance columns (and associated prohibited substance value and prohibited substance unit columns) may be included in a file. If a metabolite is included in the file the substance becomes mandatory. Example: |
The index is a number ranging from 1 to 10. If the record is not 'locked', the values from the file supersede the values in the database, otherwise any new substances will be added to the database. If a metabolite is included in the file, the substance becomes mandatory. |
Prohibited substance value |
prohibited_substance_value[index] |
The decimal value of the prohibited substance [index] Example: |
|
Prohibited substance unit |
prohibited_substance_unit[index] |
The specific code of the unit of measure for analysis related to the prohibited substance[index] Example: |
|
Prohibited substance details |
prohibited_substance_details[index] |
Free text for the details concerning finding. Example: |
In case of a partially submitted ATF, this text can also be updated when the record is 'locked'. |
Metabolite-only indicator |
prohibited_substance_metabolite_only[index] |
Indicator that signifies whether metabolite(s) only were detected. Default is 'N'. If 'Y' then the substance becomes mandatory. Example: |
|
Metabolite |
prohibited_substance_metabolite[index] |
Free text for the metabolite. The index is a number ranging from 1 to 10. A maximum number of 10 metabolite columns (and associated metabolite value and metabolite unit columns) may be included in a file. Example: |
If the record is not 'locked', the values from the file supersedes the values in the database, otherwise any new metabolites are added to the database. |
Prohibited substance unit |
prohibited_substance_metabolite_unit[index] |
The specific code of the unit of measure for analysis related to the metabolite[index]. Example: |
|
Prohibited substance value |
prohibited_substance_metabolite_value[index] |
The decimal value of the metabolite [index] Example: |
|
Prohibited substance- Estimated concentration of 19-NA (>, ≤) |
prohibited_substance_estconcentration [index] |
Effective when Date_Recieved is equal to or greater than 01-April-2021: Mandatory under the Prohibited Substance 19-norandrosterone. Possible values: (Specific codes):
|
|
Prohibited substance-Presence of THNE |
presence_THNE_compatible[index] Presence_THNE_incompatible[index] |
Effective when Date_Recieved is equal to or greater than 01-April-2021: Required under the Prohibited Substance 19-norandrosterone. When both THNE are empty or FALSE is selected for any of them then “No presence” is selected in the Lab Results. Values :TRUE, FALSE. blank |
|
Prohibited substance-GC/C/IRMS 19-NA 19-NE |
GC_C_IRMS_19NA_19NE[index] |
Effective when Date_Recieved is equal to or greater than 01-April-2021: Optional for Prohibited Substance 19-norandrosterone. Required when GC/C/IRMS 19-NA 19-N was performed. Value: TRUE , FALSE , blank |
|
Prohibited substance-19-NA/19-NE ratio
|
prohibited_substance_19NA_19NE_ratio [index] |
Effective when Date_Recieved is equal to or greater than 01-April-2021: Optional for Prohibited Substance 19-norandrosterone. Numeric positive value |
|
Prohibited substance-Target Compounds under 19-norandrosterone |
TC_substance[index] TC_substance_variable_code[Index] TC_substance_variable_d_value[Index] TC_substance_variable_u_value[Index] |
Effective when Date_Recieved is equal to or greater than 01-April-2021: Mandatory to select one Target Compound when GC/C/IRMS 19-NA 19-N is selected. TC_Substance code :
TC_substance_variable_code:
TC_substance_variable_d_value ,TC_substance_variable_u_value: Numeric values Example: TC_substance[1]=19-norandrosterone TC_substance_variable_code [1]=19-NA TC_substance_variable_d_value [1]= -27 TC_substance_variable_u_value [1]=0.06 TC_substance_variable_code [2]=19-NE TC_substance_variable_d_value [2]= -28 TC_substance_variable_u_value [2]=0.07 |
|
Prohibited substance-Endogenous Reference Compound under 19-norandrosterone |
ERC_substance_variable_code [Index] ERC_substance_variable_d_value [Index] ERC_substance_variable_u_value[Index] ERC2_substance_variable_code[Index] ERC2_substance_variable_d_value[Index] ERC2_substance_variable_u_value[Index] |
Mandatory to select ERC values when GC/C/IRMS 19-NA 19-N is selected. ERC_substance_variable_code: specific code of the Endogenous Reference Compound variable for IRMS. Possible values: Pregnanediol (PD), 5α-androst-16-en-3α-ol (16-en), 11β-hydroxyandrosterone (11-OHA), 11-ketoetiocholanolone (11-O-Etio), Androsterone (Androsterone), Pregnanetriol (PT)
ERC_substance_variable_d_value: δ(0/00) decimal value or integer (as per ADAMS settings for the variable). ERC_substance_variable_u_value: uc (0/00) decimal value or integer (as per ADAMS settings for the variable). ERC2_substance_variable_code is optional. ERC2_substance_variable_d_value is required when ERC2_substance_variable_code is entered. ERC2_substance_variable_u_value is required when ERC2_substance_variable_code is entered. Example: ERC_substance_variable_code [1]=16-en |
|
Prohibited substance-Specific comments |
consistent_exogenous_origin_19NA[index] inconclusive_exogenous_origin_19NA[index] consistent_endogenous_origin_19NA[index] found_in_the_sample_19NA[index] Found_Not_Compatible_19NA[index] not_consistent_norethisterone_19NA[index] not_consistent_with_pregnancy_19NA[index] other_19NA[index] |
Required when GC/C/IRMS 19-NA 19-N is selected for the Prohibited Substance. Value: True , False , Empty More than one specific comments is possible. |
|
Prohibited substance-ERA Analytical Method |
PS_PAGE_Analytical_MethodA[index] PS_PAGE_Analytical_MethodB[index] PS_PAGE_Analytical_MethodC[index] PS_PAGE_Analytical_MethodD[index] |
Apply to the following substances from 01 May 2021:
Specific Code of ERA Analytical Method for the prohibited substance [index] shall be reported.
Example: |
The new methods will be added to the existing methods. Cannot remove an existing method for the substance with the batch update.
|
Threshold substance –(Adjusted) DL |
prohibited_substance_DL[index] prohibited_substance_DL_unit[index] |
The (Adjusted) DL value for the prohibited substance for the sample Received after 01-April 2021. prohibited_substance_DL_unit[index] is mandatory when a value exist in prohibited_substance_DL[index]. Example: "IU/L" |
for an existing Substance No-Blank value is updated only when Lab Results is not locked.
|
Threshold substance – mean value |
prohibited_substance_mean[index] |
Decimal value of the Mean when a special threshold substance is concerned (max. 5 digits apart from the decimal point) Example: |
value is updated only when Lab Results is not locked. |
Threshold substance – mean unit |
prohibited_substance_mean_unit[index] |
Specific code of the unit of measure Example: |
value is updated only when Lab Results is not locked. |
Threshold substance – uncertainty |
prohibited_substance_uncertainty[index] |
Decimal value of the Uncertainty when a special threshold substance is concerned (max. 5 digits apart from the decimal point) Example: |
|
Threshold substance – uncertainty unit |
prohibited_substance_uncertainty_unit[index] |
Specific code of the unit of measure Example: |
|
Indicator Monitoring |
monitoring |
To indicate whether the sample was analysed for the Monitoring program or not. Possible values : 'y', 'n', or empty. Default is No. It is possible to indicate ‘y’(es) for monitoring while leaving the monitored_ substance data blank. If you however provide values for monitored_substance, then the ‘y’ should be on for ‘monitoring’ (‘n’ and empty are then not allowed). Example: |
|
Comments Monitored |
comments_monitored |
Comments to the monitored sample (per sample and not per substance) Example: |
|
Monitored substance |
monitored_substance[index] |
The specific substance code has to be used. For the codes see the download centre on our website. The index is a number ranging from 1 to 15. Example: |
|
Monitored substance value |
monitored_substance_value[index] |
The decimal value of the monitored substance [index] Example: |
|
Monitored substance unit |
monitored_substance_unit[index] |
The specific code of the unit of measure for analysis related to the monitored substance[index] Example: |
|
Confirmed value of the steroid profile variable with the same index |
steroid_profile_variable_confirmed[index] |
Confirmed valued for steroid profile variable |
|
Uncertainty of the steroid profile variable with the same index |
steroid_profile_variable_uc[index] |
If steroid_profile_variable_confirmed value is added then this value should be added. If steroid_profile_variable_confirmed[index] is -1 or -2 then steroid_profile_variable_uc[index] must be empty. |
|
Test method code |
test_method_code[index] |
This code has to be a valid code as has been pre-defined by the Lab-administrator. The index is a number ranging from 1 to 15. Example: |
|
Test method comments |
methods_comments |
A free text field to detail the test method codes utilized in the analysis and which will appear on the ADAMS test report. Example: |
|
Update Lab Results :
When an update record from the input file is successfully posted, the identified analytical result in ADAMS will be overwritten by the non-blank values of the update record in the file unless otherwise is specified in the table above (if blank in the input file, then the original value in the database remains).
After applying the modifications, the updated record will be automatically Saved in ADAMS in the same and unaltered Lab result status. So, if the status of the Lab result was Not Submitted, Submitted or Partially Submitted, then this status will stay (an Update on a Cancelled record is not possible).
The common notifications will be generated, as well as an Activity in the activities tab to capture and record the batch update. The update will also be logged in the Batch Summary tab. Upon completion of the update, the 'Last updated' details on top of the Lab results page will reflect the date/time of the update and the user (organization) who performed the batch update.
Updates proposed for an analytical result that has the Cancelled status in the database or is locked due to a match with an associated DCF in ADAMS, will not be accepted and the update record will be rejected. Note that when the analytical result record is locked, it remains possible to add new information to it (such as a new analysis type, new substance, metabolite etc ), yet not to alter existing information.
Template: