1. Executive summary
Finland’s Digital and Population Data Services Agency (DVV) implemented the Core Public Service Vocabulary Application Profile (CPSV-AP) as the basis for a national shared service data repository, the Suomi.fi Finnish Service Catalogue (FSC). Launched in 2017 and mandated by law, the FSC provides a single point of truth for public service information from over 1,500 organisations, including all ministries, agencies, municipalities, and new regional authorities. Over 26,000 public services (with 70,900 related service channels) are described in the catalogue in a uniform, machine-readable format, enabling citizens and businesses to easily find up-to-date services on the Suomi.fi portal and allowing widespread reuse of the data via open APIs. By 2024 the FSC was processing around 358 million API requests per year from over 130 integrated digital services. This case study describes the context and motivation for reusing CPSV-AP in Finland, the implementation experience, challenges faced and solutions applied, the resulting outcomes and impacts, and key lessons learned for the future.
The Finnish Service Catalogue in numbers:
| 29 500 services | 1700 organisations | 355 million API requests in a year (2025) |
| 70 900 service channels | 9300 users (public service officials) that update the data | 240 web services that use data |
2. Context of asset reuse
In the 2000s, Finland’s government began developing a one-stop portal (now Suomi.fi) to help citizens discover public services and handle official matters online. Initially covering central government, the portal was expanded around 2009 to include services from all municipalities (around 300 at the time). However, this decentralised content model, with the Suomi.fi web editorial team updating all service pages, quickly proved unsustainable. A tiny central team struggled to keep thousands of service entries updated, leading to outdated information and broken links.
To address this, Finland conceived a centralised Service Catalogue (Palvelutietovaranto, PTV) where every public authority would enter structured descriptions of their services into a single database. Citizens could then find all services in one place (the Suomi.fi site) and agencies could reuse the data in their own websites and applications via APIs.
The PTV (now the Finnish Service Catalogue) provides a centralised, machine-readable service catalogue through which citizens can access over 26.000 services.
In 2014, the Ministry of Finance made the development of this catalogue a priority under the National Service Architecture Programme (KaPA). Crucially, in 2016 Finland enacted the Act on Central Government’s Joint e-Service Support Services (571/2016), which legally requires all public sector organisations to document their services in the FSC. This legislative mandate, along with strong top-level support, ensured nationwide participation and provided a clear governance framework. The stage was set for a unified, interoperable approach to service data management – and the emerging European CPSV-AP standard offered a timely model for the PTV’s data structure.
3. Motivation & decision rationale
Finland’s decision to reuse CPSV-AP for its service catalogue was driven by both urgent practical needs and strategic long-term considerations:
Efficiency and consistency
The immediate impetus was to replace a myriad of duplicative, inconsistent service descriptions with one standardised model. A common vocabulary would enable each service to be described once and reused, eliminating redundant work and reducing errors. The CPSV-AP – a ready-made EU standard for describing public services – aligned well with this goal by providing a core data model (covering elements like service names, providers, target groups, and channels) that could be applied across all Finnish services. Adopting CPSV-AP promised to save time and ensure consistent, high-quality data for users.
Interoperability and future-proofing
By the mid-2010s, cross-border and cross-platform interoperability of public services was becoming increasingly important (e.g. for the forthcoming European Single Digital Gateway). Using a European-standard model like CPSV-AP would make Finnish service data easily sharable and comparable across borders and systems. As Former Chief Specialist Marko Latvanen noted, the timing was ideal, Finland was designing its data model just as CPSV-AP version 2 was being developed by the European Commission. “The timing was fortunate… it was a win–win. We could draw on the European model for structure and ensure our data would be compliant moving forward, sparing us from rework later.” Finland’s experts joined the EU’s CPSV-AP working group in 2014 and 2015, contributing their real-world insights and in turn shaping the standard to better suit practical needs. This collaboration with the European Commission gave Finland confidence that it was making a future-proof choice, aligned with international best practices.
4. Implementation experience
Co-development and alignment
From the start, Finland ensured that the PTV data model was aligned with CPSV-AP. Marko Latvanen actively participated in drafting CPSV-AP release 2.0.0.[S(1] During one of the three working groups, he highlighted how Finland operationalises CPSV‑AP by using legally mandated, general service descriptions that are shared nationally and then enriched locally by municipalities with concrete details such as channels, costs, and related properties, supported by a formal two‑tier classification based on life events and target groups. Marko’s approach provided an implementation example that validates CPSV‑AP’s abstraction level, demonstrating how a common European core can support reusable base services and local specialisation without undermining interoperability.
This close cooperation meant that the PTV was effectively “born CPSV-AP compliant.” Many core classes and properties of CPSV-AP (Service, Public Organisation, Service Channel, Life Event, etc.) were directly implemented in the Finnish model. The official PTV data model description was made publicly available on the national interoperability platform, underscoring transparency and alignment with open standards.
A small section of the official Finnish Service Catalogue Datamodel
National adaptations
While CPSV-AP provided the foundation, the implementation team made adjustments to fit Finland’s context. For example, CPSV-AP’s optional concept of “Public Event” (for one-off events like town hall meetings or deadlines) was not included in the Finnish Service Catalogue, as the focus was kept on permanent public services offered to citizens and businesses. Conversely, some extensions were added: notably, Finland’s model introduced “general descriptions”, reusable template texts for common local services (e.g. library services, primary healthcare) that multiple providers can share. The PTV also includes detailed accessibility information for service locations. These additions remain compatible with CPSV-AP’s framework and demonstrate its flexibility: implementers can include extra fields or code lists for national needs without breaking the core schema. Finland also established controlled vocabularies (code lists) for categories like service types, target groups, life events, etc., to ensure data quality and semantic consistency across all entries (these code lists are published on the official PTV code registry).
Technical development
The FSC was developed by DVV as a centralised web application with two main interfaces: a web front-end (where authorised users in each organisation input and update their service information) and open APIs (OUT APIs for retrieving data, and IN APIs for system integration). The data model was finalised by 2015 - 2016, and the platform was built and tested in 2016. The official launch of the Suomi.fi Service Catalogue took place in 2017, coinciding with the full production release of the revamped Suomi.fi portal. From day one, the FSC’s open API enabled other e-services to pull the latest service information. For instance, many municipal websites were configured to fetch service details from the FSC instead of hosting their own text, ensuring that whenever a municipality updates its data in the catalogue, all connected websites show the new information immediately.
Support and training
Implementing a central repository of this scale required significant effort in change management. DVV provided comprehensive support: online guidance, detailed instructions and data model documentation, webinars and even an e-learning course (“PTV driving licence”) to train thousands of public servants in how to describe services in a user-centric way. There were early concerns from some stakeholders about the workload for maintaining data, but the agency emphasized the long-term efficiency gains. During rollout, a network of regional support persons and “PTV coaches” was formed to help local organisations populate their data. This proactive approach helped achieve broad adoption within a short period: by the end of 2017, nearly all required organisations had onboarded to the FSC, populating entries for the majority of public services nationwide.
5. Challenges & solutions
This section provides a concise overview of the main challenges encountered during the implementation of the Finnish Service Catalogue and the corresponding solutions that were put in place. The table below provides a short summary, whereas the following section dives into each challenge and solution.
|
Challenges |
Solutions |
|
|
|
|
|
|
|
|
Challenge 1: Fragmented data sources and stakeholder buy-in
Before the FSC, service information was scattered, and no single authority had a complete overview. Agencies and municipalities were initially hesitant to adopt a central system, fearing loss of control or extra work.
The 2016 law (Act 571/2016) made participation obligatory, effectively uniting all public organisations under one scheme. High-level mandates coupled with clear benefits (less duplicate effort, compliance with the Services Directive, better service to citizens) persuaded stakeholders. The legal obligation was backed by extensive training and support. As usage grew, organisations saw that a single well-maintained entry could serve multiple channels, reducing their workload in the long run.
Challenge 2: Aligning a standard model with national needs
CPSV-AP did not cover every detail that Finnish users wanted (e.g. certain sector-specific attributes), and some terms in the European model felt too oriented towards legal jargon descriptions rather than plain language for citizens.
Finland adopted CPSV-AP’s core for all common elements but made use of extensions and configurable fields for local needs. The PTV data model included additional attributes (like the general descriptions and accessibility details mentioned earlier) and omitted irrelevant parts of CPSV-AP. Thanks to the model’s flexibility, these changes were implemented without undermining interoperability.
Challenge 3: Managing complexity
As various domains (social services, education, etc.) got involved, each wanted to add new data fields, leading to a much larger model than originally envisaged. This complexity raised concerns about usability and future maintenance.
The architects kept the model modular (avoiding deep hierarchies) and documented it thoroughly. They set governance processes for evaluating any further changes, recognising that stability was crucial once hundreds of systems depend on the data format. In fact, since 2020 there have been almost no breaking changes to the data model. Even now, as part of an ongoing architecture reform to modernise the platform, DVV is avoiding major schema changes, only a few new fields will be added, and all API integrators are given until 2027 to switch to the new API version 12.
Challenge 4: Data quality and sustainability
With thousands of users entering data, how to keep information accurate, up-to-date, and useful for citizens?
The FSC team instituted quality controls and feedback loops. The system features built-in validators (for example, flagging broken web links or inconsistent formatting) and requires key fields like citizen usage instructions for each service. DVV regularly communicates with contributing organisations, providing usage analytics and reminders.
6. Outcomes & impact
The implementation of the Finnish Service Catalogue with CPSV-AP at its core has led to significant positive impacts:
Unified service information and better user experience
All public services in Finland are now described in a single repository using a standard format. This covers national, regional, and municipal services, as well as some services by NGOs and private providers. The structured data model ensures each service entry includes key details (such as description, provider, target users, service channels like contact points or e-services, and links to forms or instructions). This uniformity has greatly improved findability and clarity. Citizens and businesses can go to Suomi.fi and search for, say, a “building permit” and they will get a consolidated list of all relevant permit services across different authorities, with consistent descriptions.
Operational efficiency gains
The FSC eliminated duplicated effort. Instead of hundreds of web editors independently updating their local webpages, information is maintained once in the central catalogue and reused everywhere. This has saved countless hours of work and reduced errors.
Content is kept more current: updates happen at the source, and propagate via APIs to all consuming sites, avoiding the old problem of “last year’s info” lingering on some municipal webpage. The central system also introduced performance metrics and data quality monitoring, for example, DVV tracks how often entries are updated and can prompt lagging organisations as needed. The result is a higher quality of service information with less manual labour.
Widespread data reuse and innovation
Because FSC data is open by default, it is heavily reused not just on Suomi.fi but across Finland’s digital ecosystem. In 2023, 2024, and 2025, the Service Catalogue was handling around 350+ million API calls yearly (from both public and private sector services). At least 240 websites and applications pull data from the FSC, including 90+ municipal portals and nearly all regional health service websites. This means citizens get the same reliable information whether they visit a small town’s own site or the national portal. The shared structure of data has also enabled new digital tools. A prominent example is the Suomi.fi Permit Wizard, which helps entrepreneurs determine what permits and licences they need for a new business: the wizard dynamically queries the Service Catalogue to present relevant permit services and guidance. Similarly, various “life-event” based guide pages on Suomi.fi automatically list applicable services from the FSC. The uniform, JSON-based open API has made it straightforward for developers to integrate service data into chatbots, mobile apps, and even map services. This reuse amplifies the value of the data far beyond the initial portal.
Interoperability and EU compliance
By basing its model on CPSV-AP, Finland ensures its service data can be understood in a European context. This has positioned the country ahead of the curve for complying with EU-wide initiatives like the Once-Only Technical System and the Single Digital Gateway Regulation, which require member states to share certain service information across borders.
7. Lessons learned & future plans
High-level support and mandates are critical
A central service catalogue touches many independent organisations. Without strong top-down support, and a legal mandate, it would have been very difficult to achieve full coverage. The 2016 law was “the main reason we have this much data in the system,” noted Marko Latvanen. Clear authority and obligations drove adoption where voluntary approaches had failed in the past.
Adopt standards early, but tailor them pragmatically
Engaging in the CPSV-AP initiative from the beginning saved Finland time and ensured alignment with international standards. However, the team also learned that a standard like CPSV-AP is a basis. They advise others to adopt the core of such standards for compatibility, but not to shy away from extending the model to meet user needs, as long as these extensions are well-governed. Crucially, maintain clarity on which parts of the model are standard versus local. Documenting the data model (as Finland did on the interoperability platform) and sharing experiences in international forums can help improve the standard itself over time.
Invest in user-centric design and training
The success of the FSC depended not just on technical implementation but on thousands of people using it to input quality data. Finland’s approach was to focus on the end users of service information (citizens and businesses) and design the data fields and user interface around their needs (e.g. making descriptions simple and avoiding legal jargon). Extensive training and support ensured that the public servants who provided the data understood these principles and the importance of keeping information up to date.
Plan for sustainability and scalability
Once an interoperability asset like the FSC gains traction, it can quickly grow in scope and usage. It’s important to plan for infrastructure scalability (Finland has moved the Suomi.fi services to the cloud to handle traffic) and to be cautious about making frequent changes. The Finnish team is careful about versioning and backward compatibility, knowing that updates affect many dependent systems. Now, as they undertake a significant technical upgrade of the FSC’s API and architecture, they are doing so with a long transition period and minimal changes to the data model, to avoid disruption.
Future plans
Moving forward, Finland’s focus for the Service Catalogue is on technical renewal and enhanced services rather than expanding the data model. The FSC’s architecture is being modernised (with the rollout of “version 12” APIs by 2026–2027) to improve performance and align with current standards (e.g. using REST/JSON with standard date formats, introducing API keys for better support). The core data model will remain stable with only minor additions, so existing users (now over 240 integrations) can transition smoothly. DVV also plans to develop new tools and features that leverage rich service data. For instance, there is interest in applying AI to assist with data quality checks and to provide more personalised advice to users (e.g. chatbots that guide citizens through service options using the FSC data).
For more information, please visit the CPSV-AP GitHub and Finland’s Digital and Population Data Services Agency (DVV) webiste
Written jointly by the SEMIC team and the DVV.
(last update April 2026)