> 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/assessment-criteria.md).
# Assessment Criteria
## What are Assessment Criteria?
Assessment Criteria are the detailed evaluation questions, statements, or checkpoints used to measure the maturity and effectiveness of a specific Key Process Area (KPA).
They define the standards, practices, or capabilities that must be evaluated in order to determine how well a process area is implemented, managed, and optimized.
## Purpose of Assessment Criteria
Assessment Criteria help:
* Standardize the evaluation process
* Ensure consistency across assessments
* Capture measurable evidence
* Identify capability gaps and improvement opportunities
* Support objective maturity scoring
Each criterion is designed to assess a specific aspect of a KPA and contributes to the calculation of the overall KPA Maturity Index.
## Structure of Assessment Criteria
Assessment Criteria are typically presented as questions or measurable statements.
Each assessment criterion typically includes:
* **Question**
* A clear evaluation question defining what is being assessed.
* **Context**
* Guidance explaining what should be considered during evaluation.
* **Maturity Levels and Scoring**
* Standardized maturity levels describing increasing capability maturity, each associated with a score.
## Examples of Assessment Criteria
Examples include:
* Governance Structure, organizational oversight and accountability
* Strategic Alignment, alignment with healthcare priorities
* Affiliate Adoption, extent of SNOMED CT uptake
* Monitoring and Metrics, tracking adoption and usage
* Stakeholder Engagement, collaboration with key participants
* User Training, education and capability development
* Clinical Workflow Integration, embedding into daily processes
* Data Exchange, interoperability across systems
* Terminology Updates, maintenance and version management
* Search and Usability, effectiveness of terminology tools
* Decision Support, use in clinical guidance and alerts
* Analytics and Reporting, use for insights and reporting
{% hint style="info" %}
To see the specific criteria/questions for each stakeholder, please refer to the full assessment, which can be found here: [SNOMED CT Implementation Maturity Assessment](/snomed-ct-practical-guides/implementation-maturity-framework-guide/snomed-ct-implementation-maturity-assessment.md)
#### Stakeholder-specific assessments:
* Members: [Maturity Assessment for Members (National Release Center)](/snomed-ct-practical-guides/implementation-maturity-framework-guide/snomed-ct-implementation-maturity-assessment/maturity-assessment-for-members-national-release-center.md)
* User organisations: [Maturity Assessment for User Organizations](/snomed-ct-practical-guides/implementation-maturity-framework-guide/snomed-ct-implementation-maturity-assessment/maturity-assessment-for-user-organizations.md)
* Software products: [Maturity Assessment for Vendors/ Software Products](/snomed-ct-practical-guides/implementation-maturity-framework-guide/snomed-ct-implementation-maturity-assessment/maturity-assessment-for-vendors-software-products.md)
{% endhint %}
### Ranking and Scoring
Each assessment criterion is evaluated using standardized ranking options that are closely aligned with the overall maturity model of the framework.
The ranking levels represent progressive stages of capability maturity, from limited or ad hoc implementation to optimized and continuously improving practices. This ensures consistency between individual assessment criteria, KPA Maturity Indexes, and the Overall Maturity Level.
The framework typically uses a maturity scale such as:
* 0 - Not Implemented
* 1 - Initial / Ad Hoc
* 2 - Defined / Structured
* 3 - Advanced / Established
* 4 - Integrated / Continuously Improved
* 5 - Optimized / Adaptive Ecosystem
Each level is associated with a predefined score that contributes to maturity calculations across the framework.
This close alignment with the maturity model enables:
* Consistent and objective evaluation
* Comparable scoring across KPAs
* Clear identification of maturity progression
* Structured roadmaps for continuous improvement
Higher maturity levels indicate stronger governance, broader adoption, improved interoperability, and more advanced operational capabilities.
## Role in the Maturity Assessment
Assessment Criteria act as the operational layer of the framework. They translate high-level KPAs into practical and measurable evaluation points.
The results collected from all criteria within a KPA are consolidated to generate a maturity score for that process area. These scores are then combined to determine the organization’s overall maturity level.
## Importance of Well-Defined Criteria
Well-designed assessment criteria ensure that the maturity assessment is:
* Objective
* Repeatable
* Measurable
* Transparent
* Actionable
Clear and comprehensive criteria improve the accuracy of the assessment and provide meaningful insights that support informed decision-making and continuous improvement initiatives.
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/assessment-criteria.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.