Student Performance (Physical Examination and Medical Tests requests)

Description:

This database contains the records of student–patient interactions when students request physical-examination or medical tests inside Clinical Mind AI activities configured with these interaction types. It is provided in long format: each row represents one requested exam/test (or exam sub-step) within a student attempt. A single attempt can have multiple rows as the student requests multiple physical examinations or tests. Use attemptId to group rows from the same submission and to join with other reports (e.g., Student Performance; Conversation Data). Use patientId to join with the Patients reports for demographics and authorship metadata.

How responses are produced:

• If the requested exam/test exists in the patient’s predefined data, the platform retrieves and returns that authored information to the student (ground-truth for the case). This information is already available in the Patients databases and not shown in this report. This database contains the specific request by the student, but not the response by the system if the information comes from the patient data.
• If the requested item is not present in the patient’s data (or a normal baseline is required), the platform auto-generates a normal response using templated/physiology-consistent defaults. This information is available in this database. It provides the student specific request and the AI-generated response.

Responses can be multi-line, may include basic HTML and line breaks, and appear in the institution’s language.

Variables:

id — Unique system-generated identifier for this interaction record (primary key).

attemptId — Identifier of the student’s attempt in which this request occurred. Use as the canonical join key with Student Performance and Conversation Data for the same attempt.

activityType — Format of the activity in which the interaction occurred (for example, Individual, OSCE).

courseId — Identifier of the course in which the activity was assigned. Join to Courses for metadata.

courseName — Display name of the course in which the activity was assigned.

institution — Name of the institution associated with the interaction.

country — Country of the associated institution.

patientId — Identifier of the simulated patient involved in the interaction. Join to Patients for patient-level details.

patientName — Display name of the simulated patient at the time of the interaction (convenience field for browsing/reporting).

interactionType — High-level request type: PHYSICAL_EXAMINATION or MEDICAL_TEST. Determines which subfields are most relevant on the row.

interactionCategory — Category within the interactionType. Physical exam: body system/region (for example, CARDIOVASCULAR, RESPIRATORY). Medical tests: broad family (for example, Laboratory, Imaging, Microbiology, Cardiac).

interactionSubCategory — Sub-classification within the category. Physical exam: method/approach (for example, inspection, palpation, auscultation). Medical tests: subfamily (for example, blood chemistry, hematology, MRI brain, echocardiography).

interactionTitle — Specific maneuver or test label (for example, palpation-extremities; chest CT; urine culture). Serves as the item title for the requested action.

request — The student’s request written as plain text. This variable is filled in the case of open-ended request for physical examination or medical tests. If the interaction type is selecting from a list, the variables interactionCategory, interactionSubCategory and interactionTitle will contain the specific option clicked by the student.

response — The result returned to the student generated by AI for data not available in the patient database. Stored as rich text and may include basic HTML and line breaks. Responses to request that are available in the patient data are not visible in this report and must be retrieved from the patient database.

isNormalGeneratedValue — Boolean indicating that the response was auto-generated with normal findings by the platform (TRUE). This typically occurs when the requested exam/test is not present in the patient’s predefined data or when a normal baseline is requested. If the requested information exists and is retrieved from the patient record, this field is FALSE (even if those authored findings happen to be normal).

isGenerationComplete — Boolean indicating whether the platform finished assembling or generating the response (TRUE/FALSE). Retrieval is typically complete immediately; auto-generation may be FALSE until finalized.

specifications — Test- or maneuver-specific parameters that affect the response (for example, CT without contrast; MRI T1/T2; microbiology culture from wound swab; Gram stain method). Stored as concise free text; use this for protocol/parameter details rather than narrative findings.

performedBy — Display name of the user who issued the request (typically the student).

performedById — Unique identifier of the user who issued the request. Join to the Users database for details.

performedByRole — Role of the requester within the system (typically STUDENT).

performedAt — Timestamp indicating when the request was submitted (full datetime string with timezone). Use with attemptId to order interactions within a session.

interactionCreatedAt — Timestamp when this interaction record was created in the datastore (may differ slightly from performedAt).

interactionUpdatedAt — Timestamp of the most recent update to this interaction record (for example, when a generated response is finalized).