All Pages require a summary for proper visual display. In this section detail the purpose of the page

Terminology Servers and Other Technical Resources

Below are a list of terminology server and other relevant technical resources, which is expected to grow over the next few weeks to make sure you have enough useful resources to hand at the Hackathon.


Patients First terminology server 

This terminology server is now available as a SNApp resource and can be found here - http://its.patientsfirst.org.nz/RestService.svc/Terminz

API documentation for the Patients First term server can be found here : http://www.slideshare.net/PeterJordan4/patients-first-terminology-services-a-brief-introduction-for-developers

HL7 FHIR Server

HL7 NZ chair and FHIR management group member David Hay blogging about SNApp: https://fhirblog.com/2016/09/29/supporting-the-snomed-snapp-hackathon/

The server can be found here - http://snapp.clinfhir.com:8080/baseDstu3 with a 'how to' here https://fhirblog.com/2016/10/02/snapp-server/

CSIRO Ontoserver

CSIRO's Ontoserver is now available at https://ontoserver.csiro.au/snapp

Australian Digital Health Agency's National Clinical Terminology Service (NCTS)

Please use the live NCTS site https://www.healthterminologies.gov.au to get access.

 


IHTSDO Resources

IHTSDO has a number of technical resources that you may find useful running up to the event:

SNOMED In 5 Minutes - some simple code examples from the community of working SNOMED CT

IHTSDO SNOMED CT Browser - made up of a couple of github repos, https://github.com/IHTSDO/sct-browser-frontend and https://github.com/IHTSDO/sct-snapshot-rest-api, and a live REST API, http://docs.snomedctsnapshotapi.apiary.io/

SNOMED Query Service - a simple server which loads SNOMED CT into memory and offers an API which also implements the SNOMED CT Expression Constraint Query Language

 

There's more in our github repositories, all available under an Apache v2 license.

And if you want to ask the development team any questions, sign up to IHTSDO's Slack and jump in to the SNApp channel.