- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
StructureDefinition UKCore-Condition
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-Condition | active | 2.6.0 | 2024-06-07 | This profile defines the UK constraints and extensions on the International FHIR resource Condition. |
Profile_Purpose |
---|
This profile allows recording of detailed information about a condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. The condition could be a point in time diagnosis in the context of an encounter, it could be an item on the practitioner’s problem list, or it could be a concern that doesn’t exist on the practitioner’s problem list. Often, a condition is about a clinician's assessment and assertion of a particular aspect of an individual's state of health. It can be used to record information about a disease/illness identified from the application of clinical reasoning over the pathologic and pathophysiologic findings (diagnosis), or identification of health issues/situations that a practitioner considers harmful, potentially harmful and may be investigated and managed (problem), or other health issue/situation that may require ongoing monitoring and/or management (health issue/concern). |
Detailed Descriptions
Condition | |
Definition | A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Condition.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Condition.meta | |
Definition | 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Condition.implicitRules | |
Definition | 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
Condition.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Mappings |
|
Condition.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have 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. |
Invariants |
|
Mappings |
|
Condition.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Condition.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Condition.extension:bodyStructureR6 | |
Definition | Optional Extension Element - found in all resources. |
Cardinality | 0...1 |
Type | Extension(Reference(UKCoreCondition)) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.extension:conditionEpisode | |
Definition | The episodicity status of a condition. |
Cardinality | 0...* |
Type | Extension(CodeableConcept) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Condition.identifier | |
Definition | 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. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Requirements | Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers. |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.clinicalStatus | |
Definition | The clinical status of the condition. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The clinical status of the condition or diagnosis. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.verificationStatus | |
Definition | The verification status to support the clinical status of the condition. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The verification status to support or decline the clinical status of the condition or diagnosis. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.category | |
Definition | A category assigned to the condition. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A ValueSet to identify the category of a condition. |
Comments | The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. |
Invariants |
|
Mappings |
|
Condition.severity | |
Definition | A subjective assessment of the severity of the condition as evaluated by the clinician. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A subjective assessment of the severity of the condition as evaluated by the clinician. |
Must Support | True |
Comments | Coding of the severity with a terminology is preferred, where possible. |
Invariants |
|
Mappings |
|
Condition.code | |
Definition | Identification of the condition, problem or diagnosis. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code from the SNOMED Clinical Terminology UK with the expression (<404684003 |Clinical finding| OR <413350009 |Finding with explicit context| OR <272379006 |Event|). |
Must Support | True |
Summary | True |
Alias | type |
Requirements | 0..1 to account for primarily narrative only resources. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Condition.bodySite | |
Definition | The anatomical location where this condition manifests itself. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. |
Summary | True |
Comments | Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. |
Invariants |
|
Mappings |
|
Condition.subject | |
Definition | Indicates the patient or group who the condition record is associated with. |
Cardinality | 1...1 |
Type | Reference(Patient | Group) |
Must Support | True |
Summary | True |
Alias | patient |
Requirements | Group is typically used for veterinary or public health use cases. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Condition.encounter | |
Definition | The Encounter during which this Condition was created or to which the creation of this record is tightly associated. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Summary | True |
Comments | 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". |
Invariants |
|
Mappings |
|
Condition.onset[x] | |
Definition | Estimated or actual date or date-time the condition began, in the opinion of the clinician. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. |
Invariants |
|
Mappings |
|
Condition.abatement[x] | |
Definition | 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" - Conditions are never really resolved, but they can abate. |
Cardinality | 0...1 |
Type | dateTime |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.recordedDate | |
Definition | The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Invariants |
|
Mappings |
|
Condition.recorder | |
Definition | Individual who recorded the record and takes responsibility for its content. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) |
Must Support | True |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Condition.asserter | |
Definition | Individual who is making the condition statement. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Condition.stage | |
Definition | Clinical stage or grade of a condition. May include formal severity assessments. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Condition.stage.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Condition.stage.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Condition.stage.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.stage.summary | |
Definition | A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes describing condition stages (e.g. Cancer stages). |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Condition.stage.assessment | |
Definition | Reference to a formal record of the evidence on which the staging assessment is based. |
Cardinality | 0...* |
Type | Reference(ClinicalImpression | DiagnosticReport | Observation) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Condition.stage.type | |
Definition | The kind of staging, such as pathological or clinical staging. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes describing the kind of condition staging (e.g. clinical or pathological). |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Condition.evidence | |
Definition | Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. |
Invariants |
|
Mappings |
|
Condition.evidence.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Condition.evidence.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Condition.evidence.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
Condition.evidence.code | |
Definition | A manifestation or symptom that led to the recording of this condition. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes that describe the manifestation or symptoms of a condition. |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Condition.evidence.detail | |
Definition | Links to other relevant information, including pathology reports. |
Cardinality | 0...* |
Type | Reference(Resource) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Condition.note | |
Definition | Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. |
Cardinality | 0...* |
Type | Annotation |
Comments | For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). |
Invariants |
|
Mappings |
|
Table View
Condition | .. | |
Condition.extension | Extension | .. |
Condition.extension | Extension | .. |
Condition.clinicalStatus | .. | |
Condition.verificationStatus | .. | |
Condition.category | .. | |
Condition.severity | .. | |
Condition.code | .. | |
Condition.bodySite | .. | |
Condition.subject | .. | |
Condition.recorder | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-Condition" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-Condition" /> <version value="2.6.0" /> <name value="UKCoreCondition" /> <title value="UK Core Condition" /> <status value="active" /> <date value="2024-06-07" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [Condition](https://hl7.org/fhir/R4/Condition.html)." /> <purpose value="This profile allows recording of detailed information about a condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. \n\nThe condition could be a point in time diagnosis in the context of an encounter, it could be an item on the practitioner’s problem list, or it could be a concern that doesn’t exist on the practitioner’s problem list. Often, a condition is about a clinician's assessment and assertion of a particular aspect of an individual's state of health. \n\nIt can be used to record information about a disease/illness identified from the application of clinical reasoning over the pathologic and pathophysiologic findings (diagnosis), or identification of health issues/situations that a practitioner considers harmful, potentially harmful and may be investigated and managed (problem), or other health issue/situation that may require ongoing monitoring and/or management (health issue/concern)." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Condition" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Condition" /> <derivation value="constraint" /> <differential> <element id="Condition.extension:bodyStructureR6"> <path value="Condition.extension" /> <sliceName value="bodyStructureR6" /> <short value="An extension to replicate the changes within R6 to support adding a reference to the body part affected by the diagnosed condition." /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/6.0/StructureDefinition/extension-Condition.bodyStructure" /> </type> <isModifier value="false" /> </element> <element id="Condition.extension:conditionEpisode"> <path value="Condition.extension" /> <sliceName value="conditionEpisode" /> <short value="The episodicity value of the condition can be represented by one of the following codes: \nfirst | new | review | end." /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-ConditionEpisode" /> </type> </element> <element id="Condition.clinicalStatus"> <path value="Condition.clinicalStatus" /> <short value="The clinical status of the condition." /> <mustSupport value="true" /> </element> <element id="Condition.verificationStatus"> <path value="Condition.verificationStatus" /> <short value="The verification status to support the clinical status of the condition." /> <mustSupport value="true" /> </element> <element id="Condition.category"> <path value="Condition.category" /> <binding> <strength value="extensible" /> <description value="A ValueSet to identify the category of a condition." /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCategory" /> </binding> </element> <element id="Condition.severity"> <path value="Condition.severity" /> <short value="A subjective assessment of the severity of the condition as evaluated by the clinician." /> <mustSupport value="true" /> </element> <element id="Condition.code"> <path value="Condition.code" /> <short value="Identification of the condition, problem or diagnosis." /> <mustSupport value="true" /> <binding> <strength value="preferred" /> <description value="A code from the SNOMED Clinical Terminology UK with the expression (<404684003 |Clinical finding| OR <413350009 |Finding with explicit context| OR <272379006 |Event|)." /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCode" /> </binding> </element> <element id="Condition.bodySite"> <path value="Condition.bodySite" /> <binding> <strength value="preferred" /> </binding> </element> <element id="Condition.subject"> <path value="Condition.subject" /> <short value="Indicates the patient or group who the condition record is associated with." /> <mustSupport value="true" /> </element> <element id="Condition.recorder"> <path value="Condition.recorder" /> <short value="Individual who recorded the record and takes responsibility for its content." /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-Condition", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-Condition", "version": "2.6.0", "name": "UKCoreCondition", "title": "UK Core Condition", "status": "active", "date": "2024-06-07", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [Condition](https://hl7.org/fhir/R4/Condition.html).", "purpose": "This profile allows recording of detailed information about a condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. \n\nThe condition could be a point in time diagnosis in the context of an encounter, it could be an item on the practitioner’s problem list, or it could be a concern that doesn’t exist on the practitioner’s problem list. Often, a condition is about a clinician's assessment and assertion of a particular aspect of an individual's state of health. \n\nIt can be used to record information about a disease/illness identified from the application of clinical reasoning over the pathologic and pathophysiologic findings (diagnosis), or identification of health issues/situations that a practitioner considers harmful, potentially harmful and may be investigated and managed (problem), or other health issue/situation that may require ongoing monitoring and/or management (health issue/concern).", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Condition", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Condition", "derivation": "constraint", "differential": { "element": [ { "id": "Condition.extension:bodyStructureR6", "path": "Condition.extension", "sliceName": "bodyStructureR6", "short": "An extension to replicate the changes within R6 to support adding a reference to the body part affected by the diagnosed condition.", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/6.0/StructureDefinition/extension-Condition.bodyStructure" ] } ], "isModifier": false }, { "id": "Condition.extension:conditionEpisode", "path": "Condition.extension", "sliceName": "conditionEpisode", "short": "The episodicity value of the condition can be represented by one of the following codes: \\nfirst | new | review | end.", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-ConditionEpisode" ] } ] }, { "id": "Condition.clinicalStatus", "path": "Condition.clinicalStatus", "short": "The clinical status of the condition.", "mustSupport": true }, { "id": "Condition.verificationStatus", "path": "Condition.verificationStatus", "short": "The verification status to support the clinical status of the condition.", "mustSupport": true }, { "id": "Condition.category", "path": "Condition.category", "binding": { "strength": "extensible", "description": "A ValueSet to identify the category of a condition.", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCategory" } }, { "id": "Condition.severity", "path": "Condition.severity", "short": "A subjective assessment of the severity of the condition as evaluated by the clinician.", "mustSupport": true }, { "id": "Condition.code", "path": "Condition.code", "short": "Identification of the condition, problem or diagnosis.", "mustSupport": true, "binding": { "strength": "preferred", "description": "A code from the SNOMED Clinical Terminology UK with the expression (<404684003 |Clinical finding| OR <413350009 |Finding with explicit context| OR <272379006 |Event|).", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCode" } }, { "id": "Condition.bodySite", "path": "Condition.bodySite", "binding": { "strength": "preferred" } }, { "id": "Condition.subject", "path": "Condition.subject", "short": "Indicates the patient or group who the condition record is associated with.", "mustSupport": true }, { "id": "Condition.recorder", "path": "Condition.recorder", "short": "Individual who recorded the record and takes responsibility for its content.", "mustSupport": true } ] } }
Feedback
Click here to:Report issue for UKCore-Condition, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Bleeding From Ear - An example to illustrate a patient bleeding from ear.Example UKCore-Condition-BleedingFromEar
CodingSCT DescId - An example to illustrate the extension which adds a SNOMED CT description Id to CodeableConcept.
Example UKCore-Extension-CodingSCTDescId
Condition Episode - An example to illustrate the extension which is used to indicate the episodicity status of a condition.
Example UKCore-Extension-ConditionEpisode
Example Usage Scenarios
The following are example usage scenarios for the UK Core Condition profile:
- Query for a Patient’s current or historical conditions
- Record or update a Patient’s conditions
Profile Specific Implementation Guidance:
Mandatory and Must Support Data Elements
The following elements are identified as MustSupport, and it is expected that consumers and suppliers SHALL support these as per the MustSupport Guidance.
Element | Reason |
---|---|
Condition.clinicalStatus | The clinical status of the condition. |
Condition.verificationStatus | The verification status to support the clinical status of the condition. |
Condition.severity | A subjective assessment of the severity of the condition as evaluated by the clinician. |
Condition.code | Identification of the condition, problem or diagnosis. |
Condition.subject | Indicates the patient or group who the condition record is associated with. |
Condition.recorder | Individual who recorded the record and takes responsibility for its content. |
Extensions
More information about the extensions on the UKCore-Condition
profile can be found using the links below.
Extension | Context | Link | Comment |
---|---|---|---|
bodyStructureR6 | Condition.extension | http://hl7.org/fhir/6.0/StructureDefinition/extension-Condition.bodyStructure | An extension to replicate the changes within R6 to support adding a reference to the body part affected by the diagnosed condition. |
conditionEpisode | Condition.extension | https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-ConditionEpisode | The episodicity value of the condition can be represented by one of the following codes: \nfirst | new | review | end. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
Condition.category | extensible | https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCategory |
Condition.code | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-ConditionCode |
Condition.extension:conditionEpisode | extensible | ValueSet UKCore-ConditionEpisodicity |
subject
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
encounter
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Encounter.
recorder
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-PractitionerRole
- Profile UKCore-RelatedPerson
asserter
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-PractitionerRole
- Profile UKCore-RelatedPerson
stage
Condition.stage.assessment
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
note
The resource referenced in Condition.note.authorReference
SHALL conform to one of the following:
- Profile UKCore-Organization
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-RelatedPerson