> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : DEDxxx - - (Données franchise) - Approved , and is part of release 201101
- ( 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  
Franchise, type
No
-
-
Option.
See the Recommendations page. 
Deductible... 
20  
Expression en (taux, montant, durée)
Yes
2
Option.
 
ExemptionExpressedAsCode 
30  
Base de calcul
Yes
3
Option.
 
ExemptionCalculationBaseCode 
40  
Type en terminologie Informex
Yes
1
Option.
 
ExcessInformexCode 
50  
Rachat du délai de carence
No
-
-
Option.
 
SurrenderOfUnrefundedSickLeavePeriodBinary 
60  
Maintien du délai de carence après 60 ans
No
-
-
Option.
 
UnrefundedPeriodMaintainedAbove60YearsBinary 
70  
Rachat de la franchise
No
-
-
Option.
 
FranchiseDeductableBuyoutBinary 
80  
Franchise contractuelle
No
-
-
Option.
 
ContractualExemptionBinary 
90  
La franchise n'est pas d'application
No
-
-
Option.
 
TheExemptionDoesNotApplyBinary 
100  
Franchise seuil
No
-
-
Option.
 
ThresholdExemptionBinary 
110  
Franchise jeune conducteur
No
-
-
Option.
 
ExemptionYoungDriverBinary 
120  
Franchise territoriale
No
-
-
Option.
 
LocalExemptionBinary 
130  
Franchise consignée
No
-
-
Option.
 
InBailmentOfTheExemptionBinary 
140  
Franchise, montant
No
-
-
Option.
 
ExemptionAmount 
150  
Valeur minimale
No
-
-
Option.
 
MinimalValueOfFranchiseDeductableAmount 
160  
Valeur maximale
No
-
-
Option.
 
MaximalValueOfFranchiseDeductableAmount 
170 d 
Pourcentage sur la valeur assurée
No
-
-
Option.
Deleted- as decided 2010/12/09 
FranchiseDeductableOnInsuredValuePercentage 
180 d 
Pourcentage sur le montant des dégâts
No
-
-
Option.
Deleted- as decided 2010/12/09 
FranchiseDeductableOnDamageAmountPercentage 
181 n 
Franchise, pourcentage
No
-
-
Option.
Added- as decided 2010/12/09 
FranchiseDeductablePercentage 
190  
Franchise, date de début de période
No
-
-
Option.
 
PeriodStartDate 
200  
Franchise, date de fin de période
No
-
-
Option.
 
PeriodEndDate 
210  
Délai de carence en jours, semaines, mois, ...
No
-
-
Option.
 
WaitingDelayDuration 
220  
Délai d'attente en jours, semaines, mois, ...
No
-
-
Option.
 
ExpiryDate 
230  
Franchise, Durée en années, mois, semaines ou jours
No
-
-
Option.
 
LengthDuration 
240  
Franchise territoriale, le pays, code et/ou nom
No
-
-
Option.
 
EventAddress CountryCoded CountryName 

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