X12 transaction guide · Government and regulatory
EDI 249 Animal Toxicological Data
The X12 document used to exchange animal toxicology data collected from studies on pesticides, drugs or other substances.
- Sent by
- Testing laboratory or study sponsor
- Received by
- Regulatory agency or sponsor
- Standard
- ANSI ASC X12
What is an EDI 249?
The EDI 249 Animal Toxicological Data is the ANSI X12 transaction set used to exchange animal toxicology data collected from studies on pesticides, drugs or other substances. It accommodates the lowest reportable level of individual data from the studies.
Regulators assess the safety of chemicals and medicines partly from animal studies submitted by sponsors. Submitting study data electronically, at the level of individual observations, lets reviewers analyze it directly. Regulators now generally prescribe their own study data standards, so current submission formats should be confirmed with each agency.
How to read this diagram: the top row shows who sends the 249, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 249 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.
When it is used
- Submitting toxicology study data to regulators
- Exchanging study data between laboratories and sponsors
- Supporting regulatory safety reviews
Where it fits in the document flow
Structure
Mandatory segments in the 249 (X12 release 008010)
The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.
- ST
- BGN
- STP
- N1
- GID
- GRP
- MSG
- GDP
- REF
- ANI
- ARC
- AOL
- AOR
- NTE
- AST
- AOI
- SE
Practical example
The 249 in practice
A contract laboratory completes a toxicity study on a new pesticide for a sponsor. It transfers the individual animal observations and measurements to the sponsor, which includes them in its regulatory submission. The agency's reviewers analyze the data as part of the safety assessment.
Implementation
Implementation considerations for the 249
- Confirm the study data format each regulator requires.
- Preserve data integrity and audit trails.
- Follow good laboratory practice requirements.
- Validate data against the approved study protocols.
How ECOM helps
Automate the 249 with ECOM
Industry
Pharmaceuticals
Orders, ship notices, chargebacks and sales data exchange for pharma manufacturers and distributors.
Industry
Manufacturing
Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related government and regulatory documents
Need help with the EDI 249?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.