FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example OperationDefinition/Measure-care-gaps (Narrative)

Clinical Quality Information Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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 care-gaps operation as an OperationDefinition on Measure. See the Operation documentation

URL: [base]/Measure/$care-gaps

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INperiodStart1..1date

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 s

INperiodEnd1..1date

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

INtopic1..1string

The topic to be used to determine which measures are considered for the care gaps report. Any measure with the given topic will be included in the report

INsubject1..1string
(reference)

Subject for which the care gaps report will be produced

OUTreturn1..1Bundle

The result of the care gaps report will be returned as a document bundle with a MeasureReport entry for each included measure

The effect of invoking this operation is to calculate a set of measures for a particular topic (e.g. Preventive Care and Screening) and return a document describing the results of each measure for the given subject. Note that it is up to the server to determine whether or not the generated care gaps report is persisted. If the server does not persist the results, the operation does not affect state and can be invoked with a GET

 

 

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.