284 Commercial Vehicle Safety Reports

Functional Group IH

X12I Transportation Subcommittee

This X12 Transaction Set contains the format and establishes the data contents of the Commercial Vehicle Safety Reports Transaction Set (284) for use within the context of an Electronic Data Interchange (EDI) environment. This bi-directional transaction set can be used by authorized parties to electronically request and send reports on information related to the safe operation of commercial road vehicles, such as inspection reports, safety and compliance review reports, and hazardous material incident reports.

Heading

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To indicate the beginning of a transaction set

  3. NM1 Loop Optional
    Repeat >1
    1. To supply the full name of an individual or organizational entity

      The NM1 loop carries information about the party transmitting or receiving the report.
    2. To specify additional names

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To transmit identifying information as specified by the Reference Identification Qualifier

    6. To identify a person or office to whom administrative communications should be directed

    7. To specify pertinent dates and times

Detail

Position
Segment
Name
Max use
  1. HL Loop Mandatory
    Repeat >1
    1. To identify dependencies among and the content of hierarchically related groups of data segments

      The HL segment identifies the hierarchical relationship of commercial vehicle safety information carried by the transaction. A Report parent level is required for all reports. An Inspection Report may have child levels Event, Company, Shipment, Product Description, Component, Person, Transportation Equipment, Violation. A Compliance Review may have child levels Company, Fleet, Violation, Safety Factor, Safety Fitness, Support Document, Review History, Recommendation. Company may have Product Description child levels. A Hazardous Materials Incident may have child levels Event, Company, Shipment, Traffic Unit, Property. Event may have a Response child level. Shipment may have Product Description child levels. Traffic Unit may have child levels Person, Transportation Equipment. Person may have a Nature of Injury child level. Product Description may have Container child levels. An Accident Report may have child levels Event, Reference Location, Traffic Unit, Property. Traffic Unit may have child levels Transportation Equipment, Person, Shipment. Transportation Equipment may have child levels Action, Damage, Person. Person may have child levels Action, Nature of Injury. Shipment may have Product Description child levels.
    2. To identify the type or transmission or both of paperwork or supporting information

    3. To transmit identifying information as specified by the Reference Identification Qualifier

    4. To specify pertinent dates and times

    5. To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

      The YNQ provides responses to conditions relating to the entity specified in 2/0100.
    6. To identify a commodity or a group of commodities or a tariff page commodity

    7. To specify information relative to hazardous material

    8. To specify the hazardous notation and endorsement information

    9. To specify the hazardous material shipping name and additional descriptive requirements

    10. To specify the physical qualities, packaging, weights, and dimensions relating to the item

    11. To indicate identifying marks and numbers for shipping containers

    12. LQ Loop Optional
      Repeat >1
      1. Code to transmit standard industry codes

        The LQ loop provides report data in coded form.
      2. To transmit identifying information as specified by the Reference Identification Qualifier

      3. To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

        The YNQ provides responses to conditions relating to the data specified in 2/1200.
      4. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

      5. To report information

      6. To specify quantity information

      7. To provide a general description of the area where an entity is located

      8. To provide scores on tests that a student has taken

      9. To provide descriptions that identify a specific vehicle

      10. To provide dynamic information pertaining to a vehicle

      11. AMT Loop Optional
        Repeat >1
        1. To indicate the total monetary amount

        2. To specify pertinent dates and times

    13. NM1 Loop Optional
      Repeat >1
      1. To supply the full name of an individual or organizational entity

        The NM1 loop identifies the entity reporting or receiving the data, the entities involved in the event, or the location of the event.
      2. To specify additional names

      3. To specify the location of the named party

      4. To specify the geographic place of the named party

      5. To transmit identifying information as specified by the Reference Identification Qualifier

      6. To identify a person or office to whom administrative communications should be directed

      7. To describe employment position

      8. To supply demographic information

      9. To supply additional demographic identification

      10. To specify pertinent dates and times

      11. To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

        The YNQ provides responses to conditions relating to the entity specified in 2/2400.
      12. LIE Loop Optional
        Repeat >1
        1. To provide an accurate description of where an individual was located or an event took place

        2. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

    14. MTX Loop Optional
      Repeat >1
      1. To specify textual data

      2. To specify identifying information

  2. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.