US20020062230A1 - Message and program system supporting communication - Google Patents
Message and program system supporting communication Download PDFInfo
- Publication number
- US20020062230A1 US20020062230A1 US10/017,165 US1716501A US2002062230A1 US 20020062230 A1 US20020062230 A1 US 20020062230A1 US 1716501 A US1716501 A US 1716501A US 2002062230 A1 US2002062230 A1 US 2002062230A1
- Authority
- US
- United States
- Prior art keywords
- patient
- service
- arrow
- message
- flowchart
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT 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/60—ICT 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 operation of medical equipment or devices
- G16H40/67—ICT 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 operation of medical equipment or devices for remote operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H70/00—ICT specially adapted for the handling or processing of medical references
- G16H70/60—ICT specially adapted for the handling or processing of medical references relating to pathologies
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
Description
- This invention relates to a messaging communication method and program system supporting communication between patients and physicians, physician extenders including nurses, and the ordering of prescriptions, alternatively supporting communication between clients, service providers, service extenders including service assistants and the ordering of services.
- FIG. 1 depicts prior art human-computer interfaces capable of supporting messaging upon communications networks. One exemplary prior art computer system includes a
display screen 2 in anenclosure 4,audio speakers second enclosure 10 housing aremovable media drive 12. Keyboard 14 is interfaced viaphysical transport mechanism 16 to the computer.Selector device 18 is interfaced viaphysical transport mechanism 20 to the computer.Audio microphone 22 is interfaced viaphysical transport mechanism 24 to the computer. The computer system interfaces viaphysical transport mechanism 30 tonetwork 32. - Certain exemplary prior art handheld computer interfaces are often
single enclosures 40 incorporating a miniature display screen 42 withbuttons 44 and apointing device 46. Thecomputer enclosure 40 is often held in one hand, while thepointing device 46 is held with the other hand.Wireless communications port 48 can both transmit 50 signals and receive 38 signals transmitted bywireless transceiver interface 36, which interfaces tonetwork 32 viaphysical transport mechanism 34. Other exemplary uses of such devices include mountingenclosure 40 on a wrist- or arm-band, thus freeing one hand. - Other exemplary prior art computer systems include but are not limited to devices incorporating one or more audio speakers such as6 or 8, at least one
audio microphone 22, which may or may not possess adisplay screen 2, but often possess a miniature display screen 42 and oftenseveral buttons 44 orkeyboard 14. Cellular telephones, both hand held and vehicle-mounted, possessing all these features are readily available connecting to either local wireless networks or larger national and international networks, in some cases through orbitingsatellite transceivers 36, which useseparate carriers 34 to further interface to ground base stations which provide high bandwidth gateways to large Wide Area Networks (WANs), including the Internet and the World Wide Web. - These exemplary devices are often capable of receiving messages, such as e-mail and paging messages. Many of these exemplary devices are capable of audio exchanges in a fashion similar to a telephone with a telephone messaging center. Many of these exemplary devices may further support the loading and adding of programs to provide upgraded services and new service capabilities. Many of these systems possess the ability to retain such loaded or added programs after the power to the module has been turned off. Such devices have been used to further provide a communication avenue between patients and physicians, through email and paging-style messages. Paging a doctor with a short message such as “Water has broken” may give an adequate portrayal of some situations such as the imminence of labor in childbirth. However, such a messaging system could not adequately portray the circumstances regarding a potential breach birth.
- Traditional telephones have often been used to permit a physician and patient to communicate. However, there are problems with such devices. Telephones without answering or message centers require that both patient and physician be available at essentially the same time, which is often difficult to arrange. Telephones, even with messaging centers, still have problems. Often the stored messages are short in duration. Even when the messages may be quite long, patients do not tend to give concise, clear and complete verbal medical descriptions of exactly the relevant conditions needed to describe their medical condition. This leads to a situation of question and answers, often with the patient and/or doctor having to wait significant amounts of time between each “bounce” before there is enough information in front of the physician to respond with a consultation. Further, physicians must listen through their patients messages, often wasting time trying to sort through the words to determine the observed medical conditions. This is an inefficient use of the physicians' time.
- Email exchanges between patients and physicians can provide greater amounts of information. However, there is a tendency to waste both patient and doctor time for several reasons. First, patients do not tend to write concise, clear and complete medical descriptions of exactly the relevant conditions needed to describe their medical condition. This is understandable, most people are not trained enough at medicine to know what a physician will need to know. This again leads to question and answer situations, often with the patient and doctor having to wait significant amounts of time between each “bounce” before there is enough information in front of the physician to respond with a consultation. Further, physicians must read what their patients have written, often wasting time trying to sort through the words to determine the observed medical conditions. This is an inefficient use of the physicians' time.
- The devices mentioned above have also been used to further provide a communication avenue between clients and service providers for various kinds of service support, through email and paging-style messages. Brief messages such as “flat tire” may convey adequate information in some circumstances but would be fundamentally inadequate in situations based around mission critical technologies such as aircraft.
- Consider a commonly occurring scenario in the airline industry. A technician in an isolated location finds an intermittent failure in testing a system possessing electromechanical, fluidic and airfoil control components, by way of example. The determination of the proper course of action involves decisions regarding each of these areas of the aircraft's technologists, combined with an understanding of the reliability history of the system involved and the relevant government and airline regulations. Client such as the local airport technician need access to high level, integrated service provider responses.
- Traditional telephones have often been used to permit a service provider and client to communicate. However, there are problems with such devices. Telephones without answering or message centers require that both client and service provider be available at essentially the same time, which is often difficult to arrange or involve the clients waiting for extended periods of time “on hold”. Telephones, even with messaging centers, still have problems. Often the stored messages are short in duration. Even when the messages may be quite long, clients do not tend to give concise, clear and complete verbal service descriptions of exactly the relevant conditions needed to describe their service condition. This leads to a situation of question and answers, often with the client and/or doctor having to wait significant amounts of time between each “bounce” before there is enough information in front of the service provider to respond with a consultation. Also, the expertise of the service providers may vary greatly, making the omission of specific questions possible, limiting the utility of the direct contact. Further, service providers must listen through their clients messages, often wasting time trying to sort through the words to determine the observed service conditions. This is an inefficient use of the service providers' time.
- Email exchanges between clients and service providers can provide greater amounts of information. However, there is a tendency to waste both client and doctor time for several reasons. First, clients do not tend to write concise, clear and complete service descriptions of exactly the relevant conditions needed to describe their service condition. This is understandable, most people are not trained enough in the service area's technology to know what a service provider will need to know. This again leads to question and answer situations, often with the client and doctor having to wait significant amounts of time between each “bounce” before there is enough information in front of the service provider to respond with a consultation. Further, service providers must read what their clients have written, often wasting time trying to sort through the words to determine the observed service conditions. This is an inefficient use of the service providers' time.
- FIG. 2 depicts a generic prior art block of a messaging communications system supporting the online ordering of prescriptions by physicians interacting with pharmacies. Email and other messaging systems have been used to provide a limited form of automation for the placing of prescription orders with various pharmacies possessing online message capabilities.
Physician 100 interacts 102 with a physician-operatedcomputer 104, which may be a desktop, notebook, or handheld computer, possibly embedded in a cellular telephone. The physician operatedcomputer 104 sends a specialized message, a prescription ordering message, usingphysical transport mechanism 106 to anetwork 108, which is controlled and accessed 110 bynetwork server 112.Network server 112 accesses 114 medical databases andpatient database 116.Network server 112 then sends a specialized pharmaceutical order message to apharmacy computer 120 which is linked 118 to thesame network 110. - There is a central problem with such systems. The patient is not part of the interaction. The patient cannot choose whether to order the prescription. The patient cannot choose which pharmacy or where the pharmacy sends the prescription, or whether a traditional brick and mortar pharmacy is preferred. The patient cannot choose between different brands.
- One aspect of this invention embodies a method of messaging upon a network involving at least one physician, at least one patient and a workflow engine. Each physician operates a computer, which from time to time is capable of receiving and sending messages upon the network at a corresponding address on the network. Each patient operates a computer, which from time to time, is capable of receiving and sending messages upon the network at a corresponding address on the network. The workflow engine accesses the network for receiving and sending messages upon the network using at least one workflow engine address on the network. The method comprises using a first medical message wizard by the patient on the patient operated computer, a medical profiler process performed by the workflow engine and a second medical message wizard by the first physician on the physician operated computer at the first corresponding physician address.
- Using the first medical message wizard by the patient is further comprised of generating an educated query message and sending the educated query message to the medical profiler address. Performing the medical profiler process by the workflow engine is further comprised of receiving the educated query message at the medical profiler address; processing the received educated query message; generating a patient message log entry in a medical profile of the patient; generating a patient medical query message; sending the patient medical query message to a first physician with the corresponding physician address. Using the second medical message wizard by the first physician is further comprised of receiving the patient medical query message; processing the patient medical query message; generating a physician-viewable patient medical query message; and displaying a physician-viewable patient medical query message.
- This embodiment of the invention has several advantageous characteristics: It minimizes the need for extensive typing for the patient. It decreases the need for message “ping-pong” between patient and physician due to insufficient information in the patient's messages to the physician. It allows the physician to read in an optimized format, which minimizes the physician's reading time. In many cases, the physician will not need to poll a chart pool, because the medical profile will cover the required information. There is no need for phone tag with patients.
- A further aspect of this invention involves further embodiments of the first messaging wizard, medical profiler process and second messaging wizard. The second medical message wizard further comprises responding to the physician-viewable patient medical query message; generating a patient response message; sending the patient response message; and copying the patient response message with an appended physician billing data to the workflow engine. Responding to the physician-viewable patient medical query message creates a first-physician response. Generating a patient response message from the physician-viewable patient medical query message and the first-physician response. Sending the patient response message to the patient at the corresponding patient address.
- The medical profiler process further comprises: receiving the copied patient response message with the appended physician billing data; processing the received, copied patient response message with the appended physician billing data; generating a patient response log entry in the medical profile of the patient. Processing the received, copied patient response message with the appended physician billing data creates a processed, received, copied patient response message with the appended physician billing data. The generating a patient response log entry in the medical profile of the patient is from the processed, received, copied patient response message with the appended physician billing data.
- The first message wizard further comprises: receiving the patient response message; processing the received patient response message to create a processed, received patient response message; and displaying the processed, received patient response message.
- This aspect of the invention is advantageous for several reasons. It supports the physician responding to the optimized educated query of the patient. It supports the automated logging of physician responses with billing information at the workflow engine. It supports the patient receiving the physician's response.
- Further embodiments of this invention advantageously support the use of authentication keys insuring secure communications between patient and workflow engine, between patient and physician and between physician and workflow engine.
- Further embodiments of this invention advantageously support physician extenders, including nurses, physician assistants and administrators. Further embodiments of this invention advantageously support prescriptions involving, not only the physician, workflow engine and pharmacy, but also the patient. This is advantageous for several reasons. The patient takes part in the prescription-ordering interaction. The patient can choose whether to order the prescription. The patient can choose which pharmacy to purchase the prescription from. The patient can choose where the pharmacy sends the prescription. The patient can choose whether a traditional brick and mortar pharmacy is preferred. The patient can choose between different brands.
- Another aspect of this invention embodies a computer program residing on a computer readable medium accessible by the patient operated computer capable of receiving patient response messages and sending messages to a workflow engine. It includes code for receiving the patient response message with an embedded prescription; code for displaying the received patient response message; code for responding to the patient response message; code for sending the patient prescription message to the workflow engine. The code for responding to the patient response message further includes code for generating a patient prescription message from the embedded prescription.
- This aspect of the invention is advantageous for several reasons. The patient takes part in the prescription-ordering interaction. The patient can choose whether to order the prescription. The patient can choose which pharmacy to purchase the prescription from. The patient can choose where the pharmacy sends the prescription. The patient can choose whether a traditional brick and mortar pharmacy is preferred. The patient can choose between different brands.
- Another aspect of this invention embodies a method of messaging upon a network involving at least one service provider, at least one client and a service-flow engine. Each service provider operates a computer, which from time to time is capable of receiving and sending messages upon the network at a corresponding address on the network. Each client operates a computer, which from time to time, is capable of receiving and sending messages upon the network at a corresponding address on the network. The service-flow engine accesses the network for receiving and sending messages upon the network using at least one service-flow engine address on the network. The method comprises using a first service message interface by the client on the client operated computer, a service profiler process performed by the service-flow engine and a second service message interface by the first service provider on the service provider operated computer at the first corresponding service provider address.
- Using the first service message interface by the client is further comprised of generating an educated query message and sending the educated query message to the service profiler address. Performing the service profiler process by the service-flow engine is further comprised of receiving the educated query message at the service profiler address; processing the received educated query message; generating a client message log entry in a service profile of the client; generating a client service query message; sending the client service query message to a first service provider with the corresponding service provider address. Using the second service message interface by the first service provider is further comprised of receiving the client service query message; processing the client service query message; generating a service provider-viewable client service query message; and displaying a service provider-viewable client service query message. This embodiment of the invention has several advantageous characteristics: It minimizes the need for extensive typing for the client. It decreases the need for message “ping-pong” between client and service provider due to insufficient information in the client's messages to the service provider. It allows the service provider to read in an optimized format, which minimizes the service provider's reading time. In many cases, the service provider will not need to poll a chart pool, because the service profile will cover the required information. There is no need for phone tag with clients.
- A further aspect of this invention involves further embodiments of the first message interface, service profiler process and second message interface. The second service message interface further comprising responding to the service provider-viewable client service query message; generating a client response message; sending the client response message; and copying the client response message with an appended service provider billing data to the service-flow engine. Responding to the service provider-viewable client service query message creates a first-service provider response. Generating a client response message from the service provider-viewable client service query message and the first-service provider response. Sending the client response message to the client at the corresponding client address.
- The service profiler process further comprises: receiving the copied client response message with the appended service provider billing data; processing the received, copied client response message with the appended service provider billing data; generating a client response log entry in the service profile of the client. Processing the received, copied client response message with the appended service provider billing data creates a processed, received, copied client response message with the appended service provider billing data. The generating a client response log entry in the service profile of the client is from the processed, received, copied client response message with the appended service provider billing data.
- The first message interface further comprises: receiving the client response message; processing the received client response message to create a processed, received client response message; and displaying the processed, received client response message.
- This aspect of the invention is advantageous for several reasons. It supports the service provider responding to the optimized educated query of the client. It supports the automated logging of service provider responses with billing information at the service-flow engine. It supports the client receiving the service provider's response.
- Further embodiments of this invention advantageously support the use of authentication keys insuring secure communications between client and service-flow engine, between client and service provider and between service provider and service-flow engine.
- Further embodiments of this invention advantageously support service extenders, including service assistants, service provider assistants and administrators.
- Further embodiments of this invention advantageously supports service recommendations involving the service provider, service-flow engine and supplier, but also the client. This is advantageous for several reasons. The client takes part in the service recommendation-ordering interaction. The client can choose whether to order the service recommendation. The client can choose which supplier to purchase the service recommendation from. The client can choose where the supplier sends the service recommendation. The client can choose whether a traditional brick and mortar supplier is preferred. The client can choose between different brands.
- Another aspect of this invention embodies a computer program residing on a computer readable medium accessible by the client operated computer capable of receiving client response messages and sending messages to a service-flow engine. It includes code for receiving the client response message with an embedded service recommendation; code for displaying the received client response message; code for responding to the client response message; code for sending the client service recommendation message to the service-flow engine. The code for responding to the client response message further includes code for generating a client service recommendation message from the embedded service recommendation.
- This aspect of the invention is advantageous for several reasons. The client takes part in the service recommendation-ordering interaction. The client can choose whether to order the recommended service(s). The client can choose which supplier to purchase the recommended service(s) from. The client can choose where the supplier delivers the recommended service(s). The client can choose whether a traditional brick and mortar supplier is preferred. The client can choose between different brands.
- These and other advantages of the present invention will become apparent upon reading the following detailed descriptions and studying the various figures of the drawings.
- FIG. 1 depicts prior art human-computer interface capable of supporting messaging upon communications networks;
- FIG. 2 depicts a generic prior art block of a messaging communications system supporting the online ordering of prescriptions by physicians interacting with pharmacies;
- FIG. 3A depicts a flow diagram of an embodiment of the invention in accordance with certain embodiments;
- FIG. 3B depicts a more detailed flow diagram of an embodiment of the invention in accordance with certain embodiments;
- FIG. 4 depicts an interactive flow between a patient using a first messaging wizard, medical profiler performing a medical profiler process and physician using a second messaging wizard in accordance with an embodiment of the invention;
- FIG. 5 depicts a flowchart of operations supporting the generation and sending of an educated query by a patient using the first messaging wizard in accordance with embodiments supporting FIG. 4;
- FIG. 6 depicts a flowchart of operations supporting the reception, processing, logging of the educated query message from the patient, and the generation and sending of the patient medical query message to a physician by the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 4;
- FIG. 7 depicts a flowchart of operations supporting reception, processing and viewing the patient medical query message by the second message wizard for the physician in accordance with embodiments supporting FIG. 4;
- FIG. 8 depicts a flowchart of operations supporting reception, generation and sending a patient response message, as well as copying the patient response message with an appended physician billing data to the medical profiler address in accordance with embodiments supporting FIG. 4;
- FIG. 9 depicts a flowchart of operations supporting the reception, processing, logging the copied patient response message with an appended physician billing data by the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 4;
- FIG. 10 depicts a flowchart of operations supporting reception, processing and display of the patient response message using the first messaging wizard on the patient operated computer in accordance with embodiments supporting FIG. 4;
- FIG. 11 depicts a flowchart of further
details regarding operation 604, generation of an educated query message by the first messaging wizard in accordance with embodiments supporting FIG. 5; - FIG. 12 depicts a flowchart of further
details regarding operation 638, processing the educated query message using the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 6; - FIG. 13 depicts a flowchart of further
details regarding operation 642, generation of a patient medical query message by the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 6; - FIG. 14 depicts a flowchart of further
details regarding operation 678, processing the received patient medical query message by the second messaging wizard in accordance with embodiments supporting FIG. 7; - FIG. 15 depicts a flowchart of further
details regarding operation 722, copying the patient response message with appended physician billing data to the medical profiler by the second messaging wizard in accordance with embodiments supporting FIG. 8; - FIG. 16 depicts a flowchart of further
details regarding operation 748, processing the received, copied the patient response message with appended physician billing data using the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 9; - FIG. 17 depicts a flowchart of further
details regarding operation 708, generating patient response message using the second message wizard in accordance with embodiments supporting FIG. 8; - FIG. 18 depicts a flowchart of further
details regarding operation 778, processing the received patient response message using the first message wizard in accordance with embodiments supporting FIG. 10; - FIG. 19 depicts a flowchart of further
details regarding operation 712, sending the patient response message with appended physician billing data using the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 8; - FIG. 20 depicts a flowchart of further
details regarding operation 708, generating the patient response message using the second message wizard in accordance with embodiments supporting FIG. 8; - FIG. 21 depicts a flowchart of operations of the medical profiler process performed by the medical profiler in accordance with alternative embodiments supporting FIG. 4;
- FIG. 22 depicts a flowchart of further
details regarding operation 1048, processing the patient response message destined for the patient using the medical profiler process performed by the medical profiler in accordance with embodiments supporting FIG. 21; - FIG. 23 depicts a flowchart of further
details regarding operation 642, generating a patient medical query message using the medical profiler process performed by the medical profiler in accordance with embodiments; - FIG. 24 depicts a flowchart of operations using the third message wizard on the physician extender computer in accordance with embodiments supporting FIG. 9;
- FIG. 25 depicts a flowchart of further
details regarding operation 602, generating the physician-viewable patient medical query message in accordance with embodiments supporting FIGS. 7; - FIG. 26 depicts a flowchart of further
details regarding operation 708, generating the patient response message using the second message wizard in accordance with embodiments supporting FIG. 8; - FIG. 27 depicts a flowchart of further operations embodying the third message wizard in accordance with certain embodiments;
- FIG. 28 depicts a flowchart of further operations embodied in the message profiler process in accordance with certain embodiments;
- FIG. 29 depicts a flowchart of further operations embodied in a second messaging wizard in accordance with certain embodiments supporting prescriptions;
- FIG. 30 depicts a flowchart of further operations embodied in a medical profiler in accordance with certain embodiments supporting prescriptions;
- FIG. 30A depicts a flowchart of further
details regarding operation 1311, integrating a prescription order in the medical profiler process in accordance with embodiments supporting FIG. 30; - FIG. 31 depicts a flowchart of further operations embodied in the first messaging wizard in accordance with certain embodiments supporting prescriptions;
- FIG. 32 depicts a flowchart of further details of
operation 1352, ordering the embedded prescription of FIG. 31; - FIG. 33 depicts a flowchart of further details of
operation 1170 of FIG. 25; - FIG. 34 depicts a flowchart of further details of
operation 1222 of FIG. 27; - FIG. 35 depicts a flowchart of further details of
operation 1402 of FIG. 34; - FIG. 36 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments supporting billing patients;
- FIG. 37 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments further supporting billing patients;
- FIG. 38 depicts a flowchart of further operations embodying a billing process in accordance with certain embodiments;
- FIG. 39 depicts a flowchart of further details of
operation 1518 of FIG. 38; - FIG. 40 depicts a flowchart of further details of
operation 708 of FIG. 8 supporting a physician requesting a second opinion in accordance with certain embodiments; - FIG. 41 depicts a flowchart of operations embodied in the second message wizard supporting a second physician and a second opinion request in accordance with certain embodiments;
- FIG. 42 depicts a flowchart of operations embodied in a second message wizard supporting maintaining a collection of patient response templates in accordance with certain embodiments;
- FIG. 43 depicts a flowchart of further details of
operation 704 of FIG. 8 supporting use of a patient response template to create a first-physician response in accordance with certain embodiments; - FIG. 44 depicts a flowchart of operations embodied in a first messaging wizard to support maintaining a collection of patient problem templates in accordance with certain embodiments;
- FIG. 45 depicts a flowchart of further details of
operation 604 of FIG. 5 supporting use of a patient problem template to create an educated medical query using a first medical wizard in accordance with certain embodiments; - FIG. 46 depicts a flowchart of operations embodied in a medical profiler process to generate and send patient problem templates to patients in accordance with certain embodiments;
- FIG. 47 depicts a flow diagram of a medical profiler process in accordance with certain embodiments;
- FIG. 48 depicts a flow diagram of a computer program capable of receiving a message from a physician containing a prescription and responding to the message containing the prescription by generating and sending a prescription order message in accordance with certain embodiments in accordance with an aspect of the invention;
- FIG. 49 depicts a flowchart of further details of the code of1854 of FIG. 48 supporting receiving a patient response message with an embedded prescription in accordance with certain embodiments; and
- FIG. 50 depicts a flowchart of further details of the code of1862 of FIG. 48 supporting responding to the patient response message in accordance with certain embodiments.
- FIG. 50A depicts a flowchart of further details of1311 of FIG. 30 supporting integrating a prescription order in accordance with certain embodiments;
- FIG. 50B depicts a flowchart of further details of1324 of FIG. 30A supporting generating a pharmacy prescription order in accordance with certain embodiments;
- FIG. 50C depicts a flowchart of further details of1326 of FIG. 30A supporting sending a pharmacy prescription order to a pharmacy in accordance with certain embodiments;
- FIG. 50D depicts a flowchart of further details of1106 of FIG. 23 supporting determining a routing chain of physician extenders and embedding the routing chain into a second patient query in accordance with certain embodiments;
- FIG. 50E depicts a flowchart of further details of1178 of FIG. 24 supporting determining successor physician extenders in an embedded physician extender routing chain, generating a successor medical query message with embedded proposed patient response and sending the successor patient medical query to the successor physician extender;
- FIG. 50F depicts a flowchart of further details of646 of FIG. 6 supporting generating a routing tree of physicians with first physician final destination and source list of physicians, generating and sending a source medical query to each physician included in the physician source list;
- FIG. 51 depicts a more detailed flow diagram of an embodiment of the invention in accordance with certain embodiments;
- FIG. 52 depicts an interactive flow between a client using a first message interface, service profiler performing a service profiler process and service provider using a second message interface in accordance with an embodiment of the invention;
- FIG. 52A depicts an interactive flow between a client using a first message interface, service profiler performing a service profiler process and service provider using a second message interface in accordance with a further embodiment of the invention;
- FIG. 53 depicts a flowchart of operations supporting the generation and sending of an educated query by a client using the first message interface in accordance with embodiments supporting FIG. 52;
- FIG. 54 depicts a flowchart of operations supporting the reception, processing, logging of the educated query message from the client, and the generation and sending of the client service query message to a service provider by the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 52;
- FIG. 55 depicts a flowchart of operations supporting reception, processing and viewing the client service query message by the second message interface for the service provider in accordance with embodiments supporting FIG. 52;
- FIG. 56 depicts a flowchart of operations supporting reception, generation and sending a client response message, as well as copying the client response message with an appended service provider billing data to the service profiler address in accordance with embodiments supporting FIG. 52;
- FIG. 57 depicts a flowchart of operations supporting the reception, processing, logging the copied client response message with an appended service provider billing data by the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 52;
- FIG. 58 depicts a flowchart of operations supporting reception, processing and display of the client response message using the first message interface on the client operated computer in accordance with embodiments supporting FIG. 52;
- FIG. 59 depicts a flowchart of further
details regarding operation 2604, generation of an educated query message by the first message interface in accordance with embodiments supporting FIG. 53; - FIG. 60 depicts a flowchart of further
details regarding operation 2638, processing the educated query message using the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 54; - FIG. 61 depicts a flowchart of further
details regarding operation 2642, generation of a client service query message by the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 54; - FIG. 62 depicts a flowchart of further
details regarding operation 2678, processing the received client service query message by the second message interface in accordance with embodiments supporting FIG. 55; - FIG. 63 depicts a flowchart of further
details regarding operation 2722, copying the client response message with appended service provider billing data to the service profiler by the second message interface in accordance with embodiments supporting FIG. 56; - FIG. 64 depicts a flowchart of further
details regarding operation 2748, processing the received, copied the client response message with appended service provider billing data using the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 57; - FIG. 65 depicts a flowchart of further
details regarding operation 2708, generating client response message using the second message interface in accordance with embodiments supporting FIG. 56; - FIG. 66 depicts a flowchart of further
details regarding operation 2778, processing the received client response message using the first message interface in accordance with embodiments supporting FIG. 58; - FIG. 67 depicts a flowchart of further
details regarding operation 2712, sending the client response message with appended service provider billing data using the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 56; - FIG. 68 depicts a flowchart of further
details regarding operation 2708, generating the client response message using the second message interface in accordance with embodiments supporting FIG. 56; - FIG. 69 depicts a flowchart of operations of the service profiler process performed by the service profiler in accordance with alternative embodiments supporting FIG. 52;
- FIG. 70 depicts a flowchart of further
details regarding operation 3048, processing the client response message destined for the client using the service profiler process performed by the service profiler in accordance with embodiments supporting FIG. 69; - FIG. 71 depicts a flowchart of further
details regarding operation 2642, generating a client service query message using the service profiler process performed by the service profiler in accordance with embodiments; - FIG. 72 depicts a flowchart of operations using the third message interface on the service extender computer in accordance with embodiments supporting FIG. 57;
- FIG. 73 depicts a flowchart of further
details regarding operation 2602, generating the service-provider-viewable client service query message in accordance with embodiments supporting FIGS. 55; - FIG. 74 depicts a flowchart of further
details regarding operation 2708, generating the client response message using the second message interface in accordance with embodiments supporting FIG. 56; - FIG. 75 depicts a flowchart of further operations embodying the third message interface in accordance with certain embodiments;
- FIG. 76 depicts a flowchart of further operations embodied in the message profiler process in accordance with certain embodiments;
- FIG. 77 depicts a flowchart of further operations embodied in a second message interface in accordance with certain embodiments supporting service recommendations;
- FIG. 78 depicts a flowchart of further operations embodied in a service profiler in accordance with certain embodiments supporting service recommendations;
- FIG. 78A depicts a flowchart of further
details regarding operation 3311, integrating a service order in the service profiler process in accordance with embodiments supporting FIG. 78; - FIG. 79 depicts a flowchart of further operations embodied in the first message interface in accordance with certain embodiments supporting service recommendations;
- FIG. 80 depicts a flowchart of further details of
operation 3352, ordering the embedded service recommendation of FIG. 79; - FIG. 81 depicts a flowchart of further details of
operation 3170 of FIG. 73; - FIG. 82 depicts a flowchart of further details of
operation 3222 of FIG. 75; - FIG. 83 depicts a flowchart of further details of
operation 3402 of FIG. 82; - FIG. 84 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments supporting billing clients;
- FIG. 85 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments further supporting billing clients;
- FIG. 86 depicts a flowchart of further operations embodying a billing process in accordance with certain embodiments;
- FIG. 87 depicts a flowchart of further details of
operation 3518 of FIG. 86; - FIG. 88 depicts a flowchart of further details of
operation 2704 of FIG. 56 supporting a service provider requesting a second opinion in accordance with certain embodiments; - FIG. 89 depicts a flowchart of operations embodied in the second message interface supporting a second service provider and a second opinion request in accordance with certain embodiments;
- FIG. 90 depicts a flowchart of operations embodied in a second message interface supporting maintaining a collection of client response templates in accordance with certain embodiments;
- FIG. 91 depicts a flowchart of further details of
operation 2704 of FIG. 56 supporting use of a client response template to create a first-service-provider response in accordance with certain embodiments; - FIG. 92 depicts a flowchart of operations embodied in a first message interface to support maintaining a collection of client problem templates in accordance with certain embodiments;
- FIG. 93 depicts a flowchart of further details of
operation 2604 of FIG. 53 supporting use of a client problem template to create an educated service query using a first service interface in accordance with certain embodiments; - FIG. 94 depicts a flowchart of operations embodied in a service profiler process to generate and send client problem templates to clients in accordance with certain embodiments;
- FIG. 95 depicts a flow diagram of a service profiler process in accordance with certain embodiments;
- FIG. 96 depicts a flow diagram of a computer program capable of receiving a message from a service provider containing a service recommendation and responding to the message containing the service recommendation by generating and sending a service order message in accordance with certain embodiments in accordance with an aspect of the invention;
- FIG. 97 depicts a flowchart of further details of the code of3854 of FIG. 96 supporting receiving a client response message with an embedded service recommendation in accordance with certain embodiments; and
- FIG. 98 depicts a flowchart of further details of the code of3862 of FIG. 96 supporting responding to the client response message in accordance with certain embodiments.
- FIG. 98A depicts a flowchart of further details of3311 of FIG. 78 supporting integrating a service order in accordance with certain embodiments;
- FIG. 98B depicts a flowchart of further details of3324 of FIG. 78A supporting generating a supplier service order in accordance with certain embodiments;
- FIG. 98C depicts a flowchart of further details of3326 of FIG. 78A supporting sending a supplier service order to a supplier in accordance with certain embodiments;
- FIG. 98D depicts a flowchart of further details of3106 of FIG. 71 supporting determining a routing chain of service extenders and embedding the routing chain into a second client query in accordance with certain embodiments;
- FIG. 98E depicts a flowchart of further details of3178 of FIG. 72 supporting determining successor service extenders in an embedded service extender routing chain, generating a successor medical query message with embedded proposed client response and sending the successor client medical query to the successor service extender;
- FIG. 98F depicts a flowchart of further details of2646 of FIG. 53 supporting generating a routing tree of service providers with first service provider final destination and source list of service providers, generating and sending a source medical query to each service provider included in the service provider source list;
- FIG. 1 and2 refer to prior art and were previously discussed in the Background of the invention.
- Discussion of Primary Terms as used herein:
- A message will refer to a communication session with a source and a destination whose contents can be described in a digital fashion. Examples of messages include but are not limited to phone mail, email and pager messages.
- A medical profile of a patient is a collection of information residing in some computer accessible media which from time to time a computer may be able to access.
- The medical profiler process is the system-wide activities which are performed in an automated fashion by the workflow engine to facilitate the medical communication between patients, physicians, physician extenders and pharmacies to support at least the following: medical queries, replies and transactions involved in prescriptions.
- The workflow engine is the mechanism performing the collection of operations known as the medical profiler process. It has at least one address on the network shared with patients, physicians, physician extenders and pharmacies. Note that this shared network may in fact be partitioned into a collection of networks, each possessing gateways, firewalls and the like as is well known in the art. Note that the workflow engine may include but is not limited to one computer, and in fact, in certain embodiments preferably involves more than one server computer as will be discussed later.
- A patient as used herein will have two components of meaning: the first component being the entity about whose health the medical profile, query messages, response message and prescriptions are directed; the second is the responsible adult acting for the patient in all the transactions, such as generating the query messages, receiving and considering the response messages and ordering the prescriptions. Note that a list of the first component entities includes but is not limited to pets, trees, children, the physically incapacitated, the mentally incapacitated and the emotionally incapacitated.
- FIG. 3A depicts a flow diagram of an embodiment of the invention in accordance with certain embodiments. There are two main flows of information likely to be prevalent with users of this invention. The most common flow would be a patient200 initiate 202
query 204, where the patient will launch anelectronic message 206. These messages can subcategorized in four main groups- Request a refill, Schedule an appointment, Consult symptoms with thephysician 212 and page thephysician 212. The second possible flow is initiation of messages by the clinic/physician 212 aimed at broadcasting information topatients 200. - At the time of registration or post sending the first consultation/refill request the
patient 200 is being asked to fill in his/hermedical profile 208.Medical profile 208 would contain the patient 200's medication list, allergies, problems and demographics. Themedical profile 208 is then validated by the patient 200's medical staff and is approved. Once approved themedical profile 208 is locked and thepatient 200 may not alter the profile. Theprofile 208 is updated automatically by transactions made by the workflow engine or by the patient's medical staff. In the event that thepatient 200 wants to edit themedical profile 208 then the patient initiates aquery 204 to the medical staff informing them that the profile needs corrections. The medical staff can with one click approve thepatient query 204 and update theprofile 208. - FIG. 3A portrays the typical flow of a
patient 200 initiatedquery 204. Thepatient 200 through the use of awizard 202, initiates aneducated query 204. Using a problem-related database and knowledge of the patientmedical profile 208, the application generates a problem specific questioner (form). This form is both problem andpatient 200 specific. The form is advantageous in that it removes the need for a great deal of typing on behalf of thepatient 200. It is further advantageous in decreasing the need for message ping pong between the patient 200 and thephysician 212 due to insufficient data. It is further advantageous in allowing thephysician 212 to read a more readable and intelligent format than that of apatient 200 free text waffle. - The next step in the flow of the message is attaching the summary of the patient medical record or as we call it ‘medical profile’208 to the message. The
patient 200 initiates the medical profile at the point of registration to the workflow engine or at the time of the first refill/consult request. Thepatient 200 is asked by the workflow engine to fill in his/her medical profile i.e. problems allergies and medications. Thismedical profile 208 is interactive and will be later validated by thenurse 242 orphysician 212. Once validated for the first time it is locked and thepatient 200 can no longer tamper with the data. Anyprescription 252 sent through the workflow engine automatically updates themedical profile 208. Thepatient 200 may add data to the ‘locked’medical profile 208 but that data will not be embedded in themedical profile 208 prior to thephysician 212 or his staff validating the new data. The workflow engine attaches themedical profile 208 to any patient related document thus avoids the need for a chart pull at the point of care, plus it allows thepatient 200 to present themedical profile 208 toforeign physicians 212 when on the move. - The workflow engine then takes the message and the
medical profile 208 attached and routes it to the proper physician extender according to the type of message sent. As an example, a refill messages would be routed to thenurse 242, an urgent scheduling query will also get to thenurse 242, a non-urgent query will be routed to the scheduling desk. This process allows thephysician 212 to share the workload with his extenders. - Each member of the physician's staff can create his own canned replies246. These are replies that were typed once by the staff were saved and may be pasted with two clicks to message bodies of future replies. With many physicians complaining about repetitious replies to their patients this tool allows both the saving of time and a reduction in typing need. The pasted ‘canned replies’ are then editable and customizable.
- Once edited and filled by the medical staff the messages are routed to the
physician 212 who in most cases needs to do nothing more then approve his staff's work and in a single click send the message to thepatient 200. Thephysician 212 at this stage may determine a fee for the service and addeducational material 220 and pointers (from a library) to sites of further patient education. The workflow engine notifies thepatient 200 via regular e-mail (patient@ aol.com) that a message is waiting for him in his Healinx inbox and provides an hyperlink to lead thepatient 200 to his Healinx inbox. - The physician/physician extender may also prescribe medication and attach it to the outgoing message, this in turn checks the medication using a licensed database against the patient's medical profile for drug/drug, drug/allergy conflicts and alerts the physician. It also allows us to attach education material to the prescription alerting the
patient 200 for possible side effects and actions that should or should not be taken with the prescribed medication.Education material 220 taken from the database is attached to the prescription and can be viewed by thepatient 200. - The
patient 200 reading the message views the embedded prescription and has the choice of ordering 264 the prescription in the pharmacy of his choice to be delivered from anonline pharmacy 260 or to be picked up from his favorite brick and mortartraditional pharmacy 260. In addition in the event that thepatient 200 is on the move then he may choose with a single click theclosest pharmacy 260 and the prescription will be electronically shipped to thatpharmacy 260 at no extra cost or hassle. -
Physicians 212 may set the workflow engine to allowpatient 200 paging, themessage 204 typed by thepatient 200 will be sent to thephysician 212 over 20 pager or phone. Thephysician 212 can then request 214 additional information such as the patient medical profile and initiate a call back 216 to thepatient 200. Thephysician 212 may set up the times of day he willing to be accessible by pager and the pricing per beep dependant on the time of day. - Further embodiments of the invention support the workflow engine creating routing chains of physician extenders starting with a first physician extender proceeding through successor physician extenders until the routing chain terminates with a physician reviewing the collective proposed patient response. The routing chain may be generated by the workflow engine based upon the patient's educated query message.
- Further embodiments of the invention support the workflow engine creating routing trees of physicians with patent query messages starting with a source list of physicians, possibly routing to intermediate physicians and culminating in a first physician who reviews the collective physician responses to their respective patient medical queries.
- Using outsourced solutions, the
patients 200 can monitor their readings of blood pressure, sugar level, or other monitoring and transmit it to Healinx. We then take the readings and imbed these in the patientmedical profile 208. If abnormal readings are found bothpatient 200 andphysician 212 are notified. Through an embedded database and the patient'smedical profile 208 the workflow engine searches forpatient 200 as to who should schedule a preventive examination. As an example the workflow engine would remind all women 25-45 to schedule a mammogram. The workflow engine will hold a customized preventive health calendar perpatient 200 and remind thatpatient 200 to schedule an appointment if needed. - Through the
medical profile 208 ofpatient 200's the workflow engine will allow clinics to search for certain patient characteristics. Using this filter the clinic can rapidly create variable patient mailing lists to which they can mail at once. - For example in the event that the clinic seeks to contact all males aged 25-45 who are smokers that take Prozac.
- Further embodiments of the invention include the capability for a vendor to author templates and routing them through an authoring tool. Templates would be descriptions of the most common customer queries. The templates would support the customer diagnostics of the problem and allow the customer to provide a comprehensive description of the problem encountered.
- The customer can then be provided with the most common solutions to the diagnosis. And allow the client to choose whether the off-the-shelf reply is adequate or not. If not then the customer may send the query to the vendor. For premium pricing the customer may page and get an immediate phone response.
- Identifying the template used allows triage of the mail into the most adequate department for reply. This allows the people in charge of replying to customize their replies and paste these in the message body. The message according to its severity can then be sent to a supervisor for approval or directly to the
patient 200. - The vendor may attach a prescription (the spare part needed) and allow the
patient 200 to choose the most convenient service center. The order is then sent to a service center of the customer's 200 choice and authorization and pricing of the entire service are controlled by the vendor. - FIG. 3B depicts a flow diagram of an embodiment of the invention in accordance with certain embodiments.
Patient 200 is the primary initiator of this invention.Arrow 202 depicts the interactions ofpatient 200 to create the educatedquery message 204. The educatedquery message 204 is an optimized medical query directed by the patient to address concerns and conditions involving the patient.Arrow 206 depicts the sending of educatedquery message 204 to themedical profile 208 which is managed by the medical profiler process. The workflow engine performs the various medical profiler process operations. More will be said about the workflow engine shortly.Arrow 210 depicts interactive communication between theworkflow engine 208 and thephysicians 212 primarily regarding the medical profiler.Physicians 212 are the central destination of patient generated educated medical query messages as sent by 210 from the medical profiler process to thephysician 212.Arrow 214 depicts the response ofphysician 212 to the educated query message, generating aconsultative response 216.Consultation 216 provides the basis of thepatient response message 226.Arrow 218 depicts the inclusion of the physicianconsultative response 216 witheducational material 220.Educational material 220 is included in certain, but not all cases, to meet mandated regulations as well as provide the physicians a mechanism to distribute standard material regarding various conditions and treatments.Arrow 222 depicts the workflow engine activities required to incorporate the consultative response and includedmaterials 220 with billing information (charging) 224. Charging 224 performs tasks of notifying a patient medical profile of the consultative transaction, what was the query, response, educational materials included and the medical service expenses.Arrow 226 depicts the actual patent response message derived from 224 query, physician response, educational materials included and the medical service expenses sent topatient 200. -
Arrow 230 depicts the message information flow from the workflow engine tophysician extender 232.Physician extenders 232 perform a number of medical service tasks under the direction ofphysicians 212.Arrow 234 depicts the sending of proposed patient response messages generated byphysician extenders 232 to aphysician 212.Arrow 240 depicts another message information flow from the workflow engine to anurse 242. While nurses are physician extenders, anurse 242 performs a specific additional task distinguishing them from other physician extenders, such as physician assistants and administrators. Nurse 242 can propose prescription refills for example.Arrow 244 depicts the sending of proposed patient response message, which may further include proposed embedded prescription refills, fromnurse 242 tophysician 246. -
Physician 212 performs a review on the proposed patient response messages from physician extenders, including nurses, as delivered byarrows Arrow 248 depicts the interaction between template replies 246 andphysician 212. -
Arrow 250 depicts the information and activity flow based upon theconsultative response 216 and the placing of aprescription message 252.Prescription message 252 is created based upon the physician'sconsultative response 216, which in turn is based upon the patient's medical query message and possibly a nurse's proposed prescription refill.Arrow 254 depicts sending aprescription message 252 to orderingprocess 256.Patient 200 receives thepatent response message 226, and may respond by ordering the embedded prescription, which is depicted byarrow 264 indicating a patient prescription message sent toordering process 256.Ordering process 256 waits until both thephysician prescription message 254 andpatient prescription message 264 have been received and processed before theorder 258 is actually placed withpharmacy 260.Pharmacy 260 sends the prescription topatient 300 as indicated byarrow 362. - FIG. 4 depicts an interactive flow between a patient using a first messaging wizard, workflow engine performing a medical profiler process and physician using a second messaging wizard in accordance with an embodiment of the invention.
Patient 300 interacts 302 with patient operatedcomputer 304, which can access 306 and perform the operations offirst messaging wizard 308.Physician 350 interacts 352 with physician operatedcomputer 354, which can access 356 and perform the operations ofsecond messaging wizard 358.Physician extender 400 interacts 402 with physician extender operatedcomputer 404, which can access 406 and perform the operations of second messaging wizard 408. -
Patient 300 usingfirst messaging wizard 308 on patient operatedcomputer 304 generates 310 educatedquery message 312 and sends it 314 toworkflow engine 320 where it is received bymedical profiler process 322.Medical profiler process 322 generates 324 patientmessage log entry 326, which is added 328 to the patient medical profile 330.Medical profiler process 322 further generates 340 patientmedical query message 342, which is sent 344 to physician operatedcomputer 354. -
Physician 350 usingsecond messaging wizard 358 on physician operatedcomputer 354 receives and responds to the patientmedical query message 342, generating 360 apatient response message 362, which in certain embodiments is sent 364 directly to the patient operatedcomputer 304. In certain alternative embodiments,patient response message 362 is sent 370 to the workflow engine, where themedical profiler process 322 then sends 372 a version to the patient operatedcomputer 304.Physician 350 usingsecond messaging wizard 358 on physician operatedcomputer 354 further responds to the patientmedical query message 342, generating a patient response message with appendedphysician billing data 382, which is sent 384 to to the workflow engine, where themedical profiler process 322 then generates 390 a patientresponse log entry 392 which is added 394 to the patient medical profile 330. - In certain situations, a prescription is embedded into
patient response message 362 by thephysician 350 usingsecond messaging wizard 358 on physician operatedcomputer 354 in response to the patientmedical query message 342, which embedded into thepatient response message 362.Physician 350 usingsecond messaging wizard 358 on physician operatedcomputer 354 also generates 480physician prescription message 482, which is sent 484 to the workflow engine using themedical profiler process 322.Patient 300 usingfirst messaging wizard 308 on patient operatedcomputer 304 generates 490 patientprescription order message 492 and sends it 494 toworkflow engine 320 where it is received bymedical profiler process 322. Once bothphysician prescription message 482 and patientprescription order message 492 have been received and authenticated, themedial profiler process 322 generates 500 a pharmacyprescription order message 502 which is sent 504 to thepharmacy computer 506. -
Medical profiler process 322 accesses 510 the patient medical profile 330 to generate 512 patientbilling report message 514 which is sent 516 tobilling system 518. Note that thebilling system 518 in certain embodiments is a separate system element external to the workflow engine. In certain alternative embodiments,billing system 518 resides within the operations performed by the workflow engine. In certain further embodiments,billing system 518 is part of the medical profiler process. -
Medical profiler process 322 further generates 400 a second patientmedical query message 402, which is sent 404 to physician extender operatedcomputer 414.Physician extender 410 usingthird messaging wizard 418 on physician operatedcomputer 414 receives and responds to the second patientmedical query message 412, generating 430 a proposed patient response message 432, which is sent 434 directly to the physician operatedcomputer 354, where it is inserted into the patientmedical query message 342. In certain alternative embodiments, patient response message 432 is sent 436 to the workflow engine, where themedical profiler process 322 then sends a version to the physician operatedcomputer 354.Physician extender 410 usingthird messaging wizard 418 on physician operatedcomputer 414 further responds 440 to the second patientmedical query message 402, generating a proposed patient response message with appended physicianextender billing data 442, which is sent 444 to the workflow engine, where themedical profiler process 322 then generates 450 a proposed patient response with appended physician extender billing data logentry 452 which is added 454 to the patient medical profile 330. - Note that in the flowcharts included herein, the starting operation of a flowchart may perform operations to allocate systems resources for use by the subsequent operations of the flowchart in certain embodiments. The starting operation of a flowchart may further perform initialize systems resources in certain embodiments.
- Note also that in the flowcharts included herein, the terminating or exit operation of a flowchart may perform operations to release allocated systems resources used by the subsequent operations of the flowchart in certain embodiments. The terminating operation of a flowchart may further perform a “return” operation in certain embodiments. Alternatively, the terminating operation of a flowchart may not perform a “return” operation in certain embodiments.
- FIG. 5 depicts a flowchart of operations supporting the generation and sending of an educated query by a patient using the first messaging wizard in accordance with embodiments supporting FIG. 4.
Operation 600 starts the operations of this flowchart.Arrow 602 directs the flow of execution fromoperation 600 tooperation 604.Operation 604 performs generating of an educated query message.Arrow 606 directs execution fromoperation 604 tooperation 608.Operation 608 performs sending the educated query message to the workflow engine.Arrow 610 directs execution fromoperation 608 tooperation 612.Operation 612 terminates the operations of this flowchart. - FIG. 6 depicts a flowchart of operations supporting the reception, processing, logging of the educated query message from the patient, and the generation and sending of the patient medical query message to a physician by the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 4.
Operation 630 starts the operations of this flowchart.Arrow 632 directs the flow of execution fromoperation 630 tooperation 634.Operation 634 performs receiving the educated query message at the workflow engine.Arrow 636 directs execution fromoperation 634 tooperation 638.Operation 638 performs processing the received educated query message to create the processed, received educated query message.Arrow 640 directs execution fromoperation 638 tooperation 642.Operation 642 performs generating a patient medical query message.Arrow 644 directs execution fromoperation 642 tooperation 646.Operation 646 performs sending the patient medical query message to first physician at corresponding physician address.Arrow 648 directs execution fromoperation 646 tooperation 650.Operation 650 terminates the operations of this flowchart. - In certain embodiments,
operation 646 further includes selecting a first physician. In certain further embodiments,operation 646 further includes selecting a first physician based upon the received educated query message. In certain further embodiments,operation 646 further includes selecting a first physician based upon the processed, received educated query message. -
Arrow 652 directs the flow of execution from startingoperation 638 tooperation 654.Operation 654 performs generating a patient message log entry in the patient medical profile.Arrow 656 directs execution fromoperation 654 tooperation 650. - FIG. 7 depicts a flowchart of operations supporting reception, processing and viewing the patient medical query message by the second message wizard for the physician in accordance with embodiments supporting FIG. 4.
-
Operation 670 starts the operations of this flowchart.Arrow 672 directs the flow of execution fromoperation 670 tooperation 674.Operation 674 performs receiving the patient query message.Arrow 676 directs execution fromoperation 674 tooperation 678.Operation 678 performs processing the received patient medical query message to create the processed, received patient medical message.Arrow 680 directs execution fromoperation 678 tooperation 682.Operation 682 performs generating a physician-viewable patient medical query message from the processed, received patient medical query message.Arrow 684 directs execution fromoperation 682 tooperation 686.Operation 686 performs displaying the physician-viewable patient medical query message.Arrow 688 directs execution fromoperation 686 tooperation 690.Operation 690 terminates the operations of this flowchart. - FIG. 8 depicts a flowchart of operations supporting reception, generation and sending a patient response message, as well as copying the patient response message with an appended physician billing data to the workflow engine in accordance with embodiments supporting FIG. 4.
Operation 700 starts the operations of this flowchart.Arrow 702 directs the flow of execution fromoperation 700 tooperation 704.Operation 704 performs responding to the physician-viewable patient medical query message to create a first-physician response.Arrow 706 directs execution fromoperation 704 tooperation 708.Operation 708 performs generating a patient response message from the first-physician response.Arrow 710 directs execution fromoperation 708 tooperation 712.Operation 712 performs sending the patient response message to the patient at the corresponding patient address.Arrow 714 directs execution fromoperation 712 tooperation 716.Operation 716 terminates the operations of this flowchart. -
Arrow 720 directs the flow of execution from startingoperation 708 tooperation 722.Operation 722 performs copying the patient response message with appended physician billing data to workflow engine.Arrow 724 directs execution fromoperation 722 tooperation 716. - FIG. 9 depicts a flowchart of operations supporting the reception, processing, logging the copied patient response message with an appended physician billing data by the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 4.
Operation 740 starts the operations of this flowchart.Arrow 742 directs the flow of execution fromoperation 740 tooperation 744.Operation 744 performs receiving the copied patient response message with appended physician billing data.Arrow 746 directs execution fromoperation 744 tooperation 748.Operation 748 performs processing the received, copied patient response message with appended physician billing data to create the processed, received, copied patient response message with appended physician billing data.Arrow 750 directs execution fromoperation 748 tooperation 752.Operation 752 performs generating a patient response log entry in patient medical profile from the processed, received, copied patient response message with appended physician billing data.Arrow 754 directs execution fromoperation 752 tooperation 756.Operation 756 terminates the operations of this flowchart. - FIG. 10 depicts a flowchart of operations supporting reception, processing and display of the patient response message using the first messaging wizard on the patient operated computer in accordance with embodiments supporting FIG. 4. Operation Q0 starts the operations of this flowchart.
Arrow 772 directs the flow of execution fromoperation 770 tooperation 774.Operation 774 performs receiving the patient response message.Arrow 776 directs execution fromoperation 774 tooperation 778.Operation 778 performs processing the received patient response message, to create a processed, received patient response message.Arrow 780 directs execution fromoperation 778 tooperation 782.Operation 782 performs displaying the processed, received patient response message.Arrow 784 directs execution fromoperation 782 tooperation 786.Operation 786 terminates the operations of this flowchart. - FIG. 11 depicts a flowchart of further
details regarding operation 604, generation of an educated query message by the first messaging wizard in accordance with embodiments supporting FIG. 5.Arrow 800 directs the flow of execution from startingoperation 604 tooperation 802.Operation 802 performs providing a patient-to-profiler authentication key.Arrow 804 directs execution fromoperation 802 tooperation 806.Operation 806 performs encrypting the educated query message with patient-to-profiler authentication key.Arrow 808 directs execution fromoperation 806 tooperation 810.Operation 810 terminates the operations of this flowchart. - FIG. 12 depicts a flowchart of further
details regarding operation 638, processing the educated query message using the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 6.Arrow 820 directs the flow of execution from startingoperation 638 tooperation 822.Operation 822 performs providing a profiler-from-patient authentication key.Arrow 824 directs execution fromoperation 822 tooperation 826.Operation 826 performs decrypting the received, educated query message with profiler-from-patient authentication key.Arrow 828 directs execution fromoperation 826 tooperation 830.Operation 830 terminates the operations of this flowchart. - FIG. 13 depicts a flowchart of further
details regarding operation 642, generation of a patient medical query message by the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 6.Arrow 850 directs the flow of execution from startingoperation 642 tooperation 852.Operation 852 performs providing profiler-from-first-physician authentication key.Arrow 854 directs execution fromoperation 852 tooperation 856.Operation 856 performs encrypting patient medical query message with profiler-from-first-physician authentication key.Arrow 858 directs execution fromoperation 856 tooperation 860.Operation 860 terminates the operations of this flowchart. - FIG. 14 depicts a flowchart of further
details regarding operation 678, processing the received patient medical query message by the second messaging wizard in accordance with embodiments supporting FIG. 7.Arrow 880 directs the flow of execution from startingoperation 678 tooperation 882.Operation 882 performs providing a first-physician-from-profiler authentication key.Arrow 884 directs execution fromoperation 882 tooperation 886.Operation 886 performs decrypting the received patient medical query message with the first-physician-from-profiler authentication key.Arrow 888 directs execution fromoperation 886 tooperation 890.Operation 890 terminates the operations of this flowchart. - FIG. 15 depicts a flowchart of further
details regarding operation 722, copying the patient response message with appended physician billing data to the workflow engine by the second messaging wizard in accordance with embodiments supporting FIG. 8.Arrow 900 directs the flow of execution from startingoperation 722 tooperation 902.Operation 902 performs providing a first-physician-to-profiler authentication key.Arrow 904 directs execution fromoperation 902 tooperation 906.Operation 906 performs encrypting the patient response message with appended physician billing data with the first-physician-to-profiler authentication key.Arrow 908 directs execution fromoperation 906 tooperation 910.Operation 910 performs sending first-physician-to-profiler encrypted patient response message with appended physician billing data to the workflow engine.Arrow 912 directs execution fromoperation 910 tooperation 914.Operation 914 terminates the operations of this flowchart. - FIG. 16 depicts a flowchart of further
details regarding operation 748, processing the received, copied the patient response message with appended physician billing data using the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 9.Arrow 930 directs the flow of execution from startingoperation 748 tooperation 932.Operation 932 performs providing a profiler-from-first-physician authentication key.Arrow 934 directs execution fromoperation 932 tooperation 936.Operation 936 performs decrypting the received, copied patient response message with appended physician billing data with the profiler-from-first physician authentication key to create the processed, received patient response message with appended physician billing data.Arrow 938 directs execution fromoperation 936 tooperation 940.Operation 940 terminates the operations of this flowchart. - FIG. 17 depicts a flowchart of further
details regarding operation 708, generating patient response message using the second message wizard in accordance with embodiments supporting FIG. 8.Arrow 950 directs the flow of execution from startingoperation 708 tooperation 952.Operation 952 performs providing first-physician-to-patient authentication key.Arrow 954 directs execution fromoperation 952 tooperation 956.Operation 956 performs generating an unencrypted patient response message from the physician-viewable patient medical query message and the first-physician response.Arrow 958 directs execution fromoperation 956 tooperation 960.Operation 960 performs encrypt the unencrypted patient response message with the first-physician-to-patient authentication key to create the patient response message.Arrow 962 directs execution fromoperation 960 tooperation 964.Operation 964 terminates the operations of this flowchart. - Note that
operations - FIG. 18 depicts a flowchart of further
details regarding operation 778, processing the received patient response message using the first message wizard in accordance with embodiments supporting FIG. 10.Arrow 980 directs the flow of execution from startingoperation 778 tooperation 982.Operation 982 performs providing a patient-from-first-physician authentication key.Arrow 984 directs execution fromoperation 982 tooperation 986.Operation 986 performs decrypting the received patient response message with the patient-from-first-physician authentication key to create the processed, received patient response message.Arrow 988 directs execution fromoperation 986 tooperation 990.Operation 990 terminates the operations of this flowchart. - FIG. 19 depicts a flowchart of further
details regarding operation 712, sending the patient response message with appended physician billing data using the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 8.Arrow 1000 directs the flow of execution from startingoperation 712 tooperation 1002.Operation 1002 performs sending patient response message destined to patient to workflow engine.Arrow 1004 directs execution fromoperation 1002 tooperation 1006.Operation 1006 terminates the operations of this flowchart. - FIG. 20 depicts a flowchart of further
details regarding operation 708, generating the patient response message using the second message wizard in accordance with embodiments supporting FIG. 8.Arrow 1010 directs the flow of execution from startingoperation 708 tooperation 1012.Operation 1012 performs providing the first-physician-to-profiler authentication code.Arrow 1014 directs execution fromoperation 1012 tooperation 1016.Operation 1016 performs providing the patient address as destination address within the patient response message, to create an unencrypted patient response message with patient address destination.Arrow 1018 directs execution fromoperation 1016 tooperation 1020.Operation 1020 performs encrypting the unencrypted patient response message with the first-physician-to-profiler authentication code to create the patient response message destined for the patient at the corresponding patient address.Arrow 1022 directs execution fromoperation 1020 tooperation 1024.Operation 1024 terminates the operations of this flowchart. - Note that
operations - FIG. 21 depicts a flowchart of operations of the medical profiler process performed by the workflow engine in accordance with alternative embodiments supporting FIG. 4.
Operation 1040 starts the operations of this flowchart.Arrow 1042 directs the flow of execution fromoperation 1040 tooperation 1044.Operation 1044 performs receiving the patient response message destined for the patient at the corresponding patient address.Arrow 1046 directs execution fromoperation 1044 tooperation 1048.Operation 1048 performs processing the received patient response message destined for the patient at the corresponding patient address, to create the patient response message for the patient at the corresponding patient address.Arrow 1050 directs execution fromoperation 1048 tooperation 1052.Operation 1052 performs sending the patient response message to the patient at the corresponding patient address.Arrow 1054 directs execution fromoperation 1052 tooperation 1056.Operation 1056 terminates the operations of this flowchart. - FIG. 22 depicts a flowchart of further
details regarding operation 1048, processing the patient response message destined for the patient using the medical profiler process performed by the workflow engine in accordance with embodiments supporting FIG. 21.Arrow 1070 directs the flow of execution from startingoperation 1048 tooperation 1072.Operation 1072 performs providing a profiler-from-first-physician authentication key.Arrow 1074 directs execution fromoperation 1072 tooperation 1076.Operation 1076 performs decrypting the received patient response message destined for the patient at the corresponding patient address to create the processed, received patient response message for the patient at the corresponding patient address.Arrow 1078 directs execution fromoperation 1076 tooperation 1080.Operation 1080 terminates the operations of this flowchart. - FIG. 23 depicts a flowchart of further
details regarding operation 642, generating a patient medical query message using the medical profiler process performed by the workflow engine in accordance with embodiments.Arrow 1100 directs the flow of execution from startingoperation 642 tooperation 1102.Operation 1102 performs selecting a first physician extender from the physician extenders.Arrow 1104 directs execution fromoperation 1102 tooperation 1106.Operation 1106 performs generating a second patient medical query message for the first physician extender.Arrow 1108 directs execution fromoperation 1106 tooperation 1110.Operation 1110 performs sending the second patient medical query message to the first physician extender at the corresponding physician extender address.Arrow 1112 directs execution fromoperation 1110 tooperation 1114.Operation 1114 terminates the operations of this flowchart. - Note that in certain embodiments,
operation 1102 is based upon the received educated query message. In certain further embodiments,operation 1102 is based upon the processed, received educated query message. - FIG. 24 depicts a flowchart of operations using the third message wizard on the physician extender computer in accordance with embodiments supporting
- FIG. 9.
Operation 1150 starts the operations of this flowchart.Arrow 1152 directs the flow of execution fromoperation 1150 tooperation 1154.Operation 1154 performs receiving a second patient message by first physician extender operating a computer at the corresponding physician extender address.Arrow 1156 directs execution fromoperation 1154 tooperation 1158.Operation 1158 performs processing the received second patient medical query message to create a processed, received second patient medical query message.Arrow 1160 directs execution fromoperation 1158 tooperation 1162.Operation 1162 performs generating a physician extender-viewable patient medical query message from the processed, received second patient medical query message.Arrow 1164 directs execution fromoperation 1162 tooperation 1166.Operation 1166 performs displaying the physician extender-viewable medical query message.Arrow 1168 directs execution fromoperation 1166 tooperation 1170.Operation 1170 performs responding to the physician extender-viewable medical query message to create a physician extender response.Arrow 1172 directs execution fromoperation 1170 tooperation 1174.Operation 1174 performs generating the proposed patient response message from physician extender response.Arrow 1176 directs execution fromoperation 1174 tooperation 1178.Operation 1178 performs sending the proposed patient response message to the first physician at the corresponding physician address.Arrow 1180 directs execution fromoperation 1178 tooperation 1182.Operation 1182 terminates the operations of this flowchart. - FIG. 25 depicts a flowchart of further
details regarding operation 682, generating the physician-viewable patient medical query message in accordance with embodiments supporting FIGS. 7.Arrow 1200 directs the flow of execution from startingoperation 682 tooperation 1202.Operation 1202 performs receiving proposed patient response message from first physician extender.Arrow 1204 directs execution fromoperation 1202 tooperation 1206.Operation 1206 performs processing the received patient response message to create processed, received patient response message.Arrow 1208 directs execution fromoperation 1206 tooperation 1210.Operation 1210 performs inserting the processed, received proposed patient response message as part of the physician-viewable patient medical query message.Arrow 1212 directs execution fromoperation 1210 tooperation 1214.Operation 1214 terminates the operations of this flowchart. - FIG. 26 depicts a flowchart of further
details regarding operation 708, generating the patient response message using the second message wizard in accordance with certain embodiments.Arrow 1220 directs the flow of execution from startingoperation 708 tooperation 1222.Operation 1222 performs reviewing the proposed patient response message.Arrow 1224 directs execution fromoperation 1222 tooperation 1226.Operation 1226 terminates the operations of this flowchart. - FIG. 27 depicts a flowchart of further operations embodying the third message wizard in accordance with certain embodiments.
Arrow 1240 directs the flow of execution from startingoperation 1240 tooperation 1242.Operation 1242 performs generating a copied proposed patient response message with appended physician extender billing data from the physician extender-viewable patient medical query message and first physician extender response.Arrow 1244 directs execution fromoperation 1242 tooperation 1246.Operation 1246 performs sending copied proposed patient response with appended physician extender billing data to workflow engine.Arrow 1248 directs execution fromoperation 1246 tooperation 1250.Operation 1250 terminates the operations of this flowchart. - FIG. 28 depicts a flowchart of further operations embodied in the message profiler process in accordance with certain embodiments.
Operation 1270 starts the operations of this flowchart.Arrow 1272 directs the flow of execution fromoperation 1270 tooperation 1274.Operation 1274 performs receiving the copied proposed patient response message with the appended physician extender billing data.Arrow 1276 directs execution fromoperation 1274 tooperation 1278.Operation 1278 performs processing the received copied proposed patient response message with the appended physician extender billing data, to create a processed, received copied proposed patient response message with the appended physician extender billing data.Arrow 1280 directs execution fromoperation 1278 tooperation 1282.Operation 1282 performs generating a physician extender log entry in the medical profile of the patient from the processed, received copied patient response message with the appended physician extender billing data.Arrow 1284 directs execution fromoperation 1282 tooperation 1286.Operation 1286 terminates the operations of this flowchart. - FIG. 29 depicts a flowchart of further operations embodied in a second messaging wizard in accordance with certain embodiments supporting prescriptions.
Operation 1290 starts the operations of this flowchart.Arrow 1291 directs the flow of execution fromoperation 1290 tooperation 1292.Operation 1292 performs generating an embedded prescription.Arrow 1293 directs execution fromoperation 1292 tooperation 1294.Operation 1294 performs inserting the embedded prescription into patient response message.Arrow 1295 directs execution fromoperation 1294 tooperation 1296.Operation 1296 performs generating a physician prescription message from the embedded prescription.Arrow 1297 directs execution fromoperation 1296 tooperation 1298.Operation 1298 performs sending the physician prescription message to the workflow engine.Arrow 1299 directs execution fromoperation 1298 tooperation 1300.Operation 1300 terminates the operations of this flowchart. - FIG. 30 depicts a flowchart of further operations embodied in a medical profiler in accordance with certain embodiments supporting prescriptions.
Operation 1305 starts the operations of this flowchart.Arrow 1306 directs the flow of execution fromoperation 1305 tooperation 1307.Operation 1307 performs maintaining a list of pharmacies, each with a corresponding pharmacy address.Arrow 1308 directs execution fromoperation 1307 tooperation 1309.Operation 1309 terminates the operations of this flowchart. -
Arrow 1310 directs the flow of execution from startingoperation 1305 tooperation 1311.Operation 1311 performs integrating a prescription order.Arrow 1312 directs execution fromoperation 1311 tooperation 1309.Operation 1309 terminates the operations of this flowchart. - Note that
arrows - FIG. 30A depicts a flowchart of further
details regarding operation 1311, integrating a prescription order in the medical profiler process in accordance with embodiments supporting FIG. 30.Arrow 1315 directs the flow of execution from the starting ofoperation 1311 tooperation 1316.Operation 1316 performs receiving the physician prescription message.Arrow 1317 directs execution fromoperation 1316 tooperation 1318.Operation 1318 performs processing the received physician prescription message, to create a processed, received physician prescription message. -
Arrow 1319 directs execution fromoperation 1311 tooperation 1320.Operation 1320 performs receiving a patient prescription order message.Arrow 1321 directs execution fromoperation 1320 tooperation 1322.Operation 1322 performs processing the received patient prescription order message to create a processed, received patient prescription order message. -
Arrow 1323 directs execution fromoperation 1322 tooperation 1324.Arrow 1330 directs execution fromoperation 1318 tooperation 1324. Note that in certain embodiments, botharrows operation 1324 can execute.Operation 1324 performs generating a pharmacy prescription order message from the processed, received physician prescription message and the processed, received patient prescription order message.Arrow 1325 directs execution fromoperation 1324 tooperation 1326.Operation 1326 performs sending the pharmacy prescription order message to one of the pharmacies at the corresponding pharmacy address.Arrow 1327 directs execution fromoperation 1326 tooperation 1328.Operation 1328 terminates the operations of this flowchart. - FIG. 31 depicts a flowchart of further operations embodied in the first messaging wizard in accordance with certain embodiments supporting prescriptions.
Operation 1340 starts the operations of this flowchart.Arrow 1342 directs the flow of execution fromoperation 1340 tooperation 1344.Operation 1344 performs responding to the embedded prescription within the processed, received patient response message.Arrow 1346 directs execution fromoperation 1344 tooperation 1348.Operation 1348 terminates the operations of this flowchart. -
Arrow 1350 directs the flow of execution from startingoperation 1340 tooperation 1352.Operation 1352 performs ordering the embedded prescription from the processed, received patient response message.Arrow 1354 directs execution fromoperation 1352 tooperation 1348.Operation 1348 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by patient choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 32 depicts a flowchart of further details of
operation 1352, ordering the embedded prescription of FIG. 31.Arrow 1360 directs the flow of execution from startingoperation 1352 tooperation 1362.Operation 1362 performs generating a patient prescription message from the processed, received patient response message.Arrow 1364 directs execution fromoperation 1362 tooperation 1366.Operation 1366 performs sending the patient prescription message to the workflow engine.Arrow 1368 directs execution fromoperation 1366 tooperation 1370.Operation 1370 terminates the operations of this flowchart. - FIG. 33 depicts a flowchart of further details of
operation 1170 of FIG. 25.Arrow 1380 directs the flow of execution from startingoperation 1170 tooperation 1382.Operation 1382 performs generating a proposed embedded prescription refill in the proposed patient response.Arrow 1384 directs execution fromoperation 1382 tooperation 1386.Operation 1386 terminates the operations of this flowchart. - FIG. 34 depicts a flowchart of further details of
operation 1222 of FIG. 27.Arrow 1400 directs the flow of execution from startingoperation 1222 tooperation 1402.Operation 1402 performs reviewing the proposed embedded prescription refill.Arrow 1404 directs execution fromoperation 1402 tooperation 1406.Operation 1406 terminates the operations of this flowchart. - FIG. 35 depicts a flowchart of further details of
operation 1402 of FIG. 34.Arrow 1420 directs the flow of execution from startingoperation 1402 tooperation 1 422.Operation 1422 performs approving the proposed prescription refill.Arrow 1424 directs execution fromoperation 1422 tooperation 1426.Operation 1426 terminates the operations of this flowchart. -
Arrow 1430 directs the flow of execution from startingoperation 1402 tooperation 1432.Operation 1432 performs revising the proposed embedded prescription refill.Arrow 1434 directs execution fromoperation 1432 tooperation 1426.Operation 1426 terminates the operations of this flowchart. -
Arrow 1440 directs the flow of execution from startingoperation 1402 tooperation 1442.Operation 1442 performs deleting the proposed embedded prescription refill.Arrow 1444 directs execution fromoperation 1442 tooperation 1426.Operation 1426 terminates the operations of this flowchart. -
Arrow 1450 directs the flow of execution from startingoperation 1402 tooperation 1452.Operation 1452 performs generating a second embedded prescription.Arrow 1454 directs execution fromoperation 1452 tooperation 1426.Operation 1426 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by patient choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 36 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments supporting billing patients.
Operation 1470 starts the operations of this flowchart.Arrow 1472 directs the flow of execution fromoperation 1470 tooperation 1474.Operation 1474 performs generating a billing report from the patient medical profile.Arrow 1476 directs execution fromoperation 1474 tooperation 1478.Operation 1478 terminates the operations of this flowchart. - FIG. 37 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments further supporting billing patients.
Operation 1490 starts the operations of this flowchart.Arrow 1492 directs the flow of execution fromoperation 1490 tooperation 1494.Operation 1494 performs sending the billing report to the billing system.Arrow 1496 directs execution fromoperation 1494 tooperation 1498.Operation 1498 terminates the operations of this flowchart. - FIG. 38 depicts a flowchart of further operations embodying a billing process in accordance with certain embodiments.
Operation 1510 starts the operations of this flowchart.Arrow 1512 directs the flow of execution fromoperation 1510 tooperation 1514.Operation 1514 performs receiving the billing report for the patient.Arrow 1516 directs execution fromoperation 1514 tooperation 1518.Operation 1518 performs generating a bill for the patient based from the received billing report for the patient.Arrow 1520 directs execution fromoperation 1518 tooperation 1522.Operation 1522 terminates the operations of this flowchart. ### - FIG. 39 depicts a flowchart of further details of
operation 1518 of FIG. 38.Arrow 1540 directs the flow of execution from startingoperation 1518 tooperation 1542.Operation 1542 performs generating a personal bill for the patient.Arrow 1544 directs execution fromoperation 1542 tooperation 1546.Operation 1546 terminates the operations of this flowchart. -
Arrow 1550 directs the flow of execution from startingoperation 1518 tooperation 1552.Operation 1552 performs generating an insurance bill for the patient to corresponding insurance provider.Arrow 1554 directs execution fromoperation 1552 tooperation 1546.Operation 1546 terminates the operations of this flowchart. - Note that a patient may not have insurance, so that in such circumstances, no insurance bills would be generated. Note also, that in certain circumstances, there may be an overall insuring, such as a governmental agency, fully paying for the health costs. In such circumstances, no personal medical bill might be generated. In certain alternative embodiments, the performing of these operations might not lead to output of one or the other kinds of medical bills.
- FIG. 40 depicts a flowchart of further details of
operation 708 of FIG. 8 supporting a physician requesting a second opinion in accordance with certain embodiments.Arrow 1570 directs the flow of execution from startingoperation 704 tooperation 1572.Operation 1572 performs generating a first-physician second opinion request message.Arrow 1574 directs execution fromoperation 1572 tooperation 1576.Operation 1576 performs sending the first physician-second opinion request message to the second physician at the corresponding physician address.Arrow 1578 directs execution fromoperation 1576 tooperation 1580.Operation 1580 terminates the operations of this flowchart. - FIG. 41 depicts a flowchart of operations embodied in the second message wizard supporting a second physician and a second opinion request in accordance with certain embodiments.
Operation 1600 starts the operations of this flowchart.Arrow 1602 directs the flow of execution fromoperation 1600 tooperation 1604.Operation 1604 performs receiving the first-physician-second opinion request message.Arrow 1606 directs execution fromoperation 1604 tooperation 1608.Operation 1608 performs processing the received, first-physician-second opinion request message to create the processed, received first-physician-second opinion request.Arrow 1610 directs execution fromoperation 1608 tooperation 1612.Operation 1612 performs displaying the processed, received first-physician-second-opinion request.Arrow 1614 directs execution fromoperation 1612 tooperation 1616.Operation 1616 performs responding to the displayed, processed, received first-physician-second opinion request to create a second opinion response.Arrow 1618 directs execution fromoperation 1616 tooperation 1620.Operation 1620 performs generating a second opinion message from the second opinion response.Arrow 1622 directs execution fromoperation 1620 tooperation 1624.Operation 1624 performs sending the second opinion message to the first-physician at the corresponding physician address.Arrow 1626 directs execution fromoperation 1624 tooperation 1628.Operation 1628 terminates the operations of this flowchart. - FIG. 42 depicts a flowchart of operations embodied in a second message wizard supporting maintaining a collection of patient response templates in accordance with certain embodiments.
Operation 1640 starts the operations of this flowchart.Arrow 1642 directs the flow of execution fromoperation 1640 tooperation 1644.Operation 1644 performs creating a patient response template.Arrow 1646 directs execution fromoperation 1644 tooperation 1648.Operation 1648 terminates the operations of this flowchart. -
Arrow 1650 directs the flow of execution from startingoperation 1640 tooperation 1652.Operation 1652 performs editing one of the patient response templates.Arrow 1654 directs execution fromoperation 1652 tooperation 1648.Operation 1648 terminates the operations of this flowchart. -
Arrow 1660 directs the flow of execution from startingoperation 1640 tooperation 1662.Operation 1662 performs deleting one of the patient response templates.Arrow 1664 directs execution fromoperation 1662 tooperation 1648.Operation 1648 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by patient choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 43 depicts a flowchart of further details of
operation 704 of FIG. 8 supporting use of a patient response template to create a first-physician response in accordance with certain embodiments.Arrow 1670 directs the flow of execution from startingoperation 704 to operation 1672. Operation 1672 performs invoking one of the patient response templates in conjunction with the processed, received patient medical query message.Arrow 1674 directs execution from operation 1672 tooperation 1676.Operation 1676 performs responding by first physician to invoked patient response template and processed, received patient medical query message to create the first-physician response.Arrow 1678 directs execution fromoperation 1676 tooperation 1680.Operation 1680 terminates the operations of this flowchart. - FIG. 44 depicts a flowchart of operations embodied in a first messaging wizard to support maintaining a collection of patient problem templates in accordance with certain embodiments.
Operation 1700 starts the operations of this flowchart.Arrow 1702 directs the flow of execution fromoperation 1700 tooperation 1704.Operation 1704 performs receiving the patient problem template from workflow engine. Arrow 1706 directs execution fromoperation 1704 tooperation 1708.Operation 1708 performs processing the received patient problem template to create a processed, received patient problem template.Arrow 1710 directs execution fromoperation 1708 tooperation 1712.Operation 1712 performs adding the processed, received patient problem template to the collection of patient problem templates.Arrow 1714 directs execution fromoperation 1712 tooperation 1716.Operation 1716 terminates the operations of this flowchart. - FIG. 45 depicts a flowchart of further details of
operation 604 of FIG. 5 supporting use of a patient problem template to create an educated medical query using a first medical wizard in accordance with certain embodiments.Arrow 1730 directs the flow of execution from startingoperation 604 tooperation 1732.Operation 1732 performs invoking one of the patient problem templates.Arrow 1734 directs execution fromoperation 1732 tooperation 1736.Operation 1736 performs responding by patient to invoked patient problem templates to create the educated query message.Arrow 1738 directs execution fromoperation 1736 tooperation 1740.Operation 1740 terminates the operations of this flowchart. - FIG. 46 depicts a flowchart of operations embodied in a medical profiler process performed by a workflow engine to generate and send patient problem templates to patients in accordance with certain embodiments.
Operation 1760 starts the operations of this flowchart.Arrow 1762 directs the flow of execution fromoperation 1760 tooperation 1764.Operation 1764 performs generating a patient problem template from the patient medical profile.Arrow 1766 directs execution fromoperation 1764 tooperation 1768.Operation 1768 performs sending the patient problem template to the patient at the corresponding patient address.Arrow 1770 directs execution fromoperation 1768 tooperation 1772.Operation 1772 terminates the operations of this flowchart. - FIG. 47 depicts a flow diagram of a medical profiler process in accordance with certain embodiments.
Box 1800 designates a Medical Profiler Process Dispatcher. This communicates viaphysical transport mechanism 1802 tonetwork 1804.Box 1808 designatesMedical profiler sub-process 1 onworkflow engine 1, performing theoperation 630 of FIG. 6. This communicates viaphysical transport mechanism 1806 tonetwork 1804.Box 1812 designatesMedical profiler sub-process 2 onworkflow engine 2, performing theoperation 740 of FIG. 9. This communicates viaphysical transport mechanism 1810 tonetwork 1804.Box 1816 designatesMedical profiler sub-process 3 onworkflow engine 3, performing theoperation 1040 of FIG. 21. This communicates viaphysical transport mechanism 1814 tonetwork 1804.Box 1820 designatesMedical profiler sub-process 4 onworkflow engine 4, performing theoperation 1270 of FIG. 28. This communicates viaphysical transport mechanism 1818 tonetwork 1804.Box 1824 designatesMedical profiler sub-process 5 onworkflow engine 5, performing theoperation 1470 of FIG. 36. This communicates viaphysical transport mechanism 1822 tonetwork 1804.Box 1828 designatesMedical profiler sub-process 6 onworkflow engine 6, performing theoperation 1490 of FIG. 37. This communicates viaphysical transport mechanism 1826 tonetwork 1804.Box 1832 designatesMedical profiler sub-process 7 onworkflow engine 7, performing theoperation 1760 of FIG. 46. This communicates viaphysical transport mechanism 1830 tonetwork 1804. - Note that in certain alternative embodiments, collections of these subprocesses may preferably reside on a single workflow engine. Note that in certain other embodiments, multiple workflow engines may be performing a given sub-process.
- FIG. 48 depicts a flow diagram of a computer program capable of receiving a message from a physician containing a prescription and responding to the message containing the prescription in accordance with an aspect of the invention.
Operation 1850 starts the operations of this flowchart.Arrow 1852 directs the flow of execution fromoperation 1850 tooperation 1854.Operation 1854 performs receiving the patient message with an embedded prescription.Arrow 1856 directs execution fromoperation 1854 tooperation 1858.Operation 1858 performs displaying the received patient message with embedded prescription.Arrow 1860 directs execution fromoperation 1858 tooperation 1862.Operation 1862 performs responding to the patient message with embedded prescription.Arrow 1864 directs execution fromoperation 1862 tooperation 1866.Operation 1866 terminates the operations of this flowchart. - FIG. 49 depicts a flowchart of further details of the code of1854 of FIG. 48 supporting receiving a patient message with an embedded prescription in accordance with certain embodiments.
Arrow 1880 directs the flow of execution from startingoperation 1854 tooperation 1882.Operation 1882 performs receiving an encrypted patient message with embedded prescription.Arrow 1884 directs execution fromoperation 1882 tooperation 1886.Operation 1886 performs processing the received, encrypted patient message with embedded prescription to create the received patient message with embedded prescription.Arrow 1888 directs execution fromoperation 1886 tooperation 1890.Operation 1890 terminates the operations of this flowchart. - FIG. 50 depicts a flowchart of further details of the code of1862 of FIG. 48 supporting responding to the patient response message in accordance with certain embodiments.
Arrow 1900 directs the flow of execution from startingoperation 1862 tooperation 1902.Operation 1902 performs generating a patient prescription message from said embedded prescription.Arrow 1904 directs execution fromoperation 1902 tooperation 1906.Operation 1906 performs sending said patient prescription message to said workflow engine.Arrow 1908 directs execution fromoperation 1906 tooperation 1910.Operation 1910 terminates the operations of this flowchart. - FIG. 50A depicts a flowchart of further details of1311 of FIG. 30 supporting integrating a prescription order in accordance with certain embodiments.
-
Arrow 1920 directs the flow of execution from startingoperation 1311 tooperation 1922.Operation 1922 determines if the received patient response message contains an embedded prescription.Arrow 1924 directs execution fromoperation 1922 tooperation 1926.Arrow 1924 directs execution when the determination is ‘Yes’ tooperation 1926.Arrow 1954 directs execution when the determination is ‘No’ tooperation 1946. -
Operation 1926 performs receiving the patient prescription order message from the first patient.Arrow 1928 directs execution fromoperation 1926 tooperation 1930.Operation 1930 determines if the patient prescription order message from the first patient is compatible with the embedded prescription contained in the received patient response message.Arrow 1932 directs execution fromoperation 1930 tooperation 1934.Arrow 1932 directs execution when the determination is ‘Yes’ tooperation 1934.Arrow 1956 directs execution when the determination is ‘No’ tooperation 1946. -
Operation 1934 determines if the patient prescription order received from the first patient authorizes the prescription order.Arrow 1936 directs execution fromoperation 1934 tooperation 1938.Arrow 1936 directs execution when the determination is ‘Yes’ tooperation 1938.Arrow 1958 directs execution when the determination is ‘No’ tooperation 1946. -
Operation 1938 determines a first pharmacy from the patient prescription order.Arrow 1940 directs execution fromoperation 1938 tooperation 1942.Operation 1942 performs generates and sends the prescription order message to the first pharmacy based upon the received patient response message and the received patient prescription order message.Arrow 1944 directs execution fromoperation 1942 tooperation 1946.Operation 1946 terminates the operations of this flowchart. - FIG. 50B depicts a flowchart of further details of1324 of FIG. 30A supporting generating a pharmacy prescription order in accordance with certain embodiments.
-
Arrow 1960 directs the flow of execution from startingoperation 1324 tooperation 1962.Operation 1962 determines if the processed, received patient prescription order is compatible with the processed, received physician prescription.Arrow 1964 directs execution when the determination is ‘Yes’ tooperation 1966.Arrow 1978 directs usage when the determination is ‘No’ tooperation 1970. -
Operation 1966 generates a pharmacy prescription order message from the processed, received physician prescription message and the processed, received patient prescription order.Arrow 1968 directs execution fromoperation 1966 tooperation 1970.Operation 1970 terminates the operations of this flowchart. - FIG. 50C depicts a flowchart of further details of1326 of FIG. 30A supporting sending a pharmacy prescription order to a pharmacy in accordance with certain embodiments.
-
Arrow 1980 directs the flow of execution from startingoperation 1326 tooperation 1962.Operation 1962 determines if the processed, received patient prescription order is compatible with the processed, received physician prescription.Arrow 1984 directs execution fromoperation 1962 tooperation 1986.Arrow 1984 directs execution when the determination is ‘Yes’ tooperation 1986.Arrow 1998 directs usage when the determination is ‘No’ tooperation 1994. -
Operation 1986 performs determine the first pharmacy from the processed, received patient prescription order.Arrow 1988 directs execution fromoperation 1986 tooperation 1990.Operation 1990 performs sending the pharmacy prescription order message to the first pharmacy.Arrow 1992 directs execution fromoperation 1990 tooperation 1994.Operation 1994 terminates the operations of this flowchart. - FIG. 50D depicts a flowchart of further details of1106 of FIG. 23 supporting determining a routing chain of physician extenders and embedding the routing chain into a second patient query in accordance with certain embodiments.
-
Arrow 2010 directs the flow of execution from startingoperation 1106 tooperation 2012.Operation 2012 determines a routing chain of physician extenders.Arrow 2014 directs execution fromoperation 2012 tooperation 2016.Operation 2016 embeds the routing chain of physician extenders into the second medical query.Arrow 2018 directs execution fromoperation 2016 tooperation 2020.Operation 2020 terminates the operations of this flowchart. Note that a routing chain of physician extenders is a collection of at least one physician extender to whom the second patient query will be routed after the first physician extender has added their proposed response to the patient query. - FIG. 50E depicts a flowchart of further details of1178 of FIG. 24 supporting determining successor physician extenders in an embedded physician extender routing chain, generating a successor medical query message with embedded proposed patient response and sending the successor patient medical query to the successor physician extender.
-
Arrow 2030 directs the flow of execution from startingoperation 1178 tooperation 2032.Operation 2032 determines if there is a successor physician extender in the embedded physician extender chain.Arrow 2034 directs execution fromoperation 2032 tooperation 2036.Arrow 2034 directs execution when the determination is ‘Yes’ tooperation 2032.Arrow 2048 directs execution when the determination is ‘No’ tooperation 2044. -
Operation 2036 generates the successor medical query message with the embedded proposed patient response.Arrow 2038 directs execution fromoperation 2036 tooperation 2040.Operation 2040 send the successor patient medical query to the successor physician extender.Arrow 2042 directs execution fromoperation 2040 tooperation 2044.Operation 2044 terminates the operations of this flowchart. - FIG. 50F depicts a flowchart of further details of646 of FIG. 6 supporting generating a routing tree of physicians with first physician final destination and source list of physicians, generating and sending a source medical query to each physician included in the physician source list.
-
Arrow 2060 directs the flow of execution from startingoperation 646 tooperation 2062.Operation 2062 performs generating a routing tree of physicians with the first physician the final destination of the routing tree and a source list of physicians of the routing tree.Arrow 2064 directs execution fromoperation 2062 tooperation 2066.Operation 2066 performs generating and sending a source medical query for and to each physician belonging to the source list of the routing tree.Arrow 2068 directs execution fromoperation 2066 tooperation 2070.Operation 2070 terminates the operations of this flowchart. - Additional Discussion of Primary Terms as used herein:
- A service profile of a client is a collection of information residing in some computer accessible media which from time to time a computer may be able to access.
- The service profiler process is the system-wide activities which are performed in an automated fashion by the service-flow engine to facilitate the service communication between clients, service providers, service extenders and suppliers to support at least the following: service queries, replies and transactions involved in service recommendations.
- The service-flow engine is the mechanism performing the collection of operations known as the service profiler process. It has at least one address on the network shared with clients, service providers, service extenders and suppliers. Note that this shared network may in fact be partitioned into a collection of networks, each possessing gateways, firewalls and the like as is well known in the art. Note that the service-flow engine may include but is not limited to one computer, and in fact, in certain embodiments preferably involves more than one server computer as will be discussed later.
- A client as used herein will have two components of meaning: The first component being the entity about whom the service profile, query messages, response message and service recommendations are directed; the second is a responsible individual acting for the client in all the transactions, such as generating the query messages, receiving and considering the response messages and ordering the service recommendations. Note that a list of the first component entities includes but is not limited to people, corporations, companies, organizations, as well as real estate, machinery including but not limited to automobiles, computer systems, web sites, software, telephones, communications networks and systems.
- Further embodiments of the invention support the service-flow engine creating routing chains of service extenders starting with a first service extender proceeding through successor service provider extenders until the routing chain terminates with a service provider reviewing the collective proposed client response. The routing chain may be generated by the service-flow engine based upon the client's educated query message.
- Further embodiments of the invention support the service-flow engine creating routing trees of service providers with patent query messages starting with a source list of service providers, possibly routing to intermediate service providers and culminating in a first service provider who reviews the collective service provider responses to their respective client service queries.
- FIG. 51 depicts a flow diagram of an embodiment of the invention in accordance with certain embodiments.
Client 2200 is the primary initiator of this invention.Arrow 2202 depicts the interactions ofclient 2200 to create the educatedquery message 2204. The educatedquery message 2204 is an optimized service query directed by the client to address concerns and conditions involving the client.Arrow 2206 depicts the sending of educatedquery message 2204 to theservice profile 2208 which is managed by the service profiler process. The service-flow engine performs the various service profiler process operations. More will be said about the service-flow engine shortly.Arrow 2210 depicts interactive communication between the service-flow engine 2208 and the service providers 2212 primarily regarding the service profiler. Service providers 2212 are the central destination of client generated educated service query messages as sent by 2210 from the service profiler process to the service provider 2212.Arrow 2214 depicts the response of service provider 2212 to the educated query message, generating aconsultative response 2216.Consultation 2216 provides the basis of theclient response message 2226.Arrow 2218 depicts the inclusion of the service providerconsultative response 2216 witheducational material 2220.Educational material 2220 is included in certain, but not all cases, to meet mandated regulations as well as provide the service providers a mechanism to distribute standard material regarding various conditions and treatments.Arrow 2222 depicts the service-flow engine activities required to incorporate the consultative response and includedmaterials 2220 with billing information (charging) 2224.Charging 2224 performs tasks of notifying a client service profile of the consultative transaction, what was the query, response, educational materials included and the service expenses.Arrow 2226 depicts the actual patent response message derived from 2224 query, service provider response, educational materials included and the service expenses sent toclient 2200. -
Arrow 2230 depicts the message information flow from the service-flow engine to service extender 2232. Service extenders 2232 perform a number of service tasks under the direction of service providers 2212.Arrow 2234 depicts the sending of proposed client response messages generated by service extenders 2232 to a service provider 2212.Arrow 2240 depicts another message information flow from the service-flow engine to aservice assistant 2242. While service assistants are service extenders, aservice assistant 2242 performs a specific additional task distinguishing them from other service extenders, such as service provider assistants and administrators.Service assistant 2242 can propose service recommendation refills for example.Arrow 2244 depicts the sending of proposed client response message, which may further include proposed embedded service recommendation refills, fromservice assistant 2242 toservice provider 2246. - Service provider2212 performs a review on the proposed client response messages from service extenders, including service assistants, as delivered by
arrows Arrow 2248 depicts the interaction between template replies 2246 and service provider 2212. -
Arrow 2250 depicts the information and activity flow based upon theconsultative response 2216 and the placing of aservice recommendation message 2252.Service recommendation message 2252 is created based upon the service provider'sconsultative response 2216, which in turn is based upon the client's service query message and possibly a service assistant's proposed service recommendation refill.Arrow 2254 depicts sending aservice recommendation message 2252 toordering process 2256.Client 2200 receives thepatent response message 2226, and may respond by ordering the embedded service recommendation, which is depicted byarrow 2264 indicating a client service recommendation message sent toordering process 2256.Ordering process 2256 waits until both the service providerservice recommendation message 2254 and clientservice recommendation message 2264 have been received and processed before theorder 2258 is actually placed withsupplier 2260.Supplier 2260 sends the service recommendation toclient 2300 as indicated byarrow 2362. - FIG. 52 depicts an interactive flow between a client using a first message interface, service-flow engine performing a service profiler process and service provider using a second message interface in accordance with an embodiment of the invention.
Client 2300 interacts 2302 with client operatedcomputer 2304, which can access 2306 and perform the operations offirst message interface 2308.Service provider 2350 interacts 2352 with service provider operatedcomputer 2354, which can access 2356 and perform the operations ofsecond message interface 2358.Service extender 2400 interacts 2402 with service extender operatedcomputer 2404, which can access 2406 and perform the operations of second message interface 2408. -
Client 2300 usingfirst message interface 2308 on client operatedcomputer 2304 generates 2310 educatedquery message 2312 and sends it 2314 to service-flow engine 2320 where it is received byservice profiler process 2322.Service profiler process 2322 generates 2324 clientmessage log entry 2326, which is added 2328 to theclient service profile 2330.Service profiler process 2322 further generates 2340 clientservice query message 2342, which is sent 2344 to service provider operatedcomputer 2354. -
Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 receives and responds to the clientservice query message 2342, generating 2360 aclient response message 2362, which in certain embodiments is sent 2364 directly to the client operatedcomputer 2304. In certain alternative embodiments,client response message 2362 is sent 2370 to the service-flow engine, where theservice profiler process 2322 then sends 2372 a version to the client operatedcomputer 2304.Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 further responds to the clientservice query message 2342, generating a client response message with appended serviceprovider billing data 2382, which is sent 2384 to the service-flow engine, where theservice profiler process 2322 then generates 20 2390 a clientresponse log entry 2392 which is added 2394 to theclient service profile 2330. - In certain situations, a service recommendation is embedded into
client response message 2362 by theservice provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 in response to the clientservice query message 2342, which embedded into theclient response message 2362.Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 also generates 2480 service providerservice recommendation message 2482, which is sent 2484 to the service-flow engine using theservice profiler process 2322.Client 2300 usingfirst message interface 2308 on client operatedcomputer 2304 generates 2490client order message 2492 and sends it 2494 to service-flow engine 2320 where it is received byservice profiler process 2322. Once both service providerservice recommendation message 2482 andclient order message 2492 have been received and authenticated, themedial profiler process 2322 generates 2500 a supplierservice order message 2502 which is sent 2504 to thesupplier computer 2506. -
Service profiler process 2322 accesses 2510 theclient service profile 2330 to generate 2512 clientbilling report message 2514 which is sent 2516 tobilling system 2518. Note that thebilling system 2518 in certain embodiments is a separate system element external to the service-flow engine. In certain alternative embodiments,billing system 2518 resides within the operations performed by the service-flow engine. In certain further embodiments,billing system 2518 is part of the service profiler process. - Note that in the flowcharts included herein, the starting operation of a flowchart may perform operations to allocate systems resources for use by the subsequent operations of the flowchart in certain embodiments. The starting operation of a flowchart may further perform initialize systems resources in certain embodiments.
- Note also that in the flowcharts included herein, the terminating or exit operation of a flowchart may perform operations to release allocated systems resources used by the subsequent operations of the flowchart in certain embodiments. The terminating operation of a flowchart may further perform a “return” operation in certain embodiments. Alternatively, the terminating operation of a flowchart may not perform a “return” operation in certain embodiments.
- FIG. 52A depicts an interactive flow between a client using a first message interface, service-flow engine performing a service profiler process and service provider using a second message interface in accordance with a further embodiment of the invention.
Client 2300 interacts 2302 with client operatedcomputer 2304, which can access 2306 and perform the operations offirst message interface 2308.Service provider 2350 interacts 2352 with service provider operatedcomputer 2354, which can access 2356 and perform the operations ofsecond message interface 2358.Service extender 2400 interacts 2402 with service extender operatedcomputer 2404, which can access 2406 and perform the operations of second message interface 2408. -
Client 2300 usingfirst message interface 2308 on client operatedcomputer 2304 generates 2310 educatedquery message 2312 and sends it 2314 to service-flow engine 2320 where it is received byservice profiler process 2322.Service profiler process 2322 generates 2324 clientmessage log entry 2326, which is added 2328 to theclient service profile 2330.Service profiler process 2322 further generates 2340 clientservice query message 2342, which is sent 2344 to service provider operatedcomputer 2354. -
Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 receives and responds to the clientservice query message 2342, generating 2360 aclient response message 2362, which in certain embodiments is sent 2364 directly to the client operatedcomputer 2304. In certain alternative embodiments,client response message 2362 is sent 2370 to the service-flow engine, where theservice profiler process 2322 then sends 2372 a version to the client operatedcomputer 2304.Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 further responds to the clientservice query message 2342, generating a client response message with appended serviceprovider billing data 2382, which is sent 2384 to to the service-flow engine, where theservice profiler process 2322 then generates 2390 a clientresponse log entry 2392 which is added 2394 to theclient service profile 2330. - In certain situations, a service recommendation is embedded into
client response message 2362 by theservice provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 in response to the clientservice query message 2342, which embedded into theclient response message 2362.Service provider 2350 usingsecond message interface 2358 on service provider operatedcomputer 2354 also generates 2480 service providerservice recommendation message 2482, which is sent 2484 to the service-flow engine using theservice profiler process 2322.Client 2300 usingfirst message interface 2308 on client operatedcomputer 2304 generates 2490client order message 2492 and sends it 2494 to service-flow engine 2320 where it is received byservice profiler process 2322. Once both service providerservice recommendation message 2482 andclient order message 2492 have been received and authenticated, themedial profiler process 2322 generates 2500 a supplierservice order message 2502 which is sent 2504 to thesupplier computer 2506. -
Service profiler process 2322 accesses 2510 theclient service profile 2330 to generate 2512 clientbilling report message 2514 which is sent 2516 tobilling system 2518. Note that thebilling system 2518 in certain embodiments is a separate system element external to the service-flow engine. In certain alternative embodiments,billing system 2518 resides within the operations performed by the service-flow engine. In certain further embodiments,billing system 2518 is part of the service profiler process. -
Service profiler process 2322 further generates 2400 a second clientservice query message 2402, which is sent 2404 to service extender operatedcomputer 2414.Service extender 2410 usingthird message interface 2418 on service provider operatedcomputer 2414 receives and responds to the second clientservice query message 2412, generating 2430 a proposedclient response message 2432, which is sent 2434 directly to the service provider operatedcomputer 2354, where it is inserted into the clientservice query message 2342. In certain alternative embodiments,client response message 2432 is sent 2436 to the service-flow engine, where theservice profiler process 2322 then sends a version to the service provider operatedcomputer 2354.Service extender 2410 usingthird message interface 2418 on service provider operatedcomputer 2414 further responds 2440 to the second clientservice query message 2402, generating a proposed client response message with appended serviceextender billing data 2442, which is sent 2444 to the service-flow engine, where theservice profiler process 2322 then generates 2450 a proposed client response with appended service extender billingdata log entry 2452 which is added 2454 to theclient service profile 2330. - FIG. 53 depicts a flowchart of operations supporting the generation and sending of an educated query by a client using the first message interface in accordance with embodiments supporting FIG. 52.
Operation 2600 starts the operations of this flowchart.Arrow 2602 directs the flow of execution fromoperation 2600 tooperation 2604.Operation 2604 performs generating of an educated query message.Arrow 2606 directs execution fromoperation 2604 tooperation 2608.Operation 2608 performs sending the educated query message to the service-flow engine.Arrow 2610 directs execution fromoperation 2608 tooperation 2612.Operation 2612 terminates the operations of this flowchart. - FIG. 54 depicts a flowchart of operations supporting the reception, processing, logging of the educated query message from the client, and the generation and sending of the client service query message to a service provider by the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 52.
Operation 2630 starts the operations of this flowchart.Arrow 2632 directs the flow of execution fromoperation 2630 tooperation 2634.Operation 2634 performs receiving the educated query message at the service-flow engine.Arrow 2636 directs execution fromoperation 2634 tooperation 2638.Operation 2638 performs processing the received educated query message to create the processed, received educated query message.Arrow 2640 directs execution fromoperation 2638 tooperation 2642.Operation 2642 performs generating a client service query message.Arrow 2644 directs execution fromoperation 2642 tooperation 2646.Operation 2646 performs sending the client service query message to first service provider at corresponding service provider address.Arrow 2648 directs execution fromoperation 2646 tooperation 2650.Operation 2650 terminates the operations of this flowchart. - In certain embodiments,
operation 646 further includes selecting a first service provider. In certain further embodiments,operation 646 further includes selecting a first service provider based upon the received educated query message. In certain further embodiments,operation 646 further includes selecting a first service provider based upon the processed, received educated query message. -
Arrow 2652 directs the flow of execution from startingoperation 2638 tooperation 2654.Operation 2654 performs generating a client message log entry in the client service profile.Arrow 2656 directs execution fromoperation 2654 tooperation 2650. - FIG. 55 depicts a flowchart of operations supporting reception, processing and viewing the client service query message by the second message interface for the service provider in accordance with embodiments supporting FIG. 52.
Operation 2670 starts the operations of this flowchart.Arrow 2672 directs the flow of execution fromoperation 2670 tooperation 2674.Operation 2674 performs receiving the client query message.Arrow 2676 directs execution fromoperation 2674 tooperation 2678.Operation 2678 performs processing the received client service query message to create the processed, received client service message.Arrow 2680 directs execution fromoperation 2678 tooperation 2682.Operation 2682 performs generating a service-provider-viewable client service query message from the processed, received client service query message.Arrow 2684 directs execution fromoperation 2682 tooperation 2686.Operation 2686 performs displaying the service-provider-viewable client service query message.Arrow 2688 directs execution fromoperation 2686 tooperation 2690.Operation 2690 terminates the operations of this flowchart. - FIG. 56 depicts a flowchart of operations supporting reception, generation and sending a client response message, as well as copying the client response message with an appended service provider billing data to the service-flow engine in accordance with embodiments supporting FIG. 52.
Operation 2700 starts the operations of this flowchart.Arrow 2702 directs the flow of execution fromoperation 2700 tooperation 2704.Operation 2704 performs responding to the service-provider-viewable client service query message to create a first-service-provider response.Arrow 2706 directs execution fromoperation 2704 tooperation 2708.Operation 2708 performs generating a client response message from the first-service-provider response.Arrow 2710 directs execution fromoperation 2708 tooperation 2712.Operation 2712 performs sending the client response message to the client at the corresponding client address.Arrow 2714 directs execution fromoperation 2712 tooperation 2716.Operation 2716 terminates the operations of this flowchart. -
Arrow 2720 directs the flow of execution from startingoperation 2708 tooperation 2722.Operation 2722 performs copying the client response message with appended service provider billing data to service-flow engine.Arrow 2724 directs execution fromoperation 2722 tooperation 2716. - FIG. 57 depicts a flowchart of operations supporting the reception, processing, logging the copied client response message with an appended service provider billing data by the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 52.
Operation 2740 starts the operations of this flowchart.Arrow 2742 directs the flow of execution fromoperation 2740 tooperation 2744.Operation 2744 performs receiving the copied client response message with appended service provider billing data.Arrow 2746 directs execution fromoperation 2744 tooperation 2748.Operation 2748 performs processing the received, copied client response message with appended service provider billing data to create the processed, received, copied client response message with appended service provider billing data.Arrow 2750 directs execution fromoperation 2748 tooperation 2752.Operation 2752 performs generating a client response log entry in client service profile from the processed, received, copied client response message with appended service provider billing data.Arrow 2754 directs execution fromoperation 2752 tooperation 2756.Operation 2756 terminates the operations of this flowchart. - FIG. 58 depicts a flowchart of operations supporting reception, processing and display of the client response message using the first message interface on the client operated computer in accordance with embodiments supporting FIG. 52.
Operation 2770 starts the operations of this flowchart.Arrow 2772 directs the flow of execution fromoperation 2770 tooperation 2774.Operation 2774 performs receiving the client response message.Arrow 2776 directs execution fromoperation 2774 tooperation 2778.Operation 2778 performs processing the received client response message, to create a processed, received client response message.Arrow 2780 directs execution fromoperation 2778 tooperation 2782.Operation 2782 performs displaying the processed, received client response message.Arrow 2784 directs execution fromoperation 2782 tooperation 2786.Operation 2786 terminates the operations of this flowchart. - FIG. 59 depicts a flowchart of further
details regarding operation 2604, generation of an educated query message by the first message interface in accordance with embodiments supporting FIG. 53.Arrow 2800 directs the flow of execution from startingoperation 2604 tooperation 2802.Operation 2802 performs providing a client-to-profiler authentication key.Arrow 2804 directs execution fromoperation 2802 tooperation 2806.Operation 2806 performs encrypting the educated query message with client-to-profiler authentication key.Arrow 2808 directs execution fromoperation 2806 tooperation 2810.Operation 2810 terminates the operations of this flowchart. FIG. 60 depicts a flowchart of furtherdetails regarding operation 2638, processing the educated query message using the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 54.Arrow 2820 directs the flow of execution from startingoperation 2638 tooperation 2822.Operation 2822 performs providing a profiler-from-client authentication key.Arrow 2824 directs execution fromoperation 2822 tooperation 2826.Operation 2826 performs decrypting the received, educated query message with profiler-from-client authentication key.Arrow 2828 directs execution fromoperation 2826 tooperation 2830.Operation 2830 terminates the operations of this flowchart. - FIG. 61 depicts a flowchart of further
details regarding operation 2642, generation of a client service query message by the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 54.Arrow 2850 directs the flow of execution from startingoperation 2642 tooperation 2852.Operation 2852 performs providing profiler-from-first-service-provider authentication key.Arrow 2854 directs execution fromoperation 2852 tooperation 2856.Operation 2856 performs encrypting client service query message with profiler-from-first-service-provider authentication key.Arrow 2858 directs execution fromoperation 2856 tooperation 2860.Operation 2860 terminates the operations of this flowchart. - FIG. 62 depicts a flowchart of further
details regarding operation 2678, processing the received client service query message by the second message interface in accordance with embodiments supporting FIG. 55.Arrow 2880 directs the flow of execution from startingoperation 2678 tooperation 2882.Operation 2882 performs providing a first-service-provider-from-profiler authentication key.Arrow 2884 directs execution fromoperation 2882 tooperation 2886.Operation 2886 performs decrypting the received client service query message with the first-service-provider-from-profiler authentication key.Arrow 2888 directs execution fromoperation 2886 tooperation 2890.Operation 2890 terminates the operations of this flowchart. - FIG. 63 depicts a flowchart of further
details regarding operation 2722, copying the client response message with appended service provider billing data to the service-flow engine by the second message interface in accordance with embodiments supporting FIG. 56.Arrow 2900 directs the flow of execution from startingoperation 2722 tooperation 2902.Operation 2902 performs providing a first-service-provider-to-profiler authentication key. -
Arrow 2904 directs execution fromoperation 2902 tooperation 2906.Operation 2906 performs encrypting the client response message with appended service provider billing data with the first-service-provider-to-profiler authentication key.Arrow 2908 directs execution fromoperation 2906 tooperation 2910.Operation 2910 performs sending first-service-provider-to-profiler encrypted client response message with appended service provider billing data to the service-flow engine.Arrow 2912 directs execution fromoperation 2910 tooperation 2914.Operation 2914 terminates the operations of this flowchart. - FIG. 64 depicts a flowchart of further
details regarding operation 2748, processing the received, copied the client response message with appended service provider billing data using the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 57.Arrow 2930 directs the flow of execution from startingoperation 2748 tooperation 2932.Operation 2932 performs providing a profiler-from-first-service-provider authentication key.Arrow 2934 directs execution fromoperation 2932 tooperation 2936.Operation 2936 performs decrypting the received, copied client response message with appended service provider billing data with the profiler-from-first service provider authentication key to create the processed, received client response message with appended service provider billing data.Arrow 2938 directs execution fromoperation 2936 tooperation 2940.Operation 2940 terminates the operations of this flowchart. - FIG. 65 depicts a flowchart of further
details regarding operation 2708, generating client response message using the second message interface in accordance with embodiments supporting FIG. 56.Arrow 2950 directs the flow of execution from startingoperation 2708 tooperation 2952.Operation 2952 performs providing first-service-provider-to-client authentication key.Arrow 2954 directs execution fromoperation 2952 tooperation 2956.Operation 2956 performs generating an unencrypted client response message from the service-provider-viewable client service query message and the first-service-provider response.Arrow 2958 directs execution fromoperation 2956 tooperation 2960.Operation 2960 performs encrypt the unencrypted client response message with the first-service-provider-to-client authentication key to create the client response message.Arrow 2962 directs execution fromoperation 2960 tooperation 2964.Operation 2964 terminates the operations of this flowchart. - Note that
operations - FIG. 66 depicts a flowchart of further
details regarding operation 2778, processing the received client response message using the first message interface in accordance with embodiments supporting FIG. 58.Arrow 2980 directs the flow of execution from startingoperation 2778 tooperation 2982.Operation 2982 performs providing a client-from-first-service-provider authentication key.Arrow 2984 directs execution fromoperation 2982 tooperation 2986.Operation 2986 performs decrypting the received client response message with the client-from-first-service-provider authentication key to create the processed, received client response message.Arrow 2988 directs execution fromoperation 2986 tooperation 2990.Operation 2990 terminates the operations of this flowchart. - FIG. 67 depicts a flowchart of further
details regarding operation 2712, sending the client response message with appended service provider billing data using the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 56.Arrow 3000 directs the flow of execution from startingoperation 2712 tooperation 3002.Operation 3002 performs sending client response message destined to client to service-flow engine.Arrow 3004 directs execution fromoperation 3002 tooperation 3006.Operation 3006 terminates the operations of this flowchart. - FIG. 68 depicts a flowchart of further
details regarding operation 2708, generating the client response message using the second message interface in accordance with embodiments supporting FIG. 56.Arrow 3010 directs the flow of execution from startingoperation 2708 tooperation 3012.Operation 3012 performs providing the first-service-provider-to-profiler authentication code.Arrow 3014 directs execution fromoperation 3012 tooperation 3016.Operation 3016 performs providing the client address as destination address within the client response message, to create an unencrypted client response message with client address destination.Arrow 3018 directs execution fromoperation 3016 tooperation 3020.Operation 3020 performs encrypting the unencrypted client response message with the first-service-provider-to-profiler authentication code to create the client response message destined for the client at the corresponding client address.Arrow 3022 directs execution fromoperation 3020 tooperation 3024.Operation 3024 terminates the operations of this flowchart. - Note that
operations - FIG. 69 depicts a flowchart of operations of the service profiler process performed by the service-flow engine in accordance with alternative embodiments supporting FIG. 52.
Operation 3040 starts the operations of this flowchart.Arrow 3042 directs the flow of execution fromoperation 3040 tooperation 3044.Operation 3044 performs receiving the client response message destined for the client at the corresponding client address.Arrow 3046 directs execution fromoperation 3044 tooperation 3048.Operation 3048 performs processing the received client response message destined for the client at the corresponding client address, to create the client response message for the client at the corresponding client address.Arrow 3050 directs execution fromoperation 3048 tooperation 3052.Operation 3052 performs sending the client response message to the client at the corresponding client address.Arrow 3054 directs execution fromoperation 3052 tooperation 3056.Operation 3056 terminates the operations of this flowchart. - FIG. 70 depicts a flowchart of further
details regarding operation 3048, processing the client response message destined for the client using the service profiler process performed by the service-flow engine in accordance with embodiments supporting FIG. 69.Arrow 3070 directs the flow of execution from startingoperation 3048 tooperation 3072.Operation 3072 performs providing a profiler-from-first-service-provider authentication key.Arrow 3074 directs execution fromoperation 3072 tooperation 3076. -
Operation 3076 performs decrypting the received client response message destined for the client at the corresponding client address to create the processed, received client response message for the client at the corresponding client address.Arrow 3078 directs execution fromoperation 3076 tooperation 3080.Operation 3080 terminates the operations of this flowchart. - FIG. 71 depicts a flowchart of further
details regarding operation 2642, generating a client service query message using the service profiler process performed by the service-flow engine in accordance with embodiments.Arrow 3100 directs the flow of execution from startingoperation 2642 tooperation 3102.Operation 3102 performs selecting a first service extender from the service extenders.Arrow 3104 directs execution fromoperation 3102 tooperation 3106.Operation 3106 performs generating a second client service query message for the first service extender.Arrow 3108 directs execution fromoperation 3106 tooperation 3110.Operation 3110 performs sending the second client service query message to the first service extender at the corresponding service extender address.Arrow 3112 directs execution fromoperation 3110 tooperation 3114.Operation 3114 terminates the operations of this flowchart. - Note that in certain embodiments,
operation 3102 is based upon the received educated query message. In certain further embodiments,operation 3102 is based upon the processed, received educated query message. - FIG. 72 depicts a flowchart of operations using the third message interface on the service extender computer in accordance with embodiments supporting FIG. 57.
Operation 3150 starts the operations of this flowchart. -
Arrow 3152 directs the flow of execution fromoperation 3150 tooperation 3154.Operation 3154 performs receiving a second client message by first service extender operating a computer at the corresponding service extender address.Arrow 3156 directs execution fromoperation 3154 tooperation 3158.Operation 3158 performs processing the received second client service query message to create a processed, received second client service query message.Arrow 3160 directs execution fromoperation 3158 tooperation 3162.Operation 3162 performs generating a service extender-viewable client service query message from the processed, received second client service query message.Arrow 3164 directs execution fromoperation 3162 tooperation 3166.Operation 3166 performs displaying the service extender-viewable service query message.Arrow 3168 directs execution fromoperation 3166 tooperation 3170.Operation 3170 performs responding to the service extender-viewable service query message to create a service is extender response.Arrow 3172 directs execution fromoperation 3170 tooperation 3174.Operation 3174 performs generating the proposed client response message from service extender response.Arrow 3176 directs execution fromoperation 3174 tooperation 3178.Operation 3178 performs sending the proposed client response message to the first service provider at the corresponding service provider address.Arrow 3180 directs execution fromoperation 3178 tooperation 3182.Operation 3182 terminates the operations of this flowchart. - FIG. 73 depicts a flowchart of further
details regarding operation 2682, generating the service-provider-viewable client service query message in accordance with embodiments supporting FIGS. 55.Arrow 3200 directs the flow of execution from startingoperation 2682 tooperation 3202.Operation 3202 performs receiving proposed client response message from first service extender.Arrow 3204 directs execution fromoperation 3202 tooperation 3206.Operation 3206 performs processing the received client response message to create processed, received client response message.Arrow 3208 directs execution fromoperation 3206 tooperation 3210.Operation 3210 performs inserting the processed, received proposed client response message as part of the service-provider-viewable client service query message.Arrow 3212 directs execution fromoperation 3210 tooperation 3214.Operation 3214 terminates the operations of this flowchart. - FIG. 74 depicts a flowchart of further
details regarding operation 2708, generating the client response message using the second message interface in accordance with certain embodiments.Arrow 3220 directs the flow of execution from startingoperation 2708 tooperation 3222.Operation 3222 performs reviewing the proposed client response message.Arrow 3224 directs execution fromoperation 3222 tooperation 3226.Operation 3226 terminates the operations of this flowchart. - FIG. 75 depicts a flowchart of further operations embodying the third message interface in accordance with certain embodiments.
Arrow 3240 directs the flow of execution from startingoperation 3240 tooperation 3242.Operation 3242 performs generating a copied proposed client response message with appended service extender billing data from the service extender-viewable client service query message and first service extender response.Arrow 3244 directs execution fromoperation 3242 tooperation 3246.Operation 3246 performs sending copied proposed client response with appended service extender billing data to service-flow engine.Arrow 3248 directs execution fromoperation 3246 tooperation 3250.Operation 3250 terminates the operations of this flowchart. - FIG. 76 depicts a flowchart of further operations embodied in the message profiler process in accordance with certain embodiments.
Operation 3270 starts the operations of this flowchart.Arrow 3272 directs the flow of execution fromoperation 3270 tooperation 3274.Operation 3274 performs receiving the copied proposed client response message with the appended service extender billing data.Arrow 3276 directs execution fromoperation 3274 tooperation 3278.Operation 3278 performs processing the received copied proposed client response message with the appended service extender billing data, to create a processed, received copied proposed client response message with the appended service extender billing data.Arrow 3280 directs execution fromoperation 3278 tooperation 3282.Operation 3282 performs generating a service extender log entry in the service profile of the client from the processed, received copied client response message with the appended service extender billing data.Arrow 3284 directs execution fromoperation 3282 tooperation 3286.Operation 3286 terminates the operations of this flowchart. - FIG. 77 depicts a flowchart of further operations embodied in a second message interface in accordance with certain embodiments supporting service recommendations.
Operation 3290 starts the operations of this flowchart.Arrow 3291 directs the flow of execution fromoperation 3290 tooperation 3292.Operation 3292 performs generating an embedded service recommendation.Arrow 3293 directs execution fromoperation 3292 tooperation 3294.Operation 3294 performs inserting the embedded service recommendation into client response message.Arrow 3295 directs execution fromoperation 3294 tooperation 3296.Operation 3296 performs generating a service provider service recommendation message from the embedded service recommendation.Arrow 3297 directs execution fromoperation 3296 tooperation 3298.Operation 3298 performs sending the service provider service recommendation message to the service-flow engine.Arrow 3299 directs execution fromoperation 3298 tooperation 3300.Operation 3300 terminates the operations of this flowchart. - FIG. 78 depicts a flowchart of further operations embodied in a service profiler in accordance with certain embodiments supporting service recommendations.
Operation 3305 starts the operations of this flowchart.Arrow 3306 directs the flow of execution fromoperation 3305 tooperation 3307.Operation 3307 performs maintaining a list of suppliers, each with a corresponding supplier address.Arrow 3308 directs execution fromoperation 3307 tooperation 3309.Operation 3309 terminates the operations of this flowchart. -
Arrow 3310 directs the flow of execution from startingoperation 3305 tooperation 3311.Operation 3311 performs integrating a service order.Arrow 3312 directs execution fromoperation 3311 tooperation 3309.Operation 3309 terminates the operations of this flowchart. - Note that
arrows - FIG. 78A depicts a flowchart of further
details regarding operation 3311, integrating a service order in the service profiler process in accordance with embodiments supporting FIG. 78.Arrow 3315 directs the flow of execution from the starting ofoperation 3311 tooperation 3316.Operation 3316 performs receiving the service provider service recommendation message.Arrow 3317 directs execution fromoperation 3316 tooperation 3318.Operation 3318 performs processing the received service provider service recommendation message, to create a processed, received service provider service recommendation message. -
Arrow 3319 directs execution fromoperation 3311 tooperation 3320.Operation 3320 performs receiving a client order message.Arrow 3321 directs execution fromoperation 3320 tooperation 3322.Operation 3322 performs processing the received client order message to create a processed, received client order message. -
Arrow 3323 directs execution fromoperation 3322 tooperation 3324.Arrow 3330 directs execution fromoperation 3318 tooperation 3324. Note that in certain embodiments, botharrows operation 3324 can execute.Operation 3324 performs generating a supplier service order message from the processed, received service provider service recommendation message and the processed, received client order message.Arrow 3325 directs execution fromoperation 3324 tooperation 3326.Operation 3326 performs sending the supplier service order message to one of the suppliers at the corresponding supplier address.Arrow 3327 directs execution fromoperation 3326 tooperation 3328.Operation 3328 terminates the operations of this flowchart. - FIG. 79 depicts a flowchart of further operations embodied in the first message interface in accordance with certain embodiments supporting service recommendations.
Operation 3340 starts the operations of this flowchart.Arrow 3342 directs the flow of execution fromoperation 3340 tooperation 3344.Operation 3344 performs responding to the embedded service recommendation within the processed, received client response message.Arrow 3346 directs execution fromoperation 3344 tooperation 3348.Operation 3348 terminates the operations of this flowchart. -
Arrow 3350 directs the flow of execution from startingoperation 3340 tooperation 3352.Operation 3352 performs ordering the embedded service recommendation from the processed, received client response message.Arrow 3354 directs execution fromoperation 3352 tooperation 3348.Operation 3348 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by client choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 80 depicts a flowchart of further details of
operation 3352, ordering the embedded service recommendation of FIG. 79.Arrow 3360 directs the flow of execution from startingoperation 3352 tooperation 3362.Operation 3362 performs generating a client service recommendation message from the processed, received client response message.Arrow 3364 directs execution fromoperation 3362 tooperation 3366.Operation 3366 performs sending the client service recommendation message to the service-flow engine.Arrow 3368 directs execution fromoperation 3366 tooperation 3370.Operation 3370 terminates the operations of this flowchart. - FIG. 81 depicts a flowchart of further details of
operation 3170 of FIG. 73.Arrow 3380 directs the flow of execution from startingoperation 3170 tooperation 3382.Operation 3382 performs generating a proposed embedded service recommendation refill in the proposed client response.Arrow 3384 directs execution fromoperation 3382 tooperation 3386.Operation 3386 terminates the operations of this flowchart. - FIG. 82 depicts a flowchart of further details of
operation 3222 of FIG. 75.Arrow 3400 directs the flow of execution from startingoperation 3222 tooperation 3402.Operation 3402 performs reviewing the proposed embedded service recommendation refill.Arrow 3404 directs execution fromoperation 3402 tooperation 3406.Operation 3406 terminates the operations of this flowchart. - FIG. 83 depicts a flowchart of further details of
operation 3402 of FIG. 82.Arrow 3420 directs the flow of execution from startingoperation 3402 tooperation 3422.Operation 3422 performs approving the proposed service recommendation refill.Arrow 3424 directs execution fromoperation 3422 tooperation 3426.Operation 3426 terminates the operations of this flowchart. -
Arrow 3430 directs the flow of execution from startingoperation 3402 tooperation 3432.Operation 3432 performs revising the proposed embedded service recommendation refill.Arrow 3434 directs execution fromoperation 3432 tooperation 3426.Operation 3426 terminates the operations of this flowchart. -
Arrow 3440 directs the flow of execution from startingoperation 3402 tooperation 3442.Operation 3442 performs deleting the proposed embedded service recommendation refill.Arrow 3444 directs execution fromoperation 3442 tooperation 3426.Operation 3426 terminates the operations of this flowchart. -
Arrow 3450 directs the flow of execution from startingoperation 3402 tooperation 3452.Operation 3452 performs generating a second embedded service recommendation.Arrow 3454 directs execution fromoperation 3452 tooperation 3426.Operation 3426 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by client choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 84 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments supporting billing clients.
Operation 3470 starts the operations of this flowchart.Arrow 3472 directs the flow of execution fromoperation 3470 tooperation 3474.Operation 3474 performs generating a billing report from the client service profile.Arrow 3476 directs execution fromoperation 3474 tooperation 3478.Operation 3478 terminates the operations of this flowchart. - FIG. 85 depicts a flowchart of further operations embodying the message profiler process in accordance with certain embodiments further supporting billing clients.
Operation 3490 starts the operations of this flowchart.Arrow 3492 directs the flow of execution fromoperation 3490 tooperation 3494. -
Operation 3494 performs sending the billing report to the billing system.Arrow 3496 directs execution fromoperation 3494 tooperation 3498.Operation 3498 terminates the operations of this flowchart. - FIG. 86 depicts a flowchart of further operations embodying a billing process in accordance with certain embodiments.
Operation 3510 starts the operations of this flowchart.Arrow 3512 directs the flow of execution fromoperation 3510 tooperation 3514.Operation 3514 performs receiving the billing report for the client.Arrow 3516 directs execution fromoperation 3514 tooperation 3518.Operation 3518 performs generating a bill for the client based from the received billing report for the client.Arrow 3520 directs execution fromoperation 3518 tooperation 3522.Operation 3522 terminates the operations of this flowchart. - FIG. 87 depicts a flowchart of further details of
operation 3518 of FIG. 86.Arrow 3540 directs the flow of execution from startingoperation 3518 tooperation 3542.Operation 3542 performs generating a personal bill for the client.Arrow 3544 directs execution fromoperation 3542 tooperation 3546.Operation 3546 terminates the operations of this flowchart. -
Arrow 3550 directs the flow of execution from startingoperation 3518 tooperation 3552.Operation 3552 performs generating an insurance bill for the client to corresponding insurance provider.Arrow 3554 directs execution fromoperation 3552 tooperation 3546.Operation 3546 terminates the operations of this flowchart. - Note that a client may not have insurance, so that in such circumstances, no insurance bills would be generated. Note also, that in certain circumstances, there may be an overall insuring, such as a governmental agency, fully paying for the health costs. In such circumstances, no personal service bill might be generated. In certain alternative embodiments, the performing of these operations might not lead to output of one or the other kinds of service bills.
- FIG. 88 depicts a flowchart of further details of
operation 2704 of FIG. 56 supporting a service provider requesting a second opinion in accordance with certain embodiments.Arrow 3570 directs the flow of execution from startingoperation 2704 tooperation 3572.Operation 3572 performs generating a first-service-provider-second opinion request message.Arrow 3574 directs execution fromoperation 3572 tooperation 3576.Operation 3576 performs sending the first-service-provider-second opinion request message to the second service provider at the corresponding service provider address.Arrow 3578 directs execution fromoperation 3576 tooperation 3580.Operation 3580 terminates the operations of this flowchart. - FIG. 89 depicts a flowchart of operations embodied in the second message interface supporting a second service provider and a second opinion request in accordance with certain embodiments.
Operation 3600 starts the operations of this flowchart.Arrow 3602 directs the flow of execution fromoperation 3600 tooperation 3604.Operation 3604 performs receiving the first-service-provider-second opinion request message.Arrow 3606 directs execution fromoperation 3604 tooperation 3608.Operation 3608 performs processing the received, first-service-provider-second opinion request message to create the processed, received first-service-provider-second opinion request.Arrow 3610 directs execution fromoperation 3608 tooperation 3612.Operation 3612 performs displaying the processed, received first-service-provider-second-opinion request.Arrow 3614 directs execution fromoperation 3612 tooperation 3616.Operation 3616 performs responding to the displayed, processed, received first-service-provider-second opinion request to create a second opinion response.Arrow 3618 directs execution fromoperation 3616 tooperation 3620.Operation 3620 performs generating a second opinion message from the second opinion response.Arrow 3622 directs execution fromoperation 3620 tooperation 3624.Operation 3624 performs sending the second opinion message to the first-service-provider at the corresponding service provider address.Arrow 3626 directs execution fromoperation 3624 tooperation 3628.Operation 3628 terminates the operations of this flowchart. - FIG. 90 depicts a flowchart of operations embodied in a second message interface supporting maintaining a collection of client response templates in accordance with certain embodiments.
Operation 3640 starts the operations of this flowchart.Arrow 3642 directs the flow of execution fromoperation 3640 tooperation 3644.Operation 3644 performs creating a client response template.Arrow 3646 directs execution fromoperation 3644 tooperation 3648.Operation 3648 terminates the operations of this flowchart. -
Arrow 3650 directs the flow of execution from startingoperation 3640 tooperation 3652.Operation 3652 performs editing one of the client response templates.Arrow 3654 directs execution fromoperation 3652 tooperation 3648.Operation 3648 terminates the operations of this flowchart. -
Arrow 3660 directs the flow of execution from startingoperation 3640 tooperation 3662.Operation 3662 performs deleting one of the client response templates.Arrow 3664 directs execution fromoperation 3662 tooperation 3648.Operation 3648 terminates the operations of this flowchart. - Note that in certain embodiments, the starting operation may act as a branching mechanism. Such a mechanism can be driven by client choices via a user interface, such as buttons or pull down menus being selected or pushed.
- FIG. 91 depicts a flowchart of further details of
operation 2704 of FIG. 56 supporting use of a client response template to create a first-service-provider response in accordance with certain embodiments.Arrow 3670 directs the flow of execution from startingoperation 2704 to operation 3672. Operation 3672 performs invoking one of the client response templates in conjunction with the processed, received client service query message.Arrow 3674 directs execution from operation 3672 tooperation 3676.Operation 3676 performs responding by first service provider to invoked client response template and processed, received client service query message to create the first-service-provider response.Arrow 3678 directs execution fromoperation 3676 tooperation 3680.Operation 3680 terminates the operations of this flowchart. - FIG. 92 depicts a flowchart of operations embodied in a first message interface to support maintaining a collection of client problem templates in accordance with certain embodiments.
Operation 3700 starts the operations of this flowchart.Arrow 3702 directs the flow of execution fromoperation 3700 tooperation 3704.Operation 3704 performs receiving the client problem template from service-flow engine. Arrow 3706 directs execution fromoperation 3704 tooperation 3708.Operation 3708 performs processing the received client problem template to create a processed, received client problem template.Arrow 3710 directs execution fromoperation 3708 tooperation 3712.Operation 3712 performs adding the processed, received client problem template to the collection of client problem templates.Arrow 3714 directs execution fromoperation 3712 tooperation 3716.Operation 3716 terminates the operations of this flowchart. - FIG. 93 depicts a flowchart of further details of
operation 2604 of FIG. 53 supporting use of a client problem template to create an educated service query using a first service interface in accordance with certain embodiments.Arrow 3730 directs the flow of execution from startingoperation 2604 tooperation 3732.Operation 3732 performs invoking one of the client problem templates.Arrow 3734 directs execution fromoperation 3732 tooperation 3736.Operation 3736 performs responding by client to invoked client problem templates to create the educated query message.Arrow 3738 directs execution fromoperation 3736 tooperation 3740.Operation 3740 terminates the operations of this flowchart. - FIG. 94 depicts a flowchart of operations embodied in a service profiler process performed by a service-flow engine to generate and send client problem templates to clients in accordance with certain embodiments.
Operation 3760 starts the operations of this flowchart.Arrow 3762 directs the flow of execution fromoperation 3760 tooperation 3764.Operation 3764 performs generating a client problem template from the client service profile.Arrow 3766 directs execution fromoperation 3764 tooperation 3768.Operation 3768 performs sending the client problem template to the client at the corresponding client address.Arrow 3770 directs execution fromoperation 3768 tooperation 3772.Operation 3772 terminates the operations of this flowchart. - FIG. 95 depicts a flow diagram of a service profiler process in accordance with certain embodiments.
Box 3800 designates a Service Profiler Process Dispatcher. This communicates viaphysical transport mechanism 3802 tonetwork 3804.Box 3808 designatesService profiler sub-process 1 on service-flow engine 1, performing theoperation 2630 of FIG. 54. This communicates viaphysical transport mechanism 3806 tonetwork 3804.Box 3812 designatesService profiler sub-process 2 on service-flow engine 2, performing theoperation 2740 of FIG. 57. This communicates viaphysical transport mechanism 3810 tonetwork 3804.Box 3816 designatesService profiler sub-process 3 on service-flow engine 3, performing theoperation 3040 of FIG. 69. This communicates viaphysical transport mechanism 3814 tonetwork 3804.Box 3820 designatesService profiler sub-process 4 on service-flow engine 4, performing theoperation 3270 of FIG. 76. This communicates viaphysical transport mechanism 3818 tonetwork 3804.Box 3824 designatesService profiler sub-process 5 on service-flow engine 5, performing theoperation 3470 of FIG. 84. This communicates viaphysical transport mechanism 3822 tonetwork 3804.Box 3828 designatesService profiler sub-process 6 on service-flow engine 6, performing theoperation 3490 of FIG. 85. This communicates viaphysical transport mechanism 3826 tonetwork 3804.Box 3832 designatesService profiler sub-process 7 on service-flow engine 7, performing theoperation 3760 of FIG. 94. This communicates viaphysical transport mechanism 3830 tonetwork 3804. - Note that in certain alternative embodiments, collections of these subprocesses may preferably reside on a single service-flow engine. Note that in certain other embodiments, multiple service-flow engines may be performing a given sub-process.
- FIG. 96 depicts a flow diagram of a computer program capable of receiving a message from a service provider containing a service recommendation and responding to the message containing the service recommendation in accordance with an aspect of the invention.
Operation 3850 starts the operations of this flowchart.Arrow 3852 directs the flow of execution fromoperation 3850 tooperation 3854.Operation 3854 performs receiving the client message with an embedded service recommendation.Arrow 3856 directs execution fromoperation 3854 tooperation 3858.Operation 3858 performs displaying the received client message with embedded service recommendation.Arrow 3860 directs execution fromoperation 3858 tooperation 3862.Operation 3862 performs responding to the client message with embedded service recommendation.Arrow 3864 directs execution fromoperation 3862 tooperation 3866.Operation 3866 terminates the operations of this flowchart. - FIG. 97 depicts a flowchart of further details of the code of3854 of FIG. 96 supporting receiving a client message with an embedded service recommendation in accordance with certain embodiments.
Arrow 3880 directs the flow of execution from startingoperation 3854 tooperation 3882.Operation 3882 performs receiving an encrypted client message with embedded service recommendation.Arrow 3884 directs execution fromoperation 3882 tooperation 3886.Operation 3886 performs processing the received, encrypted client message with embedded service recommendation to create the received client message with embedded service recommendation.Arrow 3888 directs execution fromoperation 3886 tooperation 3890.Operation 3890 terminates the operations of this flowchart. - FIG. 98 depicts a flowchart of further details of the code of3862 of FIG. 96 supporting responding to the client response message in accordance with certain embodiments.
Arrow 3900 directs the flow of execution from startingoperation 3862 tooperation 3902.Operation 3902 performs generating a client service recommendation message from said embedded service recommendation.Arrow 3904 directs execution fromoperation 3902 tooperation 3906.Operation 3906 performs sending said client service recommendation message to said service-flow engine.Arrow 3908 directs execution fromoperation 3906 tooperation 3910.Operation 3910 terminates the operations of this flowchart. - FIG. 98A depicts a flowchart of further details of3311 of FIG. 78 supporting integrating a service order in accordance with certain embodiments.
-
Arrow 3920 directs the flow of execution from startingoperation 3311 tooperation 3922.Operation 3922 determines if the received client response message contains an embedded service recommendation.Arrow 3924 directs execution fromoperation 3922 tooperation 3926.Arrow 3924 directs execution when the determination is ‘Yes’ tooperation 3926.Arrow 3954 directs execution when the determination is ‘No’ tooperation 3946. -
Operation 3926 performs receiving the client service order message from the first client.Arrow 3928 directs execution fromoperation 3926 tooperation 3930.Operation 3930 determines if the client service order message from the first client is compatible with the embedded service recommendation contained in the received client response message.Arrow 3932 directs execution fromoperation 3930 tooperation 3934.Arrow 3932 directs execution when the determination is ‘Yes’ tooperation 3934.Arrow 3956 directs execution when the determination is ‘No’ tooperation 3946.Operation 3934 determines if the client service order received from the first client authorizes the service order.Arrow 3936 directs execution fromoperation 3934 tooperation 3938.Arrow 3936 directs execution when the determination is ‘Yes’ tooperation 3938.Arrow 3958 directs execution when the determination is ‘No’ tooperation 3946. -
Operation 3938 determines a first pharmacy from the client service order.Arrow 3940 directs execution fromoperation 3938 tooperation 3942.Operation 3942 performs generates and sends the service order message to the first pharmacy based upon the received client response message and the received client service order message.Arrow 3944 directs execution fromoperation 3942 tooperation 3946.Operation 3946 terminates the operations of this flowchart. - FIG. 98B depicts a flowchart of further details of3324 of FIG. 78A supporting generating a pharmacy service order in accordance with certain embodiments.
-
Arrow 3960 directs the flow of execution from startingoperation 1324 tooperation 3962.Operation 3962 determines if the processed, received client service order is compatible with the processed, received service provider service recommendation.Arrow 3964 directs execution when the determination is ‘Yes’ tooperation 3966.Arrow 3978 directs usage when the determination is ‘No’ tooperation 3970. -
Operation 3966 generates a pharmacy service order message from the processed, received service provider service recommendation message and the processed, received client service order.Arrow 3968 directs execution fromoperation 3966 tooperation 3970.Operation 3970 terminates the operations of this flowchart. - FIG. 98C depicts a flowchart of further details of3326 of FIG. 78A supporting sending a pharmacy service order to a pharmacy in accordance with certain embodiments.
-
Arrow 3980 directs the flow of execution from startingoperation 3326 tooperation 3962.Operation 3962 determines if the processed, received client service order is compatible with the processed, received service provider service recommendation.Arrow 3984 directs execution fromoperation 3962 tooperation 3986.Arrow 3984 directs execution when the determination is ‘Yes’ tooperation 3986.Arrow 3998 directs usage when the determination is ‘No’ tooperation 3994. -
Operation 3986 performs determine the first pharmacy from the processed, received client service order.Arrow 3988 directs execution fromoperation 3986 tooperation 3990.Operation 3990 performs sending the pharmacy service order message to the first pharmacy.Arrow 3992 directs execution fromoperation 3990 tooperation 3994.Operation 3994 terminates the operations of this flowchart. - FIG. 98D depicts a flowchart of further details of3106 of FIG. 71 supporting determining a routing chain of service extenders and embedding the routing chain into a second client query in accordance with certain embodiments.
-
Arrow 4010 directs the flow of execution from startingoperation 1106 tooperation 4012.Operation 4012 determines a routing chain of service extenders.Arrow 4014 directs execution fromoperation 4012 tooperation 4016.Operation 4016 embeds the routing chain of service extenders into the second service query.Arrow 4018 directs execution fromoperation 4016 tooperation 4020.Operation 4020 terminates the operations of this flowchart. - Note that a routing chain of service extenders is a collection of at least one service extender to whom the second client query will be routed after the first service extender has added their proposed response to the client query.
- FIG. 98E depicts a flowchart of further details of3178 of FIG. 72 supporting determining successor service extenders in an embedded service extender routing chain, generating a successor service query message with embedded proposed client response and sending the successor client service query to the successor service extender.
-
Arrow 4030 directs the flow of execution from startingoperation 1178 tooperation 4032.Operation 4032 determines if there is a successor service extender in the embedded service extender chain.Arrow 4034 directs execution fromoperation 4032 tooperation 4036.Arrow 4034 directs execution when the determination is ‘Yes’ tooperation 4032.Arrow 4048 directs execution when the determination is ‘No’ tooperation 4044. -
Operation 4036 generates the successor service query message with the embedded proposed client response.Arrow 4038 directs execution fromoperation 4036 tooperation 4040.Operation 4040 send the successor client service query to the successor service extender.Arrow 4042 directs execution fromoperation 4040 tooperation 4044.Operation 4044 terminates the operations of this flowchart. - FIG. 98F depicts a flowchart of further details of2646 of FIG. 54 supporting generating a routing tree of service providers with first service provider final destination and source list of service providers, generating and sending a source service query to each service provider included in the service provider source list.
-
Arrow 4060 directs the flow of execution from startingoperation 646 tooperation 4062.Operation 4062 performs generating a routing tree of service providers with the first service provider the final destination of the routing tree and a source list of service providers of the routing tree.Arrow 4064 directs execution fromoperation 4062 tooperation 4066.Operation 4066 performs generating and sending a source service query for and to each service provider belonging to the source list of the routing tree.Arrow 4068 directs execution fromoperation 4066 tooperation 4070.Operation 4070 terminates the operations of this flowchart.
Claims (42)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/017,165 US20020062230A1 (en) | 1999-09-13 | 2001-12-14 | Message and program system supporting communication |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US39434199A | 1999-09-13 | 1999-09-13 | |
US10/017,165 US20020062230A1 (en) | 1999-09-13 | 2001-12-14 | Message and program system supporting communication |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US39434199A Division | 1999-03-22 | 1999-09-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020062230A1 true US20020062230A1 (en) | 2002-05-23 |
Family
ID=23558542
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/017,165 Abandoned US20020062230A1 (en) | 1999-09-13 | 2001-12-14 | Message and program system supporting communication |
US11/526,205 Expired - Fee Related US7809584B2 (en) | 1999-09-13 | 2006-09-21 | Message and program system supporting communication |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/526,205 Expired - Fee Related US7809584B2 (en) | 1999-09-13 | 2006-09-21 | Message and program system supporting communication |
Country Status (5)
Country | Link |
---|---|
US (2) | US20020062230A1 (en) |
EP (1) | EP1415259A2 (en) |
AU (1) | AU6802000A (en) |
CA (1) | CA2385683A1 (en) |
WO (1) | WO2001024098A2 (en) |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020171865A1 (en) * | 2001-05-18 | 2002-11-21 | Parry Travis J. | Image forming devices and methods of obtaining medication information |
US20030050797A1 (en) * | 2001-09-12 | 2003-03-13 | Siemens Medical Solutions Health Services Corporation | System and user interface for processing healthcare related event information |
US20030125987A1 (en) * | 2001-12-28 | 2003-07-03 | Siemens Medical Solutions Health Services Corporation | System and method for managing healthcare communication |
US20030149599A1 (en) * | 2002-02-01 | 2003-08-07 | Charles Goodall | Method and apparatus for prescription processing |
US20040172289A1 (en) * | 2003-02-28 | 2004-09-02 | Dejan Kozic | Method and system for remotely verifying a prescription |
US20060041330A1 (en) * | 2004-08-18 | 2006-02-23 | Walgreen Co. | System and method for checking the accuracy of a prescription fill |
US20060241355A1 (en) * | 2004-12-20 | 2006-10-26 | Howell Thomas A | Healthcare base |
US20070074018A1 (en) * | 2005-09-23 | 2007-03-29 | Scansafe Limited | Network communications |
US20070088590A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for out of stock medication |
US20070088565A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for medication payments |
US20070088594A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing |
US20070088569A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for prescription verification |
US20070088568A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing using resource function assignments |
US20070088567A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for compound medication |
US20070088566A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for specialty medication |
US20070225578A1 (en) * | 2006-03-24 | 2007-09-27 | Howell Thomas A | Medical monitoring system |
US20080103836A1 (en) * | 2006-10-31 | 2008-05-01 | Athenahealth, Inc. | Medical document attachment handling |
US20080270186A1 (en) * | 2004-08-24 | 2008-10-30 | Soren Mikkelsen | Giving a Service to a Patient |
US20080306761A1 (en) * | 2007-06-07 | 2008-12-11 | Walgreen Co. | System and Method of Performing Remote Verification of a Prescription in Combination with a Patient Access Terminal |
US20090018867A1 (en) * | 2004-07-09 | 2009-01-15 | Bruce Reiner | Gesture-based communication and reporting system |
US20090030722A1 (en) * | 2007-07-25 | 2009-01-29 | Walgreen Co. | System and method for performing a remote verification of a pharmacy fill utilizing an image to image comparison |
US20090125326A1 (en) * | 2007-11-13 | 2009-05-14 | Wasson David S | Method and apparatus for indirect medical consultation |
US20090167553A1 (en) * | 2007-12-30 | 2009-07-02 | Jin Hong | Open Mobile Online Reservation and Ordering Systems |
US20100049753A1 (en) * | 2005-12-19 | 2010-02-25 | Commvault Systems, Inc. | Systems and methods for monitoring application data in a data replication system |
US20100082979A1 (en) * | 2005-09-23 | 2010-04-01 | Scansafe Limited | Method for the provision of a network service |
US20100125461A1 (en) * | 2008-11-14 | 2010-05-20 | Walgreen Co. | System and Method of Using a Non-Retail Central Filling Facility to Process Pharmacy Product Prescriptions in a Pharmacy Retail Network |
US7769601B1 (en) * | 1999-11-15 | 2010-08-03 | Walgreen Co. | Apparatus and method for accessing pharmacy information and ordering prescriptions |
US20110137679A1 (en) * | 2009-12-09 | 2011-06-09 | International Business Machines Corporation | Method to transform clinician order entry |
US8145501B1 (en) | 2008-10-09 | 2012-03-27 | Walgreen Co. | System and method for performing pharmacy product filling using non-registered pharmacists |
US8190565B2 (en) | 2003-11-13 | 2012-05-29 | Commvault Systems, Inc. | System and method for performing an image level snapshot and for restoring partial volume data |
US8204859B2 (en) | 2008-12-10 | 2012-06-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
US8271830B2 (en) | 2005-12-19 | 2012-09-18 | Commvault Systems, Inc. | Rolling cache configuration for a data replication system |
US8285684B2 (en) | 2005-12-19 | 2012-10-09 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8290808B2 (en) * | 2007-03-09 | 2012-10-16 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US8352422B2 (en) | 2010-03-30 | 2013-01-08 | Commvault Systems, Inc. | Data restore systems and methods in a replication environment |
US8463751B2 (en) | 2005-12-19 | 2013-06-11 | Commvault Systems, Inc. | Systems and methods for performing replication copy storage operations |
US8489656B2 (en) | 2010-05-28 | 2013-07-16 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8504517B2 (en) | 2010-03-29 | 2013-08-06 | Commvault Systems, Inc. | Systems and methods for selective data replication |
US8504515B2 (en) | 2010-03-30 | 2013-08-06 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
US8655850B2 (en) | 2005-12-19 | 2014-02-18 | Commvault Systems, Inc. | Systems and methods for resynchronizing information |
US8666780B2 (en) | 2005-10-18 | 2014-03-04 | Walgreen Co. | System for separating and distributing pharmacy order processing |
US8726242B2 (en) | 2006-07-27 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
US8725698B2 (en) | 2010-03-30 | 2014-05-13 | Commvault Systems, Inc. | Stub file prioritization in a data replication system |
US20150112722A1 (en) * | 2013-10-21 | 2015-04-23 | OSIA Medical, Inc. | Medical condition tracking and analysis |
US9495382B2 (en) | 2008-12-10 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods for performing discrete data replication |
US20170228516A1 (en) * | 2012-09-20 | 2017-08-10 | Masimo Corporation | Intelligent medical escalation process |
US20170357774A1 (en) * | 2016-06-08 | 2017-12-14 | David FIGG | Automated prescription communication system and method |
US10580279B2 (en) | 2012-12-31 | 2020-03-03 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US10607728B2 (en) * | 2015-10-06 | 2020-03-31 | Cerner Innovation, Inc. | Alert optimizer |
US10635260B2 (en) | 2007-01-22 | 2020-04-28 | Cerner Innovation, Inc. | System and user interface for clinical reporting and ordering provision of an item |
US10642460B2 (en) | 2012-10-05 | 2020-05-05 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US10699812B2 (en) | 2015-12-30 | 2020-06-30 | Cerner Innovation, Inc. | Intelligent alert suppression |
US11042318B2 (en) | 2019-07-29 | 2021-06-22 | Commvault Systems, Inc. | Block-level data replication |
US11109818B2 (en) | 2018-04-19 | 2021-09-07 | Masimo Corporation | Mobile patient alarm display |
US11238064B2 (en) | 2016-03-10 | 2022-02-01 | Commvault Systems, Inc. | Snapshot replication operations based on incremental block change tracking |
US11269543B2 (en) | 2012-04-23 | 2022-03-08 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
US11422732B2 (en) | 2018-02-14 | 2022-08-23 | Commvault Systems, Inc. | Live browsing and private writable environments based on snapshots and/or backup copies provided by an ISCSI server |
US11488711B2 (en) | 2013-10-11 | 2022-11-01 | Masimo Corporation | Alarm notification system |
US11507470B2 (en) | 2014-11-14 | 2022-11-22 | Commvault Systems, Inc. | Unified snapshot storage management |
US11809285B2 (en) | 2022-02-09 | 2023-11-07 | Commvault Systems, Inc. | Protecting a management database of a data storage management system to meet a recovery point objective (RPO) |
US11847026B2 (en) | 2013-01-11 | 2023-12-19 | Commvault Systems, Inc. | Single snapshot for multiple agents |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7590971B2 (en) | 2003-08-01 | 2009-09-15 | Idx Investment Corporation | Enterprise task manager |
US8533004B1 (en) | 2004-09-10 | 2013-09-10 | Ldm Group, Llc | Systems and methods for patient communications in conjunction with prescription medications |
US8781848B1 (en) | 2004-09-10 | 2014-07-15 | Ldm Group, Llc | Systems and methods for providing an inducement of a purchase in conjunction with a prescription |
US7809761B2 (en) | 2005-10-11 | 2010-10-05 | Idx Investment Corporation | Data object tracking system and method |
US20090259492A1 (en) * | 2008-04-09 | 2009-10-15 | Strategic Medical, Llc | Remote Consultation System and Method |
US8812599B2 (en) * | 2011-01-10 | 2014-08-19 | Epic Systems Corporation | Networked inbox |
US10114621B2 (en) * | 2011-01-11 | 2018-10-30 | Entit Software Llc | Methods and apparatus to generate a wizard application |
US20130268284A1 (en) * | 2012-04-05 | 2013-10-10 | Ryan Heck | System and Method for Transferring Patients Between Hospitals |
US20150134343A1 (en) * | 2012-05-16 | 2015-05-14 | Andrew Michael Kluger | Interactive Communications System for the Coordination and Management of patient-Centered Health Care Services |
US8538780B1 (en) * | 2012-11-26 | 2013-09-17 | Sweeney Healthcare Enterprises, LLC | System for identifying and addressing concerns of medical patients |
US9037578B2 (en) | 2012-12-03 | 2015-05-19 | Wellclub, Llc | Content suggestion engine |
US10521559B1 (en) * | 2013-10-18 | 2019-12-31 | Advanced Health Communications, L.L.C. | Advanced healthcare information routing and delivery systems and methods of use and doing business |
Citations (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4491725A (en) * | 1982-09-29 | 1985-01-01 | Pritchard Lawrence E | Medical insurance verification and processing system |
US4513382A (en) * | 1982-08-17 | 1985-04-23 | Westinghouse Electric Corp. | Electric utility automated distribution apparatus with improved data display |
US4873687A (en) * | 1987-10-05 | 1989-10-10 | Ibm Corporation | Failing resource manager in a multiplex communication system |
US5255187A (en) * | 1990-04-03 | 1993-10-19 | Sorensen Mark C | Computer aided medical diagnostic method and apparatus |
US5277188A (en) * | 1991-06-26 | 1994-01-11 | New England Medical Center Hospitals, Inc. | Clinical information reporting system |
US5301105A (en) * | 1991-04-08 | 1994-04-05 | Desmond D. Cummings | All care health management system |
US5469353A (en) * | 1993-11-26 | 1995-11-21 | Access Radiology Corp. | Radiological image interpretation apparatus and method |
US5542420A (en) * | 1993-04-30 | 1996-08-06 | Goldman; Arnold J. | Personalized method and system for storage, communication, analysis, and processing of health-related data |
US5594638A (en) * | 1993-12-29 | 1997-01-14 | First Opinion Corporation | Computerized medical diagnostic system including re-enter function and sensitivity factors |
US5619991A (en) * | 1995-04-26 | 1997-04-15 | Lucent Technologies Inc. | Delivery of medical services using electronic data communications |
US5630125A (en) * | 1994-05-23 | 1997-05-13 | Zellweger; Paul | Method and apparatus for information management using an open hierarchical data structure |
US5660176A (en) * | 1993-12-29 | 1997-08-26 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system |
US5666492A (en) * | 1995-01-17 | 1997-09-09 | Glaxo Wellcome Inc. | Flexible computer based pharmaceutical care cognitive services management system and method |
US5711297A (en) * | 1993-12-29 | 1998-01-27 | First Opinion Corporation | Computerized medical advice system and method including meta function |
US5737539A (en) * | 1994-10-28 | 1998-04-07 | Advanced Health Med-E-Systems Corp. | Prescription creation system |
US5748907A (en) * | 1993-10-25 | 1998-05-05 | Crane; Harold E. | Medical facility and business: automatic interactive dynamic real-time management |
US5758095A (en) * | 1995-02-24 | 1998-05-26 | Albaum; David | Interactive medication ordering system |
US5797515A (en) * | 1995-10-18 | 1998-08-25 | Adds, Inc. | Method for controlling a drug dispensing system |
US5825881A (en) * | 1996-06-28 | 1998-10-20 | Allsoft Distributing Inc. | Public network merchandising system |
US5823948A (en) * | 1996-07-08 | 1998-10-20 | Rlis, Inc. | Medical records, documentation, tracking and order entry system |
US5845255A (en) * | 1994-10-28 | 1998-12-01 | Advanced Health Med-E-Systems Corporation | Prescription management system |
US5851182A (en) * | 1996-09-11 | 1998-12-22 | Sahadevan; Velayudhan | Megavoltage radiation therapy machine combined to diagnostic imaging devices for cost efficient conventional and 3D conformal radiation therapy with on-line Isodose port and diagnostic radiology |
US5890129A (en) * | 1997-05-30 | 1999-03-30 | Spurgeon; Loren J. | System for exchanging health care insurance information |
US5897493A (en) * | 1997-03-28 | 1999-04-27 | Health Hero Network, Inc. | Monitoring system for remotely querying individuals |
US5911687A (en) * | 1995-11-15 | 1999-06-15 | Hitachi, Ltd. | Wide area medical information system and method using thereof |
US5987480A (en) * | 1996-07-25 | 1999-11-16 | Donohue; Michael | Method and system for delivering documents customized for a particular user over the internet using imbedded dynamic content |
US5991731A (en) * | 1997-03-03 | 1999-11-23 | University Of Florida | Method and system for interactive prescription and distribution of prescriptions in conducting clinical studies |
US6006191A (en) * | 1996-05-13 | 1999-12-21 | Dirienzo; Andrew L. | Remote access medical image exchange system and methods of operation therefor |
US6014631A (en) * | 1998-04-02 | 2000-01-11 | Merck-Medco Managed Care, Llc | Computer implemented patient medication review system and process for the managed care, health care and/or pharmacy industry |
US6039688A (en) * | 1996-11-01 | 2000-03-21 | Salus Media Inc. | Therapeutic behavior modification program, compliance monitoring and feedback system |
US6112247A (en) * | 1997-11-18 | 2000-08-29 | Intel Corporation | Network controller for processing status queries |
US6149585A (en) * | 1998-10-28 | 2000-11-21 | Sage Health Management Solutions, Inc. | Diagnostic enhancement method and apparatus |
US6154444A (en) * | 1996-10-25 | 2000-11-28 | Nec Corporation | Source routing method for fast connection re-establishment in response to early-arriving trouble report messages |
US6253326B1 (en) * | 1998-05-29 | 2001-06-26 | Palm, Inc. | Method and system for secure communications |
US6256613B1 (en) * | 1997-03-14 | 2001-07-03 | Health Resources And Technology Inc. | Medical consultation management system |
US6302844B1 (en) * | 1999-03-31 | 2001-10-16 | Walker Digital, Llc | Patient care delivery system |
US20010037219A1 (en) * | 2000-04-27 | 2001-11-01 | Malik Stephen Nabeil | Systems, methods and computer program products for facilitating one-to-one secure on-line communications between professional services providers and remotely located clients |
US6330491B1 (en) * | 1999-07-21 | 2001-12-11 | Nicholas Lion | Integrated system and method of vending prescription medications using a network of remotely distributed, automated dispensing units |
US6343318B1 (en) * | 1998-05-29 | 2002-01-29 | Palm, Inc. | Method and apparatus for communicating information over low bandwidth communications networks |
US6363393B1 (en) * | 1998-02-23 | 2002-03-26 | Ron Ribitzky | Component based object-relational database infrastructure and user interface |
US20020065682A1 (en) * | 1999-05-18 | 2002-05-30 | David M. Goldenberg | Virtual doctor interactive cybernet system |
US6405037B1 (en) * | 1995-12-11 | 2002-06-11 | Openwave Systems Inc. | Method and architecture for an interactive two-way data communication network |
US6493427B1 (en) * | 1998-06-16 | 2002-12-10 | Telemanager Technologies, Inc. | Remote prescription refill system |
US20030018495A1 (en) * | 2001-07-11 | 2003-01-23 | Lester Sussman | System and method for medical drug prescription acquisition |
US20030028399A1 (en) * | 2000-09-25 | 2003-02-06 | Duane Davis | Method and system for providing interactive health care services |
US6584445B2 (en) * | 1998-10-22 | 2003-06-24 | Computerized Health Evaluation Systems, Inc. | Medical system for shared patient and physician decision making |
US7251609B1 (en) * | 1999-04-29 | 2007-07-31 | The Trustees Of Boston University | Method for conducting clinical trials over the internet |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995029455A1 (en) | 1994-04-21 | 1995-11-02 | Fillingane Sam D O | Electronic hand-held prescription writing and transmitting device |
JPH0919467A (en) | 1995-07-05 | 1997-01-21 | Matsushita Electric Ind Co Ltd | Patient information system |
IL131873A0 (en) * | 1997-03-13 | 2001-03-19 | First Opinion Corp | Disease management system |
-
2000
- 2000-08-29 AU AU68020/00A patent/AU6802000A/en not_active Abandoned
- 2000-08-29 EP EP00955897A patent/EP1415259A2/en not_active Withdrawn
- 2000-08-29 WO PCT/US2000/023730 patent/WO2001024098A2/en not_active Application Discontinuation
- 2000-08-29 CA CA002385683A patent/CA2385683A1/en not_active Abandoned
-
2001
- 2001-12-14 US US10/017,165 patent/US20020062230A1/en not_active Abandoned
-
2006
- 2006-09-21 US US11/526,205 patent/US7809584B2/en not_active Expired - Fee Related
Patent Citations (49)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4513382A (en) * | 1982-08-17 | 1985-04-23 | Westinghouse Electric Corp. | Electric utility automated distribution apparatus with improved data display |
US4491725A (en) * | 1982-09-29 | 1985-01-01 | Pritchard Lawrence E | Medical insurance verification and processing system |
US4873687A (en) * | 1987-10-05 | 1989-10-10 | Ibm Corporation | Failing resource manager in a multiplex communication system |
US5255187A (en) * | 1990-04-03 | 1993-10-19 | Sorensen Mark C | Computer aided medical diagnostic method and apparatus |
US5301105A (en) * | 1991-04-08 | 1994-04-05 | Desmond D. Cummings | All care health management system |
US5277188A (en) * | 1991-06-26 | 1994-01-11 | New England Medical Center Hospitals, Inc. | Clinical information reporting system |
US5542420A (en) * | 1993-04-30 | 1996-08-06 | Goldman; Arnold J. | Personalized method and system for storage, communication, analysis, and processing of health-related data |
US5748907A (en) * | 1993-10-25 | 1998-05-05 | Crane; Harold E. | Medical facility and business: automatic interactive dynamic real-time management |
US5469353A (en) * | 1993-11-26 | 1995-11-21 | Access Radiology Corp. | Radiological image interpretation apparatus and method |
US5724968A (en) * | 1993-12-29 | 1998-03-10 | First Opinion Corporation | Computerized medical diagnostic system including meta function |
US5660176A (en) * | 1993-12-29 | 1997-08-26 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system |
US5594638A (en) * | 1993-12-29 | 1997-01-14 | First Opinion Corporation | Computerized medical diagnostic system including re-enter function and sensitivity factors |
US5711297A (en) * | 1993-12-29 | 1998-01-27 | First Opinion Corporation | Computerized medical advice system and method including meta function |
US5868669A (en) * | 1993-12-29 | 1999-02-09 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system |
US5630125A (en) * | 1994-05-23 | 1997-05-13 | Zellweger; Paul | Method and apparatus for information management using an open hierarchical data structure |
US5737539A (en) * | 1994-10-28 | 1998-04-07 | Advanced Health Med-E-Systems Corp. | Prescription creation system |
US5845255A (en) * | 1994-10-28 | 1998-12-01 | Advanced Health Med-E-Systems Corporation | Prescription management system |
US5666492A (en) * | 1995-01-17 | 1997-09-09 | Glaxo Wellcome Inc. | Flexible computer based pharmaceutical care cognitive services management system and method |
US5758095A (en) * | 1995-02-24 | 1998-05-26 | Albaum; David | Interactive medication ordering system |
US5619991A (en) * | 1995-04-26 | 1997-04-15 | Lucent Technologies Inc. | Delivery of medical services using electronic data communications |
US5797515A (en) * | 1995-10-18 | 1998-08-25 | Adds, Inc. | Method for controlling a drug dispensing system |
US5911687A (en) * | 1995-11-15 | 1999-06-15 | Hitachi, Ltd. | Wide area medical information system and method using thereof |
US6405037B1 (en) * | 1995-12-11 | 2002-06-11 | Openwave Systems Inc. | Method and architecture for an interactive two-way data communication network |
US6006191A (en) * | 1996-05-13 | 1999-12-21 | Dirienzo; Andrew L. | Remote access medical image exchange system and methods of operation therefor |
US5825881A (en) * | 1996-06-28 | 1998-10-20 | Allsoft Distributing Inc. | Public network merchandising system |
US5823948A (en) * | 1996-07-08 | 1998-10-20 | Rlis, Inc. | Medical records, documentation, tracking and order entry system |
US5987480A (en) * | 1996-07-25 | 1999-11-16 | Donohue; Michael | Method and system for delivering documents customized for a particular user over the internet using imbedded dynamic content |
US5851182A (en) * | 1996-09-11 | 1998-12-22 | Sahadevan; Velayudhan | Megavoltage radiation therapy machine combined to diagnostic imaging devices for cost efficient conventional and 3D conformal radiation therapy with on-line Isodose port and diagnostic radiology |
US6154444A (en) * | 1996-10-25 | 2000-11-28 | Nec Corporation | Source routing method for fast connection re-establishment in response to early-arriving trouble report messages |
US6039688A (en) * | 1996-11-01 | 2000-03-21 | Salus Media Inc. | Therapeutic behavior modification program, compliance monitoring and feedback system |
US5991731A (en) * | 1997-03-03 | 1999-11-23 | University Of Florida | Method and system for interactive prescription and distribution of prescriptions in conducting clinical studies |
US6256613B1 (en) * | 1997-03-14 | 2001-07-03 | Health Resources And Technology Inc. | Medical consultation management system |
US5897493A (en) * | 1997-03-28 | 1999-04-27 | Health Hero Network, Inc. | Monitoring system for remotely querying individuals |
US5890129A (en) * | 1997-05-30 | 1999-03-30 | Spurgeon; Loren J. | System for exchanging health care insurance information |
US6112247A (en) * | 1997-11-18 | 2000-08-29 | Intel Corporation | Network controller for processing status queries |
US6363393B1 (en) * | 1998-02-23 | 2002-03-26 | Ron Ribitzky | Component based object-relational database infrastructure and user interface |
US6014631A (en) * | 1998-04-02 | 2000-01-11 | Merck-Medco Managed Care, Llc | Computer implemented patient medication review system and process for the managed care, health care and/or pharmacy industry |
US6343318B1 (en) * | 1998-05-29 | 2002-01-29 | Palm, Inc. | Method and apparatus for communicating information over low bandwidth communications networks |
US6253326B1 (en) * | 1998-05-29 | 2001-06-26 | Palm, Inc. | Method and system for secure communications |
US6493427B1 (en) * | 1998-06-16 | 2002-12-10 | Telemanager Technologies, Inc. | Remote prescription refill system |
US6584445B2 (en) * | 1998-10-22 | 2003-06-24 | Computerized Health Evaluation Systems, Inc. | Medical system for shared patient and physician decision making |
US6149585A (en) * | 1998-10-28 | 2000-11-21 | Sage Health Management Solutions, Inc. | Diagnostic enhancement method and apparatus |
US6302844B1 (en) * | 1999-03-31 | 2001-10-16 | Walker Digital, Llc | Patient care delivery system |
US7251609B1 (en) * | 1999-04-29 | 2007-07-31 | The Trustees Of Boston University | Method for conducting clinical trials over the internet |
US20020065682A1 (en) * | 1999-05-18 | 2002-05-30 | David M. Goldenberg | Virtual doctor interactive cybernet system |
US6330491B1 (en) * | 1999-07-21 | 2001-12-11 | Nicholas Lion | Integrated system and method of vending prescription medications using a network of remotely distributed, automated dispensing units |
US20010037219A1 (en) * | 2000-04-27 | 2001-11-01 | Malik Stephen Nabeil | Systems, methods and computer program products for facilitating one-to-one secure on-line communications between professional services providers and remotely located clients |
US20030028399A1 (en) * | 2000-09-25 | 2003-02-06 | Duane Davis | Method and system for providing interactive health care services |
US20030018495A1 (en) * | 2001-07-11 | 2003-01-23 | Lester Sussman | System and method for medical drug prescription acquisition |
Cited By (131)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8364504B1 (en) | 1999-11-15 | 2013-01-29 | Walgreen Co. | Pharmacy network management system and method for ordering prescriptions |
US10235499B1 (en) | 1999-11-15 | 2019-03-19 | Walgreen Co. | Pharmacy network management system and method for refilling prescriptions |
US7769601B1 (en) * | 1999-11-15 | 2010-08-03 | Walgreen Co. | Apparatus and method for accessing pharmacy information and ordering prescriptions |
US7774134B1 (en) | 1999-11-15 | 2010-08-10 | Walgreen Co. | Pharmacy network management system and method for searching for a pharmacy store location with a drive through |
US8510131B1 (en) | 1999-11-15 | 2013-08-13 | Walgreen Co. | Pharmacy network management system and method for refilling prescriptions |
US8055513B1 (en) | 1999-11-15 | 2011-11-08 | Walgreen Co. | Pharmacy network management system and method for searching for a pharmacy store location |
US20020171865A1 (en) * | 2001-05-18 | 2002-11-21 | Parry Travis J. | Image forming devices and methods of obtaining medication information |
US7184155B2 (en) * | 2001-05-18 | 2007-02-27 | Hewlett-Packard Development Company, L.P. | Image forming devices and methods of obtaining medication information |
US7447644B2 (en) * | 2001-09-12 | 2008-11-04 | Siemens Medical Solutions Usa, Inc. | System and user interface for processing healthcare related event information |
US20030050797A1 (en) * | 2001-09-12 | 2003-03-13 | Siemens Medical Solutions Health Services Corporation | System and user interface for processing healthcare related event information |
US20030125987A1 (en) * | 2001-12-28 | 2003-07-03 | Siemens Medical Solutions Health Services Corporation | System and method for managing healthcare communication |
US7451096B2 (en) * | 2001-12-28 | 2008-11-11 | Siemens Medical Solution Usa, Inc. | System and method for managing healthcare communication |
US20030149599A1 (en) * | 2002-02-01 | 2003-08-07 | Charles Goodall | Method and apparatus for prescription processing |
US8321236B2 (en) | 2002-02-01 | 2012-11-27 | Walgreen Co. | Method and apparatus for prescription processing |
US20040172289A1 (en) * | 2003-02-28 | 2004-09-02 | Dejan Kozic | Method and system for remotely verifying a prescription |
US8190565B2 (en) | 2003-11-13 | 2012-05-29 | Commvault Systems, Inc. | System and method for performing an image level snapshot and for restoring partial volume data |
US8195623B2 (en) | 2003-11-13 | 2012-06-05 | Commvault Systems, Inc. | System and method for performing a snapshot and for restoring data |
US8645320B2 (en) | 2003-11-13 | 2014-02-04 | Commvault Systems, Inc. | System and method for performing an image level snapshot and for restoring partial volume data |
US20090018867A1 (en) * | 2004-07-09 | 2009-01-15 | Bruce Reiner | Gesture-based communication and reporting system |
US8335694B2 (en) * | 2004-07-09 | 2012-12-18 | Bruce Reiner | Gesture-based communication and reporting system |
US20060041330A1 (en) * | 2004-08-18 | 2006-02-23 | Walgreen Co. | System and method for checking the accuracy of a prescription fill |
US8666541B1 (en) | 2004-08-18 | 2014-03-04 | Walgreen Co. | System and method for checking the accuracy of a prescription fill |
US8224483B1 (en) | 2004-08-18 | 2012-07-17 | Walgreen Co. | System for checking the accuracy of a prescription fill |
US7801642B2 (en) | 2004-08-18 | 2010-09-21 | Walgreen Co. | System and method for checking the accuracy of a prescription fill |
US20080270186A1 (en) * | 2004-08-24 | 2008-10-30 | Soren Mikkelsen | Giving a Service to a Patient |
US8202217B2 (en) | 2004-12-20 | 2012-06-19 | Ip Venture, Inc. | Healthcare base |
US20060241355A1 (en) * | 2004-12-20 | 2006-10-26 | Howell Thomas A | Healthcare base |
US8200971B2 (en) | 2005-09-23 | 2012-06-12 | Cisco Technology, Inc. | Method for the provision of a network service |
US8255465B2 (en) * | 2005-09-23 | 2012-08-28 | Scansafe Limited | Network communications |
US20100082979A1 (en) * | 2005-09-23 | 2010-04-01 | Scansafe Limited | Method for the provision of a network service |
US20070074018A1 (en) * | 2005-09-23 | 2007-03-29 | Scansafe Limited | Network communications |
US7734478B2 (en) | 2005-10-18 | 2010-06-08 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing using resource function assignments |
US8311891B2 (en) | 2005-10-18 | 2012-11-13 | Walgreen Co. | System for separating and distributing pharmacy order processing for medication payments |
US20070088590A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for out of stock medication |
US8315887B2 (en) | 2005-10-18 | 2012-11-20 | Walgreen Co. | System for separating and distributing pharmacy order processing for specialty medication |
US20070088565A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for medication payments |
US7831448B1 (en) | 2005-10-18 | 2010-11-09 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing using resource function assignments |
US7860730B1 (en) | 2005-10-18 | 2010-12-28 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing |
US7765108B2 (en) | 2005-10-18 | 2010-07-27 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing |
US20070088594A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing |
US20070088569A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for prescription verification |
US20070088568A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | Method and apparatus for inter-pharmacy workload balancing using resource function assignments |
US20070088567A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for compound medication |
US20070088566A1 (en) * | 2005-10-18 | 2007-04-19 | Walgreen Co. | System for separating and distributing pharmacy order processing for specialty medication |
US8175891B2 (en) | 2005-10-18 | 2012-05-08 | Walgreen Co. | System for separating and distributing pharmacy order processing for compound medication |
US8666780B2 (en) | 2005-10-18 | 2014-03-04 | Walgreen Co. | System for separating and distributing pharmacy order processing |
US9971657B2 (en) | 2005-12-19 | 2018-05-15 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US20100049753A1 (en) * | 2005-12-19 | 2010-02-25 | Commvault Systems, Inc. | Systems and methods for monitoring application data in a data replication system |
US8121983B2 (en) | 2005-12-19 | 2012-02-21 | Commvault Systems, Inc. | Systems and methods for monitoring application data in a data replication system |
US9298382B2 (en) | 2005-12-19 | 2016-03-29 | Commvault Systems, Inc. | Systems and methods for performing replication copy storage operations |
US8655850B2 (en) | 2005-12-19 | 2014-02-18 | Commvault Systems, Inc. | Systems and methods for resynchronizing information |
US8656218B2 (en) | 2005-12-19 | 2014-02-18 | Commvault Systems, Inc. | Memory configuration for data replication system including identification of a subsequent log entry by a destination computer |
US8271830B2 (en) | 2005-12-19 | 2012-09-18 | Commvault Systems, Inc. | Rolling cache configuration for a data replication system |
US8285684B2 (en) | 2005-12-19 | 2012-10-09 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8725694B2 (en) | 2005-12-19 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for performing replication copy storage operations |
US9020898B2 (en) | 2005-12-19 | 2015-04-28 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8793221B2 (en) | 2005-12-19 | 2014-07-29 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US9208210B2 (en) | 2005-12-19 | 2015-12-08 | Commvault Systems, Inc. | Rolling cache configuration for a data replication system |
US9639294B2 (en) | 2005-12-19 | 2017-05-02 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8935210B2 (en) | 2005-12-19 | 2015-01-13 | Commvault Systems, Inc. | Systems and methods for performing replication copy storage operations |
US9002799B2 (en) | 2005-12-19 | 2015-04-07 | Commvault Systems, Inc. | Systems and methods for resynchronizing information |
US8463751B2 (en) | 2005-12-19 | 2013-06-11 | Commvault Systems, Inc. | Systems and methods for performing replication copy storage operations |
US20070225578A1 (en) * | 2006-03-24 | 2007-09-27 | Howell Thomas A | Medical monitoring system |
US8112293B2 (en) | 2006-03-24 | 2012-02-07 | Ipventure, Inc | Medical monitoring system |
US9003374B2 (en) | 2006-07-27 | 2015-04-07 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
US8726242B2 (en) | 2006-07-27 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
US20080103836A1 (en) * | 2006-10-31 | 2008-05-01 | Athenahealth, Inc. | Medical document attachment handling |
US11314384B2 (en) | 2007-01-22 | 2022-04-26 | Cerner Innovation, Inc. | System and user interface for clinical reporting and ordering provision of an item |
US10635260B2 (en) | 2007-01-22 | 2020-04-28 | Cerner Innovation, Inc. | System and user interface for clinical reporting and ordering provision of an item |
US8290808B2 (en) * | 2007-03-09 | 2012-10-16 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US20130218629A1 (en) * | 2007-03-09 | 2013-08-22 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US8428995B2 (en) * | 2007-03-09 | 2013-04-23 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US8799051B2 (en) * | 2007-03-09 | 2014-08-05 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US20080306761A1 (en) * | 2007-06-07 | 2008-12-11 | Walgreen Co. | System and Method of Performing Remote Verification of a Prescription in Combination with a Patient Access Terminal |
US20090030722A1 (en) * | 2007-07-25 | 2009-01-29 | Walgreen Co. | System and method for performing a remote verification of a pharmacy fill utilizing an image to image comparison |
US8775198B2 (en) | 2007-07-25 | 2014-07-08 | Walgreen Co. | System and method for performing a remote verification of a pharmacy fill utilizing an image to image comparison |
US20090125326A1 (en) * | 2007-11-13 | 2009-05-14 | Wasson David S | Method and apparatus for indirect medical consultation |
WO2009064850A2 (en) * | 2007-11-13 | 2009-05-22 | Wasson David S | Method and apparatus for indirect medical consultation |
US8762173B2 (en) | 2007-11-13 | 2014-06-24 | Red Stick Ventures L.L.C. | Method and apparatus for indirect medical consultation |
WO2009064850A3 (en) * | 2007-11-13 | 2009-08-27 | Wasson David S | Method and apparatus for indirect medical consultation |
US20090167553A1 (en) * | 2007-12-30 | 2009-07-02 | Jin Hong | Open Mobile Online Reservation and Ordering Systems |
US8145501B1 (en) | 2008-10-09 | 2012-03-27 | Walgreen Co. | System and method for performing pharmacy product filling using non-registered pharmacists |
US20100125461A1 (en) * | 2008-11-14 | 2010-05-20 | Walgreen Co. | System and Method of Using a Non-Retail Central Filling Facility to Process Pharmacy Product Prescriptions in a Pharmacy Retail Network |
US7941325B2 (en) | 2008-11-14 | 2011-05-10 | Walgreen Co. | System and method of using a non-retail central filling facility to process pharmacy product prescriptions in a pharmacy retail network |
US9495382B2 (en) | 2008-12-10 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods for performing discrete data replication |
US9396244B2 (en) | 2008-12-10 | 2016-07-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
US8204859B2 (en) | 2008-12-10 | 2012-06-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
US8666942B2 (en) | 2008-12-10 | 2014-03-04 | Commvault Systems, Inc. | Systems and methods for managing snapshots of replicated databases |
US9047357B2 (en) | 2008-12-10 | 2015-06-02 | Commvault Systems, Inc. | Systems and methods for managing replicated database data in dirty and clean shutdown states |
US20110137679A1 (en) * | 2009-12-09 | 2011-06-09 | International Business Machines Corporation | Method to transform clinician order entry |
US9727936B2 (en) | 2009-12-09 | 2017-08-08 | International Business Machines Corporation | Method to transform clinician order entry |
US8504517B2 (en) | 2010-03-29 | 2013-08-06 | Commvault Systems, Inc. | Systems and methods for selective data replication |
US8868494B2 (en) | 2010-03-29 | 2014-10-21 | Commvault Systems, Inc. | Systems and methods for selective data replication |
US8504515B2 (en) | 2010-03-30 | 2013-08-06 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
US9002785B2 (en) | 2010-03-30 | 2015-04-07 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
US9483511B2 (en) | 2010-03-30 | 2016-11-01 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
US8725698B2 (en) | 2010-03-30 | 2014-05-13 | Commvault Systems, Inc. | Stub file prioritization in a data replication system |
US8352422B2 (en) | 2010-03-30 | 2013-01-08 | Commvault Systems, Inc. | Data restore systems and methods in a replication environment |
US8589347B2 (en) | 2010-05-28 | 2013-11-19 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8745105B2 (en) | 2010-05-28 | 2014-06-03 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8572038B2 (en) | 2010-05-28 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US8489656B2 (en) | 2010-05-28 | 2013-07-16 | Commvault Systems, Inc. | Systems and methods for performing data replication |
US11269543B2 (en) | 2012-04-23 | 2022-03-08 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
US10833983B2 (en) * | 2012-09-20 | 2020-11-10 | Masimo Corporation | Intelligent medical escalation process |
US11887728B2 (en) | 2012-09-20 | 2024-01-30 | Masimo Corporation | Intelligent medical escalation process |
US20170228516A1 (en) * | 2012-09-20 | 2017-08-10 | Masimo Corporation | Intelligent medical escalation process |
US10978206B2 (en) | 2012-10-05 | 2021-04-13 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US10642460B2 (en) | 2012-10-05 | 2020-05-05 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US11164673B2 (en) | 2012-10-05 | 2021-11-02 | Cerner Innovation, Inc. | Attaching patient context to a call history associated with voice communication |
US11232864B2 (en) | 2012-10-05 | 2022-01-25 | Cerner Innovation, Inc. | Multi-action button for mobile devices |
US10777059B2 (en) | 2012-12-31 | 2020-09-15 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US10580279B2 (en) | 2012-12-31 | 2020-03-03 | Cerner Innovation, Inc. | Alert management utilizing mobile devices |
US11847026B2 (en) | 2013-01-11 | 2023-12-19 | Commvault Systems, Inc. | Single snapshot for multiple agents |
US11699526B2 (en) | 2013-10-11 | 2023-07-11 | Masimo Corporation | Alarm notification system |
US11488711B2 (en) | 2013-10-11 | 2022-11-01 | Masimo Corporation | Alarm notification system |
US20150112722A1 (en) * | 2013-10-21 | 2015-04-23 | OSIA Medical, Inc. | Medical condition tracking and analysis |
US11507470B2 (en) | 2014-11-14 | 2022-11-22 | Commvault Systems, Inc. | Unified snapshot storage management |
US20220277818A1 (en) * | 2015-10-06 | 2022-09-01 | Cerner Innovation, Inc. | Alert Optimizer |
US11749389B2 (en) * | 2015-10-06 | 2023-09-05 | Cerner Innovation, Inc. | Alert optimizer |
US11342052B2 (en) * | 2015-10-06 | 2022-05-24 | Cerner Innovation, Inc. | Alert optimizer |
US10607728B2 (en) * | 2015-10-06 | 2020-03-31 | Cerner Innovation, Inc. | Alert optimizer |
US10699812B2 (en) | 2015-12-30 | 2020-06-30 | Cerner Innovation, Inc. | Intelligent alert suppression |
US11127498B2 (en) | 2015-12-30 | 2021-09-21 | Cerner Innovation, Inc. | Intelligent alert suppression |
US11238064B2 (en) | 2016-03-10 | 2022-02-01 | Commvault Systems, Inc. | Snapshot replication operations based on incremental block change tracking |
US20170357774A1 (en) * | 2016-06-08 | 2017-12-14 | David FIGG | Automated prescription communication system and method |
US11422732B2 (en) | 2018-02-14 | 2022-08-23 | Commvault Systems, Inc. | Live browsing and private writable environments based on snapshots and/or backup copies provided by an ISCSI server |
US11109818B2 (en) | 2018-04-19 | 2021-09-07 | Masimo Corporation | Mobile patient alarm display |
US11844634B2 (en) | 2018-04-19 | 2023-12-19 | Masimo Corporation | Mobile patient alarm display |
US11042318B2 (en) | 2019-07-29 | 2021-06-22 | Commvault Systems, Inc. | Block-level data replication |
US11709615B2 (en) | 2019-07-29 | 2023-07-25 | Commvault Systems, Inc. | Block-level data replication |
US11809285B2 (en) | 2022-02-09 | 2023-11-07 | Commvault Systems, Inc. | Protecting a management database of a data storage management system to meet a recovery point objective (RPO) |
Also Published As
Publication number | Publication date |
---|---|
US20070124173A1 (en) | 2007-05-31 |
CA2385683A1 (en) | 2001-04-05 |
EP1415259A2 (en) | 2004-05-06 |
WO2001024098A3 (en) | 2002-04-25 |
WO2001024098A2 (en) | 2001-04-05 |
US7809584B2 (en) | 2010-10-05 |
AU6802000A (en) | 2001-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7809584B2 (en) | Message and program system supporting communication | |
US20040220829A1 (en) | Distributed system and method for managing communication among healthcare providers, patients and third parties | |
US8990834B2 (en) | Managing healthcare information in a distributed system | |
US7171371B2 (en) | Method and system for providing pre and post operative support and care | |
US8301462B2 (en) | Systems and methods for disease management algorithm integration | |
US7856365B2 (en) | Method and system for providing current industry specific data to physicians | |
US20040243435A1 (en) | Medical information management system | |
US7703042B2 (en) | System and method for a seamless user interface for an integrated electronic health care information system | |
US20030216937A1 (en) | System and method for providing on-line healthcare | |
US7286997B2 (en) | Internet-based, customizable clinical information system | |
US20140289001A1 (en) | System and method for recruiting subjects for research studies and clinical trials over the internet | |
US20030195774A1 (en) | Medical practice management system | |
US20090083073A1 (en) | Home Healthcare Documentation Clearing House | |
Giuse | Supporting communication in an integrated patient record system | |
WO2004072795A2 (en) | System, method, and computer program for interfacing an expert system to a clinical information system | |
US20120310663A1 (en) | Systems and methods for managing and/or administering prescription benefits | |
US20120253868A1 (en) | Healthcare information communication system | |
US20130297332A1 (en) | Health care practice management messaging and mining system and method | |
US20130231955A1 (en) | Integrated, Multilevel Medical Services | |
Hammond | Hospital information systems: a review in perspective | |
US20110218824A1 (en) | Patient-Physician Connectivity System and Method | |
WO2002001483A2 (en) | Patient health record access system | |
Jirjis et al. | A framework for clinical communication supporting healthcare delivery | |
WO2003067388A2 (en) | Distributed system and method for managing communication among healthcare providers, patients and third parties | |
Pugno | Ethical considerations of electronic communication in the clinical outpatient setting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RELAYHEALTH CORPORATION, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:HEALINX CORPORATION;REEL/FRAME:013302/0805 Effective date: 20020814 |
|
AS | Assignment |
Owner name: MCKESSON INFORMATION SOLUTIONS LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RELAYHEALTH CORPORATION;REEL/FRAME:018492/0219 Effective date: 20061102 |
|
AS | Assignment |
Owner name: MCKESSON TECHNOLOGIES, INC.,GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MCKESSON INFORMATION SOLUTIONS LLC;REEL/FRAME:024363/0621 Effective date: 20091231 Owner name: MCKESSON TECHNOLOGIES, INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MCKESSON INFORMATION SOLUTIONS LLC;REEL/FRAME:024363/0621 Effective date: 20091231 |
|
AS | Assignment |
Owner name: MCKESSON TECHNOLOGIES INC.,GEORGIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME BY REMOVING THE COMMA BETWEEN TECHNOLOGIES AND INC. PREVIOUSLY RECORDED ON REEL 024363 FRAME 0621. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:MCKESSON INFORMATION SOLUTIONS LLC;REEL/FRAME:024499/0065 Effective date: 20091231 Owner name: MCKESSON TECHNOLOGIES INC., GEORGIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME BY REMOVING THE COMMA BETWEEN TECHNOLOGIES AND INC. PREVIOUSLY RECORDED ON REEL 024363 FRAME 0621. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:MCKESSON INFORMATION SOLUTIONS LLC;REEL/FRAME:024499/0065 Effective date: 20091231 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |