Clinical Logs Are Now Full Encounter Records

When we introduced the HealthTasks REST API, clinical logs were already available to connected systems. What most programs still could not move cleanly was the full encounter record educators already review in product, or the progress numbers leadership already trusts.

That gap is closed.

Clinical logs are more than hours

A clinical log is not a timesheet. It is the encounter: who was there, what happened, which skills were performed, and how the shift was documented.

The REST API now returns that fuller picture. Programs can pull approved logs with patient and setting context, ICD and CPT fields from the template, per-encounter notes and AI summaries, skill totals, verified times, and feedback, alongside the student, preceptor, classroom, and site.

In short, the same clinical evidence faculty already approve can land in a SIS, warehouse, or reporting tool without a spreadsheet middle step.

A light example of what comes back for a skill on an approved log:

{
  "name": "IM Injection",
  "ability_level": "performed",
  "count": 1
}

And for encounter context:

{
  "setting": ["Hospital"],
  "age_range": ["Adult (18-64 years)"],
  "icd_codes": ["J44.1", "I10"]
}

Full field shapes live in the API docs.

Progress without rebuilding the math

Hours logged are only one signal. Programs also track progress toward hour requirements, skills completion, evaluation averages, and checkoff scores. Educators already see those KPIs in HealthTasks. Integrations often rebuilt them from raw events anyway.

Student and classroom analytics endpoints now expose those same rollups directly. Campus systems can sync progress the way the program already measures it.

{
  "total_hours": 86.5,
  "hours_percentage": 72.1,
  "skills_percentage": 64.0,
  "evaluation_score": 91.4,
  "checkoff_score": 88.2
}

That matters for Power BI, warehouse loads, and campus integration platforms. Leadership gets clinical progress next to the rest of institutional reporting, without asking IR to reverse-engineer competency math.

Keep HealthTasks as the system of record

Clinical education stays in HealthTasks. Connected tools consume encounter detail and progress KPIs through the same public OpenAPI used for placements, compliance, and evaluations.

That is the Open CEM idea applied to day-to-day clinical evidence: less export work, fewer parallel trackers, and a clearer path from the unit to institutional reporting.

Get started

Explore the docs, or reach out if you want to walk through how clinical logs and progress analytics fit your stack.

• API documentation
• REST API overview
• The Open CEM
• Webhooks