> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 200901 : Identifier : M0214 - Sinistre, suivi des actes de gestion / Schade, opvolging beheersdaden - (dixit GT Echanges Sinistres; la compagnie envoie l'agenda (complet) du sinistre à l'intermédiaire / dixit de WerkGroep Uitwisselingen Schade; de verzekeraar verzendt het (volledige) schadedossier-agenda aan de tussenpersoon)- - ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) ( Additional information is present below the details-table ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
||
| 11 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
|
| 12 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
|
| 20 |
Type de police
|
Yes
|
5
|
Mand.
|
|||
| 30 |
Date (ré-)ouverture dossier
|
No
|
-
|
-
|
Option.
|
||
| 40 |
Date de clôture du dossier
|
No
|
-
|
-
|
Option.
|
||
| 41 |
Date et heure de l'événement
|
No
|
-
|
-
|
Option.
|
||
| 60 |
Numéro de sinistre
|
No
|
-
|
-
|
Mand.
|
||
| 80 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
||
| 81 | n |
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
| 82 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
| 110 | u |
Etat du dossier
|
Yes
|
1
|
Mand.
|
||
| 230 |
Action (agenda, suivi des actions) - Action
|
No
|
-
|
-
|
Option.
|
multiple presencies- sorted ascending on date
|
|
| 240 |
Action (agenda, suivi des actions) - Date d'agenda
|
No
|
-
|
-
|
Mand.
|
||
| 241 |
Action (agenda, suivi des actions) - Action exécutée
|
No
|
-
|
-
|
Mand.
|
||
| 250 |
Action (agenda, suivi des actions) - Description
|
No
|
-
|
-
|
Mand.
|
||
| 280 |
Assureur - Assureur
|
No
|
-
|
-
|
Mand.
|
||
| 281 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
||
| 310 |
Assureur - Correspondant - Correspondant, gestionnaire
|
No
|
-
|
-
|
Option.
|
||
| 320 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
||
| 330 |
Assureur - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
| 331 |
Assureur - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 332 |
Assureur - Correspondant - e-Mail
|
No
|
-
|
-
|
Mand.
|
||
| 370 |
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
||
| 371 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
||
| 372 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
||
| 380 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
||
| 390 |
Intermédiaire - Référence sinistre du producteur
|
No
|
-
|
-
|
Mand.
|
||
| 391 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
||
| 392 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
||
| 393 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
| 394 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 395 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
||
| 420 |
Preneur d'assurance - Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
||
| 430 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.