CI/CD
Merge, test, ship as a pipeline: continuous integration proves every change; continuous delivery makes releasing boring.
In one line
CI/CD turns software delivery into an automated pipeline: every commit is built and tested (continuous integration), and releases flow through staged, repeatable deployments (continuous delivery) instead of heroic release weekends.
How it works
A pipeline definition lives in the repo (GitHub Actions, GitLab CI): on every push — lint, type-check, unit tests, build; on merge — integration tests, artifact build, deploy to staging, then production with progressive strategies (canary, blue-green) and instant rollback. The cultural half matters as much as the tooling: small changes, trunk-based flow, and the pipeline as the only road to production — which is also an audit trail regulators appreciate.
Where it shows up in digital health
Health software amplifies the stakes: an EHR integration regression is a patient-safety event, so the pipeline carries extra gates — profile validation for FHIR artefacts, security scans, evidence capture for quality systems (IEC 62304 contexts). This platform's own launch gate (roadmap M5) requires exactly this: typecheck, lint, build and tests on every PR before anything public ships.