972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Healthcare and insurance

EDI 148 Report of Injury, Illness or Incident

The X12 document used to report injuries, illnesses or incidents for statistical, legal, claims and risk management purposes.

Sent by
Employer, insurer or claims administrator
Received by
Workers' compensation authority, insurer or other interested party
Standard
ANSI ASC X12

What is an EDI 148?

The EDI 148 Report of Injury, Illness or Incident is the ANSI X12 transaction set used to report information about an injury, illness or incident to entities that need it for statistical, legal, claims and risk management processing.

Workplace injuries must be reported to insurers and, in many jurisdictions, to workers' compensation authorities within set deadlines. Electronic reporting speeds up claims and gives authorities consistent data. Many jurisdictions have adopted specific reporting standards, so implementers follow each jurisdiction's requirements. Reports can be updated later.

How the EDI 148 worksDiagram of the EDI 148 Report of Injury, Illness or Incident. Employer, insurer or claims administrator sends it to workers' compensation authority, insurer or other interested party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BHT (Beginning of Hierarchical Transaction) and detail: the required HL loop with HL (Hierarchical Level). 6 optional loops are listed by their first segment.How the EDI 148 worksReport of Injury, Illness or Incident: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 148SENDEREmployer, insurer orclaims administratorRECEIVERWorkers'compensationauthority, insurer orother interested party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code IJGS … GETransaction set 148ST … SEHEADINGBHTBeginning of Hierarchical Transaction+ 1 optional loop, starting with:NM1DETAILRequired loop HL · repeats up to 999,999HLHierarchical Level+ 5 optional loops, starting with:NM1ESILNLXCFIBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 148. Your trading partner's implementation guide adds its own requirements.
How the EDI 148 worksDiagram of the EDI 148 Report of Injury, Illness or Incident. Employer, insurer or claims administrator sends it to workers' compensation authority, insurer or other interested party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BHT (Beginning of Hierarchical Transaction) and detail: the required HL loop with HL (Hierarchical Level). 6 optional loops are listed by their first segment.How the EDI 148 worksReport of Injury, Illness or Incident: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 148SENDEREmployer,insurer orclaimsadministratorRECEIVERWorkers'compensationauthority,insurer or otherinterested party997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code IJ (GS … GE)Transaction set 148 (ST … SE)HEADINGBHTBeginning of HierarchicalTransaction+ 1 optional loop, starting with:NM1DETAILRequired loop HL · repeats up to999,999HLHierarchical Level+ 5 optional loops, starting with:NM1ESILNLXCFIBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 148. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 148, 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 148 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.

Expand diagram Download SVG

When it is used

  • Reporting workplace injuries to insurers
  • Filing first reports of injury with authorities
  • Reporting incidents for risk management

Where it fits in the document flow

This document 148 Report of Injury, Illness or Incident
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 148 (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
  • BHT
  • NM1
  • HL
  • ESI
  • LX
  • LN
  • VEH
  • AMT
  • III
  • LM
  • LQ
  • CFI
  • AD1
  • SE

Practical example

The 148 in practice

A warehouse worker is injured lifting a pallet. The employer's safety system sends the workers' compensation insurer a 148 with the employee, the date and place of the incident, the nature of the injury and the medical treatment. The insurer opens a claim and files the required report with the state authority.

Implementation

Implementation considerations for the 148

  • Follow each jurisdiction's reporting standard and deadlines.
  • Protect employees' personal and health data.
  • Use the injury and body part codes required.
  • Update reports as the claim develops over time.

How ECOM helps

Automate the 148 with ECOM

Industry

Healthcare

Secure B2B integration and file transfer for providers, suppliers, distributors and healthcare partners.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

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 healthcare and insurance documents

All 31 healthcare and insurance documents

Need help with the EDI 148?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us