Operation
Definition
for
Value
SetFHIRDeviceCategory
This operation is used to return all the information related to an encounter described
in the resource on which this operation is invoked. The response is a bundle of type "searchset
". At a minimum, the encounter resource itself is returned, along with any other resources
that the server has available for the given encounter for the user. The server also returns
whatever resources are needed to support the records - e.g. linked practitioners, locations,
organizations etc. The principle intended use for this operation is to provide a patient
with access to their record, or to allow a client to retrieve everything for an encounter
for efficient display).
are included in the encounter compartment for the identified encounter (have a reference
to the encounter)
are referenced by the standard extenstion for associating an encounter (where no reference
element exists) http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
the server believes are relevant to the context of the encounter for any other reason
(internally defined/decided)
any resource referenced by the above, including binaries and attachments (to make a more
complete package)
In the US Realm, at a mimimum, the resources returned SHALL include all the data covered
by the meaningful use common data elements (see
for further guidance). Other applicable implementation guides may make additional rules
about the information that is returned. Note that for many resources, the exact nature
of the link to encounter can be ambiguous (e.g. for a DiagnosticReport, is it the encounter
when it was initiated, or when it was reported?)
The key differences between this operation and simply searching the encounter compartment
are: * unless the client requests otherwise, the server returns the entire result set
in a single bundle (rather than using paging) * the server is responsible for determining
what resources to return as included resources (rather than the client specifying which
ones)
This operation is used to return all the information related to an encounter described
in the resource on which this operation is invoked. The response is a bundle of type "searchset
". At a minimum, the encounter resource itself is returned, along with any other resources
that the server has available for the given encounter for the user. The server also returns
whatever resources are needed to support the records - e.g. linked practitioners, locations,
organizations etc. The principle intended use for this operation is to provide a patient
with access to their record, or to allow a client to retrieve everything for an encounter
for efficient display).
The server SHOULD return all resources it has that:
* are included in the encounter compartment for the identified encounter (have a reference
to the encounter)
* are referenced by the standard extenstion for associating an encounter (where no reference
element exists) http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
* the server believes are relevant to the context of the encounter for any other reason
(internally defined/decided)
* any resource referenced by the above, including binaries and attachments (to make a
more complete package)
In the US Realm, at a mimimum, the resources returned SHALL include all the data covered
by the meaningful use common data elements (see [DAF](http://hl7.org/fhir/us/daf) for
further guidance). Other applicable implementation guides may make additional rules about
the information that is returned. Note that for many resources, the exact nature of
the link to encounter can be ambiguous (e.g. for a DiagnosticReport, is it the encounter
when it was initiated, or when it was reported?)
The key differences between this operation and simply searching the encounter compartment
are: * unless the client requests otherwise, the server returns the entire result set
in a single bundle (rather than using paging) * the server is responsible for determining
what resources to return as included resources (rather than the client specifying which
ones)
</
OperationDefinition
>
{
"resourceType" : "ValueSet",
"id" : "device-category",
"meta" : {
"lastUpdated" : "2022-09-10T04:52:37.223+10:00",
"profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"]
},
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><ul><li>Include all codes defined in <a href=\"codesystem-device-category.html\"><code>http://hl7.org/fhir/device-category</code></a></li></ul></div>"
},
"extension" : [{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "oo"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-state",
"valueCode" : "trial-use"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 1
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "draft"
}],
"url" : "http://hl7.org/fhir/ValueSet/device-category",
"identifier" : [{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.4.642.3.3307"
}],
"version" : "5.0.0-ballot",
"name" : "FHIRDeviceCategory",
"title" : "FHIRDeviceCategory",
"status" : "draft",
"experimental" : true,
"date" : "2020-12-28T16:55:11+11:00",
"publisher" : "HL7 (FHIR Project)",
"contact" : [{
"telecom" : [{
"system" : "url",
"value" : "http://hl7.org/fhir"
},
{
"system" : "email",
"value" : "fhir@lists.hl7.org"
}]
}],
"description" : "The association state of the device.",
"immutable" : true,
"compose" : {
"include" : [{
"system" : "http://hl7.org/fhir/device-category"
}]
}
}
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.
Terminology
|
Propose
a
change