SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201601 : Identifier : M9103 - Description d'un intervenant, mise à jour / Persoonsgegevens, aanlevering - (Données sur une relation d'affaires, individu ou autre / Gegevens over een zakenrelatie, individu of ander) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
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 |
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 |
Rôle de l'Intervenant
|
Yes
|
0
|
Option.
|
Party...
|
|||
| 50 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
| 60 |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 70 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 80 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 90 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail NameExtension
|
||
| 100 |
Code titre
|
Yes
|
0
|
Option.
|
OfficialName TitleDetail TitleCoded
|
|||
| 110 |
Adresse - rue
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail StreetName
|
||
| 120 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 130 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 140 |
Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
OfficialAddress PostalCode
|
||
| 150 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
OfficialAddress CityName
|
||
| 160 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 170 |
Adresse de correspondance - rue
|
No
|
-
|
-
|
Option.
|
PostalAddress AddressDetail StreetName
|
||
| 180 |
Adresse de correspondance - numéro de maison
|
No
|
-
|
-
|
Option.
|
PostalAddress AddressDetail HouseNumber
|
||
| 190 |
Adresse de correspondance - identifiant
|
No
|
-
|
-
|
Option.
|
PostalAddress AddressDetail AddressIdentifierResponsibleAgency
|
||
| 200 |
Adresse de correspondance - code postal
|
No
|
-
|
-
|
Option.
|
PostalAddress PostalCode
|
||
| 210 |
Adresse de correspondance - localité
|
No
|
-
|
-
|
Option.
|
PostalAddress CityName
|
||
| 220 |
Adresse de correspondance - code pays
|
No
|
-
|
-
|
Option.
|
PostalAddress CountryCoded
|
||
| 230 |
Adresse de facturation - rue
|
No
|
-
|
-
|
Option.
|
BillingAddress AddressDetail StreetName
|
||
| 240 |
Adresse de facturation - numéro de maison
|
No
|
-
|
-
|
Option.
|
BillingAddress AddressDetail HouseNumber
|
||
| 250 |
Adresse de facturation - identifiant
|
No
|
-
|
-
|
Option.
|
BillingAddress AddressDetail AddressIdentifier
|
||
| 260 |
Adresse de facturation - code postal
|
No
|
-
|
-
|
Option.
|
BillingAddress PostalCode
|
||
| 270 |
Adresse de facturation - localité
|
No
|
-
|
-
|
Option.
|
BillingAddress CityName
|
||
| 280 |
Adresse de facturation - code pays
|
No
|
-
|
-
|
Option.
|
BillingAddress CountryCoded
|
||
| 290 |
Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
| 300 |
Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
||
| 310 |
Numéro d'unité d'entreprise
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
||
| 320 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID CommunicationChannelNumber
|
||
| 330 |
Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID CommunicationChannelNumber
|
||
| 340 |
e-Mail (normal, non-légal)
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID CommunicationChannelNumber
|
||
| 350 |
Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID CommunicationChannelNumber
|
||
| 360 |
Numéro de GSM (smartphone)
|
No
|
-
|
-
|
Option.
|
MobileTelephoneCommID CommunicationChannelNumber
|
||
| 370 |
Assureur - Assureur
|
No
|
-
|
-
|
Cond.
|
Mandatory for Rôle de l'intervenant = PTY+003
|
RelatedActualInsurer
|
|
| 380 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 390 |
Assureur - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 400 |
Assureur - Date opt-in/out contractuel
|
No
|
-
|
-
|
Cond.
|
Together with RPT+300 - COM+008 and BIN+A004
|
EmailOptInOrOutDate
|
|
| 410 |
Assureur - Référence police
|
No
|
-
|
-
|
Option.
|
PolicyReference
|
||
| 420 |
Assureur - Référence police du producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
||
| 430 |
Assureur - Numéro d'identification de l'intervenant (à la compagnie)
|
No
|
-
|
-
|
Option.
|
PartyIdentificationAsGivenByInsurerReference
|
||
| 440 |
Assureur - Référence dossier client chez l'intermédiaire
|
No
|
-
|
-
|
Option.
|
FileReference
|
||
| 450 |
Assureur - Adresse e-Mail contractuel
|
No
|
-
|
-
|
Cond.
|
Together with RPT+300 - DTM+158 and BIN+A004
|
EmailContractuallyBindingCommID CommunicationChannelNumber
|
|
| 460 |
Assureur - e-Mail contractuel
|
No
|
-
|
-
|
Cond.
|
Together with RPT+300 - DTM+158 and COM+008
|
EmailOptInObtainedBinary
|
|
| 470 |
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.