Clinical Case Activities
Description:
This database lists clinical case activities authored by instructors in the Clinical Mind AI platform. Each row represents one element within an activity (e.g., a section or an item inside a section). Activity-level fields (e.g., purpose, complexity, learning outcomes) repeat across rows belonging to the same activity, while section and item fields describe the specific content or interaction (text, image, open-ended question, patient interaction, rubric, and optional feedback).
Activities are created by selecting a simulated patient, defining the educational purpose, complexity, and learning outcomes, and then composing sections that may contain questions or media. Items may optionally reference a rubric and include instructor feedback. When rubrics are attached to notes written by students in the medical record of the patient, the corresponding rows will have empty values for sectionId and related section variables (notes are located outside of sections, as they can be present in multiple patient interaction sections).
If an activity includes questions with rubrics and feedback enabled, the maxScore field reflects the total possible score for that item. When multiple rubrics are attached to a question, their maxScore values are summed. These will not be split into multiple rows.
Variables:
createdAt — Date and time when the activity was first created on the platform.
updatedAt — Date and time of the most recent update to the activity.
createdBy — Unique identifier of the user who originally created the activity. Join with the Users database to obtain user details.
updatedBy — Unique identifier of the user who last updated the activity. Join with the Users database to obtain user details.
id — Unique system-generated identifier for the activity (activity-level key; repeats across its rows).
patientId — Identifier of the linked simulated patient for this activity. When an activity is locked (for example, assigned to a course or published), patientId references the patient snapshot used by the activity. Join with the Patients databases to retrieve patient metadata.
purpose — Brief statement of the educational purpose of the activity, entered by the creator.
complexity — Difficulty level selected by the creator (numeric scale 1–5: 1 Easy, 2 Fair, 3 Intermediate, 4 Difficult, 5 Very Difficult). Previously this question was about complexity in the alpha version of the platform.
studentInstructions — Instructions shown to students at the start of the activity, entered by the creator. May include HTML and links.
isReviewRequired — Boolean indicating whether instructor review is required before sending activity feedback to students (TRUE/FALSE). If FALSE, feedback is released immediately after completion.
isAiGeneratedFeedback — Boolean indicating whether AI-generated feedback is enabled at the activity level (TRUE/FALSE).
isActive — Boolean indicating whether the activity is currently active/assigned (TRUE) or archived (FALSE).
isEditable — Boolean indicating whether the activity can be edited (TRUE) or is locked (FALSE). FALSE commonly indicates the institutional-library copy or an activity attached to a course; TRUE indicates an unlocked record. Edits to a locked/published activity create a new copy to preserve the original.
originalActivityId — Identifier of the first version from which this activity was duplicated or derived (version lineage root).
lastActivityId — Identifier of the most recent version in the lineage chain for this activity.
lastModifiedById — Identifier of the user who most recently modified the activity. Join with the Users database to obtain user details.
originallyById — Identifier of the user who originally authored the activity. Join with the Users database to obtain user details.
isActivityFeedbackActive — Boolean indicating whether activity-level feedback is enabled for this activity (TRUE/FALSE).
isItemFeedbackActive — Boolean indicating whether item-level feedback is enabled for items within this activity (TRUE/FALSE). In the platform, even if an activity has feedback ON, this can be turned off for specific items such as medical history or notes in the medical record of the patient.
originallyBy — Display name of the original author of the activity.
lastModifiedBy — Display name of the most recent editor of the activity.
learningOutcomes — Learning outcomes targeted by the activity. May be empty if none were tagged.
patientName — Display name of the linked simulated patient.
courseNames — List of course names in which this activity is assigned. Stored as a list/array; may appear comma-separated in exports.
institution — Name of the institution associated with the activity.
country — Country of the associated institution.
sectionId — Unique identifier for the section within the activity (repeats across items in the same section). Sections are the main organizational unit inside a clinical case activity.
sectionTitle — Title of the section (for example, Case introduction, Physical examination) as entered by the creator. Optional.
interactionType — For sections that are patient interactions, indicates the specific interaction with the AI-simulated patient (for example, Medical history, Physical examination). Empty for non-interaction sections.
sectionPosition — Order of the section within the activity (integer, 1-based).
itemId — Unique identifier for the item within the section.
itemPosition — Order of the item within its section (integer, 1-based). Patient-interaction sections that only host the interaction may not have an item position.
itemType — Type of the item at this position (for example, TEXT, IMAGE, OPEN_ENDED, MCQ). Patient-interaction sections are also indicated here (for example, MEDICAL_HISTORY, PHYSICAL_EXAMINATION).
itemContent — Main content of the item (question stem, prompt, passage, or other content). Stored as rich text and may include HTML and links. Patient interaction sections or notes do not have content in this variable. Patient interaction sections retrieve content from the patient data. Notes are empty during patient creation as they are written by the students.
maxScore — Maximum attainable score for this row when the itemType is a question or has a rubric attached and feedback is active. If one or more rubrics are attached to the item, maxScore equals the sum of all attached rubrics’ maxScore for that item. This report does not split an item into multiple rows when multiple rubrics are attached.
itemOptions — Options for MCQ or similar item types. Stored as structured data (for example, JSON array) and option labels may include HTML.
itemFeedback — Instructor-provided feedback criteria or exemplar guidance associated with the item. Stored as rich text; may include HTML and links. Presence and visibility depend on isItemFeedbackActive.
interactionSetting — Settings associated with the patient interaction section. For example, in Medical History sections the options are: Report, Text chat or Text/Voice chat. This variable will show the specific selection in that patient interaction section.
rubricId — Identifier of a rubric attached to the item or interaction. Join with the Rubrics database to retrieve rubric structure and max scores.
Notes: Notes in the medical record of a patient are empty by default as only students can input new notes to the patient during the performance of the activity. As notes are not part of a specific section can be present in multiple patient interaction sections, sectionId and similar section fields will be empty when itemType indicates Notes. Notes will be shown in this report for an activity only when an instructor has feedback ON and notes are associated with a rubric. In all other cases Notes will not be present in the column itemType.