Skip to end of metadata
Go to start of metadata

ADAMS 4.7.0

 For IRMS performed on Urine samples: labs are able to indicate a dedicated Overall IRMS conclusion irrespective and independent from the overall Lab test result. 

ADAMS Release 4.1.1 - changes as of 16 March 2016

For samples reported as of 16 March 2016 the following becomes effective, if the date received of the sample is after 1 January 2016:

  • Urine lab results validity is calculated based on microbial contamination markers: these fields are mandatory if the date received is after 16 March 2016; Confirmation will be required
  • Labs will have to indicate whether the TA approved or not the suspicious confirmation procedure request: this information is mandatory under certain conditions  
  • Presence/Absence of Confounding factors, as per ITP: this information is mandatory
  • Confirmation of the presence of confounding factors: this information is mandatory
  • δ values of IRMS Target Compounds, and associated uc: at least one is mandatory
  • δ values of Endogenous Reference Compounds, and associated uc: one is mandatory (preferentially PDiol)
  • IRMS Comments: free text (optional)

Important rules for the Update:

  • if the initial value for a Confounding factor is set to "yes" , then for the Batch Update it will be enforced to provide a confirmed value
  • if the date_received of the sample is on or after 16 March , the GC/C/IRMS conclusion (column irms_consistent) no longer applies
  • if results with a date_received before 1 Jan 2016 are updated with new IRMS details (target compounds, endogenous reference compounds, confounding factors etc), the system will require complete relevant details

ADAMS 4.1 - the anticipated changes as of 1 January 2016:

The following will be effective as of the start date of the TD2016EAAS & TD2016IRMS Reporting in 2016.

  • Sample collection date is mandatory if the sample is received after the start date of the TD2016EAAS & TD2016IRMS Reporting in 2016

Click here for a sample CSV file for ADAMS v4.0

Each sample record in the CSV/XML file should contain at least the mandatory fields. Once the update is triggered for the sample record in the input file, ADAMS will look for the corresponding result record in the database, based on the unique identification of 5 fields: sample code, sample type, sample AB, Lab name, date received.

As a general rule, each time an update is proposed for a result record in the database, ADAMS will validate on mandatory fields and business rules as they are prevalent on the Lab results page. ADAMS will apply the validity-check on the resultant of the value in the database and the value in the input file.

Below are comments on updatable fields (for the CSV file the sequence of the columns is not relevant).

Field

Column header

Comments

Example(s)

Sample Code

sample_code
MANDATORY

No update allowed.
The sample code must be unique in combination with the sample type, sampleAB, the Lab name and the Date received by the Lab.

"1479265"

Sample Type

sample_type
MANDATORY

No update allowed.

"URINE"
"BLOOD"

Sample A or B

sampleAB
MANDATORY

No update allowed.  It is possible to have the values "B1" and "B2" for samples reported after January 1st 2015. (ADAMS Release 4.0)

"A"
"B", "B1", "B2"

Date Received by Lab

date_received
MANDATORY

No update allowed (yyyy-MM-dd)

"2012-01-12"
"2012-11-28"

Date of Sample Collection

sample_collection_date

There are business rules, such as date_received can not be earlier than sample_collection date etc.

This field is mandatory for samples with a date received after 1 Jan 2016

"2012-01-28"

Date results reported

analysis_report_date

There are business rules, such as analysis_report_date can not be earlier than sample_collection date etc.

"2012-04-13"

Analysis date

Analysis_date

There are business rules, such as analysis_date can not be earlier than sample_collection date etc.

"2012-04-13"

Analysis time

Analysis_time

 

"9:10"

Country

country

 

"US or "USA"

Region

region

 

"US-KY"

City

city

 

"Montreal"

lin

lin

 

"A127692"

Mission Order #

mo_number

 

"M-127698"

Screen T/E Ratio

te_ratio

 Only relevant for results received before January 1st 2014.

"2.4"

pH

ph

 

"5"

Specific gravity

specific_gravity

Becomes mandatory if a Steroid profile variable is entered. This field is mandatory for results received after January 1st 2014

"1.003"
"2.3612"

Validityvalid

urine sample validity. This field is mandatory for results received after January 1st 2014

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

"Yes" or "No"

Send notification of results to

