Drug library dynamic version management

Abstract

A drug library management system generates versions of drug library data that can be used by infusion pumps, and version of drug library data that can be used by systems or components in a clinical environment other than infusion pumps. One version of the drug library data may be customized for a particular infusion pump, while another version may be a generalized version that can be used by middleware systems that process messages received from various infusion pumps that are using a different version of the drug library data. The generalized version may be archived separately from a drug library database used by the drug library management system to generate the various versions.

1 - 20 . (canceled) 
     
     
         21 . A computer-implemented method comprising:
 under control of one or more computing devices configured with specific computer-executable instructions,
 storing, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
 a first reference to infusion pump data in the drug library database representing a first infusion pump type of a plurality of infusion pump types; and 
 a second reference to clinical care area data in the drug library database representing a first clinical care area of a plurality of clinical care areas; 
 
 generating customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules are associated with individual medications; 
 generating generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules, and wherein the generalized drug library data is different from the customized drug library data; 
 providing the customized drug library data to an infusion pump associated with the first infusion pump type; and 
 providing the generalized drug library data to a computing system in communication with the infusion pump. 
   
     
     
         22 . The computer-implemented method of  claim 21 , further comprising:
 receiving an infusion message from the infusion pump, wherein the infusion pump is configured to display infusion data comprising a medication name, and transmit the infusion message comprising a medication identifier and not comprising the medication name; and   determining the medication name using the medication identifier and the generalized drug library data.   
     
     
         23 . The computer-implemented method of  claim 22 , further comprising:
 receiving, from a second infusion pump, a second infusion message comprising a second medication identifier; and   determining a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump, wherein the second infusion pump is associated with a second infusion pump type of the plurality of infusion pump types.   
     
     
         24 . The computer-implemented method of  claim 21 , further comprising:
 receiving, from a user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and   storing, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.   
     
     
         25 . The computer-implemented method of  claim 21 , further comprising:
 storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and   receiving, from a user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.   
     
     
         26 . The computer-implemented method of  claim 21 , further comprising providing the generalized drug library data to a drug library archive, wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries. 
     
     
         27 . The computer-implemented method of  claim 21 , further comprising:
 accessing archived generalized drug library data corresponding to a prior version of the worksheet data;   comparing the generalized drug library data to the archived generalized drug library data; and   presenting a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.   
     
     
         28 . The computer-implemented method of  claim 21 , further comprising:
 receiving input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and   storing, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.   
     
     
         29 . The computer-implemented method of  claim 21 , further comprising:
 storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and   receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.   
     
     
         30 . The computer-implemented method of  claim 21 , wherein generating the generalized drug library data comprises formatting the generalized drug library data using JavaScript Object Notation. 
     
     
         31 . A system comprising:
 a computer-readable memory storing executable instructions; and   one or more processors in communication with the computer-readable memory and programmed by the executable instructions to:
 store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
 a first reference to infusion pump data in the drug library database representing a first infusion pump type of a plurality of infusion pump types; and 
 a second reference to clinical care area data in the drug library database representing a first clinical care area of a plurality of clinical care areas; 
 
 generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules are associated with individual medications; 
 generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules, and wherein the generalized drug library data is different from the customized drug library data; 
 provide the customized drug library data to an infusion pump associated with the first infusion pump type; and 
 provide the generalized drug library data to a computing system in communication with the infusion pump. 
   
     
     
         32 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 receive an infusion message from the infusion pump, wherein the infusion pump is configured to display infusion data comprising a medication name, and transmit the infusion message comprising a medication identifier and not comprising the medication name; and   determine the medication name using the medication identifier and the generalized drug library data.   
     
     
         33 . The system of  claim 32 , wherein the one or more processors are further programmed by the executable instructions to:
 receive, from a second infusion pump, a second infusion message comprising a second medication identifier; and   determine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump, wherein the second infusion pump is associated with a second infusion pump type of the plurality of infusion pump types.   
     
     
         34 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 receive, from a user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and   store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.   
     
     
         35 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and   receive, from a user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.   
     
     
         36 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to provide the generalized drug library data to a drug library archive, wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries. 
     
     
         37 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 access archived generalized drug library data corresponding to a prior version of the worksheet data;   compare the generalized drug library data to the archived generalized drug library data; and   present a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.   
     
     
         38 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 receive input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and   store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.   
     
     
         39 . The system of  claim 31 , wherein the one or more processors are further programmed by the executable instructions to:
 store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and   receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and the generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.   
     
     
         40 . The system of  claim 31 , wherein the generalized drug library data comprises JavaScript Object Notation data.