SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M9130 - Description opération de renumérotation de portefeuille / Beschrijving hernummering portefeuille - (Liste des contrats et/ou sinistres impactés / Lijst van de betrokken polissen en/of schadedossiers)
- Approved
, and is part of release 201901 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
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 |
Numéro du compte agent identifiant le portefeuille
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 50 |
Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if possible for the full list
|
ReferenceChangeAsOfDate
|
|
| 60 |
Applicable dès échéance mmaaaa
|
No
|
-
|
-
|
Cond.
|
if possible for the full list
|
ReferenceRenewalChangeAsOfDate
|
|
| 70 |
Police
|
No
|
-
|
-
|
Option.
|
0..n occurrences
|
DocumentPolicyOrAmendment
|
|
| 80 |
Police - Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if needed per individual policy
|
ReferenceChangeAsOfDate
|
|
| 90 |
Police - Applicable dès échéance mmaaaa
|
No
|
-
|
-
|
Cond.
|
if needed per individual policy
|
ReferenceRenewalChangeAsOfDate
|
|
| 100 |
Police - Ancien numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 110 |
Police - Nouveau numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 120 |
Police - Ancien numéro d'avenant
|
No
|
-
|
-
|
Option.
|
EndorsementReference
|
||
| 130 |
Police - Nouveau numéro d'avenant
|
No
|
-
|
-
|
Option.
|
EndorsementReference
|
||
| 140 |
Dossier sinistre
|
No
|
-
|
-
|
Option.
|
0..n occurrences
|
DocumentClaimNotification
|
|
| 150 |
Dossier sinistre - Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if needed per individual claim
|
ReferenceChangeAsOfDate
|
|
| 160 |
Dossier sinistre - Ancien numéro de dossier
|
No
|
-
|
-
|
Mand.
|
ClaimReference
|
||
| 170 |
Dossier sinistre - Nouveau numéro de dossier
|
No
|
-
|
-
|
Mand.
|
ClaimReference
|
||
| 180 |
Assureur actuel - le "nouveau" dans le cas
|
No
|
-
|
-
|
Mand.
|
RelatedActualInsurer
|
||
| 190 |
Assureur actuel - code FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 200 |
Assureur actuel - Ancien numéro du compte producteur
|
No
|
-
|
-
|
Option.
|
AgentAccountReference
|
||
| 210 |
Assureur précédent - le "ancien" dans le cas
|
No
|
-
|
-
|
Cond.
|
if needed/changed
|
RelatedPreviousInsuranceAgent
|
|
| 220 |
Assureur précédent - code FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 230 |
Assureur précédent - Ancien numéro du compte producteur
|
No
|
-
|
-
|
Mand.
|
AgentAccountReference
|
||
| 240 |
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.