You know where you stand.
You know what comes first.
You know what it costs.
What this is about
Technical work in research and health rarely fails because of one technology. More often there is no shared picture of what is already there, what a new rule actually requires, and which step comes first.
Synaptic Four helps research institutions, clinics, companies and development teams to build that picture, to plan a workable solution and to bring it into operation. The starting point is always the concrete situation:
- Which systems are already there?
- Which requirements apply?
- Which people and means are available?
- What shows that the solution does its job?
You do not get a general technology recommendation.
Four kinds of engagement
Understand and sort the requirements
Synaptic Four checks which requirements matter technically for your project and how your infrastructure stands against them. The check separates:
- what is already met
- technical gaps
- organisational tasks
- questions for legal review or for the competent authority
The result is a technical orientation.
Review infrastructure and software
A review shows how an existing system works today and where the risks are. Depending on the engagement, it can cover:
- structure and the components in use
- data flows and storage locations
- sign-in and permissions
- interfaces and standards
- logging and error handling
- backup and restore
- installation, configuration and operation
- tests, known limits and maintainability
Build software
A project runs in this order:
- Clarify requirements and use cases.
- Set the structure and the interfaces.
- Build a bounded prototype.
- Check functions and failure cases.
- Document and hand over.
- Support operation when needed.
Plan and hand over
The aim is that your team understands the solution and can carry it on as far as possible.
Typical results
The table shows what is in hand at the end of an engagement.
The exact scope is the written offer.
| Engagement | Result |
|---|---|
| Assessment (up to 2 days) | A report on the current state and the gaps, a plan with effort and cost, a conversation of 60 minutes |
| Compact assessment (half a day) | A result of one to two pages, for example on a data management plan or a short code review |
| Infrastructure review | An overview of the structure, a sketch of the data flows, a risk list, an action plan |
| Assessment of the European Health Data Space | An overview of the relevant requirements, the gaps, the order of the steps |
| Prototype or first version | A working proof of the function, source code, an installation guide, handover documentation |
| Data management plan | The data flow, responsibilities, a concept for storage and access |
How the work starts
- First conversation. 30 minutes, free of charge, with no obligation. It shows whether the work fits.
- Assessment. Up to two days remotely, with a written report.Payment is after the report.
- Project or ongoing support. A project with a fixed price and acceptance criteria,Ongoing support for at least three months.
The page on the whole path to operation is Conversation to operation →
What it costs
| Format | Price |
|---|---|
| Compact assessment, half a day | €600 |
| Assessment, up to 2 days | €1,800 fixed price |
| Project | Fixed price from the day rate: €1,200, for research and non-profits €960 |
| Ongoing support | €2,400 per month for two days, minimum term three months |
All prices are net plus VAT. The written offer is binding.
Which format fits?
| If you … | fits | from |
|---|---|---|
| need a first orientation on one clearly bounded question | Compact assessment | €600 |
| want a system or a project assessed thoroughly | Assessment | €1,800 |
| want a function, a prototype or a component built | Project | at the day rate |
| need technical support on a regular basis | Ongoing support | €2,400 month |
| want to try a product for 90 days on your side | Pilot | €10,000 |
| want to use a product on a lasting basis | Commitments | Ferrum , Solum , BioResearch Assistant |