Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Archived, and was part of release : Identifier : M9102 - Description d'un intervenant, agrément expert / Beschrijving betrokkene, goedkeuren expert - (As in Community MIG's - Divers : Communication des agréments des experts / Diversen : Mededeling van erkenningen van experten) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 1
|
| 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 |
Description d'un intervenant
|
No
|
-
|
-
|
Mand.
|
XEH+91+1+9102+x--x+x--x++x--x+x--x'
|
|||
| 20 |
Nom officiel
|
No
|
-
|
-
|
Option.
|
NME+001+x--x'
|
OfficialName NameDetail LastName
|
||
| 30 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
ADR+002+x--x
|
OfficialAddress AddressDetail StreetName
|
||
| 40 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
ADR+002+:x--x
|
OfficialAddress AddressDetail HouseNumber
|
||
| 50 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
ADR+002+::x--x
|
OfficialAddress AddressDetail BoxNumber
|
||
| 60 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
ADR+002++x--x
|
OfficialAddress PostalCode
|
||
| 70 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
ADR+002+++x--x
|
OfficialAddress CityName
|
||
| 80 |
Date de début
|
No
|
-
|
-
|
Option.
|
DTM+041:x--x:001'
|
PeriodStartDate
|
||
| 90 |
Date de fin
|
No
|
-
|
-
|
Option.
|
DTM+022:x--x:001'
|
PeriodEndDate
|
||
| 100 |
Numéro d'agrément de l'expert
|
No
|
-
|
-
|
Option.
|
RFF+041:x--x'
|
ExpertApprovalReference
|
||
| 110 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
COM+001:x--x'
|
PrivateTelephoneCommID CommunicationChannelNumber
|
||
| 120 |
Langue de communication
|
Yes
|
3
|
Option.
|
ATT+A10C+x--x'
|
LanguageCode
|
|||
| 130 |
Description d'un intervenant
|
No
|
-
|
-
|
Mand.
|
XET+91'
|
|||
(*) 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.