Generated Narrative: ConceptMap R3-ServiceDefinition-element-map-to-R4 Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to Basicversion: 4.0.1) Source Code Relationship Target Code Comment ServiceDefinition.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ServiceDefinition.meta` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ServiceDefinition.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ServiceDefinition.implicitRules` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. ServiceDefinition.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ServiceDefinition.language` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). ServiceDefinition.text (text) is equivalent to Basic.text Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ServiceDefinition.text` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. ServiceDefinition.contained (contained) is equivalent to Basic.contained Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ServiceDefinition.contained` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. ServiceDefinition.identifier (identifier) is equivalent to Basic.identifier Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ServiceDefinition.identifier` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this service definition outside of FHIR, where it is not possible to use the logical URI. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Logical URI to reference this service definition (globally unique) (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.url (url) maps to wider concept Extension (STU3: Logical URI to reference this service definition (globally unique) (new)) Element `ServiceDefinition.url` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Business version of the service definition (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.version (version) maps to wider concept Extension (STU3: Business version of the service definition (new)) Element `ServiceDefinition.version` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There may be different service definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the service definition with the format [url]|[version]. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Name for this service definition (computer friendly) (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.name (name) maps to wider concept Extension (STU3: Name for this service definition (computer friendly) (new)) Element `ServiceDefinition.name` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Name for this service definition (human friendly) (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.title (title) maps to wider concept Extension (STU3: Name for this service definition (human friendly) (new)) Element `ServiceDefinition.title` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: draft | active | retired | unknown (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.status (status) maps to wider concept Extension (STU3: draft | active | retired | unknown (new)) Element `ServiceDefinition.status` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired service definition without due consideration. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: For testing purposes, not real usage (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.experimental (experimental) maps to wider concept Extension (STU3: For testing purposes, not real usage (new)) Element `ServiceDefinition.experimental` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.experimental` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental service definition in production. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Date this was last changed (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.date (date) maps to wider concept Extension (STU3: Date this was last changed (new)) Element `ServiceDefinition.date` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.date` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the service definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Name of the publisher (organization or individual) (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.publisher (publisher) maps to wider concept Extension (STU3: Name of the publisher (organization or individual) (new)) Element `ServiceDefinition.publisher` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization, but may be an individual. The publisher (or steward) of the service definition is the organization or individual primarily responsible for the maintenance and upkeep of the service definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the service definition. This item SHOULD be populated unless the information is available from context. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Natural language description of the service definition (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.description (description) maps to wider concept Extension (STU3: Natural language description of the service definition (new)) Element `ServiceDefinition.description` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This description can be used to capture details such as why the service definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the service definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Why this service definition is defined (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.purpose (purpose) maps to wider concept Extension (STU3: Why this service definition is defined (new)) Element `ServiceDefinition.purpose` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the service definition Instead it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this service definition. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Describes the clinical usage of the module (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.usage (usage) maps to wider concept Extension (STU3: Describes the clinical usage of the module (new)) Element `ServiceDefinition.usage` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.usage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: When the service definition was approved by publisher (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.approvalDate (approvalDate) maps to wider concept Extension (STU3: When the service definition was approved by publisher (new)) Element `ServiceDefinition.approvalDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.approvalDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The 'date' element may be more recent than the approval date because of minor changes / editorial corrections. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: When the service definition was last reviewed (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.lastReviewDate (lastReviewDate) maps to wider concept Extension (STU3: When the service definition was last reviewed (new)) Element `ServiceDefinition.lastReviewDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.lastReviewDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If specified, this is usually after the approval date. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: When the service definition is expected to be used (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.effectivePeriod (effectivePeriod) maps to wider concept Extension (STU3: When the service definition is expected to be used (new)) Element `ServiceDefinition.effectivePeriod` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The effective period for a service definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015. Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Context the content is intended to support (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.useContext (useContext) maps to wider concept Extension (STU3: Context the content is intended to support (new)) Element `ServiceDefinition.useContext` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Intended jurisdiction for service definition (if applicable) (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.jurisdiction (jurisdiction) maps to wider concept Extension (STU3: Intended jurisdiction for service definition (if applicable) (new)) Element `ServiceDefinition.jurisdiction` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). It may be possible for the service definition to be used in jurisdictions other than those for which it was originally designed or intended. Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: E.g. Education, Treatment, Assessment, etc (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.topic (topic) maps to wider concept Extension (STU3: E.g. Education, Treatment, Assessment, etc (new)) Element `ServiceDefinition.topic` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.topic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: A content contributor (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.contributor (contributor) maps to wider concept Extension (STU3: A content contributor (new)) Element `ServiceDefinition.contributor` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Contact details for the publisher (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.contact (contact) maps to wider concept Extension (STU3: Contact details for the publisher (new)) Element `ServiceDefinition.contact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc. Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Use and/or publishing restrictions (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.copyright (copyright) maps to wider concept Extension (STU3: Use and/or publishing restrictions (new)) Element `ServiceDefinition.copyright` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Additional documentation, citations, etc (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.relatedArtifact (relatedArtifact) maps to wider concept Extension (STU3: Additional documentation, citations, etc (new)) Element `ServiceDefinition.relatedArtifact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Each related resource is either an attachment, or a reference to another resource, but not both. Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: "when" the module should be invoked (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.trigger (trigger) maps to wider concept Extension (STU3: "when" the module should be invoked (new)) Element `ServiceDefinition.trigger` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.trigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 24 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: What data is used by the module (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.dataRequirement (dataRequirement) maps to wider concept Extension (STU3: What data is used by the module (new)) Element `ServiceDefinition.dataRequirement` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.dataRequirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 25 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to STU3: Operation to invoke (new)version: 0.1.0) Source Code Relationship Target Code Comment ServiceDefinition.operationDefinition (operationDefinition) maps to wider concept Extension (STU3: Operation to invoke (new)) Element `ServiceDefinition.operationDefinition` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.operationDefinition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR STU3 ServiceDefinition to FHIR R4 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ServiceDefinition to FHIR R4.
Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ServiceDefinition.meta` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ServiceDefinition.implicitRules` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ServiceDefinition.language` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ServiceDefinition.text` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ServiceDefinition.contained` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ServiceDefinition.identifier` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this service definition outside of FHIR, where it is not possible to use the logical URI.
Element `ServiceDefinition.url` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version.
Element `ServiceDefinition.version` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There may be different service definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the service definition with the format [url]|[version].
Element `ServiceDefinition.name` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.
Element `ServiceDefinition.title` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Element `ServiceDefinition.status` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired service definition without due consideration.
Element `ServiceDefinition.experimental` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.experimental` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental service definition in production.
Element `ServiceDefinition.date` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.date` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the service definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Element `ServiceDefinition.publisher` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization, but may be an individual. The publisher (or steward) of the service definition is the organization or individual primarily responsible for the maintenance and upkeep of the service definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the service definition. This item SHOULD be populated unless the information is available from context.
Element `ServiceDefinition.description` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This description can be used to capture details such as why the service definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the service definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created).
Element `ServiceDefinition.purpose` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the service definition Instead it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this service definition.
Element `ServiceDefinition.usage` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.usage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.approvalDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.approvalDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The 'date' element may be more recent than the approval date because of minor changes / editorial corrections.
Element `ServiceDefinition.lastReviewDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.lastReviewDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If specified, this is usually after the approval date.
Element `ServiceDefinition.effectivePeriod` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The effective period for a service definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.
Element `ServiceDefinition.useContext` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Element `ServiceDefinition.jurisdiction` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). It may be possible for the service definition to be used in jurisdictions other than those for which it was originally designed or intended.
Element `ServiceDefinition.topic` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.topic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.contributor` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.contact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.
Element `ServiceDefinition.copyright` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.relatedArtifact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Each related resource is either an attachment, or a reference to another resource, but not both.
Element `ServiceDefinition.trigger` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.trigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.dataRequirement` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.dataRequirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ServiceDefinition.operationDefinition` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.operationDefinition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).