HdBe-Contact
CBB | Concept | Status |
---|---|---|
HdBe-Encounter | Un contact est toute interaction, quelle que soit la situation, entre un patient et le professionnel de la santé, dans laquelle le professionnel de la santé a la responsabilité première de diagnostiquer, d'évaluer et de traiter l'état du patient et d'informer le patient. Il peut s'agir de visites, de rendez-vous ou d'interactions non en face à face. Les contacts peuvent être des visites chez le médecin généraliste ou d'autres cabinets, des visites à domicile, des admissions (en hôpital, établissement de soins ou maison de repos, en établissement psychiatrique ou en cliniques de revalidation) ou d'autres contacts pertinents. Cela comprend les contacts passés et futurs. PurposeLes contacts peuvent être enregistrés pour fournir des informations sur les interactions qui ont eu lieu entre le patient et le professionnel de la santé, et dans quel contexte elles ont eu lieu. InstructionsL'environnement domestique est l'environnement dans lequel le patient séjourne de manière régulière. Une distinction est ainsi faite entre le fait de vivre dans une habitation particulière (privée) et vivre dans un établissement de repos et de soins infirmiers. Cette distinction est la différence entre une « vie indépendante, avec soins supplémentaires éventuels » et une « prise en charge, logement compris ». Dès lors, les résidences-services relèvent de la première catégorie, tandis que les séjours en maisons de repos et de soins relèvent de la seconde. | active |
Encounter | Encounter | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
ContactType | 1..1 | CodeableConceptBinding | |
ContactWith | I | 0..* | Reference(HdBe-HealthProfessional) |
Location | I | 0..1 | Reference(HdBe-HealthcareOrganization) |
StartDateTime | 1..1 | dateTime | |
EndDateTime | 0..1 | dateTime | |
ContactReason | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
Problem | I | 0..* | Reference(HdBe-Problem) |
Procedure | I | 0..* | Reference(HdBe-Procedure) |
DeviatingResult | 0..* | string | |
CommentContactReason | 0..1 | string | |
Origin | 0..1 | CodeableConceptBinding | |
Destination | 0..1 | CodeableConceptBinding |
Encounter | 0..* | |
Encounter.ContactType | CodeableConcept | 1..1 |
Encounter.ContactWith | Reference(HdBe-HealthProfessional) | 0..* |
Encounter.Location | Reference(HdBe-HealthcareOrganization) | 0..1 |
Encounter.StartDateTime | dateTime | 1..1 |
Encounter.EndDateTime | dateTime | 0..1 |
Encounter.ContactReason | BackboneElement | 0..* |
Encounter.ContactReason.Problem | Reference(HdBe-Problem) | 0..* |
Encounter.ContactReason.Procedure | Reference(HdBe-Procedure) | 0..* |
Encounter.ContactReason.DeviatingResult | string | 0..* |
Encounter.ContactReason.CommentContactReason | string | 0..1 |
Encounter.Origin | CodeableConcept | 0..1 |
Encounter.Destination | CodeableConcept | 0..1 |
Encounter | |
Definition | Root concept of the Contact information model. This concept contains all data elements of the Contact information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Encounter.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Encounter.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.ContactType | |
Definition | The type of contact, such as ambulatory, home visit, or virtual. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | ContactType codes |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.ContactWith | |
Definition | The health professional with whom the contact took or will take place. The specialty and role of the health professional can be entered in the HealthProfessional information model. |
Cardinality | 0...* |
Type | Reference(HdBe-HealthProfessional) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.Location | |
Definition | The physical location at which the contact took or will take place. |
Cardinality | 0...1 |
Type | Reference(HdBe-HealthcareOrganization) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.StartDateTime | |
Definition | The date and time at which the contact took or will take place. |
Cardinality | 1...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
Encounter.EndDateTime | |
Definition | The date and time at which the contact ended or will end. If the contact takes place over a period of time, this indicates the end of the period, in the case of an admission, for example. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
Encounter.ContactReason | |
Definition | Container of the ContactReason concept. This container contains all data elements of the ContactReason concept. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Encounter.ContactReason.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Encounter.ContactReason.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Encounter.ContactReason.modifierExtension | |
Definition | 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Encounter.ContactReason.Problem | |
Definition | The problem that is the reason for the contact. |
Cardinality | 0...* |
Type | Reference(HdBe-Problem) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.ContactReason.Procedure | |
Definition | The procedure carried out or that will be carried out during the contact. |
Cardinality | 0...* |
Type | Reference(HdBe-Procedure) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Encounter.ContactReason.DeviatingResult | |
Definition | A deviating result which serves as the reason for the contact. |
Cardinality | 0...* |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.ContactReason.CommentContactReason | |
Definition | Explanation of the reason for the contact. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Encounter.Origin | |
Definition | Location from which the patient comes before the encounter. In most cases this will only be used when the patient is admitted. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Origin codes |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Encounter.Destination | |
Definition | Location to which the patient will go after the encounter. In most cases this will only be used when the patient is discharged. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Destination codes |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Example instances
Encounter | |
---|---|
ContactType | CT0005 - Inpatient (code by Healtdata.Be (Sciensano)) |
ContactWith | Reference to HealthProfessional (E. Penninx) |
Location | Reference to HealthcareProvider (GRAND HOPITAL DE CHARLEROI - SAINT-JOSEPH) |
StartDateTime | 2012-08-16T08:30:00 |
EndDateTime | 2012-08-19T10:20:00 |
ContactReason | - |
ContactReason.Problem | |
ContactReason.Procedure | |
ContactReason.DeviatingResult | |
ContactReason.CommentContactReason | stomach ache |
Origin | 264362003 - Home (code by SNOMED CT) |
Destination | 22232009 - Hospital (code by SNOMED CT) |
zib Encounter-v4.0.1 difference
Concept | Category | Description |
---|---|---|
ContactType |
terminology | Replaced codes with codes in use by Healthdata.be - Sciensano. |
Destination |
terminology | Added SNOMED codes Unkown and Other to the ValueSet. |
Origin |
terminology | Added SNOMED codes Unkown and Other to the ValueSet. |
ContactType |
textual | Added ', such as ambulatory, home visit, or virtual' |
CommentContactReason |
textual | Added period at the end of definition. |
Procedure |
textual | Replaced 'or will' by 'or that will'. |
Encounter |
textual | Removed Dutch context from Evidence Base and Instructions. |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
ContactType | ContactType | extensible | https://fhir.healthdata.be/ValueSet/ContactType |
Origin | Origin | extensible | https://fhir.healthdata.be/ValueSet/Origin |
Destination | Destination | extensible | https://fhir.healthdata.be/ValueSet/Destination |