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

EDIFACT message guide · Healthcare and social

SSREGW Notification of registration of a worker

The UN/EDIFACT message social security bodies exchange to register a worker's social security number and compile worker details.

Sent by
Designated social security body
Received by
Equivalent body in another state
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT SSREGW message?

SSREGW is the UN/EDIFACT notification of registration of a worker. The directory defines it as a message exchanged between designated bodies to interchange and register a worker's social security number, and to request and compile details of a worker.

Workers who move between countries build up social security records in each. Registration exchanges let the bodies link the worker's identities across systems, so contributions and entitlements can later be combined. It supports the coordination of social security systems between states, as provided for in bilateral or multilateral agreements such as those between member states of an economic union.

How the EDIFACT SSREGW message worksDiagram of the UN/EDIFACT SSREGW Notification of registration of a worker message. Designated social security body sends it to equivalent body in another state. It usually starts the exchange. It is usually followed by SSRECH. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and GEI (Processing information) and body and segment groups: the required SG2 loop with PNA (Party identification). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SSREGW message worksNotification of registration of a worker: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSSREGWSENDERDesignated socialsecurity bodyRECEIVEREquivalent body inanother stateCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYSSRECHWorker's insurancehistory2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage SSREGWUNH … UNTSTART OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 99PNAParty identification+ 4 conditional groups, starting with:RFFDTMPDIAUTBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for SSREGW. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT SSREGW message worksDiagram of the UN/EDIFACT SSREGW Notification of registration of a worker message. Designated social security body sends it to equivalent body in another state. It usually starts the exchange. It is usually followed by SSRECH. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and GEI (Processing information) and body and segment groups: the required SG2 loop with PNA (Party identification). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SSREGWmessage worksNotification of registration of a worker: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSSREGWSENDERDesignatedsocial securitybodyRECEIVEREquivalent bodyin another stateCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYSSRECHWorker's insurance history2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message SSREGW (UNH … UNT)START OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 99PNAParty identification+ 4 conditional groups, starting with:RFFDTMPDIAUTBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for SSREGW.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends SSREGW, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around SSREGW and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Registering a migrant worker's social security number
  • Linking a worker's records between countries
  • Requesting worker details from another body

Where it fits in the message flow

This message SSREGW Notification of registration of a worker
Usually followed by SSRECH Worker's insurance history

Structure

Mandatory segments in SSREGW (directory D.21A)

In UN/EDIFACT directory D.21A, the SSREGW message has 20 segment positions arranged in 5 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • GEI
  • SG2 (PNA)
  • UNT

Practical example

SSREGW in practice

A worker registered in one country starts a job in another. The new country's social security body sends the first country's body an SSREGW registering the worker's new number and requesting confirmation of identity details. Both bodies link the records for future benefit calculations.

Implementation

Implementation considerations for SSREGW

  • Follow the bilateral or multilateral agreements governing exchanges.
  • Protect personal data under applicable law.
  • Match identities carefully across systems.
  • Record cross-references between national numbers.

How ECOM helps

Automate SSREGW with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Industry

Healthcare

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

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related healthcare and social messages

All 20 healthcare and social messages

Need help with SSREGW?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us