Skip to main content
All CollectionsX12 EDITransaction Sets800-899
X12 - 848 - Material Safety Data Sheet
X12 - 848 - Material Safety Data Sheet
Skylar Nguyen avatar
Written by Skylar Nguyen
Updated over 2 months ago

Product: X12 EDI

Transaction: 848


848 - Material Safety Data Sheet

FUNCTIONAL GROUP=MS

This X12 Transaction Set contains the format and establishes the data contents of the Material Safety Data Sheet Transaction Set (848) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to communicate chemical characteristics, hazards, and precautions for the safe handling and use of a material. The transaction set is intended to convey the information required for a Material Safety Data Sheet (MSDS) as defined by the Occupational Safety and Health Administration (OSHA) Hazard Communication Standard, 29 CFR 1910.1200 in the United States, and Workplace Hazardous Materials Information System (WHIMS) in Canada, and various state, province, and local requirements under right-to-know legislation.

The MSDS provides the receiver with detailed information concerning material identity, emergency response, chemical and physical characteristics, toxicology, and industrial hygiene procedures.

State and federal law dictate who is obligated to provide the MSDS and to whom it should be issued. In addition, third-party providers or others with no statutory obligation may voluntarily provide an MSDS to anyone.

This transaction set allows for transmission of MSDS data in a structured, unstructured, or semi-structured form.
CAUTION: With this transaction set, text format is critical due to the MSDS's primary role as a vehicle for hazards communication. The risk if this information is not transmitted clearly and accurately could be harmful to human life, harmful to the environment, could cause mishandling of product, could result in regulatory non-compliance, and could result in liability.

Trading partners need to agree on how to interpret, store, and display/print MSDS text, especially text contained in the MSG and SD1 segments. For example, a sender may wish to format text so that one print line is mapped to one MSG segment. Segment terminator and data element delimiter characters shall not appear in any MSDS data.

WARNING: Alteration of the original document will occur if the EDI translator or application software converts characters to uppercase. This may adversely affect the appearance, effectiveness, clarity, readability, and communicability of the printed MSDS document.


SCHEMA


ST

Segment

Name

Position

ST

0100

BMS

Beginning Segment For Material Safety Data Sheet

0200

NTE

0300

REF

0400

DTM

0500

N1

LIN

Segment

Name

Position

LIN

0100

PID

0200

MSS

Segment

Name

Position

MSS

Material Safety Data Sheet Section Information

0300

MEA

0400

MSG

Message Text

0500

SD1

Segment

Name

Position

SD1

Safety Data

0600

MEA

0700

PKG

Marking, Packaging, Loading

0720

TD4

0740

MSG

Message Text

0800

CID

Segment

Name

Position

CID

Characteristic/Class ID

1000

MEA

1100

LX

Segment

Name

Position

LX

Transaction Set Line Number

1150

CID

Characteristic/Class ID

1200

MEA

1300

STA

Statistics

1400

TMD

Test Method

1500

MSG

Message Text

1600

SD1

Segment

Name

Position

SD1

Safety Data

1700

MEA

1800

PKG

Marking, Packaging, Loading

1820

TD4

1840

MSG

Message Text

1900

CID

Segment

Name

Position

CID

Characteristic/Class ID

2100

MEA

2200

SE

Segment

Name

Position

SE

Transaction Set Trailer

0200


COMMENTS


Notes

2/0100

LIN loop is product level. MSS is section level. The first SD1 loop is safety data relating to the section only. The first CID loop is for complex measurements on safety data. LX loop is used to specify product characteristics, components, or complex measurements (i.e., those with environmental parameters). The second SD1 loop is safety data relating to a particular product characteristic or component. The second CID loop is for complex measurements on safety data, which related to a particular product characteristic or component.

2/0300

Regulation notifications can be contained in MSS or SD1 or both.

2/0500

Trading partners must agree on a convention for text processing that will not split words, and which can convey correct meaning, in successive SD1 or MSG segments.

2/0600

Regulation notifications can be contained in MSS or SD1 or both.

2/0800

Trading partners must agree on a convention for text processing that will not split words, and which can convey correct meaning, in successive SD1 or MSG segments.

rev 11/12/2024


​

Did this answer your question?