FHIR Release 3 (STU) CI-Build

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Operation-measure-data-requirements

Example OperationDefinition/Measure-data-requirements (Narrative)

Maturity Level : N/A
Responsible Owner: Clinical Quality Information Work Group Ballot Standards Status : Informative Compartments : Not linked to any No defined compartments

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

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

Data Requirements

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

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

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

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN periodStart 1..1 0..1 date

The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive

IN periodEnd 1..1 0..1 date

The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive

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 measure

The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the measure. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the libraries referenced by the measures. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements) requirements). This operation defines what resources are subsequently referenced in the evaluatedResources element of the MeasureReport when submitting measure data

 

 

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.