US20070179808A1

US20070179808A1 - Method and apparatus for medical covering group processing, review, and management

Info

Publication number: US20070179808A1
Application number: US11/525,521
Authority: US
Inventors: David Weinstein; Robert Reiss
Original assignee: Individual
Current assignee: Change Healthcare Technologies LLC
Priority date: 1999-03-22
Filing date: 2006-09-21
Publication date: 2007-08-02
Also published as: AU4022900A; EP1163621A2; WO2000057341A3; US6218744B1; WO2000057341A2; CA2365409A1

Abstract

Certain embodiments include a method for a first covering group member belonging to a covering group of using a request list containing a request list component for each of the covering group members. The covering group containing at least two covering group members. Each of the request list components further contains a request summary collection containing at least a past-due request summary and a immediately-due request summary. The method includes the user performing the following. Selecting a second of the covering group members belonging to the covering group. Selecting a first of the summaries of the request summary collection contained in the request list component for the second covering group member. Perceiving a request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising a requestor name, a requested item, a request response list containing at least two request responses.

Description

This application claims priority to U.S. provisional application No. 60/125,461, filed Mar. 22, 1999, entitled “On-line Prescription Service”.

TECHNICAL FIELD

Embodiments relate to the field of medical prescriptions, medical laboratory tests and physician referrals. In particular, certain embodiments relate to interactive tools for the prescribing practitioners, pharmacists and medical care management of prescriptions. In particular, certain embodiments relate to interactive tools for primary care providers, medical consultants and medical care management of medical referrals. In particular, certain embodiments relate to interactive tools for prescribing practitioners, medical laboratories and medical care management of laboratory tests.

BACKGROUND ART

Traditionally, the process of creating and refilling prescriptions entails an enormous of waste of time and effort. New prescriptions, are often hand-written on pieces of paper and then hand carried by the patient to the pharmacist. There are no readily available mechanisms efficiently checking that the prescription is on a list of medications covered by the patient's insurer (known herein as the FORMULARY). Conflicts with FORMULARY compliance are usually first noted at the pharmacy, often leading to several phone calls between the pharmacist and physician and resulting in wasting the patient's, physician's and pharmacist's time. The decision to use non-FORMULARY compliant drugs often brings the patient into this process, usually adding to the time and overhead required to complete the process of starting a new prescription.
What is needed is an optimized procedure minimizing the physician's time and maximizing the reliability of the process. What is needed includes automated FORMULARY compliance review. What is further needed is optimized reliable communication between physician and pharmacy.
Prescription refill requests are also written on pieces of paper, which are then submitted for approval to someone of prescription authority, usually a physician. They are often found in stacks on a physician's desk. These stacks of paper have a large potential for getting lost, with vital time critical prescription refill slips of paper looking no different from prescription refill requests which are not needed for days. While the prescription may have been reviewed for FORMULARY compliance, these other procedural problems are again a large waste of time. They render the quality of service a result of near random acts of administration, dependent upon someone reviewing the refill requests, after which, something may happen. What is needed is a time-efficient process for refill requests prioritizing the refill requests for the authorizing physician.
Additionally, there is the issue of whether a physician can be available for prescription prefill or refill authorization. There are times when physicians are unavailable, attending conferences, important personal or family events, etc. Physicians have evolved a covering group mechanism, where two or more doctors will belong to a covering group, and if one physician is not available, the others have authorization to order prescription refills. However, the system has some major problems. There are now multiple piles of slips of paper. There is no ready way to know where these piles are located or which ones among them are time-critical. There is no ready way to know the location of patient medical files needed for these requests, any of the covering physicians may have them. This situation again leads to a great deal of waste and confusion. What is needed is an efficient refill authorization procedure accessible by every member of the covering group, presenting a prioritized list of pending refill requests, supporting authorization with automated FORMULARY compliance.
Once the refill order has been authorized, a second ordeal of waste and confusion takes place. A pharmacy must be contacted, usually be telephone or FAX, again tying up the prescriber and/or their staff to insure that the pharmacy got the message, etc. It should be noted that physicians in managed care settings are required to see 25-35 patients per day to “earn their pay”. The physicians' expertise is taken away from the pressing health problems for which their skills are most vitally needed by these procedural inefficiencies. The inefficiencies just described cost everyone, the physician's income, the patient's time, and the required bureaucratic overhead (expense) at the pharmacy and physician's office. Optimized, reliable communication between physician and pharmacy is again needed.
Another problem related to this is the medical management issue: which physicians are unresponsive to this vital paperwork activity. No one can readily extract performance information from such a situation as it currently exists. What is needed is a tracking mechanism efficiently extracting information of physician responsiveness.
A related situation involves referrals to specialists in managed care settings. The process begins with the patient's primary care provider filling out a request form for a specialist to examine a patient. This request form is tangible paper, which is physically picked up and taken to an administrator who approves and schedules the specialist consultation, assuming the primary care provider has followed certain guidelines. Once this has happened, the specialist at the appointed time sees the patient, and may prescribe a medication. Today, there is no efficient mechanism for feedback from the specialist to the primary care provider. What is needed is an efficient referral procedure automating the communication, the redundant human entry and the compliance confirmation of the various steps in this process. What is further needed is an efficient feedback mechanism from the specialist to the primary care provider.
Again, there is the issue of whether a physician can be available to authorize referrals or respond to requests from specialists. The covering groups are also used for these situations. Again, there are multiple piles of slips of paper. Again, there is no ready way to know where these piles are located or which ones among them are time-critical. Again, there is no ready way to know the location of patient medical files needed for these requests, any of the covering physicians may have them. Again, the situation leads to a great deal of waste and confusion. What is needed is an efficient referral review and authorization procedure accessible by every member of the covering group, presenting a prioritized list of pending referral requests and supporting authorization.
A related situation involves lab results. As before, a form is filled out. The issue of whether the test is covered by insurance must be addressed before the test is performed, usually by an administrator approving the request. The medical lab receives the approved request form, often this is hand carried by the patient. The lab then takes the required samples, often sending these medical samples to a regional lab where the actual results are generated. Once the results are back, the lab distributes them to the requesting physicians. If something is significantly deviant, a physician may well need to make a timely judgement call to safeguard the patient's health. Even though the people carrying out this process are dedicated, the process itself is cumbersome, often requiring people to physically process and transport lots of pieces of paper to achieve a result in a timely and reliable fashion. What is needed is an efficient referral procedure automating the communication, the redundant human entry and the compliance confirmation of the various steps in this process.
Again, there is the issue of whether a physician can be available to authorize and review lab tests. The covering groups are also used for these situations. Again, there are multiple piles of slips of paper. Again, there is no ready way to know where these piles are located or which ones among them are time-critical. Again, there is no ready way to know the location of patient medical files needed for these requests and reviews, any of the covering physicians may have them. Again, the situation leads to a great deal of waste and confusion. The problem of an untimely lab result review can jeopardize a patient's health, perhaps even be life-threatening. What is needed is an efficient laboratory test review and authorization procedure accessible by every member of the covering group, presenting a prioritized list of pending laboratory test reviews and requests, and supporting authorization with automated insurance compliance.
While certain inventions have been patented which aid in creating prescriptions (see U.S. Pat. No. 5,737,539 and U.S. Pat. No. 5,845,255), these inventions do not address covering group authorization, management nor refills. They also do not support batch authorization of prescriptions. Prescriptions are treated as essentially isolated events in what is often very much a covering group environment. These vital activities are left to the clumsy, paper intensive approaches of the past, which waste so much time and money for everyone involved.
To summarize, there is a strong and consistent need for an optimized process of communication, compliance review, decision-making, and progress monitoring for both the individual physician, specialist, the covering group they belong to, medical administration, pharmacies and labs regarding prescription refills, physician referrals and lab tests. The results of satisfying these needs will be lower health care costs and improved health care quality for patients. The results of satisfying these needs will further reduce waste for the managed care systems, physicians, pharmacists, medical labs, and their offices. The results of satisfying these needs will further increase the revenue of many physicians who are currently inundated with paperwork, which gets in the way of their practice and their income.

SUMMARY OF THE INVENTION

