> 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/understanding-and-progressing-maturity/progressing-to-higher-maturity-levels-vendors-software-products.md).
# Progressing to Higher Maturity Levels (Vendors / Software Products)
This section provides guidance to support Vendors in progressing to higher levels of maturity in SNOMED CT-enabled products.
Progression typically involves moving from basic feature support to fully integrated, intelligent, and interoperable platforms.
***
## Moving from Level 0–1 (None / Basic) to Level 2 (Emerging)
### Typical Situation
• Limited or no SNOMED CT support\
• Basic functionality
### Key Actions
• Introduce SNOMED CT into core product features\
• Enable basic coding and storage\
• Provide initial user interfaces
### Outcome
→ Initial SNOMED CT capability in the product
***
## Moving from Level 2 (Emerging) to Level 3 (Advanced)
### Typical Situation
• SNOMED CT supported in some modules\
• Basic usability
### Key Actions
• Expand coverage across modules\
• Improve usability (search, selection)\
• Introduce structured terminology processes
### Outcome
→ Consistent SNOMED CT functionality across the product
***
## Moving from Level 3 (Advanced) to Level 4 (Integrated)
### Typical Situation
• Good coverage\
• Limited interoperability depth\
• Manual terminology processes
### Key Actions
• Implement terminology lifecycle management\
• Strengthen interoperability (standards-based exchange)\
• Improve data consistency\
• Automate updates and versioning
### Outcome
→ Scalable, interoperable product architecture
***
## Moving from Level 4 (Integrated) to Level 5 (Optimizing)
### Typical Situation
• Strong platform capability\
• Limited advanced features
### Key Actions
• Introduce advanced analytics and CDS\
• Optimize performance and usability\
• Enable innovation and new use cases\
• Continuously improve based on feedback
### Outcome
→ Intelligent, data-driven platform
***
## Key Success Factors
• Strong product design\
• Robust terminology management\
• Standards-based interoperability\
• Continuous innovation
***
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/implementation-maturity-framework-guide/understanding-and-progressing-maturity/progressing-to-higher-maturity-levels-vendors-software-products.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.