Generated Narrative: StructureDefinition ext-R5-PlanDefinition.actor Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Actors within the plan (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:title 0..1 Extension R5: User-visible title (new) #xD; url 1..1 uri "title" #xD; value[x] 0..1 string User-visible title #xD; extension:description 0..1 Extension R5: Describes the actor (new) #xD; url 1..1 uri "description" #xD; value[x] 0..1 markdown Describes the actor #xD; extension:option 1..* Extension R5: Who or what can be this actor (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 Extension R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson (new) #xD; url 1..1 uri "type" #xD; value[x] 0..1 code careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson Binding: R5ActionParticipantTypeForR4 (0.1.0) (required): The type of participant in the activity. #xD; extension:typeCanonical 0..1 Extension R5: Who or what can participate (new) #xD; url 1..1 uri "typeCanonical" #xD; value[x] 0..1 canonical(Cross-version Profile for R5.CapabilityStatement for use in FHIR R4(0.1.0) | CapabilityStatement) Who or what can participate #xD; extension:typeReference 0..1 Extension R5: Who or what can participate (new) #xD; url 1..1 uri "typeReference" #xD; value[x] 0..1 Reference(Cross-version Profile for R5.CareTeam for use in FHIR R4(0.1.0) | CareTeam | Cross-version Profile for R5.Device for use in FHIR R4(0.1.0) | Device | Cross-version Profile for R5.DeviceDefinition for use in FHIR R4(0.1.0) | DeviceDefinition | Cross-version Profile for R5.Endpoint for use in FHIR R4(0.1.0) | Endpoint | Cross-version Profile for R5.Group for use in FHIR R4(0.1.0) | Group | Cross-version Profile for R5.HealthcareService for use in FHIR R4(0.1.0) | HealthcareService | Cross-version Profile for R5.Location for use in FHIR R4(0.1.0) | Location | 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.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.RelatedPerson for use in FHIR R4(0.1.0) | RelatedPerson) Who or what can participate #xD; extension:role 0..1 Extension R5: E.g. Nurse, Surgeon, Parent (new) #xD; url 1..1 uri "role" #xD; value[x] 0..1 CodeableConcept E.g. Nurse, Surgeon, Parent #xD; url 1..1 uri "option" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.actor" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: `PlanDefinition.actor` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `PlanDefinition.actor` as defined in FHIR R5 in FHIR R4. The source element is defined as: `PlanDefinition.actor` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5: `PlanDefinition.actor` 0..* `BackboneElement` Following are the generation technical comments: Element `PlanDefinition.actor` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `PlanDefinition.actor` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor` 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: `PlanDefinition.actor.title` (new:string)
Element `PlanDefinition.actor.title` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.title` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.title` 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.
R5: `PlanDefinition.actor.description` (new:markdown)
Element `PlanDefinition.actor.description` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.description` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
A description of how the actor fits into the overall actions of the plan definition.
R5: `PlanDefinition.actor.option` (new:BackboneElement)
Element `PlanDefinition.actor.option` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.option` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson (new)
R5: `PlanDefinition.actor.option.type` (new:code)
Element `PlanDefinition.actor.option.type` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.type` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson
The type of participant in the activity.
R5: `PlanDefinition.actor.option.typeCanonical` (new:canonical(CapabilityStatement))
Element `PlanDefinition.actor.option.typeCanonical` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.typeCanonical` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.typeCanonical` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
R5: `PlanDefinition.actor.option.typeReference` (new:Reference(CareTeam,Device,DeviceDefinition,Endpoint,Group,HealthcareService,Location,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))
Element `PlanDefinition.actor.option.typeReference` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.typeReference` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.typeReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).
Element `PlanDefinition.actor.option.typeReference` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.typeReference` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.typeReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).
R5: `PlanDefinition.actor.option.role` (new:CodeableConcept)
Element `PlanDefinition.actor.option.role` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.role` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The role the participant should play in performing the described 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).