Certain embodiments include a method for a first covering group member belonging to a covering group using a request list containing a request list component for each of the covering group members. The covering group containing at least two covering group members. Each of the request list components further contains a request summary collection containing at least a past-due request summary and an immediately-due request summary.
The method includes the user performing the following. Selecting a second of the covering group members belonging to the covering group. Selecting a first of the summaries of the request summary collection contained in the request list component for the second covering group member. Perceiving a request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising a requestor name, a requested item and a request response list containing at least two request responses.
Such embodiments advantageously support one member of the covering group viewing the prioritized request summaries of other covering group members, or themselves. Such embodiments further advantageously support one member viewing request detail reports of a selected request summary of other group covering members, or themselves.
Certain embodiments include a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list.
The method includes the user performing the following. Selecting a second of the covering group members belonging to the covering group. Selecting a first of the summaries of the request summary collection contained in the request list component for the second covering group member. Perceiving a request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising a requestor name, a requested item and a request response list containing at least two request responses.
Such embodiments advantageously support one member of the covering group viewing the prioritized request summaries of other covering group members, or themselves. Such embodiments further advantageously support one member viewing request detail reports of a selected request summary of other group covering members, or themselves.
Certain embodiments include selecting a first of the request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component. Such embodiments advantageously support selection of request responses in a user efficient fashion.
Certain embodiments include selecting to send at least one of the preliminary request responses. Such embodiments advantageously support authorization through communication by sending at least one of the preliminary request responses.
Certain further embodiments include selecting to send at least one of the preliminary request responses comprising selecting to send at least all of the preliminary request responses of the first summary component. Such embodiments advantageously support authorization through communication by sending at least all of the preliminary request responses of one of the summary components.
Certain further embodiments include selecting to send at least one of the preliminary request responses comprising selecting to send at least all of the preliminary request responses. Such embodiments advantageously support authorization through sending all of the preliminary request responses at one time.
Certain embodiments include the requested item being a prescription and the request summary collection further containing a future-due request summary. Such embodiments advantageously support prescription request processing.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component comprised of selecting to create a view of medication history response. Such embodiments support selective viewing of a patient's medication history response.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component further comprised of selecting to create a view of appointment history response. Such embodiments support selective viewing of a patient's appointment history response.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component further comprised of selecting to create a change prescription response. Such embodiments advantageously support changing a prescription in response to a prescription refill request.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component comprised of selecting to create a hold prescription response. Such embodiments advantageously support communicating that a physician has issued a hold on the prescription request. This informs the pharmacy that it has been noted and to expect response soon.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component further comprised of selecting to create a view pharmacy message response. Such embodiments advantageously support pharmacy feedback to the prescribing physician or their covering group member. Further, this directly and efficiently supports the pharmacy passing on the comments and requests of the patient or the patient's insurer.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component selecting to create a forward to primary care provider response. Such embodiments advantageously support forwarding a request response to the primary care provider.
Certain further embodiments include selecting the first request response of the request detail report for the first summary of the first summary component to create the preliminary request response of the first summary of the first summary component further comprised of selecting to create a fill prescription response. Such embodiments advantageously support authorization of a prescription refill request.
Certain further embodiments include selecting to create the fill prescription response further comprised of selecting to fill the prescription response in terms of units. Such embodiments advantageously support refilling the prescription in terms of units.
Certain further embodiments include selecting to fill the prescription response in terms of units comprised of selecting to fill the prescription response in terms of one unit of the prescription. Such embodiments advantageously support single unit refills.
Certain further embodiments include selecting to fill the prescription response in terms of units comprised of selecting to fill the prescription response in terms of at least two units of the prescription. Such embodiments advantageously support multiple unit refills.
Certain embodiments include selecting to create the fill prescription response comprised of selecting to fill the fill prescription response in terms of time duration. Such embodiments advantageously support refill authorizations extending over a duration of time.
Certain further embodiments include selecting to create a new prescription. Such embodiments advantageously support incorporation of new prescriptions into the covering group monitoring system.
Certain further embodiments include selecting to create the new prescription comprised of the following. Selecting a patient identifier associated with the new prescription to create a patient with the new prescription. Selecting a medication associated with the new prescription to create a medication with the new prescription. Selecting a dosage associated with the new prescription to create a dosage with the new prescription. Selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription. Selecting a prescription direction associated with the new prescription to create a direction with the new prescription. Selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription. And authorizing the new prescription, with the patient identifier, with the medication, with the dosage, with the number of units, with the direction at the filling pharmacy. Such embodiments advantageously support physician-efficient prescription creations within the covering group monitor.
Certain further embodiments include selecting the patient identifier associated with the new prescription to create the patient with the new prescription comprised of the following. Perceiving a patient identifier list containing at least one patient identifier. Selecting a first of the patient identifiers of the patient identifier list to create the patient with the new prescription. Such embodiments advantageously support perception of a patient identifier list and selecting a patient identifier from that perceived list. This minimizes the paper shuffling and potential for inaccurate typing the patient identifier.
Certain further embodiments include selecting the medication associated with the new prescription to create the medication with the new prescription comprised of the following. Perceiving a medication list containing at least two medications. Selecting a first of the medications of the medication list to create the medication with the new prescription. Such embodiments advantageously support perceiving a medication list and selecting a medication from that medication list. Such embodiments may further provide information upon FORMULARY compliance and insurer coverage.
Certain further embodiments include selecting the dosage associated with the new prescription to create the dosage with the new prescription comprised of the following. Perceiving a dosage list containing at least one dosage. Selecting a first of the dosages of the dosage list to create the dosage with the new prescription. Such embodiments advantageously support a dosage list and selecting a dosage from the dosage list.
Certain further embodiments include selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription comprised of the following. Perceiving a number of units list containing at least one number of units. Selecting a first of the number of units of the number of units list to create the number of units with the new prescription. Such embodiments advantageously support perceiving a numbers of units list and selecting from that list.
Certain further embodiments include selecting a prescription direction associated with the new prescription to create a direction with the new prescription comprised of the following. Perceiving a direction list containing at least one direction. Selecting a first of the directions of the direction list to create the direction with the new prescription. Such embodiments advantageously support perceiving standard directions for a medication for various conditions and selecting directions in keeping with the medication and patient's condition.
Certain further embodiments include selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription comprised of the following. Perceiving a pharmacy list containing at least one pharmacy. Selecting a first of the pharmacies of the pharmacy list to create the pharmacy with the new prescription. Such embodiments advantageously support perceiving the pharmacy list and selecting a pharmacy from that list.
Certain further embodiments include the pharmacy list being annotated with patient pharmacy preferences and history. Such embodiments advantageously support optimizing the patient's time in picking up prescriptions.
Certain further embodiments include authorizing the new prescription with the patient identifier, medication, dosage, number of units, and direction at the filling pharmacy comprised of sending the new prescription with the patient identifier, medication, dosage, number of units and direction to the filling pharmacy. Such embodiments advantageously support authorizing communicating the prescription to the pharmacy.
Certain further embodiments include authorizing the new prescription with the patient identifier, medication, dosage, number of units, direction at the filling pharmacy is comprised of sending the new prescription with the patient identifier, medication, dosage, number of units, direction at the filling pharmacy to a physician. Such embodiments advantageously support authorization including sending the prescription request to another physician for authorization. This is particularly beneficial in situations where a consulting physician wishes a patient's primary care provider to review the prescription before authorizing the pharmacy to fill the prescription.
Certain further embodiments include where the requested item is a referral and the request summary collection further contains a referral result summary. Such embodiments advantageously support covering group monitoring of referrals. Such embodiments also advantageously support the covering group monitoring of referral results, thus improving the quality of health care in such covering group environments.
Certain further embodiments include where the requested item is a laboratory test and the request summary collection further contains a test result summary. Such embodiments advantageously support covering group monitoring of laboratory test requests. Such embodiments also advantageously support the covering group monitoring of laboratory test results, thus improving the quality of health care in such covering group environments.
Certain further embodiments include selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component which is comprised of at least one of the following. Acoustically selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component. Visually selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component.
Such embodiments advantageously support both acoustic and visual selection of request responses. As used herein, a visual response includes but is not limited to tactile stimulus of a visual surface, such as a touch pad or transparent touch screen and the use of a pointing device such as a mouse or pen type device.
Certain further embodiments include perceiving the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member comprised of the following. Hearing the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requester name, the requested item, the request response list containing at least two request responses. Seeing the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requestor name, the requested item, the request response list containing at least two request responses.
Such embodiments advantageously support both hearing and/or seeing the request detail report. Such embodiments additionally support the physician or medical practitioner when their eyes are committed to some task, such as driving a car. While they cannot reasonably or ethically take their eyes off the traffic, they do have the time to hear a request detail report.
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.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a viewing region including a group monitor for prescriptions for a covering group, in accordance with certain embodiments;
FIG. 2 depicts a viewing region including a group monitor for prescriptions and referrals for a covering group, in accordance with certain embodiments;
FIG. 3 depicts a viewing region including a group monitor for prescriptions and referrals for a covering group, in accordance with certain embodiments;
FIG. 4 depicts a usage flowchart performing a method for the first covering group member belonging to the covering group using the request list contains the request list component for each covering group member, in accordance with using certain usage embodiments;
FIG. 5A depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group using the request list containing the request list component for each covering group member, in accordance with certain embodiments;
FIG. 5B depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group using the request list containing the request list component for each covering group member in accordance with certain embodiments;
FIG. 5C depicts a detail flowchart of user operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses of the first summary component in accordance with certain embodiments;
FIG. 6A depicts a detail flowchart of user operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses in accordance with certain embodiments;
FIG. 6B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view of medication history response in accordance with certain embodiments;
FIG. 6C depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view of appointment history response in accordance with certain embodiments;
FIG. 7A depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a change prescription response in accordance with certain embodiments;
FIG. 7B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a hold prescription response in accordance with certain embodiments;
FIG. 7C depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view pharmacy message response in accordance with certain embodiments;
FIG. 8A depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a forward to primary care provider response in accordance with certain embodiments;
FIG. 8B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a fill prescription response in accordance with certain embodiments;
FIG. 8C depicts a detail flowchart of user operation 2232 of FIG. 8B performing selecting to fill the prescription response in terms of units in accordance with certain embodiments;
FIG. 9A depicts a detail flowchart of user operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of one unit of the prescription in accordance with certain embodiments;
FIG. 9B depicts a detail flowchart of user operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of at least two units of the prescription in accordance with certain embodiments;
FIG. 10A depicts a detail flowchart of user operation 2232 of FIG. 8B performing selecting to fill the fill prescription response in terms of time duration in accordance with certain embodiments;
FIG. 10B depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group of using the request list containing the request list component for each covering group member in accordance with certain embodiments, in accordance with certain embodiments;
FIG. 11 depicts a detail flowchart of user operation 2332 of FIG. 10B further performing selecting to create the new prescription in accordance with certain embodiments;
FIG. 12A depicts a detail flowchart of user operation 2352 of FIG. 11 performing selecting a patient identifier associated with the new prescription to create a patient with the new prescription in accordance with certain embodiments;
FIG. 12B depicts a detail flowchart of user operation 2362 of FIG. 11 performing selecting the medication associated with the new prescription to create the medication with the new prescription in accordance with certain embodiments;
FIG. 13A depicts a detail flowchart of user operation 2372 of FIG. 11 performing selecting the dosage associated with the new prescription to create the dosage with the new prescription in accordance with certain embodiments;
FIG. 13B depicts a detail flowchart of user operation 2362 of FIG. 11 performing selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription in accordance with certain embodiments;
FIG. 14A depicts a detail flowchart of user operation 2392 of FIG. 14A performing selecting a prescription direction associated with the new prescription to create a direction with the new prescription in accordance with certain embodiments;
FIG. 14B depicts a detail flowchart of user operation 2402 of FIG. 11 performing selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription in accordance with certain embodiments;
FIG. 15A depicts a detail flowchart of user operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, the number of units and with the direction to the filling pharmacy in accordance with certain embodiments;
FIG. 15B depicts a detail flowchart of user operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, with the number of units and with the direction at the filling pharmacy to a physician in accordance with certain embodiments;
FIG. 16 depicts a system block diagram for a computing system supporting the first covering group member interacting with a request list containing a request list component for each of the covering group members of the covering group;
FIG. 17 depicts a viewing region component supporting changing a prescription, in accordance with certain embodiments;
FIG. 18 depicts a viewing region component supporting viewing a patient medical history, in accordance with certain embodiments;
FIG. 19 depicts a viewing region component supporting viewing a patient appointment history, in accordance with certain embodiments;
FIG. 20 depicts a viewing region component supporting starting a new prescription, in accordance with certain embodiments;
FIG. 21 depicts a viewing region component supporting creating a new prescription by selecting a patient, in accordance with certain embodiments;
FIG. 22 depicts a viewing region component supporting creating a new prescription showing the selected patient, in accordance with certain embodiments;
FIG. 23 depicts a viewing region component supporting creating a new prescription by selecting a pharmacy, in accordance with certain embodiments;
FIG. 24 depicts a viewing region component supporting creating a new prescription showing the selected patient and the selected pharmacy, in accordance with certain embodiments;
FIG. 25 depicts a viewing region component supporting creating a new prescription by selecting a medication, in accordance with certain embodiments;
FIG. 26 depicts a viewing region component supporting creating a new prescription showing the selected patient, the selected pharmacy and selected medication, in accordance with certain embodiments;
FIG. 27 depicts a viewing region component supporting creating a new prescription showing the selected patient, the selected pharmacy and selected medication, with directions and number of units, ready for authorization, in accordance with certain embodiments;
FIG. 28 depicts a viewing region component supporting creating a prior authorization request form for FORMULARY override for a new prescription, in accordance with certain embodiments;
FIG. 29 depicts a viewing region component supporting a prescription InBox Monitor of prescribing practitioners for use in health management and pharmacies, in accordance with certain embodiments;
FIG. 30 depicts a viewing region component supporting a pharmacy prescription lookup, in accordance with certain embodiments;
FIG. 31 depicts a viewing region component supporting a pharmacy prescription lookup response, in accordance with certain embodiments;
FIG. 32 depicts a viewing region component including a group monitor for prescriptions and referrals for a covering group with a New Referral link, in accordance with certain embodiments;
FIG. 33 depicts a viewing region component supporting selecting the patient for the new referral, in accordance with certain embodiments;
FIG. 34 depicts a viewing region component supporting selecting the department-referral type of the new referral for the selected patient, in accordance with certain embodiments;
FIG. 35 depicts a viewing region component supporting pre-requisite check-off given the department-referral type of the new referral for the selected patient, in accordance with certain embodiments;
FIG. 36 depicts a viewing region component supporting a consultant approval queue for referral requests, in accordance with certain embodiments;
FIG. 37 depicts a viewing region component supporting a referral request form with pre-requisite check-off given the department-referral type of the new referral for the selected patient, in accordance with certain embodiments;
FIG. 38 depicts a viewing region component supporting an appointment center queue for referral requests, in accordance with certain embodiments;
FIG. 39 depicts a viewing region component supporting an appointment request from a consulting medical practitioner with the department-referral type of the new referral for the selected patient, in accordance with certain embodiments;
FIG. 40 depicts a viewing region component supporting a consultant approval queue for referral requests, in accordance with certain embodiments;
FIG. 41 depicts a viewing region component supporting a referral pending appointment with consulting medical practitioner form, showing the department-referral type, prerequisite check-off list of the referral for the selected patient, in accordance with certain embodiments;
FIG. 42 depicts a viewing region component supporting a referral inbox based upon a referral group monitor, in accordance with certain embodiments;
FIG. 43 depicts a viewing region component supporting a consultant encounter report with the department-referral type for the selected patient, and the results of the encounter, in accordance with certain embodiments;
FIG. 44 depicts a viewing region component supporting a referral results summary based upon a referral group monitor, in accordance with certain embodiments;
FIG. 45 depicts a viewing region component supporting referral lookup, in accordance with certain embodiments;
FIG. 46 depicts a viewing region component supporting viewing a patient referral history, in accordance with certain embodiments;
FIG. 47 depicts a viewing region component supporting viewing a consultant encounter report referenced by a selecting a link of the patient referral history of FIG. 46, in accordance with certain embodiments;
FIG. 48 depicts a viewing region component supporting a referral volume report generator, in accordance with certain embodiments;
FIG. 49 depicts a viewing region component supporting a referral volume report resulting from the parameterization of the referral volume report generator associated with FIG. 48, in accordance with certain embodiments;
FIG. 50 depicts a viewing region component supporting a referral time lapse report generator, in accordance with certain embodiments;
FIG. 51 depicts a viewing region component supporting a referral time lapse report resulting from the parameterization of the referral time lapse report generator associated with FIG. 50, in accordance with certain embodiments;
FIG. 52 depicts a viewing region component supporting a referral time lapse report detail resulting from the selecting an underlined entry in the table of FIG. 51, in accordance with certain embodiments;
FIG. 53 depicts a viewing region component supporting a referral pending appointment with consultant form, in accordance with certain embodiments;
FIG. 54 depicts a viewing region component supporting a referral report selector, in accordance with certain embodiments;
FIG. 55 depicts a viewing region component supporting a referral report on OBG consultations by medical indication selected from the referral report selector of FIG. 54, in accordance with certain embodiments;
FIG. 56 depicts a viewing region component supporting a referral report on OBG consultations by length of wait for consultation selected from the referral report selector of FIG. 54, in accordance with certain embodiments;
FIG. 57 depicts a viewing region component supporting a referral report on the number of referrals by medical practitioner/department selected from the referral report selector of FIG. 54, in accordance with certain embodiments;
FIG. 58A depicts a detail flowchart of user operation 2032 of FIG. 5A further performing selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component in accordance with certain embodiments; and
FIG. 58B depicts a detail flowchart of user operation 2012 of FIG. 4 performing perceiving the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requester name, the requested item, the request response list containing at least two request responses in accordance with certain embodiments.

