MODULARIZATION FOR PRESCRIPTION FULFILLMENT AND ADHERENCE

• US 20140156298A1
• Filed: 12/10/2013
• Published: 06/05/2014
• Est. Priority Date: 12/05/2012
• Status: Abandoned Application

• Current Assignee: Westrock mwv, llc (WestRock Company)
• Original Assignee: Meadwestvaco (WestRock Company)
• Inventors: CRAWFORD, Patricia, MAGLIONE, Mark, TOWLE, Justin, GRINNAN, Thomas R., EYERLY, Sandra J., THOMPSON, Frederick, SADLER, Kenneth G.
• Application Number:
  US14/101,997
• Publication Number:
  US 20140156298A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients

Abstract

A modular system for facilitating fulfillment and patient adherence for multiple prescriptions. Each module is an independently executing software widget configured to perform complementary tasks in a coordinated manner to achieve specific functions as described below. Including a system module to determine a patient customize drug regimen schedule, a module to identify potential side effects and drug interactions, and other modules useful to fulfill a patient order for multiple-medications.

Claims

1. A system implemented in a distributed computing environment, the system comprising:

a core module configured to;

receive a prescription order that covers one or more medications to be taken over a period of days and during one or more administration times, the prescription order comprising one or more prescriptions for a single patient, each prescription representative of a medication and including prescription data comprised of one or more prescriber instructions and one or more product identification codes;

determine a patient customized drug regimen (PCDR) schedule that assigns an administration time to each of the prescriptions in the prescription order over the period of days;

depending on a hold status, execute filling at least one of the prescriptions for the single patient; and

a synchronization module configured to;

receive one or more of patient profile information, information indicating at least one change to the prescription order, and medication anomaly information;

determine the hold status.

2. The system of claim 1, wherein the distributed computing environment is a cloud computing environment.

3. The system of claim 1, wherein determining the hold status is based at least in part on the received patient profile information.

4. The system of claim 1, wherein determining the hold status is based at least in part on the received information indicating changes to the prescription order.

5. The system of claim 4, wherein the received information indicating at least one change to the prescription order comprises a new prescription for the single patient.

6. The system of claim 1, wherein determining the hold status is based at least in part on the medication anomaly information.

7. The system of claim 1, wherein determining the hold status is based at least in part on compatibility between two or more medications.

8. The system of claim 1, wherein the hold status comprises a status level for the single patient.

9. The system of claim 1, wherein the hold status comprises a status level for a single medication.

10. The system of claim 1, wherein executing filling at least one of the prescriptions for the single patient comprises outputting data for manually filling the at least one of the prescriptions.

11. The system of claim 1, wherein executing filling at least one of the prescriptions for the single patient comprises communicating with at least one prescription filling apparatus.

12. The system of claim 1, wherein the synchronization module is further configured to automatically determine a production date to start the period of days.

13. The system of claim 1, further comprising a parser module configured to:

receive responses to patient profile questions;

extract PCDR-related information from the responses; and

send the PCDR-related information to the core module.

14. The system of claim 1, further comprising a patient adherence module configured to:

provide a plurality of patient profile questions;

receive responses to the plurality of patient profile questions;

identify medication issues from the responses; and

output updated patient profile information.

15. The system of claim 14, wherein identifying medication issues from the responses comprises recognizing a side effect.

16. The system of claim 14, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

17. The system of claim 14, wherein the patient adherence module is further configured to maintain at least one of a communication log, medication history table, indications table, a biometrics table, or a side effects table.

18. The system of claim 17, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

19. The system of claim 14, wherein the patient adherence module is further configured to determine the hold status based on at least one of an identified medical issue, potential medication incompatibility, or user input.

20. The system of claim 14, wherein the patient adherence module is further configured to initiate communications to obtain updated patient profile information.

21. The system of claim 20, wherein the communications are initiated periodically.

22. The system of claim 21, wherein the communications are initiated monthly.

23. The system of claim 14, wherein outputting updated patient profile information comprises outputting data to the synchronization module.

24. The system of claim 1, wherein the core module further comprises a tracking interface configured to bilaterally communicate scan data indicative of prescription fulfillment functions.

25. The system of claim 1, wherein the core module is further configured to bilaterally communicate with one or more databases.

26. The system of claim 1, wherein the core module is further configured to output medical records.

27. The system of claim 1, wherein the synchronization module is further configured to generate reports for at least one of adherence outcomes, monthly fill data, and exception data for multiple patients.

28. The system of claim 1, further comprising an inventory module configured to monitor medication availability.

29. A patient adherence module implemented in a distributed computing environment, the patient adherence module configured to:

provide a plurality of patient profile questions;

receive responses to the plurality of patient profile questions;

identify medication issues from the responses; and

output updated patient profile information.

30. The patient adherence module of claim 29, wherein identifying medication issues from the responses comprises recognizing a side effect.

