FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r4
Resource TypeConceptMap
IdConceptMap-R5-Consent-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0/ConceptMap-R5-Consent-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-Consent-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:04:44.917818-05:00
NameR5ConsentElementMapToR4
TitleCross-version mapping for FHIR R5 Consent to FHIR R4 Consent
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 Consent to FHIR R4.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.controllerCross-version Extension for R5.Consent.controller for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.decisionCross-version Extension for R5.Consent.decision for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.grantorCross-version Extension for R5.Consent.grantor for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.managerCross-version Extension for R5.Consent.manager for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.periodCross-version Extension for R5.Consent.period for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.policyTextCross-version Extension for R5.Consent.policyText for use in FHIR R4
hl7.fhir.uv.xver-r5.r4#0.1.0extension-Consent.provision.expressionR5: A computable expression of the consent (new)
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.statusCross-version Extension for R5.Consent.status for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.verification.verificationTypeCross-version Extension for R5.Consent.verification.verificationType for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Consent.verification.verifiedByCross-version Extension for R5.Consent.verification.verifiedBy for use in FHIR R4

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R5-Consent-element-map-to-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/Consent|5.0.0 to Consentversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Consent.meta (meta)is equivalent toConsent.metaElement `Consent.meta` is mapped to FHIR R4 element `Consent.meta` as `Equivalent`.
Consent.implicitRules (implicitRules)is equivalent toConsent.implicitRulesElement `Consent.implicitRules` is mapped to FHIR R4 element `Consent.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.
Consent.language (language)is equivalent toConsent.languageElement `Consent.language` is mapped to FHIR R4 element `Consent.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).
Consent.text (text)is equivalent toConsent.textElement `Consent.text` is mapped to FHIR R4 element `Consent.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.
Consent.contained (contained)is equivalent toConsent.containedElement `Consent.contained` is mapped to FHIR R4 element `Consent.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.
Consent.identifier (identifier)is equivalent toConsent.identifierElement `Consent.identifier` is mapped to FHIR R4 element `Consent.identifier` as `Equivalent`. This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.
Consent.status (status)maps to wider conceptConsent.statusElement `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`. The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.
Consent.category (category)is equivalent toConsent.categoryElement `Consent.category` is mapped to FHIR R4 element `Consent.category` as `Equivalent`.
Consent.subject (subject)maps to wider conceptConsent.patientElement `Consent.subject` is mapped to FHIR R4 element `Consent.patient` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.subject` with unmapped reference targets: Group, Practitioner.
Consent.date (date)narrowerConsent.dateTimeElement `Consent.date` is mapped to FHIR R4 element `Consent.dateTime` as `SourceIsNarrowerThanTarget`.
Consent.grantee (grantee)maps to wider conceptConsent.performerElement `Consent.grantee` is mapped to FHIR R4 element `Consent.performer` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.grantee` with unmapped reference targets: CareTeam, HealthcareService. In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only.
Consent.sourceAttachment (sourceAttachment)is equivalent toConsent.source[x]Element `Consent.sourceAttachment` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`. The target context `Consent.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Consent`. The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.
Consent.sourceReference (sourceReference)maps to wider conceptConsent.source[x]Element `Consent.sourceReference` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.sourceReference` with unmapped reference targets: DocumentReference. Source element `Consent.sourceReference` has unmapped reference types. While the target element `Consent.source[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.
Consent.regulatoryBasis (regulatoryBasis)is equivalent toConsent.policyRuleElement `Consent.regulatoryBasis` is mapped to FHIR R4 element `Consent.policyRule` as `SourceIsBroaderThanTarget`.
Consent.policyBasis (policyBasis)is related toConsent.policyElement `Consent.policyBasis` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.
Consent.policyBasis.reference (reference)narrowerConsent.policyElement `Consent.policyBasis.reference` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`. While any resource may be used, Consent, PlanDefinition and Contract would be most frequent
Consent.policyBasis.url (url)narrowerConsent.policyElement `Consent.policyBasis.url` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.
Consent.verification (verification)maps to wider conceptConsent.verificationElement `Consent.verification` is mapped to FHIR R4 element `Consent.verification` as `Equivalent`.
Consent.verification.verified (verified)is equivalent toConsent.verification.verifiedElement `Consent.verification.verified` is mapped to FHIR R4 element `Consent.verification.verified` as `Equivalent`.
Consent.verification.verifiedWith (verifiedWith)is equivalent toConsent.verification.verifiedWithElement `Consent.verification.verifiedWith` is mapped to FHIR R4 element `Consent.verification.verifiedWith` as `Equivalent`.
Consent.verification.verificationDate (verificationDate)is equivalent toConsent.verification.verificationDateElement `Consent.verification.verificationDate` is mapped to FHIR R4 element `Consent.verification.verificationDate` as `SourceIsBroaderThanTarget`. Allows for history of verification/validation.
Consent.provision (provision)maps to wider conceptConsent.provisionElement `Consent.provision` is mapped to FHIR R4 element `Consent.provision` as `SourceIsBroaderThanTarget`.
Consent.provision.period (period)is equivalent toConsent.provision.periodElement `Consent.provision.period` is mapped to FHIR R4 element `Consent.provision.period` as `Equivalent`. This is the bound effective time of the consent and should be in the base provision in the Consent resource.
Consent.provision.actor (actor)maps to wider conceptConsent.provision.actorElement `Consent.provision.actor` is mapped to FHIR R4 element `Consent.provision.actor` as `Equivalent`.
Consent.provision.actor.role (role)is equivalent toConsent.provision.actor.roleElement `Consent.provision.actor.role` is mapped to FHIR R4 element `Consent.provision.actor.role` as `Equivalent`.
Consent.provision.actor.reference (reference)is equivalent toConsent.provision.actor.referenceElement `Consent.provision.actor.reference` is mapped to FHIR R4 element `Consent.provision.actor.reference` as `Equivalent`.
Consent.provision.action (action)is equivalent toConsent.provision.actionElement `Consent.provision.action` is mapped to FHIR R4 element `Consent.provision.action` as `Equivalent`. Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.
Consent.provision.securityLabel (securityLabel)is equivalent toConsent.provision.securityLabelElement `Consent.provision.securityLabel` is mapped to FHIR R4 element `Consent.provision.securityLabel` as `Equivalent`. If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.
Consent.provision.purpose (purpose)is equivalent toConsent.provision.purposeElement `Consent.provision.purpose` is mapped to FHIR R4 element `Consent.provision.purpose` as `Equivalent`. When the purpose of use tag is on the data, access request purpose of use shall not conflict.
Consent.provision.documentType (documentType)is equivalent toConsent.provision.classElement `Consent.provision.documentType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`. Multiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere.
Consent.provision.resourceType (resourceType)is equivalent toConsent.provision.classElement `Consent.provision.resourceType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`. Multiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
Consent.provision.code (code)is equivalent toConsent.provision.codeElement `Consent.provision.code` is mapped to FHIR R4 element `Consent.provision.code` as `Equivalent`.
Consent.provision.dataPeriod (dataPeriod)is equivalent toConsent.provision.dataPeriodElement `Consent.provision.dataPeriod` is mapped to FHIR R4 element `Consent.provision.dataPeriod` as `Equivalent`. This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.
Consent.provision.data (data)maps to wider conceptConsent.provision.dataElement `Consent.provision.data` is mapped to FHIR R4 element `Consent.provision.data` as `Equivalent`.
Consent.provision.data.meaning (meaning)is equivalent toConsent.provision.data.meaningElement `Consent.provision.data.meaning` is mapped to FHIR R4 element `Consent.provision.data.meaning` as `Equivalent`.
Consent.provision.data.reference (reference)is equivalent toConsent.provision.data.referenceElement `Consent.provision.data.reference` is mapped to FHIR R4 element `Consent.provision.data.reference` as `Equivalent`.
Consent.provision.provision (provision)is equivalent toConsent.provision.provisionElement `Consent.provision.provision` is mapped to FHIR R4 element `Consent.provision.provision` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: draft | active | inactive | not-done | entered-in-error | unknownversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.status (status)is equivalent toExtension (R5: draft | active | inactive | not-done | entered-in-error | unknown)Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`. The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Effective period for this Consent (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.period (period)maps to wider conceptExtension (R5: Effective period for this Consent (new))Element `Consent.period` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.period` 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/Consent|5.0.0 to R5: Who is granting rights according to the policy and rules (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.grantor (grantor)maps to wider conceptExtension (R5: Who is granting rights according to the policy and rules (new))Element `Consent.grantor` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.grantor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Consent workflow management (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.manager (manager)maps to wider conceptExtension (R5: Consent workflow management (new))Element `Consent.manager` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.manager` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Consent Enforcer (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.controller (controller)maps to wider conceptExtension (R5: Consent Enforcer (new))Element `Consent.controller` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.controller` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Human Readable Policy (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.policyText (policyText)maps to wider conceptExtension (R5: Human Readable Policy (new))Element `Consent.policyText` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.policyText` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Business case of verification (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.verification.verificationType (verificationType)maps to wider conceptExtension (R5: Business case of verification (new))Element `Consent.verification.verificationType` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`. Element `Consent.verification.verificationType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: Person conducting verification (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.verification.verifiedBy (verifiedBy)maps to wider conceptExtension (R5: Person conducting verification (new))Element `Consent.verification.verifiedBy` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`. Element `Consent.verification.verifiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: deny | permit (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.decision (decision)is equivalent toExtension (R5: deny | permit (new))Element `Consent.decision` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.decision` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|5.0.0 to R5: A computable expression of the consent (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.provision.expression (expression)maps to wider conceptExtension (R5: A computable expression of the consent (new))Element `Consent.provision.expression` has a context of Consent.provision based on following the parent source element upwards and mapping to `Consent`. Element `Consent.provision.expression` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Constraining the expression type for a specific implementation via profile is recommended

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-Consent-element-map-to-R4",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Consent-element-map-to-R4",
  "version": "0.1.0",
  "name": "R5ConsentElementMapToR4",
  "title": "Cross-version mapping for FHIR R5 Consent to FHIR R4 Consent",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:44.917818-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 Consent to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Consent",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "Consent.meta",
          "display": "meta",
          "target": [
            {
              "code": "Consent.meta",
              "display": "Consent.meta",
              "equivalence": "equivalent",
              "comment": "Element `Consent.meta` is mapped to FHIR R4 element `Consent.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Consent.implicitRules",
              "display": "Consent.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `Consent.implicitRules` is mapped to FHIR R4 element `Consent.implicitRules` as `Equivalent`.\nAsserting 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."
            }
          ]
        },
        {
          "code": "Consent.language",
          "display": "language",
          "target": [
            {
              "code": "Consent.language",
              "display": "Consent.language",
              "equivalence": "equivalent",
              "comment": "Element `Consent.language` is mapped to FHIR R4 element `Consent.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Consent.text",
          "display": "text",
          "target": [
            {
              "code": "Consent.text",
              "display": "Consent.text",
              "equivalence": "equivalent",
              "comment": "Element `Consent.text` is mapped to FHIR R4 element `Consent.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Consent.contained",
          "display": "contained",
          "target": [
            {
              "code": "Consent.contained",
              "display": "Consent.contained",
              "equivalence": "equivalent",
              "comment": "Element `Consent.contained` is mapped to FHIR R4 element `Consent.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "Consent.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Consent.identifier",
              "display": "Consent.identifier",
              "equivalence": "equivalent",
              "comment": "Element `Consent.identifier` is mapped to FHIR R4 element `Consent.identifier` as `Equivalent`.\nThis identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same."
            }
          ]
        },
        {
          "code": "Consent.status",
          "display": "status",
          "target": [
            {
              "code": "Consent.status",
              "display": "Consent.status",
              "equivalence": "wider",
              "comment": "Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.\nThe target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.\nThis element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid."
            }
          ]
        },
        {
          "code": "Consent.category",
          "display": "category",
          "target": [
            {
              "code": "Consent.category",
              "display": "Consent.category",
              "equivalence": "equivalent",
              "comment": "Element `Consent.category` is mapped to FHIR R4 element `Consent.category` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.subject",
          "display": "subject",
          "target": [
            {
              "code": "Consent.patient",
              "display": "Consent.patient",
              "equivalence": "wider",
              "comment": "Element `Consent.subject` is mapped to FHIR R4 element `Consent.patient` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.subject` with unmapped reference targets: Group, Practitioner."
            }
          ]
        },
        {
          "code": "Consent.date",
          "display": "date",
          "target": [
            {
              "code": "Consent.dateTime",
              "display": "Consent.dateTime",
              "equivalence": "narrower",
              "comment": "Element `Consent.date` is mapped to FHIR R4 element `Consent.dateTime` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.grantee",
          "display": "grantee",
          "target": [
            {
              "code": "Consent.performer",
              "display": "Consent.performer",
              "equivalence": "wider",
              "comment": "Element `Consent.grantee` is mapped to FHIR R4 element `Consent.performer` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.grantee` with unmapped reference targets: CareTeam, HealthcareService.\nIn a fully computable consent, both grantee and grantor  will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only."
            }
          ]
        },
        {
          "code": "Consent.sourceAttachment",
          "display": "sourceAttachment",
          "target": [
            {
              "code": "Consent.source[x]",
              "display": "Consent.source[x]",
              "equivalence": "equivalent",
              "comment": "Element `Consent.sourceAttachment` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.\nThe target context `Consent.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Consent`.\nThe source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id."
            }
          ]
        },
        {
          "code": "Consent.sourceReference",
          "display": "sourceReference",
          "target": [
            {
              "code": "Consent.source[x]",
              "display": "Consent.source[x]",
              "equivalence": "wider",
              "comment": "Element `Consent.sourceReference` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.sourceReference` with unmapped reference targets: DocumentReference.\nSource element `Consent.sourceReference` has unmapped reference types. While the target element `Consent.source[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.\nThe source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id."
            }
          ]
        },
        {
          "code": "Consent.regulatoryBasis",
          "display": "regulatoryBasis",
          "target": [
            {
              "code": "Consent.policyRule",
              "display": "Consent.policyRule",
              "equivalence": "equivalent",
              "comment": "Element `Consent.regulatoryBasis` is mapped to FHIR R4 element `Consent.policyRule` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.policyBasis",
          "display": "policyBasis",
          "target": [
            {
              "code": "Consent.policy",
              "display": "Consent.policy",
              "equivalence": "relatedto",
              "comment": "Element `Consent.policyBasis` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.policyBasis.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.policy",
              "display": "Consent.policy",
              "equivalence": "narrower",
              "comment": "Element `Consent.policyBasis.reference` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.\nWhile any resource may be used, Consent, PlanDefinition and Contract would be most frequent"
            }
          ]
        },
        {
          "code": "Consent.policyBasis.url",
          "display": "url",
          "target": [
            {
              "code": "Consent.policy",
              "display": "Consent.policy",
              "equivalence": "narrower",
              "comment": "Element `Consent.policyBasis.url` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.verification",
          "display": "verification",
          "target": [
            {
              "code": "Consent.verification",
              "display": "Consent.verification",
              "equivalence": "wider",
              "comment": "Element `Consent.verification` is mapped to FHIR R4 element `Consent.verification` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.verification.verified",
          "display": "verified",
          "target": [
            {
              "code": "Consent.verification.verified",
              "display": "Consent.verification.verified",
              "equivalence": "equivalent",
              "comment": "Element `Consent.verification.verified` is mapped to FHIR R4 element `Consent.verification.verified` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.verification.verifiedWith",
          "display": "verifiedWith",
          "target": [
            {
              "code": "Consent.verification.verifiedWith",
              "display": "Consent.verification.verifiedWith",
              "equivalence": "equivalent",
              "comment": "Element `Consent.verification.verifiedWith` is mapped to FHIR R4 element `Consent.verification.verifiedWith` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.verification.verificationDate",
          "display": "verificationDate",
          "target": [
            {
              "code": "Consent.verification.verificationDate",
              "display": "Consent.verification.verificationDate",
              "equivalence": "equivalent",
              "comment": "Element `Consent.verification.verificationDate` is mapped to FHIR R4 element `Consent.verification.verificationDate` as `SourceIsBroaderThanTarget`.\nAllows for history of verification/validation."
            }
          ]
        },
        {
          "code": "Consent.provision",
          "display": "provision",
          "target": [
            {
              "code": "Consent.provision",
              "display": "Consent.provision",
              "equivalence": "wider",
              "comment": "Element `Consent.provision` is mapped to FHIR R4 element `Consent.provision` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.provision.period",
          "display": "period",
          "target": [
            {
              "code": "Consent.provision.period",
              "display": "Consent.provision.period",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.period` is mapped to FHIR R4 element `Consent.provision.period` as `Equivalent`.\nThis is the bound effective time of the consent and should be in the base provision in the Consent resource."
            }
          ]
        },
        {
          "code": "Consent.provision.actor",
          "display": "actor",
          "target": [
            {
              "code": "Consent.provision.actor",
              "display": "Consent.provision.actor",
              "equivalence": "wider",
              "comment": "Element `Consent.provision.actor` is mapped to FHIR R4 element `Consent.provision.actor` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.actor.role",
          "display": "role",
          "target": [
            {
              "code": "Consent.provision.actor.role",
              "display": "Consent.provision.actor.role",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.actor.role` is mapped to FHIR R4 element `Consent.provision.actor.role` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.actor.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.actor.reference",
              "display": "Consent.provision.actor.reference",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.actor.reference` is mapped to FHIR R4 element `Consent.provision.actor.reference` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.action",
          "display": "action",
          "target": [
            {
              "code": "Consent.provision.action",
              "display": "Consent.provision.action",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.action` is mapped to FHIR R4 element `Consent.provision.action` as `Equivalent`.\nNote that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'."
            }
          ]
        },
        {
          "code": "Consent.provision.securityLabel",
          "display": "securityLabel",
          "target": [
            {
              "code": "Consent.provision.securityLabel",
              "display": "Consent.provision.securityLabel",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.securityLabel` is mapped to FHIR R4 element `Consent.provision.securityLabel` as `Equivalent`.\nIf the consent specifies a security label of \"R\" then it applies to all resources that are labeled \"R\" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict."
            }
          ]
        },
        {
          "code": "Consent.provision.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "Consent.provision.purpose",
              "display": "Consent.provision.purpose",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.purpose` is mapped to FHIR R4 element `Consent.provision.purpose` as `Equivalent`.\nWhen the purpose of use tag is on the data, access request purpose of use shall not conflict."
            }
          ]
        },
        {
          "code": "Consent.provision.documentType",
          "display": "documentType",
          "target": [
            {
              "code": "Consent.provision.class",
              "display": "Consent.provision.class",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.documentType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.\nMultiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere."
            }
          ]
        },
        {
          "code": "Consent.provision.resourceType",
          "display": "resourceType",
          "target": [
            {
              "code": "Consent.provision.class",
              "display": "Consent.provision.class",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.resourceType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.\nMultiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere."
            }
          ]
        },
        {
          "code": "Consent.provision.code",
          "display": "code",
          "target": [
            {
              "code": "Consent.provision.code",
              "display": "Consent.provision.code",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.code` is mapped to FHIR R4 element `Consent.provision.code` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.dataPeriod",
          "display": "dataPeriod",
          "target": [
            {
              "code": "Consent.provision.dataPeriod",
              "display": "Consent.provision.dataPeriod",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.dataPeriod` is mapped to FHIR R4 element `Consent.provision.dataPeriod` as `Equivalent`.\nThis has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement."
            }
          ]
        },
        {
          "code": "Consent.provision.data",
          "display": "data",
          "target": [
            {
              "code": "Consent.provision.data",
              "display": "Consent.provision.data",
              "equivalence": "wider",
              "comment": "Element `Consent.provision.data` is mapped to FHIR R4 element `Consent.provision.data` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.data.meaning",
          "display": "meaning",
          "target": [
            {
              "code": "Consent.provision.data.meaning",
              "display": "Consent.provision.data.meaning",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.data.meaning` is mapped to FHIR R4 element `Consent.provision.data.meaning` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.data.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.data.reference",
              "display": "Consent.provision.data.reference",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.data.reference` is mapped to FHIR R4 element `Consent.provision.data.reference` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.provision.provision",
          "display": "provision",
          "target": [
            {
              "code": "Consent.provision.provision",
              "display": "Consent.provision.provision",
              "equivalence": "equivalent",
              "comment": "Element `Consent.provision.provision` is mapped to FHIR R4 element `Consent.provision.provision` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.status",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.status",
          "display": "status",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.\nThe target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.\nThis element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.period",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.period",
          "display": "period",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.period` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.grantor",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.grantor",
          "display": "grantor",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.grantor` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.grantor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.manager",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.manager",
          "display": "manager",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.manager` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.manager` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.controller",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.controller",
          "display": "controller",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.controller` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.controller` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.policyText",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.policyText",
          "display": "policyText",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.policyText` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.policyText` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.verification.verificationType",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.verification.verificationType",
          "display": "verificationType",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.verification.verificationType` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.verification.verificationType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.verification.verifiedBy",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.verification.verifiedBy",
          "display": "verifiedBy",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.verification.verifiedBy` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.verification.verifiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.decision",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.decision",
          "display": "decision",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Consent.decision` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.decision` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.provision.expression",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Consent.provision.expression",
          "display": "expression",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Consent.provision.expression` has a context of Consent.provision based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.provision.expression` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nConstraining the expression type for a specific implementation via profile is recommended"
            }
          ]
        }
      ]
    }
  ]
}