IP Library Granted Patent US 12,469,037
Granted Patent B1
US 12,469,037 · App. 17/205,457 · Granted Nov 11, 2025

Computing device, method and computer program product for constructing a consolidated message

Inventors: Stacy Hopkins (Loganville, GA); James Donald Stillman (Worthington, OH)
Assignee: McKesson Corporation
G06Q30/016G06Q10/08G16H20/10G16H40/20G16H70/40
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 12,469,037
App. No.
17/205,457
Granted
Nov 11, 2025
Kind
B1
Abstract

A computing device, method and computer program product are provided to construct a consolidated message. In the context of a computing device, the computing device includes a communication interface configured to receive first information regarding a product from a request processor in response to an inquiry from a source. The computing device also includes processing circuitry configured to determine whether the product is supported by one or more operational services. In an instance in which the product is supported by one or more operational services, the processing circuitry is configured to obtain second information regarding the one or more operational services to construct the consolidated message having a predefined message format and containing both the first information and the second information. The communication interface is also configured to cause the consolidated message containing both the first information and the second information to be provided to the source of the inquiry.

Claims (36)

1 . A computing device of a service provider, the computing device configured to construct a consolidated message, the computing device comprising:

a communication interface configured to receive first information regarding prescription medication from a pharmacy benefit management (PBM) entity in response to a prescription benefit coverage inquiry from a prescriber; and

processing circuitry configured to:

determine whether the prescription medication is supported by one or more operational services provided in association with the prescription medication and provided by a non-dispensing pharmacy, different than a preferred pharmacy of a patient by accessing a listing or record defining prescription medications supported by one or more operational services;

in response to determining that the prescription medication is not supported by one or more operational services, construct the consolidated message containing the first information;

in response to determining that the prescription medication is supported by one or more operational services, obtain second information regarding the one or more operational services from a memory device or a database, wherein the one or more operational services comprises services associated with one or more of: (i) one or more discounts, (ii) supporting compliance with risk evaluation mitigation strategies (REMS), (iii) prior authorization requirements, (iv) drug delivery, (v) financial assistance, or (vi) education, wherein the second information comprises contact information of the non-dispensing pharmacy and details pertaining to the one or more operational services provided in association with the prescription medication; and

construct the consolidated message having a predefined message format and containing both the first information and the second information that have been received from different parties,

wherein the communication interface is also configured to cause the consolidated message to be provided to the prescriber for the prescription benefit coverage inquiry, wherein the consolidated message contains both the first information and the second information in an instance in which the prescription medication is supported by one or more operational services,

wherein the processing circuitry is configured to conserve processing resources and network resources including bandwidth expended to construct the consolidated message relative to the processing resources and network resources otherwise expended to separately provide the first and second information by supporting separate streams of messages between the prescriber or a customer of the prescription and: (i) the PBM entity to obtain the first information in conjunction with a purchase of the prescription medication and (ii) a provider of the operational services in order to identify relevant operational services and to then obtain the second information regarding the one or more operational services that support the prescription medication.

2 . A computing device according to claim 1 wherein the processing circuitry is configured to determine whether the prescription medication is supported by one or more operational services by accessing a table defining prescriptions medications supported by one or more operational services.

3 . A computing device according to claim 1 wherein the processing circuitry is configured to obtain second information by obtaining messaging associated with the prescription medication that is to be provided to the prescriber.

4 . A computing device according to claim 3 wherein the messaging identifies a point of contact to provide assistance with respect to the prescription medication.

5 . A computing device according to claim 1 wherein the first information comprises benefit information, wherein the processing circuitry is further configured to determine from the benefit information whether a benefit is government funded, wherein the processing circuitry is configured in a manner dependent upon the benefit not being government funded to determine whether the prescription medication is supported by one or more hub services that identify a discount available for the prescription medication, and wherein the processing circuitry is configured in a manner dependent upon the benefit being government funded to eliminate a determination as to whether the prescription medication is supported by one or more hub services that identify a discount available for the prescription medication.