DETAILED DESCRIPTION OF THE INVENTION

As used herein a computer system comprises at least one computer accessibly coupled to a computer memory. In certain embodiments, a computer system comprises at least two computers, each with separate accessibly coupled computer memories. In certain embodiments, a computer system comprises at least two computers, each sharing an accessibly coupled computer memory.
As used herein, accessibly coupled computer memory includes at least a non-volatile memory. The non-volatile memory may be comprised of more than one non-volatile memory component. Access to a non-volatile memory component may be further organized about a file management system. Accessibly coupled memory may further include a volatile memory. Volatile memory may be comprised of more than one volatile memory component. Volatile memory components may include but are not limited to static RAM and various forms of Dynamic RAM. Access to a volatile memory component may be further organized as a cache memory interface to an often larger and slower memory component, which may be either volatile or non-volatile. The cache memory interface may be further multi-leveled, where successive levels of the cache memory incorporate a slower memory transfer rate to (an often) larger amount of memory.
As used herein, computer refers to an instruction-processing computer, an inference engine or an analog computer. An instruction-processing computer as used herein refers to either a Single Instruction Single Datapath (SISD) computer, Single Instruction Multiple Datapath (SIMD) computer, Multiple Instruction Single Datapath (MISD) computer, or a Multiple Instruction Multiple Datapath (MIMD) computer. Examples of SISD computers include microprocessors. Microprocessors as used herein, include but are not limited to super-scalar microprocessors, which concurrently execute components of several successive instructions of a single instruction stream involving a single datapath. Instruction processing mechanisms include but are not limited to native code execution mechanisms such as found in a 80×086 microprocessor, byte code interpreters such as JAVA and MPEG 4 use, threaded execution structures such as FORTH and Postscript use, or combinations of the above.
As used herein, inference engines operate upon a fact based and an inference rule collection. Execution of inference engines may be based upon unification processes, constraint satisfaction mechanisms and neural network threshold-stimuli mechanisms. Instructions as used herein for such inference engines would include the facts and inference rules presented to the inference engine.
As used herein, the term computer will further refer to information access, communication and analysis tools employing at least one computer in their internal operations. Such computers include but are not limited to desk top computers, portable, notebook and handheld computers, personal digital assistants and telephones with built-in messaging and/or browsing capabilities. Note that telephones may be either wireline or wireless.
Web browsers are software tools that have been in widespread use since the early 1990's. Most popular tools of this kind, including Microsoft's Internet Explorer™ and Netscape's Navigator™, support what is known as plug-ins. These plug-ins provide the ability to significantly extend the software linked to the browser, often providing additional file format capabilities (JPEG, MPEG and MP3 readers-players, for example).
Most popular tools of this kind also include the ability to execute a variety of interpreted computer languages include HTML (Hyper Text Markup Language) and JAVA™. Further note that JAVA possesses a complete windowing object class, so that entire applications could be written in JAVA and run on essentially any computer supporting a web browser with a JAVA execution engine.
Based upon these observations, embodiments assume operating platforms including but not limited to browsers, meaning a software tool executing on at least a user operated computer supporting plug-ins and the execution of languages such as JAVA. Certain embodiments will further use a browser capable of communication with other computers.
As used herein a thin client application is an embodiment assuming operating platforms such as a browser, meaning a software tool executing on at least a user operated computer supporting plug-ins and the execution of languages such as JAVA. It may further utilize communication with other computers in performing the tasks involving the relevant embodiments.
As used herein networks include but are not limited communicative couplings of computers employing wireline and/or wireless physical transport layers. In certain further embodiments, communications between computers communicatively coupled to a network may further employ a messaging protocol. In certain further embodiments, network communications between computers communicatively coupled employ a messaging protocol compatible with TCP-IP. In certain further embodiments, network communications between computers communicatively coupled employ messaging protocols compatible with Internet.
Certain embodiments include a method for a first covering group member belonging to a covering group using a request list containing a request list component for each of the covering group members. The covering group contains at least two covering group members. Each of the request list components further contains a request summary collection containing at least a past-due request summary and a immediately-due request summary.
FIG. 1 depicts a viewing region including a group monitor for prescriptions for a covering group, in accordance with certain embodiments.
Region 1000 includes a designation of the covering group being viewed. The column header 1002 is “InBox For”, which indicates that for each successive row, this column entry will identify the medical practitioner responsible for that row's request summary. The column header 1004 is “Immediates”, which indicates that for each successive row, this column entry will identify number of prescription requests for that row's request summary which are due currently. The column header 1006 is “Days Late”, which indicates that for each successive row, this column entry will identify the number of days past due of the oldest prescription request in the Immediate request queue for that row's request summary. The column header 1008 is “Futures”, which indicates that for each successive row, this column entry will identify the number of request responses not yet due for that row's request summary, known as futures.
The line starting with “Smith, William” 1010 in the “InBox For” column designates that this request summary line is for William Smith. The bolding of the lettering indicates that the result summary list for William Smith has been selected. The number “5” further labeled 1012 indicates that there are 5 request responses currently due for William Smith. The number “2” further labeled 1014 indicates that there are 2 request responses past due for William Smith. The number “51” further labeled 1016 indicates that there are 51 request responses due in the future for William Smith.
The line starting with “Doctor, Joe” 1020 in the “InBox For” column designates that this request summary line is for Joe Doctor. The line starting with “Surgeon, Frank” 1022 in the “InBox For” column designates that this request summary line is for Frank Surgeon. The line starting with “OBG, Louis” 1024 in the “InBox For” column designates that this request summary line is for Louis OBG. The line starting with “Welby, John” 1026 in the “InBox For” column designates that this request summary line is for John Welby.
Note that the user has selected the first line of the request summary table, referring to William Smith. By selecting the “Immediates” heading, the region 1030 displays “Rx InBox for: Smith, William W (Immediates)”. The request details which follow below region 1030 are from the immediately pending, or currently due, response requests.
The first response request is for “PATIENT, SUSIE K.”, labeled 1040, whose primary care provider is Smith, labeled 1042. The medication is “CIPRO 500 MCG TABLET” labeled 1044, with a prescribed quantity of 10 units labeled 1046. The directions 1048 are “TAKE 1 TABLET 2 TIMES A DAY FOR 5 DAYS”. The prescription was filled “2/11/1999”, labeled 1050. Label 1052 indicates a link to change and/or examine the details of the prescription. Label 1054 indicates that this response request was forwarded from “YUN, SMITH MD RESIDENT OF FAMILY PRACTICE”. Label 1058 indicates a pull-down menu to select a request response from a response list.
The second response request is for “PERSON, MARK S”, labeled 1060, whose primary care provider is Smith, labeled 1062. The medication is “BECLOVENT INHALER” labeled 1064, with a prescribed quantity of 16.8 units labeled 1066. The directions 1068 are “INHALE 2 PUFFS 2 TIMES DAILY, RINSE MOUTH AFTER USE (GENERIC FOR VANCERIL)”. The prescription was filled “2/13/1999”, labeled 1070. Label 1072 indicates a link to change and/or examine the details of the prescription.
Link 1080 indicates how to select creating a new prescription, in certain further embodiments.
In certain further embodiments, selecting a patient's name may act as a link to the patient's medical database. In certain further embodiments, selecting a medical practitioner's name may act as a link to the practitioner's email. In certain further embodiments, selecting a medication label may act as a link to the medication database.
FIG. 2 depicts a viewing region including a group monitor for prescriptions and referrals for a covering group, in accordance with certain embodiments.
Region 1090 designates a prescription group monitor being viewed. The column header 1002 is “InBox For”, which indicates that for each successive row, this column entry will identify the medical practitioner responsible for that row's request summary. The column header 1004 is “Immediates”, which indicates that for each successive row, this column entry will identify number of prescription requests for that row's request summary which are due currently. The column header 1006 is “Days Late”, which indicates that for each successive row, this column entry will identify the number of days past due of the oldest prescription request in the Immediate request queue for that row's request summary. The column header 1008 is “Futures”, which indicates that for each successive row, this column entry will identify the number of request responses not yet due for that row's request summary, known as futures.
Region 1200 designates a referral group monitor being viewed. The column header 1202 is “Action Items”, which indicates that for each successive row, this column entry will identify number of referral requests for that row's request summary which are due currently. The column header 1204 is “Days Late”, which indicates that for each successive row, this column entry will identify the number of action item responses which are past due for that row's request summary. The column header 1206 is “Encounter Results”, which indicates that for each successive row, this column entry will identify the number of encounter result reports available for review for that row's request summary.
The line starting with “Welby, John” 1100 in the “InBox For” column designates that this request summary line is for William Smith. The bolding of the lettering indicates that the result summary list for William Smith has been selected. The number “3” further labeled 1102 indicates that there are 3 request responses currently due for William Smith. The number “0” further labeled 1104 indicates that all immediate response requests are current for William Smith. The number “11” further labeled 1106 indicates that there are 11 request responses due in the future for John Welby. The number “3” further labeled 1108 indicates that there are 3 referral requests currently due for William Smith. The number “0” further labeled 1110 indicates that there are 0 request responses past due for William Smith. The number “2” further labeled 1112 indicates that there are 2 encounter reports ready for review by John Welby.
Item 1210 entitled “Create a New Referral” is a link to creating a new referral.
The first response request is for “PATIENT, KENNETH K.”, labeled 1140, whose primary care provider is WELBY, labeled 1142. The medication is “DOXEPHIN HCL CAP 10 MG” labeled 1144, with a prescribed quantity of 60 units labeled 1146. The directions 1148 are “TAKE 1 TABLET 2 TIMES A DAY”. The prescription was filled “12/11/1998”, labeled 1050. Label 1054 indicates that this response request was forwarded from “YUN, SMITH MD RESIDENT OF FAMILY PRACTICE”.
Label 1052 indicates collection of responses which can be quickly made. The 1, 2, 3, 4 bubbles can be selected, which would indicate 1, 2, 3 or 4, respectively, refills were authorized. Selecting the bubbles associated with “1 yr” and “2 yr” indicate that refills were authorized for the respective time duration. Selecting the bubble next to “PCP” forwards the prescription refill request to the primary care provider. Selecting the bubble next to “Hold” sends a Hold message to the pharmacy, indicating that there thought or review will be shortly given to this request before authorization. Selecting the “Med” opens the patient's medication history. Selecting the “Appt.” opens the patient's appointment history. Selecting the “Chg Rx” opens the window for changing the prescription.
FIG. 3 depicts a viewing region including a group monitor for prescriptions and referrals for a covering group, in accordance with certain embodiments.
Region 1090 designates a prescription group monitor being viewed. The column header 1002 is “InBox For”, which indicates that for each successive row, this column entry will identify the medical practitioner responsible for that row's request summary. The column header 1004 is “Immediates”, which indicates that for each successive row, this column entry will identify number of prescription requests for that row's request summary which are due currently. The column header 1006 is “Days Late”, which indicates that for each successive row, this column entry will identify the number of days past due of the oldest prescription request in the Immediate request queue for that row's request summary. The column header 1008 is “Futures”, which indicates that for each successive row, this column entry will identify the number of request responses not yet due for that row's request summary, known as futures.
Region 1300 designates a lab test group monitor being viewed. The column header 1302 is “Action Items”, which indicates that for each successive row, this column entry will identify number of referral requests for that row's request summary which are due currently. The column header 1304 is “Days Late”, which indicates that for each successive row, this column entry will identify the number of days late the oldest action item is in the action item requests for that row's request summary. The column header 1306 is “Lab Results”, which indicates that for each successive row, this column entry will identify the number of lab result reports available for review for that row's request summary.
The line starting with “Welby, John” 1100 in the “InBox For” column designates that this request summary line is for William Smith. The bolding of the lettering indicates that the result summary list for William Smith has been selected. The number “3” further labeled 1102 indicates that there are 3 request responses currently due for William Smith. The number “0” further labeled 1104 indicates that all immediate response requests are current for William Smith. The number “11” further labeled 1106 indicates that there are 11 request responses due in the future for John Welby.
The number “3” further labeled 1310 indicates that there are 3 lab test requests currently due for William Smith. The number “0” further labeled 1312 indicates that all action items are current for William Smith. The number “2” further labeled 1112 indicates that there are 2 lab reports ready for review by John Welby.
FIG. 4 depicts a usage flowchart performing a method for the first covering group member belonging to the covering group using the request list contains the request list component for each covering group member, in accordance with using certain usage embodiments.
User operation 2000 starts the usage of this flowchart. Arrow 2002 directs the usage flow from user operation 2000 to user operation 2004. User operation 2004 performs selecting a second of the covering group members belonging to the covering group. Arrow 2006 directs usage from user operation 2004 to user operation 2008. User operation 2008 performs selecting a first of the summaries of the request summary collection contained in the request list component for the second covering group member. Arrow 2010 directs usage from user operation 2008 to user operation 2012. User operation 2012 performs perceiving a request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising a requestor name, a requested item, a request response list containing at least two request responses. Arrow 2014 directs usage from user operation 2012 to user operation 2016. User operation 2016 terminates the usage of this flowchart.
Certain embodiments include a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list.
FIG. 4 also depicts a flowchart performing a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list in accordance with certain operational embodiments.
FIG. 5A depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group using the request list containing the request list component for each covering group member, in accordance with certain embodiments.
Arrow 2030 directs the usage flow from starting user operation 2000 to user operation 2032. User operation 2032 performs selecting a first of the request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component. Arrow 2034 directs usage from user operation 2032 to user operation 2036. User operation 2036 terminates the usage of this flowchart.
FIG. 5A also depicts a detail flowchart of operation 2000 of FIG. 4 further performing a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list in accordance with certain operational embodiments.
FIG. 5B depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group using the request list containing the request list component for each covering group member in accordance with certain embodiments.
Arrow 2050 directs the usage flow from starting user operation 2000 to user operation 2052. User operation 2052 performs selecting to send at least one of the preliminary request responses. Arrow 2054 directs usage from user operation 2052 to user operation 2056. User operation 2056 terminates the usage of this flowchart.
FIG. 5B also depicts a detail flowchart of operation 2000 of FIG. 4 further performing a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list in accordance with certain operational embodiments.
FIG. 5C depicts a detail flowchart of user operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses of the first summary component in accordance with certain embodiments.
Arrow 2070 directs the usage flow from starting user operation 2052 to user operation 2072. User operation 2072 performs selecting to send at least all of the preliminary request responses of the first summary component. Arrow 2074 directs usage from user operation 2072 to user operation 2076. User operation 2076 terminates the usage of this flowchart.
FIG. 5C also depicts a detail flowchart of operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses of the first summary component in accordance with certain operational embodiments.
FIG. 6A depicts a detail flowchart of user operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses in accordance with certain embodiments.
Arrow 2090 directs the usage flow from starting user operation 2052 to user operation 2092. User operation 2092 performs selecting to send at least all of the preliminary request responses. Arrow 2094 directs usage from user operation 2092 to user operation 2096. User operation 2096 terminates the usage of this flowchart.
FIG. 6A also depicts a detail flowchart of operation 2052 of FIG. 5B performing selecting to send at least all of the preliminary request responses in accordance with certain operational embodiments.
FIG. 6B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view of medication history response in accordance with certain embodiments.
Arrow 2110 directs the usage flow from starting user operation 2032 to user operation 2112. User operation 2112 performs selecting to create a view of medication history response. Arrow 2114 directs usage from user operation 2112 to user operation 2116. User operation 2116 terminates the usage of this flowchart.
FIG. 6B also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a view of medication history response in accordance with certain operational embodiments.
FIG. 6C depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view of appointment history response in accordance with certain embodiments.
Arrow 2130 directs the usage flow from starting user operation 2032 to user operation 2132. User operation 2132 performs selecting to create a view of appointment history response. Arrow 2134 directs usage from user operation 2132 to user operation 2136. User operation 2136 terminates the usage of this flowchart.
FIG. 6C also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a view of appointment history response in accordance with certain operational embodiments.
FIG. 7A depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a change prescription response in accordance with certain embodiments.
Arrow 2150 directs the usage flow from starting user operation 2032 to user operation 2152. User operation 2152 performs selecting to create a change prescription response. Arrow 2154 directs usage from user operation 2152 to user operation 2156. User operation 2156 terminates the usage of this flowchart.
FIG. 7A also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a change prescription response in accordance with certain operational embodiments.
FIG. 7B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a hold prescription response in accordance with certain embodiments.
Arrow 2170 directs the usage flow from starting user operation 2032 to user operation 2172. User operation 2172 performs selecting to create a hold prescription response. Arrow 2174 directs usage from user operation 2172 to user operation 2176. User operation 2176 terminates the usage of this flowchart.
FIG. 7B also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a hold prescription response in accordance with certain operational embodiments.
FIG. 7C depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a view pharmacy message response in accordance with certain embodiments.
Arrow 2190 directs the usage flow from starting user operation 2032 to user operation 2192. User operation 2192 performs selecting to create a view pharmacy message response. Arrow 2194 directs usage from user operation 2192 to user operation 2196. User operation 2196 terminates the usage of this flowchart.
FIG. 7C also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a view pharmacy message response in accordance with certain operational embodiments.
FIG. 8A depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a forward to primary care provider response in accordance with certain embodiments.
Arrow 2210 directs the usage flow from starting user operation 2032 to user operation 2212. User operation 2212 performs selecting to create a forward to primary care provider response. Arrow 2214 directs usage from user operation 2212 to user operation 2216. User operation 2216 terminates the usage of this flowchart.
FIG. 8A also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a forward to primary care provider response in accordance with certain operational embodiments.
FIG. 8B depicts a detail flowchart of user operation 2032 of FIG. 5A performing selecting to create a fill prescription response in accordance with certain embodiments.
Arrow 2230 directs the usage flow from starting user operation 2032 to user operation 2232. User operation 2232 performs selecting to create a fill prescription response. Arrow 2234 directs usage from user operation 2232 to user operation 2236. User operation 2236 terminates the usage of this flowchart.
FIG. 8B also depicts a detail flowchart of operation 2032 of FIG. 5A performing selecting to create a fill prescription response in accordance with certain operational embodiments.
FIG. 8C depicts a detail flowchart of user operation 2232 of FIG. 8B performing selecting to fill the prescription response in terms of units in accordance with certain embodiments.
Arrow 2250 directs the usage flow from starting user operation 2232 to user operation 2252. User operation 2252 performs selecting to fill the prescription response in terms of units. Arrow 2254 directs usage from user operation 2252 to user operation 2256. User operation 2256 terminates the usage of this flowchart.
FIG. 8C also depicts a detail flowchart of operation 2232 of FIG. 8B performing selecting to fill the prescription response in terms of units in accordance with certain operational embodiments.
FIG. 9A depicts a detail flowchart of user operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of one unit of the prescription in accordance with certain embodiments.
Arrow 2270 directs the usage flow from starting user operation 2252 to user operation 2272. User operation 2272 performs selecting to fill the prescription response in terms of one unit of the prescription. Arrow 2274 directs usage from user operation 2272 to user operation 2276. User operation 2276 terminates the usage of this flowchart.
FIG. 9A also depicts a detail flowchart of operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of one unit of the prescription in accordance with certain operational embodiments.
FIG. 9B depicts a detail flowchart of user operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of at least two units of the prescription in accordance with certain embodiments.
Arrow 2290 directs the usage flow from starting user operation 2252 to user operation 2292. User operation 2292 performs selecting to fill the prescription response in terms of at least two units of the prescription. Arrow 2294 directs usage from user operation 2292 to user operation 2296. User operation 2296 terminates the usage of this flowchart.
FIG. 9B also depicts a detail flowchart of operation 2252 of FIG. 8C performing selecting to fill the prescription response in terms of at least two units of the prescription in accordance with certain operational embodiments.
FIG. 10A depicts a detail flowchart of user operation 2232 of FIG. 8B performing selecting to fill the fill prescription response in terms of time duration in accordance with certain embodiments.
Arrow 2310 directs the usage flow from starting user operation 2232 to user operation 2312. User operation 2312 performs selecting to fill the fill prescription response in terms of time duration. Arrow 2314 directs usage from user operation 2312 to user operation 2316. User operation 2316 terminates the usage of this flowchart.
FIG. 10A also depicts a detail flowchart of operation 2232 of FIG. 8B performing selecting to fill the fill prescription response in terms of time duration in accordance with certain operational embodiments.
FIG. 10B depicts a detail flowchart of user operation 2000 of FIG. 4 further performing a method for the first covering group member belonging to the covering group of using the request list containing the request list component for each covering group member in accordance with certain embodiments, in accordance with certain embodiments.
Arrow 2330 directs the usage flow from starting user operation 2000 to user operation 2332. User operation 2332 performs selecting to create a new prescription. Arrow 2334 directs usage from user operation 2332 to user operation 2336. User operation 2336 terminates the usage of this flowchart.
FIG. 10B also depicts a detail flowchart of operation 2000 of FIG. 4 performing a method of operating a computer system by a first covering group member belonging to a covering group interacting with a request list in accordance with certain operational embodiments.
FIG. 11 depicts a detail flowchart of user operation 2332 of FIG. 10B further performing selecting to create the new prescription in accordance with certain embodiments.
Arrow 2350 directs the usage flow from starting user operation 2332 to user operation 2352. User operation 2352 performs selecting a patient identifier associated with the new prescription to create a patient with the new prescription. Arrow 2354 directs usage from user operation 2352 to user operation 2356. User operation 2356 terminates the usage of this flowchart.
Arrow 2360 directs the usage flow from user operation 2332 to user operation 2362. User operation 2362 performs selecting a medication associated with the new prescription to create a medication with the new prescription. Arrow 2364 directs usage from user operation 2362 to user operation 10B. User operation 10B terminates the usage of this operational flowchart.
Arrow 2370 directs the usage flow from user operation 2332 to user operation 2372. User operation 2372 performs selecting a dosage associated with the new prescription to create a dosage with the new prescription. Arrow 2374 directs usage from user operation 2372 to user operation 10B. User operation 10B terminates the usage of this flowchart.
Arrow 2380 directs the usage flow from user operation 2332 to user operation 2382. User operation 2382 performs selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription. Arrow 2384 directs usage from user operation 2382 to user operation 10B. User operation 10B terminates the usage of this flowchart.
Arrow 2390 directs the usage flow from user operation 2332 to user operation 2392. User operation 2392 performs selecting a prescription direction associated with the new prescription to create a direction with the new prescription. Arrow 2394 directs usage from user operation 2392 to user operation 10B. User operation 10B terminates the usage of this flowchart.
Arrow 2400 directs the usage flow from user operation 2332 to user operation 2402. User operation 2402 performs selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription. Arrow 2404 directs usage from user operation 2402 to user operation 10B. User operation 10B terminates the usage of this flowchart.
Arrow 2410 directs the usage flow from user operation 2332 to user operation 2412. User operation 2412 performs authorizing the new prescription with the patient identifier, with the medication, with the dosage, with the number of units, with the direction at the filling pharmacy. Arrow 2414 directs usage from user operation 2412 to user operation 10B. User operation 10B terminates the usage of this flowchart.
FIG. 11 also depicts a detail flowchart of operation 2332 of FIG. 10B further performing selecting to create the new prescription in accordance with certain operational embodiments.
FIG. 12A depicts a detail flowchart of user operation 2352 of FIG. 11 performing selecting a patient identifier associated with the new prescription to create a patient with the new prescription in accordance with certain embodiments.
Arrow 2430 directs the usage flow from starting user operation 2352 to user operation 2432. User operation 2432 performs perceiving a patient identifier list containing at least one patient identifier. Arrow 2434 directs usage from user operation 2432 to user operation 2436. User operation 2436 performs selecting a first of the patient identifiers of the patient identifier list to create the patient with the new prescription. Arrow 2438 directs usage from user operation 2436 to user operation 2440. User operation 2440 terminates the usage of this flowchart.
FIG. 12A also depicts a detail flowchart of operation 2352 of FIG. 11 further performing selecting the patient identifier associated with the new prescription to create a patient with the new prescription in accordance with certain operational embodiments.
FIG. 12B depicts a detail flowchart of user operation 2362 of FIG. 11 performing selecting the medication associated with the new prescription to create the medication with the new prescription in accordance with certain embodiments.
Arrow 2450 directs the usage flow from starting user operation 2362 to user operation 2452. User operation 2452 performs perceiving a medication list containing at least two medications. Arrow 2454 directs usage from user operation 2452 to user operation 2456. User operation 2456 performs selecting a first of the medications of the medication list to create the medication with the new prescription. Arrow 2458 directs usage from user operation 2456 to user operation 2460. User operation 2460 terminates the usage of this flowchart.
FIG. 12B also depicts a detail flowchart of operation 2362 of FIG. 11 further performing selecting the medication associated with the new prescription to create the medication with the new prescription in accordance with certain operational embodiments.
FIG. 13A depicts a detail flowchart of user operation 2372 of FIG. 11 performing selecting the dosage associated with the new prescription to create the dosage with the new prescription in accordance with certain embodiments.
Arrow 2470 directs the usage flow from starting user operation 2372 to user operation 2472. User operation 2472 performs perceiving a dosage list containing at least one dosage. Arrow 2474 directs usage from user operation 2472 to user operation 2476. User operation 2476 performs selecting a first of the dosages of the dosage list to create the dosage with the new prescription. Arrow 2478 directs usage from user operation 2476 to user operation 2480. User operation 2480 terminates the usage of this flowchart.
FIG. 13A also depicts a detail flowchart of operation 2372 of FIG. 11 further performing selecting the dosage associated with the new prescription to create the dosage with the new prescription in accordance with certain operational embodiments.
FIG. 13B depicts a detail flowchart of user operation 2362 of FIG. 11 performing selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription in accordance with certain embodiments.
Arrow 2510 directs the usage flow from starting user operation 2362 to user operation 2512. User operation 2512 performs perceiving a number of units list containing at least one number of units. Arrow 2514 directs usage from user operation 2512 to user operation 2516. User operation 2516 performs selecting a first of the number of units of the number of units list to create the number of units with the new prescription. Arrow 2518 directs usage from user operation 2516 to user operation 2520. User operation 2520 terminates the usage of this flowchart.
FIG. 13B also depicts a detail flowchart of operation 2362 of FIG. 11 further performing selecting a prescription unit number associated with the new prescription to create a number of units with the new prescription in accordance with certain operational embodiments.
FIG. 14A depicts a detail flowchart of user operation 2392 of FIG. 14A performing selecting a prescription direction associated with the new prescription to create a direction with the new prescription in accordance with certain embodiments.
Arrow 2530 directs the usage flow from starting user operation 2392 to user operation 2532. User operation 2532 performs perceiving a direction list containing at least one direction. Arrow 2534 directs usage from user operation 2532 to user operation 2536. User operation 2536 performs selecting a first of the directions of the direction list to create the direction with the new prescription. Arrow 2538 directs usage from user operation 2536 to user operation 2540. User operation 2540 terminates the usage of this flowchart.
FIG. 14A also depicts a detail flowchart of operation 2392 of FIG. 14A further performing selecting a prescription direction associated with the new prescription to create a direction with the new prescription in accordance with certain operational embodiments.
FIG. 14B depicts a detail flowchart of user operation 2402 of FIG. 11 performing selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription in accordance with certain embodiments.
Arrow 2550 directs the usage flow from starting user operation 2402 to user operation 2552. User operation 2552 performs perceiving a pharmacy list containing at least one pharmacy. Arrow 2554 directs usage from user operation 2552 to user operation 2556. User operation 2556 performs selecting a first of the pharmacies of the pharmacy list to create the pharmacy with the new prescription. Arrow 2558 directs usage from user operation 2556 to user operation 2560. User operation 2560 terminates the usage of this flowchart.
FIG. 14B depicts a detail flowchart of operation 2402 of FIG. 11 further performing selecting a pharmacy for filling the prescription to create a filling pharmacy for the new prescription in accordance with certain operational embodiments.
FIG. 15A depicts a detail flowchart of user operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, the number of units and with the direction to the filling pharmacy in accordance with certain embodiments.
Arrow 2570 directs the usage flow from starting user operation 2412 to user operation 2572. User operation 2572 performs sending the new prescription with the patient identifier, with the medication, with the dosage, with the number of units, with the direction to the filling pharmacy. Arrow 2574 directs usage from user operation 2572 to user operation 2576. User operation 2576 terminates the usage of this flowchart.
FIG. 15A also depicts a detail flowchart of operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, the number of units and with the direction to the filling pharmacy in accordance with certain operational embodiments.
FIG. 15B depicts a detail flowchart of user operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, with the number of units and with the direction at the filling pharmacy to a physician in accordance with certain embodiments.
Arrow 2590 directs the usage flow from starting user operation 2412 to user operation 2592. User operation 2592 performs sending the new prescription with the patient identifier, with the medication, with the dosage, with the number of units, with the direction at the filling pharmacy to a physician. Arrow 2594 directs usage from user operation 2592 to user operation 2596. User operation 2596 terminates the usage of this flowchart.
FIG. 15B also depicts a detail flowchart of operation 2412 of FIG. 11 performing sending the new prescription with the patient identifier, with the medication, with the dosage, with the number of units and with the direction at the filling pharmacy to a physician in accordance with certain operational embodiments.
FIG. 16 depicts a system block diagram for a computing system supporting the first covering group member interacting with a request list containing a request list component for each of the covering group members of the covering group.
In certain embodiments, the computing system comprises a computer 3120 operated 3110 by group member 3100 with accessibly coupled 3130 computer memory 3140 containing at least part of a program operating system executing within a browser operational platform 3160 supporting the first group member interaction.
In certain further embodiments, the computing system comprises a second computer 3220 operated 3210 by client 3200 with accessibly coupled 3230 computer memory 3240 containing at least part of a program operating system executing within a browser operational platform 3260 supporting the first group member interaction. Computer 3120 is communicatively coupled to computer 3220 via network 3330.
In certain further embodiments, the client 3220 may be someone working at a pharmacy. In certain other further embodiments, the client 3220 may be another group member. In certain other further embodiments, the client 3220 may be someone working at a on a care providers staff. In certain other further embodiments, the client 3220 may be a health care manager. In certain other further embodiments, the client 3220 may be someone working at a medical laboratory. In certain other further embodiments, the client 3220 may be a health care administrator. In certain other further embodiments, the client 3220 may be someone scheduling appointments for one or more members of the covering group.
In certain further embodiments, network 3330 is communicatively coupled 3310 to server system 3300. Server system 3300 contains 3360 at least one server computer 3320, which is accessibly coupled 3330 to computer memory 3340. In certain further embodiments, computer memory 3340 contains program code segments as part of the system level program operating system 3360 supporting the first covering group member interaction with the request list. In certain further embodiments, the program operating system program code segments are further organized for interaction in a fashion comparable to a web site 3360 as seen by the browser operational platform 3160 residing in the group member 3100 operated 3110 computer 3120.
In certain further embodiments, server system 3300 generates the request list. In certain further embodiments, server system 3300 generates at least one of the request list components. In certain further embodiments, server system 3300 generates all request list components. In certain further embodiments, server system 3300 generates at least one of the request detail reports. In certain further embodiments, server system 3300 generates all request detail reports.
In certain further embodiments, server system 3300 generates the medication history for a selected patient by the first covering group member. In certain further embodiments, server system 3300 generates the appointment history for a selected patient by the first covering group member.
In certain further embodiments, server system 3300 generates a medication list for the first covering group member. In certain further embodiments, server system 3300 generates an annotated medication list for the first covering group member. In certain further embodiments, the annotated medication list contains insurer compliance annotations.
In certain further embodiments, server system 3300 communicates 3410 with database server 3400 to retrieve information to generate a medication list for the first covering group member. In certain further embodiments, server system 3300 communicates 3410 with database server 3400 to retrieve information to generate an annotated medication list for the first covering group member. In certain further embodiments, the annotated medication list contains insurer compliance annotations. In certain further embodiments, database server 3400 may in turn access 3430 database 3420. In certain further embodiments, database server 3400 may in turn access 3430 several different databases 3420. In certain further embodiments, database 3420 may contain at least summary information provided by an insurer.
FIG. 17 depicts a viewing region component supporting changing a prescription, in accordance with certain embodiments.
FIG. 18 depicts a viewing region component supporting viewing a patient medical history, in accordance with certain embodiments.
FIG. 19 depicts a viewing region component supporting viewing a patient appointment history, in accordance with certain embodiments.
FIG. 20 depicts a viewing region component supporting starting a new prescription, in accordance with certain embodiments.
FIG. 21 depicts a viewing region component supporting creating a new prescription by selecting a patient, in accordance with certain embodiments.
FIG. 22 depicts a viewing region component supporting creating a new prescription showing the selected patient, in accordance with certain embodiments.
FIG. 23 depicts a viewing region component supporting creating a new prescription by selecting a pharmacy, in accordance with certain embodiments.
FIG. 24 depicts a viewing region component supporting creating a new prescription showing the selected patient and the selected pharmacy, in accordance with certain embodiments.
FIG. 25 depicts a viewing region component supporting creating a new prescription by selecting a medication, in accordance with certain embodiments.
FIG. 26 depicts a viewing region component supporting creating a new prescription showing the selected patient, the selected pharmacy and selected medication, in accordance with certain embodiments.
FIG. 27 depicts a viewing region component supporting creating a new prescription showing the selected patient, the selected pharmacy and selected medication, with directions and number of units, ready for authorization, in accordance with certain embodiments.
FIG. 28 depicts a viewing region component supporting creating a prior authorization request form for FORMULARY override for a new prescription, in accordance with certain embodiments.
FIG. 29 depicts a viewing region component supporting a prescription InBox Monitor of prescribing practitioners for use in health management and pharmacies, in accordance with certain embodiments.
FIG. 30 depicts a viewing region component supporting a pharmacy prescription lookup, in accordance with certain embodiments.
FIG. 31 depicts a viewing region component supporting a pharmacy prescription lookup response, in accordance with certain embodiments.
FIG. 32 depicts a viewing region component including a group monitor for prescriptions and referrals for a covering group with a New Referral link, in accordance with certain embodiments.
FIG. 33 depicts a viewing region component supporting selecting the patient for the new referral, in accordance with certain embodiments.
FIG. 34 depicts a viewing region component supporting selecting the department-referral type of the new referral for the selected patient, in accordance with certain embodiments.
FIG. 35 depicts a viewing region component supporting pre-requisite check-off given the department-referral type of the new referral for the selected patient, in accordance with certain embodiments.
FIG. 36 depicts a viewing region component supporting a consultant approval queue for referral requests, in accordance with certain embodiments.
FIG. 37 depicts a viewing region component supporting a referral request form with pre-requisite check-off given the department-referral type of the new referral for the selected patient, in accordance with certain embodiments.
FIG. 38 depicts a viewing region component supporting an appointment center queue for referral requests, in accordance with certain embodiments.
FIG. 39 depicts a viewing region component supporting an appointment request from a consulting medical practitioner with the department-referral type of the new referral for the selected patient, in accordance with certain embodiments.
FIG. 40 depicts a viewing region component supporting a consultant approval queue for referral requests, in accordance with certain embodiments.
FIG. 41 depicts a viewing region component supporting a referral pending appointment with consulting medical practitioner form, showing the department-referral type, prerequisite check-off list of the referral for the selected patient, in accordance with certain embodiments.
FIG. 42 depicts a viewing region component supporting a referral inbox based upon a referral group monitor, in accordance with certain embodiments.
FIG. 43 depicts a viewing region component supporting a consultant encounter report with the department-referral type for the selected patient, and the results of the encounter, in accordance with certain embodiments.
FIG. 44 depicts a viewing region component supporting a referral results summary based upon a referral group monitor, in accordance with certain embodiments.
FIG. 45 depicts a viewing region component supporting referral lookup, in accordance with certain embodiments.
FIG. 46 depicts a viewing region component supporting viewing a patient referral history, in accordance with certain embodiments.
FIG. 47 depicts a viewing region component supporting viewing a consultant encounter report referenced by a selecting a link of the patient referral history of FIG. 46, in accordance with certain embodiments.
FIG. 48 depicts a viewing region component supporting a referral volume report generator, in accordance with certain embodiments.
FIG. 49 depicts a viewing region component supporting a referral volume report resulting from the parameterization of the referral volume report generator associated with FIG. 48, in accordance with certain embodiments.
FIG. 50 depicts a viewing region component supporting a referral time lapse report generator, in accordance with certain embodiments.
FIG. 51 depicts a viewing region component supporting a referral time lapse report resulting from the parameterization of the referral time lapse report generator associated with FIG. 50, in accordance with certain embodiments.
FIG. 52 depicts a viewing region component supporting a referral time lapse report detail resulting from the selecting an underlined entry in the table of FIG. 51, in accordance with certain embodiments.
FIG. 53 depicts a viewing region component supporting a referral pending appointment with consultant form, in accordance with certain embodiments.
FIG. 54 depicts a viewing region component supporting a referral report selector, in accordance with certain embodiments.
FIG. 55 depicts a viewing region component supporting a referral report on OBG consultations by medical indication selected from the referral report selector of FIG. 54, in accordance with certain embodiments.
FIG. 56 depicts a viewing region component supporting a referral report on OBG consultations by length of wait for consultation selected from the referral report selector of FIG. 54, in accordance with certain embodiments.
FIG. 57 depicts a viewing region component supporting a referral report on the number of referrals by medical practitioner/department selected from the referral report selector of FIG. 54, in accordance with certain embodiments.
FIG. 58A depicts a detail flowchart of user operation 2032 of FIG. 5A further performing selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component in accordance with certain embodiments.
Arrow 2610 directs the usage flow from starting user operation 2032 to user operation 2612. User operation 2612 performs acoustically selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component is comprised of a member. Arrow 2614 directs usage from user operation 2612 to user operation 2616. User operation 2616 terminates the usage of this flowchart.
Arrow 2620 directs the usage flow from user operation 2032 to user operation 2622. User operation 2622 performs visually selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component is comprised of a member. Arrow 2624 directs usage from user operation 2622 to user operation 2616. User operation 2616 terminates the usage of this flowchart.
FIG. 58A depicts a detail flowchart of operation 2032 of FIG. 5A further performing selecting the first request responses of the request detail report for the first summary of the first summary component to create a preliminary request response of the first summary of the first summary component in accordance with certain operational embodiments.
FIG. 58B depicts a detail flowchart of user operation 2012 of FIG. 4 performing perceiving the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requestor name, the requested item, the request response list containing at least two request responses in accordance with certain embodiments.
Arrow 2630 directs the usage flow from starting user operation 2012 to user operation 2632. User operation 2632 performs hearing the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requestor name, the requested item, the request response list containing at least two request responses. Arrow 2634 directs usage from user operation 2632 to user operation 2636. User operation 2636 terminates the usage of this flowchart.
Arrow 2640 directs the usage flow from user operation 2012 to user operation 2642. User operation 2642 performs seeing the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requestor name, the requested item, the request response list containing at least two request responses. Arrow 2644 directs usage from user operation 2642 to user operation 2636. User operation 2636 terminates the usage of this flowchart.
FIG. 58B depicts a detail flowchart of operation 2012 of FIG. 4 performing perceiving the request detail report for the first summary of the request summary collection contained in the request list component for the second covering group member containing at least one request report comprising the requester name, the requested item, the request response list containing at least two request responses in accordance with certain operational embodiments.
The preceding embodiments have been provided by way of example and are not meant to constrain the scope of the following claims.

