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

FHIR IG analytics

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

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.dataPeriodSTU3: Timeframe for data controlled by this consent additional types
hl7.fhir.uv.xver-r3.r5#0.1.0extension-Consent.dateTimeSTU3: When this Consent was created or indexed additional types
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.except.dataPeriodSTU3: Timeframe for data controlled by this exception additional types
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.except.periodSTU3: Timeframe for this exception additional types
hl7.fhir.uv.xver-r3.r5#0.1.0extension-Consent.except.typeSTU3: deny | permit (new)
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.identifierSTU3: identifier additional types
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.metaSTU3: meta additional types
hl7.fhir.uv.xver-r3.r5#0.1.0extension-Consent.organizationSTU3: Custodian of the consent (new)
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2extension-Consent.periodCross-version Extension for R3.Consent.period for use in FHIR R4B
hl7.fhir.uv.xver-r3.r5#0.1.0extension-Consent.policy.authoritySTU3: Enforcement source for policy (new)
hl7.fhir.uv.xver-r3.r5#0.1.0extension-Consent.policy.uriSTU3: Specific policy covered by this consent (new)
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2extension-Consent.policyRuleCross-version Extension for R3.Consent.policyRule for use in FHIR R4B
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2extension-Consent.sourceCross-version Extension for R3.Consent.source[x] for use in FHIR R4B
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-Consent.textSTU3: text additional types

Narrative

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

