Generated Narrative: StructureDefinition ext-R3-Contract.ter.agent Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) STU3: Contract Term Agent List (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:actor 1..1 Extension STU3: Contract Term Agent Subject (new) #xD; url 1..1 uri "actor" #xD; value[x] 1..1 Reference(Cross-version Profile for STU3.Contract for use in FHIR R4(0.1.0) | Contract | Cross-version Profile for STU3.Device for use in FHIR R4(0.1.0) | Device | Cross-version Profile for STU3.Group for use in FHIR R4(0.1.0) | Group | Cross-version Profile for STU3.Location for use in FHIR R4(0.1.0) | Location | Cross-version Profile for STU3.Organization for use in FHIR R4(0.1.0) | Organization | Cross-version Profile for STU3.Patient for use in FHIR R4(0.1.0) | Patient | Cross-version Profile for STU3.Practitioner for use in FHIR R4(0.1.0) | Practitioner | Cross-version Profile for STU3.RelatedPerson for use in FHIR R4(0.1.0) | RelatedPerson | Cross-version Profile for STU3.Substance for use in FHIR R4(0.1.0) | Substance) Contract Term Agent Subject #xD; extension:role 0..* Extension STU3: Type of the Contract Term Agent (new) #xD; url 1..1 uri "role" #xD; value[x] 0..1 CodeableConcept Type of the Contract Term Agent Binding: ContractActorRoleCodes (example): Detailed codes for the contract actor role. #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-Contract.term.agent" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: `Contract.term.agent` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `Contract.term.agent` as defined in FHIR STU3 in FHIR R4. The source element is defined as: `Contract.term.agent` 0..* `BackboneElement` Following are the generation technical comments: Element `Contract.term.agent` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.agent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Contract.term.agent` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.agent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event.
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")])
STU3: `Contract.term.agent.actor` (new:Reference(Contract,Device,Group,Location,Organization,Patient,Practitioner,RelatedPerson,Substance))
Element `Contract.term.agent.actor` is part of an existing definition because parent element `Contract.term.agent` requires a cross-version extension. Element `Contract.term.agent.actor` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.agent.actor` 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.
The agent assigned a role in this Contract Provision.
STU3: Type of the Contract Term Agent (new)
STU3: `Contract.term.agent.role` (new:CodeableConcept)
Element `Contract.term.agent.role` is part of an existing definition because parent element `Contract.term.agent` requires a cross-version extension. Element `Contract.term.agent.role` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.agent.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Role played by the agent assigned this role in the execution of this Contract Provision.
Detailed codes for the contract actor role.
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).