SNOMED Documentation Search
The best way to organize an NRC depends on a wide range of factors, including the number of potential Affiliates, the vision and strategy for use of SNOMED CT in the country, the national eHealth infrastructure, the extent of customization, etc. But Members of SNOMED International are, at a minimum, required to fulfill a set of core responsibilities within the Member's territory, as shown in Figure 2 and specified in the Articles of Association. Typically, the NRC fulfills most of these obligations, however a Member may make other arrangements to fulfill some of the obligations.
The Articles of Association for SNOMED International can be found here: http://snomed.org/articles.
Figure 2 Obligations of Members.
Besides these areas, there is a range of other responsibilities that NRC may decide to undertake. The table below lists a set of possible responsibility areas. The list is not exhaustive but includes the main areas that NRCs currently cover. Some of the areas are marked as "Required," as these are part of the core responsibility areas.
Table 1. NRC Responsibility areas
Responsibility area |
Required |
Optional |
---|---|---|
Manage licenses (manually or automatically) |
|
|
Distribute International Releases |
|
|
Manage Extensions |
|
|
Manage Reference sets |
|
|
Manage Mappings |
|
|
Manage Translations |
|
|
Offer Tooling
|
||
|
|
|
|
|
|
Manage change requests for organizations in the country |
|
|
Offer education, promotion and training |
|
|
Engage stakeholders |
|
|
Offer implementation consultancy |
|
|
The competencies required for an NRC are dependent on what services the NRC chooses to deliver. However, most NRC staff should have a general understanding of SNOMED CT and SNOMED International.
If an NRC is unable to provide a specific type of service, it should seek to identify other resources that are able to meet the requirements of implementers and users in the Member country.
The following core competencies are typical for the work of an NRC. Some of these competency areas can be considered assignment-specific, as they will not be required as a constant competency within the NRC but are required to fulfill specific assignments, such as translation, mapping and development of Reference sets.
General competencies required
|
Terminology |
---|---|
Technical and IT skills |
|
Communication |
|
Implementation |
|
Education |
|
Assignment-specific competencies
|
Clinical and scientific domain specialty knowledge |
Linguistics and translation |
Specific competencies required to undertake particular NRC related tasks are outlined in Table 2.
Table 2 Competencies and skills required to undertake particular NRC tasks1
Tasks |
Main competencies |
Knowledge/Skills areas |
---|---|---|
Distribute International Release and National Extension |
|
|
Manage extensions | ||
|
|
|
|
|
|
Manage Reference sets | ||
|
|
|
|
|
|
Manage Mappings | ||
|
|
|
|
|
|
Tooling Developments
|
|
|
Manage translations |
|
|
Change requests |
|
|
|
|
|
Education, promotion and training |
|
|
Implementation consultancy |
|
|
Manage licenses (manually or automatically) |
|
|
Ref |
Notes |
---|---|
1 | Note that the range of tasks that different NRCs undertake may vary. |