SNapp server

Just a short note to say that I’ve set up a FHIR server for the SNapp event – based on the HAPI CLI server.

The IP address of the server root is:

For example¬†to get the conformance resource you’d enter:

So the recommended layout for SNapp is:

  • Data Server: SNapp (STU3)
  • Conformance Server: Public HAPI (STU3)
  • Terminology Server: Grahames Server (STU3)

Which quite nicely shows how the different server ‘roles’ could work in a real environment. I’ve created a ‘project’ to select them for you:


Just a note that if you’ve already used clinFHIR then you’ll need to reset the config to see the SNapp server in the list as the screen shot below shows (and restart the app after you’ve done that – just to be tidy).


Oh – and also worth noting that if you want to see the URL of your currently selected Patient & Conformance server, just mouse over the label in the nav-bar – like so:




About David Hay
I'm an independent contractor working with organizations like Lyniate, CSIRO in Australia and the New Zealand Ministry Of Health. I'm an HL7 Fellow, Chair Emeritus of HL7 New Zealand and a co-chair of the FHIR Management Group. I have a keen interest in health IT, especially health interoperability with HL7 and the new FHIR standard.

2 Responses to SNapp server

  1. Pingback: Confluence: SNApp

Leave a Reply

%d bloggers like this: