SQL Practical Guide

Search

SNOMED CT Document Library

    Loading...

Page tree

Versions Compared

Old Version 1

changes.mady.by.user David Markwell

Saved on

compared with

New Version Current

changes.mady.by.user Kai Kewley

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This practical guide outlines key requirements for enabling effective access to

Gloss
tSNOMED CT
 and   and illustrates some of the options for meeting these requirements using a freely available
Gloss
tSQL
 database. The rationale for using SQL as an illustrative example is that this is a widely understood way to access structured data that can be readily applied to SNOMED CT release files.

...

Note

SNOMED International also provides a range of tools that enable access to SNOMED CT content. These include a SNOMED CT Browser through through which to explore the terminology, a FHIR Terminology Server and a range of other open source tools that enable programmatic access to terminology content. For further details see see SNOMED International Tools or visit the SNOMED International GitHub repository to access open source projects supporting a range of terminology service requirements.

...

The primary purpose of this document is to enhance understanding of the logical design and release file structure of SNOMED CT and to provide practical ways to delivery services that utilize access the key features of the terminology SNOMED CT in a widely understood programming language. For more scalable and performant approaches to implementing SNOMED CT please visit SNOMED International's Github repository - e.g. https://github.com/IHTSDO.

For more details on the purpose of the document see Section 2. Objectives, Audiences and Uses.

Warning
titleLimitations
  1. The programming code that this guide contains and/or refers to is only made available to provide illustrative examples of key points related to the design, accessibility and use of SNOMED CT.
  2. It is licensed under the Apache 2 licence and is not certified to be suitable for use in a production system.
  3. The code has been developed to work in an a freely available open source relational database (MySQL - https://www.mysql.com) to make it accessible to all SNOMED CT licensees without imposing additional costs.
    • The code may need modification to work in other database environments.
    • Other database environments may also support additional features which enable alternative approaches not described in this guide.
  4. The use of SQL in this example is intended to enhance understanding of the structure and does not imply that SQL is recommended for use production systems that deliver terminology services.

...