6 . A method for constructing a consolidated message, the method comprising:

receiving first information regarding prescription medication from a pharmacy benefit management (PBM) entity in response to a prescription benefit coverage inquiry from a prescriber;

determining whether the prescription medication is supported by one or more operational services provided in association with the prescription medication and by a non-dispensing pharmacy, different than a preferred pharmacy of a patient, by accessing a listing or record defining prescription medications supported by one or more operational services;

in response to determining that the prescription medication is not supported by one or more operational services, constructing the consolidated message containing the first information;

in response to determining that the prescription medication is supported by one or more operational services, obtaining second information regarding the one or more operational services from a memory device or a database, wherein the one or more operational services comprises services associated with one or more of:

(i) one or more discounts, (ii) supporting compliance with risk evaluation mitigation strategies (REMS), (iii) prior authorization requirements, (iv) drug delivery, (v) financial assistance, or (vi) education, wherein the second information comprises contact information of the non-dispensing pharmacy and details pertaining to the one or more operational services provided in association with the prescription medication;

constructing the consolidated message having a predefined message format and containing both the first information and the second information that have been received from different parties; and

causing the consolidated message to be provided to the prescriber for the prescription benefit coverage inquiry, wherein the consolidated message contains both the first information and the second information in the instance in which the prescription medication is supported by one or more operational services,

wherein the method conserves processing resources and network resources including bandwidth expended to construct the consolidated message relative to the processing resources and network resources otherwise expended to separately provide the first and second information by supporting separate streams of messages between the prescriber or a customer of the prescription and: (i) the PBM entity to obtain the first information in conjunction with a purchase of the prescription medication and (ii) a provider of the operational services in order to identify relevant operational services and to then obtain the second information regarding the one or more operational services that support the prescription medication.

7 . A method according to claim 6 wherein determining whether the prescription medication is supported by one or more operational services comprises accessing a table defining prescription medications supported by one or more operational services.

8 . A method according to claim 6 wherein obtaining second information comprises obtaining messaging associated with the prescription medication that is to be provided to the prescriber.

9 . A method according to claim 8 wherein the messaging identifies a point of contact to provide assistance with respect to the prescription medication.

10 . A computer program product configured to construct a consolidated message, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions configured to:

receive first information regarding prescription medication from a pharmacy benefit management (PBM) entity in response to a prescription benefit coverage inquiry from a prescriber;

determine whether the prescription medication is supported by one or more operational services provided in association with the prescription medication and provided by a non-dispensing pharmacy, different than a preferred pharmacy of a patient, by accessing a listing or record defining prescription medications supported by one or more operational services;

in an instance in which the prescription medication is not supported by one or more operational services, construct the consolidated message containing the first information;

in an instance in which the prescription medication is supported by one or more operational services, obtain second information regarding the one or more operational services from a memory device or a database, wherein the one or more operational services comprises services associated with one or more of: (i) one or more discounts, (ii) supporting compliance with risk evaluation mitigation strategies (REMS), (iii) prior authorization requirements, (iv) drug delivery, (v) financial assistance, or (vi) education, wherein the second information comprises contact information of the non-dispensing pharmacy and details pertaining to the one or more operational services provided in association with the prescription medication;

construct the consolidated message having a predefined message format and containing both the first information and the second information that have been received from different parties; and

cause the consolidated message to be provided to the prescriber for the prescription benefit coverage inquiry, wherein the consolidated message contains both the first information and the second information in the instance in which the prescription medication is supported by one or more operational services,

wherein the computer program product is configured to conserve processing resources and network resources including bandwidth expended to construct the consolidated message relative to the processing resources and network resources otherwise expended to separately provide the first and second information by supporting separate streams of messages between the prescriber or a customer of the prescription and: (i) the PBM entity to obtain the first information in conjunction with a purchase of the prescription medication and (ii) a provider of the operational services in order to identify relevant operational services and to then obtain the second information regarding the one or more operational services that support the prescription medication.

