Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R5SearchParameterElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-SearchParameter-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5SearchParameterElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR R5 SearchParameter to FHIR R4.

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/SearchParameter|5.0.0 to SearchParameterversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
SearchParameter.meta (meta)is equivalent toSearchParameter.metaElement `SearchParameter.meta` is mapped to FHIR R4 element `SearchParameter.meta` as `Equivalent`.
SearchParameter.implicitRules (implicitRules)is equivalent toSearchParameter.implicitRulesElement `SearchParameter.implicitRules` is mapped to FHIR R4 element `SearchParameter.implicitRules` as `Equivalent`. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
SearchParameter.language (language)is equivalent toSearchParameter.languageElement `SearchParameter.language` is mapped to FHIR R4 element `SearchParameter.language` as `Equivalent`. 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).
SearchParameter.text (text)is equivalent toSearchParameter.textElement `SearchParameter.text` is mapped to FHIR R4 element `SearchParameter.text` as `Equivalent`. Contained resources do not have a 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 information is added later.
SearchParameter.contained (contained)is equivalent toSearchParameter.containedElement `SearchParameter.contained` is mapped to FHIR R4 element `SearchParameter.contained` as `Equivalent`. 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
SearchParameter.url (url)is equivalent toSearchParameter.urlElement `SearchParameter.url` is mapped to FHIR R4 element `SearchParameter.url` as `Equivalent`. 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. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
SearchParameter.version (version)is equivalent toSearchParameter.versionElement `SearchParameter.version` is mapped to FHIR R4 element `SearchParameter.version` as `Equivalent`. There may be different search parameter instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the search parameter with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
SearchParameter.name (name)is equivalent toSearchParameter.nameElement `SearchParameter.name` is mapped to FHIR R4 element `SearchParameter.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
SearchParameter.derivedFrom (derivedFrom)is equivalent toSearchParameter.derivedFromElement `SearchParameter.derivedFrom` is mapped to FHIR R4 element `SearchParameter.derivedFrom` as `Equivalent`. The intent of this is that a server can designate that it provides support for a search parameter defined in the specification itself (e.g. [`value-quantity`](http://hl7.org/fhir/SearchParameter/Observation-value-quantity), but detail how it is supported by the server.
SearchParameter.status (status)is equivalent toSearchParameter.statusElement `SearchParameter.status` is mapped to FHIR R4 element `SearchParameter.status` as `Equivalent`. Allows filtering of search parameters that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
SearchParameter.experimental (experimental)is equivalent toSearchParameter.experimentalElement `SearchParameter.experimental` is mapped to FHIR R4 element `SearchParameter.experimental` as `Equivalent`. Allows filtering of search parameters that are appropriate for use versus not.
SearchParameter.date (date)is equivalent toSearchParameter.dateElement `SearchParameter.date` is mapped to FHIR R4 element `SearchParameter.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the search parameter. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
SearchParameter.publisher (publisher)is equivalent toSearchParameter.publisherElement `SearchParameter.publisher` is mapped to FHIR R4 element `SearchParameter.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the search parameter is the organization or individual primarily responsible for the maintenance and upkeep of the search parameter. 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 search parameter. This item SHOULD be populated unless the information is available from context.
SearchParameter.contact (contact)is equivalent toSearchParameter.contactElement `SearchParameter.contact` is mapped to FHIR R4 element `SearchParameter.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
SearchParameter.description (description)is equivalent toSearchParameter.descriptionElement `SearchParameter.description` is mapped to FHIR R4 element `SearchParameter.description` as `Equivalent`. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the search parameter 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 search parameter is presumed to be the predominant language in the place the search parameter was created).
SearchParameter.useContext (useContext)is equivalent toSearchParameter.useContextElement `SearchParameter.useContext` is mapped to FHIR R4 element `SearchParameter.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
SearchParameter.jurisdiction (jurisdiction)is equivalent toSearchParameter.jurisdictionElement `SearchParameter.jurisdiction` is mapped to FHIR R4 element `SearchParameter.jurisdiction` as `Equivalent`. Element `SearchParameter.jurisdiction` has been flagged as deprecated. It may be possible for the search parameter to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)
SearchParameter.purpose (purpose)is equivalent toSearchParameter.purposeElement `SearchParameter.purpose` is mapped to FHIR R4 element `SearchParameter.purpose` as `Equivalent`. This element does not describe the usage of the search parameter. 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 search parameter.
SearchParameter.code (code)is equivalent toSearchParameter.codeElement `SearchParameter.code` is mapped to FHIR R4 element `SearchParameter.code` as `Equivalent`. For maximum compatibility, use only lowercase ASCII characters. Note that HL7 will never define multiple search parameters with the same code.
SearchParameter.base (base)is equivalent toSearchParameter.baseElement `SearchParameter.base` is mapped to FHIR R4 element `SearchParameter.base` as `SourceIsNarrowerThanTarget`. A search parameter must always apply to at least one resource type. When search parameters apply to more than one resource type, they can be used against any of the listed resource types, or in a cross-type search (see [Cross Resource Search](https://hl7.org/fhir/http.html#xr.html#xres-search)).
SearchParameter.type (type)is equivalent toSearchParameter.typeElement `SearchParameter.type` is mapped to FHIR R4 element `SearchParameter.type` as `Equivalent`.
SearchParameter.expression (expression)is equivalent toSearchParameter.expressionElement `SearchParameter.expression` is mapped to FHIR R4 element `SearchParameter.expression` as `Equivalent`. Note that the elements returned by the expression are sometimes complex elements where logic is required to determine quite how to handle them; e.g. CodeableConcepts may contain text and/or multiple codings, where the codings themselves contain a code and a system. For composite search parameters, the outcome of the expression must a collection of base elements from which the composites are derived.
SearchParameter.processingMode (processingMode)is related toSearchParameter.xpathUsageElement `SearchParameter.processingMode` is mapped to FHIR R4 element `SearchParameter.xpathUsage` as `RelatedTo`. The mappings for `SearchParameter.processingMode` do not allow expression of the necessary codes, per the bindings on the source and target.
SearchParameter.target (target)is equivalent toSearchParameter.targetElement `SearchParameter.target` is mapped to FHIR R4 element `SearchParameter.target` as `SourceIsNarrowerThanTarget`. In some cases, targets may exist for a search parameter that do not exist for the specified FHIRPath for all of the resources identified in SearchParameter.base. For example, the core clinical-encounter search parameter allows both Encounter and EpisodeOfCare as targets, even though not all of the base resources have EpisodeOfCare as a valid target. However, the list of targets SHOULD cover all targets that might appear that are permitted by the specified FHIRPath.
SearchParameter.multipleOr (multipleOr)is equivalent toSearchParameter.multipleOrElement `SearchParameter.multipleOr` is mapped to FHIR R4 element `SearchParameter.multipleOr` as `Equivalent`.
SearchParameter.multipleAnd (multipleAnd)is equivalent toSearchParameter.multipleAndElement `SearchParameter.multipleAnd` is mapped to FHIR R4 element `SearchParameter.multipleAnd` as `Equivalent`.
SearchParameter.comparator (comparator)is equivalent toSearchParameter.comparatorElement `SearchParameter.comparator` is mapped to FHIR R4 element `SearchParameter.comparator` as `Equivalent`. If no comparators are listed, clients should not expect servers to support any comparators.
SearchParameter.modifier (modifier)maps to wider conceptSearchParameter.modifierElement `SearchParameter.modifier` is mapped to FHIR R4 element `SearchParameter.modifier` as `RelatedTo`. The mappings for `SearchParameter.modifier` do not allow expression of the necessary codes, per the bindings on the source and target.
SearchParameter.chain (chain)is equivalent toSearchParameter.chainElement `SearchParameter.chain` is mapped to FHIR R4 element `SearchParameter.chain` as `Equivalent`. Notes: * Not all systems will declare chain values. If no chain values are specified at all, then no presumptions can be made about the degree of chaining support available * A server may use a single chain value of '*' to mean that all reference search types supported can be chained rather than enumerating all chain values * If a particular reference search parameter is supported, but not subsequent chaining, then just list that search parameter name - e.g. for Patient.practitioner, the chain value would be ```practitioner``` * If a particular reference search parameter is supported with unlimited chaining beneath it, then follow the search parameter name with '.'. E.g. ```practitioner.``` * If there are specific (not unlimited) chaining paths allowed they can be explicitly enumerated. E.g. ```practitioner.organization```
SearchParameter.component (component)maps to wider conceptSearchParameter.componentElement `SearchParameter.component` is mapped to FHIR R4 element `SearchParameter.component` as `Equivalent`.
SearchParameter.component.definition (definition)is equivalent toSearchParameter.component.definitionElement `SearchParameter.component.definition` is mapped to FHIR R4 element `SearchParameter.component.definition` as `Equivalent`.
SearchParameter.component.expression (expression)is equivalent toSearchParameter.component.expressionElement `SearchParameter.component.expression` is mapped to FHIR R4 element `SearchParameter.component.expression` as `Equivalent`. This expression overrides the expression in the definition and extracts the index values from the outcome of the composite expression.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/SearchParameter|5.0.0 to R5: normal | phonetic | other additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
SearchParameter.processingMode (processingMode)maps to wider conceptExtension (R5: normal | phonetic | other additional codes)Element `SearchParameter.processingMode` is mapped to FHIR R4 element `SearchParameter.xpathUsage` as `RelatedTo`. The mappings for `SearchParameter.processingMode` do not allow expression of the necessary codes, per the bindings on the source and target.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/SearchParameter|5.0.0 to R5: FHIRPath expression that constraints the usage of this SearchParamete (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
SearchParameter.constraint (constraint)maps to wider conceptExtension (R5: FHIRPath expression that constraints the usage of this SearchParamete (new))Element `SearchParameter.constraint` has a context of SearchParameter based on following the parent source element upwards and mapping to `SearchParameter`. Element `SearchParameter.constraint` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/SearchParameter|5.0.0 to R5: missing | exact | contains | not | text | in | not-in | below | above | type | identifier | of-type | code-text | text-advanced | iterate additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
SearchParameter.modifier (modifier)is equivalent toExtension (R5: missing | exact | contains | not | text | in | not-in | below | above | type | identifier | of-type | code-text | text-advanced | iterate additional codes)Element `SearchParameter.modifier` is mapped to FHIR R4 element `SearchParameter.modifier` as `RelatedTo`. The mappings for `SearchParameter.modifier` do not allow expression of the necessary codes, per the bindings on the source and target.