Message Content Inventory |
Identifier : M0421 - Demande, attestation de sinistres / Vraag, schadeattest - (As in Community MIG's - Echanges Intercompagnies / Inter-maatschappijberichten - Demande attestation de sinistres / Aanvraag schadeattest)
- Approved
, and is part of release 200601 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Insurer
Status : 2 - Version : 1
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
30 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
||
40 |
Compagnie émettrice
|
No
|
-
|
-
|
Mand.
|
PartySendingCompany
|
||
50 |
Compagnie émettrice Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
60 |
Compagnie émettrice Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
||
70 |
Compagnie émettrice Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
||
80 |
Compagnie émettrice Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
90 |
Compagnie émettrice Assureur - Numéro du dossier
|
No
|
-
|
-
|
Mand.
|
FileReference
|
||
100 |
Compagnie destinataire
|
No
|
-
|
-
|
Mand.
|
PartyReceivingCompany
|
||
110 |
Compagnie destinataire Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
120 |
Compagnie destinataire Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
||
130 |
Compagnie destinataire Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
||
140 |
Compagnie destinataire Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
150 |
Compagnie destinataire Assureur - Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
160 |
Message end
|
No
|
-
|
-
|
Mand.
|
(*) n u d : new / updated / deleted since previous version.
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.