Generated Narrative: StructureDefinition ext-R3-ConceptMap.contact Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.3.0) STU3: contact additional types #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-ConceptMap.contact" #xD; value[x] 0..1 ContactDetail Contact details for the publisher #xD; Documentation for this format
STU3: `ConceptMap.contact` additional types (ContactDetail) additional types from child elements (name, telecom)
This extension is part of the cross-version definitions generated to enable use of the element `ConceptMap.contact` as defined in FHIR STU3 in FHIR R4B. The source element is defined as: `ConceptMap.contact` 0..* `ContactDetail` Across FHIR versions, the element set has been mapped as: * STU3: `ConceptMap.contact` 0..* `ContactDetail` * R4: `ConceptMap.contact` 0..* `ContactDetail` * R4B: `ConceptMap.contact` 0..* `ContactDetail` Following are the generation technical comments: Element `ConceptMap.contact` is mapped to FHIR R4B element `ConceptMap.contact` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.contact` do not cover the following types: ContactDetail. The mappings for `ConceptMap.contact` do not cover the following types based on type expansion: name, telecom.
Element `ConceptMap.contact` is mapped to FHIR R4B element `ConceptMap.contact` as `SourceIsBroaderThanTarget`. The mappings for `ConceptMap.contact` do not cover the following types: ContactDetail. The mappings for `ConceptMap.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.
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
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.
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")])
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.
Contact details to assist a user in finding and communicating with the publisher.
May be a web site, an email address, a telephone number, etc.