WO2003021509A2 - A system and user interface for processing task schedule information priority - Google Patents

A system and user interface for processing task schedule information priority Download PDF

Info

Publication number
WO2003021509A2
WO2003021509A2 PCT/US2002/020650 US0220650W WO03021509A2 WO 2003021509 A2 WO2003021509 A2 WO 2003021509A2 US 0220650 W US0220650 W US 0220650W WO 03021509 A2 WO03021509 A2 WO 03021509A2
Authority
WO
WIPO (PCT)
Prior art keywords
worker
role
work
task
tasks
Prior art date
Application number
PCT/US2002/020650
Other languages
French (fr)
Other versions
WO2003021509A3 (en
Inventor
Samuel I. Brandt
Jan Dehaan
Original Assignee
Siemens Medical Solutions Health Services Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens Medical Solutions Health Services Corporation filed Critical Siemens Medical Solutions Health Services Corporation
Priority to JP2003525775A priority Critical patent/JP2005502137A/en
Priority to EP02744744A priority patent/EP1421528A2/en
Priority to CA002457962A priority patent/CA2457962A1/en
Publication of WO2003021509A2 publication Critical patent/WO2003021509A2/en
Publication of WO2003021509A3 publication Critical patent/WO2003021509A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Definitions

  • the present invention relates to project management systems in general. More specifically, the present invention relates to mechanisms for reconciling complex and overlapping responsibilities for complex tasks such as those found in a healthcare environment with task allocation models that may be supported by workflow engines. However, the present invention is equally applicable in other industries where complex task allocation is required. BACKGROUND OF THE INVENTION
  • Prior art workflow engines permit manipulation of workflow processes, including defining individual work steps to be allocated to systems, individuals, groups of individuals or systems, or combinations thereof.
  • a desired task description is typically placed into a destination work list, e.g. a set of tasks to be accomplished, at least in part, by or for that system, individual, or group.
  • Destination work lists may be defined at the time that the workflow process definition is created.
  • Work steps are typically placed into a specific destination work list in response to an event such as the completion of a previous work step or the reception of a system message, rather than when an individual or system is ready to carry out the task associated with that work step.
  • a task such as "dispense medication” may be defined within a workflow process named "medication administration.”
  • medication administration a workflow process
  • several degrees of uncertainty may exist including specifics regarding medication, a patient to whom the medication will be administered, a time when the administration is due, and the person who will be responsible at that time for administering the medication.
  • a single process definition should be applicable to all instances of the process, e.g. a drug administration definition should be applicable to the administration of Drug A by nurse Jones on 4 West to patient Smith as well as the administration of Drug B by nurse Galloway to patient McCall on 3 South.
  • nurse Galloway may be on a team with two other nurses. While each nurse on the team may have primary responsibility for a select group of patients, the other two may have secondary responsibility to perform service tasks for those patients if the first nurse, e.g. Galloway, is not available. Therefore, all three nurses may need to see overlapping work items on their own work lists, although these items may need to be presented differently depending on whether the nurse has primary or secondary responsibility. Additionally, a head floor nurse, prior to assigning a new admission, may need to see all of her subordinate nurses' pending tasks.
  • Prior art workflow engines require an explicit association of work steps and work lists at the time a process is designed. Further, each prior art work step is typically delegated to its associated work list when a system event occurs, not when an individual or system is ready to carry out the service task associated with that work step. This mechanism is inadequate for complex industries such as healthcare.
  • all medication administration work steps could be assigned to a group of nurses who may use a descriptor such as "floor nurse.” If a separate group were assigned for each nursing floor, then a separate workflow process would have to be defined for medication administration for each nursing unit. Even then, all of the nurses on each nursing floor would be exposed to all of the patients' service tasks, and there would be no mechanism to explicitly assign service tasks to an appropriate, responsible nurse. Instead each nurse would have to search through the entire ward's nursing tasks to find her own.
  • the present invention comprises a method for providing a displayable schedule of service tasks to be performed by a particular worker of a plurality of workers, e.g. tasks to be undertaken for or on behalf of specific individuals or objects such as products, equipment, and/or supplies.
  • the method comprises receiving worker identification information; generating a compilation of service tasks to be performed by the identified worker based on a role or roles assigned to the worker and a list of individuals or objects associated with the worker; and initiating display of the compilation.
  • the method comprises defining roles; defining work step types; creating work steps to be accomplished by workers; mapping work steps to the work step types; mapping work step types to roles; receiving identification information about a worker; assigning at least one role to the worker; generating a record of service tasks to be performed by the worker in response to the received identification information based on the at least one role, the performable tasks' targeted service tasks, and the assigned relationship between the worker and those targeted service tasks; and initiating display of the compiled list of tasks.
  • Fig. 1 is a schematic of an exemplary system embodiment
  • Fig. 2 is a diagrammatic representation of an exemplary work list view and work lists
  • Fig. 3 is a representative relationship flow model of an exemplary of the present invention.
  • Fig. 4 is a flowchart of an exemplary embodiment the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • the present invention may be used to allocate tasks among one or more appropriate workers in a complicated work environment.
  • an item is described as implemented in software, it can equally well be implemented as hardware.
  • a "service task,” i.e. service task 12, comprises actions to be undertaken by or on the behalf of a worker, e.g. "4" in Fig. 1, or, in healthcare systems, a patient or both as well as items needed to satisfy a requirement for which worker 4 is responsible.
  • service task 12 may include items associated with patient care needs, including the patient himself or herself, by way of example including: a physician order and its associated data; administration of laboratory tests and data associated with the laboratory tests; data associated with patient billing; therapy plans and actual therapy; medication administration and the medication, e.g. pills, shots, or bandaging; and the like; and combinations thereof.
  • a healthcare clinical information system is used as an exemplary system for illustration purposes, the present invention is applicable to systems involving processing of sequential tasks including in vertical markets in which a workflow engine is embedded within an OEM computer system.
  • record is used herein to signify information or data material to a particular subject where the information or data are preserved in non-volatile, permanent, or tangible form such as in a computer file, disk, CDROM, DVD, or other electronic storage, or the like, or combinations thereof, that are accessible by a computer or other electronic or data processing system.
  • Fig. 1 a schematic overview of a workflow system embodiment of the present invention
  • the present invention provides a solution for embedding workflow engine technology within a comprehensive vertical software system in an OEM fashion.
  • prior art workflow systems have ways to access work list items, additional useful ways may be desired to access work list items. For example, it may be desirable to access all of the individual work steps relating to a specific patient, constituting that patient's activity plan; all of the medication administration work steps for a specific patient, constituting that patient's medication administration record; and/or all of the medication administration work steps for all of a specific nurse's assigned patients, representing that nurse's medication administration task list.
  • a system for creating work flows comprises first computer 10 useful in designing and modifying a desired workflow process; second computer 20 where second computer 20 is operatively in communication with first computer 10; and third computer 30 where first computer 10 is operatively in communication with third computer 30.
  • Third computer 30 may act as a server and comprise a workflow engine (not shown in the figures) and database 32.
  • User 2 if user 2 has the authority to design and modify a workflow process, may use first computer 10 to access third computer 30 to create, modify, and manipulate workflow process definitions 22 and work list views 40 (Fig.
  • first computer 10 and second computer 20 comprise input devices (not specifically shown in the figures) such as for entering data, e.g. identification of worker 4, and output devices such as for displaying work lists 22.
  • the input device may include a keyboard, a mouse, a biometric device, a card or badge reader, or the like, or combinations thereof.
  • the output device may include a display screen, a printer, a pager, a cell phone, a facsimile machine, or the like, a combination thereof.
  • Computer 10 is useful to allow user 2 with appropriate rights to design and modify a workflow.
  • Computer 10 communicates with a workflow engine (not shown in the figures) executing in a computer such as third computer 30 having access to a database such as 32.
  • a worker role 26 may be represented in the system by a generic code for a "virtual" role 27 (Fig. 3), i.e. a placeholder to be satisfied in real-time by a code representing a specific worker 4.
  • a "role" 26, 27 may comprise a task, office, or job description for which a workflow administrator may wish to assign a work item, for example in a healthcare environment comprising nursing roles, administrative roles, physician roles, physician assistant roles, therapist roles, technician roles, and the like, or combinations thereof.
  • work list view 40 may be defined by a relationship between one or more tables in one or more databases that can be manipulated programmatically.
  • Work lists 22 and work list views 40 may be associated with work flows, such as for institution 90, that relate workers 4 to service tasks 12 and that may be the end result of work-related assignments for institution 90, e.g. patient requirements such as medication to be taken, meals to be provided, drugs to be administered, or therapy to be administered, or the like, or combinations thereof.
  • workers 4 may access the features of the present invention through an interface associated with the vertical system. Accordingly, worker 4 may log into a system such as at computer 20 to access vertical system software and, once logged into that vertical system software, view a compiled record comprising work lists 22 associated with worker 4 on a display device, e.g. a display screen, a printer, pager, cell phone, or the like, or a combination thereof. It is understood that computer 10, computer 20 and third computer 30 need not be separate computers but may be a single computer or computer system.
  • work list 22 may be created by examining worker data objects 24b related to worker 4.
  • properties of worker data object 24b may include a user role property, e.g. userRolelD, which contains a value representing an actual user role 26 (Fig. 3) or a virtual role 27 (Fig. 3) that the specific worker 4 can satisfy.
  • Worker data objects 24b may be queried using a unique user role 26 identifier for worker 4 as well as one or more virtual roles 27 that worker 4 may satisfy. For example, worker 4 may satisfy a virtual role 27 for a medication giver as well as a virtual role 27 for a physical therapist but not a virtual role 27 for a medication prescriber.
  • Work item types may have additional descriptions such as at work step data object 24d. These descriptions and other properties may be related to virtual role object 24c such as by a work item type identifier.
  • a patient may be dynamically associated with worker 4 in real-time, such as shown at patient data object 24a.
  • patient data object 24a may relate an actual patient with a specific worker 4.
  • Patients may additionally have needs or requirements directly or indirectly associated with those patients which one or more workers 4 need to address as part of a work assignment for worker 4.
  • One or more service tasks 12 will be retrievable based on worker data object 24b that is related into role data object 24c such as by the identifier of worker 4.
  • Work list 22 may then be created based using the patient data and data for worker 4.
  • Each work list 22 may further comprise a task identifier as well as an identifier of the responsible worker 4 (Fig. 1 ) to be assigned the service task.
  • the identifier for worker 4 may be a generic code at creation, e.g. one for a virtual role 27, and filled in with a code representing a specific worker 4 at runtime.
  • Work lists 22 may therefore comprise work item types such as specific work tasks to be mapped to a general user characteristics.
  • specific workers 4 (Fig. 1) may be associated with one or more virtual roles 27 and then dynamically mapped into a virtual role 27 associated with work list 22 such as at runtime.
  • virtual role 27 may act as a "place holder" to be satisfied by a specific worker 4 at the time when the task is to be performed.
  • one or more characteristics of the task to be performed e.g. a patient identifier, may also be mapped dynamically to worker 4.
  • a virtual role 27 may be associated with a predetermined type of work step.
  • the actual work step e.g. a step to effect a specific service task 12
  • both workers 4 and work steps may be independently associated with patients such as on an individual and/or group basis. Using these associations, worker 4 may be assigned a subset of work steps based upon virtual role 27 and patient associations.
  • One or more work lists 22 may be accessed through one or more work list views 40.
  • Such work list views 40 may access a single data collection (such compiled records of work lists 22 contained in database 32 in Fig. 1 ) using numerous methods as will be familiar to those of ordinary skill in the database arts, e.g. SQL joins, filters, and the like.
  • a displayable task schedule concerning service tasks 2 to be performed by a particular worker 4 of a plurality of workers 4 is created by receiving identification information reflective of worker 4; compiling a record identifying service tasks 12 to be performed by worker 4 in response to the received identification information and based at least partially on at least one of a role 26 assigned to the worker 4, a service task 12 associated with the identified worker 4, and/or a predetermined relationship between the identified worker 4 and the intended a target beneficiary of the service task 12; and initiating display of the compiled record at a display device.
  • the displayable compiled record may be formatted for display as a schedule of service tasks 12 that may be performed by at least one worker 4 of a plurality of workers 4.
  • one or more worker roles 26 are defined by user 2 with appropriate authority to define worker roles 26.
  • User 2 with appropriate authority to define work step types also defines one or more work step types.
  • user 2 with appropriate authority to create a work step creates a work step to be accomplished by worker 4, and user 2 with appropriate authority to map work steps to work step types maps the work step to a work step type.
  • Each of these users 2 above may be the same user 2 or may be a plurality of users 2, each of whom has differing authority.
  • Work step types are mapped to worker roles 26,27. Accordingly, when worker 4 wish to use the present invention, worker 4 provides identification information about the worker 4 which is received into the system, whereupon user role 26 is assigned to worker 4 and a record comprising descriptions of service tasks 12 to be performed by worker 4 in response to the received identification information is compiled, based on the user role 26 assigned to worker 4. The record may then be formatted for display at a display device, e.g. computer 20.
  • a display device e.g. computer 20.
  • a new work step 50 (Fig. 3) is created 110
  • the new work step 50 is registered and assigned 120 a work item type (not shown in the figures) by the work step definition creator, e.g. user 2.
  • this is an explicit operation required for each new work step 50.
  • user 2 acting as a workflow designer may configure one or more work steps such as "dispense medication” within a process design such as at computer 10 (Fig. 1).
  • workflow designer creates workflow processes utilizing work steps 52 (Fig. 3) that have been pre-configured. If workflow designer user 2 identifies a new work step 52, the new work step 52 may be registered with an associated work step type 50. Further, as discussed herein below, when worker 4 signs on and requests work list 22, work list view 40 may be dynamically constructed which matches one or more worker roles 26,27 associated with worker 4 to appropriate work steps 52, e.g. for service tasks 12 (Fig. 1) associated with patient requirements. If the workflow engine needs to escalate a task to worker 4, it may examine the work task type and one or more work detail characteristics, e.g. an associated patient ID, and then query for roles 26, 27 associated with the task type. Once the query is answered, a system using an embodiment of the present invention identifies an individual worker 4 associated both with that role 26,27 and that work detail characteristic.
  • work detail characteristics e.g. an associated patient ID
  • Workflow engines may be associatable with work flows such as for a target process, e.g. one involving institution 90 (Fig. 1). Accordingly, users 2 may explicitly define roles 26,27 such as for institution 90 (Fig. 1) and then explicitly map work task types 50 onto these roles 26,27 either automatically or manually 130. In a preferred embodiment, an automated method of mapping is consistent with manual processes. For example, a new work task type 50 may be defined based upon an existing work task type 50, automatically inheriting the role relationships of the parent work task 50.
  • an institution 90 such as a hospital may implement a new service task 12 such as pulse oximetry.
  • hospital 90 decides which workers 4 will be needed to provide service task 12 when it is ordered, e.g. respiratory therapy, nursing, or both.
  • the doctor may be presented with a list of service tasks 12, e.g.
  • individual workers 4 may be dynamically mapped 140 into roles 26,27 such as by using relational database techniques or object queries.
  • each individual healthcare worker 4 may explicitly assume responsibility 150 for one or more individual service tasks 12 such as patient care responsibility (Fig. 1).
  • responsibilities may be implemented with a single service task 12 such as an item needed to satisfy a patient care requirement; with a group of service tasks 12 such as patient care responsibility for the group; or on an abstraction such as a nursing unit, department, or other level that can be resolved to a group of service tasks 12 such as patient care responsibility for all of the patients contained within the group.
  • Worker 4 e.g. a, doctor or a nurse, may then assume responsibility for a group of service tasks 12 such as at a shift change. Workers 4 may also assume responsibility for a plurality of groups of service tasks 12, e.g. a respiratory therapist may assume responsibility for groups of patient requirements on several floors in hospital 90. Moreover, an individual worker 4 may also assume responsibility such as in an oversight or team capacity. Using virtual roles 27, user roles 26, and other data such as data relating to work steps 50 and service tasks 12 such as patient requirements, the present invention may capture assignment of service tasks 12, create a mapping between patients and workers 4, and use the mapping to present appropriate work items to worker 4.
  • mapping may correspond to a nurse signing on to a system of the present invention, e.g. as a "floor nurse” on “4 West” or as an "ICU nurse” in a "surgical ICU” section.
  • the nurse may use a user interface appropriate for both the contextual setting and her role (not shown in the figures) to request 160 a work list 22.
  • the present invention is able to provide appropriate work lists 22 that show those tasks appropriate for that user's role.
  • the present invention may examine 170 the worker role 26 of worker 4 and then map worker 4 to work task types 50 associated with that worker role 26. Such an examination may further entail examining service tasks 12 currently assigned to worker 4 and creating a work list view 40 from master work list 23 (Fig. 3) to show only those tasks appropriate to the worker role 26 of that worker 4 that pertains to service tasks 12 for whom that worker 4 has responsibility.
  • the present invention may compile a record identifying or otherwise encapsulating identification of service tasks 12 for worker 4 as work list 22.
  • the compiled work list 22 may comprise service tasks 12 that are currently due and service tasks 12 that are predicted to become due after other service tasks 12 have been completed.
  • Service tasks 12 may be predicted by using (1 ) all future assignments or requirements specified in a workflow definition that are mapped to certain work types 50 and service tasks 12; (2) only those future assignments or requirements specified in the workflow definition that are mapped to certain work types and service tasks 12 and that will become due when the (previously defined) default conditional alternatives are assumed to become true; and/or (3) only those future tasks specified in the workflow definition that are mapped to certain work types and service tasks 12, and that will become due when the most likely conditional alternatives are assumed to become true.
  • process design may be isolated from task allocation.
  • systems using the present invention may provide support for multiple dimensions of responsibility for determining task delegation as well as support for explicit assumption of dynamic responsibilities, such as patient care.
  • systems using the present invention may provide support for team based responsibility and multiple levels of oversight. Given its dynamic allocation, systems using the present invention may provide for reallocation of task responsibility, including those tasks in the midst of completion.
  • the present invention is consistent with a complex environment such as healthcare.
  • services are provided to patients. These services are amenable to management with workflow engine technology. Typically, the services require the involvement of many different individuals and many different departments. The services selected, and therefore the work steps required, are chosen based upon the patient's needs.
  • one or more particular workers 4 may act in multiple roles.
  • worker 4 can be a nurse with his or her own group of patients; a nurse who is a member of a team, seeing work tasks for her team member's patients; and/or a head nurse, viewing all of the tasks for her subordinate nurses' patients.
  • the flexibility allows a work list 22 to be constructed based upon the multiple factors inherent in complex environment such as healthcare. It also permits the development of complex work lists 22 which are assembled from multiple views 40 and which can render items from different views 40 in an easily recognizable manner. For example, a nurse who is a member of the nursing team could have the work items for her own patients rendered in bold, and those of her team members in italics. This may be accomplished by numerous equivalent means, such as by dynamically creating a work list 22 based upon the correlation between the user's role(s), user's patient responsibilities, the work items, and the targeted patients.
  • Workflow engines can provide coordination of many constituent work steps. However, in some situations various entities such as departments or group supervisors tasked with fulfilling the service requests choose which individuals will perform them. This creates a far more flexible system, comprising:
  • the present invention further provides a mechanism for designing workflow processes in healthcare in a generic fashion, while supporting their specific implementation.
  • Fig. 3 is a schematic flow of an embodiment showing relationships between certain components of the present invention.
  • the system in response to the received identification information, the system, using the workflow engine, compiles a record that includes a list of service tasks 12 to be performed by worker 4.
  • Compiled records may be used to provide work list 22 that is also based at least partially on one or more worker roles 26,27 and a list of service tasks 12 associated with worker 4.
  • display of the compiled work list 22 may be initiated at a display device for worker 4.
  • relationships between work item data object 24d, role data object 24c, worker data object 24b, and patient data object 24a allow creation of work list 22 for a worker 4 from the compiled record.
  • actual work steps 52 may also be defined using work step types 50 encapsulated in work step data object 24d.
  • patient requirements 12 may be retrieved from patient data object 24a and merged into a master work list 23, e.g. at database 32 (Fig. 1).
  • master work list 23 may then be manipulated such as by using work list views 40 to create a set of tasks tailored to worker 4. This allows the same work list item to be viewed in many different contexts, such as those pertaining to team nursing described above.
  • a displayable task schedule comprising one or more activities to be performed on or for one or more specific, service tasks 12 by a particular worker 4 (Fig. 1 ) may be created and manipulated.
  • the present invention may be used to provide separation between workflow process design and task delegation logic, and permit workflow processes to be configured based upon their optimal performance without requiring direct knowledge of the individual workers 4 who will ultimately perform the tasks, at the time the process is defined and the workflow task is designed.
  • the present invention separates the tasks of workflow process design from those tasks entailed in assigning responsibility to individuals.
  • Workflow designer 2 may configure the work step without prior knowledge of the individual, role, group or skill who will ultimately be assigned to perform the task, e.g. worker 4.
  • the responsibility for performing the task may be assigned at task execution time.

Abstract

A method for providing a displayable task schedule of tasks to be performed on behalf of specific service tasks such as individuals by a particular worker of a plurality of workers is disclosed. In an embodiment, the method comprises receiving worker identification information; compiling a list of tasks to be performed by a worker in response to the received identification information based on a role assigned to the worker and a list of service tasks; and initiating display of the compiled list of tasks. It is emphasized that this abstract is provided to comply with the rules requiring an abstract which will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope of meaning of the claims.

Description

A SYSTEM AND USER INTERFACE FOR PROCESSING TASK SCHEDULE INFORMATION PRIORITY
This application claims priority through United States Provisional Application 60/316,604 filed August 31 , 2001 for "A System And User Interface For Processing Task Schedule Information." FIELD OF THE INVENTION
The present invention relates to project management systems in general. More specifically, the present invention relates to mechanisms for reconciling complex and overlapping responsibilities for complex tasks such as those found in a healthcare environment with task allocation models that may be supported by workflow engines. However, the present invention is equally applicable in other industries where complex task allocation is required. BACKGROUND OF THE INVENTION
Prior art workflow engines permit manipulation of workflow processes, including defining individual work steps to be allocated to systems, individuals, groups of individuals or systems, or combinations thereof. For work steps delegated to systems, individuals, or groups, a desired task description is typically placed into a destination work list, e.g. a set of tasks to be accomplished, at least in part, by or for that system, individual, or group. Destination work lists may be defined at the time that the workflow process definition is created.
Work steps are typically placed into a specific destination work list in response to an event such as the completion of a previous work step or the reception of a system message, rather than when an individual or system is ready to carry out the task associated with that work step.
Prior art workflow models are insufficient for a complex industry such as healthcare. By way of example, in a healthcare system a task such as "dispense medication" may be defined within a workflow process named "medication administration." However, at the time that the workflow process is defined, several degrees of uncertainty may exist including specifics regarding medication, a patient to whom the medication will be administered, a time when the administration is due, and the person who will be responsible at that time for administering the medication. It is preferable that a single process definition should be applicable to all instances of the process, e.g. a drug administration definition should be applicable to the administration of Drug A by nurse Jones on 4 West to patient Smith as well as the administration of Drug B by nurse Galloway to patient McCall on 3 South.
Additionally, in healthcare many individuals may share responsibility for a single service task, and therefore it may be necessary to view the same service task within multiple work lists. For example, nurse Galloway may be on a team with two other nurses. While each nurse on the team may have primary responsibility for a select group of patients, the other two may have secondary responsibility to perform service tasks for those patients if the first nurse, e.g. Galloway, is not available. Therefore, all three nurses may need to see overlapping work items on their own work lists, although these items may need to be presented differently depending on whether the nurse has primary or secondary responsibility. Additionally, a head floor nurse, prior to assigning a new admission, may need to see all of her subordinate nurses' pending tasks.
Prior art workflow engines require an explicit association of work steps and work lists at the time a process is designed. Further, each prior art work step is typically delegated to its associated work list when a system event occurs, not when an individual or system is ready to carry out the service task associated with that work step. This mechanism is inadequate for complex industries such as healthcare. Using the example above, all medication administration work steps could be assigned to a group of nurses who may use a descriptor such as "floor nurse." If a separate group were assigned for each nursing floor, then a separate workflow process would have to be defined for medication administration for each nursing unit. Even then, all of the nurses on each nursing floor would be exposed to all of the patients' service tasks, and there would be no mechanism to explicitly assign service tasks to an appropriate, responsible nurse. Instead each nurse would have to search through the entire ward's nursing tasks to find her own.
Some prior art systems allow for administrative oversight of running tasks, with the ability to manually reassign responsibility for a service task from one individual to another. However, the volume and complexity of doing this in a healthcare setting makes it impractical. By way of example and not limitation, role assignment in healthcare may require that each of the following occur independently: optimal processes are configured, workers are assigned roles (by way of example, IV nurse, floor nurse), roles are correlated with service tasks, and workers assume responsibility for patients. All of these factors taken in concert may determine the appropriate individual responsibility for the performance of a task.
Additionally, some prior art workflow systems allow work items to be delegated to a "role." This allows a service task to be assigned to an individual who will satisfy a role before the process instance is run. By way of example, this can support task delegation to an "officer of the day," as a different officer could assume the role each day. However, this is also not sufficient for healthcare. By way of example, the responsibility for performing a task is not only related to which nurses will be working on "4 West" on a given day and on a given shift, but also upon which patients will be admitted and which nurses will have direct responsibility for which patients. Therefore, it is not possible at workflow process design time to determine which role the task needs to be delegated to. SUMMARY
The present invention comprises a method for providing a displayable schedule of service tasks to be performed by a particular worker of a plurality of workers, e.g. tasks to be undertaken for or on behalf of specific individuals or objects such as products, equipment, and/or supplies. In an embodiment, the method comprises receiving worker identification information; generating a compilation of service tasks to be performed by the identified worker based on a role or roles assigned to the worker and a list of individuals or objects associated with the worker; and initiating display of the compilation.
In a further embodiment, the method comprises defining roles; defining work step types; creating work steps to be accomplished by workers; mapping work steps to the work step types; mapping work step types to roles; receiving identification information about a worker; assigning at least one role to the worker; generating a record of service tasks to be performed by the worker in response to the received identification information based on the at least one role, the performable tasks' targeted service tasks, and the assigned relationship between the worker and those targeted service tasks; and initiating display of the compiled list of tasks.
The scope of protection is not limited by the summary of an exemplary embodiment set out above, but is only limited by the claims. BRIEF DESCRIPTION OF THE DRAWINGS
These and other features, aspects, and advantages of the present invention will become more fully apparent from the following description, appended claims, and accompanying drawings in which:
Fig. 1 is a schematic of an exemplary system embodiment;
Fig. 2 is a diagrammatic representation of an exemplary work list view and work lists;
Fig. 3 is a representative relationship flow model of an exemplary of the present invention; and
Fig. 4 is a flowchart of an exemplary embodiment the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
The present invention may be used to allocate tasks among one or more appropriate workers in a complicated work environment. In general, throughout this description, if an item is described as implemented in software, it can equally well be implemented as hardware.
Further, as used herein, "user," "worker," and "entity" are understood to interchangeably comprise a individual user or worker, a group or category of users or workers, a role or characteristic of one or more users or workers or groups, and/or a particular device or system such as a medical device or system. As used herein, a "service task," i.e. service task 12, comprises actions to be undertaken by or on the behalf of a worker, e.g. "4" in Fig. 1, or, in healthcare systems, a patient or both as well as items needed to satisfy a requirement for which worker 4 is responsible. For example, in a healthcare environment, service task 12 may include items associated with patient care needs, including the patient himself or herself, by way of example including: a physician order and its associated data; administration of laboratory tests and data associated with the laboratory tests; data associated with patient billing; therapy plans and actual therapy; medication administration and the medication, e.g. pills, shots, or bandaging; and the like; and combinations thereof. It is also understood that although a healthcare clinical information system is used as an exemplary system for illustration purposes, the present invention is applicable to systems involving processing of sequential tasks including in vertical markets in which a workflow engine is embedded within an OEM computer system.
As further used herein, "record" is used herein to signify information or data material to a particular subject where the information or data are preserved in non-volatile, permanent, or tangible form such as in a computer file, disk, CDROM, DVD, or other electronic storage, or the like, or combinations thereof, that are accessible by a computer or other electronic or data processing system.
Referring now to Fig. 1 , a schematic overview of a workflow system embodiment of the present invention, the present invention provides a solution for embedding workflow engine technology within a comprehensive vertical software system in an OEM fashion. Although prior art workflow systems have ways to access work list items, additional useful ways may be desired to access work list items. For example, it may be desirable to access all of the individual work steps relating to a specific patient, constituting that patient's activity plan; all of the medication administration work steps for a specific patient, constituting that patient's medication administration record; and/or all of the medication administration work steps for all of a specific nurse's assigned patients, representing that nurse's medication administration task list. The inventors have recognized that it is advantageous to provide this kind of work list flexibility within healthcare in which tasks are assigned to individuals based upon dynamic, complex formulae. In an exemplary embodiment, a system for creating work flows according to the present invention comprises first computer 10 useful in designing and modifying a desired workflow process; second computer 20 where second computer 20 is operatively in communication with first computer 10; and third computer 30 where first computer 10 is operatively in communication with third computer 30. Third computer 30 may act as a server and comprise a workflow engine (not shown in the figures) and database 32. User 2, if user 2 has the authority to design and modify a workflow process, may use first computer 10 to access third computer 30 to create, modify, and manipulate workflow process definitions 22 and work list views 40 (Fig. 2) to create a work step to be performed by worker 4 and the work list view 40 in which it is rendered. Worker 4 may use second computer 20 to access the system and receive a work list 22 tailored for that worker 4. Accordingly, both first computer 10 and second computer 20 comprise input devices (not specifically shown in the figures) such as for entering data, e.g. identification of worker 4, and output devices such as for displaying work lists 22. As will be understood by those in the art, the input device may include a keyboard, a mouse, a biometric device, a card or badge reader, or the like, or combinations thereof. Similarly, the output device may include a display screen, a printer, a pager, a cell phone, a facsimile machine, or the like, a combination thereof.
Computer 10 is useful to allow user 2 with appropriate rights to design and modify a workflow. Computer 10 communicates with a workflow engine (not shown in the figures) executing in a computer such as third computer 30 having access to a database such as 32.
Once implemented, the present invention allows user 2 with appropriate rights to create, modify, and manipulate workflow process definitions 22 and work list views 40 (Fig. 2) such as by mapping work item types, e.g. specific work tasks, to one or more general characteristics of one or more workers 4 who will execute the tasks defined in the workflow design, e.g. service task 12. Additionally, a worker role 26 (Fig. 3) may be represented in the system by a generic code for a "virtual" role 27 (Fig. 3), i.e. a placeholder to be satisfied in real-time by a code representing a specific worker 4. As used herein, a "role" 26, 27 may comprise a task, office, or job description for which a workflow administrator may wish to assign a work item, for example in a healthcare environment comprising nursing roles, administrative roles, physician roles, physician assistant roles, therapist roles, technician roles, and the like, or combinations thereof.
As described more fully below and as will be familiar to those of ordinary skill in the database arts, work list view 40 may be defined by a relationship between one or more tables in one or more databases that can be manipulated programmatically. Work lists 22 and work list views 40 (Fig. 2) may be associated with work flows, such as for institution 90, that relate workers 4 to service tasks 12 and that may be the end result of work-related assignments for institution 90, e.g. patient requirements such as medication to be taken, meals to be provided, drugs to be administered, or therapy to be administered, or the like, or combinations thereof.
Because the workflow engine may be embedded in a vertical application system, workers 4 may access the features of the present invention through an interface associated with the vertical system. Accordingly, worker 4 may log into a system such as at computer 20 to access vertical system software and, once logged into that vertical system software, view a compiled record comprising work lists 22 associated with worker 4 on a display device, e.g. a display screen, a printer, pager, cell phone, or the like, or a combination thereof. It is understood that computer 10, computer 20 and third computer 30 need not be separate computers but may be a single computer or computer system.
Referring additionally to Fig. 2, an object schematic of a work list view, work list 22 may be created by examining worker data objects 24b related to worker 4. In an exemplary embodiment, properties of worker data object 24b may include a user role property, e.g. userRolelD, which contains a value representing an actual user role 26 (Fig. 3) or a virtual role 27 (Fig. 3) that the specific worker 4 can satisfy. Worker data objects 24b may be queried using a unique user role 26 identifier for worker 4 as well as one or more virtual roles 27 that worker 4 may satisfy. For example, worker 4 may satisfy a virtual role 27 for a medication giver as well as a virtual role 27 for a physical therapist but not a virtual role 27 for a medication prescriber.
Work item types may have additional descriptions such as at work step data object 24d. These descriptions and other properties may be related to virtual role object 24c such as by a work item type identifier.
In this exemplary health care example, a patient may be dynamically associated with worker 4 in real-time, such as shown at patient data object 24a. For example, patient data object 24a may relate an actual patient with a specific worker 4. Patients may additionally have needs or requirements directly or indirectly associated with those patients which one or more workers 4 need to address as part of a work assignment for worker 4.
One or more service tasks 12 will be retrievable based on worker data object 24b that is related into role data object 24c such as by the identifier of worker 4. Work list 22 may then be created based using the patient data and data for worker 4.
Each work list 22 may further comprise a task identifier as well as an identifier of the responsible worker 4 (Fig. 1 ) to be assigned the service task. The identifier for worker 4 may be a generic code at creation, e.g. one for a virtual role 27, and filled in with a code representing a specific worker 4 at runtime. Work lists 22 may therefore comprise work item types such as specific work tasks to be mapped to a general user characteristics. Using virtual roles 27, specific workers 4 (Fig. 1) may be associated with one or more virtual roles 27 and then dynamically mapped into a virtual role 27 associated with work list 22 such as at runtime. Thus, virtual role 27 may act as a "place holder" to be satisfied by a specific worker 4 at the time when the task is to be performed. Additionally, one or more characteristics of the task to be performed, e.g. a patient identifier, may also be mapped dynamically to worker 4.
By way of example and not limitation, in an exemplary health care embodiment, a virtual role 27 may be associated with a predetermined type of work step. The actual work step, e.g. a step to effect a specific service task 12, may, in turn, also be associated with a predetermined work step type. Further, both workers 4 and work steps may be independently associated with patients such as on an individual and/or group basis. Using these associations, worker 4 may be assigned a subset of work steps based upon virtual role 27 and patient associations.
One or more work lists 22 may be accessed through one or more work list views 40. Such work list views 40 may access a single data collection (such compiled records of work lists 22 contained in database 32 in Fig. 1 ) using numerous methods as will be familiar to those of ordinary skill in the database arts, e.g. SQL joins, filters, and the like.
In the operation of an exemplary embodiment, referring now to Fig. 4, a flowchart of an exemplary embodiment, a displayable task schedule concerning service tasks 2 to be performed by a particular worker 4 of a plurality of workers 4 is created by receiving identification information reflective of worker 4; compiling a record identifying service tasks 12 to be performed by worker 4 in response to the received identification information and based at least partially on at least one of a role 26 assigned to the worker 4, a service task 12 associated with the identified worker 4, and/or a predetermined relationship between the identified worker 4 and the intended a target beneficiary of the service task 12; and initiating display of the compiled record at a display device. The displayable compiled record may be formatted for display as a schedule of service tasks 12 that may be performed by at least one worker 4 of a plurality of workers 4.
Accordingly, one or more worker roles 26 are defined by user 2 with appropriate authority to define worker roles 26. User 2 with appropriate authority to define work step types also defines one or more work step types. Additionally, user 2 with appropriate authority to create a work step creates a work step to be accomplished by worker 4, and user 2 with appropriate authority to map work steps to work step types maps the work step to a work step type. Each of these users 2 above may be the same user 2 or may be a plurality of users 2, each of whom has differing authority.
Work step types are mapped to worker roles 26,27. Accordingly, when worker 4 wish to use the present invention, worker 4 provides identification information about the worker 4 which is received into the system, whereupon user role 26 is assigned to worker 4 and a record comprising descriptions of service tasks 12 to be performed by worker 4 in response to the received identification information is compiled, based on the user role 26 assigned to worker 4. The record may then be formatted for display at a display device, e.g. computer 20.
User 2 with appropriate rights, such as an administrator, explicitly defines 100 one or more worker roles 26 (Fig. 3). When a new work step 50 (Fig. 3) is created 110, the new work step 50 is registered and assigned 120 a work item type (not shown in the figures) by the work step definition creator, e.g. user 2. In a currently preferred embodiment, this is an explicit operation required for each new work step 50. By way of example and not limitation, in a typical embodiment, user 2 (Fig. 1) acting as a workflow designer may configure one or more work steps such as "dispense medication" within a process design such as at computer 10 (Fig. 1).
In a currently preferred embodiment, user 2 acting as a workflow designer (shown in Fig. 1 ) creates workflow processes utilizing work steps 52 (Fig. 3) that have been pre-configured. If workflow designer user 2 identifies a new work step 52, the new work step 52 may be registered with an associated work step type 50. Further, as discussed herein below, when worker 4 signs on and requests work list 22, work list view 40 may be dynamically constructed which matches one or more worker roles 26,27 associated with worker 4 to appropriate work steps 52, e.g. for service tasks 12 (Fig. 1) associated with patient requirements. If the workflow engine needs to escalate a task to worker 4, it may examine the work task type and one or more work detail characteristics, e.g. an associated patient ID, and then query for roles 26, 27 associated with the task type. Once the query is answered, a system using an embodiment of the present invention identifies an individual worker 4 associated both with that role 26,27 and that work detail characteristic.
Workflow engines may be associatable with work flows such as for a target process, e.g. one involving institution 90 (Fig. 1). Accordingly, users 2 may explicitly define roles 26,27 such as for institution 90 (Fig. 1) and then explicitly map work task types 50 onto these roles 26,27 either automatically or manually 130. In a preferred embodiment, an automated method of mapping is consistent with manual processes. For example, a new work task type 50 may be defined based upon an existing work task type 50, automatically inheriting the role relationships of the parent work task 50.
By separating the correlation between work steps 50 and roles 26,27 from a workflow configuration, the present invention allows tasks to be reassigned to accommodate new delivery models without impacting workflow configurations. By way of example and not limitation, an institution 90 (Fig. 1) such as a hospital may implement a new service task 12 such as pulse oximetry. Based upon their roles 26, 27 as well as the relationship(s) between roles 26,27 and service tasks 12 to be accomplished, hospital 90 decides which workers 4 will be needed to provide service task 12 when it is ordered, e.g. respiratory therapy, nursing, or both. By way of further example and not limitation, when an attending doctor requests work list 22, the doctor (worker 4) may be presented with a list of service tasks 12, e.g. tasks appropriate for that physician, but which are further limited to service tasks 12 for those patients for whom the doctor is then responsible. Once work steps 50 are defined and assigned, individual workers 4 (Fig. 1) may be dynamically mapped 140 into roles 26,27 such as by using relational database techniques or object queries. By way of further example, each individual healthcare worker 4 may explicitly assume responsibility 150 for one or more individual service tasks 12 such as patient care responsibility (Fig. 1). However, such responsibilities may be implemented with a single service task 12 such as an item needed to satisfy a patient care requirement; with a group of service tasks 12 such as patient care responsibility for the group; or on an abstraction such as a nursing unit, department, or other level that can be resolved to a group of service tasks 12 such as patient care responsibility for all of the patients contained within the group. Worker 4, e.g. a, doctor or a nurse, may then assume responsibility for a group of service tasks 12 such as at a shift change. Workers 4 may also assume responsibility for a plurality of groups of service tasks 12, e.g. a respiratory therapist may assume responsibility for groups of patient requirements on several floors in hospital 90. Moreover, an individual worker 4 may also assume responsibility such as in an oversight or team capacity. Using virtual roles 27, user roles 26, and other data such as data relating to work steps 50 and service tasks 12 such as patient requirements, the present invention may capture assignment of service tasks 12, create a mapping between patients and workers 4, and use the mapping to present appropriate work items to worker 4. By way of example, in an exemplary hospital embodiment, such mapping may correspond to a nurse signing on to a system of the present invention, e.g. as a "floor nurse" on "4 West" or as an "ICU nurse" in a "surgical ICU" section. Once signed in, the nurse may use a user interface appropriate for both the contextual setting and her role (not shown in the figures) to request 160 a work list 22. By linking the user, e.g. the nurse, to a role 26, e.g. "ICU nurse," the present invention is able to provide appropriate work lists 22 that show those tasks appropriate for that user's role.
When worker 4 requests work list 22 such as at step 160, the present invention may examine 170 the worker role 26 of worker 4 and then map worker 4 to work task types 50 associated with that worker role 26. Such an examination may further entail examining service tasks 12 currently assigned to worker 4 and creating a work list view 40 from master work list 23 (Fig. 3) to show only those tasks appropriate to the worker role 26 of that worker 4 that pertains to service tasks 12 for whom that worker 4 has responsibility.
Once the mapping is completed, the present invention may compile a record identifying or otherwise encapsulating identification of service tasks 12 for worker 4 as work list 22. The compiled work list 22 may comprise service tasks 12 that are currently due and service tasks 12 that are predicted to become due after other service tasks 12 have been completed. Service tasks 12 may be predicted by using (1 ) all future assignments or requirements specified in a workflow definition that are mapped to certain work types 50 and service tasks 12; (2) only those future assignments or requirements specified in the workflow definition that are mapped to certain work types and service tasks 12 and that will become due when the (previously defined) default conditional alternatives are assumed to become true; and/or (3) only those future tasks specified in the workflow definition that are mapped to certain work types and service tasks 12, and that will become due when the most likely conditional alternatives are assumed to become true.
Accordingly, using the present invention, process design may be isolated from task allocation. Further, systems using the present invention may provide support for multiple dimensions of responsibility for determining task delegation as well as support for explicit assumption of dynamic responsibilities, such as patient care. Further, systems using the present invention may provide support for team based responsibility and multiple levels of oversight. Given its dynamic allocation, systems using the present invention may provide for reallocation of task responsibility, including those tasks in the midst of completion.
In an exemplary embodiment, the present invention is consistent with a complex environment such as healthcare. In healthcare, services are provided to patients. These services are amenable to management with workflow engine technology. Typically, the services require the involvement of many different individuals and many different departments. The services selected, and therefore the work steps required, are chosen based upon the patient's needs. However, in complex work environments, one or more particular workers 4 may act in multiple roles. By way of example and not limitation, worker 4 can be a nurse with his or her own group of patients; a nurse who is a member of a team, seeing work tasks for her team member's patients; and/or a head nurse, viewing all of the tasks for her subordinate nurses' patients. The flexibility allows a work list 22 to be constructed based upon the multiple factors inherent in complex environment such as healthcare. It also permits the development of complex work lists 22 which are assembled from multiple views 40 and which can render items from different views 40 in an easily recognizable manner. For example, a nurse who is a member of the nursing team could have the work items for her own patients rendered in bold, and those of her team members in italics. This may be accomplished by numerous equivalent means, such as by dynamically creating a work list 22 based upon the correlation between the user's role(s), user's patient responsibilities, the work items, and the targeted patients.
Workflow engines can provide coordination of many constituent work steps. However, in some situations various entities such as departments or group supervisors tasked with fulfilling the service requests choose which individuals will perform them. This creates a far more flexible system, comprising:
• Support for dynamic reallocation of responsibilities;
• Provision for multilevel, team based task assignment;
• Allowing work list items to be viewed in multiple different contexts; and
• The present invention further provides a mechanism for designing workflow processes in healthcare in a generic fashion, while supporting their specific implementation.
Fig. 3 is a schematic flow of an embodiment showing relationships between certain components of the present invention. Referring additionally to Fig. 1 , in an exemplary embodiment, in response to the received identification information, the system, using the workflow engine, compiles a record that includes a list of service tasks 12 to be performed by worker 4. Compiled records may be used to provide work list 22 that is also based at least partially on one or more worker roles 26,27 and a list of service tasks 12 associated with worker 4. Once the record is compiled, display of the compiled work list 22 may be initiated at a display device for worker 4.
As shown additionally in Fig. 2 and discussed above, relationships between work item data object 24d, role data object 24c, worker data object 24b, and patient data object 24a allow creation of work list 22 for a worker 4 from the compiled record. Additionally, actual work steps 52 may also be defined using work step types 50 encapsulated in work step data object 24d. For example, patient requirements 12 may be retrieved from patient data object 24a and merged into a master work list 23, e.g. at database 32 (Fig. 1). Once created, master work list 23 may then be manipulated such as by using work list views 40 to create a set of tasks tailored to worker 4. This allows the same work list item to be viewed in many different contexts, such as those pertaining to team nursing described above.
Accordingly, a displayable task schedule comprising one or more activities to be performed on or for one or more specific, service tasks 12 by a particular worker 4 (Fig. 1 ) may be created and manipulated. In part, the present invention may be used to provide separation between workflow process design and task delegation logic, and permit workflow processes to be configured based upon their optimal performance without requiring direct knowledge of the individual workers 4 who will ultimately perform the tasks, at the time the process is defined and the workflow task is designed.
In an exemplary embodiment, the present invention separates the tasks of workflow process design from those tasks entailed in assigning responsibility to individuals. Workflow designer 2 may configure the work step without prior knowledge of the individual, role, group or skill who will ultimately be assigned to perform the task, e.g. worker 4. In one embodiment, the responsibility for performing the task may be assigned at task execution time.
It will be understood that various changes in the details, materials, and arrangements of the parts which have been described and illustrated above in order to explain the nature of this invention may be made by those skilled in the art without departing from the principle and scope of the invention as recited in the following claims.

Claims

CLAIMS What is claimed is: 1 ) A method for providing a displayable task schedule of at least one service task to be performed by at least one worker, comprising the steps of: a. receiving worker identification information; b. compiling a record identifying a service task to be performed by the worker, wherein the compiled record: i. is generated in response to the received identification information; and ii. is based at least partially on at least one of:
(1 ) a role assigned to the worker;
(2) a service task associated with the worker; and
(3) a predetermined relationship between the worker and the service task; and c. initiating display of the compiled record at a display device.
2) The method of claim 1 , wherein the service task is at least one of (a) a physician order, (b) administration of laboratory or other diagnostic tests, (c) therapy plans, (d) therapy services administration, (e) medication administration, and (f) medication administration plans.
3) The method of claim 1 , wherein the role assigned to the worker is at least one of (a) a nursing role, (b) an administrative role, (c) a physician role, (d) a physician assistant role, (e) a therapist role, (f) a technician role, and (g) a role assigned by a workflow administrator.
4) The method of claim 1 , wherein the role assigned to the worker comprises a role performable by more than one worker of a predetermined plurality of workers.
5) The method of claim 4 wherein: a. the multiple workers comprise a multilevel team; and b. the role comprises a team-based task assignment. 6) The method of claim 1 wherein the role assigned to the worker comprises task characteristics associated with a service task.
7) The method of claim 1 wherein step (b) further comprises the step of compiling the record by using a view of service tasks, the view reflecting a predetermined context.
8) The method of claim 1 wherein the compiled record in step (c) further indicates who is currently responsible for executing a predetermined service task based on current assignment of roles and current association with service tasks.
9) The method of claim 1 , wherein the service task further comprises a work step, the method further comprising the steps of: a. associating the work step with a work step type; b. associating the work step type with a virtual role for a worker; c. relating the worker to a service task; and d. relating the worker to the virtual role.
10) The method of claim 9, further comprising the step of relating the worker to individuals for whom the service task will be performed
11 ) The method of claim 9 further comprising the step of dynamically reallocating responsibilities associated with the work step to the worker in response to the received identification information based on a role assigned to the worker.
12) A method for providing a displayable task schedule of a service task to be performed by at least one worker of a plurality of workers, comprising the steps of: a. defining a worker role by a user with appropriate authority to define the worker role; b. defining a work step type by a user with appropriate authority to define work step types; c. creating a work step to be accomplished by the at least one worker by a user with appropriate authority to create a work step; d. mapping the work step to the work step type by a user with appropriate authority to map the work step to the work step type; e. mapping the work step type to the worker role; f. receiving identification information about the at least one worker; g. assigning the worker role to the at least one worker; h. compiling a record identifying service task s to be performed by the at least one worker in response to the received identification information based on the worker role assigned to the at least one worker; and i. initiating display of the compiled record at a display device.
13) The method of claim 12 wherein step (i) further comprises the steps of: i. mapping work task types to the worker role; ii. examining additional criteria useful for filtering work task types; iii. creating a view of a master work list, the view based at least partially on a context comprising the work task types mapped to the worker role and the additional criteria; and iv. creating a display of the compiled record using the view.
14) The method of claim 12 wherein the compiled record comprises service tasks that are currently due and service tasks that are predicted to become due after other service tasks have been completed.
15) The method of claim 14 wherein the predicted tasks are predicted by at least one of: a. including a predetermined number of future tasks specified in a definition of the workflow that are mapped to predetermined work types and service tasks; b. including only predetermined future tasks specified in the workflow definition that are mapped to certain work types and service tasks and that will become due when the default conditional alternatives are assumed to become true; and c. including only predetermined future tasks specified in the workflow definition that are mapped to certain work types and service tasks, and that will become due when the most likely conditional alternatives are assumed to become true.
16) A computer program embodied within a computer-readable medium created using the method of claim 1.
PCT/US2002/020650 2001-08-31 2002-07-01 A system and user interface for processing task schedule information priority WO2003021509A2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2003525775A JP2005502137A (en) 2001-08-31 2002-07-01 System and user interface for processing task schedule information priority
EP02744744A EP1421528A2 (en) 2001-08-31 2002-07-01 A system and user interface for processing task schedule information priority
CA002457962A CA2457962A1 (en) 2001-08-31 2002-07-01 A system and user interface for processing task schedule information

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US31660401P 2001-08-31 2001-08-31
US60/316,604 2001-08-31
US10/114,218 2002-04-02
US10/114,218 US6714913B2 (en) 2001-08-31 2002-04-02 System and user interface for processing task schedule information

