Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : ROD030 - - (Données personne (individu) / Gegevens persoon (individu))
- Approved
, and is part of release 202201 |
Sender :
Receiver :
Status : 2 - Version : 7
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
| 10 | u |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ROD+030
|
ObjectInsuredPersonIndividual
|
| 20 | u |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
NME+001+x--x
|
OfficialName NameDetail LastName
|
| 30 | u |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
NME+001+:x--x
|
OfficialName NameDetail FirstName
|
| 40 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
NME+001+::x--x
|
OfficialName NameDetail FirstName
|
||
| 50 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
NME+001+:::x--x
|
OfficialName NameDetail FirstName
|
||
| 60 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
NME+001+::::x--x
|
OfficialName NameDetail NameExtension
|
||
| 70 | u |
Adresse - rue
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002+x--x
|
OfficialAddress AddressDetail StreetName
|
| 80 | u |
Adresse - numéro de maison
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002+:x--x
|
OfficialAddress AddressDetail HouseNumber
|
| 90 | u |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002+::x--x
|
OfficialAddress AddressDetail BoxNumber
|
| 100 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
ADR+002+::::x--x
|
OfficialAddress AddressDetail AddressExtension
|
||
| 110 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
ADR+002+:::::x--x
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 120 |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
ADR+002+:::::x--x:x--x
|
OfficialAddress
|
||
| 130 | u |
Adresse - code postal
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002++x--x
|
OfficialAddress PostalCode
|
| 140 | u |
Adresse - localité
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002+++x--x
|
OfficialAddress CityName
|
| 150 | u |
Adresse - code pays
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ADR+002++++x--x
|
OfficialAddress CountryCoded
|
| 160 | u |
Date de naissance
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
DTM+001:x--x:001
|
BirthDate
|
| 161 |
Date lecture adresse authentique
|
No
|
-
|
-
|
Cond.
|
if BIN A09X = 1
|
DTM+160:x--x:001
|
AuthenticAddressTakenDate
|
|
| 170 |
Numéro du registre national
|
No
|
-
|
-
|
Cond.
|
depending on the legislator - Mandatory IF IPD+A502 IN (110,115,120,140)
|
RFF+022:x--x
|
NationalRegisterReference
|
|
| 180 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
COM+001:x--x
|
PrivateTelephoneCommID CommunicationChannelNumber
|
|
| 190 |
Numéro de téléphone bureau
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
COM+006:x--x
|
OfficeTelephoneCommID CommunicationChannelNumber
|
|
| 200 |
Numéro de GSM
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
COM+007:x--x
|
MobileTelephoneCommID CommunicationChannelNumber
|
|
| 210 |
Numéro de fax
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
COM+002:x--x
|
FaxCommID CommunicationChannelNumber
|
|
| 220 |
Adresse e-Mail
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
COM+003:x--x
|
EmailAddressCommID CommunicationChannelNumber
|
|
| 230 |
Profession
|
Yes
|
0
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
PFN+001+x--x:x--x:x--x:x--x+x--x+x--x
|
OccupationPrimary JobDetail JobIdentifier CodeListIdentifier CodeListResponsibleAgencyCoded JobName JobCategoryCoded
|
||
| 240 |
Sexe
|
Yes
|
2
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ATT+A124+x--x:x--x:x--x:x--x
|
GenderCode
|
||
| 250 |
Etat civil
|
Yes
|
5
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ATT+A123+x--x:x--x:x--x:x--x
|
CivilStatusCode
|
||
| 260 |
Code langue de l'intervenant
|
Yes
|
2
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ATT+A10T+x--x:x--x:x--x:x--x
|
LanguageCodeOfThePartyConcernedCode
|
||
| 270 |
Statut social
|
Yes
|
6
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
ATT+A132+x--x:x--x:x--x:x--x
|
SocialStatusCode
|
||
| 279 |
Personne exposée politiquement
|
No
|
-
|
-
|
Mand.
|
BIN+A12E+x--x
|
PoliticallyExposedPersonBinary
|
||
| 280 |
Données eID conformes
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
BIN+A09X+x--x
|
EidDataUnchangedBinary
|
|
| 281 |
Adresse officielle authentique
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
BIN+A1ZQ+x--x
|
OfficialAddressAuthenticBinary
|
|
| 290 |
Personne isolée
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
BIN+A225+x--x
|
IsolatedPersonBinary
|
|
| 300 |
Description
|
No
|
-
|
-
|
Cond.
|
Mandatory IF IPD+A502 IN (110,115,120,140)
|
FTX+019+x--x:x--x:x--x:x--x:x--x
|
DescriptionText
|
|
| 310 |
Garantie
|
No
|
-
|
-
|
Mand.
|
1..n presencies
|
ICD+xxx (segment group, multiple occurrencies)
|
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.