SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0213 - Sinistre, Attestation de -, partie sinistre / Schadegeval, -attest, gedeelte schadegeval - (As in Community MIG's - Echanges Intercompagnies - Attestation de sinistres - partie sinistre - Voir M0151 pour la partie contrat / Inter-maatschappijberichten - Schadeattest - gedeelte schadegeval - Zie M0151 voor het gedeelte contract)
- 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 | d |
Message envelope, sender identification, public
|
No
|
-
|
-
|
Mand.
|
deleted as incorporated in MCI AMEMEv1
|
SenderIdentificationDetail SenderDomainAddress
|
| 20 | d |
Message envelope, sender identification, private
|
No
|
-
|
-
|
Option.
|
deleted as incorporated in MCI AMEMEv1
|
SenderIdentificationDetail SenderUserAddress
|
| 30 | d |
Message envelope, recipient identification, public
|
No
|
-
|
-
|
Mand.
|
deleted as incorporated in MCI AMEMEv1
|
RecipientIdentificationDetail RecipientDomainAddress
|
| 40 | d |
Message envelope, recipient identification, private
|
No
|
-
|
-
|
Option.
|
deleted as incorporated in MCI AMEMEv1
|
RecipientIdentificationDetail RecipientUserAddress
|
| 50 | d |
Message envelope, content type est attestation de sinistre
|
No
|
-
|
-
|
Option.
|
deleted as incorporated in MCI AMEMEv1
|
GroupType
|
| 60 |
Sinistre, en domaine auto
|
No
|
-
|
-
|
Mand.
|
|||
| 70 | u |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
|
| 80 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 90 |
SAS état du dossier sinistre
|
Yes
|
1
|
Mand.
|
SasClaimFileStatusCode
|
|||
| 100 |
SAS responsabilité du conducteur
|
Yes
|
1
|
Mand.
|
SasDriverLiabilityCode
|
|||
| 110 |
SAS sinistre déjà pris en compte
|
No
|
-
|
-
|
Mand.
|
SasClaimAlreadyAccountedBinary
|
||
| 120 |
Montant payé aux usagers faibles
|
No
|
-
|
-
|
Mand.
|
AmountPaidToTheWeakerRoadUsersAmount
|
||
| 130 |
Montant des indemnités réellement payées
|
No
|
-
|
-
|
Mand.
|
ExpensesActuallyMadeAmount
|
||
| 140 |
Evénement
|
No
|
-
|
-
|
Mand.
|
EventGeneric
|
||
| 150 |
Evénement - Moment de l'événement
|
No
|
-
|
-
|
Mand.
|
MomentOfTheEventDateTime
|
||
| 160 |
Evénement - Objet de risque, véhicule
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredTractorVehicle
|
||
| 170 |
Evénement - Objet de risque, véhicule - SAS disponibilité des données du conducteur
|
Yes
|
1
|
Mand.
|
SasDriverDataAvailabilityProcesscode
|
|||
| 180 |
Evénement - Objet de risque, véhicule - Type de véhicule
|
Yes
|
1
|
Mand.
|
VehicleCode
|
|||
| 190 |
Evénement - Objet de risque, véhicule - Conducteur
|
No
|
-
|
-
|
Mand.
|
PartyDriver
|
||
| 200 |
Evénement - Objet de risque, véhicule - Conducteur - Nom officiel (nom de famille, prénom)
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName
|
||
| 210 |
Evénement - Objet de risque, véhicule - Conducteur - Date de naissance
|
No
|
-
|
-
|
Mand.
|
BirthDate
|
||
(*) 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.