Claims

1. A method for a first covering group member belonging to a covering group containing at least two covering group members of using a request list containing a request list component for each of said covering group members of said covering group, each of said request list components further containing a request summary collection containing at least a past-due request summary and a immediately-due request summary, comprising the steps of:

selecting a second of said covering group members belonging to said covering group;

selecting a first of said summaries of said request summary collection contained in said request list component for said second covering group member; and

perceiving a request detail report for said first summary of said request summary collection contained in said request list component for said second covering group member containing at least one request report comprising a requester name, a requested item, a request response list containing at least two request responses.

2. A method as recited in claim 1, further comprising the step of:

selecting a first of said request responses of said request detail report for said first summary of said first summary component to create a preliminary request response of said first summary of said first summary component.

3. A method as recited in claim 2, further comprising the step of:

selecting to send at least one of said preliminary request responses.

4. A method as recited in claim 3,

wherein selecting to send at least one of said preliminary request responses further comprises the step of

selecting to send at least all of said preliminary request responses of said first summary component.

5. A method as recited in claim 3,

selecting to send at least all of said preliminary request responses.

6. A method as recited in claim 3,

wherein said requested item is a prescription; and

wherein said request summary collection further containing a future-due request summary.

7. A method as recited in claim 6,

wherein selecting said first request response of said request detail report for said first summary of said first summary component to create said preliminary request response of said first summary of said first summary component is comprised of the step of

