> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : IxD2xx - - (Données spécifiques (sous-)garanties Individuelles, Collectives et Hospitalisation) - Approved , and is part of release 202001
Sender :
Receiver :
Status : 2 - Version : 3
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
5  
Garantie, type
No
-
-
Mand.
 
ICD+2xx or ISD+2xx 
SubGuarantee... 
10  
Durée indemnisation
No
-
-
Option.
 
DTM+031:nombre_jours:101 
CompensationDuration 
20  
Type d'allocation pour invalidité de longue durée
Yes
1
Option.
 
ATT+2200+valeur_code::valeur 
PaymentForLongTermDisabilityCode 
21 n 
Cause de l'incapacité couverte
Yes
1
Option.
 
ATT+2260+x--x 
IncapacityCauseCoveredCode 
22 n 
Type de l'incapacité couverte
Yes
1
Option.
 
ATT+2262+x--x 
IncapacityCoveredCode 
30  
Subrogation conventionnelle
No
-
-
Option.
 
BIN+21V9+1_oui/2_non 
AgreedSubrogationBinary 
31 n 
Incapacité partielle couverte
No
-
-
Option.
 
BIN+2261+x--x 
PartialDisabilityCoveredBinary 
32 n 
Rente viagère se transférant sur 2ième tête
No
-
-
Option.
 
BIN+1625+x--x 
AnnuityTransposingTo2ndHeadBinary 
40  
Capital décès
No
-
-
Option.
 
MOA+026:amount:EUR:2:001 +X024:X025:X030 
DeathBenefitAmount 
50  
Capital - indemnité journalière
No
-
-
Option.
 
MOA+036:amount:EUR:2:001 +X024:X025:X030 
CapitalDailyAllowanceAmount 
60  
Capital - allocation maximale
No
-
-
Option.
 
MOA+037:amount:EUR:2:001 +X024:X025:X030 
CapitalMaximumBenefitAmount 
70 u 
Capital - indemnité annuelle
No
-
-
Cond.
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti 
MOA+042:amount:EUR:2:001 +X024:X025:X030 
CapitalAnnualCompensationAmount 
80 u 
Intervention dès pourcentage incapacité
No
-
-
Option.
 
PCD+012:pourcentage:2:2 
InterventionAsOfIncapacityPercentage 
90 d 
Pourcentage d'invalidité permanente
No
-
-
Option.
 
PCD+038:pourcentage:2 
PercentagePermanentIncapacityPercentage 
91 n 
Seuil pour invalidité considérée totale
No
-
-
Option.
 
PCD+072:pourcentage:2:2 
PermanentIncapacityTresholdPercentage 
100 u 
Pourcentage de croissance de la rente
No
-
-
Cond.
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti 
PCD+044:pourcentage:2 
GrowthOfTheAllowancePercentage 
110 n 
Pourcentage de croissance annuelle de la rente
No
-
-
Cond.
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti 
PCD+070:pourcentage:2:2 
YearlyGrowthOfTheAllowancePercentage 

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