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

SSIMOD Modification of identity details

The UN/EDIFACT message used to tell the country of first registration about changes to a worker's identity details.

Sent by
Designated social security body
Received by
Body in the country of first registration
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT SSIMOD message?

SSIMOD is the UN/EDIFACT modification of identity details. The directory defines it as a message sent to communicate to the country of first registration the modifications of identity details that took place since the last transmission about the worker.

Names, addresses and civil status change over a working life. Passing changes back to the country of first registration keeps linked records consistent, so later exchanges about the worker match correctly. It complements SSREGW, which registers the worker initially. Keeping identity details aligned prevents mismatches when insurance histories are later requested with SSRECH.

How the EDIFACT SSIMOD message worksDiagram of the UN/EDIFACT SSIMOD Modification of identity details message. Designated social security body sends it to body in the country of first registration. It usually follows SSREGW. 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 IND (Index details). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT SSIMOD message worksModification of identity details: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSSSREGWNotification ofregistration of aworkerSSIMODSENDERDesignated socialsecurity bodyRECEIVERBody in the country offirst registrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage SSIMODUNH … UNTSTART OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 2INDIndex details+ 3 conditional groups, starting with:RFFPNAAUTBlue 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 SSIMOD. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT SSIMOD message worksDiagram of the UN/EDIFACT SSIMOD Modification of identity details message. Designated social security body sends it to body in the country of first registration. It usually follows SSREGW. 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 IND (Index details). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT SSIMODmessage worksModification of identity details: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSSSREGWNotification of registration of aworkerSSIMODSENDERDesignatedsocial securitybodyRECEIVERBody in thecountry of firstregistrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message SSIMOD (UNH … UNT)START OF MESSAGEBGMBeginning of messageGEIProcessing informationBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 2INDIndex details+ 3 conditional groups, starting with:RFFPNAAUTBlue 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 SSIMOD.Your trading partner's implementation guide adds itsown requirements.

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

  • Reporting name changes after marriage
  • Reporting changes of address or civil status
  • Correcting identity data

Where it fits in the message flow

Usually follows SSREGW Notification of registration of a worker
This message SSIMOD Modification of identity details

Structure

Mandatory segments in SSIMOD (directory D.21A)

In UN/EDIFACT directory D.21A, the SSIMOD message has 21 segment positions arranged in 6 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 (IND)
  • UNT

Practical example

SSIMOD in practice

A worker registered abroad changes surname after marriage. The social security body in the country of residence records the change and sends the country of first registration an SSIMOD with the old and new details. That body updates its record so future exchanges match.

Implementation

Implementation considerations for SSIMOD

  • Send changes promptly after they are recorded.
  • Protect personal data under applicable law.
  • Identify the worker with cross-referenced numbers.
  • Keep a history of identity changes for each worker.

How ECOM helps

Automate SSIMOD 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 SSIMOD?

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

Request a Demo Contact us