Patent Grant
10552577
The present invention relates to a system and associated method for fulfillment of a medication requisition to be dispensed by a patient care provider for administration to a patient.
Patient care providers routinely dispense medication units for administration to patients in the course of providing health care services. In this regard, the dispensing and administration of medication units may require authorization by a governing regulatory body. The medication units may be prepared and/or otherwise dispensed by a pharmacy located at or otherwise affiliated with a given patient care provider or by third-party source(s). For example, many hospitals have an onsite pharmacy from which medication units may be dispensed after preparation at the pharmacy.
A number of factors may present logistical challenges to a patient care provider in fulfilling medication requisitions. For example, each medication unit to be dispensed by a given patient care provider may have a different associated fulfillment timing requirement to ensure timely dispensing and administration of the medication unit to the corresponding patient. Additionally, the scope of inventory needed for a pharmacy to accommodate a wide range of potential medication units may be difficult to maintain, particularly in relation to medication unit components having a limited shelf-life, demanding handling/storage requirements and/or otherwise experiencing supply shortages. Also, the preparation of certain types of mediation units necessitates specialized equipment, facilities and skills that may not be commonly available, thereby limiting sourcing options. Further, cost efficiencies may be unavailable to many patient care providers.
In addition to the foregoing, an emphasis on detailed record-keeping for medication units continues to grow in the healthcare field. Such record-keeping may entail the obtainment and storage of various data pertaining to the preparation and handling of medication units. In this regard, the administrative burden associated with such record-keeping continues to increase.
Currently, existing approaches for obtaining medication units largely entail source selection processes in which limited and/or static data is utilized to make a selection and/or in which sourcing selection options are otherwise limited.
The present disclosure generally relates to an improved system and associated method for fulfillment of a medication requisition to be dispensed by a patient care provider for administration to a patient.
In one aspect, an improved system comprises a requisition generator and a requisition fulfillment logic provided for use by a patient care provider. The requisition generator may be employed to generate a medication requisition for at least one contained unit of a medication to be dispensed by the patient care provider and administered to a patient. The requisition fulfillment logic may be executed by a computer-based tool to process a medication requisition and provide decision data for use in selecting one of a plurality of different fulfillment sites to fulfill the medication requisition. The decision data may be based, at least in part, on one of medication requisition fulfillment cost data and/or medication requisition fulfillment timing data corresponding with each of the plurality of fulfillment sites. The system may further include a requisition router to route a given medication requisition to a selected fulfillment site that is selected from the plurality of fulfillment sites for preparation of the medication requisition.
Accordingly, the system relieves a user of the patient care provider from, and/or assists user of the patient care provider in, the mental task of e.g. keeping track of inventory/availability of medication units with relation to fulfillment sites. Even more, the user may obtain the medication unit that best suits the patient care provider's needs from the appropriate fulfillment site. Moreover, the system implements improved man machine interaction, since the requisition router may route the medication requisition to the selected fulfillment site without the necessity of an interaction with the user of the patient care provider. In the context of this application, the term user of a patient care provider may relate to a human person, such as and not limited to an employee or an owner of a patient care provider.
As may be appreciated, the provision of a system having requisition fulfillment logic to provide decision data may facilitate the realization of enhanced cost efficiencies and/or timely medication requisition fulfillment by a patient care provider. For example, the decision data may be provided to assist the patient care provider in assessing trade-offs between utilizing different fulfillment sites in relation to a given medication requisition.
In contemplated embodiments, at least one or more than one of the plurality of fulfillment sites may be located remotely relative to the patient care provider. Further, at least another one of the plurality of fulfillment sites may be located at a patient care provider site corresponding with the patient care provider. For example, the patient care provider may have a pharmacy onsite or otherwise affiliated therewith. Hence, the system may, in an automated manner, allow a user of the patient care provider to select the most appropriate of a number of fulfillment sites without the necessity of accessing the individual fulfillment site. Moreover, the user of the patient care provider can reduce processing power at the patient care provider's site, by accessing and/or using processing power of one or more fulfillment sites.
In contemplated implementations, the patient care provider may comprise an entity that is authorized by a governing regulatory body to dispense medication requisitions. Further, the patient care provider may be an entity that is authorized by a governing regulatory body to prepare medication requisitions.
By way of primary example, the patient care provider may comprise one of the following:
In relation to the contemplated system, a contained medication unit corresponding with a given medication requisition may be obtained by a patient care provider from a selected fulfillment site for dispensing by the patient care provider for administration to a patient. In this regard, the contained medication unit may comprise one of the following:
In some implementations, a contained medication unit may be received by the patient care provider from a remote fulfillment site, wherein the contained medication unit may be associated with a kit comprising a plurality of contained medication units (e.g., a container used for handling the corresponding plurality of medication units). The association may be obtained or defined in a database and/or a table of a database that identifies for each contained medication unit a corresponding kit. Accordingly, for each contained medication unit and for each kit there may be a direct relation between exactly one specific contained medication unit and one specific kit. In this regard, the different medication requisitions corresponding with the plurality of contained medication units comprising the kit may be associated with a corresponding kit identifier, thereby facilitating various record-keeping functionalities, e.g., the obtainment and maintenance of certain medication requisition metadata referenced hereinbelow. For example, a kit identifier (e.g., a machine-readable marking on a container used for handling the corresponding plurality of medication units) may be utilized to facilitate data collection in relation to the location, handling, etc., of the associated medication units. Accordingly, the system allows in a simple and efficient manner to provide a specific contained medication unit with a number (i.e., a kit of) contained medication units, and maintain records relating thereto, without needing to separately obtain/record information for each individual/specific medication unit (e.g., in relation to location, handling, etc.). In particular, in view of the complexity of organizing a chain of products, the system provides in a simple and automated manner obtaining a specific medication unit while providing a kit of medication units. The system may particularly comprise a computing environment implementing or being part of the requisition generator and/or the requisition fulfillment logic and/or the requisition router.
As noted, the system may comprise requisition fulfillment logic to provide decision data based in part on at least one of medication requisition fulfillment cost data and/or medication requisition fulfillment timing data corresponding with each of a plurality of fulfillment sites. Such data may be stored and otherwise maintained in a medication requisition database.
The medication requisition fulfillment timing data may comprise at least one of the following:
In contemplated system embodiments, each of the plurality of fulfillment sites may provide all or at least a portion of the medication requisition fulfillment cost data and/or medication requisition fulfillment timing data corresponding with the given fulfillment site. More particularly, such data (simply referred to as medication requisition data) may be provided by the fulfillment sites to the medication requisition database. For example, the data may be provided on a periodic, request/response, or other basis. By way of further example, the data may be provided in relation to predetermined types or otherwise specified medication units.
In some embodiments the requisition fulfillment logic may comprise one or more algorithms (e.g., stored in a computer-readable medium) for processing the medication requisition (e.g., by a computer) in relation to medication requisition fulfillment cost data and/or medication requisition fulfillment timing data stored at the medication requisition database. In one approach, an algorithm may provide for the selective establishment of weighting parameters associated with each of medication requisition fulfillment cost data and/or medication requisition fulfillment timing data (e.g., via software program instructions/user input).
In some applications, the requisition fulfillment logic may be provided to be customizable by a given patient care provider. By way of example, a given patient care provider may set algorithm weighting parameters and/or may define additional logic parameters.
In certain implementations, the requisition fulfillment logic may be operable to automatically select a fulfillment site to fulfill a given medication requisition based on the generated decision data. As may be appreciated, such automated selection functionality may be established in relation to predetermined types of medication requisitions. Further, in some embodiments, the requisition router may be operable to automatically route medication requisitions to an automatically selected fulfillment site. Accordingly, without the need of human interaction, the system may allow for efficient drug medication requisition fulfillment. In particular, the efficiency may be improved by the system becoming more failsafe as the router is not prone to errors a human may make.
In some arrangements, the selected fulfillment site may be adapted to selectively, automatically and/or semi-automatically reject a given medication requisition routed to it (e.g., in the event of unforeseen or other circumstances). In turn, a requisition rejection may be communicated by the fulfillment site (e.g., in a selective, automatic and/or semi-automatic manner) to the fulfillment logic and medication requisition database, wherein the requisition fulfillment logic is further utilized to provide decision data for use selecting a different fulfillment site. Correspondingly, the medication requisition database may be updated in relation to the medication requisition.
In contemplated embodiments, the fulfillment site selected to fulfill a given medication requisition may be adapted to provide medication requisition metadata to a medication requisition database in relation to fulfillment of the medication requisition. In this regard, the selected fulfillment site may follow predetermined procedures and/or utilize data collection tools to obtain and provide medication requisition metadata in relation to the preparation, handling, etc., of a medication unit corresponding with a given medication requisition, and to provide medication requisition metadata to the medication requisition database. In turn, the system may be provided so that the patient care provider corresponding with a given medication requisition may access at least a portion of the corresponding medication requisition metadata from the medication requisition database.
The medication requisition metadata may comprise one or more of the following types of data:
In various implementations, the contemplated system may include a distributed medication requisition management system that includes a distributed medication requisition management client at each of the plurality of fulfillment sites and in operative communication with the requisition router so as to receive medication requisitions from the requisition router. In turn, the system may further include a medication requisition management network that includes the distributed medication requisition management clients, the medication requisition database, and the requisition router. In such implementations, the system may be maintained so that at least portions of the corresponding medication requisition metadata are located at separate physical locations.
In another aspect, a distributed medication requisition management system may comprise a requisition generator to generate a medication requisition for at least one contained unit of a medication for dispensing by a patient care provider, and a medication requisition database operable to store the medication requisition. The system may further include a plurality of medication requisition management clients resident in a plurality of fulfillment sites capable of fulfilling a medication requisition. A medication requisition management network may be provided in operative communication with each of the plurality of medication requisition management clients, the medication requisition database, and the requisition generator, wherein the medication requisition management network is operable to provide the medication requisition to the medication requisition management client of a selected fulfillment site of the plurality of fulfillment sites. The system may be provided so that the patient care provider obtains a contained medication unit corresponding with the medication requisition from the selected fulfillment site for dispensing and administration to a corresponding patient, and wherein the selected fulfillment site provides medication requisition metadata to the medication requisition management network for storage in the medication requisition database in corresponding relation to the medication requisition.
As may be appreciated, various ones and combinations of the functionalities noted hereinabove may be utilized in the distributed medication requisition management system.
In a further aspect, a method for fulfillment of a medication requisition to be dispensed by a patient care provider, for administration to a patient is provided. In some embodiments, the method may include generating a medication requisition by use of a requisition generator by a patient care provider, wherein the medication requisition is for at least one contained unit of a medication for administration to a patient. The method may further comprise processing the medication requisition, by use of requisition fulfillment logic by a patient care provider and executed by a computer-based tool, wherein the processing provides decision data for use in selecting one of a plurality of fulfillment sites to fulfill the medication requisition. In this regard, decision data may be based at least in part on one of medication requisition fulfillment cost data or medication requisition fulfillment timing data corresponding to each of the plurality of fulfillment sites. Further, the method may include routing of the medication requisition by a requisition router to a selected fulfillment site selected from the plurality of fulfillment sites for preparation of the medication requisition.
In some embodiments, the method may further include selecting automatically, by operation of the requisition fulfillment logic, the selected fulfillment site at least partially based on the decision data. Additionally, or alternatively, the method may further comprise routing automatically, by operation of the router, the medication requisition to the selected fulfillment site for fulfillment of the medication requisition. In various method embodiments, the method may employ a system comprising any of the system features described herein.
According to yet another aspect, a computer program product is provided that can be stored on a computer readable medium and/or can be implemented as computer processable data stream, wherein the computer program product comprises computer processable instructions, which instructions when read in the memory of a computer and executed by the computer cause the computer to carry out the method(s) as described in general above, and in more specific examples below.
Numerous additional features and advantages of the present invention will become apparent to those skilled in the art upon consideration of the embodiment descriptions provided hereinbelow.
The system 100 may include a number of components that may be used to generate a medication requisition, to prepare decision data for use in the selection of a fulfillment site for fulfillment of the medication requisition, and to route a given medication requisition to a selected fulfillment site. In this regard, the components of the system 100 may include a requisition generator 20, requisition fulfillment logic 30, and a requisition router 40, respectively. By way of example, the requisition generator 20, requisition fulfillment logic 30, and a requisition router 40 may be located at a patient care provider 10.
The requisition generator 20 may generate a medication requisition corresponding to a medication unit that is to be used or dispensed by the patient care provider 10 for administration to a patient 70. The requisition generator 20 may be operable to generate the medication requisition in an automated or partially automated manner based on an order comprising a data stream. By way of example, the order may correspond with a medication prescribed by a physician.
In one approach, the requisition generator 20 may be operable to parse or otherwise derive data from a data stream to generate the medication requisition. Additionally or alternatively, the requisition generator 20 may generate a medication requisition based on data that is received directly from a user (e.g., by way of data entry via a user interface).
The requisition generator 20 may be operable to provide the medication requisition for processing by requisition fulfillment logic 30. Requisition fulfillment logic 30 may comprise a computer-based tool (e.g., including hardware and/or software) for providing decision data for use in selecting one of a plurality of fulfillment sites to fulfill a given medication requisition. The computer-based tool may comprise a memory operable to store non-transitory machine-readable instructions that may be executed by a processor. Requisition fulfillment logic 30 may further include or access a database that may be used by the requisition fulfillment logic 30 to produce the decision data.
The data utilized by requisition fulfillment logic 30 to provide the decision data may at least include medication requisition preparation cost data and/or medication requisition preparation timing data that corresponds to a plurality of potential fulfillment sites that have the ability to fulfill the medication requisition. For example, as shown in
In this regard, the requisition fulfillment logic 30 may provide the decision data to a user (e.g., provided to a user at the patient care provider 10 via a user interface device). The user may then select one of the plurality of fulfillment sites for fulfillment of the medication requisition (e.g., via input at a user interface). In an embodiment, requisition fulfillment logic 30 may automatically select a fulfillment site at least partially based on the decision data for a given medication requisition. Optionally, a determination as to whether a fulfillment site is selected by a user or automatically selected may at least partially depend upon an identifiable characteristic of a given medication requisition (e.g., dependent upon medication type, medication amount, timing requirements, or other data associated with the medication requisition). In this regard, potential time and cost savings may be realized.
As noted, a requisition router 40 may be provided to route the medication requisition to the selected fulfillment site for fulfillment of the medication requisition. As schematically presented in
Regardless of the relative location of the selected fulfillment site, the requisition router 40 may be operable to communicate the medication requisition to the selected fulfillment site. The requisition router 40 may receive the identity of the selected fulfillment site from a user (e.g., a user at the patient care provider 10) or may automatically route the medication requisition order to the selected fulfillment site based on the automatic selection of a fulfillment site by the requisition fulfillment logic 30.
One or more of the fulfillment sites 60a and 60b may be adapted to selectively, automatically and/or semi-automatically reject a given medication requisition routed to it (e.g., in the event of unforeseen circumstances). In turn, a requisition rejection may be communicated by the fulfillment site 60a or 60b (e.g., in a selective, automatic and/or semi-automatic manner) to requisition fulfillment logic 30 and medication requisition database 90, wherein the requisition fulfillment logic 30 is further utilized to provide decision data for use selecting a different fulfillment site. Correspondingly, the medication requisition database 90 may be updated in relation to the medication requisition.
As stated above, the fulfillment sites may include one or more remote fulfillment sites 60a and 60b located remotely relative to the patient care provider 10. Furthermore, the patient care provider 10 may include a patient care provider site that may include a pharmacy 50. In turn, the pharmacy 50 may include a fulfillment site 55 located in the pharmacy 50. It may also be appreciated that the patient care provider 10 may be affiliated with a pharmacy 50 that is located offsite relative to the patient care provider site. In any regard, each of the fulfillment sites 55, 60a, and 60b may be capable of fulfilling a medication requisition and providing the medication unit corresponding to the medication requisition to the pharmacy 50. In turn, the pharmacy 50 may be operable to dispense the medication unit for administration to the patient 70.
Additionally, as depicted in
The medication requisition database 90 may be located in a single location that is either remote from or local to one or more of the patient care provider site or remote fulfillment sites. The medication requisition database 90 may also be provided at a separate location distinct from either the patient care provider site or remote fulfillment site. Further, the medication requisition database 90 may comprise a number of portions or instances that may each be located at separate locations corresponding to or separate from the patient care provider site or remote fulfillment sites.
For example, the medication requisition database 90 may store medication requisition metadata related to the medication requisition. Furthermore, the medication requisition database 90 may store the medication requisition fulfillment cost data and the medication requisition fulfillment timing data employed by the requisition fulfillment logic 30 to produce the decision data for use in selecting one of the plurality of fulfillment sites to fulfill the medication requisition. In this regard, the remote fulfillment sites 60a and 60b may be in operative communication with the medication requisition database 90 to provide medication requisition fulfillment cost data and medication requisition fulfillment timing data corresponding to each respective fulfillment site to the medication requisition database 90.
The medication requisition database 90 may be located remotely from the remote fulfillment sites 60a and 60b as well as the patient care provider 10. Alternatively, the medication requisition database 90 may be located at one of the remote fulfillment sites 60a or 60b or at the patient care provider 10. In any regard, access to the medication requisition database 90 may be facilitated via the medication requisition management network 80.
As may be appreciated, the patient care provider 10 may include an entity authorized by a governing regulatory body (e.g., a pharmacy board) to dispense and prepare medication units for administration to patients. In this regard, the patient care provider may include an authorized entity capable of compounding or otherwise preparing contained medication units for administration to patients. Primarily, examples of patient care providers include the following:
In an application, the patient care provider may be a hospital having an affiliated pharmacy. It may be appreciated that the affiliated pharmacy may be located onsite with respect to the hospital or the hospital may be affiliated with an offsite pharmacy. In either regard, the medication unit associated with the medication requisition may be administered to the patient at the patient care provider site by the patient care provider. In the case of an offsite pharmacy, the offsite pharmacy may service a plurality of different affiliated hospital sites.
As stated above the medication requisitions generated by the requisition generator 20 may each correspond to a contained unit of a medication for administration to patient. The contained medication unit may be a patient specific unit comprising a medication unit designated for administration to a specific patient. In an embodiment, the contained medication unit may include a non-patient specific unit to be subsequently designated for administration to a specific patient. In an embodiment, a contained medication unit may be a medical source unit (e.g., a compounded or other ingredient) to be used in the preparation of a patient specific unit and/or a non-patient specific unit.
In various embodiments, the contained medication unit may correspond to a variety of different substances that require licensure or other authorization by governing body to prepare. Examples of contained medication units that may correspond to medication requisitions include:
The medication requisition generated by the requisition generator 20 may include data indicative of one or more properties or requirements of the medication requisition. In this regard, the medication requisition may include:
In any regard, the requisition fulfillment logic 30 may receive the medication requisition and be operable to compare the medication requisition (e.g., medication identity, medication amount, medication concentration, scheduled dispensation time, etc.) in relation to the medication requisition preparation timing data and/or the medication requisition preparation cost data for the plurality of fulfillment sites to determine the decision data for use in determining which fulfillment site may be capable of, or best suited to, fulfill the medication requisition.
In one example, the requisition fulfillment logic 30 may determine which fulfillment site or sites from the plurality of fulfillment sites is capable of fulfilling a medication requisition based on whether a fulfillment site can fulfill the medication requisition prior to the scheduled dispensation time for the medication requisition. In this regard, the medication requisition fulfillment timing data may include, for example:
Of those fulfillment sites capable of fulfilling a medication requisition in accord with the scheduled administration time, the medication requisition fulfillment cost data may in turn be used to determine which of the eligible fulfillment sites represent the lowest cost for the fulfillment of the medication requisition. In this regard, the fulfillment site with the lowest cost of fulfillment capable of fulfilling in time for the scheduled administration of the medication unit associated with the medication requisition may be identified as the selected fulfillment site. However, other logic may be applied that may for example, strike different balances between considerations of medication requisition fulfillment cost data, medication requisition fulfillment timing data, or other relevant information for use in producing the decision data. In this regard, the applied logic may be as selectively established by a given patient care provider 10. For example, an algorithm may be established with weighting parameters associated with the relative importance of the medication requisition fulfillment cost data relative to the medication requisition fulfillment timing data. In an example, the patient care provider 10 may predetermine or have control over the weighting of the data. Other factors or data may also be weighted in the algorithm used to arrive at the decision data.
In contemplated implementations, the patient care provider 10 may be able to customize the algorithm and/or factors considered in providing a decision data. For example, the patient care provider may provide overriding conditions that dictate selection of a selected fulfillment site regardless of the decision data. The overriding condition may be based on medication requisitions generated in a specific period, of a specific kind, for administration in a certain period, or other factors related to the medication requisition or fulfillment of the medication requisition.
With further respect to the requisition router 40, as discussed above, the requisition router 40 may be operable to route a medication requisition to a selected one of a plurality of fulfillment sites. As such, the requisition router 40 may be in direct communication with each of the remote fulfillment sites 60a and 60b as well as the fulfillment site 55 located in the pharmacy 50 of the patient care provider 10. In an embodiment, the routing of medication requisitions from the requisition router 40 to the selected fulfillment site may occur in substantially real-time upon selection of the fulfillment site. In an embodiment, the routing of a medication requisition to the selected fulfillment site may occur periodically as either initiated by the requisition router 40 or the selected fulfillment site. The requisition router 40 may be operable to transmit a group or batch of individual medication requisitions to a single fulfillment site simultaneously in the case where the fulfillment site has been selected as the selected fulfillment site for a number of medication requisitions.
In an embodiment, the requisition router 40 may provide medication requisitions to a fulfillment site by way of the medication requisition management network 80. In this regard, rather than direct communication between the requisition router 40 and remote fulfillment sites 60a and 60b, the requisition router 40 may communicate with remote fulfillment sites 60a and 60b by way of the medication requisition management network 80.
Each fulfillment site may be operable to provide medication requisition metadata to the medication requisition database 90 (e.g., either directly or via the medication requisition management network 80) regarding medication requisition fulfillment at the fulfillment site. The medication requisition metadata may include details regarding the composition, preparation, transportation, or other data concerning the medication requisition. The medication requisition metadata may be maintained in corresponding relation to a medication requisition record in the medication requisition database 90. The medication requisition metadata may be periodically updated by a fulfillment site before, during, or after fulfillment of the medication requisition. This may be particularly advantageous in the case of remote fulfillment sites as the patient care provider 10 may access the medication requisition database 90 to obtain information regarding the medication requisition during fulfillment by the remote fulfillment site. However, even in the case of an onsite fulfillment site (e.g., fulfillment site 55), medication requisition metadata may still be provided to the medication requisition database (e.g., to maintain records corresponding to the medication requisition).
The medication requisition metadata may include data corresponding to a plurality of different classes of data relating to the medication requisition including:
In addition, in the case of the remote fulfillment site 60a or 60b, the remote fulfillment site may dispatch the medication requisition for physical delivery to patient care provider 10 for administration to the patient 70. Accordingly, the remote fulfillment sites 60a and 60b may be able to ship or otherwise physically dispatch the medication requisition to patient care provider 10. As such, the remote fulfillment site may utilize dedicated delivery vehicles and/or third party delivery services. In either or any regard, the mode of physically dispatching the medication requisition may include tracking data associated with the transport of the medication requisition.
In an embodiment, a remote fulfillment site may collectively send more than one medication requisition to the patient care provider 10. In this regard, a kit may be sent from the remote fulfillment site to the patient care provider 10. The kit may include a plurality of medication requisitions destined to the same patient care provider 10. As such, the kit may include a kit identification. Each medication requisition disposed in the kit may be correlated to the kit identification. In this regard, once the kit is received at the patient care provider, the kit identification may be used to determine that each of the plurality of medication requisitions associated with the kit have likewise been received. Furthermore, any one of the medication requisitions identified that is associated with the kit may indicate that each of the other medication requisitions associated with the kit have been received.
Accordingly, the remote fulfillment site may also provide to the medication requisition management network 80 the kit identification and correlated medication requisitions associated with the kit. In turn, the kit identification and data regarding the correlated medication requisitions associated with the kit may be provided to the patient care provider 10 and/or the medication requisition database 90 for storage.
In an embodiment, each fulfillment site may include a medication requisition management client. The medication requisition management client may be in operable communication with the medication requisition management network 80, wherein the medication requisition management client is operable to receive/send data corresponding with a medication requisition to/from from the medication requisition management network 80. In this regard, the medication requisition management client may be employed by the fulfillment site to assist in the preparation of the medication unit associated with a medication requisition in a manner that also generates or documents medication requisition metadata as described above.
The medication requisitions may be passed on to a requisition preparation management system 230. The requisition preparation management system 230 may be operable to organize 232 medication requisitions received at the medication requisition preparation management client 210. The organization may include prioritization, scheduling, or other tasks associated with the organization or management of medication requisitions. The medication requisition preparation management client 230 may also be operative to route 234 medication requisitions to an appropriate work station 240. In this regard, a plurality of work stations 240 may be provided that may each be suited for different tasks or work flows. As such, depending on the nature of a medication requisition, a particular type of work station 240 may be used to prepare the requisition.
In this regard, the medication requisition preparation management system 230 may be in operative communication with one or more work stations 240. The routing 234 of medication requisitions may be at least partially based on the nature or type of the medication unit and the capabilities of the various work stations 240. In an embodiment, other parameters such as technician schedules, work station schedules, work station location, or other information may be used alone or in combination to route 234 medication requisitions to a particular work station 40.
At the work station 240, a work flow may be prepared 242 that may be used for the preparation of the medication requisition. In this regard, a work flow that is specific to the medication requisition currently being prepared at the work station 240 may be generated and presented to a user at the work station 240. Accordingly, the user may follow a sequence of steps to prepare the medication unit corresponding to the medication requisition based on the prepared work flow presented.
During and/or after the preparation of the medication requisition, the work station 240 may be used to assist in checking 244 the preparation of the medical order. For example, the work station 240 may allow for recording of documentation regarding the preparation of the medication unit such as, for example, barcode scans of products, images of apparatus during or after use in the preparation of the medication unit, or other information related to the preparation of the medication unit. This data may correspond to at least a portion of the medication requisition metadata described above.
Such information collected for the checking 244 may be stored for viewing by appropriate personnel (e.g., a pharmacist) so that the pharmacist may verify the prepared medication requisition prior to the medication requisition leaving the fulfillment site 200. In an embodiment, the information and/or data collected at the work station 240 may be made available to a pharmacist via a network (e.g., the medication requisition management network 80). In this regard, it may be also appreciated that alternate or additional pharmacists (e.g., a pharmacist at the patient care provider 10) may provide concurrent or additional reviews of the medication unit associated with a medication requisition being fulfilled. In any regard, the pharmacist tasked with verifying a medication requisition may access the information and/or data remotely (e.g., in a location in the fulfillment site but outside the room where the medication unit has been prepared or even entirely removed from the fulfillment site premises) via the network 80.
Once the medication requisition has been prepared in accordance with the prepared 242 work flow and checked 242 at workstation 240, the medication requisition preparation management system 230 may send medication requisition metadata to the medication requisition management network 80 for storage in the medication requisition database 90 and/or permission to patient care provider 10. In turn, the medication requisition preparation management system 230 may manage dispatching 238 the medication requisition to the patient care provider 10. In this regard, the medication requisition preparation management system 230 may oversee physical shipment of the medication requisition to the patient care provider 10 in addition to providing data regarding the dedication requisition to the medication requisition management network 80.
Patient care providers currently have limited access to sources of medication units needed for patient care. This limitation derives primarily from the current limitations of their systems and processes to enable only static choices for each specific type of medication unit. These static choices are often determined through completely manual procurement/evaluation processes, and are only revisited episodically. This often results in higher than optimal costs for meeting the provider's needs for medication units, and seriously limits the ability of the patient care provider to efficiently and rapidly respond to events—such as drug shortages or local events that generate significant supply/demand changes—that require a different sourcing approach.
Upon implementation of the present invention, patient care providers will be able to define a set of dynamically-applied rules for selecting sources of each specific type of medication units. This dynamic response capability will enable needs for medication units to be more reliably met on a timely basis, more efficient and effective response for local events and supply issues, and lower cost of medication units taking into consideration new sources of supply.
The foregoing description of the present invention has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, and skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain known modes of practicing the invention and to enable others skilled in the art to utilize the invention in such or other embodiments and with various modifications required by the particular application(s) or use(s) of the present invention. It is intended that the appended claims be construed to include alternative embodiments to the extent permitted by the prior art.
This application claims priority to U.S. Provisional Patent Application No. 61/695,831 filed Aug. 31, 2012, entitled “MEDICATION REQUISITION FULFILLMENT SYSTEM AND METHOD,” which application is incorporated herein by reference in its entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2013/031707 | 3/14/2013 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2014/035478 | 3/6/2014 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 641748 | Smith | Jan 1900 | A |
| 819339 | Cleland | May 1906 | A |
| 3426150 | Tygart | Feb 1969 | A |
| 3739943 | Williamsen et al. | Jun 1973 | A |
| 3742938 | Stern | Jul 1973 | A |
| 3756752 | Stenner | Sep 1973 | A |
| 3774762 | Lichtenstein | Nov 1973 | A |
| 3786190 | Pori | Jan 1974 | A |
| 3809871 | Howard et al. | May 1974 | A |
| 3810102 | Parks, III et al. | May 1974 | A |
| 3848112 | Weichselbaum et al. | Nov 1974 | A |
| 3858574 | Page | Jan 1975 | A |
| 3878967 | Joslin et al. | Apr 1975 | A |
| 3910257 | Fletcher et al. | Oct 1975 | A |
| 3910260 | Sarnoff et al. | Nov 1975 | A |
| 3921196 | Patterson | Nov 1975 | A |
| 3971000 | Cromwell | Jul 1976 | A |
| 3995630 | Verrdonk | Dec 1976 | A |
| 3998103 | Bjorklund et al. | Dec 1976 | A |
| 4032908 | Rice et al. | Jun 1977 | A |
| 4078562 | Friedman | Mar 1978 | A |
| 4144496 | Cunningham et al. | Mar 1979 | A |
| 4151407 | McBride et al. | Apr 1979 | A |
| 4156867 | Bench et al. | May 1979 | A |
| 4164320 | Irazoqui et al. | Aug 1979 | A |
| 4173971 | Karz | Nov 1979 | A |
| 4199307 | Jassawalla | Apr 1980 | A |
| 4270532 | Franetzki et al. | Jun 1981 | A |
| 4273121 | Jassawalla | Jun 1981 | A |
| 4282872 | Franetzki et al. | Aug 1981 | A |
| 4308866 | Jelliffe et al. | Jan 1982 | A |
| 4319338 | Grudowski et al. | Mar 1982 | A |
| 4320757 | Whitney et al. | Mar 1982 | A |
| 4354252 | Lamb et al. | Oct 1982 | A |
| 4369780 | Sakai | Jan 1983 | A |
| 4370983 | Lichtenstein | Feb 1983 | A |
| 4373527 | Fischell | Feb 1983 | A |
| 4381776 | Latham, Jr. | May 1983 | A |
| 4385630 | Gilcher et al. | May 1983 | A |
| 4398289 | Schoate | Aug 1983 | A |
| 4398908 | Siposs | Aug 1983 | A |
| 4414566 | Peyton et al. | Nov 1983 | A |
| 4416654 | Schoendorfer et al. | Nov 1983 | A |
| 4425114 | Schoendorfer et al. | Jan 1984 | A |
| 4428381 | Hepp | Jan 1984 | A |
| 4443216 | Chappell | Apr 1984 | A |
| 4447224 | DeCant, Jr. et al. | May 1984 | A |
| 4449538 | Corbitt et al. | May 1984 | A |
| 4451255 | Bujan et al. | May 1984 | A |
| 4457750 | Hill | Jul 1984 | A |
| 4458693 | Badzinski et al. | Jul 1984 | A |
| 4460358 | Somerville et al. | Jul 1984 | A |
| 4464172 | Lichtenstein | Aug 1984 | A |
| 4469481 | Kobayashi | Sep 1984 | A |
| 4475901 | Kraegen et al. | Oct 1984 | A |
| 4476381 | Rubin | Oct 1984 | A |
| 4480751 | Lueptow | Nov 1984 | A |
| 4481670 | Freeburg | Nov 1984 | A |
| 4487604 | Iwatschenko et al. | Dec 1984 | A |
| 4490798 | Franks et al. | Dec 1984 | A |
| 4496351 | Hillel et al. | Jan 1985 | A |
| 4511352 | Theeuwes et al. | Apr 1985 | A |
| 4525861 | Freeburg | Jun 1985 | A |
| 4529401 | Leslie et al. | Jul 1985 | A |
| 4531527 | Reinhold, Jr. et al. | Jul 1985 | A |
| 4538138 | Harvey et al. | Aug 1985 | A |
| 4545071 | Freeburg | Oct 1985 | A |
| 4551133 | Zegers de Beyl et al. | Nov 1985 | A |
| 4559038 | Berg et al. | Dec 1985 | A |
| 4560979 | Rosskopf | Dec 1985 | A |
| 4561443 | Hogrefe et al. | Dec 1985 | A |
| 4562751 | Nason | Jan 1986 | A |
| 4564054 | Gustaysson | Jan 1986 | A |
| 4590473 | Burke et al. | May 1986 | A |
| 4602249 | Abbott | Jul 1986 | A |
| 4619653 | Fischell | Oct 1986 | A |
| 4622979 | Katchis et al. | Nov 1986 | A |
| 4624661 | Arimond | Nov 1986 | A |
| 4636950 | Caswell et al. | Jan 1987 | A |
| 4637817 | Archibald et al. | Jan 1987 | A |
| 4650469 | Berg et al. | Mar 1987 | A |
| 4652262 | Veracchi | Mar 1987 | A |
| 4653010 | Figler et al. | Mar 1987 | A |
| 4676776 | Howson | Jun 1987 | A |
| 4681563 | Deckert et al. | Jul 1987 | A |
| 4688167 | Agarwal | Aug 1987 | A |
| 4691580 | Fosslien | Sep 1987 | A |
| 4695954 | Rose et al. | Sep 1987 | A |
| 4696671 | Epstein et al. | Sep 1987 | A |
| 4697928 | Csongor | Oct 1987 | A |
| 4702595 | Mutschler et al. | Oct 1987 | A |
| 4705506 | Archibald | Nov 1987 | A |
| D293135 | Medema et al. | Dec 1987 | S |
| 4714462 | DiComenico | Dec 1987 | A |
| 4717042 | McLaughlin | Jan 1988 | A |
| 4718576 | Tamura et al. | Jan 1988 | A |
| 4722224 | Scheller et al. | Feb 1988 | A |
| 4722349 | Baumberg | Feb 1988 | A |
| 4722734 | Kolln | Feb 1988 | A |
| 4730849 | Siegel | Mar 1988 | A |
| 4731058 | Doan | Mar 1988 | A |
| 4732411 | Siegel | Mar 1988 | A |
| 4741732 | Crankshaw et al. | May 1988 | A |
| 4741736 | Brown | May 1988 | A |
| 4756706 | Kerns et al. | Jul 1988 | A |
| 4759756 | Forman | Jul 1988 | A |
| 4778449 | Weber et al. | Oct 1988 | A |
| 4779626 | Peel et al. | Oct 1988 | A |
| 4784645 | Fischell | Nov 1988 | A |
| 4785799 | Schoon et al. | Nov 1988 | A |
| 4785969 | McLaughlin | Nov 1988 | A |
| 4796644 | Polaschegg | Jan 1989 | A |
| 4797840 | Fraden | Jan 1989 | A |
| 4803625 | Fu et al. | Feb 1989 | A |
| 4810090 | Boucher | Mar 1989 | A |
| 4810243 | Howson | Mar 1989 | A |
| 4811844 | Moulding, Jr. et al. | Mar 1989 | A |
| 4816208 | Woods et al. | Mar 1989 | A |
| 4817044 | Ogren | Mar 1989 | A |
| 4828545 | Epstein et al. | May 1989 | A |
| 4829524 | Yoshida | May 1989 | A |
| 4830018 | Treach | May 1989 | A |
| 4831562 | McIntosh et al. | May 1989 | A |
| 4832033 | Maher et al. | May 1989 | A |
| 4835372 | Gombrich et al. | May 1989 | A |
| 4835521 | Andrejasich et al. | May 1989 | A |
| 4838275 | Lee | Jun 1989 | A |
| 4839806 | Goldfischer et al. | Jun 1989 | A |
| 4845644 | Anthias et al. | Jul 1989 | A |
| 4847764 | Halvorson | Jul 1989 | A |
| 4850009 | Zook et al. | Jul 1989 | A |
| 4850972 | Schulman et al. | Jul 1989 | A |
| 4853521 | Claeys et al. | Aug 1989 | A |
| 4854324 | Hirschman et al. | Aug 1989 | A |
| 4857713 | Brown | Aug 1989 | A |
| 4857716 | Gombrich et al. | Aug 1989 | A |
| 4865584 | Epstein et al. | Sep 1989 | A |
| 4871351 | Feingold | Oct 1989 | A |
| 4878175 | Norden-Paul et al. | Oct 1989 | A |
| 4889132 | Hutcheson et al. | Dec 1989 | A |
| 4889134 | Greenwold et al. | Dec 1989 | A |
| 4893270 | Beck et al. | Jan 1990 | A |
| 4897777 | Janke et al. | Jan 1990 | A |
| 4898209 | Zbed | Feb 1990 | A |
| 4898576 | Philip | Feb 1990 | A |
| 4898578 | Rubalcaba, Jr. | Feb 1990 | A |
| 4901728 | Hutchison | Feb 1990 | A |
| 4908017 | Howson et al. | Mar 1990 | A |
| 4912623 | Rantala et al. | Mar 1990 | A |
| 4916441 | Gombrich et al. | Apr 1990 | A |
| 4922922 | Pollock et al. | May 1990 | A |
| 4925444 | Orkin et al. | May 1990 | A |
| 4933843 | Scheller et al. | Jun 1990 | A |
| 4937777 | Flood et al. | Jun 1990 | A |
| 4941808 | Qureshi et al. | Jul 1990 | A |
| 4943279 | Samiotes et al. | Jul 1990 | A |
| 4946445 | Lynn | Aug 1990 | A |
| 4949274 | Hollander et al. | Aug 1990 | A |
| 4952928 | Carroll et al. | Aug 1990 | A |
| 4953074 | Kametani et al. | Aug 1990 | A |
| 4960230 | Marelli | Oct 1990 | A |
| 4966579 | Polaschegg | Oct 1990 | A |
| 4967928 | Carter | Nov 1990 | A |
| 4968295 | Neumann | Nov 1990 | A |
| 4977590 | Milovancevic | Dec 1990 | A |
| 4978335 | Arthur, III | Dec 1990 | A |
| 4991091 | Allen | Feb 1991 | A |
| 4992926 | Janke et al. | Feb 1991 | A |
| 4993068 | Piosenka et al. | Feb 1991 | A |
| 4993506 | Angel | Feb 1991 | A |
| 4998249 | Bennett et al. | Mar 1991 | A |
| 5002055 | Merki et al. | Mar 1991 | A |
| 5003296 | Lee | Mar 1991 | A |
| 5006699 | Felkner et al. | Apr 1991 | A |
| 5007429 | Treatch et al. | Apr 1991 | A |
| 5012402 | Akiyama | Apr 1991 | A |
| 5012411 | Policastro et al. | Apr 1991 | A |
| 5014875 | McLaughlin et al. | May 1991 | A |
| 5016172 | Dessertine | May 1991 | A |
| 5023770 | Siverling | Jun 1991 | A |
| 5025374 | Roizen et al. | Jun 1991 | A |
| 5036852 | Leishman | Aug 1991 | A |
| 5038800 | Oba | Aug 1991 | A |
| 5041086 | Koenig et al. | Aug 1991 | A |
| 5045048 | Kaleskas et al. | Sep 1991 | A |
| 5047959 | Phillips et al. | Sep 1991 | A |
| 5053031 | Borsanyi | Oct 1991 | A |
| 5053990 | Kreifels et al. | Oct 1991 | A |
| 5055001 | Natwick et al. | Oct 1991 | A |
| 5057076 | Polaschegg | Oct 1991 | A |
| 5061243 | Winchell et al. | Oct 1991 | A |
| 5072356 | Watt et al. | Dec 1991 | A |
| 5072383 | Brimm et al. | Dec 1991 | A |
| 5072412 | Henderson, Jr. et al. | Dec 1991 | A |
| 5078683 | Sancoff et al. | Jan 1992 | A |
| 5084828 | Kaufman et al. | Jan 1992 | A |
| 5087245 | Doan | Feb 1992 | A |
| 5088904 | Okada | Feb 1992 | A |
| 5088981 | Howson et al. | Feb 1992 | A |
| 5088990 | Hivale et al. | Feb 1992 | A |
| 5096385 | Georgi et al. | Mar 1992 | A |
| 5098377 | Borsanyi et al. | Mar 1992 | A |
| 5100380 | Epstein et al. | Mar 1992 | A |
| 5100394 | Dudar et al. | Mar 1992 | A |
| 5104374 | Bishko et al. | Apr 1992 | A |
| 5108363 | Tuttle et al. | Apr 1992 | A |
| 5108367 | Epstein et al. | Apr 1992 | A |
| 5108372 | Swenson | Apr 1992 | A |
| 5109487 | Ohgomori et al. | Apr 1992 | A |
| 5109849 | Goodman et al. | May 1992 | A |
| 5112319 | Lai | May 1992 | A |
| 5116203 | Natwick et al. | May 1992 | A |
| 5116312 | Blankenship et al. | May 1992 | A |
| 5131092 | Sackmann et al. | Jul 1992 | A |
| 5134574 | Beaverstock et al. | Jul 1992 | A |
| 5135500 | Zdeb | Aug 1992 | A |
| 5137023 | Mendelson et al. | Aug 1992 | A |
| 5151978 | Bronikowski et al. | Sep 1992 | A |
| 5152296 | Simons | Oct 1992 | A |
| 5153416 | Neeley | Oct 1992 | A |
| 5153827 | Coutre et al. | Oct 1992 | A |
| 5155693 | Altmayer et al. | Oct 1992 | A |
| 5157595 | Lovrenich | Oct 1992 | A |
| 5158091 | Butterfield et al. | Oct 1992 | A |
| 5159673 | Sackmann et al. | Oct 1992 | A |
| 5160320 | Yum et al. | Nov 1992 | A |
| 5161211 | Taguchi et al. | Nov 1992 | A |
| 5167235 | Seacord et al. | Dec 1992 | A |
| 5169642 | Brinker et al. | Dec 1992 | A |
| 5172698 | Stanko | Dec 1992 | A |
| 5176004 | Gaudet | Jan 1993 | A |
| 5179569 | Sawyer | Jan 1993 | A |
| 5179700 | Aihara et al. | Jan 1993 | A |
| 5181910 | Scanlon | Jan 1993 | A |
| 5190185 | Blechl | Mar 1993 | A |
| 5190522 | Wojcicki et al. | Mar 1993 | A |
| 5191891 | Righter | Mar 1993 | A |
| 5208762 | Charhut et al. | May 1993 | A |
| 5208907 | Shelton et al. | May 1993 | A |
| 5211849 | Kitaevich et al. | May 1993 | A |
| 5213099 | Tripp, Jr. | May 1993 | A |
| 5213232 | Kraft et al. | May 1993 | A |
| 5213568 | Lattin et al. | May 1993 | A |
| 5219330 | Bollish et al. | Jun 1993 | A |
| 5219331 | Vanderveen | Jun 1993 | A |
| 5225974 | Mathews et al. | Jul 1993 | A |
| 5226425 | Righter | Jul 1993 | A |
| 5228450 | Sellers | Jul 1993 | A |
| 5231990 | Gauglitz | Aug 1993 | A |
| 5234404 | Tuttle et al. | Aug 1993 | A |
| 5235510 | Yamada et al. | Aug 1993 | A |
| 5236416 | McDaniel et al. | Aug 1993 | A |
| 5238001 | Gallant et al. | Aug 1993 | A |
| 5240007 | Pytel et al. | Aug 1993 | A |
| 5244463 | Cordner, Jr. et al. | Sep 1993 | A |
| 5245704 | Weber et al. | Sep 1993 | A |
| 5254096 | Rondelet et al. | Oct 1993 | A |
| 5256156 | Kern et al. | Oct 1993 | A |
| 5256157 | Samiotes et al. | Oct 1993 | A |
| 5265010 | Evans-Paganelli et al. | Nov 1993 | A |
| 5265431 | Gaudet et al. | Nov 1993 | A |
| 5267174 | Kaufman et al. | Nov 1993 | A |
| 5271405 | Boyer et al. | Dec 1993 | A |
| 5272318 | Gorman | Dec 1993 | A |
| 5272321 | Otsuka et al. | Dec 1993 | A |
| 5273517 | Barone et al. | Dec 1993 | A |
| 5277188 | Selker | Jan 1994 | A |
| 5283861 | Dangler et al. | Feb 1994 | A |
| 5284150 | Butterfield et al. | Feb 1994 | A |
| 5286252 | Tuttle et al. | Feb 1994 | A |
| 5292029 | Pearson | Mar 1994 | A |
| 5297257 | Struger et al. | Mar 1994 | A |
| 5298021 | Sherer | Mar 1994 | A |
| 5304126 | Epstein et al. | Apr 1994 | A |
| 5307263 | Brown | Apr 1994 | A |
| 5307372 | Sawyer et al. | Apr 1994 | A |
| 5307463 | Hyatt et al. | Apr 1994 | A |
| 5311908 | Barone et al. | May 1994 | A |
| 5314243 | McDonald et al. | May 1994 | A |
| 5315505 | Pratt et al. | May 1994 | A |
| 5317506 | Coutre et al. | May 1994 | A |
| 5319363 | Welch et al. | Jun 1994 | A |
| 5319543 | Wilhelm | Jun 1994 | A |
| 5321618 | Gessman | Jun 1994 | A |
| 5321829 | Zifferer | Jun 1994 | A |
| 5325478 | Shelton et al. | Jun 1994 | A |
| 5327341 | Whalen et al. | Jul 1994 | A |
| 5331549 | Crawford, Jr. | Jul 1994 | A |
| 5336245 | Adams et al. | Aug 1994 | A |
| 5337230 | Baumgartner et al. | Aug 1994 | A |
| 5337919 | Spaulding et al. | Aug 1994 | A |
| 5338157 | Blomquist | Aug 1994 | A |
| 5339421 | Housel, III | Aug 1994 | A |
| 5339821 | Fujimoto | Aug 1994 | A |
| 5341291 | Roizen et al. | Aug 1994 | A |
| 5341412 | Ramot et al. | Aug 1994 | A |
| 5348008 | Bornn et al. | Sep 1994 | A |
| 5348539 | Herskowitz | Sep 1994 | A |
| 5349675 | Fitzgerald et al. | Sep 1994 | A |
| 5356378 | Doan | Oct 1994 | A |
| 5361202 | Doue | Nov 1994 | A |
| 5361758 | Hall et al. | Nov 1994 | A |
| 5366896 | Margrey et al. | Nov 1994 | A |
| 5366904 | Qureshi et al. | Nov 1994 | A |
| 5367555 | Isoyama | Nov 1994 | A |
| 5368562 | Blomquist et al. | Nov 1994 | A |
| 5370612 | Maeda et al. | Dec 1994 | A |
| 5371687 | Holmes, II et al. | Dec 1994 | A |
| 5374251 | Smith | Dec 1994 | A |
| 5374813 | Shipp | Dec 1994 | A |
| 5374965 | Kanno | Dec 1994 | A |
| 5375604 | Kelly et al. | Dec 1994 | A |
| 5376070 | Purvis et al. | Dec 1994 | A |
| 5377864 | Blechl et al. | Jan 1995 | A |
| 5378231 | Johnson et al. | Jan 1995 | A |
| 5379214 | Arbuckle et al. | Jan 1995 | A |
| 5389078 | Zalesky et al. | Feb 1995 | A |
| 5390238 | Kirk et al. | Feb 1995 | A |
| 5392951 | Gardner et al. | Feb 1995 | A |
| 5395320 | Padda et al. | Mar 1995 | A |
| 5395321 | Kawahara et al. | Mar 1995 | A |
| 5398336 | Tantry et al. | Mar 1995 | A |
| 5401059 | Ferrario | Mar 1995 | A |
| 5404292 | Hendrickson | Apr 1995 | A |
| 5404384 | Colburn et al. | Apr 1995 | A |
| 5406473 | Yoshikura et al. | Apr 1995 | A |
| 5412715 | Volpe | May 1995 | A |
| 5415167 | Wilk | May 1995 | A |
| 5416695 | Stutman et al. | May 1995 | A |
| 5417222 | Dempsey et al. | May 1995 | A |
| 5420977 | Sztipanovits et al. | May 1995 | A |
| 5421343 | Feng | Jun 1995 | A |
| 5423746 | Burkett et al. | Jun 1995 | A |
| 5429602 | Hauser | Jul 1995 | A |
| 5431201 | Torchia et al. | Jul 1995 | A |
| 5431299 | Brewer et al. | Jul 1995 | A |
| 5431627 | Pastrone et al. | Jul 1995 | A |
| 5433736 | Nilsson | Jul 1995 | A |
| 5438607 | Przygoda, Jr. et al. | Aug 1995 | A |
| 5440699 | Farrand et al. | Aug 1995 | A |
| 5441047 | David et al. | Aug 1995 | A |
| 5445294 | Gardner et al. | Aug 1995 | A |
| 5445621 | Poli et al. | Aug 1995 | A |
| 5446868 | Gardea, II et al. | Aug 1995 | A |
| 5453098 | Botts et al. | Sep 1995 | A |
| 5455851 | Chaco et al. | Oct 1995 | A |
| 5458123 | Unger | Oct 1995 | A |
| 5460294 | Williams | Oct 1995 | A |
| 5460605 | Tuttle et al. | Oct 1995 | A |
| 5461665 | Shur et al. | Oct 1995 | A |
| 5462051 | Oka et al. | Oct 1995 | A |
| 5464392 | Epstein et al. | Nov 1995 | A |
| 5465286 | Clare et al. | Nov 1995 | A |
| 5467773 | Bergelson et al. | Nov 1995 | A |
| 5468110 | McDonald et al. | Nov 1995 | A |
| 5469855 | Pompei et al. | Nov 1995 | A |
| 5471382 | Tallman et al. | Nov 1995 | A |
| 5474552 | Palti | Dec 1995 | A |
| 5482043 | Zulauf | Jan 1996 | A |
| 5482446 | Williamson | Jan 1996 | A |
| 5485408 | Blomquist | Jan 1996 | A |
| 5490610 | Pearson | Feb 1996 | A |
| 5494592 | Latham, Jr. et al. | Feb 1996 | A |
| 5496265 | Langley et al. | Mar 1996 | A |
| 5496273 | Pastrone et al. | Mar 1996 | A |
| 5502944 | Kraft et al. | Apr 1996 | A |
| 5507412 | Ebert et al. | Apr 1996 | A |
| 5508912 | Schneiderman | Apr 1996 | A |
| 5509318 | Gomes | Apr 1996 | A |
| 5509422 | Fukami | Apr 1996 | A |
| 5513957 | O'Leary | May 1996 | A |
| 5514088 | Zakko | May 1996 | A |
| 5514095 | Brightbill et al. | May 1996 | A |
| 5515426 | Yacenda et al. | May 1996 | A |
| 5520450 | Colson, Jr. et al. | May 1996 | A |
| 5520637 | Pager et al. | May 1996 | A |
| 5522396 | Langer et al. | Jun 1996 | A |
| 5522798 | Johnson et al. | Jun 1996 | A |
| 5526428 | Arnold | Jun 1996 | A |
| 5528503 | Moore et al. | Jun 1996 | A |
| 5529063 | Hill | Jun 1996 | A |
| 5531680 | Dumas et al. | Jul 1996 | A |
| 5531697 | Olsen et al. | Jul 1996 | A |
| 5531698 | Olsen | Jul 1996 | A |
| 5533079 | Colburn et al. | Jul 1996 | A |
| 5533981 | Mandro et al. | Jul 1996 | A |
| 5534691 | Holdaway et al. | Jul 1996 | A |
| 5536084 | Curtis et al. | Jul 1996 | A |
| 5537313 | Pirelli | Jul 1996 | A |
| 5537853 | Finburgh et al. | Jul 1996 | A |
| 5542420 | Goldman et al. | Aug 1996 | A |
| 5544649 | David et al. | Aug 1996 | A |
| 5544651 | Wilk | Aug 1996 | A |
| 5544661 | Davis et al. | Aug 1996 | A |
| 5545140 | Conero et al. | Aug 1996 | A |
| 5546580 | Seliger et al. | Aug 1996 | A |
| 5547470 | Johnson et al. | Aug 1996 | A |
| 5549117 | Tacklind et al. | Aug 1996 | A |
| 5549460 | O'Leary | Aug 1996 | A |
| 5553609 | Chen et al. | Sep 1996 | A |
| 5558638 | Evers et al. | Sep 1996 | A |
| 5558640 | Pfeiler et al. | Sep 1996 | A |
| 5560352 | Heim et al. | Oct 1996 | A |
| 5562232 | Pearson | Oct 1996 | A |
| 5562621 | Claude et al. | Oct 1996 | A |
| 5563347 | Martin et al. | Oct 1996 | A |
| 5564803 | McDonald et al. | Oct 1996 | A |
| 5568912 | Minami et al. | Oct 1996 | A |
| 5569186 | Lord et al. | Oct 1996 | A |
| 5569187 | Kaiser | Oct 1996 | A |
| 5571258 | Pearson | Nov 1996 | A |
| 5573502 | LeCocq et al. | Nov 1996 | A |
| 5573506 | Vasko | Nov 1996 | A |
| 5575632 | Morris et al. | Nov 1996 | A |
| 5576952 | Stutman et al. | Nov 1996 | A |
| 5579001 | Dempsey et al. | Nov 1996 | A |
| 5579378 | Arlinghaus, Jr. | Nov 1996 | A |
| 5581369 | Righter et al. | Dec 1996 | A |
| 5581687 | Lyle et al. | Dec 1996 | A |
| 5582593 | Hultman | Dec 1996 | A |
| 5583758 | Mcilroy et al. | Dec 1996 | A |
| 5588815 | Zaleski, II | Dec 1996 | A |
| 5589932 | Garcia-Rubio et al. | Dec 1996 | A |
| 5590648 | Mitchell et al. | Jan 1997 | A |
| 5593267 | McDonald et al. | Jan 1997 | A |
| 5594637 | Eisenberg et al. | Jan 1997 | A |
| 5594786 | Chaco et al. | Jan 1997 | A |
| 5597995 | Williams et al. | Jan 1997 | A |
| 5598536 | Slaughter, III et al. | Jan 1997 | A |
| 5601445 | Schipper et al. | Feb 1997 | A |
| 5609575 | Larson et al. | Mar 1997 | A |
| 5609576 | Voss et al. | Mar 1997 | A |
| 5613115 | Gihl et al. | Mar 1997 | A |
| 5619428 | Lee et al. | Apr 1997 | A |
| 5619991 | Sloane | Apr 1997 | A |
| 5623652 | Vora et al. | Apr 1997 | A |
| 5623925 | Swenson et al. | Apr 1997 | A |
| 5626144 | Tacklind et al. | May 1997 | A |
| 5628619 | Wilson | May 1997 | A |
| 5630710 | Tune et al. | May 1997 | A |
| 5631844 | Margrey et al. | May 1997 | A |
| 5633910 | Cohen | May 1997 | A |
| D380260 | Hyman | Jun 1997 | S |
| 5634893 | Rishton | Jun 1997 | A |
| 5637082 | Pages et al. | Jun 1997 | A |
| 5637093 | Hyman et al. | Jun 1997 | A |
| 5640301 | Roecher et al. | Jun 1997 | A |
| 5640953 | Bishop et al. | Jun 1997 | A |
| 5641628 | Bianchi | Jun 1997 | A |
| 5643193 | Papillon et al. | Jul 1997 | A |
| 5643212 | Coutre et al. | Jul 1997 | A |
| 5647853 | Feldmann et al. | Jul 1997 | A |
| 5647854 | Olsen et al. | Jul 1997 | A |
| 5651775 | Walker et al. | Jul 1997 | A |
| 5652566 | Lambert | Jul 1997 | A |
| 5658240 | Urdahl et al. | Aug 1997 | A |
| 5658250 | Blomquist et al. | Aug 1997 | A |
| 5661978 | Holmes et al. | Sep 1997 | A |
| 5664270 | Bell et al. | Sep 1997 | A |
| 5666404 | Ciccotelli et al. | Sep 1997 | A |
| D385646 | Chan | Oct 1997 | S |
| 5678562 | Sellers | Oct 1997 | A |
| 5678568 | Uchikubo et al. | Oct 1997 | A |
| 5681285 | Ford et al. | Oct 1997 | A |
| 5682526 | Smokoff et al. | Oct 1997 | A |
| 5683367 | Jordan et al. | Nov 1997 | A |
| 5685844 | Marttila | Nov 1997 | A |
| 5687717 | Halpern | Nov 1997 | A |
| 5687734 | Dempsey et al. | Nov 1997 | A |
| 5695473 | Olsen | Dec 1997 | A |
| 5697951 | Harpstead | Dec 1997 | A |
| 5700998 | Palti | Dec 1997 | A |
| 5701894 | Cherry et al. | Dec 1997 | A |
| 5704351 | Mortara et al. | Jan 1998 | A |
| 5704364 | Saltzstein et al. | Jan 1998 | A |
| 5704366 | Tacklind et al. | Jan 1998 | A |
| 5712798 | Langley et al. | Jan 1998 | A |
| 5712912 | Tomko et al. | Jan 1998 | A |
| 5713485 | Liff et al. | Feb 1998 | A |
| 5713856 | Eggers et al. | Feb 1998 | A |
| 5715823 | Wood et al. | Feb 1998 | A |
| 5716114 | Holmes et al. | Feb 1998 | A |
| 5716194 | Butterfield et al. | Feb 1998 | A |
| 5718562 | Lawless et al. | Feb 1998 | A |
| 5719761 | Gatti et al. | Feb 1998 | A |
| RE35743 | Pearson | Mar 1998 | E |
| 5724025 | Tavori | Mar 1998 | A |
| 5724580 | Levin et al. | Mar 1998 | A |
| 5732709 | Tacklind et al. | Mar 1998 | A |
| 5733259 | Valcke et al. | Mar 1998 | A |
| 5735887 | Barreras, Sr. et al. | Apr 1998 | A |
| 5737539 | Edelson et al. | Apr 1998 | A |
| 5740185 | Bosse | Apr 1998 | A |
| 5740800 | Hendrickson et al. | Apr 1998 | A |
| 5745366 | Higham et al. | Apr 1998 | A |
| 5745378 | Barker et al. | Apr 1998 | A |
| 5752917 | Fuchs | May 1998 | A |
| 5752976 | Duffin et al. | May 1998 | A |
| 5755563 | Clegg et al. | May 1998 | A |
| 5758095 | Albaum et al. | May 1998 | A |
| 5764923 | Tallman et al. | Jun 1998 | A |
| 5766155 | Hyman et al. | Jun 1998 | A |
| 5769811 | Stacey et al. | Jun 1998 | A |
| 5771657 | Lasher et al. | Jun 1998 | A |
| 5772585 | Lavin et al. | Jun 1998 | A |
| 5772586 | Heinonen et al. | Jun 1998 | A |
| 5772635 | Dastur et al. | Jun 1998 | A |
| 5772637 | Heinzmann et al. | Jun 1998 | A |
| 5776057 | Swenson et al. | Jul 1998 | A |
| 5778345 | McCartney | Jul 1998 | A |
| 5778882 | Raymond et al. | Jul 1998 | A |
| 5781442 | Engleson et al. | Jul 1998 | A |
| 5782805 | Meinzer et al. | Jul 1998 | A |
| 5782878 | Morgan et al. | Jul 1998 | A |
| 5785650 | Akasaka et al. | Jul 1998 | A |
| 5788669 | Peterson | Aug 1998 | A |
| 5790409 | Fedor et al. | Aug 1998 | A |
| 5791342 | Woodard | Aug 1998 | A |
| 5791880 | Wilson | Aug 1998 | A |
| 5793861 | Haigh | Aug 1998 | A |
| 5793969 | Kamentsky et al. | Aug 1998 | A |
| 5795317 | Brierton et al. | Aug 1998 | A |
| 5795327 | Wilson et al. | Aug 1998 | A |
| 5797515 | Liff et al. | Aug 1998 | A |
| 5800387 | Duffy et al. | Sep 1998 | A |
| 5801755 | Echerer | Sep 1998 | A |
| 5803906 | Pratt et al. | Sep 1998 | A |
| 5805442 | Crater et al. | Sep 1998 | A |
| 5805454 | Valerino et al. | Sep 1998 | A |
| 5805456 | Higham et al. | Sep 1998 | A |
| 5805505 | Zheng et al. | Sep 1998 | A |
| 5807321 | Stoker et al. | Sep 1998 | A |
| 5807322 | Lindsey et al. | Sep 1998 | A |
| 5807336 | Russo et al. | Sep 1998 | A |
| 5810747 | Brudny et al. | Sep 1998 | A |
| 5812410 | Lion et al. | Sep 1998 | A |
| 5814015 | Gargano et al. | Sep 1998 | A |
| 5815566 | Ramot et al. | Sep 1998 | A |
| 5818528 | Roth et al. | Oct 1998 | A |
| 5822418 | Yacenda et al. | Oct 1998 | A |
| 5822544 | Chaco et al. | Oct 1998 | A |
| 5823949 | Goltra | Oct 1998 | A |
| 5826237 | Macrae et al. | Oct 1998 | A |
| 5829438 | Gibbs et al. | Nov 1998 | A |
| 5832447 | Rieker et al. | Nov 1998 | A |
| 5832448 | Brown | Nov 1998 | A |
| 5832450 | Myers et al. | Nov 1998 | A |
| 5833599 | Schrier et al. | Nov 1998 | A |
| 5841975 | Layne et al. | Nov 1998 | A |
| 5842841 | Danby et al. | Dec 1998 | A |
| 5842976 | Williamson | Dec 1998 | A |
| 5845253 | Rensimer et al. | Dec 1998 | A |
| 5848593 | McGrady et al. | Dec 1998 | A |
| 5851186 | Wood et al. | Dec 1998 | A |
| 5852590 | De La Huerga | Dec 1998 | A |
| 5853387 | Clegg et al. | Dec 1998 | A |
| 5855550 | Lai et al. | Jan 1999 | A |
| 5857967 | Frid et al. | Jan 1999 | A |
| 5859972 | Subramaniam et al. | Jan 1999 | A |
| 5865745 | Schmitt et al. | Feb 1999 | A |
| 5865786 | Sibalis et al. | Feb 1999 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5871465 | Vasko | Feb 1999 | A |
| 5876926 | Beecham | Mar 1999 | A |
| 5880443 | McDonald et al. | Mar 1999 | A |
| 5882338 | Gray | Mar 1999 | A |
| 5883370 | Walker et al. | Mar 1999 | A |
| 5883576 | De La Huerga | Mar 1999 | A |
| 5884273 | Sattizahn et al. | Mar 1999 | A |
| 5884457 | Ortiz et al. | Mar 1999 | A |
| 5885245 | Lynch et al. | Mar 1999 | A |
| 5891035 | Wood et al. | Apr 1999 | A |
| 5891734 | Gill et al. | Apr 1999 | A |
| 5893697 | Zimi et al. | Apr 1999 | A |
| 5894273 | Meador et al. | Apr 1999 | A |
| 5895371 | Levitas et al. | Apr 1999 | A |
| 5897493 | Brown | Apr 1999 | A |
| 5897530 | Jackson | Apr 1999 | A |
| 5897989 | Beecham | Apr 1999 | A |
| 5899665 | Makino et al. | May 1999 | A |
| 5899855 | Brown | May 1999 | A |
| 5901150 | Jhuboo et al. | May 1999 | A |
| 5904668 | Hyman et al. | May 1999 | A |
| 5905653 | Higham et al. | May 1999 | A |
| 5907291 | Chen et al. | May 1999 | A |
| 5907493 | Boyer et al. | May 1999 | A |
| 5908027 | Butterfield et al. | Jun 1999 | A |
| 5910107 | Iliff | Jun 1999 | A |
| 5910252 | Truitt et al. | Jun 1999 | A |
| 5911132 | Sloane | Jun 1999 | A |
| 5911687 | Sato et al. | Jun 1999 | A |
| 5912818 | McGrady et al. | Jun 1999 | A |
| 5913197 | Kameda | Jun 1999 | A |
| 5913310 | Brown | Jun 1999 | A |
| 5915089 | Stevens et al. | Jun 1999 | A |
| 5915240 | Karpf | Jun 1999 | A |
| 5919154 | Toavs et al. | Jul 1999 | A |
| 5921938 | Aoyama et al. | Jul 1999 | A |
| 5923018 | Kameda et al. | Jul 1999 | A |
| 5924074 | Evans | Jul 1999 | A |
| 5924103 | Ahmed et al. | Jul 1999 | A |
| 5927540 | Godlewski | Jul 1999 | A |
| 5931791 | Saltzstein et al. | Aug 1999 | A |
| 5935060 | Iliff | Aug 1999 | A |
| 5935099 | Peterson et al. | Aug 1999 | A |
| 5935106 | Olsen | Aug 1999 | A |
| 5938413 | Makino et al. | Aug 1999 | A |
| 5939326 | Chupp et al. | Aug 1999 | A |
| 5939699 | Perttunen et al. | Aug 1999 | A |
| 5940306 | Gardner et al. | Aug 1999 | A |
| 5940802 | Hildebrand et al. | Aug 1999 | A |
| 5941829 | Saltzstein et al. | Aug 1999 | A |
| 5942986 | Shabot et al. | Aug 1999 | A |
| 5943423 | Muftic | Aug 1999 | A |
| 5943633 | Wilson et al. | Aug 1999 | A |
| 5944659 | Flach et al. | Aug 1999 | A |
| 6068156 | Liff et al. | May 2000 | A |
| 6283322 | Liff et al. | Sep 2001 | B1 |
| 6330491 | Lion | Dec 2001 | B1 |
| 6438451 | Lion | Aug 2002 | B1 |
| 6471089 | Liff et al. | Oct 2002 | B2 |
| 6564121 | Wallace et al. | May 2003 | B1 |
| 6581798 | Liff et al. | Jun 2003 | B2 |
| 6711460 | Reese | Mar 2004 | B1 |
| 6735497 | Wallace et al. | May 2004 | B2 |
| 6776304 | Liff et al. | Aug 2004 | B2 |
| 6814255 | Liff et al. | Nov 2004 | B2 |
| 7006893 | Hart et al. | Feb 2006 | B2 |
| 7151982 | Liff et al. | Dec 2006 | B2 |
| 7427002 | Liff et al. | Sep 2008 | B2 |
| 7831448 | Goodall et al. | Nov 2010 | B1 |
| 7941325 | Heald et al. | May 2011 | B2 |
| 7991507 | Liff et al. | Aug 2011 | B2 |
| 8280549 | Liff et al. | Oct 2012 | B2 |
| 8374887 | Alexander | Feb 2013 | B1 |
| 20020100762 | Liff et al. | Aug 2002 | A1 |
| 20030050731 | Rosenblum | Mar 2003 | A1 |
| 20040019794 | Moradi et al. | Jan 2004 | A1 |
| 20040172289 | Kozic et al. | Sep 2004 | A1 |
| 20040204954 | Lacko | Oct 2004 | A1 |
| 20050080651 | Morrison et al. | Apr 2005 | A1 |
| 20050177392 | Domashnev | Aug 2005 | A1 |
| 20060265245 | McCallie et al. | Nov 2006 | A1 |
| 20070088590 | Berkelhamer et al. | Apr 2007 | A1 |
| 20070088594 | Goodall et al. | Apr 2007 | A1 |
| 20070250341 | Howe et al. | Oct 2007 | A1 |
| 20080195416 | Tribble | Aug 2008 | A1 |
| 20100012546 | Togashi et al. | Jan 2010 | A1 |
| 20100057489 | Howe | Mar 2010 | A1 |
| 20100094653 | Tribble et al. | Apr 2010 | A1 |
| 20100125461 | Heald et al. | May 2010 | A1 |
| 20110267465 | Alexander et al. | Nov 2011 | A1 |
| 20130173277 | Eller | Jul 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003022322 | Jan 2003 | JP |
| 2003022322 | Jan 2003 | JP |
| 2004078970 | Mar 2004 | JP |
| 2004078970 | Mar 2004 | JP |
| 2004232557 | Aug 2004 | JP |
| 2005269257 | Sep 2005 | JP |
| 2010533927 | Oct 2010 | JP |
| 2009012371 | Jan 2009 | WO |
| Entry |
|---|
| Texas Administrative Code, Title 22, Part 15, Ch 291, Rules 20, 36, and 71-74. Feb. 10, 2004. |
| Peterson, Charles D. and Anderson, Jr., Howard C.; “The North Dakota Telepharmacy Project: Restoring and Retaining Pharmacy Services in Rural Communities” Feb. 1, 2004. |
| Cato Reference Manual, Support for Trial Version (Abridged), Vienna, May 2004 Jun. 1, 2004. |
| Seifert et al.; “The Training of a Telepharmacist: Addressing the Needs of Rural West Texas,” American Journal of Pharmaceutical Education 2004; 68 (3) Article 60. Jul. 16, 2004. |
| Cato Reference Manual, Vienna, May 2005 May 1, 2005. |
| Phillips, Jon, Associate Director of Telemedicine; “Telepharmacy at Texas Tech,” presented Apr. 30, 2003, published at http://www.ttuhsc.edu/telemedicine/publication.htm at least by Jun. 22, 2003 Jun. 22, 2003. |
| International Search Report pertaining to International Application No. PCT/US2013/031707. |
| International Preliminary Report on Patentability to International Application No. PCT/US2013/031707. |
| English translation of KIPO's Notice of Final Rejection issued in related Korean Patent Application No. 10-2015-7007596. |
| Korean Office Action for Korean counterpart Application No. 10-2017-7036887; action dated Jan. 31, 2018; (12 pages). |
| Canadian Office Action for related Canadian Application No. 2,883,273; action dated Mar. 6, 2018; (8 pages). |
| Japanese Office Action for related Japanese Application No. 2017-106958; action dated Apr. 10, 2018; (3 pages). |
| Korean Office Action for related Korean Application No. 10-2017-7036887; action dated Jul. 31, 2018; (3 pages). |
| Korean Office Action and English translation for related Korean Application No. 10-2017-7036887; action dated Oct. 10, 2018; (7 pages). |
| Australian Examination Report for related Australian Application No. 2013309509; action dated Dec. 4, 2018; (6 pages). |
| Augstralian Office Action for related Australian Application No. 2013309509; action dated Feb. 19, 2019; (6 pages). |
| New Zealand Examination Report for related New Zealand Application No. 739406; report dated May 3, 2019; (4 pages). |
| KIPO's Second Notice of Final Rejection dated Nov. 21, 2017 in related Korean Patent Application No. 10-2015-7007596. |
| Canadian Office Action for related Canadian Application No. 2,883,273; action dated Jan. 21, 2019; (7 pages). |
| Korean Preliminary Rejection for related Korean Application No. 10-2018-7032745; action dated Dec. 17, 2018; (13 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20150235003 A1 | Aug 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61695831 | Aug 2012 | US |
