Skip to main content

cimi.statement

The namespace containing cimi-derived classes representing complete clinical statements. In this specification, these classes derive from the StatementTopic class hierarchy, not ClinicalStatement, which is a significant departure from CIMI. This simplifies the resulting logical models.

ActionNotPerformedStatement [Abstract]

Abstract class representing non-performance of any type of action.

Based On ClinicalStatement

StatementTopic must be a ActionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a NotPerformedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ActionPerformedStatement [Abstract]

Abstract class representing performance of any type of action.

Based On ClinicalStatement

StatementTopic must be a ActionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a PerformedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ActionRequestedAgainstStatement [Abstract]

Abstract class representing a request to not perform any type of action.

Based On ClinicalStatement

StatementTopic must be a ActionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a RequestedAgainstContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ActionRequestedStatement [Abstract]

Abstract class representing a request for any type of action.

Based On ClinicalStatement

StatementTopic must be a ActionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a RequestedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ClinicalNote [Entry]

An entry concerning a patient where the result is a narrative text. Can be related to a specific Focus, such as a condition; and evidence and interpretation from FindingTopic. Progress Note (C0747978)

Based On ClinicalStatement

StatementTopic must be a FindingTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a RecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ClinicalStatement

A special type of information entry consisting of a topic and a context. The ClinicalStatement class provides the core pattern for more specific clinical statement classes, such as a statement that a finding has been found in a patient or that a procedure has been proposed by a clinical decision support system. The ClinicalStatement pattern defines the core attributes common to most clinical statements and specifies a composition pattern that encourage model component reuse and better alignment with the SNOMED CT Concept Model. A clinical statement is composed of the StatementTopic class (grouping of attributes for capturing information about a procedure or a clinical finding) and the StatementContext class (grouping of attributes providing the context for the statement topic such as whether a procedure was performed, requested, not performed or whether a finding is suspected present or absent in the patient). At the archetype level, the topic and context components are coordinated to form the clinical statement. For instance, the composition of the ProcedureTopic with the NotPerformed context indicates that the given procedure was not performed.

Based On InformationEntry

StatementTopic required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

CodedEvaluationResultRecorded

Represents the result of evaluations (measurements, tests, or questions) that have been performed whose answer is expressed as a code.

Based On EvaluationResultRecorded

StatementTopic must be a EvaluationResultTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
         where  EvaluationResultTopic
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
         where  EvaluationResultRecordedContext
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ConditionAbsenceStatement [Entry]

A finding that a condition is or was not present in the subject at a certain time, not necessarily the time the information is gathered. no disease present (C0277541)

Based On ClinicalStatement

StatementTopic must be a ConditionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a AbsenceContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

ConditionPresenceStatement [Entry]

A condition that is or may be present in a subject. 'Condition' is interpreted broadly and could be a disorder, abnormality, problem, injury, complaint, functionality, illness, disease, ailment, sickness, affliction, upset, difficulty, disorder, symptom, worry, or trouble. In CIMI terms, it is an archetype of ClinicalStatement that combines a ConditionTopic with the ConditionPresenceContext context. The core attributes of ClinicalStatement are not included here because of mapping difficulties to FHIR DomainResource.

Based On ClinicalStatement

SourceOfInformation must be a PatientOrPractitionerOrRelatedPerson
optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
StatementTopic must be a ConditionTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a ConditionPresenceContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation must be a Patient
required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

DiagnosticService

A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes.

Value:  CodeableConcept from DiagnosticServiceVS
(if covered)
A set of codes drawn from different coding systems, representing the same concept.

EvaluationResultRecorded

Represents the result of evaluations (measurements, tests, or questions) that have been performed. EvaluationResultRecorded has a value representing the result (answer), or an ExceptionValue indicating why the value is not present. The subject of a finding can be the entire patient, or an entity such as a location body structure, intervention, or condition. Things observed about the subject can include social and behavioral factors, subjective and objective observations, and assessments.

Based On ClinicalStatement

StatementTopic must be a EvaluationResultTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

FindingStatement [Abstract]

