> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : ICD2xx - - (Données spécifiques des garanties Individuelles, Collectives et Hospitalisation) - Approved , and is part of release 201001 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info ) ( Additional information is present below the details-table ) |
Version : 1 Status : 2 |
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2-UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
| 5 |
Garantie, type
|
No
|
-
|
-
|
Mand.
|
ICD+2xx
|
||
| 10 |
Durée indemnisation
|
No
|
-
|
-
|
Option.
|
DTM+031:nombre_jours:101
|
||
| 20 |
Type d'allocation pour invalidité de longue durée
|
Yes
|
1
|
Option.
|
ATT+2200+valeur_code::valeur
|
|||
| 30 |
Subrogation conventionnelle
|
No
|
-
|
-
|
Option.
|
BIN+21V9+1_oui/2_non
|
||
| 40 |
Capital décès
|
No
|
-
|
-
|
Option.
|
MOA+026:amount:EUR:2:001 +X024:X025:X030
|
||
| 50 |
Capital - indemnité journalière
|
No
|
-
|
-
|
Option.
|
MOA+036:amount:EUR:2:001 +X024:X025:X030
|
||
| 60 |
Capital - allocation maximale
|
No
|
-
|
-
|
Option.
|
MOA+037:amount:EUR:2:001 +X024:X025:X030
|
||
| 70 |
Capital - indemnité annuelle
|
No
|
-
|
-
|
Option.
|
MOA+042:amount:EUR:2:001 +X024:X025:X030
|
||
| 80 |
Pourcentage intervention
|
No
|
-
|
-
|
Option.
|
PCD+012:pourcentage:2
|
||
| 90 |
Pourcentage d'invalidité permanente
|
No
|
-
|
-
|
Option.
|
PCD+038:pourcentage:2
|
||
| 100 |
Pourcentage de croissance de la rente
|
No
|
-
|
-
|
Option.
|
PCD+044:pourcentage:2
|
||
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.