|
| Id |
2.16.840.1.113883.3.1937.99.61.26.11.58
ref (from repository: bccdapilot-) |
Effective Date |
valid from 2013‑09‑09 |
| Status |
 Final
|
Version Label |
|
| Name |
x_ActMoodOrderEvent |
Display Name |
x_ActMoodOrderEvent |
| Source Code System |
2.16.840.1.113883.5.1001 - Act Mood
|
| Level/ Type |
Code |
Display Name |
Code System |
Description |
| 0‑L |
EVN
|
event (occurrence)
|
Act Mood |
A service that actually happens, may be an ongoing service or a documentation of a
past service. Historical note: in previous RIM versions, the event mood was captured
as a separate class hierarchy, called Patient_service_event, and later Service_event.
|
| 0‑L |
PRMS
|
promise
|
Act Mood |
An intent to perform a service that has the strength of a commitment, i.e., other
parties may rely on the originator of such promise that said originator will see to
it that the promised act will be fulfilled. A promise can be either solicited or unsolicited.
|
| 0‑L |
RQO
|
request
|
Act Mood |
A request or order for a service is an intent directed from a placer (request author)
to a fulfiller (service performer).
Rationale: The concepts of a 'request' and an 'order' are viewed as different, because
there is an implication of a mandate associated with order. In practice, however,
this distinction has no general functional value in the inter-operation of health
care computing. 'Orders' are commonly refused for a variety of clinical and business
reasons, and the notion of a 'request' obligates the recipient (the fulfiller) to
respond to
the sender (the author). Indeed, in many regions, including Australia and Europe,
the common term used is 'request.'
Thus, the concept embodies both notions, as there is no useful distinction to be made.
If a mandate is to be associated with a request, this will be embodied in the 'local'
business rules applied to the transactions. Should HL7 desire to provide a distinction
between these in the future, the individual concepts could be added as specializations
of this concept.
The critical distinction here, is the difference between this concept and an 'intent',
of which it is a specialization. An intent involves decisions by a single party, the
author. A request, however, involves decisions by two parties, the author and the
fulfiller, with an obligation on the part of the fulfiller to respond to the request
indicating that the fulfiller will indeed fulfill the request.
|
|
| |
|
| Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear
in @nullFlavor attribute instead of @code.
|
|
|
|
Value Set x_ActMoodOrderEvent 2013‑09‑09