Publications (2)

Publication Number Publication Date
WO2003021509A2 true WO2003021509A2 (en) 2003-03-13
WO2003021509A3 WO2003021509A3 (en) 2004-01-22

Family

ID=26811938

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/020650 WO2003021509A2 (en) 2001-08-31 2002-07-01 A system and user interface for processing task schedule information priority

Country Status (5)

Country Link
US (1) US6714913B2 (en)
EP (1) EP1421528A2 (en)
JP (1) JP2005502137A (en)
CA (1) CA2457962A1 (en)
WO (1) WO2003021509A2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005259113A (en) * 2004-02-12 2005-09-22 Ricoh Co Ltd Process editing apparatus, process management apparatus, process editing program, process management program, recording medium, process editing method and process management method
WO2015145405A1 (en) * 2014-03-28 2015-10-01 Koninklijke Philips N.V. Smart phone based multi-patient worklist (spwl)
WO2016120527A1 (en) 2015-01-28 2016-08-04 Eränkö Timo System and method for communication in a telecommunication network

Families Citing this family (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732092B2 (en) * 2001-09-28 2004-05-04 Client Dynamics, Inc. Method and system for database queries and information delivery
US20030126004A1 (en) * 2001-12-27 2003-07-03 International Business Machines Corporation Method and system for a graphical view of selectable work items
US20030149598A1 (en) * 2002-01-28 2003-08-07 Santoso Nugroho Iwan Intelligent assignment, scheduling and notification scheme for task management
US8457980B1 (en) * 2002-04-17 2013-06-04 Parkview Health System, Inc. Method of administering the delivery of health care services
US7386797B1 (en) * 2002-05-22 2008-06-10 Oracle Corporation Framework to model and execute business processes within a collaborative environment
US20040030614A1 (en) * 2002-06-19 2004-02-12 Shields Jay C. Computer-implemented method and system for managing workload of procurement individuals
US20040249674A1 (en) * 2003-05-06 2004-12-09 Eisenberg Floyd P. Personnel and process management system suitable for healthcare and other fields
US20040260593A1 (en) * 2003-05-20 2004-12-23 Klaus Abraham-Fuchs System and user interface supporting workflow operation improvement
US20050015279A1 (en) * 2003-05-21 2005-01-20 Rucker Donald W. Service order system and user interface for use in healthcare and other fields
US7590971B2 (en) * 2003-08-01 2009-09-15 Idx Investment Corporation Enterprise task manager
US20070274506A1 (en) * 2003-08-20 2007-11-29 Bret Schundler Distributed call center system and method for volunteer mobilization
US7399205B2 (en) 2003-08-21 2008-07-15 Hill-Rom Services, Inc. Plug and receptacle having wired and wireless coupling
US20050108050A1 (en) * 2003-10-14 2005-05-19 Claus Knapheide Medical information user interface and task management system
US20050251418A1 (en) * 2003-10-15 2005-11-10 Cerner Innovation, Inc. System and method for processing ad hoc orders in an automated patient care environment
US20050086072A1 (en) * 2003-10-15 2005-04-21 Fox Charles S.Jr. Task-based system and method for managing patient care through automated recognition
US7664657B1 (en) 2003-11-25 2010-02-16 Vocollect Healthcare Systems, Inc. Healthcare communications and documentation system
US20050138031A1 (en) * 2003-12-05 2005-06-23 Wefers Wolfgang M. Systems and methods for assigning task-oriented roles to users
US7487435B2 (en) * 2003-12-12 2009-02-03 Dynamic Logic, Inc. Method and system for conducting an on-line survey
US20050137926A1 (en) * 2003-12-17 2005-06-23 International Business Machines Corporation Method and apparatus for dynamic device allocation for managing escalation of on-demand business processes
EP1738307A4 (en) * 2004-03-24 2009-04-22 Clevor Technologies Inc A system and method for constructing a schedule that better achieves one or more business goals
US20050283400A1 (en) * 2004-05-13 2005-12-22 Ivo Nelson System and method for delivering consulting services and information technology solutions in a healthcare environment
US20050288965A1 (en) * 2004-06-23 2005-12-29 University Of Washington Role-based approach for managing patient care information generated by healthcare provider
US7319386B2 (en) * 2004-08-02 2008-01-15 Hill-Rom Services, Inc. Configurable system for alerting caregivers
US7852208B2 (en) 2004-08-02 2010-12-14 Hill-Rom Services, Inc. Wireless bed connectivity
US20060053035A1 (en) * 2004-09-09 2006-03-09 Eisenberg Floyd P Healthcare personnel management system
US7562026B2 (en) * 2004-11-12 2009-07-14 Siemens Medical Solutions Usa, Inc. Healthcare procedure and resource scheduling system
WO2006058103A2 (en) * 2004-11-24 2006-06-01 Siemens Medical Solutions Usa, Inc. A predictive user interface system
US20060253281A1 (en) * 2004-11-24 2006-11-09 Alan Letzt Healthcare communications and documentation system
US20060122865A1 (en) * 2004-11-24 2006-06-08 Erik Preiss Procedural medicine workflow management
WO2007035185A2 (en) * 2004-12-03 2007-03-29 Mckesson Automation Inc. Mobile point of care system and associated method and computer program product
US20060149599A1 (en) * 2005-01-03 2006-07-06 Cerner Innovation, Inc. System and method for automatically generating physician orders for urgent care
US7443303B2 (en) 2005-01-10 2008-10-28 Hill-Rom Services, Inc. System and method for managing workflow
US8655832B2 (en) * 2005-01-21 2014-02-18 International Business Machines Corporation Publishing activity tasks in a collaborative environment
US7356538B2 (en) * 2005-01-25 2008-04-08 International Business Machines Corporation Configurable business controls task notification
US20060173713A1 (en) * 2005-01-26 2006-08-03 Alan Petro Integrated medical device and healthcare information system
DE102005009056A1 (en) * 2005-02-28 2006-09-07 Siemens Ag Method for operating a medical information system
US8239238B2 (en) * 2005-03-21 2012-08-07 Microsoft Corporation Methods and apparatus for encoding a work item type definition
WO2006116529A2 (en) * 2005-04-28 2006-11-02 Katalytik, Inc. System and method for managing healthcare work flow
US8321241B1 (en) * 2005-05-31 2012-11-27 Allscripts Software, Llc Electronic patient record documentation with push and pull of data to and from database
US20070016466A1 (en) 2005-07-15 2007-01-18 Sterling Services Group, L.C. Patient room cleaning system and method
US7778844B2 (en) * 2005-08-04 2010-08-17 Idx Investment Corporation System and method for managing the exchange of information between healthcare systems
US20070043590A1 (en) * 2005-08-19 2007-02-22 Grey Trends, Llc Method and System of Coordinating Communication and Quality Control in Home Care
US7809761B2 (en) 2005-10-11 2010-10-05 Idx Investment Corporation Data object tracking system and method
JP5331289B2 (en) 2005-10-11 2013-10-30 株式会社日立製作所 Work management support method and work management support system using sensor nodes
US20070203746A1 (en) * 2005-10-24 2007-08-30 Siemens Medical Solutions Health Services Corporation System and user interface enabling user order item selection for medical and other fields
US10360996B2 (en) * 2006-03-31 2019-07-23 Cerner Innovation, Inc. Method for selectively associating content items with pre-configured alternatives based upon directed user input
US8825508B2 (en) * 2006-05-02 2014-09-02 Ascom Tateco Ab Method and apparatus for automated staff assignment
US20070288283A1 (en) * 2006-06-09 2007-12-13 Devshop Inc. Method for project management
US20070294322A1 (en) * 2006-06-19 2007-12-20 Cerner Innovation, Inc. Defining privileges in association with the automated configuration, implementation and/or maintenance of a healthcare information system
US20080021758A1 (en) * 2006-07-05 2008-01-24 Jan Teichmann Responsibility determination
US8621418B2 (en) * 2006-07-25 2013-12-31 International Business Machines Corporation Interlinked change-request computer system and method having role-based tabular interface
US8677319B2 (en) * 2006-07-25 2014-03-18 International Business Machines Corporation Computer method and system for composite state management of software change requests
US10242117B2 (en) * 2006-09-15 2019-03-26 Ent. Services Development Corporation Lp Asset data collection, presentation, and management
US20080071579A1 (en) * 2006-09-19 2008-03-20 Siemens Medical Solutions Usa, Inc. System For Acquiring and Processing Patient Medical information
US8788305B2 (en) * 2006-09-28 2014-07-22 Sap Ag Method for processing concurrent personnel assignments
US20080114638A1 (en) * 2006-11-10 2008-05-15 Inspection Management Systems, Inc. Parameter-based appointment scheduling system and method
US10540731B2 (en) 2006-11-24 2020-01-21 Compressus Inc. Pre-fetching patient data for virtual worklists
US10169533B2 (en) * 2006-11-24 2019-01-01 Compressus, Inc. Virtual worklist for analyzing medical images
US10635260B2 (en) * 2007-01-22 2020-04-28 Cerner Innovation, Inc. System and user interface for clinical reporting and ordering provision of an item
US8094521B2 (en) * 2007-02-28 2012-01-10 Nightingale Products LLC Caregiver personal alert device
US20080249816A1 (en) * 2007-04-05 2008-10-09 Luke Khalilian System and Method for Monitoring Workflow in a Project Management System
US20080270212A1 (en) * 2007-04-25 2008-10-30 Jeffrey Blight Method, apparatus or software for managing a data processing process
US20080288280A1 (en) * 2007-05-15 2008-11-20 Belcher Deborah J System and method for meeting payer protocols
US8461968B2 (en) * 2007-08-29 2013-06-11 Hill-Rom Services, Inc. Mattress for a hospital bed for use in a healthcare facility and management of same
US7868740B2 (en) 2007-08-29 2011-01-11 Hill-Rom Services, Inc. Association of support surfaces and beds
US8082160B2 (en) 2007-10-26 2011-12-20 Hill-Rom Services, Inc. System and method for collection and communication of data from multiple patient care devices
US8355928B2 (en) * 2007-12-05 2013-01-15 Siemens Medical Solutions Usa, Inc. Medical user interface and workflow management system
US8706748B2 (en) * 2007-12-12 2014-04-22 Decho Corporation Methods for enhancing digital search query techniques based on task-oriented user activity
US8169304B2 (en) 2008-02-22 2012-05-01 Hill-Rom Services, Inc. User station for healthcare communication system
US20090292578A1 (en) * 2008-05-20 2009-11-26 Catalina Maria Danis Articulation Workload Metrics
US8255225B2 (en) * 2008-08-07 2012-08-28 Vocollect Healthcare Systems, Inc. Voice assistant system
US8451101B2 (en) * 2008-08-28 2013-05-28 Vocollect, Inc. Speech-driven patient care system with wearable devices
US20100077458A1 (en) * 2008-09-25 2010-03-25 Card Access, Inc. Apparatus, System, and Method for Responsibility-Based Data Management
RU2015119672A (en) * 2008-11-06 2015-11-10 Конинклейке Филипс Электроникс, Н.В. METHOD AND SYSTEM FOR COORDINATION OF IMPLEMENTATION OF CLINICAL METHODOLOGICAL RECOMMENDATIONS
CN102203784B (en) * 2008-11-06 2019-06-04 皇家飞利浦电子股份有限公司 Dynamic clinical worklist
US20100223557A1 (en) * 2009-02-28 2010-09-02 Adam Kenney Method and system for workflow integration
US20100257015A1 (en) * 2009-04-01 2010-10-07 National Information Solutions Cooperative, Inc. Graphical client interface resource and work management scheduler
US20110029315A1 (en) * 2009-07-28 2011-02-03 Brent Nichols Voice directed system and method for messaging to multiple recipients
CN102053973A (en) * 2009-10-30 2011-05-11 国际商业机器公司 Device and method for providing page navigation in multi-character supporting network application
US20110153352A1 (en) * 2009-12-22 2011-06-23 Semian Douglas D Scheduling and communications system and method
US9697481B2 (en) * 2009-12-23 2017-07-04 Siemens Aktiengesellschaft Method for operating a hospital information system
US8779924B2 (en) * 2010-02-19 2014-07-15 Hill-Rom Services, Inc. Nurse call system with additional status board
JP2011192078A (en) * 2010-03-15 2011-09-29 Ricoh Co Ltd Task managing device and task management program
US20120053978A1 (en) * 2010-07-28 2012-03-01 Glen Robert Andersen Self-contained web-based communications platform for work assignments
EP2416267A1 (en) 2010-08-05 2012-02-08 F. Hoffmann-La Roche AG Method of aggregating task data objects and for providing an aggregated view
US20140006057A1 (en) * 2011-03-16 2014-01-02 Koninklijke Philips N.V. Patient virtual rounding with context based clinical decision support
US8577719B2 (en) * 2012-01-13 2013-11-05 Darlene Danece Bainbridge Strategic quality support system
US9411934B2 (en) 2012-05-08 2016-08-09 Hill-Rom Services, Inc. In-room alarm configuration of nurse call system
US9314159B2 (en) 2012-09-24 2016-04-19 Physio-Control, Inc. Patient monitoring device with remote alert
US10318635B2 (en) 2012-09-28 2019-06-11 Cerner Innovation, Inc. Automated mapping of service codes in healthcare systems
US10403391B2 (en) 2012-09-28 2019-09-03 Cerner Health Services, Inc. Automated mapping of service codes in healthcare systems
US10565315B2 (en) 2012-09-28 2020-02-18 Cerner Innovation, Inc. Automated mapping of service codes in healthcare systems
US20140324555A1 (en) * 2013-04-25 2014-10-30 Xerox Corporation Methods and systems for evaluation of remote workers
US10540448B2 (en) 2013-07-15 2020-01-21 Cerner Innovation, Inc. Gap in care determination using a generic repository for healthcare
US9830424B2 (en) 2013-09-18 2017-11-28 Hill-Rom Services, Inc. Bed/room/patient association systems and methods
US20150294251A1 (en) * 2014-04-11 2015-10-15 Nec Europe Ltd. Distributed task scheduling using multiple agent paradigms
US20160026941A1 (en) * 2014-07-26 2016-01-28 International Business Machines Corporation Updating and synchronizing existing case instances in response to solution design changes
US20160349942A1 (en) * 2015-05-29 2016-12-01 Rockwell Automation Technologies, Inc. Presentation of tasks to a user
US10600015B2 (en) 2015-06-24 2020-03-24 Karl Storz Se & Co. Kg Context-aware user interface for integrated operating room
US11123014B2 (en) 2017-03-21 2021-09-21 Stryker Corporation Systems and methods for ambient energy powered physiological parameter monitoring
US11605018B2 (en) 2017-12-27 2023-03-14 Cerner Innovation, Inc. Ontology-guided reconciliation of electronic records
US20200012977A1 (en) * 2018-07-03 2020-01-09 Sap Se Refined system-aided user definition in the current modeling context
US11449986B2 (en) 2018-10-23 2022-09-20 International Business Machines Corporation Enhancing medical imaging workflows using artificial intelligence
US11911325B2 (en) 2019-02-26 2024-02-27 Hill-Rom Services, Inc. Bed interface for manual location
US11675805B2 (en) 2019-12-16 2023-06-13 Cerner Innovation, Inc. Concept agnostic reconcilation and prioritization based on deterministic and conservative weight methods

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5530861A (en) * 1991-08-26 1996-06-25 Hewlett-Packard Company Process enaction and tool integration via a task oriented paradigm
US5937388A (en) * 1996-12-05 1999-08-10 Hewlett-Packard Company System and method for performing scalable distribution of process flow activities in a distributed workflow management system

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4847764C1 (en) * 1987-05-21 2001-09-11 Meditrol Inc System for dispensing drugs in health care instituions
US5842173A (en) * 1994-10-14 1998-11-24 Strum; David P. Computer-based surgical services management system
US5745901A (en) 1994-11-08 1998-04-28 Kodak Limited Workflow initiated by graphical symbols
US5692125A (en) * 1995-05-09 1997-11-25 International Business Machines Corporation System and method for scheduling linked events with fixed and dynamic conditions
US6061506A (en) * 1995-08-29 2000-05-09 Omega Software Technologies, Inc. Adaptive strategy-based system
US5799297A (en) 1995-12-15 1998-08-25 Ncr Corporation Task workflow management system and method including an external program execution feature
US5842976A (en) * 1996-05-16 1998-12-01 Pyxis Corporation Dispensing, storage, control and inventory system with medication and treatment chart record
US5987422A (en) 1997-05-29 1999-11-16 Oracle Corporation Method for executing a procedure that requires input from a role
US6088679A (en) * 1997-12-01 2000-07-11 The United States Of America As Represented By The Secretary Of Commerce Workflow management employing role-based access control
US6115646A (en) 1997-12-18 2000-09-05 Nortel Networks Limited Dynamic and generic process automation system
US6052684A (en) 1998-03-24 2000-04-18 Hewlett-Packard Company System and method for performing consistent workflow process execution in a workflow management system
US6078982A (en) 1998-03-24 2000-06-20 Hewlett-Packard Company Pre-locking scheme for allowing consistent and concurrent workflow process execution in a workflow management system
US6067548A (en) 1998-07-16 2000-05-23 E Guanxi, Inc. Dynamic organization model and management computing system and method therefor
US6279009B1 (en) 1998-12-04 2001-08-21 Impresse Corporation Dynamic creation of workflows from deterministic models of real world processes
US6278901B1 (en) 1998-12-18 2001-08-21 Impresse Corporation Methods for creating aggregate plans useful in manufacturing environments
US6308163B1 (en) 1999-03-16 2001-10-23 Hewlett-Packard Company System and method for enterprise workflow resource management
US6458080B1 (en) * 2000-05-31 2002-10-01 International Business Machines Corporation Managing parameters effecting the comprehensive health of a user

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5530861A (en) * 1991-08-26 1996-06-25 Hewlett-Packard Company Process enaction and tool integration via a task oriented paradigm
US5937388A (en) * 1996-12-05 1999-08-10 Hewlett-Packard Company System and method for performing scalable distribution of process flow activities in a distributed workflow management system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GEORGAKOPOULOS D ET AL: "AN OVERVIEW OF WORKFLOW MANAGEMENT: FROM PROCESS MODELING TO WORKFLOW AUTOMATION INFRASTRUCTURE" DISTRIBUTED AND PARALLEL DATABASES, KLUWER, NL, vol. 3, no. 2, April 1995 (1995-04), pages 119-153, XP001055255 ISSN: 0926-8782 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005259113A (en) * 2004-02-12 2005-09-22 Ricoh Co Ltd Process editing apparatus, process management apparatus, process editing program, process management program, recording medium, process editing method and process management method
WO2015145405A1 (en) * 2014-03-28 2015-10-01 Koninklijke Philips N.V. Smart phone based multi-patient worklist (spwl)
WO2016120527A1 (en) 2015-01-28 2016-08-04 Eränkö Timo System and method for communication in a telecommunication network
US10868740B2 (en) 2015-01-28 2020-12-15 Timo Eränkö Systems for feed-back communication in real-time in a telecommunication network

Also Published As

Publication number Publication date
US6714913B2 (en) 2004-03-30
WO2003021509A3 (en) 2004-01-22
CA2457962A1 (en) 2003-03-13
US20030045958A1 (en) 2003-03-06
JP2005502137A (en) 2005-01-20
EP1421528A2 (en) 2004-05-26

Similar Documents

Publication Publication Date Title
US6714913B2 (en) System and user interface for processing task schedule information
US20220044775A1 (en) Secure electronic information system, method and apparatus for associative data processing
US7813941B2 (en) Patient bed search system
US10192034B2 (en) System and method for clinical strategy for therapeutic pharmacies
US6363393B1 (en) Component based object-relational database infrastructure and user interface
CN102043931B (en) Private data access control method based on role permission dynamic conversion
JP2005507123A (en) A system for managing healthcare-related information that supports health care business activities
JP2003196399A (en) System for providing healthcare related information, method for providing user interface, and method for providing healthcare related information
JP2005518577A (en) Healthcare-related event information processing system used for task execution scheduling
US20090276246A1 (en) Automated Interdisciplinary Plan of Care Generation System
US20110276343A1 (en) Dynamic clinical worklist
Schmidt et al. Permutations of cooperative work practices: A study of two oncology clinics
US20220277000A1 (en) Dynamic Regrouping and Presentation of Electronic Patient Records
US20090217340A1 (en) Methods and systems for clinical context management via context injection into components and data
US20040102998A1 (en) System and method to support patient identifiers for imaging and information systems in health care enterprise
Blazin et al. Never enough time: mixed methods study identifies drivers of temporal demand that contribute to burnout among physicians who care for pediatric hematology-oncology patients
JP5397792B2 (en) Hospital information system and bed control display method
Patil et al. An architecture for a health care provider's workstation
WO2002052483A2 (en) System and method for integration of health care records, and for a seamless user interface, for an integrated electronic health care information system
Pangalos et al. Design of secure medical database systems
Esterhay Jr User metaphors for health care professional workstations
US20140324455A1 (en) Central control of distributed organizational structures
Gülçin Development of chemotherapy plan generation tool
Rutt Building blocks for distributed information systems in hospitals
US20080249805A1 (en) Smart clinical data clipboard

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): CA JP

Kind code of ref document: A2

Designated state(s): CA

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FR GB GR IE IT LU MC NL PT SE SK TR

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2002744744

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2457962

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2003525775

Country of ref document: JP

WWP Wipo information: published in national office

Ref document number: 2002744744

Country of ref document: EP