This
page
is
part
of
the
FHIR
Specification
(v5.0.0:
R5
-
STU
v6.0.0-ballot2:
Release
6
Ballot
(2nd
Draft)
(see
Ballot
Notes
).
This
is
the
The
current
published
version
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
| Clinical Quality Information Work Group | Maturity Level : N/A | Standards Status : Informative | Compartments : 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 submit-data operation as an OperationDefinition on Measure. See the Operation documentation
Generated Narrative: OperationDefinition Measure-submit-data
URL: [base]/Measure/$submit-data
URL: [base]/Measure/[id]/$submit-data
Parameters
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | measureReport | 1..1 | MeasureReport |
The measure report being submitted |
||
| IN | resource | 0..* | Resource |
The individual resources that make up the data-of-interest being submitted |
The effect of invoking this operation is that the submitted data is posted to the receiving system and can be used for subsequent calculation of the relevant quality measure. The data-of-interest for a measure can be determined by examining the measure definition, or by invoking the $data-requirements operation
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.