Logical model for recording the use of a medical device by a patient

Unique ID of this device use registration, assigned by the system that creates the DeviceUseStatement

Reference to a request or plan on which this use is based, e.g. a ServiceRequest or prescription

Status of the registration (active, completed, entered-in-error, intended, stopped, on-hold)

The patient who uses the medical device

Extra information on which this registration is based, e.g. a prior Procedure or Observation

Description of how often or when the device is used, e.g. every night between 22:00 and 07:00

Date and time when the registration was entered

Who created the registration, e.g. a nurse recording the use

The device being used, e.g. reference to Device 'Insulin pump SN12345'

Reason why the device is used - can be a condition (problem), procedure or observation code

Reference to a clinical source for the reason, e.g. a diagnosis in a problem resource

The anatomical location where the device is used or implanted

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Specific location on the body, e.g. left hip

Laterality of the body site where the device is used/implanted (right, left, both)

Relative position of the device on the body (e.g., upper/lower, medial/lateral, internal/external)

Remarks or additional instructions, e.g. 'Patient reports irritation around the sensor'

Logical model for recording the use of a medical device by a patient

Unique ID of this device use registration, assigned by the system that creates the DeviceUseStatement

Reference to a request or plan on which this use is based, e.g. a ServiceRequest or prescription

Status of the registration (active, completed, entered-in-error, intended, stopped, on-hold)

The patient who uses the medical device

Extra information on which this registration is based, e.g. a prior Procedure or Observation

Description of how often or when the device is used, e.g. every night between 22:00 and 07:00

Date and time when the registration was entered

Who created the registration, e.g. a nurse recording the use

The device being used, e.g. reference to Device 'Insulin pump SN12345'

Reason why the device is used - can be a condition (problem), procedure or observation code

Reference to a clinical source for the reason, e.g. a diagnosis in a problem resource

The anatomical location where the device is used or implanted

Specific location on the body, e.g. left hip

Laterality of the body site where the device is used/implanted (right, left, both)

Relative position of the device on the body (e.g., upper/lower, medial/lateral, internal/external)

Remarks or additional instructions, e.g. 'Patient reports irritation around the sensor'

Logical model for recording the use of a medical device by a patient

Unique ID of this device use registration, assigned by the system that creates the DeviceUseStatement

Reference to a request or plan on which this use is based, e.g. a ServiceRequest or prescription

Status of the registration (active, completed, entered-in-error, intended, stopped, on-hold)

The patient who uses the medical device

Extra information on which this registration is based, e.g. a prior Procedure or Observation

Description of how often or when the device is used, e.g. every night between 22:00 and 07:00

Date and time when the registration was entered

Who created the registration, e.g. a nurse recording the use

The device being used, e.g. reference to Device 'Insulin pump SN12345'

Reason why the device is used - can be a condition (problem), procedure or observation code

Reference to a clinical source for the reason, e.g. a diagnosis in a problem resource

The anatomical location where the device is used or implanted

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Specific location on the body, e.g. left hip

Laterality of the body site where the device is used/implanted (right, left, both)

Relative position of the device on the body (e.g., upper/lower, medial/lateral, internal/external)

Remarks or additional instructions, e.g. 'Patient reports irritation around the sensor'