R5-Requirements-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-Requirements-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-Requirements-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from Requirements to Basic Source Code Card. Type Relationship Target Code Card. Type Comment Requirements.meta 0..1 todo is equivalent to Basic.meta 0..1 todo Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `Requirements.meta` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Requirements.implicitRules 0..1 todo is equivalent to Basic.implicitRules 0..1 todo Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `Requirements.implicitRules` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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. 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. Requirements.language 0..1 todo is equivalent to Basic.language 0..1 todo Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `Requirements.language` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.language` has no mapping target…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-Requirements-element-map-to-R4
  l: R5-Requirements-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5RequirementsElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 Requirements to FHIR R4 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:47.9124555-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 Requirements to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Requirements
    l: Requirements
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 4.0.1
  element:
    code:
      v: Requirements.meta
    display:
      v: meta
    target:
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `Requirements.meta` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: Requirements.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `Requirements.implicitRules` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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. 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.
  element:
    code:
      v: Requirements.language
    display:
      v: language
    target:
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `Requirements.language` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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:
    code:
      v: Requirements.text
    display:
      v: text
    target:
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `Requirements.text` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 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.
  element:
    code:
      v: Requirements.contained
    display:
      v: contained
    target:
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `Requirements.contained` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: Requirements.identifier
    display:
      v: identifier
    target:
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `Requirements.identifier` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Requirements
    l: Requirements
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.url
    l: extension-Requirements.url
  target version:
    v: 0.1.0
  element:
    code:
      v: Requirements.url
    display:
      v: url
    target:
      code:
        v: Extension
      equivalence:
        v: wider
      comment:
        v: Element `Requirements.url` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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. 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.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Requirements
    l: Requirements

v: 5.0.0

v: 0.1.0

code:
  v: Requirements.version
display:
  v: version
target:
  code:
    v: Extension
  equivalence:
    v: wider
  comment:
    v: Element `Requirements.version` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 Requirements 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 Requirements with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.versionAlgorithm
  l: extension-Requirements.versionAlgorithm
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.versionAlgorithm[x]
  display:
    v: versionAlgorithm[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.versionAlgorithm[x]` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.versionAlgorithm[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.name
  l: extension-Requirements.name
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.name
  display:
    v: name
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.name` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 alphanumeric type name to ensure that it is machine-processing friendly.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.title
  l: extension-Requirements.title
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.title` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.status
  l: extension-Requirements.status
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.status` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of Requirements that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.experimental
  l: extension-Requirements.experimental
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.experimental
  display:
    v: experimental
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.experimental` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.experimental` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of Requirements that are appropriate for use versus not.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.date
  l: extension-Requirements.date
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.date
  display:
    v: date
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.date` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 Requirements. 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.publisher
  l: extension-Requirements.publisher
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.publisher
  display:
    v: publisher
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.publisher` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 Requirements is the organization or individual primarily responsible for the maintenance and upkeep of the Requirements. 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 Requirements. This item SHOULD be populated unless the information is available from context.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.contact
  l: extension-Requirements.contact
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.contact
  display:
    v: contact
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.contact` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.description
  l: extension-Requirements.description
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.description
  display:
    v: description
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.description` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 for a general description of the requirements, and which covers why it was defined.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.useContext
  l: extension-Requirements.useContext
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.useContext` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 that all or any of the contexts apply.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.jurisdiction
  l: extension-Requirements.jurisdiction
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.jurisdiction
  display:
    v: jurisdiction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.jurisdiction` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Element `Requirements.jurisdiction` has been flagged as deprecated. It may be possible for the Requirements 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.).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.purpose
  l: extension-Requirements.purpose
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.purpose
  display:
    v: purpose
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.purpose` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.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 Requirements. 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 Requirements.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.copyright
  l: extension-Requirements.copyright
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.copyright
  display:
    v: copyright
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.copyright` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ...

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.copyrightLabel
  l: extension-Requirements.copyrightLabel
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.copyrightLabel
  display:
    v: copyrightLabel
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.copyrightLabel` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.copyrightLabel` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.derivedFrom
  l: extension-Requirements.derivedFrom
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.derivedFrom
  display:
    v: derivedFrom
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.derivedFrom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Existing statements (by key) may be narrowed or clarified, and additional statements added.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.reference
  l: extension-Requirements.reference
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.reference
  display:
    v: reference
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.reference` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.actor
  l: extension-Requirements.actor
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.actor
  display:
    v: actor
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.actor` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If more than one actor is specified, then it's up to the statements to describe in narrative if they don't apply to all actors.

source:
  v: http://hl7.org/fhir/StructureDefinition/Requirements
  l: Requirements
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement
  l: extension-Requirements.statement
target version:
  v: 0.1.0
element:
  code:
    v: Requirements.statement
  display:
    v: statement
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Requirements.statement.key
  display:
    v: key
  target:
    code:
      v: Extension.extension:key
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.key` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.key` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.key` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Refer directly to the statement by {url}#{key}
element:
  code:
    v: Requirements.statement.label
  display:
    v: label
  target:
    code:
      v: Extension.extension:label
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.label` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.label` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.label` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The key is intended for computers, while this is intended for humans. In its absence, the key should be convenient for a human to say (e.g. not a UUID)
element:
  code:
    v: Requirements.statement.conformance
  display:
    v: conformance
  target:
    code:
      v: Extension.extension:conformance
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.conformance` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conformance` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conformance` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The conformance code is extracted from the requirement to make indexing and display easier. The requirement needs to express the conformance verbs directly in the markdown content. It's not unusual to mix verbs in a single sentence (e.g. System SHALL do X and SHOULD do Y)
element:
  code:
    v: Requirements.statement.conditionality
  display:
    v: conditionality
  target:
    code:
      v: Extension.extension:conditionality
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.conditionality` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.conditionality` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.conditionality` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There is no intent that the conditional statement by evaluatable
element:
  code:
    v: Requirements.statement.requirement
  display:
    v: requirement
  target:
    code:
      v: Extension.extension:requirement
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.requirement` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.requirement` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.requirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Requirements.statement.derivedFrom
  display:
    v: derivedFrom
  target:
    code:
      v: Extension.extension:derivedFrom
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.derivedFrom` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.derivedFrom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This can be just a key, if there is only one matching statement in the requirements statements referenced in Requirements.derivedFrom. If there is more than one, it should be in the format ```url#key```
element:
  code:
    v: Requirements.statement.parent
  display:
    v: parent
  target:
    code:
      v: Extension.extension:parent
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.parent` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.parent` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.parent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Follows the same convention as statement.derivedFrom, where a reference is the canonical of the Requirements followed by '#' and the 'key' of the specific requirement.
element:
  code:
    v: Requirements.statement.satisfiedBy
  display:
    v: satisfiedBy
  target:
    code:
      v: Extension.extension:satisfiedBy
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.satisfiedBy` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.satisfiedBy` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.satisfiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is for use when the requirement is met be a pre-existing artifact e.g. a rule that's met by the base FHIR spec, or a national implementation guide.
element:
  code:
    v: Requirements.statement.reference
  display:
    v: reference
  target:
    code:
      v: Extension.extension:reference
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.reference` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.reference` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Requirements.statement.source
  display:
    v: source
  target:
    code:
      v: Extension.extension:source
    equivalence:
      v: wider
    comment:
      v: Element `Requirements.statement.source` is part of an existing definition because parent element `Requirements.statement` requires a cross-version extension. Element `Requirements.statement.source` is not mapped to FHIR R4, since FHIR R5 `Requirements` is not mapped. Element `Requirements.statement.source` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).