Generated Narrative: StructureDefinition ext-R5-DeviceDispense.performer Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Who performed event (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:function 0..1 Extension R5: Who performed the dispense and what they did (new) #xD; url 1..1 uri "function" #xD; value[x] 0..1 CodeableConcept Who performed the dispense and what they did #xD; extension:actor 1..1 Extension R5: Individual who was performing (new) #xD; url 1..1 uri "actor" #xD; value[x] 1..1 Reference(Cross-version Profile for R5.Practitioner for use in FHIR R4(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR R4(0.1.0) | PractitionerRole | Cross-version Profile for R5.Organization for use in FHIR R4(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR R4(0.1.0) | Patient | Cross-version Profile for R5.Device for use in FHIR R4(0.1.0) | Device | Cross-version Profile for R5.RelatedPerson for use in FHIR R4(0.1.0) | RelatedPerson | Cross-version Profile for R5.CareTeam for use in FHIR R4(0.1.0) | CareTeam) Individual who was performing #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.performer" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: `DeviceDispense.performer` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `DeviceDispense.performer` as defined in FHIR R5 in FHIR R4. The source element is defined as: `DeviceDispense.performer` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5 `DeviceDispense.performer` 0..* `BackboneElement` Following are the generation technical comments: Element `DeviceDispense.performer` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `DeviceDispense.performer` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer` 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: Who performed the dispense and what they did (new)
R5: `DeviceDispense.performer.function` (new:CodeableConcept)
Element `DeviceDispense.performer.function` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension. Element `DeviceDispense.performer.function` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer.function` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Allows disambiguation of the types of involvement of different performers. Element `DeviceDispense.performer.function` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension. Element `DeviceDispense.performer.function` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer.function` 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.
Who performed the dispense and what they did
Distinguishes the type of performer in the dispense. For example, date enterer, packager, final checker.
R5: `DeviceDispense.performer.actor` (new:Reference(Practitioner,PractitionerRole,Organization,Patient,Device,RelatedPerson,CareTeam))
Element `DeviceDispense.performer.actor` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension. Element `DeviceDispense.performer.actor` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the device.
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).