Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Operation-library-data-requirements

Example OperationDefinition/Library-data-requirements (Narrative)

Maturity Level : N/A
Responsible Owner: Clinical Decision Support Work Group Standards Status : Informative Compartments : Not linked to any No 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

Data Requirements

OPERATION: Data Requirements Generated Narrative: OperationDefinition Library-data-requirements The official URL for this operation definition is:

http://hl7.org/fhir/OperationDefinition/Library-data-requirements The data-requirements operation aggregates and returns the parameters and data requirements for a resource and all its dependencies as a single module definition

URL: [base]/$data-requirements

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

Parameters

Use Name Scope 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.