Service 03
Custom Development
We wrote the code that runs SENAITE LIMS. The same people who maintain the core build the parts your lab needs.
The difference is small but compounds fast. An integrator reads the docs and works around the bugs. We read the commit history because we wrote it. When the right answer is to change the core, we change the core.
Recent releases that ship in production today include the senaite.astm 2.0 instrument transport (which added HL7 v2 over MLLP next to the existing ASTM server), the SENAITY anomaly-QA layer, and the HealthWatch monitoring service that powers SENAITE Care.
Your custom code lives in a dedicated private GitHub repository. Every change goes through a pull request, which documents what changed and why. When you report an issue, we track it as a GitHub issue, fix it in a pull request, and link the two so you can follow the work from report to resolution.
Improvements that belong in the core platform are contributed upstream to the public SENAITE repositories. The whole community benefits, and your system stays close to the mainline rather than drifting into a private fork you have to maintain alone.
- Custom add-ons. Plone packages that extend SENAITE the right way — installable, upgradeable, reproducible.
- Instrument interfaces. Our own ASTM protocol handler, HL7 v2 over MLLP, serial, file-based. We scope each device individually once we have seen the interface docs.
- Workflow customization. Sample types, analysis services, calculation services, verification states, transitions.
- Report templates. Certificates of analysis, audit reports, regulatory exports, customer-branded outputs.
- System integration. ERP, LDAP / Active Directory, billing, third-party databases, instrument vendor APIs.
- JSON API extensions. Custom endpoints, push consumers, integration hooks for external systems and dashboards.
- Data migration. Bika LIMS, LabWare, STARLIMS, custom databases. We have scripts. We have war stories.
- Performance work. ZODB consistency checks, index rebuilds, query optimization, ConflictError remediation.
Most laboratories ask us to migrate everything. We generally advise against it. Pulling years of legacy data into the LIMS database inflates the system for records you rarely need at full detail, and the verification process for legacy data is rarely worth the time.
Our default is to keep your historical data accessible for reference and comparison through a database connection, and only import what genuinely needs to live in the new system — open samples and active clients at go-live, for example. You keep the history. The new system stays lean. Audits remain answerable.
- 1Hour budget
You buy a budget of hours and use them freely — consulting, development, support, debugging. We estimate each piece of work in ranges up front and bill the actual hours used.
- 2Fixed scope
Defined deliverable, milestone billing. Best for instrument integrations and migrations where the work is well bounded.
- 3Retainer
Reserved capacity per month for ongoing feature work and incident response. Best for labs where SENAITE is critical infrastructure.
Related
Pair this with
Looking for a custom solution?
Describe what you need and we will tell you how we would build it. No obligation, no sales pitch. Just a technical conversation about your requirements — and a quote.