send_result_to

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

"UCI"
"CCES"

Test Authority

ta

This is a mandatory field for samples reported after January 1st 2015. (ADAMS Release 4.0)

"ITTF"

Sample Collection Authority

sca

If the mandatory SCA is missing in the database and in the file, AND the status of the record is (partially) submitted, then an error is given.

"AIBA"

Results Management AuthorityrmaThis is an optional field for samples reported after January 1st 2015. (ADAMS Release 4.0) 

Test Type

test_type

 

"IC"
"OOC"

Name of the competition

competition_name

 

"2011 Worldcup"

Sport

sport_code

The combination of sport and discipline is validated.

"SK"
"AQ"

Sport discipline

discipline_code

One may indicate only the discipline in the file (sport in the database is taken)

"SK"
"AQ"

Athlete Gender

gender

 

"M", "F", "X"

Test result

test_result

If an invalid Test result transition is proposed, then the record is rejected.

"Negative"
"NotAnalyzed" "AAF" , "ATF"

Test Result reason

test_result_reason

 

"text"

Special type of analysis

analysis_attribute

The new value overwrites the old value, even if the old value has multiple attributes.

  • For Urine:

ESAs (incl. recombinant EPOs and analogues)   [internal code EPO]; GC/C/IRMS  [code IRMS] ; Insulins  [code Insulin] ; GHRF (GHRH/GHS/GHRP)  [code GH] see below; GnRH [code GnRH ] ; IGF-1 analogues (code IGF1]; Other (code Other]

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:

GH Isoforms  [code hGH] ; GH Biomarkers   [code hGH Markers] ; Blood Transfusions  [code Transfusion] ; HBOCS [code HBOCS] ; ESAs (incl. recombinant EPOs and analogues)  [code EPOb]; IGF-1 analogues [IGF1b] ; Insulins [code Insulinsb] ; Other  [code Other]

** ADAMS 3.5 ** in case a hGH or hGH Markers substance is included in the Update file or present in the database, then the resultant of the update makes it necessary to have the hGH or hGH Markers attribute included for the resultant Lab result as well

"EPO" , "hGH"
"GC/C/IRMS"
"Other", "hGH Markers"
"EPO|Other"

 

GC/C/IRMS conclusion

irms_consistent

When a value is specified, the analysis _attribute is the file should be 'IRMS'

This will no longer be effective when the new IRMS functionality will be implemented as of 16 March 2016.

"yes"
"no"

Analysis Details / Explanation

analysis_details

Free text (in case of a partially submitted ATF, this text can also be updated when the record is 'locked')

 

Prohibited substance

prohibited_substance[index]

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.

"danazol"

Prohibited substance value

prohibited_substance_value[index]

 

"2.3"

Prohibited substance unit

prohibited_substance_unit[index]

 

"IU/L"

Prohibited substance details

prohibited_substance_details[index]

Free text (in case of a partially submitted ATF, this text can also be updated when the record is 'locked')

"free text"

Metabolite-only indicator

prohibited_substance_metabolite_only[index]

 

"Y"
"N"

Metabolite

prohibited_substance_metabolite[index]

Free text for the metabolite. 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.

"text"

Prohibited substance value

prohibited_substance_metabolite_value[index]

 

"4.15"

Prohibited substance unit

prohibited_substance_metabolite_unit[index]

 

"IU/L"

Confirmed value of the steroid profile variable with the same indexsteroid_profile_variable_confirmed[index]Confirmed valued for steroid profile variable 
Uncertainty of the steroid profile variable with the same indexsteroid_profile_variable_uc[index]No - If steroid_profile_variable_confirmed value is added then this value should be added    -   Added Since V3.4 

Steroid profile variables

Steroid_profile_variable_code[index]

The index is from 1 to 6. This field is mandatory for results received after January 1st 2014

SP variables can always be added (even if the result is 'locked'). The Specific Gravity is mandatory when an SP variable assumes a value.

Current codes are: androsterone, epitestosterone, 5b-androstanediol, 5a-androstanediol, testosterone, etiocholanolone, T/E.

Steroid profile variables value

Steroid_profile_variable_value[index]

For samples with a received date after 1 Jan 2016, a value of '-2' will be allowed for Epitestosterone

