Synaptic Four · Data and research

Solum

Consent, an access check and a log, as a component beside your application, instead of building them again.

Discuss integration See the demo

What it is about

Anyone who builds clinical software increasingly has to show that data is used only for the purpose a person agreed to, and that every access can be traced.

In the EU, the European Health Data Space adds duties for clinical software: from March 2029 for patient summaries and electronic prescriptions, and from March 2031 for further areas. A logging component is one of the required parts.

Consent, the access check and the log are cross-cutting tasks. They are easy to get wrong, and they are the same at the core for every application. Solum separates them from the rest of the application and takes on this one task.

Why embed it instead of building it

  • One task, cleanly separated. The consent logic sits in one place. It is not spread through the application.
  • A log from the start. Consent and access land in one log entry. If that log write fails, the call does not count as a success.
  • Your team and your reviewers can read what the component does.

Who Solum is for

  • Manufacturers of practice, clinic and information systems for health care who do not want to build consent and the log themselves. That is the main audience. Small practices, laboratories and clinics rarely have their own development teams. They benefit from Solum through the maker of their software.
  • Development teams that build research and study applications, where access to the data depends on a consent.
  • Architects who want to separate the consent logic from the rest of the application.

How Solum fits an existing application

An authorised person records the consent or withdraws it. An access then goes like this.
  1. The application asks for access.
    It calls Solum over the HTTP interface, for example to encrypt or decrypt a field.
  2. Solum checks the stored consent.
    A valid consent must be stored for that person, that purpose and that field.
  3. Solum answers.
    On success the result comes back. Without coverage the answer is a refusal.
  4. The application acts on the answer.
    What it does with the result is its own logic.
  5. The event is logged.
    A read of the consent state writes no line.

Integration guide in the Solum repository

Architecture in the Solum repository

Anyone who places clinical software on the market has to describe outside components in their own technical documentation. For medical devices under IEC 62304, that includes, for example, the version, the requirements and known faults. For that, Solum provides fixed versions with a changelog, an integration guide, a security overview, a threat model, the process for security incidents, and a public issue list.
What the manufacturer still does: sign-in and roles, the screen for recording consent, how the application uses the result, custody of the keys, and their own conformity assessment.

Your data and your independence

Consent records and the log sit in files whose location you set. Solum does not send them to a service of Synaptic Four.
The guides and the operations handbook are public. Operation without Synaptic Four is described there.

Status and limits

Early use
The integration guide is public. The component has not been tried in production operation.
Solum includes country profiles. The profile for Kenya is for evaluation. The profiles for Nigeria and South Africa are drafts.
Implemented
  • Recording and withdrawing consent, a check per person, purpose and field, and a log in the same call
  • A getting-started guide, an integration guide and an operations handbook
Not checked yet
  • a full run in a live application
Not included
  • a medical record, interpretation of findings, certification
Older functions without an authorisation check are not the integration interface and are not meant to be built in.

What Solum is not

Solum is not a medical record, does not interpret findings, and does not replace the manufacturer’s certification.
Whether a person consented is not decided by Solum. An authorised person records the consent.

Cost and licence

  • €0

    Evaluation

  • €18,000

    Manufacturer licence, per year and product line, any number of installations

  • €4,800

    Integration sprint, four days

Solum is under the Business Source License 1.1. The source can be read. Non-commercial research, academic use, education and internal research operation are free of charge. Using it in a product that is sold needs the manufacturer licence. Each version becomes Apache-2.0 after four years.
Evaluation and integration are free of charge. The manufacturer licence is charged only when your product with Solum goes to customers.

All offers on this path

Do you build clinical software and are you considering building Solum in?

Describe your application and your consent case. The conversation clarifies the interfaces and the integration path. The evaluation is free of charge.

Discuss integration See the demo