> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Archived, and was part of release 201001 :
 Identifier : PTY003GRP - - (Données preneur d'assurance - Groupement de personnes / Gegevens verzekeringsnemer - Groepering van personen) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 3 - Version : 3
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
TB2 XML and JSON representation (***)
Indicator
Identifier
Version
5  
Party, type
No
-
-
Mand.
 
PartyMainPolicyHolder 
10  
Nom officiel - Nom
No
-
-
Mand.
 
OfficialName NameDetail LastName 
20  
Nom officiel - Extension du nom
No
-
-
Option.
 
OfficialName NameDetail NameExtension 
30  
Code titre
Yes
0
Option.
 
OfficialName TitleDetail TitleCoded 
40  
Adresse - rue
No
-
-
Mand.
 
OfficialAddress AddressDetail StreetName 
50  
Adresse - numéro de maison
No
-
-
Mand.
 
OfficialAddress AddressDetail HouseNumber 
60  
Adresse - numéro de boîte
No
-
-
Option.
 
OfficialAddress AddressDetail BoxNumber 
70  
Adresse - extension
No
-
-
Option.
 
OfficialAddress AddressDetail AddressExtension 
80  
Adresse - identifiant
No
-
-
Option.
 
OfficialAddress AddressDetail AddressIdentifier 
90  
Adresse - code postal
No
-
-
Mand.
 
OfficialAddress PostalCode 
100  
Adresse - localité
No
-
-
Option.
 
OfficialAddress CityName 
110  
Adresse - code pays
No
-
-
Option.
 
OfficialAddress CountryCoded 
120  
Numéro du compte financier
No
-
-
Option.
 
AccountReference 
130 n 
Code BIC
No
-
-
Option.
 
BicReference 
140  
Numéro IBAN
No
-
-
Option.
 
InternationalBankAccountNumberReference 
150  
Numéro de téléphone privé
No
-
-
Option.
 
PrivateTelephoneCommID CommunicationChannelNumber 
160  
Numéro de fax
No
-
-
Option.
 
FaxCommID CommunicationChannelNumber 
170  
Adresse boîte postale électronique
No
-
-
Option.
 
EmailAddressCommID CommunicationChannelNumber 
180  
Personne physique ou morale
Yes
2
Mand.
 
NaturalOrLegalPersonCode 
190  
Langue de communication
Yes
3
Mand.
 
LanguageCode 
200  
Nationalité
Yes
6
Option.
 
NationalityCode 
210 u 
Statut juridique
Yes
7
Option.
 
LegalFormCode 
220  
Statut social
Yes
5
Option.
 
SocialStatusCode 
230  
Code commerce (NACEBEL)
Yes
1
Option.
 
BusinessCodeNacebelCode 
240  
Instructions en cours
No
-
-
Option.
 
DeclarationInvestigationPending ResponseCoded 
250  
Assurance refusée, résiliée ou prolongée sous conditions
No
-
-
Option.
 
DeclarationInsuranceRefusedOrEndedOrExtendedUnderCircumstances ResponseCoded 
260 u 
Assurance refusée, résiliée ou prolongée sous conditions - Type de difficulté
No
-
-
Option.
 
ResponseTypeOfDifficulty ResponseDetail ResponseDetailValueCoded 

(*) 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.