HL7 FHIR® Implementation Guide: Breast Cancer Data, Release 1 - US Realm (Draft for Comment)
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-AssertionTopic-model"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p><b>BC AssertionTopic Logical Model</b></p> <p>The base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there.</p> </div> </text> <url value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-AssertionTopic-model"/> <identifier> <system value="http://hl7.org/fhir/us/breastcancer"/> <value value="cimi.AssertionTopic"/> </identifier> <version value="0.1.0"/> <name value="AssertionTopicModel"/> <title value="BC AssertionTopic 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 base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there."/> <kind value="logical"/> <abstract value="false"/> <type value="cimi-AssertionTopic-model"/> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element"/> <derivation value="specialization"/> <snapshot> <element id="cimi-AssertionTopic-model"> <path value="cimi-AssertionTopic-model"/> <definition value="The base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there."/> <min value="0"/> <max value="*"/> <base> <path value="cimi-AssertionTopic-model"/> <min value="0"/> <max value="*"/> </base> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.value"> <path value="cimi-AssertionTopic-model.value"/> <short value="Code representing the base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found."/> <definition value="Code representing the base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there."/> <alias value="codeableConcept"/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.value"/> <min value="0"/> <max value="1"/> </base> <type> <code value="Coding"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.topicCode"> <path value="cimi-AssertionTopic-model.topicCode"/> <short value="The concept representing the finding or action that is the topic of the statement."/> <definition value="The concept representing the finding or action that is the topic of the statement. For action topics, the TopicCode represents the action being described. For findings, the TopicCode represents the 'question' or property being investigated. For evaluation result findings, the TopicCode contains a concept for an observable entity, such as systolic blood pressure. For assertion findings, the TopicCode contains a code representing the condition, allergy, or other item being asserted. In all cases, the TopicCode describes the topic independent of the context of the action or the finding. CIMI Alignment: TopicCode is the new CIMI name for the attribute formerly called 'key' in CIMI V0.0.4."/> <min value="1"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.topicCode"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-TopicCode-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.findingMethod"> <path value="cimi-AssertionTopic-model.findingMethod"/> <short value="The technique used to create the finding; for example, the specific imaging technique, lab test code, or assessment vehicle."/> <definition value="The technique used to create the finding; for example, the specific imaging technique, lab test code, or assessment vehicle. CIMI Alignment: In CIMI V0.0.4, this attribute was called 'method'. The value set binding reflects CIMI's preference for LOINC codes."/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.findingMethod"/> <min value="0"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-FindingMethod-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.interpretation"> <path value="cimi-AssertionTopic-model.interpretation"/> <code> <system value="http://ncimeta.nci.nih.gov"/> <code value="C0420833"/> </code> <short value="A clinical interpretation of a finding."/> <definition value="A clinical interpretation of a finding. CIMI Alignment: The value set binding has been chosen to align with FHIR. (Note: it is not clear if Interpretation belongs in FindingTopic, rather than a context class, but that is how CIMI has modeled it.)"/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.interpretation"/> <min value="0"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-Interpretation-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> </snapshot> <differential> <element id="cimi-AssertionTopic-model"> <path value="cimi-AssertionTopic-model"/> <definition value="The base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there."/> <min value="0"/> <max value="*"/> <base> <path value="cimi-AssertionTopic-model"/> <min value="0"/> <max value="*"/> </base> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.value"> <path value="cimi-AssertionTopic-model.value"/> <short value="Code representing the base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found."/> <definition value="Code representing the base topic for conditions, allergies, adverse events, etc. These are things that are asserted to exist or not. The Value is interpreted in the context of the class; for an AdverseSensitivityToSubstance, the value is the substance; for a ConditionPresenceStatement, the Value represents the type of condition found. CIMI Alignment: In CIMI V0.0.4, this class was called Assertion, but CIMI recently decided to change the name to AssertionTopic, as anticipated here. In CIMI V0.0.4, Assertion defines three attributes: dateAsserted, verificationStatus, and findingMethod. VerificationStatus more properly only applies in the PresenceContext context, and can be found there. FindingMethod more properly belongs in FindingTopic, and can be found there."/> <alias value="codeableConcept"/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.value"/> <min value="0"/> <max value="1"/> </base> <type> <code value="Coding"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.topicCode"> <path value="cimi-AssertionTopic-model.topicCode"/> <short value="The concept representing the finding or action that is the topic of the statement."/> <definition value="The concept representing the finding or action that is the topic of the statement. For action topics, the TopicCode represents the action being described. For findings, the TopicCode represents the 'question' or property being investigated. For evaluation result findings, the TopicCode contains a concept for an observable entity, such as systolic blood pressure. For assertion findings, the TopicCode contains a code representing the condition, allergy, or other item being asserted. In all cases, the TopicCode describes the topic independent of the context of the action or the finding. CIMI Alignment: TopicCode is the new CIMI name for the attribute formerly called 'key' in CIMI V0.0.4."/> <min value="1"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.topicCode"/> <min value="1"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-TopicCode-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.findingMethod"> <path value="cimi-AssertionTopic-model.findingMethod"/> <short value="The technique used to create the finding; for example, the specific imaging technique, lab test code, or assessment vehicle."/> <definition value="The technique used to create the finding; for example, the specific imaging technique, lab test code, or assessment vehicle. CIMI Alignment: In CIMI V0.0.4, this attribute was called 'method'. The value set binding reflects CIMI's preference for LOINC codes."/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.findingMethod"/> <min value="0"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-FindingMethod-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> <element id="cimi-AssertionTopic-model.interpretation"> <path value="cimi-AssertionTopic-model.interpretation"/> <code> <system value="http://ncimeta.nci.nih.gov"/> <code value="C0420833"/> </code> <short value="A clinical interpretation of a finding."/> <definition value="A clinical interpretation of a finding. CIMI Alignment: The value set binding has been chosen to align with FHIR. (Note: it is not clear if Interpretation belongs in FindingTopic, rather than a context class, but that is how CIMI has modeled it.)"/> <min value="0"/> <max value="1"/> <base> <path value="cimi-AssertionTopic-model.interpretation"/> <min value="0"/> <max value="1"/> </base> <type> <code value="http://hl7.org/fhir/us/breastcancer/StructureDefinition/cimi-Interpretation-model"/> </type> <mustSupport value="false"/> <isModifier value="false"/> <isSummary value="false"/> </element> </differential> </StructureDefinition>