Generated Narrative: StructureDefinition terminology-resource-identifier-metadata Name Flags Card. Type Description & Constraints Extension 0..* Extension Additional metadata in identifier elements for terminology resources. #xD; Slices for extension Content/Rules for all slices #xD; extension:preferred 0..1 Extension Whether this an identifier that should be used #xD; extension 0..0 #xD; url 1..1 uri "preferred" #xD; value[x] 1..1 boolean Value of extension #xD; extension:authoritative 0..1 Extension Whether this identifier is considered to be authoritative #xD; extension 0..0 #xD; url 1..1 uri "authoritative" #xD; value[x] 1..1 boolean Value of extension #xD; extension:comment 0..1 Extension Text to explain the use of the additional metadata values. #xD; extension 0..0 #xD; url 1..1 uri "comment" #xD; value[x] 1..1 string Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/terminology-resource-identifier-metadata" #xD; value[x] 0..0 #xD; Documentation for this format
Terminology Resource Identifier Metadata
HL7 International / Terminology Infrastructure
Additional metadata in identifier elements for terminology resources.
Additional metadata which may be asserted in identifier elements for terminology resources.
This represents additional metadata values which apply the identifier values in FHIR terminology resources.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
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
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 managable, 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.
Whether this an identifier that should be used
Indicates whether this identifier is a 'preferred' identifier
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/R5/extensibility.html) for a list).
Whether this identifier is considered to be authoritative
Indicates whether this identifier is an 'authoritative' identifier
Text to explain the use of the additional metadata values.