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

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

Extension: ExtensionPermission_Justification - Detailed Descriptions

Page standards status: Trial-use Maturity Level: 0

Definitions for the ext-R5-Permission.justification extension.

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

0. Extension
Definition

R5: Permission.justification (new:BackboneElement)


Optional Extension Element - found in all resources.

ShortR5: The asserted justification for using the data (new)Optional Extensions Element
Comments

Element Permission.justification is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Control0..1*
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.

Control0..*
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:basis
    Slice Namebasis
    Definition

    R5: Permission.justification.basis (new:CodeableConcept)

    ShortR5: The regulatory grounds upon which this Permission builds (new)Additional Content defined by implementations
    Comments

    Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control0..*
    TypeExtension
    Requirements

    Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    6. Extension.extension:basis.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 Valuebasis
    8. Extension.extension:basis.value[x]
    Definition

    This would be a codeableconcept, or a coding, which can be constrained to , for example, the 6 grounds for processing in GDPR.


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

    ShortThe regulatory grounds upon which this Permission buildsValue of extension
    Control0..1
    BindingFor example codes, see For codes, see R5ConsentPolicyForR3 (0.1.0)
    (example to http://hl7.org/fhir/uv/xver/ValueSet/R5-consent-policy-for-R3|0.1.0)

    Regulatory policy examples

    TypeCodeableConcept, 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, boolean, base64Binary, Signature, unsignedInt, time, Timing, decimal
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    10. Extension.extension:evidence
    Slice Nameevidence
    Definition

    R5: Permission.justification.evidence (new:Reference(Resource))

    ShortR5: Justifing rational (new)Additional Content defined by implementations
    Comments

    Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

    Control0..*
    TypeExtension
    Requirements

    Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    12. Extension.extension:evidence.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 Valueevidence
    14. Extension.extension:evidence.value[x]
    Definition

    Justifing rational.


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

    ShortJustifing rationalValue of extension
    Comments

    While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

    Control0..1
    TypeReference(Cross-version Profile for R5.Resource for use in FHIR STU3, Resource), 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.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/5.0/StructureDefinition/extension-Permission.justification
    18. 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

    R5: Permission.justification (new:BackboneElement)

    ShortR5: The asserted justification for using the data (new)
    Comments

    Element Permission.justification is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

    Control0..1
    Is Modifierfalse
    2. Extension.extension
    Control0..*
    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:basis
      Slice Namebasis
      Definition

      R5: Permission.justification.basis (new:CodeableConcept)

      ShortR5: The regulatory grounds upon which this Permission builds (new)
      Comments

      Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control0..*
      Requirements

      Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      6. Extension.extension:basis.url
      Control1..1
      Fixed Valuebasis
      8. Extension.extension:basis.value[x]
      Definition

      This would be a codeableconcept, or a coding, which can be constrained to , for example, the 6 grounds for processing in GDPR.

      ShortThe regulatory grounds upon which this Permission builds
      Control0..1
      BindingFor example codes, see R5ConsentPolicyForR3 (0.1.0)
      (example to http://hl7.org/fhir/uv/xver/ValueSet/R5-consent-policy-for-R3|0.1.0)

      Regulatory policy examples

      TypeCodeableConcept
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      10. Extension.extension:evidence
      Slice Nameevidence
      Definition

      R5: Permission.justification.evidence (new:Reference(Resource))

      ShortR5: Justifing rational (new)
      Comments

      Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

      Control0..*
      Requirements

      Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      12. Extension.extension:evidence.url
      Control1..1
      Fixed Valueevidence
      14. Extension.extension:evidence.value[x]
      Definition

      Justifing rational.

      ShortJustifing rational
      Comments

      While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

      Control0..1
      TypeReference(Cross-version Profile for R5.Resource for use in FHIR STU3, Resource)
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      16. Extension.url
      Control1..1
      Fixed Valuehttp://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.justification
      18. Extension.value[x]
      Control0..0

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

      0. Extension
      Definition

      R5: Permission.justification (new:BackboneElement)

      ShortR5: The asserted justification for using the data (new)
      Comments

      Element Permission.justification is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

      Control0..1
      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
      Control0..*
      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:basis
        Slice Namebasis
        Definition

        R5: Permission.justification.basis (new:CodeableConcept)

        ShortR5: The regulatory grounds upon which this Permission builds (new)
        Comments

        Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

        Control0..*
        TypeExtension
        Requirements

        Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.basis is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

        8. Extension.extension:basis.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:basis.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:basis.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 Valuebasis
          14. Extension.extension:basis.value[x]
          Definition

          This would be a codeableconcept, or a coding, which can be constrained to , for example, the 6 grounds for processing in GDPR.

          ShortThe regulatory grounds upon which this Permission builds
          Control0..1
          BindingFor example codes, see R5ConsentPolicyForR3 (0.1.0)
          (example to http://hl7.org/fhir/uv/xver/ValueSet/R5-consent-policy-for-R3|0.1.0)

          Regulatory policy examples

          TypeCodeableConcept
          [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
          16. Extension.extension:evidence
          Slice Nameevidence
          Definition

          R5: Permission.justification.evidence (new:Reference(Resource))

          ShortR5: Justifing rational (new)
          Comments

          Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

          Control0..*
          TypeExtension
          Requirements

          Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension. Element Permission.justification.evidence is not mapped to FHIR STU3, since FHIR R5 Permission is not mapped. Element Permission.justification.evidence has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

          18. Extension.extension:evidence.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:evidence.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:evidence.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 Valueevidence
            24. Extension.extension:evidence.value[x]
            Definition

            Justifing rational.

            ShortJustifing rational
            Comments

            While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent

            Control0..1
            TypeReference(Cross-version Profile for R5.Resource for use in FHIR STU3, Resource)
            [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
            26. 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/5.0/StructureDefinition/extension-Permission.justification
            28. 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