Skip to content

SAUMO  ·  A DATA LAYER FOR HEALTHCARE

A read-only data layer beside your patient record system.

Saumo reads data from your current system, maps it to FHIR R4 with a person reviewing the mapping, and shares it with applications under control. The original system stays untouched.

FEATURES

What Saumo does

Six things you can build EHDS preparation on, without replacing a system.

Saumo screen: a test repository with its records by resource type. Synthetic data only.

01  ·  READ

Reads many sources

CDA R2 documents, FHIR R4 interfaces and spreadsheet exports. Saumo never writes to the original system.

02  ·  MAP

AI suggests, a person approves

AI suggests how the data maps to FHIR R4 structures. An expert reviews and approves the mapping before use.

03  ·  REPOSITORIES

Data kept in order

Mapped data is stored in repositories separated by purpose of use.

04  ·  ACCESS

Role and purpose

Users see only what their role and purpose allow.

05  ·  LOG

Every access is recorded

Every access leaves an entry in the access log. Supervisors can see who looked at what, and why.

06  ·  INTERFACE

A standards-based interface

Applications read the data through an open-standard interface, including applications built by others.

SECURITY AND PRIVACY

Patient data stays under your control

Saumo is designed so that your data protection officer can approve it.

Illustration: a padlock beside an access log where every read is recorded.

READ ONLY

No write access

Saumo never writes to the patient record system. The original data stays where it is.

LOCATION

Data processed in Finland

Data is processed and stored in Finland.

ACCESS

Bound to purpose

Access is based on role and purpose. Nothing extra is shown.

MONITORING

Everything leaves a trace

Every access is logged, and the log can be monitored and reported.

STANDARDS

Built on open standards

Saumo is FHIR R4 native, aligned to the HL7 Europe Base and Core profiles STU 2.0, and tracks the balloted European Patient Summary guide.

The EHDS Regulation does not name a technical standard. The European exchange format will be set by implementing act, and we follow its preparation.

Illustration: differently shaped pieces plugging into one shared connector.
  • FHIR R4
  • HL7 EUROPE BASE STU 2.0
  • HL7 EUROPE CORE STU 2.0
  • CDA R2 (READ)
  • EUROPEAN PATIENT SUMMARY (TRACKED)
  • SMART ON FHIR

FIRST APPLICATION

Saumo Esikooste

An app for professionals that builds a pre-visit summary from Saumo data. Esikooste shows only what the role and purpose allow, and tells you the source of every item.

Esikooste reads data only through the Saumo interface. It never changes patient records.

Ask for a demo →
Saumo Esikooste app: a signed-in user connected to Saumo, with the stated purpose shown. Synthetic data.

NEXT STEP

Let us start with your data sources.

Book a 30-minute EHDS review. We go through where your data comes from, what the Regulation requires and in which order to proceed.