The EvidenceReport Resource is a specialized container for a collection of resources and codable concepts, adapted to support compositions of Evidence, EvidenceVariable, and Citation resources and related concepts.

An absolute URI that is used to identify this EvidenceReport 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 EvidenceReport 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.

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

Allows filtering of EvidenceReports that are appropriate for use versus not.

Allows filtering of summaries that are appropriate for use versus not.

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 report instances.

Assist in searching for appropriate content.

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

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

Allows externally provided and/or usable identifiers to be associated with this EvidenceReport.

This element will contain unique identifiers that support de-duplication of EvidenceReports. This identifier can be valid for only one EvidenceReport resource.

A formal identifier that is used to identify things closely related to this EvidenceReport.

Allows externally provided and/or usable identifiers to be associated with this EvidenceReport.

May include trial registry identifiers, e.g. NCT04372602 from clinicaltrials.gov. This identifier can be valid for multiple EvidenceReport resources.

Citation Resource or display of suggested citation for this report.

used for reports for which external citation is expected, such as use in support of scholarly publications.

Specifies the kind of report, such as grouping of classifiers, search results, or human-compiled expression.

May be used in searching and filtering.

Used for footnotes and annotations.

Link, description or reference to artifact associated with the report.

Specifies the subject or focus of the report. Answers "What is this report about?".

May be used as an expression for search queries and search results

Characteristic.

Characteristic code.

Example 1 is a Citation. Example 2 is a type of outcome. Example 3 is a specific outcome.

Characteristic value.

Example 1 is Citation #37. Example 2 is selecting clinical outcomes. Example 3 is 1-year mortality.

Is used to express not the characteristic.

Timeframe for the characteristic.

Used for general notes and annotations not coded elsewhere.

The name of the organization or individual that published the evidence report.

Helps establish the "authority/credibility" of the evidence report. May also allow for contact.

Usually an organization but may be an individual. The publisher (or steward) of the evidence report is the organization or individual primarily responsible for the maintenance and upkeep of the evidence report. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the evidence report. This item SHOULD be populated unless the information is available from context.

Contact details to assist a user in finding and communicating with the publisher.

Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

An individiual, organization, or device primarily involved in the creation and maintenance of the content.

Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

An individiual, organization, or device primarily responsible for internal coherence of the content.

Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

An individiual, organization, or device primarily responsible for review of some aspect of the content.

Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

An individiual, organization, or device responsible for officially endorsing the content for use in some setting.

Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Relationships that this composition has with other compositions or documents that already exist.

A document is a version specific composition.

The type of relationship that this composition has with anther composition or document.

If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.

The target composition/document of this relationship.

The root of the sections that make up the composition.

The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents.

Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.

The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section.

A code identifying the kind of content contained within the section. This should be consistent with the section title.

Provides computable standardized labels to sections within the document.

The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.

If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.

A definitional Resource identifying the kind of content contained within the section. This should be consistent with the section title.

Identifies who is responsible for the information in this section, not necessarily who typed it in.

Identifies who is responsible for the content.

A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is peferred to contain sufficient detail to make it acceptable for a human to just read the narrative.

Document profiles may define what content should be represented in the narrative.

How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.

Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.

This element is labeled as a modifier because a change list must not be misunderstood as a complete list.

Specifies the order applied to the items in the section entries.

Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries.

Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.

Specifies any type of classification of the evidence report.

May be used in searching and filtering, or may be the key content of the report.

A reference to the actual resource from which the narrative in the section is derived.

If there are no entries in the list, an emptyReason SHOULD be provided.

Quantity as content.

If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.

Allows capturing things like "none exist" or "not asked" which can be important for most lists.

The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.

A nested sub-section within this section.

Nested sections are primarily used to help human readers navigate to particular portions of the document.