How to build regulated systems
Practical guides to the systems regulated companies build most: the modules, the architecture, the integrations, the rules and a phased plan from prototype to production.
Each guide ends with the OceanLab product builds that match the system.
- Claims management systemThe modules, architecture and integrations a claims system needs, the rules it must follow, and an order to build it in, from a clickable prototype to production.4 matching builds
- KYC onboarding systemThe parts of a know-your-customer and know-your-business onboarding system, how they fit together, the rules behind them and an order to build them in.5 matching builds
- Loan origination systemThe modules a loan origination system needs, from application to funding, how to structure the credit decision so it can be explained, and an order to build it in.5 matching builds
- EHR systemThe modules, data model and integrations an electronic health record needs, the rules it must follow, and an order to build it in, from a clickable prototype to a live clinic.5 matching builds
- Patient portalWhat a patient portal needs, how it connects to clinical systems, the privacy and access rules behind it, and an order to build it in.4 matching builds
- Telehealth platformThe parts of a telehealth platform, from booking and video to prescribing and follow-up, the rules that apply to remote care, and an order to build it in.4 matching builds
- Remote patient monitoring systemHow readings get from a device at home to a clinician who acts on them, the rules for monitoring software, and an order to build it in.4 matching builds
- Medical billing systemHow a medical billing system turns care into paid claims, the payer rules it must follow, and an order to build it in.2 matching builds
- Pharmacy management systemWhat a pharmacy system needs, from safe dispensing to batch-level stock and controlled drug registers, the rules behind it, and an order to build it in.1 matching builds
- Clinical trial management systemThe parts of a clinical trial system, from site setup and visits to eConsent and safety reporting, the GCP and Part 11 rules behind them, and an order to build it in.3 matching builds
- Core banking systemWhat a core banking system does, the ledger and controls at its heart, the systems around it, and an order to build or modernise it in.3 matching builds
- Payment gatewayThe parts of a payment gateway, from checkout and tokenisation to routing, disputes and settlement, the card and payment rules behind it, and an order to build it in.5 matching builds
- AML and fraud monitoring systemHow transaction monitoring, sanctions screening and fraud detection fit together, the case work behind them, the rules they serve and an order to build them in.3 matching builds
- Reconciliation and treasury systemHow bank, processor and ledger data are matched, how treasury sees and moves cash, the controls around payments, and an order to build it in.3 matching builds
- Regulatory reporting systemHow regulatory returns are built from source data instead of spreadsheets, the checks and sign-off around them, and an order to build it in.4 matching builds
- Investment platformThe parts of an investment platform, from onboarding and suitability to orders, positions and reporting, the rules behind them, and an order to build it in.6 matching builds
- Crypto walletHow self-custody wallets and institutional custody platforms handle keys, approvals and many chains, the rules that apply when you hold assets for others, and an order to build it in.5 matching builds
Two ways to work with OceanLab
Project build
We design and build the system as one project. It starts with a clickable prototype your team tries before any production code is written. Pay per milestone (outcome-based) or hourly at $30-50/hr, depending on role and seniority.
Embedded engineers
Our engineers join your team on a flexible monthly retainer. Part-time is fine and it runs month to month, with hours that overlap the US, UK and Europe, the Middle East, and Australia and Asia. Outcome-based or $30-50/hr.
Questions
Are these guides tied to one vendor or stack?
No. They describe the parts every version of the system needs. The stack depends on your team, your existing systems and your rules.
Do the guides include timelines and prices?
They list what drives the cost and the order to build in, not fixed numbers. Use the software development cost tool for an estimate based on your scope.
