Zum Hauptinhalt springen

ZeqDosing

PK/PD, dose-response, clinical trial modeling.

  • Protocol ID — zeq-dosing
  • Category — Pharma
  • Endpoint — POST /api/pharma/dosing
  • Auth — api-key
  • Rate limit — 15/min
  • Version — 1.287.0
  • Precision — ≤0.1% (KO42-enforced)

What it does

Individualized drug dosing. Population PK models (NONMEM-style), Bayesian dose adjustment, therapeutic drug monitoring with HulyaPulse sampling schedules.

Signature

Request

POST /api/pharma/dosing
ParamTypeRequiredDefaultDescription
drugstringDrug name or identifier.
patientParamsobject{ weight_kg, creatinine, age, sex }
levelsarray[{ time, concentration }] measured drug levels.

Response

{ recommendedDose, interval_hr, peakPredicted, troughPredicted, auc, zeqond }

Runnable example

curl -sS -X POST \
-H "Authorization: Bearer $ZEQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"drug": "<value>",
"patientParams": {},
"levels": []
}' \
"https://api.zeq.dev/api/pharma/dosing"

Integrate

  1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
  2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
  3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

  • Near — wrap /api/pharma/dosing in a language SDK so builders can call it in three lines.
  • Medium — publish a reference integration demonstrating ZeqDosing alongside a real workload, with pulse-aligned metrics.
  • Far — propose ZeqDosing as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.