31. The patient adherence module of claim 29, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

32. The patient adherence module of claim 29 wherein the patient adherence module is further configured to maintain at least one of a communication log, a biometrics table, or a side effects table.

33. The patient adherence module of claim 32, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

34. The patient adherence module of claim 29 wherein the patient adherence module is further configured to determine a hold status based on at least one of an identified medical issue or user input.

35. The patient adherence module of claim 29, wherein the patient adherence module is further configured to initiate communications to obtain updated patient profile information.

36. The patient adherence module of claim 35, wherein the communications are initiated periodically.

37. The patient adherence module of claim 36, wherein the communications are initiated monthly.

38. The patient adherence module of claim 29 wherein outputting updated patient profile information comprises outputting data to at least one database.

39. A method implemented on a computing system, the method comprising:

receiving a prescription order that covers one or more medications to be taken over a period of days and during one or more administration times, the prescription order comprising one or more prescriptions for a single patient, each prescription representative of a medication and including prescription data comprised of one or more prescriber instructions and one or more product identification codes;

receiving one or more of patient profile information, information indicating at least one change to the prescription order, and medication anomaly information;

determining a patient customized drug regimen (PCDR) schedule that assigns an administration time to each of the prescriptions in the prescription order over the period of days;

determining a hold status; and

depending on the hold status, executing filling at least one of the prescriptions for the single patient.

40. The method of claim 39, wherein the distributed computing environment is a cloud computing environment.

41. The method of claim 39, wherein determining the hold status is based at least in part on the received patient profile information.

42. The method of claim 39, wherein determining the hold status is based at least in part on the received information indicating changes to the prescription order.

43. The method of claim 42, wherein the received information indicating at least one change to the prescription order comprises a new prescription for the single patient.

44. The method of claim 39, wherein determining the hold status is based at least in part on the medication anomaly information.

45. The method of claim 39, wherein determining the hold status is based at least in part on compatibility between two or more medications.

46. The method of claim 39, wherein the hold status comprises a status level for the single patient.

47. The method of claim 39, wherein the hold status comprises a status level for a single medication.

48. The method of claim 39, wherein executing filling at least one of the prescriptions for the single patient comprises outputting data for manually filling the at least one of the prescriptions.

49. The method of claim 39, wherein executing filling at least one of the prescriptions for the single patient comprises communicating with a prescription filling apparatus.

50. The method of claim 39, further comprising automatically determining a production date to start the period of days.

51. The method of claim 39, further comprising bilaterally communicating to obtain scan data indicative of prescription fulfillment functions.

52. The method of claim 39, further comprising updating one or more databases.

53. The method of claim 39, further comprising outputting medical records.

54. The method of claim 39, further comprising generating reports for at least one of adherence outcomes, monthly fill data, and exception data for multiple patients.

55. The method of claim 39, further comprising monitoring medication availability.

56. A method implemented on a computing system, the method comprising:

providing a plurality of patient profile questions;

receiving responses to the plurality of patient profile questions;

identifying medication issues from the responses; and

outputting updated patient profile information.

57. The method of claim 56, wherein identifying medication issues from the responses comprises recognizing one of a medication side effect or a drug interaction.

58. The method of claim 56, wherein identifying medication issues from the responses comprises accessing a patient DNA profile.

59. The method of claim 56, further comprising maintaining at least one of a communication log, a biometrics table, or a side effects table.

60. The method of claim 59, wherein identifying medication issues from the responses comprises recognizing a side effect based on the side effects table.

61. The method of claim 56, further comprising determining a hold status based on at least one of an identified medical issue or user input.

62. The method of claim 56, further comprising initiating communications to obtain updated patient profile information.

63. The method of claim 62, wherein the communications are initiated periodically.

64. The method of claim 63, wherein the communications are initiated monthly.

65. The method of claim 56, wherein outputting updated patient profile information comprises outputting data to one or more databases.

66. A method implemented on a computing system, the method comprising:

providing a plurality of patient profile questions;

receiving responses to the plurality of patient profile questions;

identifying medication issues from the responses; and

collecting the medication issues in one or more log(s).

67. The method of claim 66 further comprising, analyzing the medication issues in the one or more log(s), determining when 10 or more patients taking the same medication are reporting one or more of the same medication issues, and identifying the medication issue as a new medication issue associated with the medication the 10 or more patients were taking

68. The method of claim 67 further comprising reporting the new medication issue as being associated with the medication the 10 or more patients were taking to one of an external database or an internal database.

69. The method of claim 66 further comprising, analyzing the medication issues in the one or more log(s), determining when 10 or more patients taking the two or more of the same medication(s) are reporting one or more of the same medication issues, and identifying the medication issue as a new medication issue associated with the two or more medication(s) the 10 or more patients were takingThe method of claim 69 further comprising reporting the new medication issue as being associate with the two or more medications the 10 or more patients were taking to one of an external database or an internal database.