What each product is made of, and how it was built.
Seven products, seven engineering records. Every claim on these pages is traceable to code in the repository named on it — the stack, the mechanisms that keep records correct, the data model, what it connects to, and what it deliberately does not do yet.
Engineering documentation, one page per product
Each page pairs with the service page it documents: the service page is what it does for you, the resource page is how it works.
HMO Solution
The engineering record behind delegated UM, credentialing, claims and quality on one contract graph.
eklotho-nexus · development/backend + development/frontendRead the tech →EMR Solution
The engineering record behind a clinical EMR that reads and writes the same record the network runs on.
eklotho-nexus · development/emr-frontend + development/backendRead the tech →eRx Solution
The engineering record behind a prescribing engine that treats e-prescribing vendors as swappable transmission channels behind one gateway.
eklotho-nexus · development/backend (app/services/erx, routers, models) + development/emr-frontendRead the tech →Phlebotomy Solution
The engineering record behind referral intake, dispatch, the offline field app and chain of custody.
soCal · a separate repository from eklotho-nexusRead the tech →RPM Solution
The engineering record behind device ingest, alert rules, monthly compliance and the readings a clinician sees in the chart.
eklotho-nexus · development/backend + development/careprogram-frontendRead the tech →CCM Solution
The engineering record behind enrollment, coded care plans, care-time tiers and an attested monthly review.
eklotho-nexus · development/backend + development/careprogram-frontendRead the tech →Laboratory Solutions
The engineering record behind ordering authority, chain of custody, result verification and PHI redaction.
getclrd · a separate repository from eklotho-nexusRead the tech →Traceable, or it is not on the page
- Every mechanism described here was read out of the codebase. Each page names the modules and services it was written from, and nothing appears on it that the code does not do.
- Scope questions are answered directly rather than on a page. Tell us what your programme needs and we will tell you what is in place today and what would be built for you.
- No invented numbers, benchmarks, uptime figures or customer counts appear anywhere on these pages. No procedure-code identifiers are published — the CPT set is licensed by the AMA. No reimbursement outcome is promised.
- Infrastructure is designed for HIPAA obligations under a BAA. We document the controls and hand over the runbooks; there is no such thing as certified software here and we do not claim it.