"12"

Threshold substance – mean value

prohibited_substance_mean[index]

 

"2.1234"

Threshold substance – mean unit

prohibited_substance_mean_unit[index]

 

"IU/L"

Threshold substance – uncertainty

prohibited_substance_uncertainty[index]

 

"3.1234"

Threshold substance – uncertainty unit

prohibited_substance_uncertainty_unit[index]

 

"IU/L"

Indicator Monitoringmonitoring

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).

 "y", "n", ""
Comments Monitoredcomments_monitored "comments"
Monitored substancemonitored_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. 

 "caffeine"

Monitored substance value

monitored_substance_value[index]

 

"2.3"

Monitored substance unit

monitored_substance_unit[index]

 

"IU/L"

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)

 
Confirmed specific gravityconfirmed_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.

 
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 after 1 Jan 2016.

The confirmation request status is mandatory for a Suspicious Steroidal Passport under certain conditions.

The selection options are boolean values (true/false)

 
Presence of confounding factors

CF_code[index]

CF_presence[index]

CF_conc[index]

CF_unit[index]

These fields become effective as per 16 March 2016 and apply to Urine samples with a date received after 1 Jan 2016.

CF_code[index]: specific code of the Confounding Factor variable. Possible values: ‘ethylglucuronide’ for  ‘Ethyl Glucuronide’; ‘5areductase’ for ‘5a-reductase inhibitors’; ‘ketoconazole’ for ‘ketoconazole or similar’; ‘hCG’ for ‘Heterodimeric hCG’; ‘steroids’ for ‘Anabolic Steroids’; masking’ for ‘Masking Agents and diuretics’. The index number ranges from 1 to 6.

If Lab results are entered after the start date of the TD2016EAAS & TD2016IRMS Reporting in Jan 2016 AND the sample_type = Urine in the file, then ALL CF_codes for index 1 to 6 should be present in the Import file.

CF_presence[index]: Boolean with values True (yes-confounding factor is present) or False (no - confounding factor is not present). Mandatory for all indices from 1 to 6.

CF_conc[index]: decimal value for the estimated concentration of the confounding factor. This is currently only applicable to Ethyl Glucuronide’ : it is an optional field, yet the Lab should enter a value if concentration is above 5 ug/mL.

CF_unit[index]: unit for the estimated concentration of the confounding factor. This is currently only applicable to Ethyl Glucuronide’ , and defaults to ug/mL (optional field).

 
Confirmation of the presence of confounding factors

CF_presence_confirmed[index]

CF_conc_confirmed[index]

These fields become effective as per 16 March 2016 and apply to Urine samples with a date received after 1 Jan 2016.

The CF_code[index] will be used.

CF_presence_confirmed[index]: Boolean with values True (yes- Confirmed confounding factor is present) or False (no- Confirmed confounding factor is not present). It is mandatory for all CFs where CF-presence (initial value) = ‘True’ – the file should then contain a CF_code_confirmed = CF_code  AND a CF_presence_confirmed

CF_conc_confirmed[index]: decimal value for the Confirmed estimated concentration of the confounding factor. This is currently only applicable to Ethyl Glucuronide’. It is mandatory if for any index (CF_code_confirmed[index] = ‘ethylglucuronide’ AND CF_presence_confirmed[index] = ‘True’).

 
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).

TC_variable_d_value[index]: δ (0/00) decimal value or integer as per ADM2 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 ADM2 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

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, then the default is PD. Possible values: Pregnanediol (PD), 5α-androst-16-en-3α-ol (16-en), 11β-hydroxyandrosterone (11-OHA), 11-ketoetiocholanolone (11-O-Etio)

ERC_variable_d_value: δ(0/00) decimal value or integer as per ADM2 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 ADM2 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.

 
Comments for the IRMS reportingIRMS_comments

free text comments to the IRMS analysis for the sample (optional)

This field becomes effective as per 16 March 2016 and applies to Urine samples with a date received after 1 Jan 2016.

 
Overall IRMS conclusionirms_conclusion  This variable becomes effective as per release 4.7.0

The possible values:

  • Negative

  • AAF

  • ATF

  • ATF_technical

  • ATF_opinion

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).

 

 

 

 

  • No labels