Gegenereerde narrative: StructureDefinition logical-device-use-statement Naam Markeringen Kard. Type Omschrijving & constraints logical-device-use-statement 0..* Element Logical Model: DeviceUseStatement Elementen gedefinieerd in ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension #xD; sourceProfile 0..1 uri source Profile #xD; targetProfile 0..1 uri target Profile #xD; sourceProfileElementUrl 0..* uri Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model. #xD; sourceProfileElementJson 0..* string Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape. #xD; targetProfileElementUrl 0..* uri Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model. #xD; targetProfileElementJson 0..* string Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape. #xD; profileSpecificData 0..* Extension Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload. #xD; routeProfileName 0..1 string Profile route name or concept label used by the source-target pair. #xD; sourceResourceType 1..1 code FHIR source resource type accepted on the source side. #xD; targetResourceType 1..1 code FHIR target resource type produced on the target side. #xD; identifier 0..* Identifier DeviceUseStatement identifiers. #xD; status 0..1 code Device use statement status. #xD; subject 0..1 Reference(Patient) Patient subject. #xD; device 0..1 Reference(Device) Device reference. #xD; timingPeriod 0..1 Period Period of device use. #xD; bodySite 0..1 CodeableConcept Body site associated with the device. #xD; note 0..* Annotation Notes about device use. #xD; deviceReference 0..1 Reference(Device) Medical device reference used by ACP MedicalDevice profiles. #xD; subjectReference 0..1 Reference(Patient) Patient subject of the device use statement. #xD; timing 0..1 Element Timing or period for device use, preserving the R4 timing choice. #xD; reasonCode 0..* CodeableConcept Reason codes associated with medical device use. #xD; convertedDeviceUseStatement 0..1 DeviceUseStatement Normalized R4 DeviceUseStatement payload before final target profile canonical normalization. #xD; Documentatie voor dit formaat
Logical intermediate model for DeviceUseStatement translation. It is source-family neutral and captures the R4 request/requester shape independent of the STU3 source.
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")])
Source profile used to populate this logical model.
Target profile intended for this logical model instance.
Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.
Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.
Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.
Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.
Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.
Profile route name or concept label used by the source-target pair.
FHIR source resource type accepted on the source side.
FHIR target resource type produced on the target side.
Medical device reference used by ACP MedicalDevice profiles.
Patient subject of the device use statement.
Timing or period for device use, preserving the R4 timing choice.
Reason codes associated with medical device use.
Normalized R4 DeviceUseStatement payload before final target profile canonical normalization.