> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Identifier : DPTDAMDOD030 - - (Claimant - Damage - Damaged object - données personne (individu)) - Approved , and is part of release 201501
 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 2 - Version : 1
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
TB2 XML and JSON representation (***)
Indicator
Identifier
Version
10  
Claimant - Damage - Damaged person (injured individual)
No
-
-
Mand.
 
ObjectDamagedPersonIndividual 
20  
Claimant - Damage - Damaged person - object instance identifier
No
-
-
Option.
 
RiskObjectDetail ObjectIdentifier CodeListIdentifier 
30  
Claimant - Damage - Damaged person - object instance name
No
-
-
Option.
 
RiskObjectDetail ObjectName 
40  
Claimant - Damage - Damaged person - Type d'affiliation à la mutuelle
Yes
1
Option.
 
MutualInsuranceCoverageCode 
50  
Claimant - Damage - Damaged person - Injured individual -
No
-
-
Mand.
 
PartyDamagedPerson 
60  
Claimant - Damage - Damaged person - Injured individual - Identifier at insurer
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
70  
Claimant - Damage - Damaged person - Injured individual - Identifier at intermediary
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
80  
Claimant - Damage - Damaged person - Injured individual - Type d'affiliation à la mutuelle
Yes
1
Option.
 
MutualInsuranceCoverageCode 
90  
Claimant - Damage - Damaged person - Injured individual - Pourcentage d'invalidité permanente
No
-
-
Option.
 
PercentagePermanentIncapacityPercentage 
100 u 
Claimant - Damage - Damaged person - Treating medical doctor
No
-
-
Option.
 
PartyUsualDoctor 
110  
Claimant - Damage - Damaged person - Treating medical doctor - Identifier at insurer
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
120  
Claimant - Damage - Damaged person - Treating medical doctor - Identifier at intermediary
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
130  
Claimant - Damage - Damaged person - Treating medical doctor - Official name
No
-
-
Option.
 
OfficialName NameDetail LastName FirstName NameExtension 
140  
Claimant - Damage - Damaged person - Treating medical doctor - Address
No
-
-
Option.
 
OfficialAddress 
150  
Claimant - Damage - Damaged person - Treating medical doctor - Telephone
No
-
-
Option.
 
PrivateTelephoneCommID CommunicationChannelNumber 
160 u 
Claimant - Damage - Damaged person - Hospital
No
-
-
Option.
 
PartyHospital 
170  
Claimant - Damage - Damaged person - Hospital - Identifier at insurer
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
180  
Claimant - Damage - Damaged person - Hospital - Identifier at intermediary
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
190  
Claimant - Damage - Damaged person - Hospital - Official name
No
-
-
Option.
 
OfficialName NameDetail LastName FirstName NameExtension 
200  
Claimant - Damage - Damaged person - Hospital - Address
No
-
-
Option.
 
OfficialAddress 
210  
Claimant - Damage - Damaged person - Hospital - Telephone
No
-
-
Option.
 
PrivateTelephoneCommID CommunicationChannelNumber 
220 u 
Claimant - Damage - Damaged person - Certifying medical doctor
No
-
-
Option.
 
PartyCertifiedMedicalDoctor 
230  
Claimant - Damage - Damaged person - Certifying medical doctor - Identifier at insurer
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
240  
Claimant - Damage - Damaged person - Certifying medical doctor - Identifier at intermediary
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
250  
Claimant - Damage - Damaged person - Certifying medical doctor - Official name
No
-
-
Option.
 
OfficialName NameDetail LastName FirstName NameExtension 
260  
Claimant - Damage - Damaged person - Certifying medical doctor - Address
No
-
-
Option.
 
OfficialAddress 
270  
Claimant - Damage - Damaged person - Certifying medical doctor - Examination date
No
-
-
Option.
 
MedicalCheckUpDate 
280  
Claimant - Damage - Damaged person - Certifying medical doctor - Report sent date
No
-
-
Option.
 
DocumentSentDate 
290  
Claimant - Damage - Damaged person - Certifying medical doctor - Telephone
No
-
-
Option.
 
PrivateTelephoneCommID CommunicationChannelNumber 
300  
Claimant - Damage - Damaged person - Certifying medical doctor - Communication text
No
-
-
Option.
 
CommunicationText 

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