Generated Narrative: StructureDefinition condition-eu-core Name Flags Card. Type Description & Constraints Condition 0..* Condition Detailed information about conditions, problems or diagnoses #xD; language 0..1 code Language of the condition content #xD; text 0..1 Narrative Text summary of the resource, for human interpretation #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:assertedDate 0..1 (Complex) Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted URL: http://hl7.org/fhir/StructureDefinition/condition-assertedDate #xD; value[x] 1..1 dateTime Date and time of the diagnosis assertion #xD; extension:relatedArtifact 0..* RelatedArtifact Additional documentation, citations, etc. URL: http://hl7.org/fhir/StructureDefinition/artifact-relatedArtifact #xD; identifier 0..* Identifier External Ids for this condition #xD; <a href="StructureDefinition-condition-eu-core-definitions.html#Condition.clinicalStatus" title="The problem status describes the condition of the problem:#xA;#xD;#xD;#xA;1.#x9;Active problems are problems of which the patient experiences symptoms or for which evidence exists.#xA;#xD;#xD;#xA;2.#x9;If condition is abated, then clinicalStatus must be either inactive, resolved, or remission. #xA;#xD;#xD;#xA;3.#x9;Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore.">clinicalStatus 1..1 CodeableConcept active | recurrence | relapse | inactive | remission | resolved | unknown Binding: ConditionClinicalStatusCodes (required) #xD; verificationStatus 0..1 CodeableConcept unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ConditionVerificationStatus (required) #xD; category 0..* CodeableConcept Category #xD; severity 0..1 CodeableConcept Subjective severity of condition Binding: ConditionDiagnosisSeverity (preferred) #xD; code 1..1 CodeableConcept Identification of the condition, problem or diagnosis Binding: Problems - IPS (preferred) Additional Bindings Purpose eHDSI Illness and Disorder Preferred #xD; bodySite C 0..* CodeableConcept Anatomical location, if relevant Binding: SNOMEDCTBodyStructures (preferred) Constraints: eu-bodysite-1 #xD; Slices for extension Content/Rules for all slices #xD; extension:bodySite 0..1 (Complex) Target anatomic location or structure URL: http://hl7.org/fhir/StructureDefinition/bodySite #xD; value[x] 1..1 Reference(BodyStructure (EU core)) Value of extension #xD; subject 1..1 Reference(Patient (EU core)) Who has the condition? #xD; Slices for onset[x] 0..1 dateTime, Age, Period, Range, string Estimated or actual date, date-time, or age Slice: Unordered, Open by type:$this #xD; onset[x]:onsetDateTime 0..1 dateTime Estimated or actual date, date-time, or age #xD; Slices for abatement[x] 0..1 dateTime, Age, Period, Range, string When in resolution/remission Slice: Unordered, Open by type:$this #xD; abatement[x]:abatementDateTime 0..1 dateTime When in resolution/remission #xD; recordedDate 0..1 dateTime Date when the condition record was created #xD; participant #xD; actor 1..1 Reference(PractitionerRole (EU base) | Practitioner (EU base) | Patient (EU core) | RelatedPerson | Device | Organization (EU core) | CareTeam) Who or what participated in the activities related to the allergy (e.g. asserter, reporter) #xD; stage 0..* BackboneElement Stage/grade #xD; summary 0..1 CodeableConcept Most recent Stage Group #xD; assessment 0..* Reference(ClinicalImpression | DiagnosticReport | Observation) Formal record of assessment #xD; type 0..1 CodeableConcept Staging system used. #xD; note 0..* Annotation Additional information about the Condition #xD; Documentation for this format
This profile introduces essential constraints and extensions for the Condition resource that apply across multiple use cases.
Copyright HL7 Europe. Licensed under creative commons public domain (CC0 1.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.
If category is problems list item, the clinicalStatus should not be unknown
category.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-category' and code='problem-list-item').exists() implies clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and code='unknown').exists().not()
If condition is abated, then clinicalStatus must be either inactive, resolved, or remission.
abatement.exists() implies (clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='inactive' or code='resolved' or code='remission')).exists())
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Entity, Role, or Act,Observation[classCode=OBS, moodCode=EVN, code=ASSERTION, value<Diagnosis]
< 243796009 |Situation with explicit context| : 246090004 |Associated finding| = ( ( < 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 272379006 |Event|)
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.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
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 summary of the resource, for human interpretation
Human readable specification of the problem. This is a general notes/comments entry for description of the problem, its diagnosis and prognosis.
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.
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.
Must have either extensions or value[x], not both
Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted
When the asserter identified the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern. For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain. Asserted date supports the recognition that information is not always entered in a system immediately. Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time. If this difference is significant for your use case, assertion date may be useful.
The assertedDate is in the context of the recording practitioner and might not be the same as the recordedDate.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Date and time of the diagnosis assertion
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).
Additional documentation, citations, etc.
Related artifacts such as additional documentation, justification, dependencies, bibliographic references, and predecessor and successor artifacts.
Each related artifact is either an attachment, or a reference to another resource, but not both.
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.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Globally unique identifier of this problem 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](http://hl7.org/fhir/R5/resource.html#identifiers)). 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.
Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.
active | recurrence | relapse | inactive | remission | resolved | unknown
The problem status describes the condition of the problem: 1. Active problems are problems of which the patient experiences symptoms or for which evidence exists. 2. If condition is abated, then clinicalStatus must be either inactive, resolved, or remission. 3. Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore.
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
This element is labeled as a modifier because the status contains codes that mark the condition as no longer active.
Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="clinicalStatus", moodCode=EVN].value
unconfirmed | provisional | differential | confirmed | refuted | entered-in-error
The verification status to support the clinical status of the condition.
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.
This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.
Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="verificationStatus", moodCode=EVN].value
The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.
'problem' if from PRB-3. 'diagnosis' if from DG1 segment in PV1 message
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.
Can be pre/post-coordinated into value. Or ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="severity"].value
Identification of the condition, problem or diagnosis
Identification of the condition, problem or diagnosis.
0..1 to account for primarily narrative only resources.
Additional conformance binding to a problem code when ICD-10 or Orphanet codes are used.
(< 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 413350009 |Finding with explicit context| OR < 272379006 |Event|
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](http://hl7.org/fhir/extensions/StructureDefinition-bodySite.html). May be a summary code, or a reference to a very precise definition of the location, or both.
Either a body site code or a reference to a BodyStructure resource SHALL be used, but not both.
(coding.empty() and text.empty()) or extension('http://hl7.org/fhir/StructureDefinition/bodySite').empty()
< 442083009 |Anatomical or acquired body structure|
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. 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.
Record details about the anatomical location of a specimen or body part. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Indicates the patient or group who the condition record is associated with.
Group is typically used for veterinary or public health use cases.
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".
.inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
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.
.effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value
Onset of the symptom, complaint, functional limitation, complication or date of diagnosis. A ‘vague’ date, such as only the year or the month and the year, is permitted.
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.
.effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed
The date or estimated date that the condition resolved or went into remission. A ‘vague’ date, such as only the year or the month and the year, is permitted
Date when the condition record was created
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.
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.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Distinguishes the type of involvement of the actor in the activities related to the condition.
Who or what participated in the activities related to the allergy (e.g. asserter, reporter)
Indicates who or what participated in the activities related to the condition.
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.
./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage/grade"]
Codes describing condition stages (e.g. Cancer stages).
Reference to the evidence on which the staging assessment is based.
The kind of staging, such as pathological or clinical staging.
Codes describing the kind of condition staging (e.g. clinical or pathological).
./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage type"]
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).
.outboundRelationship[typeCode=SPRT].target[classCode=OBS, moodCode=EVN]
Additional information about the Condition
Comment by the one who determined or updated the Problem.
.inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value