SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DEDxxx - - (Données franchise)
- Approved
, and is part of release 202101 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 3
|
| 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 | u |
Base de calcul
|
Yes
|
4
|
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 en dommages corporels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
CorporalDamagesExemptionBinary
|
|
| 150 |
Franchise en dommages matériels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
MaterialDamagesExemptionBinary
|
|
| 160 |
Franchise en dommages mixtes
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
MixedDamagesExemptionBinary
|
|
| 170 |
Franchise en dommages immatériels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
ImmaterialDamagesExemptionBinary
|
|
| 180 |
Franchise en objets confiés
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
EntrustedObjectsExemptionBinary
|
|
| 190 | u |
Franchise, montant
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
ExemptionAmount
|
| 200 | u |
Valeur minimale
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
MinimalValueOfFranchiseDeductableAmount
|
| 210 | u |
Valeur maximale
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
MaximalValueOfFranchiseDeductableAmount
|
| 220 | n |
Franchise - intervention dès incapacité pourcentage
|
No
|
-
|
-
|
Option.
|
InterventionAsOfIncapacityPercentage
|
|
| 221 | n |
Franchise - pourcentage sur valeur assurée
|
No
|
-
|
-
|
Option.
|
FranchiseDeductableOnInsuredValuePercentage
|
|
| 222 | n |
Franchise - pourcentage sur montant des dégats
|
No
|
-
|
-
|
Option.
|
FranchiseDeductableOnDamageAmountPercentage
|
|
| 223 | u |
Franchise - pourcentage (sur montant spécifié)
|
No
|
-
|
-
|
Option.
|
see P11U value
|
FranchiseDeductablePercentage
|
| 224 | n |
Franchise - pourcentage minimal en incapacité de travail
|
No
|
-
|
-
|
Option.
|
MinimumWorkIncapacityPercentage
|
|
| 230 |
Franchise, date de début de période
|
No
|
-
|
-
|
Option.
|
PeriodStartDate
|
||
| 240 |
Franchise, date de fin de période
|
No
|
-
|
-
|
Option.
|
PeriodEndDate
|
||
| 250 |
Délai de carence en jours, semaines, mois, ...
|
No
|
-
|
-
|
Option.
|
WaitingDelayDuration
|
||
| 260 |
Délai d'attente en jours, semaines, mois, ...
|
No
|
-
|
-
|
Option.
|
ExpiryDate
|
||
| 270 |
Franchise, Durée en années, mois, semaines ou jours
|
No
|
-
|
-
|
Option.
|
LengthDuration
|
||
| 280 |
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.