pub struct ConditionInner {Show 40 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 clinical_status: CodeableConcept,
pub clinical_status_ext: Option<FieldExtension>,
pub verification_status: Option<CodeableConcept>,
pub verification_status_ext: Option<FieldExtension>,
pub category: Vec<Option<CodeableConcept>>,
pub category_ext: Vec<Option<FieldExtension>>,
pub severity: Option<CodeableConcept>,
pub severity_ext: Option<FieldExtension>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub body_site: Vec<Option<CodeableConcept>>,
pub body_site_ext: Vec<Option<FieldExtension>>,
pub subject: Reference,
pub subject_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub onset: Option<ConditionOnset>,
pub onset_ext: Option<ConditionOnsetExtension>,
pub abatement: Option<ConditionAbatement>,
pub abatement_ext: Option<ConditionAbatementExtension>,
pub recorded_date: Option<DateTime>,
pub recorded_date_ext: Option<FieldExtension>,
pub participant: Vec<Option<ConditionParticipant>>,
pub participant_ext: Vec<Option<FieldExtension>>,
pub stage: Vec<Option<ConditionStage>>,
pub stage_ext: Vec<Option<FieldExtension>>,
pub evidence: Vec<Option<CodeableReference>>,
pub evidence_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
Condition v5.0.0
Detailed information about conditions, problems or diagnoses
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
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>>External Ids for this condition
Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
clinical_status: CodeableConceptConditionClinicalStatus; active | recurrence | relapse | inactive | remission | resolved | unknown
The clinical status of the condition.
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown
clinical_status_ext: Option<FieldExtension>Extension field.
verification_status: Option<CodeableConcept>ConditionVerificationStatus; unconfirmed | provisional | differential | confirmed | refuted | entered-in-error
The verification status to support the clinical status of the condition. The verification status pertains to the condition, itself, not to any specific condition attribute.
verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.
verification_status_ext: Option<FieldExtension>Extension field.
category: Vec<Option<CodeableConcept>>ConditionCategory; problem-list-item | encounter-diagnosis
A category assigned to the condition.
The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.
category_ext: Vec<Option<FieldExtension>>Extension field.
severity: Option<CodeableConcept>ConditionSeverity; Subjective severity of condition
A subjective assessment of the severity of the condition as evaluated by the clinician.
Coding of the severity with a terminology is preferred, where possible.
severity_ext: Option<FieldExtension>Extension field.
code: Option<CodeableConcept>ConditionKind; Identification of the condition, problem or diagnosis
Identification of the condition, problem or diagnosis.
code_ext: Option<FieldExtension>Extension field.
body_site: Vec<Option<CodeableConcept>>BodySite; Anatomical location, if relevant
The anatomical location where this condition manifests itself.
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodyStructure resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/bodySite. May be a summary code, or a reference to a very precise definition of the location, or both.
body_site_ext: Vec<Option<FieldExtension>>Extension field.
subject: ReferenceWho has the condition?
Indicates the patient or group who the condition record is associated with.
subject_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>The Encounter during which this Condition was created
The Encounter during which this Condition was created or to which the creation of this record is tightly associated.
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a “new” diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first “known”.
encounter_ext: Option<FieldExtension>Extension field.
onset: Option<ConditionOnset>Estimated or actual date, date-time, or age
Estimated or actual date or date-time the condition began, in the opinion of the clinician.
Age is generally used when the patient reports an age at which the Condition began to occur. Period is generally used to convey an imprecise onset that occurred within the time period. For example, Period is not intended to convey the transition period before the chronic bronchitis or COPD condition was diagnosed, but Period can be used to convey an imprecise diagnosis date. Range is generally used to convey an imprecise age range (e.g. 4 to 6 years old). Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject’s lifetime) or when asthma transitioned to become severe.
onset_ext: Option<ConditionOnsetExtension>Extension field.
abatement: Option<ConditionAbatement>When in resolution/remission
The date or estimated date that the condition resolved or went into remission. This is called “abatement” because of the many overloaded connotations associated with “remission” or “resolution” - Some conditions, such as chronic conditions, are never really resolved, but they can abate.
There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject’s lifetime) or when asthma transitioned to become severe.
abatement_ext: Option<ConditionAbatementExtension>Extension field.
recorded_date: Option<DateTime>Date condition was first recorded
The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.
When onset date is unknown, recordedDate can be used to establish if the condition was present on or before a given date. If the recordedDate is known and provided by a sending system, it is preferred that the receiving system preserve that recordedDate value. If the recordedDate is not provided by the sending system, the receipt timestamp is sometimes used as the recordedDate.
recorded_date_ext: Option<FieldExtension>Extension field.
participant: Vec<Option<ConditionParticipant>>Who or what participated in the activities related to the condition and how they were involved
Indicates who or what participated in the activities related to the condition and how they were involved.
participant_ext: Vec<Option<FieldExtension>>Extension field.
stage: Vec<Option<ConditionStage>>Stage/grade, usually assessed formally
A simple summary of the stage such as “Stage 3” or “Early Onset”. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer’s, or Parkinson disease.
stage_ext: Vec<Option<FieldExtension>>Extension field.
evidence: Vec<Option<CodeableReference>>ManifestationOrSymptom; Supporting evidence for the verification status
Supporting evidence / manifestations that are the basis of the Condition’s verification status, such as evidence that confirmed or refuted the condition.
If the condition was confirmed, but subsequently refuted, then the evidence can be cumulative including all evidence over time. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. For example, if the Condition.code is pneumonia, then there could be an evidence list where Condition.evidence.concept = fever (CodeableConcept), Condition.evidence.concept = cough (CodeableConcept), and Condition.evidence.reference = bronchitis (reference to Condition).
evidence_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Additional information about the Condition
Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.
note_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for ConditionInner
impl Clone for ConditionInner
Source§fn clone(&self) -> ConditionInner
fn clone(&self) -> ConditionInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more