01 · READ
Reads many sources
CDA R2 documents, FHIR R4 interfaces and spreadsheet exports. Saumo never writes to the original system.
SAUMO · A DATA LAYER FOR HEALTHCARE
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
Six things you can build EHDS preparation on, without replacing a system.
01 · READ
CDA R2 documents, FHIR R4 interfaces and spreadsheet exports. Saumo never writes to the original system.
02 · MAP
AI suggests how the data maps to FHIR R4 structures. An expert reviews and approves the mapping before use.
03 · REPOSITORIES
Mapped data is stored in repositories separated by purpose of use.
04 · ACCESS
Users see only what their role and purpose allow.
05 · LOG
Every access leaves an entry in the access log. Supervisors can see who looked at what, and why.
06 · INTERFACE
Applications read the data through an open-standard interface, including applications built by others.
SECURITY AND PRIVACY
Saumo is designed so that your data protection officer can approve it.
READ ONLY
Saumo never writes to the patient record system. The original data stays where it is.
LOCATION
Data is processed and stored in Finland.
ACCESS
Access is based on role and purpose. Nothing extra is shown.
MONITORING
Every access is logged, and the log can be monitored and reported.
FIRST APPLICATION
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 →NEXT STEP
Book a 30-minute EHDS review. We go through where your data comes from, what the Regulation requires and in which order to proceed.