Condition Resource
FHIR Ā Element 3 STU Definition | Binding Strengths 3 (STU) | Questions/Proposal Ā to the group | CommentsĀ Ā |
|---|---|---|---|
clinicalStatus Comments: This element is labeled as a modifier becauseĀ theĀ status contains codes that mark the condition as not currently valid or Ā of concern. | Required | Add guidance this information Ā can be captured in the condition.code as the clinical condition: if the Ā ClinicalStatus can be represented from the codeableConcept Condition.code, it Ā should not be entered here. | Ā |
verificationStatus | Required | Should thisĀ Ā element include 'suspected' | Ā |
Ā | Ā | Add an exampleĀ Ā when a Condition is provisional or differential and then becomes confimed | Ā |
Category Comments: The categorization is often highly contextual Ā and may appear poorly differentiated or not very useful in other contexts. | Example | This element Ā seems to allow categorisation of types of information found in the resource, Ā such as: symptom, sign, diagnosis, event, complaint, etc. Is it used for Ā other purposes? | Ā |
Ā | Ā | Should there be Ā guidance to use the list resource with this element? | Ā |
Severity Comments:Ā Ā Coding of the severity with a terminology is preferred, where possible. | Preferred | Change binding the proposed Ā intensional definition for this value set: < 272141005 |Severities| | Ā |
Ā | Add guidance on validation of Ā content that is a normal condition, to avoid inappropriate information, e.g. Ā pregnancy. | Ā | |
Ā | Ā | Add guidance this information Ā can be captured in the condition.code as the clinical condition: if the Ā Severity can be represented from the Condition.code codeableConcept, it Ā should not be entered here. | Ā |
Code Identification of the condition, problem or diagnosis. | Example | Change binding strength to Preferred so SNOMED CT is the Ā Clinical Terminology of choice for this data element, and change binding the Ā proposed intensional definition for this value set: | Corrected ECL expression (( |
Ā | Ā | There is a proposed change to Ā the Scope and Usage of this resource to better reflect the in Ā scope elements for this resource.Ā | Ā |
Ā | Ā | Add guidance when the Ā condition.code may include the Severity, the ClinicalStatus even the Ā verificationStatus (confirmed) as the clinical condition: if the Ā Condition.code includes the severity and/or the clinical status and/or the Ā verification status these elements should not be captured to avoid duplicated Ā information. | Ā |
Ā | Ā | There is a proposed change to Ā the Scope and Usage of this resource to better reflect the in Ā scope elements for this resource. | Ā |
Ā | Ā | Add an example for when the Ā Condition.code is not required. | Ā |
bodySite 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 body-site-instance. May be a summary code, or a reference Ā to a very precise definition of the location, or both. | Example | The binding strength should be Ā changed for Preferred [0..*] | Ā |
Ā | Ā | In the examples f202 and f203, Ā we can see a major discrepancy between the Condition.code and the BodySite. Ā Should there be guidance when this element is used and how should data be Ā consolidated for analysis and retrieval? | Ā |
stage.summary | Example | The binding strength should be Ā changed for Preferred [0..*] | Ā |
Ā | Ā | The Content Logical Definition Ā does not seem aligned on the Expansion shown on the page. Add the following Ā to the Content Logical Definition: | Ā |
Ā | Ā | Add a Ā«CommentĀ» similar to the Ā Severity element. | Ā |
Ā | Ā | Add guidance this information Ā can be captured in the condition.code as the clinical condition: if the Ā Condition.Stage.Summary can be represented from the codeableConcept Ā Condition.code, it should not be entered here. | Ā |
Ā | Ā | Is there a dependency between Ā this element and the verificationStatus? | Ā |
Ā | Ā | Please review the Example f204 Ā whcih does not seem to comply to the definition of this element.Ā | Ā |
stage.assessment | There is no Terminology binding currently | Is there a dependency between Ā this element and the verificationStatus? | Ā |
evidence.code | Example | Change binding strength to Preferred so SNOMED CT is the Ā Clinical Terminology of choice for this data element and change binding to Ā the same as for the Condition.code unless there is a rationale for the Ā bindings to be different, knowinf that the SNOMED CT clinical finding Ā hierarchy does not have specific sub-hierarchies that are signs or symptoms. | Ā Will include the values from the Observation Resource plus items from the Condition Resource. |
Ā | Ā | Provide guidance for when to use Ā the evidence.code vs the Observation Resource | |
Ā | Ā | Please review the Example f201, Ā f002 and f003 which do not seem to comply to the definition of this Ā element.Ā | Ā |
evidence.detail | There is no Terminology binding currently | Is there a dependency between Ā this element and the verificationStatus? | Ā The detail field here allows a reference to be made to 0..* Observation Resources. |
Ā | Ā | How are the other data element Ā adjusting when a value is populated in this field? Are there validation on Ā all associated fields? Refer to example f202-malignancy. | Ā |
Ā |
Copyright Ā© 2025, SNOMED International