Skip to end of metadata
Go to start of metadata

Click here for the latest XSD file: ADAMS v4.1.1
Click here for the latest sample XML: ADAMS v4.1.1

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.

Note on the ADAMS 4.1.1 release date change from 1 March to 16 March 2016

You may have prepared Import files before 16 March 2016 with Lab results containing the new information as stated in the next info bulletin below. When these Lab results are imported after 16 March, the system will not reject the new information: the new columns/tags and their values will be allowed if the date_received is before 16 March 2016 (and after 1 Jan 2016).

In general, updates made after 16 March 2016 on older Lab results will allow for providing the new information (depending on the date_received it will be optional or mandatory).

ADAMS Release 4.1.1 - the 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
  • 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)

*******NEW  An  XSD-schema  is available (also in PDF), and a sample XML-file  *******NEW: containing confirmed values for Microbial contamination markers

Important rules for the Import:

  • if the date_received of the sample is on or after 16 March, the microbial confirmation markers are required (not needed if before 16 March)
  • if a Confirmed value is provided in the XML file for one of the relevant entities to be confirmed (Steroid Profile variable (at least one), confirmed specific gravity, confounding factor, microbial contamination), then the values should be provided for all entities
  • if the initial value for a Confounding factor is set to "yes" , then no confirmed value will be enforced for the Import (unless the previous bullet point applies); for the Batch Update however it will be enforced
  • if the date_received of the sample is on or after 16 March , the GC/C/IRMS conclusion (analysisAttributes consistent) no longer applies 


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

The following will be effective as of the start date of the TD2016EAAS & TD2016IRMS Reporting in 2016, which is set to 1 January 2016.

The existing field Sample collection date is mandatory if the date received of the Urine/Blood sample is after 1 January 2016

Additional field in CSV/XML: Confirmed specific gravity is mandatory for the SP confirmation procedure if the date received of the sample is after 1 January 2016

Allowing the value '-2' for the steroid variable epitestosterone, if the date received of the sample is after 1 January 2016

1 January 2016: Analysis attribute for Urine

As of 1 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 ]

 

BATCH HEADER INFORMATION
Each file must contain one batch header containing the following information:

Data Element

Description

File Creation Date

An ISO representation of the date that the data file was created by the laboratory (e.g. 2005-02-15). This date will be stored in ADAMS as the result posting date.

Transmission Source Name

The name of the organization, department, or possibly individual that is the source of the data transmission. This field is optional, but if provided, it will be stored in the "Observations and Details" area of the result record.

Batch ID or Number

An internal lab number to identify the batch of results contained within the transmission. This identifier will be stored with each result record in ADAMS.

Lab

An identification code indicating the Lab name that is to send the result records.

Testing Type

A code indicating whether the samples were collected in-competition ("IC") or out-of-competition ("OOC"). This tag is mandatory for the Import operation, whereas it is optional for the Update operation. If mentioned in the header, the suggested value will apply to all results in the body.

Comments

If desired, comments can be provided. This field is not mandatory.



SAMPLE DETAIL RECORDS
One sample detail record, containing the following information, must be provided for each sample analyzed:
* Identifies mandatory fields

Data Element

Description

Sample Code*

The unique sample code (e.g. test kit identifier). This will be used to match the result record to the test record.

Lab ID Number (LIN)

An internal number or code assigned to each sample by the lab. This field is not mandatory, but will be stored in ADAMS if provided.

Sample Type*

A code used to identify the type of sample provided (e.g. Blood, Urine)...

Sample A/B*

Code to indicate whether the result record relates to the analysis of the "A", the "B", "B1" or "B2"   Sample.  It is possible to specify the values "B1" and "B2" for samples reported after January 1st 2015. (ADAMS Release 4.0)

Date Sample Collected*

The sample collection date as recorded on the doping control form. (e.g. 2005-02-12)

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

Date Sample Received by Lab*

The date that the lab received the sample (e.g. 2005-02-12)

Gender of Athlete*

A code (M, F, or X) indicating the gender of the athlete as provided on the doping control form. This field is not mandatory.

Sport & Discipline*

The sport and discipline in which the athlete competes (e.g. AQ ). ADAMS will record the lab entry even though it may not exactly match the sport and discipline recorded on the sample collection order.

Event

The name of the event (e.g. Men's 100m finals) in which the athlete was competing, as provided on the doping control form.

Sample Collection Authority*

A code indicating the short name of the Sample Collection Authority.

Country of Sample Collection

A code indicating the country in which the sample was collected.

Region of Sample Collection

A code indicating the region in which the sample was collected.

City of Sample Collection

The city where the sample was collected. This is not a mandatory field but may be used to verify a match if provided.

Testing Authority*

A code indicating the short name of the Testing Authority.This is a mandatory field for samples reported after January 1st 2015. (ADAMS Release 4.0)

Results Management AuthorityA code indicating the short name of the Results Management Authority. This is an optional field for samples reported after January 1st 2015. (ADAMS Release 4.0)

Example:

<rma>    <shortName>CCES</shortName>          </rma> 

Mission order number

Optional

Competition name

If applicable, the name of a competition

Validity*urine sample validity - tag: valid with the values "true" or "false". 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 tag 'validity' will be disregarded). For samples with a date_received before 16 March 2016 the validity column remains mandatory

