Operation-plandefinition-data-requirements

R5 Final QA

This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Example OperationDefinition/PlanDefinition-data-requirements (Narrative)

Clinical Decision Support Work Group

Maturity Level: N/A

Standards Status: Informative

Compartments: Not linked to any defined compartments

This is the narrative for the resource. See also the XML, JSON or Turtle format.

Note that this is the formal definition for the data-requirements operation as an OperationDefinition on PlanDefinition. See the Operation documentation

URL: [base]/PlanDefinition/[id]/$data-requirements

Parameters

Use

Name

Scope

Cardinality

Type

Binding

Documentation

OUT

return

1..1

Library

The result of the requirements gathering is a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the plan definition

The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the plan definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the plan definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.