Skip to content
Luiz Hogrefe

AnyClinical

Research prototype on governed workflows in clinical coordination

Workflow-governance prototype · unpublished

How can a workflow around clinical care stay evidence-bound, authority-aware and explicitly handed to people at the right boundaries, including by declining to act?

Research concept on anylai.eu

Overview

33tests in the repository

AnyClinical governs the workflow around care, not care itself. Its reference workflow coordinates visits in a clinical trial: consent is a precondition, escalations are tracked until someone acknowledges them, and work is handed to people wherever authority lies with them.

It has no place to record a clinical finding, by design. The ERQYO reference implementation runs next to it in shadow mode, behind flags that are off, to compare decisions without acting on them.

The six prototypes share one application kernel in the AnyLAI repository: cases, a hash-chained event timeline, evidence with provenance and three timestamps, tasks and authority acts. Each prototype adds only its own vocabulary and rules.

A visit-coordination workflow

A visit-coordination workflow
Consent state
  1. Visit requested
  2. Consent checkGRANTED
  3. Scheduling task for the coordinator
    Escalation if not acknowledged RAISED → ACKNOWLEDGED → RESOLVED

no field for a clinical finding

Choose the consent state and follow where the workflow is allowed to go.

Text description of the diagram

A trial visit is requested. The workflow first checks consent. Only with consent GRANTED does it create a scheduling task for the coordinator. With consent refused, withdrawn, expired or not recorded, it stops and hands over to the study team. If a scheduling task is not acknowledged in time, an escalation is raised and tracked until it is acknowledged and resolved. No step records a diagnosis or a treatment.

Building blocks

  • Consent state

    NOT_RECORDED, GRANTED, REFUSED, WITHDRAWN or EXPIRED, checked before any step.

  • Escalation state

    NONE, RAISED, ACKNOWLEDGED, UNACKNOWLEDGED or RESOLVED.

  • Capability

    What an actor may do in the workflow, such as coordinate or escalate.

  • Workflow definition

    A versioned description of steps, preconditions and handoffs.

  • Handoff

    An explicit transfer to a person, recorded with its reason.

Withdrawn consent

  1. 1

    A participant's next visit is due, and the workflow prepares a scheduling task.

  2. 2

    The consent check finds consent WITHDRAWN.

  3. 3

    The workflow does not schedule; it records why and hands the case to the study team.

  4. 4

    Nothing in the system suggests what should happen clinically. That judgement stays with clinicians.

How it differs

  • AnyClinical ≠ ERQYOReference implementation · not deployed

    ERQYO is the general decision runtime; AnyClinical is one applied workflow where it is compared in shadow mode.

    ERQYO

  • AnyClinical ≠ COADFPublished framework

    COADF gives the governance principles; AnyClinical tests them in a domain where abstaining is often the correct outcome.

    COADF

Status

Workflow-governance prototype · unpublished

Workflow-governance research prototype in the AnyLAI repository, with one reference workflow. Unpublished, not deployed, not run on real data. No AI model is called.

Explicit non-goals and limits

  • It does not diagnose.
  • It does not recommend or decide treatment.
  • It is not a medical device, and it makes no medical-device claim.
  • Clinical judgement stays with clinicians. The system has no place to record a clinical finding.

← Back to Projects