Generated Narrative: StructureDefinition bcr-moc-form Name Flags Card. Type Description & Constraints <a href="StructureDefinition-bcr-moc-form-definitions.html#bcr-moc-form" title="Logical model of the Multidisciplinair Oncologisch Consult (MOC) attestation#xA;attached to a Belgian cancer registration. Captures the reason for convening#xA;the MOC, the coordinator, and the participants. Per RIZIV nomenclature#xA;350276-350280 / 350291-350302 / 350372-350383, the coordinator confirms that#xA;both the MOC report and the registration form have been completed.#xA;#xA;Source: Bijlage 55 (vervolg 2) of the RIZIV Verordening of 28 July 2003,#xA;amended 15 December 2025.">bcr-moc-form 0..* Base BCR MOC Form — Bijlage 55 vervolg 2 (Logical Model) #xD; patientName 1..1 string Patient name #xD; nationalOrInsuranceNumber 1..1 string INSZ / Ziekenfondsnummer #xD; <a href="StructureDefinition-bcr-moc-form-definitions.html#bcr-moc-form.mocReason" title="Reason(s) for convening the MOC. Codes:#xA;NEW_DIAGNOSIS = patient with a new cancer diagnosis;#xA;GUIDELINE_DEVIATION = before oncological treatment that deviates from accepted written guidelines;#xA;REPEAT_RADIATION = before a repeat irradiation of the same target area within twelve months;#xA;CTG_DRUG = before chemotherapy with a drug flagged for MOC monitoring by the Commissie Tegemoetkoming Geneesmiddelen;#xA;OTHER = other (specify in `mocOtherReason`).">mocReason 0..* code Reason for MOC Binding: BCR MOC Reason (required) #xD; mocOtherReason 0..1 string Other MOC reason #xD; requester 0..1 BackboneElement MOC requester #xD; name 1..1 string Name #xD; rizivNumber 1..1 string RIZIV number #xD; coordinator 1..1 BackboneElement MOC coordinator #xD; name 1..1 string Name #xD; rizivNumber 1..1 string RIZIV number #xD; institution 1..1 string Institution #xD; mocDate 1..1 date MOC date #xD; participant 0..* BackboneElement MOC participant #xD; name 1..1 string Name #xD; rizivNumber 1..1 string RIZIV number #xD; extramuros 0..1 boolean Extramuros participant #xD; coordinatorConfirmation 0..1 boolean Coordinator confirmation #xD; Documentation for this format
BCR MOC Form — Bijlage 55 vervolg 2 (Logical Model)
Logical model of the Multidisciplinair Oncologisch Consult (MOC) attestation attached to a Belgian cancer registration. Captures the reason for convening the MOC, the coordinator, and the participants. Per RIZIV nomenclature 350276-350280 / 350291-350302 / 350372-350383, the coordinator confirms that both the MOC report and the registration form have been completed. Source: Bijlage 55 (vervolg 2) of the RIZIV Verordening of 28 July 2003, amended 15 December 2025.
Belgian national number (INSZ/NISS) or insurance fund number.
Reason(s) for convening the MOC. Codes: NEW_DIAGNOSIS = patient with a new cancer diagnosis; GUIDELINE_DEVIATION = before oncological treatment that deviates from accepted written guidelines; REPEAT_RADIATION = before a repeat irradiation of the same target area within twelve months; CTG_DRUG = before chemotherapy with a drug flagged for MOC monitoring by the Commissie Tegemoetkoming Geneesmiddelen; OTHER = other (specify in `mocOtherReason`).
Free-text reason when `mocReason` includes OTHER.
Physician requesting the MOC (Aanvrager MOC).
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
RIZIV/INAMI identifier of the requester.
Coordinating physician for the MOC (Coördinator MOC).
RIZIV/INAMI identifier of the coordinator.
Other physicians attending the MOC. The form provides four numbered slots plus one optional extramuros participant.
RIZIV/INAMI identifier of the participant.
True if this participant was the extramuros (extra-muros, non-hospital-staff) participant.
Coordinator's signed confirmation that nomenclature articles 350276-350280, 350291-350302 and 350372-350383 were respected and that the cancer registration form was filled in.