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.

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

KPA Score = 25

KPA Score = 50

KPA Score = 25

KPA Score = 25

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

→ Level 1 – Basic (upper range)

• Emerging training programs and internal expertise

• Early clinical adoption in selected departments

• Growing awareness of SNOMED CT benefits

• 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

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

• Define roles and responsibilities

• Develop an implementation roadmap

• Align with organizational strategy

• Roll out SNOMED CT across more departments

• Standardize usage across systems

• Embed SNOMED CT in clinical documentation and processes

• Reduce reliance on free text

• Align with standards (e.g., FHIR)

• Improve data exchange with partners

• Use SNOMED CT for reporting and quality improvement

• Introduce basic dashboards and insights