Overview

Section 2 defines a set of URI spaces that are used to identify a variety of SNOMED CT resources, but it does not talk about discuss resolving these URIs. The URIs in the standard use the http scheme and the domain name snomed.info, which is owned by SNOMED International. This means that SNOMED International is in control of whether or not these URIs, when treated as URLs and resolved, will result in a document being available, a 404 ("Not Found") error, or something else.

URIs Resolved by SNOMED International

SNOMED International resolves URIs for concepts from the SNOMED CT International Edition (of the form http://snomed.info/id/{SCTID}) to the public SNOMED CT browser.

URIs for modelling resources (as described in 2.7 URIs for SNOMED Resources) will, by default, be resolved to a HTML representation of the identified entity. To support machine-readability, the HTTP Accept header will be used to perform content negotiation. For example, the value "application/fhir+json" may be supplied to request a FHIR representation in JSON syntax. Following FHIR conventions, a suffix of "?_format=json" will be interpreted as equivalent to providing an Accept header of "application/fhir+json" with maximum priority. This is to facilitate access via web browsers where access to HTTP headers is not normally available.

URIs Resolved by Others

A However, a Release Centre or other service provider providers may also want to support the resolution of these URIsother URIs (e.g. those that identify resources that they maintain). A general approach to this involves deploying a resolving service with an endpoint URL such as

...

which is configured to resolve URLs that embed SNOMED CT URIs. Continuing the example, a URL of the following form

• (1) http://myservice.example.com/?urluri=http://snomed.info/{...}

might be redirected with an HTTP response code of 303 to

• (2) http://myservice.example.com/snomed/{...}

...

• http://myservice.example.com/?urluri=http://snomed.info/id/900000000000498005

...