We show that the system does what its requirements say
A product under a standard has to work, and you have to be able to show that it does. We write requirements that a test can check, test the hardware automatically, and link each requirement to its test and its result. We have worked this way on medical software to IEC 62304, class C.
Scope
What we take on
Alongside the development, or added to a project that is already running.
We work with
- IEC 62304, class C
- Continuous integration
- Hardware-in-the-loop tests
- Traceability
Early prototypes for the risky parts
We try the parts that could stop the project first, on a prototype, before the rest of the work depends on them.
Work to your standard
Where an IEC or ISO standard applies, the work follows its process and produces the documents it asks for.
Automatic checks on every change
Continuous integration builds and tests every software change. A change that fails a test is held back.
Hardware-in-the-loop tests
The board runs against a test rig that simulates its surroundings, so tests repeat without anyone at the bench.
Traceability
Each requirement is linked to its design and its test, so a requirement without a test shows as a gap.
Questions
Questions about standards and certification
Are you certified to ISO 9001 or ISO 13485?
No. KINAV holds no certification of its own. When we work as part of your team, we work in your quality system.
Which standards have you worked to?
IEC 62304, class C, for the control logic and drivers of a heart-lung machine's gas blender. Tell us in the first call which standard applies to your product.
Can you join a project that is already running?
Yes. Automated tests, hardware-in-the-loop tests or traceability can be added to a project under way. We start by reading the requirements and the tests that exist.

Oleksii Kvasnikov · Founder and lead engineer
A product that has to meet a standard
Tell us which standard applies and how far your requirements are written down.