This table controls values for structural elements of the HL7 Reference Information Model. Therefore, it is part of the Normative Ballot for the RIM.This table controls values for structural elements of the HL7 Reference Information Model. Therefore, it is part of the Normative Ballot for the RIM.
These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.
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.
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.
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.
A planned Act for a specific time and place.
A request for the booking of an appointment.
An order for a service is an intent directed from a placer (intent author) to a filler (service performer). -- Historical note: in previous RIM versions, the order mood was captured as a separate class hierarchy, called Patient_service_order, and later Service_intent_or_order.
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.
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.
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.
Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.
A criterion or condition over service events that must apply for an associated service to be considered.
Expectation to make a specific observation with a desired value at a predefined future time
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).
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.
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.
Expectation to make a specific observation with a desired value at a predefined future time
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.
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.
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.
An order for a service is an intent directed from a placer (intent author) to a filler (service performer). -- Historical note: in previous RIM versions, the order mood was captured as a separate class hierarchy, called Patient_service_order, and later Service_intent_or_order.
A constraint domain for RMIM design.
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.
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.
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.
A planned Act for a specific time and place.
A request for the booking of an appointment.
An order for a service is an intent directed from a placer (intent author) to a filler (service performer). -- Historical note: in previous RIM versions, the order mood was captured as a separate class hierarchy, called Patient_service_order, and later Service_intent_or_order.
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.
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.
A grouping of Order, Promise. These specific moods are used in orders.
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.
An order for a service is an intent directed from a placer (intent author) to a filler (service performer). -- Historical note: in previous RIM versions, the order mood was captured as a separate class hierarchy, called Patient_service_order, and later Service_intent_or_order.
A grouping of Order, Promise and Event moods.
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.
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.
An order for a service is an intent directed from a placer (intent author) to a filler (service performer). -- Historical note: in previous RIM versions, the order mood was captured as a separate class hierarchy, called Patient_service_order, and later Service_intent_or_order.