SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 200901 : Identifier : M0410 - Demande, modification des renseignements client / Vraag, wijziging klant-gegevens - (Changement d'adresse, première version, basée sur l'ancienne requète 022 / Adreswijziging, eerste versie, met als basis het oude verzoek 022) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Broker
Receiver : Insurer
Status : 3 - 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 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
|
| 11 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
|
| 12 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 20 |
Corrigez la dénomination, sinon la raison sociale
|
Yes
|
1
|
Mand.
|
ChangeNameProcesscode
|
|||
| 30 |
Suppression de l'adresse de correspondance interne
|
Yes
|
1
|
Mand.
|
DeleteInternalCorrespondenceAddressProcesscode
|
|||
| 40 |
Numéro de police
|
No
|
-
|
-
|
Cond.
|
claimnumber absent
|
PolicyReference
|
|
| 50 |
Numéro de sinistre
|
No
|
-
|
-
|
Cond.
|
policynumber absent
|
ClaimReference
|
|
| 60 | 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. (complementing document present)
|
MessageGuidReference
|
| 61 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
| 70 |
Champ d'application de la modification
|
Yes
|
1
|
Mand.
|
FieldOfApplicationForAdjustmentCode
|
|||
| 80 |
Acte technique concomitant
|
No
|
-
|
-
|
Mand.
|
ConcomitantTechnicalActBinary
|
||
| 90 |
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
| 100 | n |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 110 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 120 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
||
| 130 | n |
Intermédiaire - Référence sinistre du producteur
|
No
|
-
|
-
|
Option.
|
ClaimReferenceIntermediaryReference
|
|
| 140 | n |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
|
| 150 | n |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
OfficialName
|
|
| 160 | n |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
|
| 170 | n |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
|
| 180 | n |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
|
| 190 |
Preneur d'assurance - Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
| 200 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
| 210 |
Preneur d'assurance - Titre et libellé
|
No
|
-
|
-
|
Mand.
|
OfficialName TitleDetail TitleCoded TitleName
|
||
| 220 |
Preneur d'assurance - Adresse principale - Rue
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail StreetName
|
||
| 230 |
Preneur d'assurance - Adresse principale - Numéro
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 240 |
Preneur d'assurance - Adresse principale - Boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 250 |
Preneur d'assurance - Adresse principale - Code postal
|
No
|
-
|
-
|
Cond.
|
Country = Belgium
|
OfficialAddress PostalCode
|
|
| 260 |
Preneur d'assurance - Adresse principale - Localité
|
No
|
-
|
-
|
Mand.
|
OfficialAddress CityName
|
||
| 270 |
Preneur d'assurance - Adresse principale - code Pays
|
No
|
-
|
-
|
Mand.
|
OfficialAddress CountryCoded
|
||
| 280 |
Preneur d'assurance - Adresse principale - Pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryName
|
||
| 290 |
Preneur d'assurance - Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
| 300 |
Preneur d'assurance - Numéro du compte financier
|
No
|
-
|
-
|
Option.
|
AccountReference
|
||
| 310 | n |
Preneur d'assurance - Code BIC
|
No
|
-
|
-
|
Option.
|
BicReference
|
|
| 320 | n |
Preneur d'assurance - Numéro IBAN
|
No
|
-
|
-
|
Option.
|
InternationalBankAccountNumberReference
|
|
| 330 |
Preneur d'assurance - Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID CommunicationChannelNumber
|
||
| 340 | n |
Preneur d'assurance - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID CommunicationChannelNumber
|
|
| 350 |
Preneur d'assurance - Langue
|
Yes
|
3
|
Mand.
|
LanguageCode
|
|||
| 360 |
Preneur d'assurance - Sexe
|
Yes
|
2
|
Mand.
|
GenderCode
|
|||
| 370 |
Preneur d'assurance - Etat civil
|
Yes
|
4
|
Cond.
|
RPT+101 present
|
CivilStatusCode
|
||
| 380 |
Preneur d'assurance - Conjoint
|
No
|
-
|
-
|
Option.
|
RelatedPartner
|
||
| 390 |
Preneur d'assurance - Conjoint - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
| 400 |
Preneur d'assurance - Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 410 |
Preneur d'assurance - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
| 420 |
Preneur d'assurance - Correspondant - Titre et libellé
|
No
|
-
|
-
|
Mand.
|
OfficialName TitleDetail TitleCoded TitleName
|
||
| 430 |
Preneur d'assurance - Correspondant - Adresse principale - Rue
|
No
|
-
|
-
|
Mand.
|
AddressDetail StreetName
|
||
| 440 |
Preneur d'assurance - Correspondant - Adresse principale - Numéro
|
No
|
-
|
-
|
Option.
|
AddressDetail HouseNumber
|
||
| 450 |
Preneur d'assurance - Correspondant - Adresse principale - Boîte
|
No
|
-
|
-
|
Option.
|
AddressDetail BoxNumber
|
||
| 460 |
Preneur d'assurance - Correspondant - Adresse principale - Code postal
|
No
|
-
|
-
|
Cond.
|
Country = Belgium
|
PostalCode
|
|
| 470 |
Preneur d'assurance - Correspondant - Adresse principale - Localité
|
No
|
-
|
-
|
Mand.
|
CityName
|
||
| 480 |
Preneur d'assurance - Correspondant - Adresse principale - code Pays
|
No
|
-
|
-
|
Mand.
|
CountryCoded
|
||
| 490 |
Preneur d'assurance - Correspondant - Adresse principale - Pays
|
No
|
-
|
-
|
Option.
|
CountryName
|
||
| 500 | n |
Preneur d'assurance - Correspondant - Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID CommunicationChannelNumber
|
|
| 510 | n |
Preneur d'assurance - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID CommunicationChannelNumber
|
|
| 520 |
Preneur d'assurance - Correspondant - Langue
|
Yes
|
3
|
Mand.
|
LanguageCode
|
|||
| 530 |
Preneur d'assurance - Sexe
|
Yes
|
2
|
Mand.
|
GenderCode
|
|||
(*) 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.