> 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/snomed-ct-implementation-maturity-assessment/maturity-assessment-for-user-organizations/example-user-organization.md).

# Example: User Organization

## Scenario

A regional hospital that:

* Uses SNOMED CT in several key departments (e.g., emergency, inpatient)
* Has invested in clinician training and support
* Has inconsistent workflow integration across systems
* Has limited interoperability with external partners
* Uses SNOMED CT minimally for analytics and decision support

This reflects a typical provider organization, where adoption is driven by local clinical needs rather than enterprise-wide strategy.

***

## Step 1: Score Key Questions

### KPA: Scope of SNOMED CT Implementation

| Question           | Selected Option                           | Score |
| ------------------ | ----------------------------------------- | ----- |
| Clinical Areas     | Partial – uneven coverage                 | 25    |
| Clinical Workflows | Developing – partial workflow integration | 25    |

KPA Score = (25 + 25) ÷ 2 = 25

***

### KPA: Governance and Strategy

| Question             | Selected Option      | Score |
| -------------------- | -------------------- | ----- |
| Governance Structure | Basic governance     | 25    |
| Strategic Alignment  | Informal discussions | 25    |

KPA Score = 25

***

### KPA: User Proficiency and Training

| Question          | Selected Option      | Score |
| ----------------- | -------------------- | ----- |
| Training Programs | Structured programs  | 50    |
| User Support      | Identified champions | 50    |

KPA Score = 50

***

#### KPA: Interoperability

| Question            | Selected Option          | Score |
| ------------------- | ------------------------ | ----- |
| Data Exchange       | Limited interoperability | 25    |
| Standards Alignment | Incomplete mappings      | 25    |

KPA Score = 25

***

### KPA: Analytics and Decision Support

| Question         | Selected Option | Score |
| ---------------- | --------------- | ----- |
| Analytics Tools  | Basic analytics | 25    |
| Decision Support | Limited tools   | 25    |

KPA Score = 25

***

## Step 2: Overall Maturity Level

<table><thead><tr><th width="265.257080078125">Area</th><th width="207.8359375">Score</th><th>Level</th></tr></thead><tbody><tr><td>Scope of Implementation</td><td>25</td><td>Level 1–2</td></tr><tr><td>Governance &#x26; Strategy</td><td>25</td><td>Level 1</td></tr><tr><td>Training &#x26; Support</td><td>50</td><td>Level 2</td></tr><tr><td>Interoperability</td><td>25</td><td>Level 1</td></tr><tr><td>Analytics &#x26; CDS</td><td>25</td><td>Level 1</td></tr><tr><td>Overall</td><td>30</td><td>Level 1 – Basic</td></tr></tbody></table>

Domain Score = (25 + 25 + 50 + 25 + 25) ÷ 5 = 30

→ Level 1 – Basic (upper range)

***

## Interpretation

### Strengths

* Emerging training programs and internal expertise
* Early clinical adoption in selected departments
* Growing awareness of SNOMED CT benefits

### Weaknesses

* Limited and inconsistent adoption across the organization
* Lack of formal governance and strategy
* Weak interoperability and standards alignment
* Minimal use of SNOMED CT for analytics or decision support

***

## Priority Actions

To progress to Level 2–3, the organization should:

### 1. Establish Governance

* Define roles and responsibilities
* Develop an implementation roadmap
* Align with organizational strategy

### 2. Expand Adoption

* Roll out SNOMED CT across more departments
* Standardize usage across systems

### 3. Improve Workflow Integration

* Embed SNOMED CT in clinical documentation and processes
* Reduce reliance on free text

### 4. Strengthen Interoperability

* Align with standards (e.g., FHIR)
* Improve data exchange with partners

### 5. Build Analytics Capability

* Use SNOMED CT for reporting and quality improvement
* Introduce basic dashboards and insights

***

<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=Example%3A%20User%20Organization" 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 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/snomed-ct-implementation-maturity-assessment/maturity-assessment-for-user-organizations/example-user-organization.md?ask=<question>&goal=<user_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.