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 a Product Strategist at Orion Health, Chair emeritus of HL7 New Zealand and 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

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: