Skip to main content
Challenge

Build a FHIR Care-Team On-Call Task Routing Engine

Route urgent research protocol tasks to on-duty study coordinators using FHIR R5 Task and CareTeam structures. Audit assignment latencies and log message transfers across institutional shifts.

Data ScienceHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Route urgent research protocol tasks to on-duty study coordinators using FHIR R5 Task and CareTeam structures. Audit assignment latencies and log message transfers across institutional shifts.

Clinical Trials Operations Specialist

Ingest protocol milestone alerts formatted as FHIR R5 Task objects.

Retrieve current on-call personnel shifts from a CareTeam schedule registry.

Apply availability, role qualifications, and shift boundaries to route task ownership.

Generate updated FHIR Task resources with assigned performers and delivery confirmation timestamps.

Task assignment dashboard with live shift timelines, open protocol tickets, and re-routing triggers.

Synthesize FHIR R5 CareTeam, Practitioner, and Task resources following HL7 FHIR Foundation specifications. Starter examples below are synthetic. They are not downloaded records.

HL7 FHIR overview Reference FHIR R5 Foundation CareTeam participant types and Task status codes to maintain standard conformance.

semantic-kernel, pydantic, fastapi. semantic-kernel orchestrates deterministic skills for shift schedule parsing and task assignment execution. Hosted or local model connector supported by Semantic Kernel to synthesize handover notes.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Consumes valid FHIR Task objects and parses current status and priority codes.

Matches task domain to eligible active practitioners within the active shift schedule.

Produces updated Task payload containing valid reference to assigned Practitioner.

Maintains an immutable routing decision log for operational compliance audits.

```json [ { "input": { "task_id": "TASK-BIO-01", "priority": "urgent", "focus": "SpecimenCollectionReview", "care_team": { "id": "TEAM-ONC", "members": [ { "practitioner_id": "PRAC-A", "role": "coordinator", "status": "on_shift" }, { "practitioner_id": "PRAC-B", "role": "coordinator", "status": "off_shift" } ] } }, "expected_output": { "task_id": "TASK-BIO-01", "status": "assigned", "assigned_to": "PRAC-A", "escalated": false, "routing_reason": "practitioner_active_on_shift" } }, { "input": { "task_id": "TASK-BIO-02", "priority": "stat", "focus": "AdverseEventAudit", "care_team": { "id": "TEAM-ONC", "members": [ { "practitioner_id": "PRAC-B", "role": "coordinator", "status": "off_shift" } ] } }, "expected_output": { "task_id": "TASK-BIO-02", "status": "held", "assigned_to": null, "escalated": true, "routing_reason": "no_active_member_on_shift" } } ] ```

Research administration operational simulator; operates on synthetic practitioner data; no emergency medical triage. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Research administration operational simulator; operates on synthetic practitioner data; no emergency medical triage. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Consumes valid FHIR Task objects and parses current status and priority codes. Matches task domain to eligible active practitioners within the active shift schedule. Produces updated Task payload containing valid reference to assigned Practitioner. Maintains an immutable routing decision log for operational compliance audits.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest protocol milestone alerts formatted as FHIR R5 Task objects. Retrieve current on-call personnel shifts from a CareTeam schedule registry. Apply availability, role qualifications, and shift boundaries to route task ownership. Generate updated FHIR Task resources with assigned performers and delivery confirmation timestamps.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Consumes valid FHIR Task objects and parses current status and priority codes. Matches task domain to eligible active practitioners within the active shift schedule. Produces updated Task payload containing valid reference to assigned Practitioner. Maintains an immutable routing decision log for operational compliance audits.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Task assignment dashboard with live shift timelines, open protocol tickets, and re-routing triggers.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Research administration operational simulator; operates on synthetic practitioner data; no emergency medical triage.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest protocol milestone alerts formatted as FHIR R5 Task objects.

  • Retrieve current on-call personnel shifts from a CareTeam schedule registry.

  • Apply availability, role qualifications, and shift boundaries to route task ownership.

  • Generate updated FHIR Task resources with assigned performers and delivery confirmation timestamps.

Resources and assets

Reference links and supporting material

Dataset notes

Synthesize FHIR R5 CareTeam, Practitioner, and Task resources following HL7 FHIR Foundation specifications. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Semantic Kernel

Agent Systems · Agent Frameworks

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest protocol milestone alerts formatted as FHIR R5 Task objects. Retrieve current on-call personnel shif...
  • Consumes valid FHIR Task objects and parses current status and priority codes. Matches task domain to eligi...
  • Task assignment dashboard with live shift timelines, open protocol tickets, and re-routing triggers.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Semantic Kernel · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a FHIR Care-Team On-Call Task Routing Engine