pub struct EvidenceInner {Show 70 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub url: Option<String>,
pub url_ext: Option<FieldExtension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub version: Option<String>,
pub version_ext: Option<FieldExtension>,
pub version_algorithm: Option<EvidenceVersionAlgorithm>,
pub version_algorithm_ext: Option<EvidenceVersionAlgorithmExtension>,
pub name: Option<String>,
pub name_ext: Option<FieldExtension>,
pub title: Option<String>,
pub title_ext: Option<FieldExtension>,
pub cite_as: Option<EvidenceCiteAs>,
pub cite_as_ext: Option<EvidenceCiteAsExtension>,
pub status: PublicationStatus,
pub status_ext: Option<FieldExtension>,
pub experimental: Option<bool>,
pub experimental_ext: Option<FieldExtension>,
pub date: Option<DateTime>,
pub date_ext: Option<FieldExtension>,
pub approval_date: Option<Date>,
pub approval_date_ext: Option<FieldExtension>,
pub last_review_date: Option<Date>,
pub last_review_date_ext: Option<FieldExtension>,
pub publisher: Option<String>,
pub publisher_ext: Option<FieldExtension>,
pub contact: Vec<Option<ContactDetail>>,
pub contact_ext: Vec<Option<FieldExtension>>,
pub author: Vec<Option<ContactDetail>>,
pub author_ext: Vec<Option<FieldExtension>>,
pub editor: Vec<Option<ContactDetail>>,
pub editor_ext: Vec<Option<FieldExtension>>,
pub reviewer: Vec<Option<ContactDetail>>,
pub reviewer_ext: Vec<Option<FieldExtension>>,
pub endorser: Vec<Option<ContactDetail>>,
pub endorser_ext: Vec<Option<FieldExtension>>,
pub use_context: Vec<Option<UsageContext>>,
pub use_context_ext: Vec<Option<FieldExtension>>,
pub purpose: Option<String>,
pub purpose_ext: Option<FieldExtension>,
pub copyright: Option<String>,
pub copyright_ext: Option<FieldExtension>,
pub copyright_label: Option<String>,
pub copyright_label_ext: Option<FieldExtension>,
pub related_artifact: Vec<Option<RelatedArtifact>>,
pub related_artifact_ext: Vec<Option<FieldExtension>>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub assertion: Option<String>,
pub assertion_ext: Option<FieldExtension>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub variable_definition: Vec<Option<EvidenceVariableDefinition>>,
pub variable_definition_ext: Vec<Option<FieldExtension>>,
pub synthesis_type: Option<CodeableConcept>,
pub synthesis_type_ext: Option<FieldExtension>,
pub study_design: Vec<Option<CodeableConcept>>,
pub study_design_ext: Vec<Option<FieldExtension>>,
pub statistic: Vec<Option<EvidenceStatistic>>,
pub statistic_ext: Vec<Option<FieldExtension>>,
pub certainty: Vec<Option<EvidenceCertainty>>,
pub certainty_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
The Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence.
Evidence v5.0.0
Single evidence bit
The Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicit_rules: Option<String>A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
text: Option<Narrative>Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
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.
url: Option<String>Canonical identifier for this evidence, represented as a globally unique URI
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 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.
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.
url_ext: Option<FieldExtension>Extension field.
identifier: Vec<Option<Identifier>>Additional identifier for the summary
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.
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.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
version: Option<String>Business version of this summary
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.
version_ext: Option<FieldExtension>Extension field.
version_algorithm: Option<EvidenceVersionAlgorithm>How to compare versions
Indicates the mechanism used to compare versions to determine which is more current.
If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 is newer, and a 0 if the version ordering can’t successfully be determined.
version_algorithm_ext: Option<EvidenceVersionAlgorithmExtension>Extension field.
name: Option<String>Name for this summary (machine friendly)
A natural language name identifying the evidence. This name should be usable as an identifier for the module by machine processing applications such as code generation.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
name_ext: Option<FieldExtension>Extension field.
title: Option<String>Name for this summary (human friendly)
A short, descriptive, user-friendly title for the summary.
title_ext: Option<FieldExtension>Extension field.
cite_as: Option<EvidenceCiteAs>Citation for this evidence
Citation Resource or display of suggested citation for this evidence.
cite_as_ext: Option<EvidenceCiteAsExtension>Extension field.
status: PublicationStatusPublicationStatus; draft | active | retired | unknown
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.
See guidance around (not) making local changes to elements here.
status_ext: Option<FieldExtension>Extension field.
experimental: Option<bool>For testing purposes, not real usage
A Boolean value to indicate that this resource is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
experimental_ext: Option<FieldExtension>Extension field.
date: Option<DateTime>Date last changed
The date (and optionally time) when the summary was last significantly changed. 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.
The date is often not tracked until the resource is published, but may be present on draft content. 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.
See guidance around (not) making local changes to elements here.
date_ext: Option<FieldExtension>Extension field.
approval_date: Option<Date>When the summary was approved by publisher
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.
See guidance around (not) making local changes to elements here.
approval_date_ext: Option<FieldExtension>Extension field.
last_review_date: Option<Date>When the summary was last reviewed by the publisher
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
If specified, this date follows the original approval date.
See guidance around (not) making local changes to elements here.
last_review_date_ext: Option<FieldExtension>Extension field.
publisher: Option<String>Name of the publisher/steward (organization or individual)
The name of the organization or individual responsible for the release and ongoing maintenance of the evidence.
Usually an organization but may be an individual. The publisher (or steward) of the evidence is the organization or individual primarily responsible for the maintenance and upkeep of the evidence. 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. This item SHOULD be populated unless the information is available from context.
publisher_ext: Option<FieldExtension>Extension field.
contact: Vec<Option<ContactDetail>>Contact details for the publisher
Contact details to assist a user in finding and communicating with the publisher.
Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see Clinical Reasoning Module).
See guidance around (not) making local changes to elements here.
contact_ext: Vec<Option<FieldExtension>>Extension field.
Who authored the content
An individiual, organization, or device primarily involved in the creation and maintenance of the content.
Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see Clinical Reasoning Module).
Extension field.
editor: Vec<Option<ContactDetail>>Who edited the content
An individiual, organization, or device primarily responsible for internal coherence of the content.
Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see Clinical Reasoning Module).
editor_ext: Vec<Option<FieldExtension>>Extension field.
reviewer: Vec<Option<ContactDetail>>Who reviewed the content
An individiual, organization, or device primarily responsible for review of some aspect of the content.
Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see Clinical Reasoning Module).
See guidance around (not) making local changes to elements here.
reviewer_ext: Vec<Option<FieldExtension>>Extension field.
endorser: Vec<Option<ContactDetail>>Who endorsed the content
An individiual, organization, or device responsible for officially endorsing the content for use in some setting.
Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see Clinical Reasoning Module).
See guidance around (not) making local changes to elements here.
endorser_ext: Vec<Option<FieldExtension>>Extension field.
use_context: Vec<Option<UsageContext>>The context that the content is intended to support
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.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
use_context_ext: Vec<Option<FieldExtension>>Extension field.
purpose: Option<String>Why this Evidence is defined
Explanation of why this Evidence is needed and why it has been designed as it has.
This element does not describe the usage of the Evidence. Instead, it provides traceability of ’‘why’’ the resource is either needed or ’‘why’’ it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this Evidence.
purpose_ext: Option<FieldExtension>Extension field.
copyright: Option<String>Use and/or publishing restrictions
A copyright statement relating to the Evidence and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the Evidence.
The short copyright declaration (e.g. (c) ‘2015+ xyz organization’ should be sent in the copyrightLabel element.
copyright_ext: Option<FieldExtension>Extension field.
copyright_label: Option<String>Copyright holder and year(s)
A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. ‘All rights reserved’, ‘Some rights reserved’).
The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general ‘copyright’ element.
copyright_label_ext: Option<FieldExtension>Extension field.
Link or citation to artifact associated with the summary
Link or citation to artifact associated with the summary.
Extension field.
description: Option<String>Description of the particular 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 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).
description_ext: Option<FieldExtension>Extension field.
assertion: Option<String>Declarative description of the Evidence
Declarative description of the Evidence.
assertion_ext: Option<FieldExtension>Extension field.
note: Vec<Option<Annotation>>Footnotes and/or explanatory notes
Footnotes and/or explanatory notes.
note_ext: Vec<Option<FieldExtension>>Extension field.
variable_definition: Vec<Option<EvidenceVariableDefinition>>Evidence variable such as population, exposure, or outcome
Evidence variable such as population, exposure, or outcome.
variable_definition_ext: Vec<Option<FieldExtension>>Extension field.
synthesis_type: Option<CodeableConcept>SynthesisType; The method to combine studies
The method to combine studies.
synthesis_type_ext: Option<FieldExtension>Extension field.
study_design: Vec<Option<CodeableConcept>>StudyDesign; The design of the study that produced this evidence
The design of the study that produced this evidence. The design is described with any number of study design characteristics.
study_design_ext: Vec<Option<FieldExtension>>Extension field.
statistic: Vec<Option<EvidenceStatistic>>Values and parameters for a single statistic
Values and parameters for a single statistic.
statistic_ext: Vec<Option<FieldExtension>>Extension field.
certainty: Vec<Option<EvidenceCertainty>>Certainty or quality of the evidence
Assessment of certainty, confidence in the estimates, or quality of the evidence.
certainty_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for EvidenceInner
impl Clone for EvidenceInner
Source§fn clone(&self) -> EvidenceInner
fn clone(&self) -> EvidenceInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more