Generated Narrative: StructureDefinition BeModelPatient Name Flags Card. Type Description & Constraints BeModelPatient 0..* Base BeModelPatient Instances of this logical model can be the target of a Reference #xD; names 0..* BackboneElement Names #xD; usage 0..1 CodeableConcept Usage context of the name (e.g. NR 11, if the name is used as a pseudonym) #xD; familyname 0..1 string Surname (NR 10) #xD; firstnames 0..1 string Given names (NR 10) #xD; title 0..1 string Title of nobility (NR 12) #xD; period 0..1 Period Period of validity of the name (e.g. NR 13 Change of name, first names and title of nobility) #xD; birth 0..1 BackboneElement Birth data #xD; place 0..1 Address Place of birth (NR 100 or NR 101) #xD; date 0..1 dateTime Date of birth (NR 100 or NR 101) #xD; multiple 0..1 positiveInt Number of siblings + person in case of multiple birth #xD; gender 0..1 BackboneElement Gender #xD; administrative 0..1 CodeableConcept Gender (integrated in the identification no.: 000) #xD; atbirth 0..1 CodeableConcept Gender at birth, accounts for gender changes and errors (NR 2 and NR 4) #xD; social 0..1 CodeableConcept Gender the person identifies with #xD; nationality 0..* CodeableConcept Current nationality (and dual nationality) (NR 31, NR 32) #xD; residence 0..* Address Main and other residences (NR 1, 3, 5, 18, 19, 20,22, 23, 24, 26, 27). NR 252 will be covered by other privacy rules. #xD; death 0..1 BackboneElement Date and state of death (place of death is not clinically relevant, and we only care about factual death, not absence (NR 151) or administrative/judicial death (NR 150)) #xD; date 0..1 dateTime Date of death #xD; deceased 0..1 boolean The person is deceased #xD; maritalstatus 0..1 CodeableConcept Marital Status #xD; telecom 0..1 ContactPoint Means of contact #xD; contact 0..* Identifier Identifiers of contact persons #xD; communication 0..1 CodeableConcept language of communication #xD; generalPractitioner 0..1 Identifier identifier of the GMD holder #xD; managingOrganisation 0..1 Identifier identifier of the organisation managing the patient record #xD; Documentation for this format
Data about a patient, according to the [National Register of Persons (Ministry of the Interior)](https://www.ibz.rrn.fgov.be/fileadmin/user_upload/nl/rr/bestand-rr/bestand-RR.pdf), and possibly other sources to be mentioned when used.
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
Usage context of the name (e.g. NR 11, if the name is used as a pseudonym)
Period of validity of the name (e.g. NR 13 Change of name, first names and title of nobility)
Number of siblings + person in case of multiple birth
Gender (integrated in the identification no.: 000)
Gender at birth, accounts for gender changes and errors (NR 2 and NR 4)
Current nationality (and dual nationality) (NR 31, NR 32)
Main and other residences (NR 1, 3, 5, 18, 19, 20,22, 23, 24, 26, 27). NR 252 will be covered by other privacy rules.
Date and state of death (place of death is not clinically relevant, and we only care about factual death, not absence (NR 151) or administrative/judicial death (NR 150))
identifier of the organisation managing the patient record