References

Two client relationships we are allowed to name.

We would rather describe two engagements we can name than seven we cannot. These two are public. Everything else we discuss once an NDA or the client's permission is in place.

Länsi-Uusimaa Wellbeing Services County (LUVN), a Finnish wellbeing services county · 2023 →

From data production to Data as Software

The county skipped conventional data warehousing and went straight to a Data Lake and Lakehouse architecture. Over two years its data production moved to a Data as Software model: SQL work became PySpark, hand-validated pipelines became unit-tested transformation functions, and data contracts now travel with the code.

After the first release, new functionality reached production every week. The way of working was written down and can be repeated elsewhere.

Read the full case

“Moving to a Data as Software model has fundamentally transformed how we approach data production — we want to understand the data and produce knowledge. The past two years of close collaboration have allowed us to treat data as a core product — improving both the speed and reliability of our data pipelines and data products. For a wellbeing services county, this means more accurate, data-driven insights that ultimately support better decision-making and better care for our citizens.”

Henna Degerlund, Chief Data Architect, Länsi-Uusimaa Wellbeing Services County

Istekki · 9/2025 →

AI Lab — an assessment of AI in health and social care

A joint assessment that identifies and evaluates AI models built in Finnish university hospitals and wellbeing services counties. The aim is to find the ones with the most potential to change care services and the decisions made around them. Invinite runs the assessment.

Why these relationships continue

We build no locks. Our longest partnership has run two years without one, and the client has chosen to carry on month after month. The reason is that work done well opens the next step: platform development leads to data production, data production leads to AI, and AI leads to how people actually do their jobs. Each step is a separate decision and a separate engagement.

Other recurring types of work

Work we have done in more than one environment. Client specifics stay between us and the client.

Roadmap and architecture work

What this demonstrates

  • A data architecture that can be governed, laid out as staged steps
  • Technical and organisational change in one plan

OMOP and research data

What this demonstrates

  • Source systems brought into a shared analytical model
  • Vocabulary mappings maintained and documented
  • Repeatability and secondary use processes

Data platform builds

What this demonstrates

  • A hybrid data platform delivered inside a regulated environment
  • IAM, monitoring, release models and resilience at production level

AI readiness reviews

What this demonstrates

  • Ownership, data, environment and lifecycle reviewed together
  • A concrete route from pilot through to production

Situation centre concepts

What this demonstrates

  • Resource and operational data brought together for day-to-day steering
  • Harmonising the sources and deciding who reads what

Regional data integration

What this demonstrates

  • Interoperability across a whole wellbeing services county
  • FHIR and OMOP applied in practice

Where regulated software development meets data architecture

What this demonstrates

  • The boundary between MDR/IVDR/MDSW environments and data work
  • Documentation, traceability and release models handled together

GET IN TOUCH

Have you got a project that needs taking all the way into use? Let's talk.

If we can't help, we'll say so.

contact@invinite.fiLinkedIn / @inviniteHelsinki · Tampere