The <code>EndpointStudyRecord</code> is used for modelling Endpoints in the flexible model such as containers for 'all endpoint study records', 'all endpoints' or even further <code>EndpointStudyRecord</code> entries. Basically everything that is an entry on the 'hierarchical chapter tree' is represented by a <code>EndpointStudyRecord</code>. <p/>The <code>EndpointStudyRecord</code> can be direct parent for <code>Element</code> objects. The latter are already flexible data objects yet provide no addressing capabilities. Modification tracking of this object - any trackable document needs such a record since the queryLastModified() and similar methods require this structure to be present. An optional modification comment. The party performing the modification. The modification date. This structure defines properies on ownership, authentication of the original author, and authorized uses of the current document. If a document originally was filtered during export and thus the data contained within the document is only a subset of the overall, this flag should be set to true. It can be used during import to advise the user if he can safely import the document or should rather take a closer look inside since otherwise data may effectively be lost! Usually no document is sealed and thus can be modified at any time by virtually anybody allowed by the access control. However, there is one big exception: IUCLID5 Agency and management of Dossier documents. Once dossiers have been created, the dossier itself and anything referenced from within is not modifyable anymore - therefore, it can be sealed. Flag that allows or prevents the current document to be copied and pasted. A user-specified name for the endpoint study record. This name is not to be confused with the so called 'default endpoint names' for REACH-IT. It is just a simple name where the user (or later some system automatism) can store text which is displayed in the section tree, the reference tracker, the import/export module, etc. This is the alphanumeric description field which is displayed on screen as indicator where the document reference points to. Usually this field has to be set when the document reference is created and should carry some clear indication where it points to such as the company name, the substance name, etc. This is a free-text field for user convenience to attach additional text to a DocumentReference. Last modification date of the target document. This field is not member of the primary key. Only at dossier creation time, the content of the field is encoded into timeStamp thus virtually creating a snapshot copy of the original object. Type of the target document, required for reference resolving. Unique identifier of the target document Note: primary key composition. Yet this does not belong to the primary key of the current class since there may be any number of DocumentReference objects pointing to the same document effectively. This is the alphanumeric description field which is displayed on screen as indicator where the document reference points to. Usually this field has to be set when the document reference is created and should carry some clear indication where it points to such as the company name, the substance name, etc. This is a free-text field for user convenience to attach additional text to a DocumentReference. The endpoint kind of the endpoint this reference points to. This field is not reliable, it may be null although the referenced document carries an 'endpoint kind' of course. Yet not all code might be changed to properly support this. Also, IUC-468 (sorting) assumes that the 'endpointKind' of the referenced FlexibleEndpoint will never change. Last modification date of the target document. This field is not member of the primary key. Only at dossier creation time, the content of the field is encoded into timeStamp thus virtually creating a snapshot copy of the original object. Type of the target document, required for reference resolving. Unique identifier of the target document Note: primary key composition. Yet this does not belong to the primary key of the current class since there may be any number of DocumentReference objects pointing to the same document effectively. The target type for the referenced flexible element. the level of data protection == confidentiality intended for the associated data / entities A free-text justification on the current confidentiality setting (see member confidentiality) Pick list <b>N78 </b> <p/>The regulatory purpose which applies: <ul> <li>Canada: Existing Substances Program under CEPA</li> <li>Canada: Pest Control Products Act (PCPA)</li> <li>EU: Biocides Programme</li> <li>EU: Existing Chemicals Programme</li> <li>EU: New Chemicals Programme</li> <li>EU: Registration, Evaluation and Authorisation of Chemicals (REACH)</li> <li>Japan: Chemical Substances Control Law</li> <li>OECD: HPV Chemicals Programme</li> <li>US: EPA HPV Chemical Challenge Programme</li> <li>US: Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA)</li> <li>US: Toxic Substances Control Act</li> <li>[other]</li> </ul> the purpose flag the data waiving the justification for the data waiving the study result type the study period the reliablility the rational reliablility [Path: PC_FLAMM.GEN_DATA_SOURCE_HD] [Path: PC_FLAMM.REFERENCE] Indicate the bibliographic reference of the study report or publication the study summary is based on. Always enter the primary reference in the first block of fields (i.e. Sort no. = 1), if there are more than one reference to be cited. Copy this block of fields for specifying any other references related to this record (e.g. report of a preliminary study or other documentation). If results of a study report have been published, indicate the full citation of that publication(s) in addition to the reference of the original study. [Path: PC_FLAMM.REFERENCE.REFERENCE_TYPE] Indicate the type of reference, e.g. "Study report" or "Publication". Select "Other company data" to characterise any unpublished information from a company other than a study report. Select "Grey literature" for any other unpublished information or "other:" and specify. [Path: PC_FLAMM.REFERENCE.REFERENCE_TYPE_TXT] [Path: PC_FLAMM.REFERENCE.REFERENCE_AUTHOR] For ease of sorting and searchability use following convention: Surname, Initial (Example 1: White D, Ruehl KJ, Borman SA & Little J. Example 2: Hartley M & Murray W (avoid unnecessary full-stops, commas)). If no individuals are cited as authors, enter name of company or organisation or "Anon." as appropriate.Note that the complete bibliographic reference may appear in this field after migration of unstructured data from existing databases. [Path: PC_FLAMM.REFERENCE.REFERENCE_YEAR] Enter year of study report or publication. For a study report this field should be completed to include it in any searches, regardless of whether the complete date is given in field "Report date". [Path: PC_FLAMM.REFERENCE.REFERENCE_TITLE] Include the title of the report. For publications, include the title of the article of a journal or article/chapter of a book (e.g. handbook). [Path: PC_FLAMM.REFERENCE.REFERENCE_SOURCE] Not relevant for any study report. For publications or any other literature source (grey literature) specify the following type of information: (i) Title of scientific journal or book (e.g. if handbook); (ii) Volume of journal; (iii) Editor, publisher, place of publication for books or articles in books; (iv) Pagination.Example 1 (journal): J. Agric. Food Chem. 38: 215-227Example 2 (handbook): In: Lyman WJ (ed.) Handbook of chemical property estimation methods. Environmental behavior of organic compounds. McGraw-Hill Book Company 15.1-15.34, New York. [Path: PC_FLAMM.REFERENCE.REFERENCE_TESTLAB] Either manually enter the name of the testing laboratory or select it from the picklist. In either case, editing is possible. [Path: PC_FLAMM.REFERENCE.REFERENCE_REPORT_NO] Specify the report number allocated by the testing laboratory. Note that any company-specific study number should be included in the respective field. [Path: PC_FLAMM.REFERENCE.REFERENCE_COMPANY_ID] Either manually enter the identity of the company who owns the data or select it from the picklist. In either case, editing is possible. [Path: PC_FLAMM.REFERENCE.REFERENCE_COMPANY_STUDY_NO] Specify any company study no. if there is such a number and if it is different from the report no. of the testing laboratory. Otherwise leave field empty. [Path: PC_FLAMM.REFERENCE.REFERENCE_REPORT_DATE] Specify the complete date of the study report, e.g. "2005-05-12" for 12 May 2005. Note that subfield "Year" should be completed in any case for sorting and searching purposes. [Path: PC_FLAMM.DATA_ACCESS] Select appropriate indication for data access. Enter "Not applicable" if the summary consists of information that is commonly accessible such as guidance on safe use. [Path: PC_FLAMM.DATA_ACCESS.LIST_POP] [Path: PC_FLAMM.DATA_ACCESS.LIST_POP_TXT] [Path: PC_FLAMM.DATA_PROT_CLAIM] Indicate as appropriate. Note: "yes" should be selected only if "Data submitter is data owner" or "Data submitter has Letter of Access". Options "yes, but willing to share" or "yes, but not willing to share" may be relevant for specific regulatory programmes where the submitter is requested to indicate whether he is willing to share studies (e.g. with vertebrates).In the supplementary remarks field, include an explanation as appropriate, i.e. justification for denial of sharing the corresponding study or refer to a document attached that provides justification (e.g. "for justification see attached document X") [Path: PC_FLAMM.DATA_PROT_CLAIM.LIST_POP_FIX] [Path: PC_FLAMM.DATA_PROT_CLAIM.LIST_POP_FIX_TXT] [Path: PC_FLAMM.CROSSREF_SAMESTUDY] A cross-reference can be included to indicate that the same study is recorded in another record. Indicate the respective chapter and record ID and enter relevant explanatory text. This may be useful if specific endpoints of a given study are described in another chapter (e.g. results on reproduction toxicity in case of a combined repeated dose / reproduction toxicity study) or if more than one experiment is described by the same study report, but included in separate records.Check with the relevant guidance document whether all the methodology details must be repeated or whether a cross-reference to the same study in another chapter may suffice.Note that any such cross-reference may become useless if a record is either printed or exchanged on its own. [Path: PC_FLAMM.CROSSREF_SAMESTUDY.TEXT_BELOW] [Path: PC_FLAMM.GEN_MAT_ME_HD] [Path: PC_FLAMM.GUIDELINE] Indicate according to which test guideline the study was conducted. If no test guideline was explicitly followed, but the methodology used is equivalent or similar to a specific guideline, you can indicate so in the "Qualifier" subfield preceding the field "Guideline".Copy this block of fields for specifying more than one guideline (e.g. US EPA in addition to OECD guideline). [Path: PC_FLAMM.GUIDELINE.QUALIFIER] Select appropriate qualifier, i.e.- "according to" (if a given test guideline was followed);- "equivalent or similar to" (if no test guideline was explicitly followed, but the methodology is equivalent or similar to a specific guideline);- "no guideline followed" (if none of above qualifiers apply. If so, fill in field "Principles of method if other than guideline");- "no guideline available" (if so, fill in field "Principles of method if other than guideline").- "no guideline required" (if so, fill in field "Principles of method if other than guideline"). [Path: PC_FLAMM.GUIDELINE.GUIDELINE] Select the applicable test guideline, e.g. "OECD Guideline xxx". If the test guideline used is not listed, choose "other guideline:" and specify the test guideline in the related text field.In this text field, you can also enter any remarks as applicable, particularly:- To include any other title of the test guideline draft used, a subtitle, another version or update number and the year of update (For instance, different titles and/or numbers may exist for a given EU test guideline.);- To indicate if a the study was performed prior to the adoption of the test guideline specified;- To indicate if the methodology used was based on an extension of the test guideline specified. [Path: PC_FLAMM.GUIDELINE.GUIDELINE_TXT] [Path: PC_FLAMM.GUIDELINE.DEVIATION] For robust study summaries or as requested by the regulatory programme, indicate if there are any deviations from the test guideline specified. If "yes" is selected, only briefly state relevant deviations in the supplementary remarks field (e.g. "other species used"); details should be described in the respective fields of the section MATERIALS AND METHODS. [Path: PC_FLAMM.GUIDELINE.DEVIATION_TXT] [Path: PC_FLAMM.METHOD_NOGUIDELINE] If no guideline was followed, include a description of the principles of the test protocol or estimated method used in the study. Details should be entered in appropriate distinct fields of section MATERIALS AND METHODS if available. Also provide a justification for using this method if appropriate.If an estimation method was used (to be indicated in field "Study result type") state the equation(s) and/or computer software or other methods applied to calculate the value(s). [Path: PC_FLAMM.METHOD_NOGUIDELINE.TEXTAREA_BELOW] [Path: PC_FLAMM.GLP_COMPLIANCE_STATEMENT] Indicate whether the study was conducted following Good Laboratory Practice or not. Select "yes (incl. certificate)" if a GLP certificate of a test facility is available. Select "yes" if a GLP compliance statement is available, but no information on a GLP certificate. You can give an explanation in the supplementary remarks field, e.g. for explaining why GLP was not complied with or for specifying which (national) GLP was followed. [Path: PC_FLAMM.GLP_COMPLIANCE_STATEMENT.LIST_SEL_FIX] [Path: PC_FLAMM.GLP_COMPLIANCE_STATEMENT.LIST_SEL_FIX_TXT] [Path: PC_FLAMM.TESTMAT_HD] [Path: PC_FLAMM.TESTMAT_INDICATOR] Select "yes" or "no" from the drop-down list for indicating that the identity of the test material is the same or is not the same, respectively, as for substance defined in section 1 (General information). In addition, the identity of the test material should be specified in the subsequent block of fields "Test material identity".NOTE: You cannot update this field, if a completed record is copied to another submission substance as reference. Therefore, in case of read-across the indication of "yes" is not relevant. [Path: PC_FLAMM.TESTMAT_INDICATOR.LIST_BELOW_SEL] [Path: PC_FLAMM.TESTMAT] Indicate the identity of the test material for one or more appropriate identifiers, e.g. CAS number, CAS name, IUPAC name. Copy this block of fields as appropriate.NOTE: In order to avoid confusion on the test material identity it is highly recommended to enter at least one substance identifier, regardless of what has been enterd in field "Identity of test material same as for substance defined in section 1 (if not read-across)". [Path: PC_FLAMM.TESTMAT.IDENTIFIER] Select an appropriate identifier from drop-down list, e.g. "CAS number". Use "Other:" and specify, if identity according to a standard identifier is not known or if an additional chemical name or number is provided. [Path: PC_FLAMM.TESTMAT.IDENTIFIER_TXT] [Path: PC_FLAMM.TESTMAT.ID] Select the corresponding substance identity from drop-down list or enter manually if the identity is not available from the list or if no list is provided for the type of identifier selected. [Path: PC_FLAMM.TESTMAT_FORM] Select the test material form from the drop-down list. If the form of the test chemical is not available in the list, select 'other:' and specify in the adjacent field. If the test material form is unknown, select 'no data'. [Path: PC_FLAMM.TESTMAT_FORM.TESTMAT_FORM] [Path: PC_FLAMM.TESTMAT_FORM.TESTMAT_FORM_TXT] [Path: PC_FLAMM.TESTMAT_DETAILS] Use freetext template and delete/add elements as appropriate. Enter any details that could be relevant for evaluating this study summary or that are requested by the respective regulatory programme. Consult the programme-specific guidance (e.g. OECD HPVC, Pesticides NAFTA or EU REACH) thereof.Note that any information that can be claimed confidential should be included in the subsequent field "Confidential details on test material".Explanations:- Name of test material (as cited in study report): only if different from any other identifiers provided in the preceding fields.- Molecular formula (if other than submission substance): specify- Molecular weight (if other than submission substance): specify- Smiles notation (if other than submission substance): provide if available- InChl (if other than submission substance): provide if available- Structural formula attached as image file (if other than submission substance): see Fig.: only if different from submission substance. Indicate Fig. no. if a file is attached in field "Attached document", e.g. state "see Fig. 1".- Substance type: indicate whether pure active substance, technical product, formulation or other.- Physical state: indicate "gas", "solid" or "liquid" only if different from submission substance or if substance can occur in different physical states.- Analytical purity: specify in %- Impurities (identity and concentrations): specify- Composition of the test material, percentage of components: specify if applicable- Isomers composition: specify if applicable- Purity test date: provide if available- Lot/batch No.: provide if available- Expiration date of the lot/batch: provide if available- Radiochemical purity (if radiolabelling): specify if applicable- Specific activity (if radiolabelling): specify if applicable- Locations of the label (if radiolabelling): specify if applicable- Expiration date of radiochemical substance (if radiolabelling): specify if applicable- Storage condition of test substance: specify if applicable- Stability under test conditions: indicate if available [Path: PC_FLAMM.TESTMAT_DETAILS.FREETEXT_BELOW] [Path: PC_FLAMM.TESTMAT_CONFIDENTIAL_DETAILS] Enter any confidential information on the test material in this separate field. Use freetext template and delete/add elements as appropriate. Enter any details that could be relevant for evaluating this study summary or that are requested by the respective regulatory programme. Consult the programme-specific guidance (e.g. OECD HPVC, Pesticides NAFTA or EU REACH) thereof.Explanations:- Analytical purity: specify in %- Impurities (identity and concentrations): specify- Composition of the test material, percentage of components: specify if applicable- Purity test date: provide if available- Lot/batch No.: : provide if available- Expiration date of the lot/batch: : provide if available- Isomers composition: specify if applicable [Path: PC_FLAMM.TESTMAT_CONFIDENTIAL_DETAILS.FREETEXT_BELOW] [Path: PC_FLAMM.REM_ME_TC] In this field, you can enter any information on materials and methods, for which no distinct field is available, or transfer free text from other databases. You can also open a rich text editor and create formatted text and tables or insert and edit any excerpt from a word processing or spreadsheet document, provided it was converted to the HTML format.Note: One rich text editor field each is provided for the MATERIALS AND METHODS and RESULTS section. In addition the fields "Overall remarks" and "Executive summary" allow rich text entry. [Path: PC_FLAMM.REM_ME_TC.RICHTEXT_BELOW] [Path: PC_FLAMM.GEN_RESULTS_HD] [Path: PC_FLAMM.PYROPHORIC_PROPERTIES] Indicate whether the solid or liquid substance ignites or causes charring when added to an inert carrier and brought into contact with air at ambient temperature for a period of five minutes. Any remarks can be entered in in the related "Remarks" field. [Path: PC_FLAMM.PYROPHORIC_PROPERTIES.IGNITION_CONTACT] [Path: PC_FLAMM.PYROPHORIC_PROPERTIES.IGNITION_CONTACT_TXT] [Path: PC_FLAMM.PYROPHORIC_PROPERTIES.REM] [Path: PC_FLAMM.RELEASE_GAS_CONTACT_WATER] Indicate whether the solid or liquid substance releases flammable gas when brought into contact with water or damp air at ambient temperature. Any remarks can be entered in the related "Remarks" field. [Path: PC_FLAMM.RELEASE_GAS_CONTACT_WATER.RELEASE_GAS_CONTACT_WATER] [Path: PC_FLAMM.RELEASE_GAS_CONTACT_WATER.RELEASE_GAS_CONTACT_WATER_TXT] [Path: PC_FLAMM.RELEASE_GAS_CONTACT_WATER.REM] [Path: PC_FLAMM.BURNING_TIME] For solid, provide burning time in sec.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.BURNING_TIME.LOQUALIFIER] For solid, provide burning time in sec.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.BURNING_TIME.LOVALUE] [Path: PC_FLAMM.BURNING_TIME.UPQUALIFIER] [Path: PC_FLAMM.BURNING_TIME.UPVALUE] [Path: PC_FLAMM.BURNING_TIME.REM] Enter any remarks related to the recorded value as appropriate. [Path: PC_FLAMM.FLAME_EXTENSION] For aerosol, provide the flame extension reported to the nearest cm, if determined with this method.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.FLAME_EXTENSION.LOQUALIFIER] For aerosol, provide the flame extension reported to the nearest cm, if determined with this method.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.FLAME_EXTENSION.LOVALUE] [Path: PC_FLAMM.FLAME_EXTENSION.UPQUALIFIER] [Path: PC_FLAMM.FLAME_EXTENSION.UPVALUE] [Path: PC_FLAMM.FLAME_EXTENSION.REM] Enter any remarks related to the recorded value as appropriate. [Path: PC_FLAMM.FLAME_PROJECTION] For aerosol, provide the flame projection reported to the nearest cm, if determined with this method.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.FLAME_PROJECTION.LOQUALIFIER] For aerosol, provide the flame projection reported to the nearest cm, if determined with this method.Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.FLAME_PROJECTION.LOVALUE] [Path: PC_FLAMM.FLAME_PROJECTION.UPQUALIFIER] [Path: PC_FLAMM.FLAME_PROJECTION.UPVALUE] [Path: PC_FLAMM.FLAME_PROJECTION.REM] Enter any remarks related to the recorded value as appropriate. [Path: PC_FLAMM.LOEXPLOS_LIMIT] For gas, provide lower explosion limit (%).Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.LOEXPLOS_LIMIT.LOQUALIFIER] For gas, provide lower explosion limit (%).Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.LOEXPLOS_LIMIT.LOVALUE] [Path: PC_FLAMM.LOEXPLOS_LIMIT.UPQUALIFIER] [Path: PC_FLAMM.LOEXPLOS_LIMIT.UPVALUE] [Path: PC_FLAMM.LOEXPLOS_LIMIT.REM] Enter any remarks related to the recorded value as appropriate. [Path: PC_FLAMM.UPEXPLOS_LIMIT] For gas, provide upper explosion limit (%).Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.UPEXPLOS_LIMIT.LOQUALIFIER] For gas, provide upper explosion limit (%).Enter a numeric value or a range of numeric values according to following conventions:(i) In the first numeric field, enter a single value (Qualifier subfield left blank) or a value if preceded by ">", ">=" or "ca." (e.g. "20", "ca. 20", ">20").(ii) In the second numeric field, enter a single value if preceded by "<" or "<=".(iii) Use both numeric fields and, as required, the lower and upper qualifier field to enter a range of numeric values (e.g. "2 - 8" or ">2 <8"). [Path: PC_FLAMM.UPEXPLOS_LIMIT.LOVALUE] [Path: PC_FLAMM.UPEXPLOS_LIMIT.UPQUALIFIER] [Path: PC_FLAMM.UPEXPLOS_LIMIT.UPVALUE] [Path: PC_FLAMM.UPEXPLOS_LIMIT.REM] Enter any remarks related to the recorded value as appropriate. [Path: PC_FLAMM.REM_RS] In this field, you can enter any other remarks on results. You can also open a rich text editor and create formatted text and tables or insert and edit any excerpt from a word processing or spreadsheet document, provided it was converted to the HTML format.Note: Both the "Materials and methods" section and "Results" section. In addition the fields "Overall remarks" and "Executive summary" allow rich text entry. [Path: PC_FLAMM.REM_RS.RICHTEXT_BELOW] [Path: PC_FLAMM.GEN_OVERALL_HD] [Path: PC_FLAMM.REM_ANYOTHER] In this field, you can enter any overall remarks or transfer free text from other databases. You can also open a rich text editor and create formatted text and tables or insert and edit any excerpt from a word processing or spreadsheet document, provided it was converted to the HTML format.Note: One rich text editor field each is provided for the MATERIALS AND METHODS and RESULTS section. In addition the fields "Overall remarks" and "Executive summary" allow rich text entry. [Path: PC_FLAMM.REM_ANYOTHER.RICHTEXT_BELOW] [Path: PC_FLAMM.AD] Attach any background document that cannot be inserted in any rich text editor field, particularly image files (e.g. an image of a structural formula).Copy this block of fields for attaching more than one file. [Path: PC_FLAMM.AD.DOC] Upload file by clicking the upload icon. As appropriate, enter any additional information, e.g. language. The file name is displayed after uploading the document. [Path: PC_FLAMM.AD.REM] As appropriate, include remarks, e.g. a short description of the content of the attached document if the file name is not self-explanatory. [Path: PC_FLAMM.AD_STUDYREPORT] If required, an electronic copy of the full study report can be attached as WORD, pdf or other document type, which will not be integrated in any report, but must be handled as separate files.Note: In the export administration you can indicate whether the attached files should be included in the data export or not. [Path: PC_FLAMM.AD_STUDYREPORT.ATTACHMENT_BELOW] Upload file by clicking the upload icon. As appropriate, enter any additional information, e.g. language. The file name is displayed after uploading the document. [Path: PC_FLAMM.PG_ILLUSTRATION] If required, an image can be attached (e.g. jpg, png, gif).Note: Only image formats are supported.It is not possible to include MS Word (doc) or Adobe Portable Documents (pdf). [Path: PC_FLAMM.PG_ILLUSTRATION.PIC_BELOW] Upload file by clicking the upload icon. As appropriate, enter any additional information, e.g. language. The file name is displayed after uploading the document. [Path: PC_FLAMM.GEN_APPL_SUM_HD] [Path: PC_FLAMM.INTERPRET_RESULTS_SUBM] Indicate the result of the test conducted according to the method indicated in the field "Guideline" or "Principles of method if other than guideline". If more than one method was used, prepare separate records.If relevant, describe any preliminary results in the field "Any other information on results incl. tables". [Path: PC_FLAMM.INTERPRET_RESULTS_SUBM.LIST_POP_FIX] [Path: PC_FLAMM.INTERPRET_RESULTS_SUBM.LIST_POP_FIX_TXT] [Path: PC_FLAMM.APPL_CL] Enter any conclusions if applicable. [Path: PC_FLAMM.APPL_CL.TEXTAREA_BELOW] [Path: PC_FLAMM.APPL_EXEC_SUM] If required by the respective national/regional programme, briefly summarise the relevant aspects of the study including the conclusions reached. If a specific format is prescribed, upload the respective freetext template if available from the drop-down list or copy it from the corresponding document.Consult the programme-specific guidance (e.g. OECD HPVC, Pesticides NAFTA or EU REACH) thereof. [Path: PC_FLAMM.APPL_EXEC_SUM.RICHTEXT_BELOW] [Path: PC_FLAMM.CROSSREF_OTHER_STUDY] A Cross-reference to other study or other studies can be included which are considered relevant in the interpretation of the test results, e.g. for supporting the conclusion that an effect observed was not substance-related. Indicate the respective chapter(s) and record ID(s) and enter relevant explanatory text.Such cross-references may be useful if it is considered relevant to discuss other results at the summary level of a single study. It should be noted that the overall appraisal of results from different studies is normally done in the hazard or risk assessment.Note that any such cross-reference may become useless if a record is either printed or exchanged on its own. [Path: PC_FLAMM.CROSSREF_OTHER_STUDY.TEXT_BELOW] The version timestamp associates the XSDs with the underlying data format specification version as published by the IUCLID Management Group. See also layout.xml and the version attribute in data documents. The document reference pointing to the current document robust study flag used for classification flag used for MSDS flag