IP Library Granted Patent US 10,764,151
Granted Patent B1
US 10,764,151 · App. 13/826,137 · Granted Sep 1, 2020

Methodologies for workflow transitioning

Inventors: John David Russo (Boston, MA); Jermie Dennis Cullip (Philadelphia, PA); Paul William Reilly (Boston, MA)
Assignee: ALLSCRIPTS SOFTWARE, LLC
H04L41/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,764,151
App. No.
13/826,137
Granted
Sep 1, 2020
Kind
B1
Abstract

A method for transitioning workflow execution includes executing, at a workstation utilizing one or more hardware processors of the workstation, a first step of a multi-step workflow; determining, utilizing a workflow engine, that a next step of the multi-step workflow is not required to be executed at a set location, and further determining that the first subsequent step of the multi-step workflow that is required to be executed at a set location is required to be executed at a server; transitioning execution of the multi-step workflow to one or more servers; and executing, at one or more servers utilizing one or more hardware processors of the one or more servers, steps of the multi-step workflow up to and including the step of the multi-step workflow that was identified as being required to be executed at a server.

Claims (63)

1. A method for transitioning workflow execution comprising:

(a) setting, for one or more steps of a multi-step workflow, a must-run location to specify

(i) that the respective step is server-running and is required to be executed at a server, or

(ii) that the respective step is workstation-running and is required to be executed at a workstation,

(iii) wherein steps which do not have a set must-run location are flexible and can be run at a server or a workstation;

(b) executing, at a first workstation utilizing one or more hardware processors of the first workstation, a first step of the multi-step workflow;

(c) determining, utilizing a workflow engine,

(i) that a next step of the multi-step workflow does not have a set must-run location and thus is flexible and not required to be executed at a set location, and

(ii) that the first subsequent step of the multi-step workflow that does have a set must-run location and thus is required to be executed at a set location is set to be server-running and is thus required to be executed at a server;

(d) transitioning execution of the multi-step workflow to one or more servers, based at least partially on the determinations

(i) that a next step of the multi-step workflow does not have a set must-run location and thus is flexible and is not required to be executed at a set location, and

(ii) that the first subsequent step of the multi-step workflow that does have a set must-run location and thus is required to be executed at a set location is set to be server-running and thus is required to be executed at a server; and

(e) executing, at the one or more servers utilizing one or more hardware processors of the one or more servers, steps of the multi-step workflow up to and including the step of the multi-step workflow that was identified as being required to be executed at a server; and

(f) subsequently determining, utilizing the workflow engine, that another next step of the multi-step workflow does not have a set must-run location and thus is flexible and not required to be executed at a set location.

2. The method of claim 1 , wherein the first workstation is located at a first site and at least one of the one or more servers is located at a second site remote from the first site.

3. The method of claim 1 , wherein one of the steps of the multi-step workflow which is set to be workstation-running is a user interface activity.

4. The method of claim 1 , wherein the one or more servers is a single server.

5. The method of claim 1 , wherein the one or more servers comprises a plurality of servers.

6. The method of claim 1 , wherein the first workstation and at least one of the one or more servers are located at the same site.

7. A method for transitioning workflow execution comprising:

(a) setting, for one or more steps of a multi-step workflow, a must-run location to specify

(i) that the respective step is server-running and is required to be executed at a server, or

(ii) that the respective step is workstation-running and is required to be executed at a workstation,

(iii) wherein steps which do not have a set must-run location are flexible and can be run at a server or a workstation;

(b) executing, at a first workstation utilizing one or more hardware processors of the first workstation, a first step of the multi-step workflow;

(c) determining, utilizing a workflow engine,

(i) that a first certain number of steps of the multi-step workflow to be performed next are flexible and are not required to be executed at a set location, and

(ii) that the first number exceeds a certain length;

(d) transitioning execution of the multi-step workflow to one or more servers, based at least partially on the determinations

(i) that the first number of steps of the multi-step workflow to be performed next are flexible and are not required to be executed at a set location, and

