Generated Narrative: StructureDefinition ext-R5-DeviceDefinition.correctiveAction Name Flags Card. Type Description & Constraints Extension 0..1 Extension(4.0.1) R5: Tracking of latest field safety corrective action (new) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:recall 1..1 Extension R5: Whether the corrective action was a recall (new) #xD; url 1..1 uri "recall" #xD; value[x] 1..1 boolean Whether the corrective action was a recall #xD; extension:scope 0..1 Extension R5: model | lot-numbers | serial-numbers (new) #xD; url 1..1 uri "scope" #xD; value[x] 0..1 code model | lot-numbers | serial-numbers Binding: R5DeviceCorrectiveactionscopeForR4 (0.1.0) (required): The type or scope of the corrective action. #xD; extension:period 1..1 Extension R5: Start and end dates of the corrective action (new) #xD; url 1..1 uri "period" #xD; value[x] 1..1 Period Start and end dates of the corrective action #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.correctiveAction" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: Tracking of latest field safety corrective action (new)
R5: `DeviceDefinition.correctiveAction` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `DeviceDefinition.correctiveAction` as defined in FHIR R5 in FHIR R4. The source element is defined as: `DeviceDefinition.correctiveAction` 0..1 `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5: `DeviceDefinition.correctiveAction` 0..1 `BackboneElement` Following are the generation technical comments: Element `DeviceDefinition.correctiveAction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.correctiveAction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
R5: Whether the corrective action was a recall (new)
R5: `DeviceDefinition.correctiveAction.recall` (new:boolean)
Element `DeviceDefinition.correctiveAction.recall` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.recall` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.recall` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'.
Element `DeviceDefinition.correctiveAction.recall` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.recall` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.recall` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.
Source 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.
Whether the corrective action was a recall
Whether the last corrective action known for this device was a recall.
When a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'.
R5: model | lot-numbers | serial-numbers (new)
R5: `DeviceDefinition.correctiveAction.scope` (new:code)
Element `DeviceDefinition.correctiveAction.scope` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.scope` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The scope of the corrective action - whether the action targeted all units of a given device model, or only a specific set of batches identified by lot numbers, or individually identified devices identified by the serial name.
The type or scope of the corrective action.
R5: Start and end dates of the corrective action (new)
R5: `DeviceDefinition.correctiveAction.period` (new:Period)
Element `DeviceDefinition.correctiveAction.period` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.period` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Start and end dates of the corrective action
Start and end dates of the corrective action.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).