SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0902 - Prévention fraude, renvoi R.S.R. / Fraudepreventie, terugsturen R.S.R. - (As in Community MIG's - Datassur - RSR : Renvoi par Datassur / Terugzending door Datassur)
- Approved
, and is part of release 2005pre - (UN/Edifact & XML/JSON : added info ) |
Sender : Datassur
Receiver : Insurer
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 |
Message about fraud prevention
|
No
|
-
|
-
|
Mand.
|
|||
| 20 |
Message about fraud prevention - RSR return
|
No
|
-
|
-
|
Mand.
|
|||
| 30 |
Message domain
|
No
|
-
|
-
|
Mand.
|
this message id domain independent
|
Domain
|
|
| 40 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 50 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 60 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
||
| 70 |
Code release RSR
|
Yes
|
0
|
Mand.
|
RsrReleaseProcesscode
|
|||
| 80 |
Type de transaction RSR
|
Yes
|
1
|
Mand.
|
RsrTransactionProcesscode
|
|||
| 90 |
Code erreur
|
No
|
-
|
-
|
Mand.
|
Note - D011 is not yet a Telebib2 coded list
|
ErrorProcesscode
|
|
| 100 |
Branche
|
Yes
|
1
|
Mand.
|
BranchProductcode ProductDetail ProductIdentifier
|
|||
| 110 |
Sous-branche
|
Yes
|
1
|
Mand.
|
SubBranchProductcode ProductDetail ProductIdentifier
|
|||
| 120 |
Moment de l'événement
|
No
|
-
|
-
|
Mand.
|
MomentOfTheEventDateTime
|
||
| 130 |
Date de constation des faits
|
No
|
-
|
-
|
Mand.
|
FactsEstablishmentDate
|
||
| 140 |
Date enregistrement par Datassur
|
No
|
-
|
-
|
Mand.
|
DatassurRegistrationDate
|
||
| 150 |
Numéro de la fiche Datassur
|
No
|
-
|
-
|
Mand.
|
DatassurRecordReference
|
||
| 160 |
Motif d'enregistrement
|
Yes
|
1
|
Mand.
|
ReasonForRegistrationCode
|
|||
| 170 |
Tranche de montant
|
Yes
|
1
|
Mand.
|
AmountBracketCode
|
|||
| 180 |
Adresse douteuse
|
No
|
-
|
-
|
Mand.
|
DatassurRegistrationAddressCodeProbablyIncorrectBinary
|
||
| 190 |
Il y a-t-il contestation de la fiche RSR
|
No
|
-
|
-
|
Mand.
|
DatassurRegistrationDisputeBinary
|
||
| 200 |
Total des indemnités
|
No
|
-
|
-
|
Mand.
|
TotalBenefitsAmount
|
||
| 210 |
Nombre de sinistres
|
No
|
-
|
-
|
Mand.
|
ClaimsQuantity
|
||
| 220 |
Nombre de sinstres responsables
|
No
|
-
|
-
|
Mand.
|
ClaimsAtFaultQuantity
|
||
| 230 |
Preneur
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
| 240 |
Preneur - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName
|
||
| 250 |
Preneur - Adresse
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail StreetName
|
||
| 260 |
Preneur - Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
| 270 |
Preneur - Numéro TVA
|
No
|
-
|
-
|
Option.
|
VatReference
|
||
| 280 |
Preneur - Personne physique ou morale
|
Yes
|
1
|
Mand.
|
NaturalOrLegalPersonCode
|
|||
| 290 | u |
Preneur - Langue
|
Yes
|
3
|
Mand.
|
LanguageCode
|
||
| 300 |
Preneur - Sexe
|
Yes
|
1
|
Mand.
|
GenderCode
|
|||
| 310 |
Preneur - Statut juridique
|
Yes
|
1
|
Mand.
|
LegalFormCode
|
|||
| 320 |
Preneur - Qualité de la personne dans le dossier
|
Yes
|
2
|
Mand.
|
CapacityOfThePartyInTheFileCode
|
|||
| 330 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 340 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
formerly named UPEA/BVVO / OCA/CDV -number
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 350 |
Assureur - Numéro du dossier
|
No
|
-
|
-
|
Mand.
|
FileReference
|
||
| 360 |
Assureur - Numéro de la fiche Datassur
|
No
|
-
|
-
|
Mand.
|
DatassurRecordReference
|
||
| 370 |
Objet de risque
|
No
|
-
|
-
|
Option.
|
ObjectInsuredUndefinedObject
|
||
| 380 |
Objet de risque - Situation du risque
|
No
|
-
|
-
|
Mand.
|
RiskAddress
|
||
| 390 |
Message end
|
No
|
-
|
-
|
Mand.
|
|||
(*) 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.