## Profile Comparison between https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient vs https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient

Left: | Patient core BE profile (https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient)
Right: | BePatient (https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient)

### Messages

Error | StructureDefinition.version | Values for version differ: '2.0.0' vs '2.1.2'
Information | StructureDefinition.title | Values for title differ: 'Patient core BE profile' vs 'BePatient'
Information | StructureDefinition.status | Values for status differ: 'active' vs 'draft'
Information | StructureDefinition.date | Values for date differ: '2022-03-24T18:40:52+01:00' vs '2025-07-17T14:54:59+00:00'
Information | StructureDefinition.comment | Values for comment differ: 'The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a 'hard' error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex. Special remarks for KMEHR users: Please note gender in KMEHR is typically expressed using CD-SEX. The two values that do not map directly to the HL7 dataset are 'undefined' (use 'other') and 'changed' (use the actual gender)' vs 'This is primarily the administrative gender. The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a 'hard' error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex. Special remarks for KMEHR users: Please note gender in KMEHR is typically expressed using CD-SEX. The two values that do not map directly to the HL7 dataset are 'undefined' (use 'other') and 'changed' (use the actual gender)'
Information | Patient.gender | Element minimum cardinalities differ: '1' vs '0'
Information | StructureDefinition.short | Values for short differ: 'An address expressed using postal conventions (as opposed to GPS or other location definition formats)' vs 'An address for the individual'
Information | StructureDefinition.comment | Values for comment differ: 'Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the [Location](location.html#) resource). Special remarks for KMEHR users: Note when .use and .type are used they SHALL use the FHIR defined valuesets as per their required binding level in the FHIR specification. In a KMEHR address, the use was defined by CD-ADDRESS but those values can be found in the FHIR valueset. KMEHR values 'careadress', 'other' and 'vacation' are not directly present in the FHIR address-use table but can be mapped to the value 'temp' in FHIR. In those cases, it is RECOMMENDED to also add a .period. In KMEHR, an address might be expressed using free text or a totally structured approach where the streetname and housenumber are put in separate fields. FHIR prefers a more pragmatic approach where the ‘text’ element is used to print on labels. Also, streetname and number are not separate fields as in KMEHR but in a structural approach are given as one or moren ‘line’ elements. It is however RECOMMENDED to use the Streetname, Housenumber and Postbox extensions to express them seperately. Note the FHIR address also allows to optionally define whether the address is a physical, postal or ‘both’ address using the .type field.' vs 'Patient may have multiple addresses with different uses or applicable periods.'

### Metadata

Name | Value | Comments
--- | --- | ---
abstract | false |
baseDefinition | http://hl7.org/fhir/StructureDefinition/Patient |
copyright |  |
date | 2022-03-24T18:40:52+01:00 | 2025-07-17T14:54:59+00:00 | Values Differ
description | Belgian federal profile for a patient. Initially based on the functional description of the NIHDI. Special remarks for KMEHR users: following elements in KMEHR are not available in this FHIR resource. If needed, an extension can be defined in a future iteration of these specifications: the 'deathlocation' (location is not available but the death of the patient is expressed by either date or Boolean cfr. infra.), the 'insurancystatus' (covered in a seperate FHIR resource: Coverage), 'insurancymembership' (covered in a seperate FHIR resource: Coverage) and 'profession' (covered in a possible future FHIR resource: OccupationalData.) |
experimental |  |
fhirVersion | 4.0.1 |
jurisdiction |  |
jurisdiction[0] | urn:iso:std:iso:3166#BE |
kind | resource |
name | BePatient |
publisher | eHealth Platform |
purpose |  |
status | active | draft | Values Differ
title | Patient core BE profile | BePatient | Values Differ
type | Patient |
url | https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient |
version | 2.0.0 | 2.1.2 | Values Differ

