Renaming the FHIR Conformance resource

 

Just a short note to let people know of a significant change that has occurred in FHIR since the Baltimore Working Group meeting in September.

Perhaps surprisingly, there’s only one actual requirement of a RESTful FHIR server – that it hosts a resource that describes what its capabilities are. It returns this resource when you call the metadata endpoint of the server like this:

http://fhir3.healthintersections.com.au/open/metadata

Previously called the conformance resource, it describes the version of FHIR that it supports, the RESTful endpoints, profiles, messaging endpoints and a host of other stuff.

However, the word ‘conformance’ has come to mean a lot more as FHIR has evolved, so its name has been changed to ‘CapabilityStatement’ to reflect that.

It has the same structure (or pretty much so I think) and serves the same purpose – it’s just a rename.

Currently only Grahames server has this change (so the link above will return it) but you can expect the other STU-3 servers to support this soon.

You have been warned!

 

 

About David Hay
I'm an independent contractor working with companies like Orion Health, 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.

One Response to Renaming the FHIR Conformance resource

  1. Pingback: Setting up your own FHIR server for profiling | Hay on FHIR

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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: