> 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-user-organizations.md).

# Progressing to Higher Maturity Levels (User Organizations)

This section provides guidance for User Organizations (e.g., healthcare providers) on how to progress between maturity levels.

Progression typically involves moving from isolated clinical use cases to enterprise-wide integration and data-driven care.

***

## Moving from Level 0–1 (None / Basic) to Level 2 (Emerging)

### Typical Situation

• SNOMED CT used in isolated workflows\
• No governance or strategy\
• Limited training

### Key Actions

• Establish ownership and governance\
• Define implementation goals\
• Expand to additional clinical areas\
• Provide basic training

### Outcome

→ Structured but limited organizational adoption

***

## Moving from Level 2 (Emerging) to Level 3 (Advanced)

### Typical Situation

• Use across several departments\
• Inconsistent workflows\
• Limited interoperability

### Key Actions

• Standardize use across departments\
• Embed SNOMED CT into workflows\
• Strengthen governance\
• Improve training and support

### Outcome

→ Consistent use across key clinical processes

***

## Moving from Level 3 (Advanced) to Level 4 (Integrated)

### Typical Situation

• Broad adoption\
• Workflow integration underway\
• Limited data use

### Key Actions

• Integrate across systems\
• Improve data quality and consistency\
• Expand interoperability\
• Introduce analytics and reporting

### Outcome

→ Fully integrated organizational use

***

## Moving from Level 4 (Integrated) to Level 5 (Optimizing)

### Typical Situation

• Integrated systems\
• Reliable data\
• Limited optimization

### Key Actions

• Implement real-time analytics\
• Enhance decision support\
• Continuously improve workflows\
• Use data for performance improvement

### Outcome

→ Data-driven, continuously improving care delivery

***

## Key Success Factors

• Clinical engagement\
• Strong governance\
• Workflow integration\
• Effective use of data

***

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=snomed-implementation-maturity-framework-guide&#x26;entry.670899847=Progressing%20to%20Higher%20Maturity%20Levels%20%28User%20Organizations%29" class="button primary">Provide Feedback</a>


---

# 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/understanding-and-progressing-maturity/progressing-to-higher-maturity-levels-user-organizations.md?ask=<question>&goal=<endgoal>
```

`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.
