Baserow stays an adapter
The temporary intake layer is useful right now, but the architecture keeps it isolated so it does not become the permanent system of record.
behringdx.health
Bridging patients and pathology with more clarity.
Behring DX is the public face of the same pathology-first system we are building behind the scenes: clearer referrals, more structured specimen workflow, sharper reporting, and a more trustworthy digital experience for clinicians and patients.
Platform shape
A cleaner stack for how the lab actually works
The product is not just report text generation. It is the workflow around specimens, blocks, slides, stains, IHC, review, and report release.
Behring owns the connective tissue
Labels, barcode targets, reconciliation, report lifecycle helpers, and pathology-specific workflow logic live here, where they can evolve without being trapped in a generic LIMS.
OpenELIS is being sharpened
The current push is to turn OpenELIS into a focused pathology operator surface instead of a broad lab menu full of biochemistry, serology, and virology branches the team does not use.
Workflow spine
The pieces we’re lining up
Referral intake
Public-facing intake with structured specimen and clinical context.
Accession + patient linkage
Middleware drives OpenELIS order creation and the sample-to-patient reconciliation layer.
Labels + barcodes
Slide, report, and lab-note labels all resolve back to the same case intelligence.
Grossing, stains, IHC
Pathology-specific steps stay explicit instead of being flattened into generic test flows.
Review + sign-out
OpenELIS becomes the reporting home once its permissions and pathology surface are tightened.
Animated System View
A motion layer that explains the product, not just decorates it
This public site can carry the same sense of system choreography as the internal platform. The flow below uses anime.js-driven SVG drawing and node motion so the stack reads as a living, connected diagnostic pathway.
Referral to report
Public intake, case orchestration, pathology workbench, and sign-out can be shown as one coherent product journey.
Public Referrals
Referral intake can live on the public site without exposing the internal lab stack
The site is ready to host a public-facing Baserow referral form as an embedded intake surface. We keep the actual form URL configurable so GitHub Pages stays static and safe.
Referral Form
Awaiting public form URL
Add a public Baserow form URL in site-config.js and this section will turn into a live intake surface.
GitHub Pages fit
Yes, this can live on GitHub Pages for free
The public track is already static, has a CNAME for behringdx.health,
and is safe to publish separately from OpenELIS, Node-RED, and the internal workbench.
- Public static marketing and referral shell on GitHub Pages
- Custom domain pointed to
behringdx.health - Internal clinical runtime kept off the public host
- Referral form URL injected as configuration, not hardcoded to a local machine
Animation direction
`anime.js` belongs in the product skin
We’re using the motion language from animejs.com as a precise interface layer, not as an AI site builder. That means better staggered reveals, responsive panels, and a product that feels intentional instead of template-ish.
- Hero choreography and section reveals
- Motion that clarifies state changes instead of decorating them
- A separate polished domain-facing experience from the internal operator workbench
Automation direction
OpenClaw fits as agent handling around the stack
OpenClaw is not the LIMS. It fits best as a set of dedicated agents around the stack: health checks, scheduled nudges, remote incident triage, and channel-based notifications.
- Ops-watch agents for middleware and OpenELIS health
- Queue-watch agents for referral and backlog notifications
- Recovery agents for safe runbook actions on an always-on machine
- Documentation agents for outage and admin recall
Right now
Two parallel tracks, one coherent product
Clinical hardening
Finish OpenELIS pathology permissions, remove irrelevant catalog noise, and make the daily operator path reliable without admin workarounds.
Brand + experience
Build `behringdx.health` in parallel so the product looks as considered as the workflow underneath it.
Ops automation
Use OpenClaw where it adds leverage around monitoring, messaging, and remote routine actions, without making it the source of clinical truth.