NICE-FeedingTubeSystem
Description
This profile is for submitting whether the patient received enteral nutrition.
Click here to go to the NICE-FeedingTubeSystem Simplifier page
NICE data dictionary links
| Capacity |
|---|
| Nutrition - enteral |
Source
This profile is used to submit feeding tube related information to the Dutch National Intensive Care Evaluation (NICE). It was derived from the Nictiz Health and Care Information Model (HCIM; Dutch: Zorginformatiebouwsteen or ZIB) FeedingTubeSystem, 2017 release version 3.1
| DeviceUseStatement | I | DeviceUseStatement | Element idDeviceUseStatement FeedingTubeSystem Alternate namesMedischHulpmiddel, SondeSysteem DefinitionFeedingTube describes the presence of a feeding tube. If this is the case, the date of placement and insertion location can be described in addition to the type of feeding tube. Furthermore, it offers the option to record identification information of the feeding tube if desired. The HCIM FeedingTubeSystem is represented in a DeviceUseStatement that has additional elements not covered in the 'root' HCIM such as the date of placement and insertion locations. The reference (NL-CM:10.3.2) toward another DeviceUseStatement to describe the presense of a feeding tube is ommited. This should be described within this DeviceUseStatement, which has a mandatory reference to a Device profile to capture the FeedingTube ProductType.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDeviceUseStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
|
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDeviceUseStatement.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceUseStatement.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceUseStatement.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language. Common Languages (extensible)Constraints
| |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDeviceUseStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDeviceUseStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
| extension | I | 1..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| HealthcareProvider | I | 0..1 | Extension(Reference(nl-core-organization)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider HealthcareProvider Alternate namesextensions, user content, Zorgaanbieder DefinitionThe healthcare provider at which use of the medical aid was initiated or where the aid was implanted. 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. Extension(Reference(nl-core-organization)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Organization Constraints
|
| HealthProfessional | I | 0..1 | Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional HealthProfessional Alternate namesextensions, user content, Zorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical aid implant. 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. Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner
| |
| valueReference | 0..1 | Reference(nl-core-practitioner | nl-core-practitionerrole) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.value[x]:valueReference HealthProfessional Alternate namesZorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical device implant. Reference(nl-core-practitioner | nl-core-practitionerrole) Constraints
| |
| reasonReference | I | 0..* | Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Why was DeviceUseStatement performed? Alternate namesextensions, user content DefinitionAnother resource whose existence justifies this DeviceUseStatement. This extension is backported from the offical HL7 DeviceUseStatement specification in FHIR R4. Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/deviceUseStatement-reasonReferenceSTU3 Constraints
|
| FeedingTubeLength | I | 0..* | Extension(Quantity) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength FeedingTubeLength Alternate namesextensions, user content, SondeLengte DefinitionThe input length of the feeding tube in cm for the patient in question as determined by formulas based on for example the NEX i.e. nosepoint-earlobe-xyphoid distance (adults) or body length (children). 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. http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-FeedingTubeLength Constraints
|
| EnteralNutrition | I | 0..* | Extension(Reference(HCIM MedicationAdministration)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition EnteralNutrition Alternate namesextensions, user content, SondeVoeding DefinitionThe description of the fluid administered through the feeding tube and the dose administered, as given in the medication prescription. Though most cases involve food being administered through the feeding tube, medication is often administered through these tubes as well. 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. Extension(Reference(HCIM MedicationAdministration)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-EnteralNutrition Constraints
|
| MedicalDevice | I | 0..0 | Extension(Reference(HCIM MedicalDevice)) | Element idDeviceUseStatement.extension:MedicalDevice MedicalDevice Alternate namesextensions, user content, MedischHulpmiddel DefinitionA description of aids required to use the feeding tube, such as an enteral feeding pump or a vacuum pump in the event of draining fluid. 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. Extension(Reference(HCIM MedicalDevice)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice Constraints
|
| Verified | S I | 1..1 | Extension(CodeableConcept) | Element idDeviceUseStatement.extension:Verified Is the instance validated by a medical professional? Alternate namesextensions, user content DefinitionExtension that is used to indicate whether the entire instance has been validated. Every instance shall be validated by a hospital member / datamanager. However, this is not always feasible in case of automated submission of NICE data elements. This extensions shall be used to indicate the validation status of the instance. 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. https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-Verified-2022Q1 Constraints
|
| HealthcareProvider | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| HealthProfessional | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| reasonReference | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| FeedingTubeLength | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| EnteralNutrition | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.identifier External identifier for this record DefinitionAn external identifier for this statement such as an IRI.
| |
| status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceUseStatement.status validated (completed) DefinitionA code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error). This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid. A coded concept indicating the current status of a the Device Usage DeviceUseStatementStatus (required)Constraints
completed
|
| subject | I | 1..1 | Reference(NICE-Patient) | Element idDeviceUseStatement.subject Patient using device DefinitionThe patient who used the device. 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.
|
| whenUsed | S I | 0..1 | Period | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed Time range defined by start and end date/time Alternate namesTijdsduur gedefinieerd door start- en einddatum/tijd DefinitionThe time period over which the device was used. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| start | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.start StartDate Alternate namesBeginDatum DefinitionThe start date of the first use or implant of the medical aid. A ‘vague’ date, such as only the year, is permitted. If the low element is missing, the meaning is that the low boundary is not known.
|
| end | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
| timing[x] | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.timing[x] How often the device was used DefinitionHow often the device was used.
| ||
| timingTiming | Timing | There are no (further) constraints on this element Data type | ||
| timingPeriod | Period | There are no (further) constraints on this element Data type | ||
| timingDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| recordedOn | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.recordedOn When statement was recorded DefinitionThe time at which the statement was made/recorded.
| |
| source | I | 0..1 | Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) | There are no (further) constraints on this element Element idDeviceUseStatement.source Who made the statement DefinitionWho reported the device was being used by the patient. 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. Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| practitionerRole | I | 0..1 | Extension(Reference(nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension:practitionerRole Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(Reference(nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/practitionerrole-reference Constraints
|
| reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
| identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.source.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
|
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
| device | I | 1..1 | Reference(HCIM FeedingTubeSystem Product) | There are no (further) constraints on this element Element idDeviceUseStatement.device Reference to device used DefinitionThe details of the device used. Reference to a derived MedicalDevice Product (Device) profile to capture the ProductType (NL-CM:10.1.3). Reference(HCIM FeedingTubeSystem Product) Constraints
|
| indication | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceUseStatement.indication Why device was used DefinitionReason or justification for the use of the device. 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.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| indication_Problem | I | 0..* | Extension(Reference(HCIM Problem)) | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension:indication_Problem Indication-Probleem Alternate namesextensions, user content, Indicatie DefinitionThe medical reason for use of the medical device. 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. Extension(Reference(HCIM Problem)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Problem Constraints
|
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.indication.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| bodySite | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite AnatomicalLocation Alternate namesAnatomischeLocatie DefinitionPatient’s anatomical location of the medical device used. Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/body-site-instance. 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. Patient’s anatomical location of the medical aid used. HulpmiddelAnatomischeLocatieCodelijst (extensible)Constraints
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| Laterality | I | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality Laterality Alternate namesextensions, user content DefinitionLaterality adds information about body side to the anatomic location, e.g. left 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. http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier
| |
| valueCodeableConcept | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.value[x]:valueCodeableConcept BodySite qualifier DefinitionQualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. MedicalDeviceLateralityCodelist MedischHulpmiddelLateraliteitCodelijst (extensible)Constraints
| |
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idDeviceUseStatement.note Addition details (comments, instructions) DefinitionDetails about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | There are no (further) constraints on this element Data type | ||
| authorReference | Reference(Practitioner | Patient | RelatedPerson) | There are no (further) constraints on this element Data type | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.text Comment Alternate namesToelichting DefinitionA comment on the feeding tube. Note that FHIR strings may not exceed 1MB in size
|
| DeviceUseStatement | I | DeviceUseStatement | Element idDeviceUseStatement FeedingTubeSystem Alternate namesMedischHulpmiddel, SondeSysteem DefinitionFeedingTube describes the presence of a feeding tube. If this is the case, the date of placement and insertion location can be described in addition to the type of feeding tube. Furthermore, it offers the option to record identification information of the feeding tube if desired. The HCIM FeedingTubeSystem is represented in a DeviceUseStatement that has additional elements not covered in the 'root' HCIM such as the date of placement and insertion locations. The reference (NL-CM:10.3.2) toward another DeviceUseStatement to describe the presense of a feeding tube is ommited. This should be described within this DeviceUseStatement, which has a mandatory reference to a Device profile to capture the FeedingTube ProductType.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDeviceUseStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
|
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDeviceUseStatement.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceUseStatement.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceUseStatement.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language. Common Languages (extensible)Constraints
| |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDeviceUseStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDeviceUseStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
| extension | I | 1..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| HealthcareProvider | I | 0..1 | Extension(Reference(nl-core-organization)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider HealthcareProvider Alternate namesextensions, user content, Zorgaanbieder DefinitionThe healthcare provider at which use of the medical aid was initiated or where the aid was implanted. 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. Extension(Reference(nl-core-organization)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Organization Constraints
|
| HealthProfessional | I | 0..1 | Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional HealthProfessional Alternate namesextensions, user content, Zorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical aid implant. 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. Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner
| |
| valueReference | 0..1 | Reference(nl-core-practitioner | nl-core-practitionerrole) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.value[x]:valueReference HealthProfessional Alternate namesZorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical device implant. Reference(nl-core-practitioner | nl-core-practitionerrole) Constraints
| |
| reasonReference | I | 0..* | Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Why was DeviceUseStatement performed? Alternate namesextensions, user content DefinitionAnother resource whose existence justifies this DeviceUseStatement. This extension is backported from the offical HL7 DeviceUseStatement specification in FHIR R4. Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/deviceUseStatement-reasonReferenceSTU3 Constraints
|
| FeedingTubeLength | I | 0..* | Extension(Quantity) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength FeedingTubeLength Alternate namesextensions, user content, SondeLengte DefinitionThe input length of the feeding tube in cm for the patient in question as determined by formulas based on for example the NEX i.e. nosepoint-earlobe-xyphoid distance (adults) or body length (children). 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. http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-FeedingTubeLength Constraints
|
| EnteralNutrition | I | 0..* | Extension(Reference(HCIM MedicationAdministration)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition EnteralNutrition Alternate namesextensions, user content, SondeVoeding DefinitionThe description of the fluid administered through the feeding tube and the dose administered, as given in the medication prescription. Though most cases involve food being administered through the feeding tube, medication is often administered through these tubes as well. 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. Extension(Reference(HCIM MedicationAdministration)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-EnteralNutrition Constraints
|
| MedicalDevice | I | 0..0 | Extension(Reference(HCIM MedicalDevice)) | Element idDeviceUseStatement.extension:MedicalDevice MedicalDevice Alternate namesextensions, user content, MedischHulpmiddel DefinitionA description of aids required to use the feeding tube, such as an enteral feeding pump or a vacuum pump in the event of draining fluid. 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. Extension(Reference(HCIM MedicalDevice)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice Constraints
|
| Verified | S I | 1..1 | Extension(CodeableConcept) | Element idDeviceUseStatement.extension:Verified Is the instance validated by a medical professional? Alternate namesextensions, user content DefinitionExtension that is used to indicate whether the entire instance has been validated. Every instance shall be validated by a hospital member / datamanager. However, this is not always feasible in case of automated submission of NICE data elements. This extensions shall be used to indicate the validation status of the instance. 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. https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-Verified-2022Q1 Constraints
|
| HealthcareProvider | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| HealthProfessional | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| reasonReference | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| FeedingTubeLength | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| EnteralNutrition | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.identifier External identifier for this record DefinitionAn external identifier for this statement such as an IRI.
| |
| status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceUseStatement.status validated (completed) DefinitionA code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error). This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid. A coded concept indicating the current status of a the Device Usage DeviceUseStatementStatus (required)Constraints
completed
|
| subject | I | 1..1 | Reference(NICE-Patient) | Element idDeviceUseStatement.subject Patient using device DefinitionThe patient who used the device. 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.
|
| whenUsed | S I | 0..1 | Period | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed Time range defined by start and end date/time Alternate namesTijdsduur gedefinieerd door start- en einddatum/tijd DefinitionThe time period over which the device was used. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| start | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.start StartDate Alternate namesBeginDatum DefinitionThe start date of the first use or implant of the medical aid. A ‘vague’ date, such as only the year, is permitted. If the low element is missing, the meaning is that the low boundary is not known.
|
| end | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
| timing[x] | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.timing[x] How often the device was used DefinitionHow often the device was used.
| ||
| timingTiming | Timing | There are no (further) constraints on this element Data type | ||
| timingPeriod | Period | There are no (further) constraints on this element Data type | ||
| timingDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| recordedOn | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.recordedOn When statement was recorded DefinitionThe time at which the statement was made/recorded.
| |
| source | I | 0..1 | Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) | There are no (further) constraints on this element Element idDeviceUseStatement.source Who made the statement DefinitionWho reported the device was being used by the patient. 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. Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| practitionerRole | I | 0..1 | Extension(Reference(nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension:practitionerRole Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(Reference(nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/practitionerrole-reference Constraints
|
| reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
| identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.source.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
|
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
| device | I | 1..1 | Reference(HCIM FeedingTubeSystem Product) | There are no (further) constraints on this element Element idDeviceUseStatement.device Reference to device used DefinitionThe details of the device used. Reference to a derived MedicalDevice Product (Device) profile to capture the ProductType (NL-CM:10.1.3). Reference(HCIM FeedingTubeSystem Product) Constraints
|
| indication | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceUseStatement.indication Why device was used DefinitionReason or justification for the use of the device. 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.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| indication_Problem | I | 0..* | Extension(Reference(HCIM Problem)) | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension:indication_Problem Indication-Probleem Alternate namesextensions, user content, Indicatie DefinitionThe medical reason for use of the medical device. 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. Extension(Reference(HCIM Problem)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Problem Constraints
|
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.indication.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| bodySite | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite AnatomicalLocation Alternate namesAnatomischeLocatie DefinitionPatient’s anatomical location of the medical device used. Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/body-site-instance. 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. Patient’s anatomical location of the medical aid used. HulpmiddelAnatomischeLocatieCodelijst (extensible)Constraints
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| Laterality | I | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality Laterality Alternate namesextensions, user content DefinitionLaterality adds information about body side to the anatomic location, e.g. left 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. http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier
| |
| valueCodeableConcept | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.value[x]:valueCodeableConcept BodySite qualifier DefinitionQualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. MedicalDeviceLateralityCodelist MedischHulpmiddelLateraliteitCodelijst (extensible)Constraints
| |
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idDeviceUseStatement.note Addition details (comments, instructions) DefinitionDetails about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | There are no (further) constraints on this element Data type | ||
| authorReference | Reference(Practitioner | Patient | RelatedPerson) | There are no (further) constraints on this element Data type | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.text Comment Alternate namesToelichting DefinitionA comment on the feeding tube. Note that FHIR strings may not exceed 1MB in size
|
| DeviceUseStatement | I | DeviceUseStatement | Element idDeviceUseStatement FeedingTubeSystem Alternate namesMedischHulpmiddel, SondeSysteem DefinitionFeedingTube describes the presence of a feeding tube. If this is the case, the date of placement and insertion location can be described in addition to the type of feeding tube. Furthermore, it offers the option to record identification information of the feeding tube if desired. The HCIM FeedingTubeSystem is represented in a DeviceUseStatement that has additional elements not covered in the 'root' HCIM such as the date of placement and insertion locations. The reference (NL-CM:10.3.2) toward another DeviceUseStatement to describe the presense of a feeding tube is ommited. This should be described within this DeviceUseStatement, which has a mandatory reference to a Device profile to capture the FeedingTube ProductType.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDeviceUseStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
|
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDeviceUseStatement.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceUseStatement.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceUseStatement.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language. Common Languages (extensible)Constraints
| |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDeviceUseStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDeviceUseStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
| extension | I | 1..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| HealthcareProvider | I | 0..1 | Extension(Reference(nl-core-organization)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider HealthcareProvider Alternate namesextensions, user content, Zorgaanbieder DefinitionThe healthcare provider at which use of the medical aid was initiated or where the aid was implanted. 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. Extension(Reference(nl-core-organization)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Organization Constraints
|
| HealthProfessional | I | 0..1 | Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional HealthProfessional Alternate namesextensions, user content, Zorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical aid implant. 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. Extension(Reference(nl-core-practitioner | nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Practitioner
| |
| valueReference | 0..1 | Reference(nl-core-practitioner | nl-core-practitionerrole) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional.value[x]:valueReference HealthProfessional Alternate namesZorgverlener DefinitionThe healthcare provider involved in the indication for use of the medical device implant. Reference(nl-core-practitioner | nl-core-practitionerrole) Constraints
| |
| reasonReference | I | 0..* | Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Why was DeviceUseStatement performed? Alternate namesextensions, user content DefinitionAnother resource whose existence justifies this DeviceUseStatement. This extension is backported from the offical HL7 DeviceUseStatement specification in FHIR R4. Extension(Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/deviceUseStatement-reasonReferenceSTU3 Constraints
|
| FeedingTubeLength | I | 0..* | Extension(Quantity) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength FeedingTubeLength Alternate namesextensions, user content, SondeLengte DefinitionThe input length of the feeding tube in cm for the patient in question as determined by formulas based on for example the NEX i.e. nosepoint-earlobe-xyphoid distance (adults) or body length (children). 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. http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-FeedingTubeLength Constraints
|
| EnteralNutrition | I | 0..* | Extension(Reference(HCIM MedicationAdministration)) | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition EnteralNutrition Alternate namesextensions, user content, SondeVoeding DefinitionThe description of the fluid administered through the feeding tube and the dose administered, as given in the medication prescription. Though most cases involve food being administered through the feeding tube, medication is often administered through these tubes as well. 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. Extension(Reference(HCIM MedicationAdministration)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-EnteralNutrition Constraints
|
| MedicalDevice | I | 0..0 | Extension(Reference(HCIM MedicalDevice)) | Element idDeviceUseStatement.extension:MedicalDevice MedicalDevice Alternate namesextensions, user content, MedischHulpmiddel DefinitionA description of aids required to use the feeding tube, such as an enteral feeding pump or a vacuum pump in the event of draining fluid. 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. Extension(Reference(HCIM MedicalDevice)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/extension-medicaldevice Constraints
|
| Verified | S I | 1..1 | Extension(CodeableConcept) | Element idDeviceUseStatement.extension:Verified Is the instance validated by a medical professional? Alternate namesextensions, user content DefinitionExtension that is used to indicate whether the entire instance has been validated. Every instance shall be validated by a hospital member / datamanager. However, this is not always feasible in case of automated submission of NICE data elements. This extensions shall be used to indicate the validation status of the instance. 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. https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-Verified-2022Q1 Constraints
|
| HealthcareProvider | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthcareProvider Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| HealthProfessional | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:HealthProfessional Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| reasonReference | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:reasonReference Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| FeedingTubeLength | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:FeedingTubeLength Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| EnteralNutrition | I | 0..0 | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.extension:EnteralNutrition Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
|
| modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.identifier External identifier for this record DefinitionAn external identifier for this statement such as an IRI.
| |
| status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceUseStatement.status validated (completed) DefinitionA code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error). This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid. A coded concept indicating the current status of a the Device Usage DeviceUseStatementStatus (required)Constraints
completed
|
| subject | I | 1..1 | Reference(NICE-Patient) | Element idDeviceUseStatement.subject Patient using device DefinitionThe patient who used the device. 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.
|
| whenUsed | S I | 0..1 | Period | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed Time range defined by start and end date/time Alternate namesTijdsduur gedefinieerd door start- en einddatum/tijd DefinitionThe time period over which the device was used. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| start | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.start StartDate Alternate namesBeginDatum DefinitionThe start date of the first use or implant of the medical aid. A ‘vague’ date, such as only the year, is permitted. If the low element is missing, the meaning is that the low boundary is not known.
|
| end | S Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.whenUsed.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
| timing[x] | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.timing[x] How often the device was used DefinitionHow often the device was used.
| ||
| timingTiming | Timing | There are no (further) constraints on this element Data type | ||
| timingPeriod | Period | There are no (further) constraints on this element Data type | ||
| timingDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| recordedOn | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.recordedOn When statement was recorded DefinitionThe time at which the statement was made/recorded.
| |
| source | I | 0..1 | Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) | There are no (further) constraints on this element Element idDeviceUseStatement.source Who made the statement DefinitionWho reported the device was being used by the patient. 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. Reference(nl-core-patient | nl-core-practitioner | nl-core-relatedperson) Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| practitionerRole | I | 0..1 | Extension(Reference(nl-core-practitionerrole)) | There are no (further) constraints on this element Element idDeviceUseStatement.source.extension:practitionerRole Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(Reference(nl-core-practitionerrole)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/practitionerrole-reference Constraints
|
| reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
| identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceUseStatement.source.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
|
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.source.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
| device | I | 1..1 | Reference(HCIM FeedingTubeSystem Product) | There are no (further) constraints on this element Element idDeviceUseStatement.device Reference to device used DefinitionThe details of the device used. Reference to a derived MedicalDevice Product (Device) profile to capture the ProductType (NL-CM:10.1.3). Reference(HCIM FeedingTubeSystem Product) Constraints
|
| indication | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceUseStatement.indication Why device was used DefinitionReason or justification for the use of the device. 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.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| indication_Problem | I | 0..* | Extension(Reference(HCIM Problem)) | There are no (further) constraints on this element Element idDeviceUseStatement.indication.extension:indication_Problem Indication-Probleem Alternate namesextensions, user content, Indicatie DefinitionThe medical reason for use of the medical device. 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. Extension(Reference(HCIM Problem)) Extension URLhttp://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice-Problem Constraints
|
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.indication.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.indication.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| bodySite | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite AnatomicalLocation Alternate namesAnatomischeLocatie DefinitionPatient’s anatomical location of the medical device used. Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/body-site-instance. 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. Patient’s anatomical location of the medical aid used. HulpmiddelAnatomischeLocatieCodelijst (extensible)Constraints
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| Laterality | I | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality Laterality Alternate namesextensions, user content DefinitionLaterality adds information about body side to the anatomic location, e.g. left 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. http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
http://nictiz.nl/fhir/StructureDefinition/BodySite-Qualifier
| |
| valueCodeableConcept | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.extension:Laterality.value[x]:valueCodeableConcept BodySite qualifier DefinitionQualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. MedicalDeviceLateralityCodelist MedischHulpmiddelLateraliteitCodelijst (extensible)Constraints
| |
| coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.bodySite.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idDeviceUseStatement.note Addition details (comments, instructions) DefinitionDetails about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceUseStatement.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDeviceUseStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | There are no (further) constraints on this element Data type | ||
| authorReference | Reference(Practitioner | Patient | RelatedPerson) | There are no (further) constraints on this element Data type | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceUseStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idDeviceUseStatement.note.text Comment Alternate namesToelichting DefinitionA comment on the feeding tube. Note that FHIR strings may not exceed 1MB in size
|
Mapping FHIR profile NICE data dictionary
| Path | identity | map | comment |
|---|---|---|---|
| DeviceUseStatement | NICE-Datadictionary-Capacity | https://www.stichting-nice.nl/dd/#612 | Nutrition - enteral |
{ "resourceType": "DeviceUseStatement", "id": "NICE-FeedingTubeSystem-Example-01", "meta": { "profile": [ "https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-FeedingTubeSystem-2022Q1" ] }, "text": { --- We have skipped the narrative for better readability of the resource --- }, "extension": [ { "url": "https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-Verified-2022Q1", "valueCodeableConcept": { "coding": [ { "system": "http://terminology.hl7.org/ValueSet/v2-0532", "code": "Y", "display": "Yes" } ] } } ], "status": "completed", "subject": { "reference": "Patient/NICE-Patient-01", "display": "P. Petersen" }, "whenUsed": { "start": "2022-01-09T15:43:00+02:00", "end": "2022-01-10T18:01:00+02:00" } }
<DeviceUseStatement xmlns="http://hl7.org/fhir"> <id value="NICE-FeedingTubeSystem-Example-01" /> <meta> <profile value="https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-FeedingTubeSystem-2022Q1" /> </meta> <text> <status /> --- We have skipped the narrative for better readability of the resource --- </text> <extension url="https://fhir.stichting-nice.nl/STU3/StructureDefinition/NICE-Verified-2022Q1"> <valueCodeableConcept> <coding> <system value="http://terminology.hl7.org/ValueSet/v2-0532" /> <code value="Y" /> <display value="Yes" /> </coding> </valueCodeableConcept> </extension> <status value="completed" /> <subject> <reference value="Patient/NICE-Patient-01" /> <display value="P. Petersen" /> </subject> <whenUsed> <start value="2022-01-09T15:43:00+02:00" /> <end value="2022-01-10T18:01:00+02:00" /> </whenUsed> </DeviceUseStatement>