> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-practical-guides/implementation-maturity-framework-guide/framework-design/target-stakeholders.md).
# Target Stakeholders
## Overview
The SNOMED CT Implementation Maturity Framework (IMF) is designed to support a multi-stakeholder ecosystem, recognizing that successful implementation of SNOMED CT depends on coordinated efforts across national bodies, healthcare providers, and technology vendors.
The framework defines three primary stakeholder groups, each with distinct roles, responsibilities, and maturity assessment perspectives:
* Members (National Release Centers)
* User Organizations (software consumers)
* Vendors (software providers)
While all stakeholders are assessed across the same domains and maturity levels, the focus of assessment differs depending on the stakeholder type.
{% hint style="info" %}
For vendors, the IMF assesses the maturity of individual software products or platforms, rather than the organization as a whole.
{% endhint %}
***
## Relationship Between Stakeholders
The IMF reflects a connected ecosystem model, where each stakeholder group depends on the others:
* Members provide governance, standards, and infrastructure
* Vendors develop products that implement those standards
* User Organizations deploy and use those products in real-world care settings
This relationship can be summarized as:
Stakeholder
Primary Role
Assessment Focus
Members
Enable
National systems and governance
Vendors
Build
Individual products and platforms
User Organizations
Use
Organizational implementation and workflows
Effective SNOMED CT implementation requires alignment across all three groups.
***
## Stakeholder Roles
### Members (National Release Centers)
Members are typically national or regional organizations responsible for governance and stewardship of SNOMED CT within a country or jurisdiction.
**Key Responsibilities**
* Define national strategy and policy
* Manage SNOMED CT licensing and distribution
* Develop and maintain national extensions
* Support interoperability at a national level
* Provide guidance and support to implementers
**Assessment Focus**
Assessment focuses on national capabilities, including governance structures, infrastructure, and adoption across the healthcare system.
**Role in the Ecosystem**
Members enable the environment in which SNOMED CT can be adopted and used consistently across healthcare systems.
***
### User Organizations (Software Consumers)
User Organizations include healthcare providers and other entities that use SNOMED CT in clinical and operational workflows.
**Key Responsibilities**
* Implement SNOMED CT within clinical systems
* Support structured clinical documentation
* Ensure consistent and accurate coding practices
* Enable data-driven clinical decision-making
* Participate in interoperability initiatives
**Assessment Focus**
Assessment focuses on organizational implementation, including system integration, clinical usage, and workforce capability.
**Role in the Ecosystem**
User Organizations deliver care and generate clinical data, realizing the practical value of SNOMED CT.
***
### Vendors (Software Providers)
Vendors are organizations that develop and maintain software systems that enable SNOMED CT use, such as electronic health records (EHRs), terminology services, and interoperability platforms.
**Key Responsibilities**
* Integrate SNOMED CT into products and platforms
* Provide terminology services and tooling
* Support interoperability standards (e.g., FHIR)
* Enable usability within clinical workflows
* Maintain compliance with SNOMED CT licensing
**Assessment Focus**
While vendors are a key stakeholder group, the IMF assesses the maturity of individual products, platforms, or solutions, rather than the vendor organization as a whole.
This means that:
* Different products from the same vendor may have different maturity levels
* Assessment focuses on product capabilities, such as terminology integration, interoperability, and usability
* Results reflect the real-world functionality available to user organizations
**Role in the Ecosystem**
Vendors build the tools and infrastructure that make SNOMED CT usable and scalable across healthcare systems.
***
## Shared Responsibilities
Although roles differ, all stakeholders share common responsibilities:
* Supporting semantic interoperability
* Ensuring high quality, structured clinical data
* Aligning with standards and best practices
* Contributing to continuous improvement
Collaboration between stakeholders is essential to achieve end-to-end maturity.
***
### Collaboration and Alignment
Achieving higher levels of maturity requires active collaboration between stakeholders.
Examples include:
* Members working with vendors to define national requirements
* Vendors delivering product capabilities aligned with standards
* User organizations providing feedback to improve systems and policies
A lack of alignment between stakeholders can limit progress, even if individual components are mature in isolation.
***
Provide Feedback
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/implementation-maturity-framework-guide/framework-design/target-stakeholders.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.