selecting to create a view of medication history response.

8. A method as recited in claim 6,

wherein selecting said first request response of said request detail report for said first summary of said first summary component to create said preliminary request response of said first summary of said first summary component is further comprised of the step of

selecting to create a view of appointment history response.

9. A method as recited in claim 6,

selecting to create a change prescription response.

10. A method as recited in claim 6,

selecting to create a hold prescription response.

11. A method as recited in claim 6,

selecting to create a view pharmacy message response.

12. A method as recited in claim 6,

selecting to create a forward to primary care provider response.

13. A method as recited in claim 6,

selecting to create a fill prescription response.

14. A method as recited in claim 13,

wherein selecting to create said fill prescription response is further comprised of the step of

selecting to fill said prescription response in terms of units.

15. A method as recited in claim 13,

wherein selecting to fill said prescription response in terms of units is comprised of the step of

selecting to fill said prescription response in terms of one unit of said prescription.

16. A method as recited in claim 14,

selecting to fill said prescription response in terms of at least two units of said prescription.

17. A method as recited in claim 13,

selecting to fill said fill prescription response in terms of time duration.

18. A method as recited in claim 6, further comprising the step of

selecting to create a new prescription.

19. A method as recited in claim 18,

wherein selecting to create said new prescription is comprised of the steps of

