SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : IxD2xx - - (Données spécifiques (sous-)garanties Individuelles, Collectives et Hospitalisation)
- Approved
, and is part of release 202001 - ( 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 |
||||||
| 5 |
Garantie, type
|
No
|
-
|
-
|
Mand.
|
SubGuarantee...
|
||
| 10 |
Durée indemnisation
|
No
|
-
|
-
|
Option.
|
CompensationDuration
|
||
| 20 |
Type d'allocation pour invalidité de longue durée
|
Yes
|
1
|
Option.
|
PaymentForLongTermDisabilityCode
|
|||
| 21 | n |
Cause de l'incapacité couverte
|
Yes
|
1
|
Option.
|
IncapacityCauseCoveredCode
|
||
| 22 | n |
Type de l'incapacité couverte
|
Yes
|
1
|
Option.
|
IncapacityCoveredCode
|
||
| 30 |
Subrogation conventionnelle
|
No
|
-
|
-
|
Option.
|
AgreedSubrogationBinary
|
||
| 31 | n |
Incapacité partielle couverte
|
No
|
-
|
-
|
Option.
|
PartialDisabilityCoveredBinary
|
|
| 32 | n |
Rente viagère se transférant sur 2ième tête
|
No
|
-
|
-
|
Option.
|
AnnuityTransposingTo2ndHeadBinary
|
|
| 40 |
Capital décès
|
No
|
-
|
-
|
Option.
|
DeathBenefitAmount
|
||
| 50 |
Capital - indemnité journalière
|
No
|
-
|
-
|
Option.
|
CapitalDailyAllowanceAmount
|
||
| 60 |
Capital - allocation maximale
|
No
|
-
|
-
|
Option.
|
CapitalMaximumBenefitAmount
|
||
| 70 | u |
Capital - indemnité annuelle
|
No
|
-
|
-
|
Cond.
|
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti
|
CapitalAnnualCompensationAmount
|
| 80 | u |
Intervention dès pourcentage incapacité
|
No
|
-
|
-
|
Option.
|
InterventionAsOfIncapacityPercentage
|
|
| 90 | d |
Pourcentage d'invalidité permanente
|
No
|
-
|
-
|
Option.
|
PercentagePermanentIncapacityPercentage
|
|
| 91 | n |
Seuil pour invalidité considérée totale
|
No
|
-
|
-
|
Option.
|
PermanentIncapacityTresholdPercentage
|
|
| 100 | u |
Pourcentage de croissance de la rente
|
No
|
-
|
-
|
Cond.
|
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti
|
GrowthOfTheAllowancePercentage
|
| 110 | n |
Pourcentage de croissance annuelle de la rente
|
No
|
-
|
-
|
Cond.
|
Mandatory IF Guarantee in 235 Rente pour frais permanents / 280 Revenu garanti
|
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.