HdBe-MedischHulpmiddel
CBB | Concept | Status |
---|---|---|
HdBe-MedicalDevice | Medische hulpmiddelen kunnen worden omschreven als de inwendig geïmplanteerde en uitwendige apparatuur en/of hulpmiddelen die de patiënt gebruikt of heeft gebruikt om de gevolgen van functionele beperkingen van orgaansystemen te verminderen of om de behandeling van een ziekte mogelijk te maken. PurposeHet vastleggen van gegevens over medische hulpmiddelen heeft een aantal redenen. Kennis van aanwezigheid biedt mogelijkheid om implantaten te kunnen traceren en rekening te houden met het hulpmiddel of apparaat bij diagnostische of therapeutische procedures, verzorging en transport. Voorbeelden hier van zijn:
Evidence BaseHet vastleggen van gegevens van medisch complexe apparatuur, zoals pacemakers, is in EPD systemen in Nederland nog niet gebruikelijk, maar soms wel een gemis: uit een specialistenbrief valt bv. vaak niet op te maken welke type pacemaker van welke fabrikant bij de patiënt aanwezig is. VWS zal met wetgeving komen voor een landelijk basisregister voor implantaten. Elke zorginstelling zal de UDI (Unique Device Identification, met een relatie naar GTIN) en UPI (Unique Patient Identification) moeten aanleveren aan het basisregister. Dit voorkomt de situatie dat een groot deel van de patiënten met een hulpmiddel of implantaat waar problemen mee zijn gesignaleerd, niet te traceren zijn. References
| active |
MedicalDevice | MedicalDevice | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
Product | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
ProductId | 0..1 | string | |
ProductType | 0..1 | CodeableConceptBinding | |
ProductDescription | 0..1 | string | |
AnatomicalLocation | I | 0..1 | Reference(HdBe-AnatomicalLocation) |
Indication | I | 0..* | Reference(HdBe-Problem) |
StartDate | 0..1 | dateTime | |
EndDate | 0..1 | dateTime | |
Comment | 0..1 | string | |
Location | I | 0..1 | Reference(HdBe-HealthcareOrganization) |
HealthProfessional | I | 0..1 | Reference(HdBe-HealthProfessional) |
MedicalDevice | 0..* | |
MedicalDevice.Product | BackboneElement | 1..1 |
MedicalDevice.Product.ProductId | string | 0..1 |
MedicalDevice.Product.ProductType | CodeableConcept | 0..1 |
MedicalDevice.ProductDescription | string | 0..1 |
MedicalDevice.AnatomicalLocation | Reference(HdBe-AnatomicalLocation) | 0..1 |
MedicalDevice.Indication | Reference(HdBe-Problem) | 0..* |
MedicalDevice.StartDate | dateTime | 0..1 |
MedicalDevice.EndDate | dateTime | 0..1 |
MedicalDevice.Comment | string | 0..1 |
MedicalDevice.Location | Reference(HdBe-HealthcareOrganization) | 0..1 |
MedicalDevice.HealthProfessional | Reference(HdBe-HealthProfessional) | 0..1 |
MedicalDevice | |
Definition | Root concept of the MedicalDevice information model. This root concept contains all data elements of the MedicalDevice information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
MedicalDevice.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 |
|
MedicalDevice.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 |
|
MedicalDevice.Product | |
Definition | The medical device (internally or externally). |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
MedicalDevice.Product.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 |
|
MedicalDevice.Product.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 |
|
MedicalDevice.Product.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 |
|
MedicalDevice.Product.ProductId | |
Definition | Unique identification code of the product. Preferably the UDI (Unique Device Identifier) is used, consisting of a UDI-DI (Device Identifier) and a UDI-PI (Production Identifier(s)). Additionally, other codes can be registered if needed. Such as: - a serial number - a NIHDI notification code (medical devices on the Belgian market: https://www.vas.ehealth.fgov.be/registers/sadm/web/search/public) - an identification code as indicated on the Nominative lists published by NIHDI: https://webappsa.riziv-inami.fgov.be/IRREQPublic/nl/Home/SearchNominative). Devices on these Nominative lists meet certain criteria for reimbursement. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicalDevice.Product.ProductType | |
Definition | The code of the type of product. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | ProductType 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 |
|
MedicalDevice.ProductDescription | |
Definition | Textual description of the product. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicalDevice.AnatomicalLocation | |
Definition | Patient’s anatomical location of the medical device used. |
Cardinality | 0...1 |
Type | Reference(HdBe-AnatomicalLocation) |
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 |
|
MedicalDevice.Indication | |
Definition | The medical reason for use of the medical device. |
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 |
|
MedicalDevice.StartDate | |
Definition | The start date of the first use or implant of the medical device. A ‘vague’ date, such as only the year, is permitted. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
MedicalDevice.EndDate | |
Definition | The end date of the last use or explant of the medical device. A ‘vague’ date, such as only the year, is permitted. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
MedicalDevice.Comment | |
Definition | Comment about use or information on the medical device used. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MedicalDevice.Location | |
Definition | The healthcare organization where the use of the medical device was initiated or where the aid was implanted. |
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 |
|
MedicalDevice.HealthProfessional | |
Definition | The health professional involved in the indication for use of the medical device implant. |
Cardinality | 0...1 |
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 |
|
Example instances
MedicalDevice | |
---|---|
Product | -- |
Product.ProductId | (01)00810323008108(17)231005(21)6789UV0 (identification by GTIN) |
Product.ProductType | 360283003 - Auditory appliance (code by SNOMED CT) |
ProductDescription | TuneAmp auditory appliance |
AnatomicalLocation | |
Indication | -- |
Indication.Problem | Reference to Problem (Listeriosis) |
StartDate | 2022-05-01 |
EndDate | |
Comment | Might need replacement in the near future. |
Location | -- |
Location.HealthcareOrganization | Reference to HealthcareOrganization (GRAND HOPITAL DE CHARLEROI - SAINT-JOSEPH) |
HealthProfessional | Reference to HealthProfessional (Dr. E. Penninx, Dermatology) |
zib MedicalDevice-v3.3.1 difference
Concept | Category | Description |
---|---|---|
description | textual | Removed 'Evidence Base' section because of Dutch focus. |
Product.ProductId |
type | Replaced the CodeableConcept datatype with a string datatype as pre-adopt from a higher zib version ( MedicationDevice in prerelease 2022-1). |
Product.ProductId |
cardinality | Relaxed the cardinality from 0..1 to 0..* as multiple product identifications codes could be possible. |
Product.ProductId |
textual | Replaced definition of product identification codes to the Belgian context. |
Product.ProductType |
terminology | Loosened the binding strength from required to extensible (zib issue #1536). |
EndDate |
naming | Translated the concept to English as it was provided in Dutch (zib issue #1534). |
HealthProfessional |
textual | Replaced the term healthcare provider with health professional. |
Location |
textual | Replaced 'at which' with 'where'. |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
Product.ProductType | ProductType | required | https://fhir.healthdata.be/ValueSet/ProductType |