Note: you are viewing the development version of See How we work for more details.

Welcome to


The FHIR® – Fast Healthcare Interoperability Resources are built from a set of modular components called "Resources". The definitions used in the various FHIR resources could potentially be viewed as a set of loose "semantics" that could be used as markup for HTML, XML or JSON documents.

While we aren't certain whether the FHIR resource constructs make sense in the context of the ecosystem, we thought that the easiest way to answer this question might be to propose a way of representing FHIR in the environment and use it to demonstrate some sample use cases.

To accomplish this, we have created two extensions:
  1. The FHIR W5 "ontology" - this provides a upper level classification of FHIR resources, as well as providing a basic list of "who, what, when, where and why" predicates.
  2. The FHIR resource definitions themselves - this is the set of resources and their attributes as defined in the FHIR core.
It would also be possible (and even sensible) to extend this core ontology with appropriate FHIR Profiles.

Relationship to other schemas

At the moment, there is almost no overlap between the FHIR schema elements and the components of the core schema. The root node of the W5 ontology (w5) is currently a direct subclass of THING. All other classes in the W5 and FHIR schemas subclass W5 descendants. The FHIR Resource inheritence structure is also preserved.

Assuming that the FHIR resource can be proven to be potentially useful, an obvious next step would be to examine how the elements within it relate to:

Next steps

Tools, Links, etc.