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

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

Extension: ExtensionConsent_Verification - Detailed Descriptions

Page standards status: Trial-use Maturity Level: 0

Definitions for the ext-R4-Consent.verification extension.

Guidance on how to interpret the contents of this table can be foundhere

0. Extension
Definition

R4: Consent.verification (new:BackboneElement)


Optional Extension Element - found in all resources.

ShortR4: Consent Verified by patient or family (new)Optional Extensions Element
Comments

Element Consent.verification has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Control0..*
This element is affected by the following invariants: ele-1
Is Modifierfalse
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
ele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
2. Extension.extension
Definition

An Extension


May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

ShortExtensionAdditional Content defined by implementations
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Control10..*
TypeExtension
Alternate Namesextensions, user content
SlicingThis element introduces a set of slices on Extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ url
  • 4. Extension.extension:verified
    Slice Nameverified
    Definition

    R4: Consent.verification.verified (new:boolean)

    ShortR4: Has been verified (new)Additional Content defined by implementations
    Comments

    Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control10..1*
    TypeExtension
    Requirements

    Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    6. Extension.extension:verified.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    Comments

    The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed Valueverified
    8. Extension.extension:verified.value[x]
    Definition

    Has the instruction been verified.


    Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

    ShortHas been verifiedValue of extension
    Control10..1
    Typeboolean, date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, base64Binary, Signature, unsignedInt, time, Timing, decimal, CodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    10. Extension.extension:verifiedWith
    Slice NameverifiedWith
    Definition

    R4: Consent.verification.verifiedWith (new:Reference(Patient,RelatedPerson))

    ShortR4: Person who verified (new)Additional Content defined by implementations
    Comments

    Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control0..1*
    TypeExtension
    Requirements

    Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    12. Extension.extension:verifiedWith.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    Comments

    The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed ValueverifiedWith
    14. Extension.extension:verifiedWith.value[x]
    Definition

    Who verified the instruction (Patient, Relative or other Authorized Person).


    Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

    ShortPerson who verifiedValue of extension
    Control0..1
    TypeReference(Cross-version Profile for R4.Patient for use in FHIR STU3, Patient, Cross-version Profile for R4.RelatedPerson for use in FHIR STU3, RelatedPerson), date, dateTime, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal, CodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    16. Extension.extension:verificationDate
    Slice NameverificationDate
    Definition

    R4: Consent.verification.verificationDate (new:dateTime)

    ShortR4: When consent verified (new)Additional Content defined by implementations
    Comments

    Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control0..1*
    TypeExtension
    Requirements

    Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    18. Extension.extension:verificationDate.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    Comments

    The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed ValueverificationDate
    20. Extension.extension:verificationDate.value[x]
    Definition

    Date verification was collected.


    Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

    ShortWhen consent verifiedValue of extension
    Control0..1
    TypedateTime, date, Meta, code, string, Address, Attachment, integer, oid, Count, instant, ContactPoint, HumanName, Money, Identifier, Coding, markdown, SampledData, Ratio, id, positiveInt, Age, Distance, Reference, Period, Quantity, Duration, Range, uri, Annotation, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal, CodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    22. Extension.url
    Definition

    Source of the definition for the extension code - a logical name or a URL.

    Shortidentifies the meaning of the extension
    Comments

    The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

    Control1..1
    Typeuri
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    XML FormatIn the XML format, this property is represented as an attribute.
    Fixed Valuehttp://hl7.org/fhir/4.0/StructureDefinition/extension-Consent.verification
    24. Extension.value[x]
    Definition

    Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

    ShortValue of extension
    Control0..01
    TypeChoice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

    Guidance on how to interpret the contents of this table can be foundhere

    0. Extension
    Definition

    R4: Consent.verification (new:BackboneElement)

    ShortR4: Consent Verified by patient or family (new)
    Comments

    Element Consent.verification has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control0..*
    Is Modifierfalse
    2. Extension.extension
    Control1..*
    SlicingThis element introduces a set of slices on Extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
    • value @ url
    • 4. Extension.extension:verified
      Slice Nameverified
      Definition

      R4: Consent.verification.verified (new:boolean)

      ShortR4: Has been verified (new)
      Comments

      Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control1..1
      Requirements

      Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      6. Extension.extension:verified.url
      Control1..1
      Fixed Valueverified
      8. Extension.extension:verified.value[x]
      Definition

      Has the instruction been verified.

      ShortHas been verified
      Control1..1
      Typeboolean
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
      10. Extension.extension:verifiedWith
      Slice NameverifiedWith
      Definition

      R4: Consent.verification.verifiedWith (new:Reference(Patient,RelatedPerson))

      ShortR4: Person who verified (new)
      Comments

      Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control0..1
      Requirements

      Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      12. Extension.extension:verifiedWith.url
      Control1..1
      Fixed ValueverifiedWith
      14. Extension.extension:verifiedWith.value[x]
      Definition

      Who verified the instruction (Patient, Relative or other Authorized Person).

      ShortPerson who verified
      Control0..1
      TypeReference(Cross-version Profile for R4.Patient for use in FHIR STU3, Patient, Cross-version Profile for R4.RelatedPerson for use in FHIR STU3, RelatedPerson)
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      16. Extension.extension:verificationDate
      Slice NameverificationDate
      Definition

      R4: Consent.verification.verificationDate (new:dateTime)

      ShortR4: When consent verified (new)
      Comments

      Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control0..1
      Requirements

      Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      18. Extension.extension:verificationDate.url
      Control1..1
      Fixed ValueverificationDate
      20. Extension.extension:verificationDate.value[x]
      Definition

      Date verification was collected.

      ShortWhen consent verified
      Control0..1
      TypedateTime
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
      22. Extension.url
      Control1..1
      Fixed Valuehttp://hl7.org/fhir/4.0/StructureDefinition/extension-Consent.verification
      24. Extension.value[x]
      Control0..0

      Guidance on how to interpret the contents of this table can be foundhere

      0. Extension
      Definition

      R4: Consent.verification (new:BackboneElement)

      ShortR4: Consent Verified by patient or family (new)
      Comments

      Element Consent.verification has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control0..*
      This element is affected by the following invariants: ele-1
      Is Modifierfalse
      Invariantsele-1: All FHIR elements must have a @value or children (hasValue() | (children().count() > id.count()))
      ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
      2. Extension.id
      Definition

      unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

      Shortxml:id (or equivalent in JSON)
      Control0..1
      Typestring
      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
      XML FormatIn the XML format, this property is represented as an attribute.
      4. Extension.extension
      Definition

      An Extension

      ShortExtension
      Control1..*
      TypeExtension
      SlicingThis element introduces a set of slices on Extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
      • value @ url
      • 6. Extension.extension:verified
        Slice Nameverified
        Definition

        R4: Consent.verification.verified (new:boolean)

        ShortR4: Has been verified (new)
        Comments

        Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

        Control1..1
        TypeExtension
        Requirements

        Element Consent.verification.verified is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verified has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verified has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

        8. Extension.extension:verified.id
        Definition

        unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

        Shortxml:id (or equivalent in JSON)
        Control0..1
        Typestring
        Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
        XML FormatIn the XML format, this property is represented as an attribute.
        10. Extension.extension:verified.extension
        Definition

        May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

        ShortAdditional Content defined by implementations
        Comments

        There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

        Control0..*
        TypeExtension
        Alternate Namesextensions, user content
        SlicingThis element introduces a set of slices on Extension.extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
        • value @ url
        • 12. Extension.extension:verified.url
          Definition

          Source of the definition for the extension code - a logical name or a URL.

          Shortidentifies the meaning of the extension
          Comments

          The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

          Control1..1
          Typeuri
          Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
          XML FormatIn the XML format, this property is represented as an attribute.
          Fixed Valueverified
          14. Extension.extension:verified.value[x]
          Definition

          Has the instruction been verified.

          ShortHas been verified
          Control1..1
          Typeboolean
          [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
          Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
          16. Extension.extension:verifiedWith
          Slice NameverifiedWith
          Definition

          R4: Consent.verification.verifiedWith (new:Reference(Patient,RelatedPerson))

          ShortR4: Person who verified (new)
          Comments

          Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

          Control0..1
          TypeExtension
          Requirements

          Element Consent.verification.verifiedWith is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verifiedWith has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verifiedWith has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

          18. Extension.extension:verifiedWith.id
          Definition

          unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

          Shortxml:id (or equivalent in JSON)
          Control0..1
          Typestring
          Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
          XML FormatIn the XML format, this property is represented as an attribute.
          20. Extension.extension:verifiedWith.extension
          Definition

          May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

          ShortAdditional Content defined by implementations
          Comments

          There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

          Control0..*
          TypeExtension
          Alternate Namesextensions, user content
          SlicingThis element introduces a set of slices on Extension.extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
          • value @ url
          • 22. Extension.extension:verifiedWith.url
            Definition

            Source of the definition for the extension code - a logical name or a URL.

            Shortidentifies the meaning of the extension
            Comments

            The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

            Control1..1
            Typeuri
            Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
            XML FormatIn the XML format, this property is represented as an attribute.
            Fixed ValueverifiedWith
            24. Extension.extension:verifiedWith.value[x]
            Definition

            Who verified the instruction (Patient, Relative or other Authorized Person).

            ShortPerson who verified
            Control0..1
            TypeReference(Cross-version Profile for R4.Patient for use in FHIR STU3, Patient, Cross-version Profile for R4.RelatedPerson for use in FHIR STU3, RelatedPerson)
            [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
            26. Extension.extension:verificationDate
            Slice NameverificationDate
            Definition

            R4: Consent.verification.verificationDate (new:dateTime)

            ShortR4: When consent verified (new)
            Comments

            Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

            Control0..1
            TypeExtension
            Requirements

            Element Consent.verification.verificationDate is part of an existing definition because parent element Consent.verification requires a cross-version extension. Element Consent.verification.verificationDate has a context of Consent based on following the parent source element upwards and mapping to Consent. Element Consent.verification.verificationDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

            28. Extension.extension:verificationDate.id
            Definition

            unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

            Shortxml:id (or equivalent in JSON)
            Control0..1
            Typestring
            Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
            XML FormatIn the XML format, this property is represented as an attribute.
            30. Extension.extension:verificationDate.extension
            Definition

            May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

            ShortAdditional Content defined by implementations
            Comments

            There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

            Control0..*
            TypeExtension
            Alternate Namesextensions, user content
            SlicingThis element introduces a set of slices on Extension.extension.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
            • value @ url
            • 32. Extension.extension:verificationDate.url
              Definition

              Source of the definition for the extension code - a logical name or a URL.

              Shortidentifies the meaning of the extension
              Comments

              The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

              Control1..1
              Typeuri
              Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
              XML FormatIn the XML format, this property is represented as an attribute.
              Fixed ValueverificationDate
              34. Extension.extension:verificationDate.value[x]
              Definition

              Date verification was collected.

              ShortWhen consent verified
              Control0..1
              TypedateTime
              [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
              Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
              36. Extension.url
              Definition

              Source of the definition for the extension code - a logical name or a URL.

              Shortidentifies the meaning of the extension
              Comments

              The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

              Control1..1
              Typeuri
              Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
              XML FormatIn the XML format, this property is represented as an attribute.
              Fixed Valuehttp://hl7.org/fhir/4.0/StructureDefinition/extension-Consent.verification
              38. Extension.value[x]
              Definition

              Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

              ShortValue of extension
              Control0..0
              TypeChoice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta
              Primitive ValueThis primitive element may be present, or absent, or replaced by an extension