Any clinical statement representing a finding.

Based On ClinicalStatement

StatementTopic must be a FindingTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
StatementContext must be a FindingContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

LaboratoryTestResultRecorded

Measurement resulting from a laboratory analysis. The category is fixed to 'laboratory' to align with US-Core.

Based On EvaluationResultRecorded

DiagnosticService 0 or more A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes.
StatementTopic must be a EvaluationResultTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
         where  EvaluationResultTopic
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

NonLabCodedEvaluationResultRecorded

A coded finding not based on a sample or measurement device.

Based On CodedEvaluationResultRecorded

StatementTopic must be a EvaluationResultTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
         where  EvaluationResultTopic
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
         where  EvaluationResultRecordedContext
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

NonLabPanelRecorded

No Description

Based On EvaluationResultRecorded

StatementTopic must be a PanelTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
PanelTopic
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
         where  EvaluationResultRecordedContext
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

PanelRecorded

No Description

Based On LaboratoryTestResultRecorded

StatementTopic must be a PanelTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
         where  EvaluationResultTopic
DiagnosticService 0 or more A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes.
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)

SimplifiedLaboratoryTestResultRecorded

The usual case for a test result from a pathology lab, based on a specimen taken from a patient. Note that the body site is not explicit here; it is part of the specimen resource associated with the lab result.

Based On LaboratoryTestResultRecorded

PanelMembers not used PanelMember represent the elements of a group of a related but independent evaluations. Examples are the measurements that compose a complete blood count (CBC), or the elements of a pathology report. Each member is an independent evaluation, but the grouping reflects a composite lab order, shared specimen, or a single report author. Typically the Category and Reason are not given for individual findings that are part of the panel, but rather given at the level of the panel itself.
DiagnosticService 0 or more A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes.
StatementTopic must be a EvaluationResultTopic
required Compositional and reusable grouping of clinical statement attributes that make up the clinical focus of a statement. StatementTopic class attributes are aligned with SNOMED CT Concept Model attributes when such an overlap exists. Note that this class does not include contextual attributes such as the nature of the action (ordered, proposed, planned, etc...), the nature of the patient state being described (e.g., present, suspected present, absent), and the attribution of this information (the who, when, where, how, why of the information recorded).
         where  EvaluationResultTopic
StatementContext must be a EvaluationResultRecordedContext
required Compositional and reusable grouping of clinical statement attributes that provides the context for the topic of a clinical statement. The StatementContext class aligns with the SNOMED CT Situations with Explicit Context (SWEC) Concept Model. The StatementContext provides the expressivity required to specify that an act was performed or not performed or that a finding was asserted to be present or absent for the given subject of information. It also often holds provenance information relevant to the context of the clinical statement. It is important to note that by default the context applies to the conjunction of the attribute specified in the statement. For instance, if a clinical statement has a topic describing a rash on left arm and a context of 'absent', then the statement states that the subject of interest did not have a rash on the left arm but might have had one on the right arm.
SubjectOfInformation required The person or thing that this entry relates to, usually the Person of Record (see Entry). However, not all entries have health information specifically about the patient, but in different contexts, could refer to a fetus, family member (living or dead), device, location, organization, behavior, finding, condition, wound, or intervention. CIMI alignment: SubjectOfInformation is not a Participation -- unlike CIMI. There's no action to participate in. Participant has extra unnecessary attributes, such as 'onBehalfOf'.
SourceOfInformation optional The person or entity that provided the information in the entry, e.g. the subject (patient), medical professional, family member, device or software program, as distinct from who recorded the entry.
Annotation 0 or more An added or follow-up note, often after the fact, that contains metadata about who made the statement and when.
RecordStatus optional Concept indicating the state of this record, e.g., 'entered in error'.
Recorded optional The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
Signed optional Provenance information specific to the signing of the clinical statement.
Cosigned 0 or more Provenance information specific to the cosigning of the clinical statement.
Verified 0 or more Provenance information specific to the verification process associated with this statement (e.g., verifier, when verified, etc.)