FHIR Application Feature Framework Implementation Guide
1.0.0-ballot - STU1 Ballot International flag

This page is part of the FHIR Application Feature Framework Implementation Guide (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

Home

Official URL: http://hl7.org/fhir/uv/application-feature/ImplementationGuide/hl7.fhir.uv.application-feature Version: 1.0.0-ballot
IG Standards status: Trial-use Maturity Level: 1 Computable Name: ApplicationFeatureFramework

Overview

CapabilityStatement is the largest/most complex of the infrastructure resources, yet there continues to be pressure to add yet more capabilities to describe additional nuances of how systems behave (or are desired to behave).

As well, the things people want to say about systems often covers concepts that are outside FHIR proper (e.g. CDS Hooks, SMART) or even outside HL7.

In the lead-up to R5 we created a draft update to the CapabilityStatement resource called CapabilityStatement2 that proposed a terminology-based approach to managing new assertions around system capabilities. However, there was not sufficient bandwidth to get implementation testing to happen prior to R5 publication. Also, during testing we realized that the focus was really on application features vs. the CapabilityStatement resource. Thus we decided to create this IG defining an Application Feature Framework.

The key details of this IG are in the following locations:

  • Specification: Contains the formal specification of the application feature framework such as defining features, querying for features, and feature negotiation.
  • Artifact Index: The implementable artifacts defined in this IG such as profiles, value sets, code systems, and operation definitions.

Credits

  • Rick Geimer, Lantana Consulting Group
  • Grahame Grieve, Health Intersections
  • Gino Canessa, Microsoft