Generated Narrative: StructureDefinition BeModelDeviceUseStatement Name Flags Card. Type Description & Constraints BeModelDeviceUseStatement 0..* Base DeviceUseStatement Logical Model #xD; identifier 0..* Identifier Identifier #xD; basedOn 0..* Reference() Based On #xD; status 1..1 code Status Binding: DeviceUseStatementStatus (required) #xD; patient 1..1 Reference(Patient) Patient #xD; derivedFrom 0..* Reference() Derived From #xD; timing[x] 0..1 Timing #xD; timingDateTime dateTime #xD; timingPeriod Period #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">timingTiming Timing #xD; recordedDate 1..1 dateTime Recorded Date #xD; source 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) Source #xD; device 1..1 Reference() Device #xD; reasonCode 0..* CodeableConcept Reason Code #xD; reasonReference 0..* Reference() Reason Reference #xD; bodySite 0..1 BackboneElement Body Site #xD; localisation 1..1 CodeableConcept Body Localisation Binding: Body Site (required) #xD; laterality 0..1 CodeableConcept Body Laterality Binding: Laterality (required) #xD; topography 0..1 CodeableConcept Body Topography Binding: https://www.ehealth.fgov.be/standards/fhir/terminology/ValueSet/be-vs-topography (required) #xD; note 0..* Annotation Note #xD; Documentation for this format
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)
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
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
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).
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
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'