Welcome to fhir.schema.org
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 schema.org ecosystem, we thought that the easiest way to answer this question might be to propose a way of representing FHIR in the schema.org environment and use it to demonstrate some sample use cases.
To accomplish this, we have created two schema.org extensions:
- 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.
- The FHIR resource definitions themselves - this is the set of resources and their attributes as defined in the FHIR core.
Relationship to other schema.org schemasAt the moment, there is almost no overlap between the FHIR schema elements and the components of the core schema.org 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.
- The proposed Health and medical types
- The BioDatabases proposal (assuming we can find where it ended up in the schema.org space)
- Schema.org root classes themselves
- Determine whether the W5 model has been correctly represented. In particular, we need to determine whether the "w"'s (e.g. where, who.actor , etc.) should be Classes or Properties and, if they are properties, what the appropriate domain(s) and range(s) are.
- Determine whether the FHIR model should be grounded in the schema.org datatypes or whether some or all of the FHIR "datatypes" (quotes because the FHIR definition of "datatype" is quite different than that used in data modeling) should be added to this list.
- Determine the appropriate level of granularity in the FHIR resources -- how much detail is required