Search PlanDefinitions

PlanDefinition on the FHIR specification website.

This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, and drug quality specifications.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

The plan definition publication date

string

External identifier for the plan definition

string

What resource is being referenced

string

A use context type and value assigned to the plan definition

string

Intended jurisdiction for the plan definition

string

What resource is being referenced

string

The description of the plan definition

string

A type of use context assigned to the plan definition

string

What resource is being referenced

string

What resource is being referenced

string

The human-friendly name of the plan definition

string

The type of artifact the plan (e.g. order-set, eca-rule, protocol)

string

The business version of the plan definition

string

The uri that identifies the plan definition

string

A quantity- or range-valued use context assigned to the plan definition

string

What resource is being referenced

string

The time during which the plan definition is intended to be in use

string

A use context assigned to the plan definition

string

Computationally friendly name of the plan definition

string

Name of the publisher of the plan definition

string

Topics associated with the module

string

Activity or plan definitions used by plan definition

string

A use context type and quantity- or range-based value assigned to the plan definition

string

The current status of the plan definition

Responses

401

Unauthorized

403

Forbidden

500

Internal server error

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json