selecting a patient identifier associated with said new prescription to create a patient with said new prescription;

selecting a medication associated with said new prescription to create a medication with said new prescription;

selecting a dosage associated with said new prescription to create a dosage with said new prescription;

selecting a prescription unit number associated with said new prescription to create a number of units with said new prescription;

selecting a prescription direction associated with said new prescription to create a direction with said new prescription;

selecting a pharmacy for filling said prescription to create a filling pharmacy for said new prescription; and

authorizing said new prescription with said patient identifier, with said medication, with said dosage, with said number of units, with said direction at said filling pharmacy.

20. A method as recited in claim 19,

wherein selecting said patient identifier associated with said new prescription to create said patient with said new prescription is comprised of the steps of

perceiving a patient identifier list containing at least one patient identifier; and

selecting a first of said patient identifiers of said patient identifier list to create said patient with said new prescription.

21. A method as recited in claim 19,

wherein selecting said medication associated with said new prescription to create said medication with said new prescription is comprised of the steps of

perceiving a medication list containing at least two medications; and

selecting a first of said medications of said medication list to create said medication with said new prescription.

22. A method as recited in claim 19,

wherein selecting said dosage associated with said new prescription to create said dosage with said new prescription is comprised of the steps of

perceiving a dosage list containing at least one dosage; and