11 . A computer program product according to claim 10 wherein the program code instructions configured to determine whether the prescription medication is supported by one or more operational services comprise program code instructions configured to access a table defining prescription medications supported by one or more operational services.

12 . A computer program product according to claim 10 wherein the program code instructions configured to obtain second information comprise program code instructions configured to obtain messaging associated with the prescription medication that is to be provided to the prescriber.

13 . A computer program product according to claim 12 wherein the messaging identifies a point of contact to provide assistance with respect to the prescription medication.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2021
From: HOPKINS, STACY; STILLMAN, JAMES DONALD
To: MCKESSON CORPORATION
Reel/Frame 055639/0156 →
References Cited (65)
US 6973435B1 · Sioufi et al. · 2005 [cited by applicant]
US 7769601B1 · Bleser et al. · 2010 [cited by applicant]
US 8219422B2 · Hallberg · 2012 [cited by applicant]
US 8660859B1 · Ansari et al. · 2014 [cited by applicant]
US 8781851B2 · Anderson et al. · 2014 [cited by applicant]
US 10438693B1 · Vandervoort et al. · 2019 [cited by applicant]
US 11610655B1 · Rubin · 2023 [cited by applicant]
US 11676692B1 · Arends · 2023 [cited by applicant]
US 20020143582A1 · Neuman et al. · 2002 [cited by applicant]
US 20030130868A1 · Coelho · 2003 [cited by applicant]
US 20040006490A1 · Gingrich et al. · 2004 [cited by applicant]
US 20040122712A1 · Hill, Sr. et al. · 2004 [cited by applicant]
US 20040172301A1 · Mihai et al. · 2004 [cited by applicant]
US 20050049746A1 · Rosenblum · 2005 [cited by applicant]
US 20050102192A1 · Gerrits et al. · 2005 [cited by applicant]
US 20060212318A1 · Dooley · 2006 [cited by applicant]
US 20060224414A1 · Astrup · 2006 [cited by examiner]
US 20060271402A1 · Rowe, III et al. · 2006 [cited by applicant]
US 20080275723A1 · Wiley et al. · 2008 [cited by applicant]
US 20090198520A1 · Piovanetti-Perez · 2009 [cited by applicant]
US 20120016687A1 · Dhavle et al. · 2012 [cited by applicant]
US 20120053955A1 · Martin · 2012 [cited by applicant]
US 20130096938A1 · Stueckemann · 2013 [cited by applicant]
US 20130179177A1 · Dhavle et al. · 2013 [cited by applicant]
US 20160055314A1 · Anderson et al. · 2016 [cited by applicant]
US 20160117472A1 · Padmani et al. · 2016 [cited by applicant]
US 20160188820A1 · Brown et al. · 2016 [cited by applicant]
US 20170098043A1 · Antony · 2017 [cited by examiner]
US 20170329921A1 · Willard et al. · 2017 [cited by applicant]
US 20180075215A1 · Loiacono · 2018 [cited by examiner]
US 20180075220A1 · Hill, Sr. · 2018 [cited by applicant]
US 20180293351A1 · Simons et al. · 2018 [cited by applicant]
US 20180293358A1 · Sooudi et al. · 2018 [cited by applicant]
US 20190333158A1 · Cedergreen · 2019 [cited by applicant]
US 20190385734A1 · Pinsonneault · 2019 [cited by applicant]
US 20200244605A1 · Nagaraja · 2020 [cited by examiner]
US 20210295970A1 · Lau et al. · 2021 [cited by applicant]
US 20220398667A1 · Cichy · 2022 [cited by applicant]
US 20230059605A1 · Sait · 2023 [cited by examiner]
US 20230268044A1 · Bothra · 2023 [cited by applicant]
CA 2495018C · 2013 [cited by applicant]
CA 2552056C · 2015 [cited by applicant]
CA 2900718A1 · 2016 [cited by applicant]
CA 2552057C · 2016 [cited by applicant]
WO WO2012009513A1 · 2012 [cited by applicant]
[cited by applicant]
U.S. Appl. No. 16/832,318, “Method, Apparatus, And Computer Program Product For Providing Estimated Prescription Costs”, unpublished (filed Mar. 27, 2020), (Stacy Hopkins, Inventor) (McKesson Corporation, Assignee). [cited by applicant]
U.S. Appl. No. 16/878,778, “Method, Apparatus, And Computer Program Product For Constructing An Updated Order Including Information From Different Sources”, unpublished (filed May 20, 2020), (Stacy Hopkins, Inventor) (M… [cited by applicant]
U.S. Appl. No. 17/201,020, “Method, Apparatus, And Computer Program Product For Constructing An Updated Order Verifying Compliance With Predefined Rule(s)”, Unpublished (filing date Mar. 15, 2021), (Stacy Hopkins, Inven… [cited by applicant]
U.S. Appl. No. 17/205,457, “Computing Device, Method And Computer Program Product For Constructing A Consolidated Message”, Unpublished (filing date Mar. 18, 2021), (Stacy Hopkins, Inventor), (McKesson Corporation, Assi… [cited by applicant]
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/878,778, dated Dec. 17, 2021, 29 pages, U.S. [cited by applicant]
Transaction Data Systems. “Computer-Rx Empowers Community Pharmacies with Digital Communications Solutions from Updox” PRNewsWire.com (Aug. 7, 2018). [cited by applicant]
U.S. Appl. No. 17/678,654, “Method, Apparatus, And Computer Program Product For Providing Synchronized Messaging”, Unpublished (filing date Feb. 23, 2022), (Stacy Hopkins, Inventor), (McKesson Corporation, Assignee). [cited by applicant]
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 16/878,778, dated May 3, 2022, 37 pages, U.S. [cited by applicant]
Bahga, Arshdeep, et al., “A Cloud-based Approach for Interoperable Electronic Health Records (EHRs),” in IEEE Journal of Biomedical and Health Informatics, Sep. 2013, pp. 894-906, vol. 17, No. 5, downloaded by the USPTO… [cited by applicant]
United States Patent and Trademark Office, Advisory Action received for U.S. Appl. No. 16/878,778, dated Sep. 23, 2022, 4 pages, U.S. [cited by applicant]
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 16/878,778, dated Dec. 6, 2022, 24 pages, U.S. [cited by applicant]
Klann, Jeffrey G., et al., “Supporting Multi-sourced Medication Information in i2b2”, AMIA Annual Symposium Proceeding, Nov. 5, 2015, pp. 747-755, PubMed ID: 26958210, PubMed Central ID: PMC4765563. [cited by applicant]
United States Patent and Trademark Office, Notice of Allowance received for U.S. Appl. No. 16/878,778, dated Apr. 21, 2023, 16 pages, U.A. [cited by applicant]
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/201,020, dated Dec. 21, 2023, 25 pages, U.S.A. [cited by applicant]
Wang, Guijun, et al., “Intelligent Aggregation of Purchase Orders in e-Procurement”, Proceedings of the 2005 Ninth IEEE International EDOC Enterprise Computing Conference, Sep. 19-23, 2005, Enschede, Netherlands, 10 pag… [cited by applicant]
United States Patent and Trademark Office, Notice of Allowance and Interview Summary received for U.S. Appl. No. 17/201,020, dated Jul. 11, 2024, 18 pages, U.S.A. [cited by applicant]
United States Patent & Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/678,654, dated Mar. 29, 2024, 31 pages, US. [cited by applicant]
United States Patent and Trademark Office, Final Office Action received for U.S. Appl. No. 17/678,654, dated Feb. 3, 2025, 26 pages, U.S.A. [cited by applicant]
United States Patent and Trademark Office, Non-Final Office Action received for U.S. Appl. No. 17/678,654, dated Jun. 11, 2025, 26 pages, U.S.A. [cited by applicant]