Generated Narrative: ConceptMap R3-Consent-element-map-to-R5

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to Consentversion: 5.0.0)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2Codes from Consent
Consent.metametais broader thanConsent.metaConsent.metaElement `Consent.meta` is mapped to FHIR R5 element `Consent.meta` as `SourceIsBroaderThanTarget`. The mappings for `Consent.meta` do not cover the following types: Meta. The mappings for `Consent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Consent.implicitRulesimplicitRulesis equivalent toConsent.implicitRulesConsent.implicitRulesElement `Consent.implicitRules` is mapped to FHIR R5 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Consent.languagelanguageis equivalent toConsent.languageConsent.languageElement `Consent.language` is mapped to FHIR R5 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.texttextis broader thanConsent.textConsent.textElement `Consent.text` is mapped to FHIR R5 element `Consent.text` as `SourceIsBroaderThanTarget`. The mappings for `Consent.text` do not cover the following types: Narrative. The mappings for `Consent.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
Consent.containedcontainedis equivalent toConsent.containedConsent.containedElement `Consent.contained` is mapped to FHIR R5 element `Consent.contained` as `SourceIsBroaderThanTarget`. 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.
Consent.identifieridentifieris broader thanConsent.identifierConsent.identifierElement `Consent.identifier` is mapped to FHIR R5 element `Consent.identifier` as `RelatedTo`. The mappings for `Consent.identifier` do not cover the following types: Identifier. The mappings for `Consent.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. This identifier is 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.statusstatusis equivalent toConsent.statusConsent.statusElement `Consent.status` is mapped to FHIR R5 element `Consent.status` as `SourceIsNarrowerThanTarget`. The mappings for `Consent.status` do not allow expression of the necessary codes, per the bindings on the source and target. 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.categorycategoryis equivalent toConsent.categoryConsent.categoryElement `Consent.category` is mapped to FHIR R5 element `Consent.category` as `Equivalent`.
Consent.patientpatientis broader thanConsent.subjectConsent.subjectElement `Consent.patient` is mapped to FHIR R5 element `Consent.subject` as `SourceIsBroaderThanTarget`. The mappings for `Consent.patient` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.patient` with unmapped reference targets: Patient. Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.
Consent.dateTimedateTimeis broader thanConsent.dateConsent.dateElement `Consent.dateTime` is mapped to FHIR R5 element `Consent.date` as `SourceIsBroaderThanTarget`. The mappings for `Consent.dateTime` do not cover the following types: dateTime. The mappings for `Consent.dateTime` do not cover the following types based on type expansion: value. This is not the time of the original consent, but the time that this statement was made or derived.
Consent.consentingPartyconsentingPartyis broader thanConsent.granteeConsent.granteeElement `Consent.consentingParty` is mapped to FHIR R5 element `Consent.grantee` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.consentingParty` with unmapped reference targets: Organization, Patient, Practitioner, RelatedPerson. Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.
Consent.actoractoris broader thanConsent.provision.actorConsent.provision.actorElement `Consent.actor` is mapped to FHIR R5 element `Consent.provision.actor` as `Equivalent`.
Consent.actor.roleroleis equivalent toConsent.provision.actor.roleConsent.provision.actor.roleElement `Consent.actor.role` is mapped to FHIR R5 element `Consent.provision.actor.role` as `Equivalent`.
Consent.actor.referencereferenceis broader thanConsent.provision.actor.referenceConsent.provision.actor.referenceElement `Consent.actor.reference` is mapped to FHIR R5 element `Consent.provision.actor.reference` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.actor.reference` with unmapped reference targets: CareTeam, Device, Group, Organization, Patient, Practitioner, RelatedPerson.
Consent.actionactionis equivalent toConsent.provision.actionConsent.provision.actionElement `Consent.action` is mapped to FHIR R5 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.policypolicyis broader thanConsent.policyBasisConsent.policyBasisElement `Consent.policy` is mapped to FHIR R5 element `Consent.policyBasis` as `SourceIsBroaderThanTarget`.
Consent.policyRulepolicyRuleis related toConsent.regulatoryBasisConsent.regulatoryBasisElement `Consent.policyRule` is mapped to FHIR R5 element `Consent.regulatoryBasis` as `RelatedTo`. The mappings for `Consent.policyRule` do not cover the following types: uri. The mappings for `Consent.policyRule` do not cover the following types based on type expansion: value. If the policy reference is not known, the resource cannot be processed. Where the reference is absent, there is no particular policy other than what is expressed directly in the consent resource.
Consent.securityLabelsecurityLabelis equivalent toConsent.provision.securityLabelConsent.provision.securityLabelElement `Consent.securityLabel` is mapped to FHIR R5 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. Not all of the security labels make sense for use in this element (may define a narrower value set?).
Consent.purposepurposeis equivalent toConsent.provision.purposeConsent.provision.purposeElement `Consent.purpose` is mapped to FHIR R5 element `Consent.provision.purpose` as `Equivalent`. This element is for discoverability / documentation, and does not modify or qualify the policy (e.g. the policy itself describes the purposes for which it applies).
Consent.dataPerioddataPeriodis broader thanConsent.provision.dataPeriodConsent.provision.dataPeriodElement `Consent.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Consent.dataPeriod` do not cover the following types: Period. The mappings for `Consent.dataPeriod` do not cover the following types based on type expansion: end, start. 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.datadatais broader thanConsent.provision.dataConsent.provision.dataElement `Consent.data` is mapped to FHIR R5 element `Consent.provision.data` as `Equivalent`.
Consent.data.meaningmeaningis equivalent toConsent.provision.data.meaningConsent.provision.data.meaningElement `Consent.data.meaning` is mapped to FHIR R5 element `Consent.provision.data.meaning` as `Equivalent`.
Consent.data.referencereferenceis broader thanConsent.provision.data.referenceConsent.provision.data.referenceElement `Consent.data.reference` is mapped to FHIR R5 element `Consent.provision.data.reference` as `SourceIsBroaderThanTarget`. The mappings for `Consent.data.reference` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.data.reference` with unmapped reference targets: Resource.
Consent.exceptexceptis related toConsent.provisionConsent.provisionElement `Consent.except` is mapped to FHIR R5 element `Consent.provision` as `RelatedTo`.
Consent.except.periodperiodis broader thanConsent.provision.periodConsent.provision.periodElement `Consent.except.period` is mapped to FHIR R5 element `Consent.provision.period` as `SourceIsBroaderThanTarget`. The mappings for `Consent.except.period` do not cover the following types: Period. The mappings for `Consent.except.period` do not cover the following types based on type expansion: end, start.
Consent.except.actoractoris broader thanConsent.provision.actorConsent.provision.actorElement `Consent.except.actor` is mapped to FHIR R5 element `Consent.provision.actor` as `Equivalent`.
Consent.except.actor.roleroleis equivalent toConsent.provision.actor.roleConsent.provision.actor.roleElement `Consent.except.actor.role` is mapped to FHIR R5 element `Consent.provision.actor.role` as `Equivalent`.
Consent.except.actor.referencereferenceis broader thanConsent.provision.actor.referenceConsent.provision.actor.referenceElement `Consent.except.actor.reference` is mapped to FHIR R5 element `Consent.provision.actor.reference` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.except.actor.reference` with unmapped reference targets: CareTeam, Device, Group, Organization, Patient, Practitioner, RelatedPerson.
Consent.except.actionactionis equivalent toConsent.provision.actionConsent.provision.actionElement `Consent.except.action` is mapped to FHIR R5 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.except.securityLabelsecurityLabelis equivalent toConsent.provision.securityLabelConsent.provision.securityLabelElement `Consent.except.securityLabel` is mapped to FHIR R5 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. Not all of the security labels make sense for use in this element (may define a narrower value set?).
Consent.except.purposepurposeis equivalent toConsent.provision.purposeConsent.provision.purposeElement `Consent.except.purpose` is mapped to FHIR R5 element `Consent.provision.purpose` as `Equivalent`. E.g. if the purpose is 'research', then the operational context must be research, in order for the consent to apply. Not all of the security labels make sense for use in this element (may define a narrower value set?).
Consent.except.classclassis related toConsent.provision.documentTypeConsent.provision.documentTypeElement `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.documentType` as `Equivalent`. Element `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.resourceType` as `Equivalent`. Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
is equivalent toConsent.provision.resourceTypeConsent.provision.resourceTypeElement `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.documentType` as `Equivalent`. Element `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.resourceType` as `Equivalent`. Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
Consent.except.codecodeis narrower thanConsent.provision.codeConsent.provision.codeElement `Consent.except.code` is mapped to FHIR R5 element `Consent.provision.code` as `SourceIsNarrowerThanTarget`. Typical use of this is a Document code with class = CDA.
Consent.except.dataPerioddataPeriodis broader thanConsent.provision.dataPeriodConsent.provision.dataPeriodElement `Consent.except.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Consent.except.dataPeriod` do not cover the following types: Period. The mappings for `Consent.except.dataPeriod` do not cover the following types based on type expansion: end, start. 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.except.datadatais broader thanConsent.provision.dataConsent.provision.dataElement `Consent.except.data` is mapped to FHIR R5 element `Consent.provision.data` as `Equivalent`.
Consent.except.data.meaningmeaningis equivalent toConsent.provision.data.meaningConsent.provision.data.meaningElement `Consent.except.data.meaning` is mapped to FHIR R5 element `Consent.provision.data.meaning` as `Equivalent`.
Consent.except.data.referencereferenceis broader thanConsent.provision.data.referenceConsent.provision.data.referenceElement `Consent.except.data.reference` is mapped to FHIR R5 element `Consent.provision.data.reference` as `SourceIsBroaderThanTarget`. The mappings for `Consent.except.data.reference` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.except.data.reference` with unmapped reference targets: Resource.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `Consent.meta` is mapped to FHIR R5 element `Consent.meta` as `SourceIsBroaderThanTarget`. The mappings for `Consent.meta` do not cover the following types: Meta. The mappings for `Consent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.text (text)is equivalent toExtension (STU3: text additional types)Element `Consent.text` is mapped to FHIR R5 element `Consent.text` as `SourceIsBroaderThanTarget`. The mappings for `Consent.text` do not cover the following types: Narrative. The mappings for `Consent.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.identifier (identifier)is equivalent toExtension (STU3: identifier additional types)Element `Consent.identifier` is mapped to FHIR R5 element `Consent.identifier` as `RelatedTo`. The mappings for `Consent.identifier` do not cover the following types: Identifier. The mappings for `Consent.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. This identifier is 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.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Period that this consent applies (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.period (period)is equivalent toExtension (STU3: Period that this consent applies (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 R5. Typically, this is because the element has been added (is a new element). This can be a subset of the period of the original statement.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: When this Consent was created or indexed additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.dateTime (dateTime)is broader thanExtension (STU3: When this Consent was created or indexed additional types)Element `Consent.dateTime` is mapped to FHIR R5 element `Consent.date` as `SourceIsBroaderThanTarget`. The mappings for `Consent.dateTime` do not cover the following types: dateTime. The mappings for `Consent.dateTime` do not cover the following types based on type expansion: value. This is not the time of the original consent, but the time that this statement was made or derived.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Custodian of the consent (new)version: 0.1.0)

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

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Source from which this consent is taken (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.source[x] (source[x])is broader thanExtension (STU3: Source from which this consent is taken (new))Element `Consent.source[x]` has a context of Consent based on following the parent source element upwards and mapping to `Consent`. Element `Consent.source[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Enforcement source for policy (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.policy.authority (authority)is equivalent toExtension (STU3: Enforcement source for policy (new))Element `Consent.policy.authority` has a context of Consent.policyBasis based on following the parent source element upwards and mapping to `Consent`. Element `Consent.policy.authority` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Specific policy covered by this consent (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.policy.uri (uri)is equivalent toExtension (STU3: Specific policy covered by this consent (new))Element `Consent.policy.uri` has a context of Consent.policyBasis based on following the parent source element upwards and mapping to `Consent`. Element `Consent.policy.uri` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This element is for discoverability / documentation, and does not modify or qualify the policy rules.

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Policy that this consents to additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.policyRule (policyRule)is broader thanExtension (STU3: Policy that this consents to additional types)Element `Consent.policyRule` is mapped to FHIR R5 element `Consent.regulatoryBasis` as `RelatedTo`. The mappings for `Consent.policyRule` do not cover the following types: uri. The mappings for `Consent.policyRule` do not cover the following types based on type expansion: value. If the policy reference is not known, the resource cannot be processed. Where the reference is absent, there is no particular policy other than what is expressed directly in the consent resource.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Timeframe for data controlled by this consent additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.dataPeriod (dataPeriod)is broader thanExtension (STU3: Timeframe for data controlled by this consent additional types)Element `Consent.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Consent.dataPeriod` do not cover the following types: Period. The mappings for `Consent.dataPeriod` do not cover the following types based on type expansion: end, start. 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.

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: deny | permit (new)version: 0.1.0)

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

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Timeframe for this exception additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.except.period (period)is broader thanExtension (STU3: Timeframe for this exception additional types)Element `Consent.except.period` is mapped to FHIR R5 element `Consent.provision.period` as `SourceIsBroaderThanTarget`. The mappings for `Consent.except.period` do not cover the following types: Period. The mappings for `Consent.except.period` do not cover the following types based on type expansion: end, start.

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/Consent|3.0.2 to STU3: Timeframe for data controlled by this exception additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Consent.except.dataPeriod (dataPeriod)is broader thanExtension (STU3: Timeframe for data controlled by this exception additional types)Element `Consent.except.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Consent.except.dataPeriod` do not cover the following types: Period. The mappings for `Consent.except.dataPeriod` do not cover the following types based on type expansion: end, start. 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.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R3-Consent-element-map-to-R5",
  "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-r3.r5"
          }
        ]
      }
    },
    {
      "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-r3.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-Consent-element-map-to-R5",
  "version": "0.1.0",
  "name": "R3ConsentElementMapToR5",
  "title": "Cross-version mapping for FHIR STU3 Consent to FHIR R5 Consent",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:59.4548111-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 STU3 Consent to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/3.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/Consent|5.0.0",
      "element": [
        {
          "code": "Consent.meta",
          "display": "meta",
          "target": [
            {
              "code": "Consent.meta",
              "display": "Consent.meta",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.meta` is mapped to FHIR R5 element `Consent.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.meta` do not cover the following types: Meta.\nThe mappings for `Consent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "code": "Consent.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Consent.implicitRules",
              "display": "Consent.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Consent.implicitRules` is mapped to FHIR R5 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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
            }
          ]
        },
        {
          "code": "Consent.language",
          "display": "language",
          "target": [
            {
              "code": "Consent.language",
              "display": "Consent.language",
              "relationship": "equivalent",
              "comment": "Element `Consent.language` is mapped to FHIR R5 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",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.text` is mapped to FHIR R5 element `Consent.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.text` do not cover the following types: Narrative.\nThe mappings for `Consent.text` do not cover the following types based on type expansion: div, status.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded in formation is added later."
            }
          ]
        },
        {
          "code": "Consent.contained",
          "display": "contained",
          "target": [
            {
              "code": "Consent.contained",
              "display": "Consent.contained",
              "relationship": "equivalent",
              "comment": "Element `Consent.contained` is mapped to FHIR R5 element `Consent.contained` as `SourceIsBroaderThanTarget`.\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."
            }
          ]
        },
        {
          "code": "Consent.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Consent.identifier",
              "display": "Consent.identifier",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.identifier` is mapped to FHIR R5 element `Consent.identifier` as `RelatedTo`.\nThe mappings for `Consent.identifier` do not cover the following types: Identifier.\nThe mappings for `Consent.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nThis identifier is 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",
              "relationship": "equivalent",
              "comment": "Element `Consent.status` is mapped to FHIR R5 element `Consent.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Consent.status` do not allow expression of the necessary codes, per the bindings on the source and target.\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",
              "relationship": "equivalent",
              "comment": "Element `Consent.category` is mapped to FHIR R5 element `Consent.category` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.patient",
          "display": "patient",
          "target": [
            {
              "code": "Consent.subject",
              "display": "Consent.subject",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.patient` is mapped to FHIR R5 element `Consent.subject` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.patient` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.patient` with unmapped reference targets: Patient.\nCommonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person."
            }
          ]
        },
        {
          "code": "Consent.dateTime",
          "display": "dateTime",
          "target": [
            {
              "code": "Consent.date",
              "display": "Consent.date",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.dateTime` is mapped to FHIR R5 element `Consent.date` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.dateTime` do not cover the following types: dateTime.\nThe mappings for `Consent.dateTime` do not cover the following types based on type expansion: value.\nThis is not the time of the original consent, but the time that this statement was made or derived."
            }
          ]
        },
        {
          "code": "Consent.consentingParty",
          "display": "consentingParty",
          "target": [
            {
              "code": "Consent.grantee",
              "display": "Consent.grantee",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.consentingParty` is mapped to FHIR R5 element `Consent.grantee` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.consentingParty` with unmapped reference targets: Organization, Patient, Practitioner, RelatedPerson.\nCommonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian."
            }
          ]
        },
        {
          "code": "Consent.actor",
          "display": "actor",
          "target": [
            {
              "code": "Consent.provision.actor",
              "display": "Consent.provision.actor",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.actor` is mapped to FHIR R5 element `Consent.provision.actor` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.actor.role",
          "display": "role",
          "target": [
            {
              "code": "Consent.provision.actor.role",
              "display": "Consent.provision.actor.role",
              "relationship": "equivalent",
              "comment": "Element `Consent.actor.role` is mapped to FHIR R5 element `Consent.provision.actor.role` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.actor.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.actor.reference",
              "display": "Consent.provision.actor.reference",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.actor.reference` is mapped to FHIR R5 element `Consent.provision.actor.reference` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.actor.reference` with unmapped reference targets: CareTeam, Device, Group, Organization, Patient, Practitioner, RelatedPerson."
            }
          ]
        },
        {
          "code": "Consent.action",
          "display": "action",
          "target": [
            {
              "code": "Consent.provision.action",
              "display": "Consent.provision.action",
              "relationship": "equivalent",
              "comment": "Element `Consent.action` is mapped to FHIR R5 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.policy",
          "display": "policy",
          "target": [
            {
              "code": "Consent.policyBasis",
              "display": "Consent.policyBasis",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.policy` is mapped to FHIR R5 element `Consent.policyBasis` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Consent.policyRule",
          "display": "policyRule",
          "target": [
            {
              "code": "Consent.regulatoryBasis",
              "display": "Consent.regulatoryBasis",
              "relationship": "related-to",
              "comment": "Element `Consent.policyRule` is mapped to FHIR R5 element `Consent.regulatoryBasis` as `RelatedTo`.\nThe mappings for `Consent.policyRule` do not cover the following types: uri.\nThe mappings for `Consent.policyRule` do not cover the following types based on type expansion: value.\nIf the policy reference is not known, the resource cannot be processed. Where the reference is absent, there is no particular policy other than what is expressed directly in the consent resource."
            }
          ]
        },
        {
          "code": "Consent.securityLabel",
          "display": "securityLabel",
          "target": [
            {
              "code": "Consent.provision.securityLabel",
              "display": "Consent.provision.securityLabel",
              "relationship": "equivalent",
              "comment": "Element `Consent.securityLabel` is mapped to FHIR R5 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. Not all of the security labels make sense for use in this element (may define a narrower value set?)."
            }
          ]
        },
        {
          "code": "Consent.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "Consent.provision.purpose",
              "display": "Consent.provision.purpose",
              "relationship": "equivalent",
              "comment": "Element `Consent.purpose` is mapped to FHIR R5 element `Consent.provision.purpose` as `Equivalent`.\nThis element is for discoverability / documentation, and does not modify or qualify the policy (e.g. the policy itself describes the purposes for which it applies)."
            }
          ]
        },
        {
          "code": "Consent.dataPeriod",
          "display": "dataPeriod",
          "target": [
            {
              "code": "Consent.provision.dataPeriod",
              "display": "Consent.provision.dataPeriod",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.dataPeriod` do not cover the following types: Period.\nThe mappings for `Consent.dataPeriod` do not cover the following types based on type expansion: end, start.\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.data",
          "display": "data",
          "target": [
            {
              "code": "Consent.provision.data",
              "display": "Consent.provision.data",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.data` is mapped to FHIR R5 element `Consent.provision.data` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.data.meaning",
          "display": "meaning",
          "target": [
            {
              "code": "Consent.provision.data.meaning",
              "display": "Consent.provision.data.meaning",
              "relationship": "equivalent",
              "comment": "Element `Consent.data.meaning` is mapped to FHIR R5 element `Consent.provision.data.meaning` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.data.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.data.reference",
              "display": "Consent.provision.data.reference",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.data.reference` is mapped to FHIR R5 element `Consent.provision.data.reference` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.data.reference` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.data.reference` with unmapped reference targets: Resource."
            }
          ]
        },
        {
          "code": "Consent.except",
          "display": "except",
          "target": [
            {
              "code": "Consent.provision",
              "display": "Consent.provision",
              "relationship": "related-to",
              "comment": "Element `Consent.except` is mapped to FHIR R5 element `Consent.provision` as `RelatedTo`."
            }
          ]
        },
        {
          "code": "Consent.except.period",
          "display": "period",
          "target": [
            {
              "code": "Consent.provision.period",
              "display": "Consent.provision.period",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.period` is mapped to FHIR R5 element `Consent.provision.period` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.except.period` do not cover the following types: Period.\nThe mappings for `Consent.except.period` do not cover the following types based on type expansion: end, start."
            }
          ]
        },
        {
          "code": "Consent.except.actor",
          "display": "actor",
          "target": [
            {
              "code": "Consent.provision.actor",
              "display": "Consent.provision.actor",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.actor` is mapped to FHIR R5 element `Consent.provision.actor` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.except.actor.role",
          "display": "role",
          "target": [
            {
              "code": "Consent.provision.actor.role",
              "display": "Consent.provision.actor.role",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.actor.role` is mapped to FHIR R5 element `Consent.provision.actor.role` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.except.actor.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.actor.reference",
              "display": "Consent.provision.actor.reference",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.actor.reference` is mapped to FHIR R5 element `Consent.provision.actor.reference` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.except.actor.reference` with unmapped reference targets: CareTeam, Device, Group, Organization, Patient, Practitioner, RelatedPerson."
            }
          ]
        },
        {
          "code": "Consent.except.action",
          "display": "action",
          "target": [
            {
              "code": "Consent.provision.action",
              "display": "Consent.provision.action",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.action` is mapped to FHIR R5 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.except.securityLabel",
          "display": "securityLabel",
          "target": [
            {
              "code": "Consent.provision.securityLabel",
              "display": "Consent.provision.securityLabel",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.securityLabel` is mapped to FHIR R5 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. Not all of the security labels make sense for use in this element (may define a narrower value set?)."
            }
          ]
        },
        {
          "code": "Consent.except.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "Consent.provision.purpose",
              "display": "Consent.provision.purpose",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.purpose` is mapped to FHIR R5 element `Consent.provision.purpose` as `Equivalent`.\nE.g. if the purpose is 'research', then the operational context must be research, in order for the consent to apply. Not all of the security labels make sense for use in this element (may define a narrower value set?)."
            }
          ]
        },
        {
          "code": "Consent.except.class",
          "display": "class",
          "target": [
            {
              "code": "Consent.provision.documentType",
              "display": "Consent.provision.documentType",
              "relationship": "related-to",
              "comment": "Element `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.documentType` as `Equivalent`.\nElement `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.resourceType` as `Equivalent`.\nMultiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere."
            },
            {
              "code": "Consent.provision.resourceType",
              "display": "Consent.provision.resourceType",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.documentType` as `Equivalent`.\nElement `Consent.except.class` is mapped to FHIR R5 element `Consent.provision.resourceType` as `Equivalent`.\nMultiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere."
            }
          ]
        },
        {
          "code": "Consent.except.code",
          "display": "code",
          "target": [
            {
              "code": "Consent.provision.code",
              "display": "Consent.provision.code",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Consent.except.code` is mapped to FHIR R5 element `Consent.provision.code` as `SourceIsNarrowerThanTarget`.\nTypical use of this is a Document code with class = CDA."
            }
          ]
        },
        {
          "code": "Consent.except.dataPeriod",
          "display": "dataPeriod",
          "target": [
            {
              "code": "Consent.provision.dataPeriod",
              "display": "Consent.provision.dataPeriod",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.except.dataPeriod` do not cover the following types: Period.\nThe mappings for `Consent.except.dataPeriod` do not cover the following types based on type expansion: end, start.\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.except.data",
          "display": "data",
          "target": [
            {
              "code": "Consent.provision.data",
              "display": "Consent.provision.data",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.data` is mapped to FHIR R5 element `Consent.provision.data` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.except.data.meaning",
          "display": "meaning",
          "target": [
            {
              "code": "Consent.provision.data.meaning",
              "display": "Consent.provision.data.meaning",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.data.meaning` is mapped to FHIR R5 element `Consent.provision.data.meaning` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Consent.except.data.reference",
          "display": "reference",
          "target": [
            {
              "code": "Consent.provision.data.reference",
              "display": "Consent.provision.data.reference",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.data.reference` is mapped to FHIR R5 element `Consent.provision.data.reference` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.except.data.reference` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Consent.except.data.reference` with unmapped reference targets: Resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.meta|0.1.0",
      "element": [
        {
          "code": "Consent.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.meta` is mapped to FHIR R5 element `Consent.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.meta` do not cover the following types: Meta.\nThe mappings for `Consent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.text|0.1.0",
      "element": [
        {
          "code": "Consent.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.text` is mapped to FHIR R5 element `Consent.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.text` do not cover the following types: Narrative.\nThe mappings for `Consent.text` do not cover the following types based on type expansion: div, status.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded in formation is added later."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.identifier|0.1.0",
      "element": [
        {
          "code": "Consent.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.identifier` is mapped to FHIR R5 element `Consent.identifier` as `RelatedTo`.\nThe mappings for `Consent.identifier` do not cover the following types: Identifier.\nThe mappings for `Consent.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nThis identifier is 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.period|0.1.0",
      "element": [
        {
          "code": "Consent.period",
          "display": "period",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "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 R5. Typically, this is because the element has been added (is a new element).\nThis can be a subset of the period of the original statement."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.dateTime|0.1.0",
      "element": [
        {
          "code": "Consent.dateTime",
          "display": "dateTime",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.dateTime` is mapped to FHIR R5 element `Consent.date` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.dateTime` do not cover the following types: dateTime.\nThe mappings for `Consent.dateTime` do not cover the following types based on type expansion: value.\nThis is not the time of the original consent, but the time that this statement was made or derived."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.organization|0.1.0",
      "element": [
        {
          "code": "Consent.organization",
          "display": "organization",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.organization` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.organization` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.source|0.1.0",
      "element": [
        {
          "code": "Consent.source[x]",
          "display": "source[x]",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.source[x]` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.source[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.policy.authority|0.1.0",
      "element": [
        {
          "code": "Consent.policy.authority",
          "display": "authority",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.policy.authority` has a context of Consent.policyBasis based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.policy.authority` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.policy.uri|0.1.0",
      "element": [
        {
          "code": "Consent.policy.uri",
          "display": "uri",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.policy.uri` has a context of Consent.policyBasis based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.policy.uri` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThis element is for discoverability / documentation, and does not modify or qualify the policy rules."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.policyRule|0.1.0",
      "element": [
        {
          "code": "Consent.policyRule",
          "display": "policyRule",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.policyRule` is mapped to FHIR R5 element `Consent.regulatoryBasis` as `RelatedTo`.\nThe mappings for `Consent.policyRule` do not cover the following types: uri.\nThe mappings for `Consent.policyRule` do not cover the following types based on type expansion: value.\nIf the policy reference is not known, the resource cannot be processed. Where the reference is absent, there is no particular policy other than what is expressed directly in the consent resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.dataPeriod|0.1.0",
      "element": [
        {
          "code": "Consent.dataPeriod",
          "display": "dataPeriod",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.dataPeriod` do not cover the following types: Period.\nThe mappings for `Consent.dataPeriod` do not cover the following types based on type expansion: end, start.\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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.except.type|0.1.0",
      "element": [
        {
          "code": "Consent.except.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Consent.except.type` has a context of Consent.provision based on following the parent source element upwards and mapping to `Consent`.\nElement `Consent.except.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.except.period|0.1.0",
      "element": [
        {
          "code": "Consent.except.period",
          "display": "period",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.period` is mapped to FHIR R5 element `Consent.provision.period` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.except.period` do not cover the following types: Period.\nThe mappings for `Consent.except.period` do not cover the following types based on type expansion: end, start."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Consent|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Consent.except.dataPeriod|0.1.0",
      "element": [
        {
          "code": "Consent.except.dataPeriod",
          "display": "dataPeriod",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Consent.except.dataPeriod` is mapped to FHIR R5 element `Consent.provision.dataPeriod` as `SourceIsBroaderThanTarget`.\nThe mappings for `Consent.except.dataPeriod` do not cover the following types: Period.\nThe mappings for `Consent.except.dataPeriod` do not cover the following types based on type expansion: end, start.\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."
            }
          ]
        }
      ]
    }
  ]
}