selecting a first of said dosages of said dosage list to create said dosage with said new prescription.

23. A method as recited in claim 19,

wherein selecting a prescription unit number associated with said new prescription to create a number of units with said new prescription is comprised of the steps of

perceiving a number of units list containing at least one number of units; and

selecting a first of said number of units of said number of units list to create said number of units with said new prescription.

24. A method as recited in claim 19,

wherein selecting a prescription direction associated with said new prescription to create a direction with said new prescription is comprised of the steps of

perceiving a direction list containing at least one direction; and

selecting a first of said directions of said direction list to create said direction with said new prescription.

25. A method as recited in claim 19,

wherein selecting a pharmacy for filling said prescription to create a filling pharmacy for said new prescription is comprised of the steps of

perceiving a pharmacy list containing at least one pharmacy; and

selecting a first of said pharmacies of said pharmacy list to create said pharmacy with said new prescription.

26. A method as recited in claim 19,

wherein authorizing said new prescription with said patient identifier, with said medication, with said dosage, with said number of units, with said direction at said filling pharmacy is comprised of the step of

sending said new prescription with said patient identifier, with said medication, with said dosage, with said number of units, with said direction to said filling pharmacy.

27. A method as recited in claim 19,

sending said new prescription with said patient identifier, with said medication, with said dosage, with said number of units, with said direction at said filling pharmacy to a physician.

