Other FHIR Resource Proposal

Other

Owning committee name

FHIR Core Team

Contributing or Reviewing Work Groups

• None

FHIR Resource Development Project Insight ID

Pending

Scope of coverage

This is not a typical resource in that it doesn't have a bounded set of semantics.

The Other resource is intended to cover all use-cases not met by HL7-defined resources. This includes resources that HL7 intends to create as well as those that are outside the scope of what HL7 will define. The scope of this resource will evolve as additional resources are defined.

This resource provides a mechanism for implementers to implement "custom" resources while still falling within the bounds of FHIR conformance, avoiding issues with collisions and ensuring that the meaning of elements within the resource remains discoverable.

The time-frame for migration from the Other resource to official HL7-defined resources is up to implementers.

RIM scope

InfrastructureRoot

Resource appropriateness

The primary purpose of this resource is to provide a safety valve for implementers where they have requirements not met by the existing FHIR specification. Extensibility is a key part of the FHIR methodology, including at the resource level. The is resource is different from others in that it isn't linked to a single concept. Instead, the concept represented by the resource is defined by an HL7-specific terminology (extensible for local use).

Expected implementations

The need for additional as-yet undefined resources is well recognized. Existing implementers are already encountering it.

Content sources

The initial vocabulary for Other resource types will be taken from the set of candidate resources identified on the wiki

Example Scenarios

The set of examples will need to be updated over time as new resources are defined.

• Referral
• UML diagram

Resource Relationships

• Link to Patient (as subject) and Practitioner (as author)
• Can link to any other resources via extensions

Timelines

Included in initial DSTU

gForge Users

N/A