> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : ROD030 - - (Données personne (individu) / Gegevens persoon (individu))-
- Approved
, and is part of release 202001
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 6
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
10 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
||
20 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
||
30 |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
||
40 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
||
50 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
||
60 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
||
70 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
||
80 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
||
90 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
||
100 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
||
110 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
||
120 |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
||
130 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
||
140 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
||
150 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
||
160 |
Date de naissance
|
No
|
-
|
-
|
Option.
|
||
161 |
Date lecture adresse authentique
|
No
|
-
|
-
|
Cond.
|
if BIN A09X = 1
|
|
170 |
Numéro du registre national
|
No
|
-
|
-
|
Cond.
|
depending on the legislator
|
|
180 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
||
190 |
Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
200 |
Numéro de GSM
|
No
|
-
|
-
|
Option.
|
||
210 |
Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
220 |
Adresse e-Mail
|
No
|
-
|
-
|
Option.
|
||
230 |
Profession
|
Yes
|
0
|
Option.
|
|||
240 |
Sexe
|
Yes
|
2
|
Option.
|
|||
250 |
Etat civil
|
Yes
|
5
|
Option.
|
|||
260 |
Code langue de l'intervenant
|
Yes
|
2
|
Option.
|
|||
270 | u |
Statut social
|
Yes
|
6
|
Option.
|
||
279 | n |
Personne exposée politiquement
|
No
|
-
|
-
|
Mand.
|
|
280 |
Données eID conformes
|
No
|
-
|
-
|
Option.
|
||
281 |
Adresse officielle authentique
|
No
|
-
|
-
|
Option.
|
||
290 |
Personne isolée
|
No
|
-
|
-
|
Option.
|
||
300 |
Description
|
No
|
-
|
-
|
Option.
|
||
310 |
Garantie
|
No
|
-
|
-
|
Mand.
|
1..n presencies
|
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.