This represents statistics, certainty, both the intended and actual population, and evidence variables.

An absolute URI that is used to identify this evidence when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this summary is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the summary is stored on different servers.

Allows the evidence to be referenced by a single globally unique identifier.

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

A formal identifier that is used to identify this summary when it is represented in other formats, or referenced in a specification, model, design or an instance.

Allows externally provided and/or usable business identifiers to be easily associated with the module.

Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this summary outside of FHIR, where it is not possible to use the logical URI.

The identifier that is used to identify this version of the summary when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the summary author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

A short, descriptive, user-friendly title for the summary.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

The status of this summary. Enables tracking the life-cycle of the content.

Allows filtering of summarys s that are appropriate for use versus not.

The date (and optionally time) when the summary was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the summary changes.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the summary. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate evidence instances.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.

The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.

The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.

Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.

If specified, this date follows the original approval date.

Contact detail and role for contributor to summary.

Link or citation to artifact associated with the summary.

A free text natural language description of the evidence from a consumer's perspective.

This description can be used to capture details such as why the evidence was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the evidence as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the evidence is presumed to be the predominant language in the place the evidence was created).

Declarative description of the Evidence.

Footnotes and/or explanatory notes.

Group being referenced.

Textual description of referent group.

Footnotes and/or explanatory notes.

Various information categories of group.

Non-actual group that is a set of characteristics.

Indication of quality of match between intended group to actual group.

Evidence variable.

Description of the variable.

Footnotes and/or explanatory notes.

exposure | referenceExposure | measuredVariable | confounder.

Definition of the actual variable related to the statistic(s).

Definition of the intended variable related to the Evidence.

Indication of quality of match between intended variable to actual variable.

The particular type of synthesis if this is a synthesis summary.

The type of study that produced this summary.

The statistic value(s).

Ordered distribution.

Level of certainty.

Textual description of certainty.

Footnotes and/or explanatory notes.

Rating of certainty.

Subcomponent of certainty.

Textual description of certainty subcomponent.

Textual note of certainty subcomponent.

Footnotes and/or explanatory notes.

Rating of certainty subcomponent.