public class ActMood extends Object
Modifier and Type | Field and Description |
---|---|
static Set<CS> |
ALL_VALUES
All values defined by this class.
|
static CS |
APT
A planned
Act for a specific time and
place. |
static CS |
ARQ
A request for the booking of an appointment.
|
static CS |
DEF
A definition of a service (master).
|
static CS |
EVN
A service that actually happens, may be an ongoing service or a
documentation of a past service.
|
static CS |
EVN_CRT
A criterion or condition over service events that must apply for an
associated service to be considered.
|
static CS |
EXPEC
An act that is considered likely to occur in the future.
|
static CS |
GOL
Expectation to make a specific observation with a desired value at a
predefined future time
|
static CS |
INT
An intention or plan to perform a service.
|
static CS |
OPT
An option is an alternative set of property-value bindings.
|
static CS |
PERM
A kind of service which is authorized to be performed.
|
static CS |
PERMRQ
A request for authorization to perform a kind of service.
|
static CS |
PRMS
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.
|
static CS |
PRP
A non-mandated intent to perform an act.
|
static CS |
RMD
A non-mandated intent to perform an act where a level of professional
responsibility is being accepted by making the proposal.
|
static CS |
RQO
A request or order for a service is an intent directed from a placer
(request author) to a fulfiller (service performer).
|
static CS |
RSK
An act that may occur in the future and which is regarded as undesirable.
|
static CS |
SLOT
Periods of time on a schedule for a resource.
|
Constructor and Description |
---|
ActMood() |
public static CS EVN_CRT
A criterion or condition over service events that must apply for an associated service to be considered.
public static CS DEF
A definition of a service (master).
Historical note: in previous RIM versions, the definition mood was captured as a separate class hierarchy, called Master_service.
public static CS GOL
Expectation to make a specific observation with a desired value at a predefined future time
public static CS INT
An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order.
public static CS ARQ
A request for the booking of an appointment.
public static CS PRMS
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.
public static CS SLOT
Periods of time on a schedule for a resource. Appointments occupy sets of one or more booked slots. A slot that is open for appointments is considered available and a slot that is held back for administrative purposes is considered blocked. A Resource slot that is "tentatively" booked is referred to as reserved.
public static CS OPT
An option is an alternative set of property-value bindings. Options specify alternative sets of values, typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together.
Historical note: in HL7 v2.x option existed in the special case for alternative medication routes (RXR segment).
public static CS PRP
A non-mandated intent to perform an act. Used to record intents that are explicitly not Orders. Professional responsibility for the 'proposal' may or may not be present.
public static CS EVN
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.
public static CS RQO
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 healthcare 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). In many regions, including Australia and Europe, the common term used is request.
Therefore, 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.
public static CS EXPEC
An act that is considered likely to occur in the future. The essential feature of an act expressed in expectation mood is that it is likely to occur. An expectation may be desirable, undesirable or neutral in effect.
public static CS PERM
A kind of service which is authorized to be performed.
public static CS PERMRQ
A request for authorization to perform a kind of service. This is distinct from RQO which is a request for an actual act. PERMRQ is merely a request for permission to perform an act.
public static CS RMD
A non-mandated intent to perform an act where a level of professional responsibility is being accepted by making the proposal.
public static CS RSK
An act that may occur in the future and which is regarded as undesirable. The essential feature of a risk is that if it occurs this would be regarded as a marker of a negative outcome or of deterioration towards a negative outcome. Recording a risk indicates that it is seen as more likely to occur in the subject than in a general member of the population but does not mean it is expected to occur.
HDR Glossary HDR Concept Lists HDR Exceptions HDR Programmer's Guide HDR Implementation Guide HDR Profile Options
Copyright © 2016, 2018, Oracle. All rights reserved