This page is part of the Breast Cancer Data Logical Models and FHIR Profiles (v0.1.0: STU 1 Draft) based on FHIR R3. . For a full list of available versions, see the Directory of published versions
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="cimi-FindingContext-model"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p><b>BC FindingContext Logical Model</b></p> <p>The FindingContext class provides the context for the EvaluationResultTopic and AssertionTopic in a clinical statement. For instance, a statement about findings may state that the finding was observed to be present or absent. This class aligns with the SNOMED Situation with Explicit Context.The base class for representing the ontological status of a finding, e.g., present, absent, goal, risk, expectation, etc. CIMI Alignment: In CIMI V0.0.4, FindingContext included a 'status' attribute. However, there are several problems with this. (1) To align with FHIR, the datatype of status should be Concept, not Attribution. (2) In FHIR, different types of status with different shades of meaning are found in different subclasses, for example, clinicalStatus and verificationStatus in Condition, and status in Observation. (3) Status will not be uniform in meaning across all CIMI finding contexts. For example, in GoalContext, the relevant status might be the progress toward the goal, which does not have the same meaning as the status of an EvaluationResult.</p> </div> </text> <url value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-FindingContext-model"/> <identifier> <system value="http://hl7.org/fhir/us/breastcancer"/> <value value="cimi.FindingContext"/> </identifier> <version value="0.1.0"/> <name value="FindingContextModel"/> <title value="BC FindingContext Logical Model"/> <status value="draft"/> <date value="2018-04-01T00:00:00+11:00"/> <publisher value="The HL7 Cancer Interoperability Group sponsored by Clinical Interoperability Council Work Group (CIC)"/> <contact> <telecom> <system value="url"/> <value value="http://standardhealthrecord.org"/> </telecom> </contact> <description value="The FindingContext class provides the context for the EvaluationResultTopic and AssertionTopic in a clinical statement. For instance, a statement about findings may state that the finding was observed to be present or absent. This class aligns with the SNOMED Situation with Explicit Context.The base class for representing the ontological status of a finding, e.g., present, absent, goal, risk, expectation, etc. CIMI Alignment: In CIMI V0.0.4, FindingContext included a 'status' attribute. However, there are several problems with this. (1) To align with FHIR, the datatype of status should be Concept, not Attribution. (2) In FHIR, different types of status with different shades of meaning are found in different subclasses, for example, clinicalStatus and verificationStatus in Condition, and status in Observation. (3) Status will not be uniform in meaning across all CIMI finding contexts. For example, in GoalContext, the relevant status might be the progress toward the goal, which does not have the same meaning as the status of an EvaluationResult."/> <keyword> <system value="http://snomed.info/sct"/> <code value="410514004"/> </keyword> <kind value="logical"/> <abstract value="false"/> <type value="cimi-FindingContext-model"/> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element"/> <derivation value="specialization"/> <snapshot> <element id="cimi-FindingContext-model"> <path value="cimi-FindingContext-model"/> <definition value="The FindingContext class provides the context for the EvaluationResultTopic and AssertionTopic in a clinical statement. For instance, a statement about findings may state that the finding was observed to be present or absent. This class aligns with the SNOMED Situation with Explicit Context.The base class for representing the ontological status of a finding, e.g., present, absent, goal, risk, expectation, etc. CIMI Alignment: In CIMI V0.0.4, FindingContext included a 'status' attribute. However, there are several problems with this. (1) To align with FHIR, the datatype of status should be Concept, not Attribution. (2) In FHIR, different types of status with different shades of meaning are found in different subclasses, for example, clinicalStatus and verificationStatus in Condition, and status in Observation. (3) Status will not be uniform in meaning across all CIMI finding contexts. For example, in GoalContext, the relevant status might be the progress toward the goal, which does not have the same meaning as the status of an EvaluationResult."/> <min value="0"/> <max value="*"/> <base> <path value="cimi-FindingContext-model"/> <min value="0"/> <max value="*"/> </base> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-FindingContext-model.contextCode"> <path value="cimi-FindingContext-model.contextCode"/> <short value="A code representing the ontological status of the statement, e.g., whether it exists, does not exist, is planned, etc."/> <definition value="A code representing the ontological status of the statement, e.g., whether it exists, does not exist, is planned, etc. Attribute aligns with the SNOMED CT Situation with Explicit Context (SWEC) Concept Model context attributes: 'Finding context (attribute)' (SCTID: 408729009) and 'Procedure context (attribute)' (SCTID: 408730004). The range allowed for this attribute shall be consistent with the SNOMED CT concept model specification for SWEC. CIMI Alignment: ContextCode is the new CIMI name for the attribute formerly called 'type' in CIMI V0.0.4."/> <min value="1"/> <max value="1"/> <base> <path value="cimi-FindingContext-model.contextCode"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-ContextCode-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> </snapshot> <differential> <element id="cimi-FindingContext-model"> <path value="cimi-FindingContext-model"/> <definition value="The FindingContext class provides the context for the EvaluationResultTopic and AssertionTopic in a clinical statement. For instance, a statement about findings may state that the finding was observed to be present or absent. This class aligns with the SNOMED Situation with Explicit Context.The base class for representing the ontological status of a finding, e.g., present, absent, goal, risk, expectation, etc. CIMI Alignment: In CIMI V0.0.4, FindingContext included a 'status' attribute. However, there are several problems with this. (1) To align with FHIR, the datatype of status should be Concept, not Attribution. (2) In FHIR, different types of status with different shades of meaning are found in different subclasses, for example, clinicalStatus and verificationStatus in Condition, and status in Observation. (3) Status will not be uniform in meaning across all CIMI finding contexts. For example, in GoalContext, the relevant status might be the progress toward the goal, which does not have the same meaning as the status of an EvaluationResult."/> <min value="0"/> <max value="*"/> <base> <path value="cimi-FindingContext-model"/> <min value="0"/> <max value="*"/> </base> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-FindingContext-model.contextCode"> <path value="cimi-FindingContext-model.contextCode"/> <short value="A code representing the ontological status of the statement, e.g., whether it exists, does not exist, is planned, etc."/> <definition value="A code representing the ontological status of the statement, e.g., whether it exists, does not exist, is planned, etc. Attribute aligns with the SNOMED CT Situation with Explicit Context (SWEC) Concept Model context attributes: 'Finding context (attribute)' (SCTID: 408729009) and 'Procedure context (attribute)' (SCTID: 408730004). The range allowed for this attribute shall be consistent with the SNOMED CT concept model specification for SWEC. CIMI Alignment: ContextCode is the new CIMI name for the attribute formerly called 'type' in CIMI V0.0.4."/> <min value="1"/> <max value="1"/> <base> <path value="cimi-FindingContext-model.contextCode"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-ContextCode-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> </differential> </StructureDefinition>