Get your API key
Contact us with your research or training use case. Credentials and integration details are shared after access is granted.
Request an API key ↘Clinical RL environment as a service
An EHR-like simulation your agent can act in - not just answer.
Gather evidence, choose a
next step, and learn from the trajectory.
observation → actionfinding ← step(action)Granted access · contact us for API credentials and integration details.
Open showcase dataset
GPT-6.1-Sol on acute intermittent porphyria and VIPoma / WDHA, three attempts each. Full transcripts with analyst review of diagnosis and whole-patient care. Recorded runs, not authored illustrations.
Open on Hugging Face ↗Environment / 01
An EHR-like encounter unfolds through actions.
The next observation depends on what the agent does.
Read the supplied facts.
Produce an answer.
Decide which facts to obtain.
Choose, observe, revise, act.
The action changes the information available - not just the wording of a reply.
Initial observation / same case for all 8 rollouts
Inspect one path
Relevant history +2 · vital assessment +3 · focused exam +3 · targeted test +6
Repeated, irrelevant or incorrect actions earn 0 · finish 0
Correct diagnosis +10 · appropriate management +10 · budget kept +10
Illustrative point values, not the production reward policy. As in the live environment, each relevant step earns its own points and the final reward depends on the result. Different valid paths can receive the same return.
Group-relative feedback
All eight rollouts share an initial case and policy snapshot.
Complete the batch to reveal final returns and group-relative advantages.
Aᵢ = (Rᵢ − mean(R)) / (std(R) + ε)
| Trajectory | Process | Result | Return R | Relative A | Group signal |
|---|
Positive advantage means above this batch's mean - not “safe” or “clinically correct.” A GRPO-style trainer can use the relative signal in its clipped policy objective with reference-policy/KL constraints.
Granted-access API / 02
Contact us with your research or training use case. Credentials and integration details are shared after access is granted.
Request an API key ↘Use authenticated environment endpoints to start an encounter, inspect permitted actions and advance the episode.
Route episode feedback into your training pipeline. Keep held-out cases separate when measuring progress.
Discuss rollout integration →Endpoint URLs, authentication format, quotas and the final reward contract come with onboarding. The batch above illustrates the training flow; it does not call the service.
Policy learning / 03
Initial context. Hidden findings. A permitted clinical action space.
o₀
Questions, examinations, tests, diagnosis and treatment choices.
o[t] → a[t] → o[t+1]
Points per category, missed findings and budget use.
trajectory + scores
Use the rollout in your RL or preference-learning pipeline.
πθ → πθ′ ↺
A correct answer ≠ a good trajectory
Step-wise observations, actions, rewards and termination.
transitions.jsonl
Trajectory pairs with score gaps and behavior diagnostics.
dpo_training.jsonl
Trajectory records, scoring metadata and filter reports.
reward_model_training.jsonl
Online PPO/GRPO training is not bundled. Process and result points, verifier scores and export rewards are research signals, not evidence of clinical safety. Measure progress on held-out encounters with ClinicalBench.
Two layers. Different jobs.
Build and inspect an agent in the environment.
Compare its performance on ClinicalBench.
Work with us / 04
Request API access. Tell us about your model, rollout workload and research use case.