Screen T/E Ratio

A number indicating the T/E ratio of the sample. For example, 2.6 would indicate a T/E ratio of 2.6:1. This field must only be used for samples received prior to January 1st 2014, it is not a mandatory field.

pH

A value indicating the pH of the sample. This is not a mandatory field; if it is not provided, the implication will be that the pH of the sample is within acceptable limits.

Specific Gravity*

A value indicating the S.G. of the sample. This is a mandatory field for samples received after January 1st 2014.

Test Result*

A code indicating the test result following the sample analysis ("Negative", AAF, ATF, "NotAnalyzed").

Test Result Reason

This is not a mandatory field.

Date results reported

Date of reporting the results. This is not a mandatory field.

Analysis Type(s) Performed

A list of analysis types that were performed on the sample. E.g. "EPO", "GC/C/IRMS", "Transfusion", "HBOCS", "hGH", and "Other". Not mandatory.
For "GC/C/IRMS" a conclusion can be provided (consistent or not).This conclusion is no longer effective for samples with a date_received on or after 16 March 2016. 

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]; 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]

Details

A free-text description (Analysis details/Explanation/ Opinion) of any relevant observations or analyses performed on the sample (e.g. sample tampering or received in poor condition, sample decomposition detected, unusual odor or color detected, etc.). This field is not mandatory. Please note that any departure from the International Standard for Laboratories must be reported to the Testing Authority outside of ADAMS, especially if the sample result is an adverse analytical finding.

Send notification of results to

A code indicating the short name of the organization the results have to be sent to. Multiple organizations are possible.

Steroid profile variable*

A code and value indicating the name of the variable and the corresponding value. This field is mandatory for samples received as of January 1st 2014.
Current codes are: androsterone, epitestosterone, 5b-androstanediol, 5a-androstanediol, testosterone, etiocholanolone, T/E.

Prohibited substance

The code, value and unit of the prohibited substance.

Metabolite only

A flag indicating whether merely metabolite(s) are involved

Mean concentration/ standard uncertainty

If a Threshold substance is concerned, the Mean/ Uncertainty values and units can be indicated

Indicator MonitoringTo indicate whether the sample was analysed for the Monitoring programme. Tag: monitoring with possible values 'true' or 'false'
Comments monitoredComments on the monitored sample. Tag: commentsMonitored
Monitored substance details
 
Test method details

 

The comments are free text, whereas the 'code' is an ISO code as has been pre-defined by the Lab administrator.

Microbial contamination parameters*, and confirmation

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", and is not-mandatory.

All are decimal values

Similar for the confirmed values:

ratio_5aand_a_confirmed  and ratio_5band_etio_confirmed (ratio_freet_totalt doesn't require confirmation)


For samples other than type 'A' the microbial contamination parameters details are optional.

Confirmed specific gravity*

This field is mandatory for 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*

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 for "approvedbyTA" or "notApprovedBy TA":

Presence of confounding factors*

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


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

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 Confounding factors should be present in the Import file.

An exception:  If the gender in a Urine Lab result is Female or X (non-Male), the confounding factor hCG should not be mandatory for A, B, B1 and B2 samples. This holds for both the Initial and Confirmed value. If the hCG initial = yes for the Female athlete, there is no need to provide a confirmed value.

Presence: Boolean with values True (yes-confounding factor is present) or False (no - confounding factor is not present). Mandatory for all confounding factors.

Decimal value for the estimated concentration of the confounding factor Ethyl Glucuronide’. Optional, yet the Lab should enter a value if concentration is above 5 ug/mL.

 

Confirmation of the presence of confounding factors*

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

Specific code of the Confirmed Confounding Factor variable. It is mandatory for all CFs where CF-presence (initial value) = ‘True’ – the Lab result should eventually contain a CF_code_confirmed = CF_code

Presenceconfirmed: 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

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

 

IRMS Target Compounds*

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

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

<value>: δ (0/00) decimal value or integer as per ADM2 settings for each variable. Mandatory if a TC_code is included for the same code.

<uc>: uc (0/00) decimal value or integer as per ADM2 settings for each variable. Mandatory if a TC_code is included for the same code.


Endogenous Reference Compounds*

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

<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. Only one ERC to be entered per result. Possible values: Pregnanediol (PD), 5α-androst-16-en-3α-ol (16-en), 11β-hydroxyandrosterone (11-OHA), 11-ketoetiocholanolone (11-O-Etio), Androsterone (Androsterone)

<value>: δ(0/00) decimal value or integer as per ADM2 settings for the variable. Mandatory if the analysis_attribute = IRMS is included.

<uc>: uc (0/00) decimal value or integer as per ADM2 settings for the variable. Mandatory if the analysis_attribute = IRMS is included.

 
Overall IRMS conclusion*

This variable becomes effective as per release 4.7.0

Tag irmsConclusion with 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).

 

Comments for the IRMS reporting

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

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

 

 

 

  • No labels