Class: Service_list

Description of: Service_list

Class steward is Patient Care
A service list is owned by one and only one Stakeholder, which may be an individual, or organization (e.g., care team.) A Stakeholder can have multiple service lists. Each service list has a subject, i.e., a material (e.g. today’s schedule for operating room 12a,) or a patient (patient’s problem list) or another person. If the service list has no subject but just an owner, the owner is considered the subject. Thus, any stakeholder can maintain personal to-do lists, diaries, logbooks, etc.

Attribute definitions for: Service_list

desc :: ED

A description of this list. This may be considerable amount of text that explains what the list is for and how it is used. This is especially relevant if the owner is an organization or work group.

id :: SET<II>

Identifiers for the service list.

name :: ST

A short name that the owner of the list chooses to find this list among others. The name must be unique among all the lists that the stakeholder owns.

type_cd :: CV

Code identifying the kind of service list. Refer to the following Table for defined list types.

Concept Implies Code Definition schedule SCH A work-list, a schedule, or a personal to-do list of items intended to be done. logbook LOG A diary of past services. issues ISS A collections of any kinds of services as issues that need to be resolved. problem list issues PRB A patient’s problem list as seen by a particular provider.

Association definitions for: Service_list

owned_by (1,1) :: Stakeholder :: owns (0,n)

has_parts (0,n) :: Service_list_item :: is_part_of (1,1)

is_about (0,1) :: Material :: is_subject_of (0,n)

is_about (0,1) :: Person :: is_subject_of (0,n)