FHIR Extensions Pack
5.3.0-ballot-tc1 - (September 2025 Ballot) International flag

This page is part of the FHIR Core Extensions Registry (v5.3.0-ballot-tc1: Release 5.3) based on FHIR (HL7® FHIR® Standard) v5.0.0. This version is a pre-release. The current official version is 5.2.0. For a full list of available versions, see the Directory of published versions

Extension: Feature Assertion (Experimental)

Official URL: http://hl7.org/fhir/StructureDefinition/feature-assertion Version: 5.3.0-ballot-tc1
Standards status: Draft Maturity Level: 0 Computable Name: FeatureAsssertion

This extension asserts that the data in a resource was authored (collected/handled/created/transformed) by an application that claims conformance to the definition of a feature. Note that 'authoring' is often a client function, but that is not always the case.

For further information about features, see the Application Feature Framework Implementation Guide.

As an example of the kind of use this extension might support, an application could choose to only use value set expansions that are explicitly labeled as 'prepared under the conformance rules defined in the CRMI implementation guide. This extension is a statement about the provenance of a particular version of the resource that it is describing; as such, it should be made in a Provenance resource referring to that particular version. Alternatively, the extension can be placed in the resource about which the assertion is made (in Resource.meta); in this case, the assertion SHOULD be removed when the resource data is altered (it may be replaced by a new assertion).

This assertion is often used to drive processing rules associated with the trustworthiness of the data in the resource. Applications/specifications/workflows that make use of this assertion should carefully consider the integrity of the chain of handling from the source the processing before choosing to trust the assertion.

A more complex alternative to this profile is to use the Obligations Profile extension.

This is an experimental extension definition; the definition is intended for testing purposes, education or evaluation, and the definition is not anticipated to be matured to a point where it is intended for genuine usage.

Context of Use

This extension may be used on the following element(s)

Usage info

Usages:

  • This Extension is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Changes since version 5.2.0:

  • No changes

    • Formal Views of Extension Content

    Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

    This structure is derived from Extension

    Summary

    Simple Extension with the type Coding: This extension asserts that the data in a resource was authored (collected/handled/created/transformed) by an application that claims conformance to the definition of a feature. Note that 'authoring' is often a client function, but that is not always the case.

    For further information about features, see the Application Feature Framework Implementation Guide.

    As an example of the kind of use this extension might support, an application could choose to only use value set expansions that are explicitly labeled as 'prepared under the conformance rules defined in the CRMI implementation guide. This extension is a statement about the provenance of a particular version of the resource that it is describing; as such, it should be made in a Provenance resource referring to that particular version. Alternatively, the extension can be placed in the resource about which the assertion is made (in Resource.meta); in this case, the assertion SHOULD be removed when the resource data is altered (it may be replaced by a new assertion).

    This assertion is often used to drive processing rules associated with the trustworthiness of the data in the resource. Applications/specifications/workflows that make use of this assertion should carefully consider the integrity of the chain of handling from the source the processing before choosing to trust the assertion.

    A more complex alternative to this profile is to use the Obligations Profile extension.

    Maturity: 0

    This structure is derived from Extension

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Extension 0..* Extension Authored by an application conforming to a set of obligations
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/feature-assertion"
    ... value[x] 1..1 Coding A code that identifies a feature

    doco Documentation for this format
    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Extension 0..* Extension Authored by an application conforming to a set of obligations
    ... id 0..1 id Unique id for inter-element referencing
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/feature-assertion"

    doco Documentation for this format

    This structure is derived from Extension

    Summary

    Simple Extension with the type Coding: This extension asserts that the data in a resource was authored (collected/handled/created/transformed) by an application that claims conformance to the definition of a feature. Note that 'authoring' is often a client function, but that is not always the case.

    For further information about features, see the Application Feature Framework Implementation Guide.

    As an example of the kind of use this extension might support, an application could choose to only use value set expansions that are explicitly labeled as 'prepared under the conformance rules defined in the CRMI implementation guide. This extension is a statement about the provenance of a particular version of the resource that it is describing; as such, it should be made in a Provenance resource referring to that particular version. Alternatively, the extension can be placed in the resource about which the assertion is made (in Resource.meta); in this case, the assertion SHOULD be removed when the resource data is altered (it may be replaced by a new assertion).

    This assertion is often used to drive processing rules associated with the trustworthiness of the data in the resource. Applications/specifications/workflows that make use of this assertion should carefully consider the integrity of the chain of handling from the source the processing before choosing to trust the assertion.

    A more complex alternative to this profile is to use the Obligations Profile extension.

    Maturity: 0

    Differential View

    This structure is derived from Extension

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Extension 0..* Extension Authored by an application conforming to a set of obligations
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/feature-assertion"
    ... value[x] 1..1 Coding A code that identifies a feature

    doco Documentation for this format

    Snapshot View

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Extension 0..* Extension Authored by an application conforming to a set of obligations
    ... id 0..1 id Unique id for inter-element referencing
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/feature-assertion"

    doco Documentation for this format

     

    Other representations of profile: CSV, Excel, Schematron

    Constraints

    IdGradePath(s)DetailsRequirements
    ele-1error**ALL** elementsAll FHIR elements must have a @value or children
    : hasValue() or (children().count() > id.count())
    ext-1error**ALL** extensionsMust have either extensions or value[x], not both
    : extension.exists() != value.exists()

    R4B

    The extension is unchanged in R4B

    R4

    The extension is unchanged in R4

    R3

    The extension is unchanged in R3

    Search Parameters for this Extension

    (none found)