pub struct DetectedIssueInner {Show 36 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 identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub status: DetectedIssueStatus,
pub status_ext: Option<FieldExtension>,
pub category: Vec<Option<CodeableConcept>>,
pub category_ext: Vec<Option<FieldExtension>>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub severity: Option<DetectedIssueSeverity>,
pub severity_ext: Option<FieldExtension>,
pub subject: Option<Reference>,
pub subject_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub identified: Option<DetectedIssueIdentified>,
pub identified_ext: Option<DetectedIssueIdentifiedExtension>,
pub author: Option<Reference>,
pub author_ext: Option<FieldExtension>,
pub implicated: Vec<Option<Reference>>,
pub implicated_ext: Vec<Option<FieldExtension>>,
pub evidence: Vec<Option<DetectedIssueEvidence>>,
pub evidence_ext: Vec<Option<FieldExtension>>,
pub detail: Option<String>,
pub detail_ext: Option<FieldExtension>,
pub reference: Option<String>,
pub reference_ext: Option<FieldExtension>,
pub mitigation: Vec<Option<DetectedIssueMitigation>>,
pub mitigation_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc.
DetectedIssue v5.0.0
Clinical issue with action
Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc.
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.
identifier: Vec<Option<Identifier>>Unique id for the detected issue
Business identifier associated with the detected issue record.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
status: DetectedIssueStatusDetectedIssueStatus; preliminary | final | entered-in-error | mitigated
Indicates the status of the detected issue.
This element is labeled as a modifier because the status contains the code entered-in-error that marks the issue as not currently valid.
status_ext: Option<FieldExtension>Extension field.
category: Vec<Option<CodeableConcept>>DetectedIssueCategory; Type of detected issue, e.g. drug-drug, duplicate therapy, etc
A code that classifies the general type of detected issue.
In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set.
category_ext: Vec<Option<FieldExtension>>Extension field.
code: Option<CodeableConcept>DetectedIssueCategory; Specific type of detected issue, e.g. drug-drug, duplicate therapy, etc
Identifies the specific type of issue identified.
code_ext: Option<FieldExtension>Extension field.
severity: Option<DetectedIssueSeverity>DetectedIssueSeverity; high | moderate | low
Indicates the degree of importance associated with the identified issue based on the potential impact on the patient.
severity_ext: Option<FieldExtension>Extension field.
subject: Option<Reference>Associated subject
Indicates the subject whose record the detected issue is associated with.
subject_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>Encounter detected issue is part of
The encounter during which this issue was detected.
This will typically be the encounter the DetectedIssue was created during, but some DetectedIssues may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests).
encounter_ext: Option<FieldExtension>Extension field.
identified: Option<DetectedIssueIdentified>When identified
The date or period when the detected issue was initially identified.
identified_ext: Option<DetectedIssueIdentifiedExtension>Extension field.
The provider or device that identified the issue
Individual or device responsible for the issue being raised. For example, a decision support application or a pharmacist conducting a medication review.
Extension field.
implicated: Vec<Option<Reference>>Problem resource
Indicates the resource representing the current activity or proposed activity that is potentially problematic.
There’s an implicit constraint on the number of implicated resources based on DetectedIssue.type; e.g. For drug-drug, there would be more than one. For timing, there would typically only be one.
implicated_ext: Vec<Option<FieldExtension>>Extension field.
evidence: Vec<Option<DetectedIssueEvidence>>Supporting evidence
Supporting evidence or manifestations that provide the basis for identifying the detected issue such as a GuidanceResponse or MeasureReport.
evidence_ext: Vec<Option<FieldExtension>>Extension field.
detail: Option<String>Description and context
A textual explanation of the detected issue.
Should focus on information not covered elsewhere as discrete data - no need to duplicate the narrative.
detail_ext: Option<FieldExtension>Extension field.
reference: Option<String>Authority for issue
The literature, knowledge-base or similar reference that describes the propensity for the detected issue identified.
reference_ext: Option<FieldExtension>Extension field.
mitigation: Vec<Option<DetectedIssueMitigation>>Step taken to address
Indicates an action that has been taken or is committed to reduce or eliminate the likelihood of the risk identified by the detected issue from manifesting. Can also reflect an observation of known mitigating factors that may reduce/eliminate the need for any action.
mitigation_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for DetectedIssueInner
impl Clone for DetectedIssueInner
Source§fn clone(&self) -> DetectedIssueInner
fn clone(&self) -> DetectedIssueInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more