Generated Narrative: StructureDefinition ext-R3-Task.meta Name Flags Card. Type Description & Constraints Extension 0..1 Extension(4.3.0) STU3: meta additional types #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:_datatype 1..1 Extension DataType slice for a FHIR STU3 `Meta` value #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/_datatype" #xD; value[x] 1..1 string Value of extension Fixed Value: Meta #xD; extension:versionId 0..1 Extension STU3: versionId #xD; url 1..1 uri "versionId" #xD; value[x] 0..1 id Version specific identifier #xD; extension:lastUpdated 0..1 Extension STU3: lastUpdated #xD; url 1..1 uri "lastUpdated" #xD; value[x] 0..1 instant When the resource version last changed #xD; extension:profile 0..* Extension STU3: profile #xD; url 1..1 uri "profile" #xD; value[x] 0..1 uri Profiles this resource claims to conform to #xD; extension:security 0..* Extension STU3: security #xD; url 1..1 uri "security" #xD; value[x] 0..1 Coding Security Labels applied to this resource Binding: R3SecurityLabelsForR4B (0.1.0) (extensible): Security Labels from the Healthcare Privacy and Security Classification System. #xD; extension:tag 0..* Extension STU3: tag #xD; url 1..1 uri "tag" #xD; value[x] 0..1 Coding Tags applied to this resource Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones" #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-Task.meta" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: `Task.meta` additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)
This extension is part of the cross-version definitions generated to enable use of the element `Task.meta` as defined in FHIR STU3 in FHIR R4B. The source element is defined as: `Task.meta` 0..1 `Meta` Across FHIR versions, the element set has been mapped as: * STU3: `Task.meta` 0..1 `Meta` * R4: `Task.meta` 0..1 `Meta` * R4B: `Task.meta` 0..1 `Meta` Following are the generation technical comments: Element `Task.meta` is mapped to FHIR R4B element `Task.meta` as `SourceIsBroaderThanTarget`. The mappings for `Task.meta` do not cover the following types: Meta. The mappings for `Task.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `Task.meta` is mapped to FHIR R4B element `Task.meta` as `SourceIsBroaderThanTarget`. The mappings for `Task.meta` do not cover the following types: Meta. The mappings for `Task.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
All FHIR elements must have a @value or children unless an empty Parameters resource
hasValue() or (children().count() > id.count()) or $this is Parameters
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
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
DataType slice for a FHIR STU3 `Meta` value
Slice to indicate the presence of a STU3 `Meta` in FHIR R4B
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.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4B/extensibility.html) for a list).
Element `Meta.versionId` is mapped to FHIR R4B element `Meta.versionId` as `Equivalent`. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
Element `Meta.versionId` is mapped to FHIR R4B element `Meta.versionId` as `Equivalent`.
The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
Element `Meta.lastUpdated` is mapped to FHIR R4B element `Meta.lastUpdated` as `Equivalent`. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.
Element `Meta.lastUpdated` is mapped to FHIR R4B element `Meta.lastUpdated` as `Equivalent`.
When the resource last changed - e.g. when the version changed.
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.
Element `Meta.profile` is mapped to FHIR R4B element `Meta.profile` as `Equivalent`. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Element `Meta.profile` is mapped to FHIR R4B element `Meta.profile` as `Equivalent`.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](https://hl7.org/fhir/s.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url]().
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Element `Meta.security` is mapped to FHIR R4B element `Meta.security` as `Equivalent`. The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Element `Meta.security` is mapped to FHIR R4B element `Meta.security` as `Equivalent`.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Element `Meta.tag` is mapped to FHIR R4B element `Meta.tag` as `Equivalent`. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Element `Meta.tag` is mapped to FHIR R4B element `Meta.tag` as `Equivalent`.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"