HealthTasks Assessments in the REST API and Canvas gradebook

Yesterday we introduced HealthTasks Assessments. Personalized Learning Plans now generate with a CJMM-aligned remediation quiz, and students complete that knowledge check in the platform.

Today HealthTasks Assessments also reach the systems programs already run. Assessments are in the public REST API and in Canvas grade passback. Schools can read submitted knowledge checks over REST, receive one Canvas assignment per quiz, and see CJMM scores on the progress chart.

The assessment still lives in HealthTasks. The gradebook, warehouse, and SIS can stay current without a spreadsheet in the middle.

Knowledge checks over REST

Campus reporting should not wait on an export to know whether remediation landed. Institution-wide API keys can now read HealthTasks Assessments through the same public OpenAPI used for placements, evaluations, and clinical logs.

Schools can pull:

• plp_quizzes: the knowledge check tied to one PLP and one student, including ready or submitted status
• plp_quiz_items: question stems, choices, competency mappings, and CJMM labels, without answer keys
• plp_quiz_attempts: submitted scores, item-level results, and rationales after the student completes the quiz

Question content is available for reporting. Correct keys stay off the items resource. Full plan markdown is not included. The same cursor, limit, and updated_since patterns apply.

This is OpenAPI 1.16.0. Field shapes live in the API docs.

Hospital partner keys are unchanged. They still only see their sites. Quiz reads are a school operation.

One Canvas assignment per quiz

Students still take the assessment in HealthTasks. Canvas stays the course gradebook.

Programs that already send skills checkoffs and evaluation scores to Canvas now get HealthTasks Assessments on the same path. Each quiz becomes its own Canvas assignment. A remediation knowledge check does not land as a line on a generic clinical score.

Faculty do not rebuild the quiz in the LMS. They do not re-enter the result. The student completes the work where the plan lives. The grade shows up where the rest of the course already lives.

That is the distinction from exporting a gap list to stand up a custom Canvas quiz. HealthTasks remains the system of record for the assessment. Canvas receives the grade.

For the original checkoff and evaluation path, see Canvas grade passback.

CJMM scores on the progress chart

Overall percent is useful. Clinical judgment work needs more than that.

The progress chart now shows CJMM scores, so faculty can see how a learner is moving on cue recognition, analysis, prioritization, action, and evaluation, not only whether they finished the quiz. The same CJMM labels that scope the questions are visible on the trajectory faculty already use to watch remediation.

Over a term, that gives programs a clearer view of which judgment skills are closing and which still need attention.

Keep the loop in HealthTasks, and connected

Assessments still close the loop in the platform: find the gap, assign the quiz, watch progress. REST reads and Canvas passback mean that loop can also reach the warehouse, the SIS, and the LMS gradebook without a second tracker.

If your program wants to see HealthTasks Assessments, REST reads, and Canvas passback in one workflow, book a demo. If you are wiring an integration, start with the API documentation.

• Book a demo
• API documentation
• Introducing HealthTasks Assessments
• Canvas grade passback
• What CJMM-aligned programs need from their CEM