Snow Owl Docs
9.x
9.x
  • Introduction
  • Quick Start
    • Create your first Resource
    • Import SNOMED CT
    • Find concepts by ID or term
    • Find concepts using ECL
    • Next steps
  • Setup and Administration
    • Plan your deployment
      • Technology stack
      • Hardware requirements
      • Software requirements
    • Configuration
      • Release package
      • Folder structure
      • Get SSL certificate (optional)
      • Preload dataset (optional)
      • Configure Elastic Cloud (optional)
      • System settings
      • Spin up the service
    • Upgrade Snow Owl
    • Backup and restore
      • Backup
      • Restore
    • User management
    • Advanced installation methods
      • Install Snow Owl
        • Using an archive
        • Using RPM
        • Using DEB
      • System configuration
        • Disable swapping
        • File descriptors
        • Virtual memory
        • Number of threads
      • Configure Snow Owl
      • Start Snow Owl
      • Stop Snow Owl
    • Advanced configuration
      • Setting JVM options
      • Logging configuration
      • Elasticsearch configuration
      • Security
        • File realm
        • LDAP realm
  • Terminology Standards
    • SNOMED CT
      • Extensions and Snow Owl
      • Scenarios
        • Single Edition
        • Single Extension Authoring
        • Multi Extension Authoring
      • Development
      • Releases
      • Upgrading
    • LOINC
    • Socialstyrelsen Standards
      • ICD-10-SE
      • ICF
      • KVÅ (KKÅ/KMÅ)
  • Content syndication
  • REST APIs
    • FHIR API
      • CodeSystem
      • ValueSet
      • ConceptMap
    • Native API
      • Resource management
      • Content access
      • Content management
      • SNOMED CT API
        • Branching
        • Compare
        • Concepts
        • Reference Sets
  • Release notes
Powered by GitBook
On this page
Export as PDF
  1. Terminology Standards

LOINC

(Pro feature)

As with every other resource in Snow Owl, a LOINC Code System needs to be created using the CodeSystems API first:

POST /codesystems
{
  "id": "LOINC",
  "url": "http://hl7.org/fhir/sid/loinc",
  "title": "LOINC",
  "language": "en",
  "description": "LOINC is a freely available international standard for tests, measurements, and observations",
  "status": "active",
  "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2023, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
  "owner": "ownerUserId",
  "contact": "https://loinc.org/",
  "oid": "2.16.840.1.113883.6.1",
  "toolingId": "loinc",
  "settings": {
      "publisher": "Regenstrief Institute, Inc.",
  }
}

Then, an official release file can be imported via the following request:

POST /loinc/LOINC/import -F "file=@Loinc_2.77.zip"

And last, create a new version to tag the content:

POST /versions
{
  "resource": "codesystems/LOINC",
  "version": "2.77",
  "description": "LOINC 2.77 2024-02-27 release",
  "effectiveTime": "2024-02-27"
}

Last updated 11 months ago