(ii) that the first number exceeds the certain length; and

(e) executing, at the one or more servers utilizing one or more hardware processors of the one or more servers, steps of the multi-step workflow; and

(f) subsequently determining, utilizing the workflow engine, that another next step of the multi-step workflow does not have a set must-run location and thus is flexible and not required to be executed at a set location.

8. The method of claim 7 , wherein the workstation is located at a first site and at least one of the one or more servers is located at a second site remote from the first site.

9. The method of claim 7 , wherein one of the steps of the multi-step workflow which is set to be workstation-running is not a user interface activity.

10. The method of claim 7 , wherein the one or more servers is a single server.

11. The method of claim 7 , wherein the one or more servers comprises a plurality of servers.

12. The method of claim 7 , wherein the workstation and at least one of the one or more servers are located at the same site.

13. A method for transitioning workflow execution comprising:

(a) setting, for one or more steps of a multi-step workflow, a must-run location to specify

(i) that the respective step is server-running and is required to be executed at a server, or

(ii) that the respective step is workstation-running and is required to be executed at a workstation,

(iii) wherein steps which do not have a set must-run location are flexible and can be run at a server or a workstation,

(b) executing, at a workstation utilizing one or more hardware processors of the workstation, a first step of the multi-step workflow;

(c) determining, utilizing a workflow engine,

(i) that a next step of the multi-step workflow does not have a set must-run location and thus is flexible and not required to be executed at a set location, and

(ii) that a decision point prevents a determination as to where the first subsequent step of the multi-step workflow that has a set must-run location is required to be executed;

(d) based at least partially on the determinations

(i) that the next step of the multi-step workflow does not have a set must-run location and is thus not required to be executed at a set location, and

(ii) that a decision point prevents a determination as to where the first subsequent step of the multi-step workflow that has a set must-run location is required to be executed, not transitioning execution of the multi-step workflow;

(e) executing the multi-step workflow through the decision point;

(f) subsequently determining, utilizing the workflow engine,

(i) that another next step of the multi-step workflow does not have a set must-run location and thus is flexible and not required to be executed at a set location, and

(ii) that another first subsequent step of the multi-step workflow that does have a set must-run location and is thus required to be executed at a set location is set to be server-running and thus is required to be executed at a server;

(g) transitioning execution of the multi-step workflow to one or more servers, based on one or more of the determinations

(i) that the another next step of the multi-step workflow does not have a set must-run location and thus is not required to be executed at a set location, and

(ii) that the another first subsequent step of the multi-step workflow that does have a set must-run location and thus is required to be executed at a set location is set to be server-running and thus is required to be executed at a server; and

(h) executing, at the one or more servers utilizing one or more hardware processors of the one or more servers, steps of the multi-step workflow up to and including the another first subsequent step of the multi-step workflow that was identified as being required to be executed at a server.

14. The method of claim 13 , wherein the workstation is located at a first site and at least one of the one or more servers is located at a second site remote from the first site.

15. The method of claim 13 , wherein one of the steps of the multi-step workflow which is set to be workstation-running is not a user interface activity.

16. The method of claim 13 , wherein the one or more servers is a single server.

17. The method of claim 13 , wherein the one or more servers comprises a plurality of servers.

18. The method of claim 13 , wherein the workstation and at least one of the one or more servers are located at the same site.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2017
From: REILLY, PAUL WILLIAM
To: ALLSCRIPTS SOFTWARE, LLC
Reel/Frame 041325/0942 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2017
From: CULLIP, JERMIE DENNIS
To: ALLSCRIPTS SOFTWARE, LLC
Reel/Frame 041278/0831 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2016
From: ALLSCRIPTS HEATLHCARE, LLC
To: ALLSCRIPTS SOFTWARE, LLC
Reel/Frame 040474/0070 →
SECURITY AGREEMENT Recorded Sep 23, 2013
From: ALLSCRIPTS SOFTWARE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 031264/0084 →