28. A method as recited in claim 6,

wherein said requested item is a referral; and

wherein said request summary collection further containing a referral result summary.

29. A method as recited in claim 6,

wherein said requested item is a laboratory test; and

wherein said request summary collection further containing a test result summary.

30. A method as recited in claim 2,

wherein selecting said first request responses of said request detail report for said first summary of said first summary component to create a preliminary request response of said first summary of said first summary component is comprised of a member of the collection comprising the steps of

acoustically selecting said first request responses of said request detail report for said first summary of said first summary component to create a preliminary request response of said first summary of said first summary component is comprised of a member; and

visually selecting said first request responses of said request detail report for said first summary of said first summary component to create a preliminary request response of said first summary of said first summary component is comprised of a member.

31. A method as recited in claim 1,

wherein perceiving said request detail report for said first summary of said request summary collection contained in said request list component for said second covering group member containing at least one request report comprising said requestor name, said requested item, said request response list containing at least two request responses is comprised of the steps of

hearing said request detail report for said first summary of said request summary collection contained in said request list component for said second covering group member containing at least one request report comprising said requestor name, said requested item, said request response list containing at least two request responses; and

seeing said request detail report for said first summary of said request summary collection contained in said request list component for said second covering group member containing at least one request report comprising said requestor name, said requested item, said request response list containing at least two request responses.

32.-124. (canceled)