Operation-library-data-requirements

Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - 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/Library-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 Library. See the Operation documentation

URL: [base]/$data-requirements

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

Parameters

Use

Name

Cardinality

Type

Binding

Documentation

IN

target

0..1

string

The target of the data requirements operation

OUT

return

1..1

Library

The result of the requirements gathering

The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for a given target resource. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the target resource 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.