### Structure

Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Patient |  | 0..* | Patient | Information about an individual or animal receiving health care services |  | 0..* | Patient | Information about an individual or animal receiving health care services |
id | Σ | 0..1 | string | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
language |  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
|  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |
contained |  | 0..* | Resource | Contained, inline Resources |  | 0..* | Resource | Contained, inline Resources |
Slices for extension |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored |
Slices for identifier | S Σ | 0..* | Identifier | An identifier for this patient Slice: Unordered, Open by value:system | S Σ C | 0..* | Identifier | An identifier for this patient Slice: Unordered, Open by value:system Constraints: be-inv-SSIN |
active | ?!Σ | 0..1 | boolean | Whether this patient's record is in active use | ?!Σ | 0..1 | boolean | Whether this patient's record is in active use |
name | S Σ | 0..* | HumanName | A name associated with the patient | S Σ | 0..* | HumanName | A name associated with the patient |
telecom | Σ | 0..* | ContactPoint | A contact detail for the individual | Σ | 0..* | ContactPoint | A contact detail for the individual |
gender | Σ | 1..1 | code | male | female | other | unknown Binding: ?? (required): The gender of a person used for administrative purposes. | Σ | 0..1 | code | male | female | other | unknown Binding: ?? (required): The gender of a person used for administrative purposes. | Element minimum cardinalities differ: '1' vs '0'
birthDate | Σ | 0..1 | date | The date of birth for the individual | Σ | 0..1 | date | The date of birth for the individual |
id |  | 0..1 | string | xml:id (or equivalent in JSON) |  | 0..1 | string | xml:id (or equivalent in JSON) |
Slices for extension |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |
value |  | 0..1 | date | Primitive value for date |  | 0..1 | date | Primitive value for date |
deceased[x] | ?!Σ | 0..1 | boolean, dateTime | Indicates if the individual is deceased or not | ?!Σ | 0..1 | boolean, dateTime | Indicates if the individual is deceased or not |
address |  | 0..* | ?? | An address expressed using postal conventions (as opposed to GPS or other location definition formats) | Σ | 0..* | ?? | An address for the individual |
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding: ?? (required) |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding: ?? (required) |
multipleBirth[x] |  | 0..1 | boolean, integer | Whether patient is part of a multiple birth |  | 0..1 | boolean, integer | Whether patient is part of a multiple birth |
photo |  | 0..* | Attachment | Image of the patient |  | 0..* | Attachment | Image of the patient |
contact | C | 0..* | BackboneElement | A contact party (e.g. guardian, partner, friend) for the patient | C | 0..* | BackboneElement | A contact party (e.g. guardian, partner, friend) for the patient |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
relationship |  | 0..* | CodeableConcept | The kind of relationship Binding: ?? (extensible) |  | 0..* | CodeableConcept | The kind of relationship Binding: ?? (extensible) |
name |  | 0..1 | HumanName | A name associated with the contact person |  | 0..1 | HumanName | A name associated with the contact person |
telecom |  | 0..* | ContactPoint | A contact detail for the person |  | 0..* | ContactPoint | A contact detail for the person |
address |  | 0..1 | Address | Address for the contact person |  | 0..1 | Address | Address for the contact person |
gender |  | 0..1 | code | male | female | other | unknown Binding: ?? (required): The gender of a person used for administrative purposes. |  | 0..1 | code | male | female | other | unknown Binding: ?? (required): The gender of a person used for administrative purposes. |
organization | C | 0..1 | Reference(Organization) | Organization that is associated with the contact | C | 0..1 | Reference(Organization) | Organization that is associated with the contact |
period |  | 0..1 | Period | The period during which this contact person or organization is valid to be contacted relating to this patient |  | 0..1 | Period | The period during which this contact person or organization is valid to be contacted relating to this patient |
communication |  | 0..* | BackboneElement | A language which may be used to communicate with the patient about his or her health |  | 0..* | BackboneElement | A language which may be used to communicate with the patient about his or her health |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
language |  | 1..1 | CodeableConcept | The language which can be used to communicate with the patient about his or her health Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
|  | 1..1 | CodeableConcept | The language which can be used to communicate with the patient about his or her health Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
preferred |  | 0..1 | boolean | Language preference indicator |  | 0..1 | boolean | Language preference indicator |
generalPractitioner |  | 0..* | Reference(Organisation core BE profile | Practitioner core BE profile | Practitioner role core BE profile) | Patient's nominated primary care provider |  | 0..* | Reference(BeOrganization | BePractitioner | BePractitionerRole) | Patient's nominated primary care provider |
managingOrganization | Σ | 0..1 | Reference(Organisation core BE profile) | Organization that is the custodian of the patient record | Σ | 0..1 | Reference(BeOrganization) | Organization that is the custodian of the patient record |
link | ?!Σ | 0..* | BackboneElement | Link to another patient resource that concerns the same actual person | ?!Σ | 0..* | BackboneElement | Link to another patient resource that concerns the same actual person |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
other | Σ | 1..1 | Reference(Patient | RelatedPerson) | The other patient or related person resource that the link refers to | Σ | 1..1 | Reference(Patient | RelatedPerson) | The other patient or related person resource that the link refers to |
type | Σ | 1..1 | code | replaced-by | replaces | refer | seealso Binding: ?? (required): The type of link between this patient resource and another patient resource. | Σ | 1..1 | code | replaced-by | replaces | refer | seealso Binding: ?? (required): The type of link between this patient resource and another patient resource. |
Documentation for this format