Message Content Inventory |
Archived, and was part of release 200701 : Identifier : ROD030 - - (Données personne (individu) / Gegevens persoon (individu)) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - Version : 2
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
5 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredPersonIndividual
|
||
10 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
15 |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
20 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
25 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
30 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
35 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
AddressDetail StreetName
|
||
40 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
AddressDetail HouseNumber
|
||
45 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
AddressDetail BoxNumber
|
||
50 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressExtension
|
||
55 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressIdentifier
|
||
60 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
PostalCode
|
||
65 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
CityName
|
||
70 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
CountryCoded
|
||
75 |
Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
80 |
Profession
|
Yes
|
0
|
Option.
|
OccupationPrimary
|
|||
85 |
Sexe
|
Yes
|
2
|
Option.
|
GenderCode
|
|||
90 |
Etat civil
|
Yes
|
4
|
Option.
|
CivilStatusCode
|
|||
95 | u |
Code langue de l'intervenant
|
Yes
|
2
|
Option.
|
LanguageCodeOfThePartyConcernedCode
|
||
100 |
Statut social
|
Yes
|
5
|
Option.
|
SocialStatusCode
|
|||
105 |
Personne isolée
|
No
|
-
|
-
|
Option.
|
IsolatedPersonBinary
|
||
110 |
Description
|
No
|
-
|
-
|
Option.
|
DescriptionText
|
||
115 |
Garantie
|
No
|
-
|
-
|
Mand.
|
Guarantee...
|
(*) 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.