Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : ECLAFIL - Echange contextuel, données sinistre - (Consultation sinistre) - Approved , and is part of release 200601 - ( UN/Edifact MIG : Fr / Nl ) |
Version : 1 Status : 2 |
| n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
XML-tag |
UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
Dossier sinistre
|
No
|
-
|
-
|
Mand.
|
Message MessageAboutClaim
|
XEH+02+1
|
||
Numéro de police
|
No
|
-
|
-
|
Option.
|
Contract ContractIdentifier
|
RFF+001+x--x
|
||
Numéro de sinistre
|
No
|
-
|
-
|
Option.
|
Claim ClaimIdentifier
|
RFF+029+x--x
|
||
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyRole InsuranceProvider Intermediary
|
PTY+002
|
||
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider ICBIdentifier
|
PTY+002+x--x (X044-1)
|
||
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
|
No
|
-
|
-
|
Mand.
|
Intermediary BrokerAccountIdentifier
|
PTY+002++x--x (X044-2)
|
||
Dossier sinistre - indication fin dossier
|
No
|
-
|
-
|
Mand.
|
XET+02
|
|||
(*) 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.