SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0641 - RC Professionnelle Architectes, liste trimestrielle / BA Beroep Architect, driemaand-lijst - (Loi 09/05/2019 - Ordre des architectes - liste trimestrielle)
- Submitted for approval
, and might be part of release 201905 - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Government
Status : 1 - 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 issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 30 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
||
| 40 |
Nombre de contrats dans la liste
|
No
|
-
|
-
|
Mand.
|
PoliciesQuantity
|
||
| 50 |
Intervenant = Preneur d'assurance = Architecte -
|
Yes
|
0
|
Mand.
|
1..n presencies (M0641 is a list!)
|
PartyMainPolicyHolder
|
||
| 60 |
Architecte - Nom officiel - Nom de famille
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
| 70 |
Architecte - Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 80 |
Architecte - Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 90 |
Architecte - Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 100 |
Architecte - Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail NameExtension
|
||
| 110 |
Architecte - Numéro d'entreprise
|
No
|
-
|
-
|
Mand.
|
CompanyNumberReference
|
||
| 120 |
Architecte - Numéro d'enrégistrement d'architecte
|
No
|
-
|
-
|
Mand.
|
RegistrationArchitectReference
|
||
| 130 |
Architecte - Assureur - Assureur
|
No
|
-
|
-
|
Mand.
|
RelatedActualInsurer
|
||
| 140 |
Architecte - Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 150 |
Architecte - Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Mand.
|
CompanyNumberReference
|
||
| 160 |
Architecte - Assureur - Référence police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 170 |
Architecte - Assureur - Date de suspension
|
No
|
-
|
-
|
Cond.
|
ATT+A003 = 4 (police suspendue)
|
SuspensionDate
|
|
| 180 |
Architecte - Assureur - Date d'annulation
|
No
|
-
|
-
|
Cond.
|
ATT+A003 = 3 (police annulée)
|
CancellationDate
|
|
| 190 |
Architecte - Assureur - Date de résiliation
|
No
|
-
|
-
|
Cond.
|
ATT+A003 = 2 (police résiliée)
|
TerminationDate
|
|
| 200 |
Architecte - Assureur - Date d'expiration
|
No
|
-
|
-
|
Cond.
|
ATT+A003 = 6 (en cours jusqu'au) et dans ce dernier trimestre
|
ExpiryDate
|
|
| 210 |
Architecte - Assureur - Etat de la police
|
No
|
-
|
-
|
Mand.
|
M0641 est la liste des - non en cours dans ce dernier trimestre -
|
ContractStatusCode
|
|
| 220 |
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.