A processing method for hospital logistics information system based on unified drug coding

Abstract

The invention discloses a processing method for an in-hospital logistics information system based on unified drug coding, and relates to the technical field of in-hospital logistics information processing. The technical scheme thereof mainly includes: constructing a unified drug coding knowledge base and a drug supply enterprise code base, and automatically generating a storage entry form after scanning the invoice issued by the drug supply enterprise or the two-dimensional code printed on the accompanying document through the hospital intranet; generating a procurement plan two-dimensional code through the hospital intranet, and uploading it to the drug supply enterprise through external network scanning; establishing a multi-level drug warehouse for the hospital drug warehouse, various pharmacies, equipment in the pharmacy, spare emergency drugs at the nurse station, and an intravenous preparation center, and the inventory drug data table, drug detail data table, etc. of each drug warehouse and their data storage and reading mechanisms are the same, and the data table name is related to the drug warehouse ID and the drug ID; the storage and procurement plans between the drug warehouses are mutually the data sources; the doctor's order data is traced back through the doctor's order status; and the drug procurement plan / drug replenishment plan is formulated according to the use of the doctor's order drugs.

Description

Technical Field

[0001] The present invention relates to the technical field of logistics information processing, and more specifically, to a processing method of an in-hospital logistics information system based on unified drug coding. Background Art

[0002] Hospital logistics is abbreviated as SPD, which is the abbreviation of the English words supply, processing, and distribution. It includes procurement management (supply) for suppliers, warehouse management (processing) for the hospital's primary logistics warehouse, and consumption distribution and replenishment management (distribution) for consumption departments such as pharmacies, configuration centers, wards, clinics, and operating rooms in the hospital. SPD was first implemented in the management of high-value consumables in hospitals. The main means is to attach barcodes or QR codes on the packaging of high-value consumables, and scan the codes to confirm receipt at each receiving link. In the use link, the code is scanned again each time the patient uses it to confirm that it has been consumed; the usage, inventory and other information recorded in each link are fed back to the upstream supply company through the information system, and the upstream supply company then organizes the supply of goods to the hospital in a timely manner.

[0003] In recent years, due to the great success of SPD in the management of high-value consumables, it has been gradually applied to drug management, namely drug SPD. Since drugs are obviously different from high-value consumables, for example, about 40% of drugs now have no barcodes, especially low-value drugs are more common without barcodes, and the price of drugs varies greatly. The cost of labeling low-value drugs is not much different from the cost of the drugs themselves, which greatly raises the cost of SPD management; drugs go through multiple links from delivery to patient use, and the daily drug consumption is huge. It is impossible to scan barcodes every time they enter and exit the warehouse, and the acceptance and use links. Therefore, in the currently implemented drug SPD, third-party logistics management companies provide manpower support to carry out logistics business. The information system is basically consistent with the drug management module in the traditional HIS system. It relies on the HIS system data to be integrated through the interface, and some inventory upper and lower limit management modes are added to obtain inventory information to provide replenishment plans or procurement plans. In theory, the ownership of the inventory of ward spare medicines and emergency medicines should belong to the ward pharmacy, but in the current drug SPD management software and hospital HIS drug management, this part of the medicine is often managed without ownership in the account management, which is a major loophole in financial management, especially the anesthetic drugs reserved in the ward. The lack of management of this part will lead to huge safety risks for anesthetic drugs.

[0004] Therefore, the present invention aims to design and provide a processing method for an in-hospital logistics information system based on unified drug coding to solve the above-mentioned problems. Summary of the invention

[0005] The purpose of the present invention is to solve the above-mentioned problem and provide a processing method for an in-hospital logistics information system based on unified drug coding.

[0006] The above technical objectives of the present invention are achieved through the following technical solutions: A processing method of an in-hospital logistics information system based on unified drug coding comprises the following steps:

[0007] S1. Build a unified drug coding knowledge base and a unified drug supply enterprise code base. The drug coding knowledge base and drug supply enterprise code base are completely consistent within the hospital and the supply enterprise / supply chain, and are updated synchronously;

[0008] S2. The drug logistics in the hospital are all circulated between entities. The entity is defined as a warehouse or a person. Then, according to the cost of drug use, it is divided into a normal warehouse and a free warehouse. The free warehouse is used for donated drug management and GCP drug management. According to the conventional drug outbound direction, the drug outflow side is regarded as the upper warehouse, and the inflow side is regarded as the lower warehouse. According to the affiliation of the inventory drugs, the upper warehouse with affiliation is regarded as the parent warehouse, and the lower warehouse is regarded as the child warehouse. When there is drug circulation between entities, drug circulation and information circulation are carried out simultaneously.

[0009] S3. Warehouse management in the in-hospital logistics system database adopts modular design; data tables are designed according to functions and application scenarios. The data tables with the same functions or the same application scenarios have exactly the same structure, and use the same main table name as the prefix or suffix of the table names of different drug warehouses and / or different drug data tables; the same application is used for the same function or the same application scenario, with the same interface operation template, printing template, and the same data storage mechanism;

[0010] The same data tables involving the same type of drugs in the drug warehouses in the hospital and each drug warehouse should use the same main table name as a prefix or suffix, and add the drug warehouse ID and / or drug ID as a suffix or prefix in the data table name, and operate data tables with different names through system configuration files or parameter settings; the three-level management of narcotic drugs should be designed according to the warehouse management model;

[0011] S4. When a drug supplier supplies drugs to a hospital, it prints an invoice QR code on the invoice or the package accompanying the goods, and automatically generates a warehouse entry after scanning the QR code on the hospital intranet; the procurement plan formulated by the hospital generates a procurement plan QR code on the hospital intranet, and directly distributes the procurement plan to different drug suppliers after scanning the procurement plan QR code on the external network;

[0012] S5. The medical order management module in the hospital logistics system database is designed in a modular way, and is divided into a medical order status data table and an execution medical order data table according to the medical order usage function; the medical order status data table is only one data table, which is written after the doctor issues the medical order; the execution medical order data table is related to the drug warehouse associated with the medical order execution site, and the table structure of all execution medical order data tables is the same, the data table name contains the same main table name, and the drug warehouse ID associated with the execution site is used as the prefix or suffix of the main table name;

[0013] S6. Visualized medical order tracing is realized through the medical order tracing data table associated with the medical order ID. In addition to being associated with the medical order status data table, the medical order tracing data table is also associated with the packaged medical order data table;

[0014] S7. Determine the drug purchase plan or replenishment plan based on the average daily consumption of drugs in the drug warehouse, the frequency of use ranking rate, the number of days the remaining inventory can be used, the planned number of days, and the planned quantity, and generate the purchase plan or replenishment plan in combination with the upper and lower limits of the inventory;

[0015] S8. The outbound data of the drug circulation in the hospital is outbound according to the purchase plan data automatically generated by the subordinate warehouse, and the inbound data of the subordinate warehouse is derived from the outbound data of the superior warehouse. The inbound and outbound data can be completed by simply modifying the quantity in the aforementioned data. When the superior warehouse issues a drug across the hierarchical warehouse, the parent warehouse / child warehouse and the general warehouse in the subordinate warehouse are synchronously inbound. When the drug is outbound, the general warehouse is synchronously outbound at the same time as the parent warehouse / child warehouse is outbound.

[0016] S9. Inventory management includes preparation specifications, packaging specifications, and quantities and unit prices related to preparation specifications or packaging specifications. Only one of the data between preparation specifications and packaging specifications needs to be entered, and the other data is directly calculated based on the conversion coefficient in the local extension code data;

[0017] S10. Use the data in the hospital logistics system to collect statistics of various data and generate various reports;

[0018] S11. When the drug coding knowledge base uses the drug local extended code knowledge base, the drug coding in the information flow related to the physical flow of drugs uses the local extended code 17-digit code; the drug coding in the information flow related to the procurement plan and replenishment plan uses the local extended code 16-digit code.

[0019] Furthermore, the construction of the drug coding knowledge base and the drug supply enterprise code base in step S1 includes the following steps:

[0020] S101. The drug coding knowledge base is a database composed of a series of data tables and associated programs; the drug coding database data table is used as the most basic data table in the drug coding knowledge base, and the fields of the drug coding database data table at least include drug code, drug name, preparation specification, preparation unit, packaging specification, packaging unit, conversion coefficient, and manufacturer;

[0021] S102. The drug supply enterprise code library at least includes a drug enterprise code table. The fields of the enterprise code table at least include the enterprise name and enterprise code. The enterprise code table may also include the enterprise website, the purchase plan push website, the email address, the contact person, the contact person's QQ, and the WeChat account.

[0022] S103. The drug coding knowledge base and drug supplier code base are completely consistent within the hospital and at the supplier / supply chain end, and are updated synchronously.

[0023] Furthermore, the configuration method of the type, level, affiliation and inventory transfer of the drug warehouse described in step S2 is:

[0024] S201. According to the drug affiliation of the hospital drug warehouse, the drug warehouse affiliated to the hospital is the first level, and the drug warehouse of each pharmacy is the second level. If there is a sub-warehouse under the pharmacy, the pharmacy general warehouse is the second level, which belongs to the virtual warehouse, and the pharmacy physical warehouse is the third level; if the equipment in the pharmacy stores drugs and performs independent inventory management, the equipment warehouse in the pharmacy belongs to the third level; the spare drug warehouse / cabinet / equipment of each ward belongs to the third level warehouse, which is affiliated to the superior pharmacy general warehouse; if the hospital has branches and the branches also have drug warehouses, and the drugs are transferred from the headquarters drug warehouse, the branch drug warehouse belongs to the second level warehouse, the branch pharmacy general warehouse belongs to the third level warehouse, and the branch ward emergency medicine cabinet and spare drug warehouse / cabinet / equipment belong to the fourth level warehouse; and drug warehouses at all levels have unique IDs, and the drug warehouse type, drug warehouse level, and the ID of the superior warehouse with affiliation need to be added to the drug warehouse code data table before adding drug warehouses;

[0025] S202, Drug in and out: When drugs are transferred between a superior warehouse and a subordinate warehouse that have no subordinate relationship and neither of the superior warehouse nor the subordinate warehouse has a sub-warehouse, the physical goods are transferred from the superior warehouse to the subordinate warehouse. During the information transfer, the superior warehouse performs outbound operations and the subordinate warehouse performs inbound operations.

[0026] When drugs are transferred between a superior warehouse and a subordinate warehouse with a subordinate relationship, the physical goods are transferred from the parent warehouse to the sub-warehouse. When information is transferred, the parent warehouse is transferred and the sub-warehouse is transferred. There is no operation in the superior warehouse.

[0027] When drugs are transferred between a superior warehouse and a subordinate warehouse that have no affiliation and the subordinate warehouse has a sub-warehouse, the physical goods are transferred from the superior warehouse to the parent warehouse or sub-warehouse of the subordinate warehouse. During the information transfer, the superior warehouse performs the outbound operation, and the subordinate warehouse enters the warehouse, and at the same time, the parent warehouse or sub-warehouse of the subordinate warehouse enters the warehouse;

[0028] When drugs are transferred between a superior warehouse and a subordinate warehouse that have no affiliation and both superior and subordinate warehouses have sub-warehouses, the physical goods are transferred from the parent warehouse or sub-warehouse of the superior warehouse to the parent warehouse or sub-warehouse of the subordinate warehouse. During the information transfer, the general warehouse of the superior warehouse is out of stock, the parent warehouse or sub-warehouse is out of stock synchronously, and the general warehouse of the subordinate warehouse is in stock, and the parent warehouse or sub-warehouse of the subordinate warehouse is in stock at the same time; and the data of the information flow is synchronously written to the relevant data table;

[0029] S203. Dispensing medicines according to doctor's orders: When a drug warehouse without a sub-warehouse dispenses medicines according to doctor's orders, the medicines are shipped out according to the doctor's orders and written into the relevant data tables of the corresponding drug warehouse and / or the medicines; when a drug warehouse with a sub-warehouse dispenses medicines, the parent warehouse or the sub-warehouse and the main warehouse synchronously record the shipment of medicines according to the doctor's orders and write them into the relevant data tables of the parent warehouse / sub-warehouse and the main warehouse of the relevant drug warehouse.

[0030] Furthermore, the contents of the relevant data table of warehouse management in step S3 include:

[0031] S301, the warehouse management module consists of a series of data tables and application interface templates, and printing templates. The data tables are designed according to functions and application scenarios. The necessary data tables include inventory data tables, drug inventory details tables, outbound data tables, inbound data tables, purchase plan data tables, batch expiration date data tables, and traceability code data tables, and they are used for inventory query, inventory details query, inventory inventory, purchase plan setting, purchase plan formulation, outbound, inbound, batch expiration date query, traceability code query, prescription / doctor's order dispensing, generation of various reports, and doctor's order issuance;

[0032] Application interface templates and printing templates include inventory query, inventory table, inventory gains, inventory losses, purchase plan, inventory upper and lower limit settings, inventory details query, outbound, inbound, return, borrow and return medicines, loss report, query of near-expiry and expired medicines, query of batch number and expiration date, query of unsalable medicines, prescription dispensing, doctor's order dispensing, traceability code query, and system configuration files;

[0033] S302. The data table names in the warehouse management module are related to the drug warehouse ID and the drug ID: each type of data table has the same main table name, and the drug warehouse ID and / or drug ID are added as prefixes to generate the data table name of the drug warehouse or the drug. Among them, the inventory data table, outbound data table, inbound data table, and procurement plan data table are only related to the drug warehouse ID, and the data table name combination method adopts "drug warehouse ID+main table name" or "main table name+drug warehouse ID"; the drug inventory details table, batch number expiration date data table, and traceability code data table are related to the drug warehouse ID and drug ID, and their data table name combination method adopts "drug warehouse ID+drug ID+main table name" or "main table name+drug warehouse ID+drug ID", and the drug ID uses the unified drug code.

[0034] S303, the interface operation template and the printing template display menus according to personnel authority, and open the interface operation template through the menu; the acquisition of interface data obtains the drug warehouse ID and drug ID according to the content in the interface, and then opens, filters and obtains the data in the corresponding data table name; when the data in the interface operation template needs to be saved, the drug warehouse ID and drug ID are obtained according to the content in the interface, and when saving, the saved content is written into a data table with a different name according to the drug warehouse ID and drug ID;

[0035] S304. When a new drug store is added to the hospital, the drug store name and drug store ID are first added to the drug store code management, and each data table associated with the drug store ID is automatically copied and added according to the template;

[0036] The method of adding a new drug-related data table in a specific drug warehouse is as follows: when a specific drug warehouse has a storage operation, the drug ID in the drug inventory data table of the corresponding drug warehouse ID is detected. If not found, after obtaining the new drug ID, the data table related to the drug ID of the drug warehouse is copied and added for the warehouse;

[0037] S305. The three-level management of narcotic drugs is designed according to the warehouse management module, that is, different drug warehouse IDs, drug warehouse levels, upper drug warehouses, and parent-child warehouses are assigned to drugs in the management of narcotic drugs at all levels, and the information flow and information processing method are exactly the same as those of ordinary drugs;

[0038] S306. The warehouse management module also includes a donated drug warehouse and a GCP drug warehouse according to the needs of the hospital. The data tables and interfaces therein have the same data table structure as other general warehouse management modules, and the table name of the data table needs to be prefixed with a "no charge" code, and the drug ID in the data table needs to be prefixed with a "no charge" code, and the basic attribute information of the drug is the same as the original drug ID; the relevant procedures for donated drugs and GCP drugs do not involve the unit price and amount of the drugs, or the unit price and retail amount are both zero.

[0039] Furthermore, the generation of the invoice QR code and the purchase plan QR code and the internal and external network data analysis described in step S4 includes the following steps:

[0040] S401. Elements of the invoice QR code include: hospital resolution website IP address, invoice QR code identifier, supplier enterprise code, hospital code, invoice date, drug code, quantity, unit price, batch number, expiration date, invoice number, drug store code, to-be-continued identifier or end identifier. The above data is used to generate the invoice QR code through QR code generation software, and printed on the invoice or the accompanying bill, or sent to the mobile phone of the relevant personnel, or downloaded and displayed on the website by the relevant personnel; drug code, quantity, unit price, batch number, expiration date, invoice number, drug store code are entered in a circular manner;

[0041] S402, parsing of the invoice QR code in the hospital intranet: use the QR code scanner in the hospital intranet to scan the invoice QR code, and find the address of the invoice parsing program stored in the intranet through the hospital parsing website IP address in the QR code. The invoice QR code identifier is a parsing program. First, the hospital code is parsed to see if it is consistent with the stored hospital code. If not, parsing is not possible. If consistent, all data is parsed into the invoice data table according to the parsing program. Among them, the supplier code is parsed into the supplier name using the supplier table in the system, and the drug code is parsed into data fields such as drug name, manufacturer, and packaging specifications according to the drug code library data table; the drug name and manufacturer can also be parsed into the hospital drug name and hospital manufacturer name according to the hospital settings; after the parsing is completed, the data in the invoice data table is parsed into the drug storage data table;

[0042] S403, Generation of entry order: When the hospital drug warehouse is operating, if the corresponding drug warehouse has unentered data, it will prompt that the operation needs to be performed, and directly fill in all the data of the entry order into the entry interface. After confirmation, the entry operation is completed, and the entry mark in the entry data table is changed to "yes" ;

[0043] S404, generation of procurement plan QR code: the procurement plan is generated by the program according to the procurement plan or the replenishment plan. The drug warehouse purchaser adjusts the procurement plan in the interface, and generates a procurement plan QR code after the adjustment. The procurement plan QR code includes: QR code parsing IP address, procurement plan identifier, hospital code, drug code, quantity, drug warehouse code, supplier enterprise code, to-be-continued identifier or end identifier. The procurement plan QR code is generated by the QR code generation software; the drug code and quantity can be entered cyclically;

[0044] S405. Parsing of the procurement plan QR code on the external network: Scan the procurement plan QR code using a mobile phone APP or a QR code scanner on the hospital's external network, and find the address of the procurement plan parsing program stored in the external network through the IP address in the procurement plan QR code. The procurement plan identifier is a parsing program that parses all data into the procurement plan data table in the parsing order, wherein the hospital code is parsed from the hospital name using the hospital information table stored on the website, the drug code is parsed into the data fields of drug name, manufacturer, and packaging specifications based on the drug code library data table, and the supplier code is parsed into the drug supplier name, website, email address, WeChat, QQ using the supplier table stored on the website; the system automatically sends the procurement plan to the address specified by the relevant supplier via the website, email address, WeChat, or QQ.

[0045] Furthermore, the doctor's order management module described in step S5 is implemented by the following steps:

[0046] S501. In addition to the necessary information of the medical order, the medical order status data table also contains the medical order status, that is, the real-time data of the link of the medical order; the medical order status data table uses the medical order ID as the primary key, and its fields include all the fields related to the medical order and the medical order status. The fields related to the medical order include patient ID, medical order type, prescription ID, current hospitalization ID, ward ID, bed number, nursing unit ID, medical order ID, medical order group number, drug ID, drug name, preparation specification, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, total amount of medical order, and remarks; if the medical order status is included in the HIS, it is obtained through the interface or the hospital information platform message transmission method; if the medical order status is not included in the HIS, the medical order status is written into the SPD system through the specific operation of the HIS system; the writing of the drug warehouse outbound data table is determined according to the medical order status set by the system;

[0047] S502, the medical order status in the medical order status data table is set and adjusted by the hospital according to the hospital management plan and process, and is stored in advance in the medical order status basic table; the fields of the medical order status basic table at least include the primary key, medical order status name, execution location, execution location code, associated drug store, associated drug store code, and whether it is effective;

[0048] S503. The execution doctor order data table adopts a modular design. All the execution doctor order data tables have the same table structure and the same execution program, but different data table names. All the execution doctor order data tables contain the same main table name, and the execution location associated drug library code is used as the prefix or suffix of the main table name. The fields of the execution doctor order data table include at least: patient ID, doctor order type, prescription ID, current hospitalization ID, ward ID, bed number, nursing unit ID, doctor order ID, doctor order group number, drug ID, drug name, preparation specification, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, total amount of doctor orders, remarks, medication time, batch, execution time, execution location, execution location code, and execution result.

[0049] S504: The execution doctor's order data table is written according to the contents of the doctor's order status data table. The name of the data table to be written needs to be consistent with the drug store code associated with the execution location. The timing and contents of data writing are related to the doctor's order type and / or execution location.

[0050] Medical orders that are executed only once include outpatient and emergency prescriptions, temporary inpatient orders, and orders to take medicines when discharged. The timing of writing the execution order data table is determined by the hospital configuration file;

[0051] The medical orders executed daily are mainly long-term medical orders for inpatients. Through the rolling medical order process of HIS, the relevant data is written into the execution medical order data table at a fixed time every day;

[0052] Medical orders that are executed multiple times a day include those executed by the intravenous preparation center and the single-dose dispensing machine, which are usually long-term medical orders. The relevant medical orders are written into the execution medical order data table at a fixed time every day according to the decision-making mechanism;

[0053] S505, writing of data from other data tables in the doctor's order data table: when a specific operation is performed on the doctor's order, the doctor's order status in the doctor's order status data table changes synchronously, including: billing, dispensing, checking, dispensing, labeling, matching, warehousing, preparation, warehousing, sorting, packaging, single-dose placement, and single-dose checking;

[0054] When executing a specific operation on the execution of a doctor's order, the drug inventory data table, drug inventory detail data table, batch number expiration date data table, and traceability code data table corresponding to the drug warehouse ID and / or drug ID of the execution site are synchronously written into the doctor's order outbound data, and the outbound timing is associated with the doctor's order status through the hospital configuration file;

[0055] Writing the cumulative quantity of executed medical orders in the medical order status data table: while writing the outbound data to the inventory-related data table, add the outbound quantity of this executed medical order to the cumulative quantity of executed medical orders in the medical order status data table and record it in the cumulative quantity of executed medical orders.

[0056] Furthermore, the visualized medical order tracing described in step S6 is implemented by the following steps:

[0057] S601. The key data table used by the medical order tracing module is used as the medical order tracing data table, and its fields include at least patient ID, prescription number, medical order number, medical order status, operation time, and medical order package ID. The medical order status in the medical order tracing data table is synchronized with the real-time medical order status in the medical order status data table. When a medical order ID changes the medical order status in the medical order status data table, a piece of data is added to the tracing medical order table, and the time when the medical order status changes is recorded as the operation time; if the medical order is packaged, the medical order package ID is recorded synchronously;

[0058] S602. Display the location of each medical order / drug in a table or graphic form according to the location of the medical order ID, or check the location of each patient's drug according to the patient information associated with the medical order ID.

[0059] Furthermore, the method for generating the purchase plan or the medicine replenishment plan in step S7 is:

[0060] S701. Generation of procurement plan / drug replenishment plan: The fields in the inventory data table displayed in the interface are: drug code, drug name, simple packaging specification, planned quantity per packaging unit, number of days physical inventory can be used, planned days, simple preparation specification, planned quantity per preparation unit, planned quantity, planned quantity unit, whether to purchase, and manufacturer; among them, the planned quantity per packaging unit, the planned quantity per preparation unit, and the planned quantity are automatically adjusted after the planned days are modified. The planned quantity is calculated by converting the planned quantity per packaging unit into multiples of the minimum planned whole packaging quantity and rounding off. Whether to purchase is adjusted in the interface; the procurement plan seen by the superior library and the generation of the hospital plan QR code are displayed or generated according to the above data requirements.

[0061] Furthermore, the automatic generation of the inbound and outbound data in step S8 includes the following steps:

[0062] S801. After the subordinate drug warehouse generates a replenishment plan, the superior warehouse automatically obtains the drug name, specification, and quantity information in the replenishment plan of the subordinate warehouse on the outbound interface, fills it in the outbound interface, and directly saves and prints the outbound order. In addition, the interface can be used to add drugs, delete drugs, and modify the outbound quantity to generate an outbound order, which is saved and printed for physical outbound delivery; useful content in the outbound order also includes viewing or printing the drug's warehouse location code, the inventory quantity of the current warehouse, the inventory quantity of the subordinate warehouse, and the number of days the inventory of the subordinate warehouse can be used;

[0063] S802. When the upper warehouse issues the drugs, the lower warehouse can synchronously receive the information of the drugs issued by the upper warehouse and generate the entry order of the lower warehouse to be displayed on the interface; the lower warehouse confirms the acceptance of all the entry orders on the interface, or completes the entry of some drugs by deleting a drug in the entry order or modifying the entry quantity;

[0064] S803. When some drugs are put into the lower-level warehouse, a return order is generated in the upper-level warehouse at the same time. The return quantity is the difference between the outgoing quantity of this warehouse and the received quantity of the lower-level warehouse. The return is completed after confirmation in the interface.

[0065] S804: When the upper-level warehouse directly issues goods to the parent warehouse or child warehouse of the lower-level warehouse, an issue order for the upper-level warehouse to issue goods to the lower-level general warehouse and an issue order for the upper-level warehouse to issue goods to the parent warehouse or child warehouse of the lower-level warehouse are generated at the same time; when the lower-level warehouse does not fully receive goods, the upper-level warehouse has a return order, but the lower-level warehouse has no return order.

[0066] Furthermore, the steps for implementing the quantity and unit price related to the preparation specifications and packaging specifications described in step S9 are:

[0067] S901. If the quantity obtained in the inventory management is the quantity and price of the preparation units, the quantity in packaging units = the quantity in packaging units / conversion coefficient, and the packaging unit price = the preparation unit price*conversion coefficient; if the quantity obtained in the inventory management is the quantity and price of the packaging units, the quantity in preparation units = the quantity in packaging units*conversion coefficient, and the preparation unit price = the packaging unit price / conversion coefficient; wherein the conversion coefficient is derived from the drug coding library data table, or is obtained from the hospital drug basic information table generated based on the drug coding library data table.

[0068] Furthermore, the steps of performing statistics of various types of data and generating various reports in step S10 include:

[0069] S1001. Query and print the detailed list of each drug in each drug warehouse: After inputting the drug warehouse name and drug name, obtain the drug warehouse ID and drug ID respectively, and combine them with the prefix / suffix of the drug inventory detailed list to find the data table name. Through conditional screening, you can view the detailed data of each drug in a specific drug warehouse within a certain period of time;

[0070] S1002. Query and print the inventory table of each drug warehouse: After inputting the drug warehouse name, obtain the drug warehouse ID, and combine it with the inventory data table prefix / suffix to find the data table name, and directly view or print the real-time inventory data of the corresponding drug warehouse; if the total warehouse inventory table is required, directly open the designated total warehouse inventory data table to view the summary data of the inventory data of each sub-warehouse;

[0071] S1003. Query and print hospital purchase data: directly filter all drug storage data tables at the drug store level 1 and summarize the data of the specified date into a temporary table to display the purchase data of the entire hospital; if the purchase data of a certain type of drug is specified, the purchase data of this type of drug is displayed by entering the drug attributes; if the purchase data of a certain drug store is specified, the purchase data of the drug store name is displayed by entering the drug store name;

[0072] S1004. Drug sales data query and printing: open each outbound data table of the drug warehouse level 2, filter all outbound data of the specified time period and the business type of medical order outbound and summarize them into a temporary table, enter the viewing conditions in the interface to filter in the temporary table, and summarize and display the total sales quantity or total amount of each drug under various conditions, or filter the total sales quantity or total amount of a certain type of drugs by the attributes associated with each drug, or the quantity converted by attribute data;

[0073] S1005. Query of unsaleable drugs: Open the inventory data table of the designated drug warehouse, sort the usage rate from low to high to display the sorting rate of each drug, and find the unsaleable drugs in the designated warehouse through the remaining inventory usable days, the minimum inventory usable days and the minimum inventory usable days drug warehouse ID, or the drug name and inventory usable days of the unsaleable drugs in all subordinate warehouses.

[0074] Furthermore, the step of using the drug-based extended code as the unified drug code in step S11 includes:

[0075] S1101. Use the 16-digit drug-based extended code as the purchase plan data. When the drug name and / or the manufacturer name and / or the approval number are changed, the quantities before and after the change are combined in the statistical purchase quantity. The uploaded purchase plan or replenishment plan is converted into a delivery note for supply based on the inventory status of the drug supplier / superior warehouse.

[0076] In summary, the present invention has the following beneficial effects:

[0077] 1. The present invention designs databases and data tables based on application scenarios, which can avoid the database running significantly slower due to excessive data volume after long-term operation. In addition, only a few data tables need to be called for different application scenarios and when indexing or querying, and the program design is simple;

[0078] 2. The parent-child library design mode in the present invention is conducive to the consistency of the general ledger management and financial management data of a pharmacy inventory, and can manage the accounts of the parent library or the child library separately, which is conducive to generating respective medicine replenishment plans, warehousing and warehousing operations and inventory management for different libraries, and the physical inventory is consistent with the book inventory (excluding the case of borrowing medicine). This scheme has very clear ownership in the management of ward spare medicines, emergency medicines, and especially the management of anesthetic drugs in the ward, and effectively supervises the management and replenishment of spare large infusions in the ward, and does not affect the respective inventory (the physical inventory is consistent with the book inventory);

[0079] 3. In the present invention, the invoice data and purchase plan data between the drug supplier and the hospital are respectively generated and parsed by the QR code, so as to realize the data exchange when the internal and external networks of the hospital are not connected;

[0080] 4. Modular design of drug storage management. When the hospital needs to add a drug warehouse, the hospital can implement new drug warehouse storage management related modules by itself without the need for technical support from software designers.

[0081] 5. In the present invention, the purchase plan and the medicine replenishment plan are generated mainly by using the average daily consumption, the frequency of use and the frequency of use ranking rate, the number of days that the remaining inventory can be used, etc. The purchase plan can be dynamically managed according to the actual consumption or usage of each warehouse, avoiding the unreasonable inventory situation caused by the purchase plan formulated by the upper and lower limit management of inventory;

[0082] 6. In the present invention, the drug outbound, inbound, purchase plan or replenishment plan data are interrelated, and the staff does not need to input drug data, and the preparation of the inbound and outbound order can be completed by modifying or not modifying the quantity, which saves the workload and work intensity of the warehouse management staff;

[0083] 7. The warehouse management data tables of each warehouse in the present invention contain the quantity and unit price in terms of preparation units and packaging units, and can be automatically converted to each other through the conversion coefficients in the unified coding knowledge base, which is suitable for data requirements in different application scenarios;

[0084] 8. Through the present invention, nurses can visualize the status of each patient's medical order / drug location at any time, so as to determine the time to go to the pharmacy to pick up medicine, or adjust the patient's treatment order according to the status of the medical order / drug location;

[0085] 9. In the present invention, the unified drug coding uses the local extension code, and the drug coding in the information flow related to the physical flow of drugs uses the local extension code 17-bit code, which is applicable to all physical data and information data are completely consistent; the drug coding in the information flow related to the procurement plan and the replenishment plan uses the local extension code 16-bit code, which is applicable to the disadvantage that the existing data cannot be fully used due to the change of the drug name or the change of the manufacturer's name. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] Figure 1 It is a schematic diagram of the process of the in-hospital logistics information system in an embodiment of the present invention;

[0087] Figure 2 It is a schematic diagram of a hospital architecture related to medicines in an embodiment of the present invention. DETAILED DESCRIPTION

[0088] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0089] The technical solution of the present invention provides a processing method for an in-hospital logistics information system based on unified drug coding, and its basic idea is:

[0090] 1. The unified drug coding refers to the same drug coding used by hospitals and drug suppliers. The drug coding is accompanied by a series of basic drug information, such as drug name, specification, manufacturer, packaging unit, conversion coefficient, preparation unit, etc., which is called drug knowledge base. The drug knowledge base is exactly the same in the hospital intranet and drug supplier / supply chain. The unified coding in the embodiment refers to the local extension code;

[0091] 2. Design databases and data tables according to SPD functions and application scenarios, mainly including warehouse management module and doctor's order management module: such as drug inventory data table, drug inventory detail table, incoming data table, outgoing data table, purchase plan data table, drug batch number expiration date data table, drug traceability code data table, etc. in the drug warehouse management module. The main table names of data tables with the same application scenario or the same function are all the same. The table names of data tables for different warehouses or different drugs are preceded or followed by the drug warehouse ID and / or drug ID. For example, the prefix or suffix of the drug inventory data table, incoming data table, outgoing data table, and purchase plan data table is In the drug warehouse ID, drug inventory details table, drug batch expiration date data table, and drug traceability code data table, the prefix or suffix in the main table name includes the drug warehouse ID and drug ID (drug ID is the unified drug code); the data tables related to drug use include the doctor's order status data table, the execution doctor's order data table, the packaged doctor's order data table, etc., among which the doctor's order status data table uses the doctor's order ID as the primary key and is written after the doctor issues the doctor's order; the execution doctor's order data table determines the timing of writing data to the associated drug warehouse data table based on the change of the doctor's order status, and the packaged doctor's order table is associated with the doctor's order ID, and further associated with the patient, so as to achieve the purpose of doctor's order tracing and then patient drug tracing;

[0092] 3. According to the different types of drug warehouses, the drug warehouses are divided into independent warehouses and parent-child warehouses. The information management of independent warehouses adopts conventional inventory management methods. In addition to the independent inventory management related data tables for the parent warehouse and the child warehouse, the parent-child warehouse also needs to build a separate data table for the storage management of the parent-child warehouse master warehouse. The in-and-out data of the child warehouse is synchronized with the operation of the master warehouse.

[0093] 4. When a drug supplier / supply chain company supplies drugs to a hospital, it prints the invoice QR code on the invoice or accompanying documents, or sends it to a relevant website or mobile phone. After scanning the QR code on the hospital intranet, a warehouse entry form is automatically generated. The procurement plan formulated by the hospital generates a procurement plan QR code on the hospital intranet. After scanning the procurement plan QR code on the external network, the procurement plan is directly distributed to different drug suppliers.

[0094] 5. The drug storage management part adopts modular design. The warehouse includes the storage management of the hospital drug warehouse, the storage management of each pharmacy, the storage management of drugs in the pharmacy equipment, the storage management of drugs in the first aid cabinets of each ward, the storage management of the spare drug warehouse in the ward, the storage management of drugs in the ward equipment, etc. All drug warehouses use the same data table structure and the same data storage method. The running program determines which data table of which storage management to use through parameters, etc.; every time the hospital adds a drug warehouse, the module related to the storage management is directly copied in the database and the required data table name is set through parameters such as the drug warehouse ID, and the relevant data tables and running programs in the drug storage management are added;

[0095] 6. The usage of the drug purchase plan is mainly based on the average daily consumption of drugs in the drug warehouse, the frequency of use and the frequency of use ranking rate, the number of days the remaining inventory can be used, etc., and the purchase plan or replenishment plan is generated by combining the upper and lower limits of the inventory;

[0096] 7. The outbound data of the drug circulation in the hospital is outbound according to the automatically generated purchase plan, and the incoming data of the drug warehouse is derived from the outbound data of the upper-level warehouse. In most cases, the inbound and outbound data do not need to be manually input, and only the quantity needs to be modified in the aforementioned data. The incoming data of the lower-level warehouse is derived from the outbound data of the upper-level warehouse, forming a closed-loop data flow of purchase / replenishment plan → outbound from the upper-level warehouse → inbound from the lower-level warehouse → outbound medical orders from the lower-level warehouse → purchase / replenishment plan;

[0097] 8. All inventory management includes preparation specifications and packaging specifications, as well as the quantity and amount related to the preparation specifications or packaging specifications. Only one of the data between the preparation specifications and packaging specifications needs to be entered, and the other data can be directly calculated based on the conversion coefficient in the unified drug coding knowledge base;

[0098] 9. If the unified coding uses the drug-based extended code, the procurement / replenishment plan shall be managed using a 16-digit code to avoid the loss of procurement / replenishment plan data due to changes in the drug name and / or manufacturer name, as well as the problem that upstream drug suppliers cannot obtain accurate procurement data.

[0099] Example 1: Hospital drug information correspondence and maintenance example

[0100] 1. Copy the drug-based extended code table and related attribute knowledge base and supplier code base to the hospital server;

[0101] 2. The hospital drugs correspond to the drugs in the table of HIS drug unique ID and the local extension code one by one, and establish the corresponding relationship between the hospital HIS unique drug ID and the local extension code;

[0102] 3. Acquisition and modification of attributes in the HIS drug basic attribute data table: automatically add attributes of each drug according to the attribute data in the attribute table associated with the local extension code, and allow HIS to modify it by itself in the interface; if the in-hospital logistics system and the hospital HIS system only interact with medical order data, and the in-hospital logistics system is a self-contained system, there is no need to modify the HIS drug basic attribute data table (the embodiments of the present invention are all in this way); the in-hospital logistics system and the hospital HIS system interact with medical order data and obtain patient data and department data through an interface, or automatically transmit the required data through the hospital information management platform.

[0103] 4. If the drug-based extended code and its attributes in the knowledge base are updated, or the supply enterprise code library is updated, update it for the hospital in a timely manner.

[0104] Example 2: Create a data table instance based on the hospital architecture. See the hospital architecture related to drugs. Figure 2 .

[0105] 1. Drug store code data table (see the table below)

[0106]

[0107]

[0108] 2. Structure and naming of drug inventory data table Fields and meanings of drug inventory data table (see the table below)

[0109]

[0110]

[0111] The drug inventory data table is uniformly named Inventory_data_table. According to each drug store ID, the drug inventory data table name of each drug store is "drug store ID_Inventory_data_table". For example, the drug inventory data table name of the Chinese patent medicine store is 1-01_Inventory_data_table, the drug inventory data table name of the Western medicine store is: 1-02_Inventory_data_table, the drug inventory data table name of the intravenous preparation center is 2-05_Inventory_data_table, the drug inventory data table name of the ward pharmacy is 2-04_Inventory_data_table, the drug inventory data table name of the ward pharmacy is 3-004_Inventory_data_table, the drug inventory data table name of the internal medicine spare medicine cabinet is 3-015_Inventory_data_table,......

[0112] 3. Structure and naming of drug inventory details

[0113] Drug inventory details table fields and meanings (see the table below)

[0114]

[0115]

[0116] The drug inventory details table is uniformly named Drug_list. According to each drug warehouse ID and each drug ID (local extension code), the drug inventory data table name of each drug warehouse is "drug warehouse ID_local extension code_Drug_list". The following table shows the table names of several drug inventory details tables in the western medicine warehouse (drug warehouse ID is 1-02) and the information of the drugs they represent.

[0117]

[0118]

[0119]

[0120] If it is a detailed inventory list of drugs in the general warehouse of an outpatient western medicine pharmacy, change 1-02 in the above table to 2-02; similarly, for a detailed inventory list of drugs in an outpatient western medicine pharmacy, change 1-02 in the above table to 3-002; for a detailed inventory list of drugs in the internal medicine department's spare medicine cabinet, change 1-02 in the above table to 3-014.

[0121] 4. Structure and naming of drug procurement plan data table

[0122] Drug procurement plan data table fields and meanings (see the table below)

[0123]

[0124]

[0125] The drug purchase plan data table is uniformly named Purchase_plan. According to each drug store ID, the drug purchase plan data table of each drug store is named "drug store ID_Purchase_plan". For example, the drug purchase plan data table of the Chinese patent medicine store is named 1-01_Purchase_plan, the drug purchase plan data table of the Western medicine store is named 1-02_Purchase_plan, the drug purchase plan data table of the intravenous preparation center is named 2-05_Purchase_plan, the drug purchase plan data table of the ward pharmacy is named 2-04_Purchase_plan, the drug purchase plan data table of the ward pharmacy is named 3-004_Purchase_plan, the drug purchase plan data table of the internal medicine spare medicine cabinet is named 3-015_Purchase_plan, etc.

[0126] Purchase plan master table (Purchase_plan_master_table): The only data table in the hospital, which is automatically written when each purchase plan is generated. When each drug warehouse issues goods, it takes corresponding data according to the attributes. The data table structure is as follows:

[0127]

[0128]

[0129] 5. Structure and naming of drug outbound data table Fields and meanings of drug outbound data table (see the table below)

[0130]

[0131]

[0132] The drug outbound data table is uniformly named Ex_warehouse. According to each drug warehouse ID, the drug outbound data table name of each drug warehouse is "drug warehouse ID_Ex_warehouse". For example, the drug outbound data table name of the Chinese patent medicine warehouse is 1-01_Ex_warehouse, the drug outbound data table name of the Western medicine warehouse is 1-02_Ex_warehouse, etc.

[0133] 6. Structure and naming of drug storage data table

[0134] Drug entry data table fields and meanings (see the table below)

[0135]

[0136]

[0137] The drug storage data table is uniformly named Warehousing. According to each drug storage ID, the drug storage data table of each drug storage is named "drug storage ID_Warehousing". For example, the drug storage data table of the Chinese patent medicine storage is named 1-01_Warehousing, the drug storage data table of the Western medicine storage is named 1-02_Warehousing, the drug storage data table of the intravenous preparation center is named 2-05_Warehousing, the drug storage data table of the ward pharmacy is named 2-04_Warehousing, the drug storage data table of the ward pharmacy is named 3-004_Warehousing, the drug storage data table of the internal medicine spare medicine cabinet is named 3-015_Warehousing, etc.

[0138] Example 3: Example of closed-loop generation and information flow of drug storage and purchase plan

[0139] 1. Information flow when drugs are transferred between a superior library and a subordinate library that have no affiliation and neither the superior library nor the subordinate library has a sub-library

[0140] Example: The Chinese patent medicine warehouse issues medicines to the outpatient Chinese medicine pharmacy, and the outpatient Chinese medicine pharmacy generates the following medicine replenishment plan:

[0141] The data comes from the purchase plan table generated by the outpatient Chinese medicine pharmacy (the conventional superior library ID Higher_Drug_Storage_ID in the purchase plan master table Purchase_plan_master_table is 1-1, and the purchase plan status Complete_plan_Status=Y. The purchase plan number Purchase_plan_No is found (where the corresponding purchase plan warehouse ID Purchase_plan_Drug_Storage_ID=2-01). All Purchase_plan_No data is filtered in the outpatient Chinese medicine pharmacy drug purchase plan data table 2-01_Purchase_plan, see the table below:

[0142]

[0143] The interface of the Chinese patent medicine warehouse outbound order is as follows:

[0144] Henan Provincial Tenth People's Hospital Traditional Chinese Medicine Warehouse Outbound Order

[0145]

[0146] Note: Because there are only 40 boxes of Wuji Baifeng Pills (Shui Mi Pills) in stock, the actual quantity shipped cannot exceed the inventory quantity, so the system automatically changes the actual quantity shipped to 40 boxes;

[0147] A box of anti-osteophyte tablets contains 50 boxes. The drug warehouse does not want to unpack the boxes for delivery, so it artificially changes the quantity to 5 boxes.

[0148] The outbound operation is completed (saved), and the inventory table of the Chinese patent medicine warehouse, the inventory details table of each medicine in the Chinese patent medicine warehouse, the batch number expiration date data table, and the traceability code data table are read and written respectively; the outbound identification in the outbound data table of the Chinese patent medicine warehouse = Y; the incoming data is written into the incoming data table of the outpatient Chinese medicine pharmacy, where the incoming identification = N; the procurement plan status of all medicines with the same procurement plan number in the procurement plan data table of the outpatient Chinese medicine pharmacy = Y; the procurement plan status of the same procurement plan number in the procurement plan master table = Y.

[0149] After the medicine is delivered to the outpatient Chinese medicine pharmacy, the outpatient Chinese medicine pharmacy opens the warehousing operation interface as follows:

[0150] Henan Provincial Tenth People's Hospital Outpatient Chinese Medicine Pharmacy Receipt

[0151]

[0152] Since we are only willing to accept 30 boxes of anti-bone hyperplasia tablets, the inventory quantity is changed to 30 boxes, so 20 boxes need to be returned and the remaining drugs are fully confirmed to be received.

[0153] The entry operation is completed (saved), and the outpatient Chinese medicine pharmacy inventory table, the inventory details table of each drug in the outpatient Chinese medicine pharmacy, the batch number expiration date data table, and the traceability code data table are read and written respectively. The entry mark in the outpatient Chinese medicine pharmacy entry data table = Y. At the same time, the anti-bone hyperplasia tablets return data is written to the Chinese patent medicine warehouse entry data table. The Chinese patent medicine pharmacy automatically generates the following return order when opening the outbound order.

[0154] Henan Provincial Tenth People's Hospital Outpatient Chinese Medicine Pharmacy Receipt

[0155]

[0156] The destocking operation is completed (saved), and the inventory table of the Chinese patent medicine warehouse, the inventory details table of anti-bone hyperplasia tablets in the Chinese patent medicine warehouse, the batch number and expiration date data table of anti-bone hyperplasia tablets, and the traceability code data table of anti-bone hyperplasia tablets are read and written respectively; the outbound identification in the outbound data table of the Chinese patent medicine warehouse = Y.

[0157] The updated information of each data sheet is as follows (only necessary information and inventory update are noted):

[0158] (1) The inventory quantity change process of the Chinese patent medicine warehouse drug inventory data table (1-01_Inventory_data_table) is shown in the following table:

[0159]

[0160] Note: The arrow in the inventory quantity → indicates the change in inventory quantity before and after delivery.

[0161] Among them, the inventory quantity of the anti-bone hyperplasia tablets changed from 50 boxes to 0 before they were shipped out and the outpatient Chinese medicine pharmacy had not confirmed receipt. After the outpatient Chinese medicine pharmacy confirmed receipt of 30 boxes, the inventory quantity remained 0. After confirming receipt of 20 boxes of drugs and confirming the return in the return interface, the inventory quantity changed to 20 boxes.

[0162] (2) The Chinese patent medicine warehouse return form interface is displayed as follows:

[0163] Henan Provincial Tenth People's Hospital Traditional Chinese Medicine Warehouse Outbound Order

[0164] (3) Inventory quantity change process of the drug inventory data table (2-01_Inventory_data_table) of the outpatient Chinese medicine pharmacy:

[0165]

[0166]

[0167] Note: After the Chinese patent medicine warehouse is shipped out, the inventory quantity of the outpatient Chinese medicine pharmacy remains unchanged before confirming receipt, and the inventory quantity after receipt changes. In the return operation, the inventory quantity of the outpatient Chinese medicine pharmacy is not affected.

[0168] (4) Details of the Chinese patent medicine library's anti-bone hyperplasia tablets (1-01_86902936000263010_Drug_list):

[0169] Inventory details of Chinese patent medicine warehouse

[0170]

[0171]

[0172] (5) Contents of the Anti-bone Hyperplasia Tablets List in the Outpatient Chinese Medicine Pharmacy (2-01_86902936000263010_Drug_list)

[0173] Drug inventory details of outpatient Chinese medicine pharmacy

[0174]

[0175] 2. An example of information flow when drugs are transferred between a superior warehouse and a subordinate warehouse with a subordinate relationship is to take the example of oral rehydration salt powder (II) issued from the ward pharmacy to the internal medicine department's spare medicine cabinet.

[0176] (1) Physical circulation:

[0177] According to the medicine replenishment plan for the internal medicine department's spare medicine cabinet, 5 boxes of oral rehydration salt powder (II) need to be replenished, and the actual goods will be delivered from the ward pharmacy to the internal medicine department's spare medicine cabinet.

[0178] (2) Ward Pharmacy Outbound Delivery Note

[0179] The interface of the Chinese patent medicine warehouse outbound order is as follows:

[0180] Henan Provincial Tenth People's Hospital Ward Pharmacy Outbound Order

[0181]

[0182] The data entered into the internal medicine nursing unit is basically consistent with the data in the above table.

[0183] There is no need for an outbound delivery note from the ward pharmacy general warehouse.

[0184] (3) Ward pharmacy drug inventory data table (3-004_Inventory_data_table) The inventory change process is shown in the following table:

[0185]

[0186] There is no change in the inventory in the ward pharmacy's general drug inventory data table.

[0187] (4) The inventory change process of the drug inventory data table (3-015_Inventory_data_table) of the internal medicine nursing unit library is shown in the following table:

[0188]

[0189] (5) Ward Pharmacy Oral Rehydration Salt Powder (II) List (3-004_86904920000280010_Drug_list)

[0190] Inventory details of Chinese patent medicine warehouse

[0191]

[0192] (6) Details of oral rehydration salt powder (II) for internal medicine nursing unit (3-015_86904920000280010_Drug_list):

[0193] Medicine inventory details for internal medicine nursing unit

[0194]

[0195]

[0196] 3. Information flow when drugs are transferred between a superior library (superior library has no sub-library) and a subordinate library with no affiliation and the subordinate library has a sub-library:

[0197] The example is that the Chinese medicine warehouse shipped 100 boxes of Chanfu An Capsules to the ward pharmacy (the replenishment plan is omitted), and the ward pharmacy received all of them.

[0198] (1) The interface of the Chinese patent medicine warehouse outbound order is as follows:

[0199] Henan Provincial Tenth People's Hospital Traditional Chinese Medicine Warehouse Outbound Order

[0200]

[0201] (2) Ward pharmacy inventory receipt (no interface display, generated in the background)

[0202] Henan Provincial Tenth People's Hospital Ward Pharmacy Receipt

[0203]

[0204]

[0205] The ward pharmacy general warehouse has the same entry order as the above table

[0206] (3) Details of the Chinese patent medicine library's Chanfuan capsules list (1-01_86904920000303010_Drug_list)

[0207] Inventory details of Chinese patent medicine warehouse

[0208]

[0209] (4) Details of the Chanfuan Capsule List in the Ward Pharmacy (2-01_86904920000303010_Drug_list)

[0210] Ward pharmacy drug inventory details

[0211]

[0212]

[0213] The detailed inventory list of drugs in the ward pharmacy is exactly the same as the above table (this drug is not available in the spare drug warehouse and emergency drug warehouse of each ward).

[0214] 4. Information flow between the upper-level library (the upper-level library has sub-libraries) and the lower-level library that have no affiliation, and the lower-level library has sub-libraries

[0215] Taking dexamethasone sodium phosphate injection as an example, the inventory transfer was transferred from the outpatient Western pharmacy to the ward pharmacy (no purchasing plan, transferred through the outbound delivery procedure).

[0216] (1) The outpatient pharmacy delivery order interface is as follows:

[0217] Outpatient Pharmacy Delivery Order of Henan Province Tenth People's Hospital

[0218]

[0219] The outpatient Western pharmacy general warehouse outbound delivery order is exactly the same as the above-mentioned outbound delivery order. It is only a virtual outbound delivery order and does not need to be displayed or confirmed.

[0220] (2) The interface of the ward pharmacy entry form is as follows:

[0221] Henan Provincial Tenth People's Hospital Ward Pharmacy Receipt

[0222]

[0223] The ward pharmacy general warehouse receipt is exactly the same as the above-mentioned delivery note. It is only a virtual receipt and does not need to be displayed or confirmed.

[0224] (3) Outpatient Western medicine dexamethasone sodium phosphate injection list (3-002_86902434000734000_Drug_list)

[0225] Outpatient Western Pharmacy Drug Inventory Details

[0226]

[0227]

[0228] (4) Details of the Dexamethasone Sodium Phosphate Injection in the Outpatient Pharmacy (2-02_86902434000734000_Drug_list)

[0229] Outpatient Western Pharmacy General Warehouse Drug Inventory Details

[0230]

[0231] The inventory of the outpatient western medicine pharmacy's total warehouse is inconsistent with the inventory of the outpatient western medicine pharmacy because the inventory quantity of the total warehouse also includes the inventory quantity in the outpatient western medicine pharmacy's house warehouse, such as the inventory of 10 each in the CT room's first aid medicine cabinet and the MRI room's first aid medicine cabinet.

[0232] (5) Details of the dexamethasone sodium phosphate injection list in the ward pharmacy (3-004_86902434000734000_Drug_list)

[0233] Ward pharmacy drug inventory details

[0234]

[0235] The difference of 10 between the final inventory quantity in packaging units and the book inventory quantity in packaging units is because 10 drugs are borrowed. The book inventory quantity in packaging units is the book inventory quantity, and the inventory quantity in packaging units is the actual inventory quantity. All procurement plans, physical inventory, and whether medical orders can be issued are based on the physical inventory.

[0236] (6) Details of the dexamethasone sodium phosphate injection in the ward pharmacy (2-04_86902434000734000_Drug_list)

[0237] Ward pharmacy drug inventory details

[0238]

[0239] The inventory of the ward pharmacy's general warehouse is inconsistent with that of the ward pharmacy because the inventory quantity of the general warehouse also includes the inventory quantity in the ward pharmacy's sub-warehouse, such as 10 pieces of inventory each in the medical emergency medicine cabinet, surgical emergency medicine cabinet, obstetric emergency medicine cabinet, pediatric emergency medicine cabinet, ICU emergency medicine cabinet, and operating room emergency medicine cabinet (a total of 60 pieces).

[0240] 5. Directly send out from the upper-level library to the lower-level library sub-library instance

[0241] In hospital management, there is a situation where large infusions are generally stored as spare drugs in the ward nurse station. According to the consumption of each ward, the drug warehouse directly replenishes the ward nurse station. In this case, the principle of information flow is to first send the goods to the ward pharmacy, and then send the goods from the ward pharmacy to the spare warehouse of the ward nurse station. The following is an example of the large infusion warehouse directly replenishing 0.9% sodium chloride injection to the internal medicine spare medicine cabinet:

[0242] (1) The interface of the delivery order of the large infusion warehouse is as follows:

[0243] Henan Provincial Tenth People's Hospital Large Infusion Warehouse Outbound Order

[0244]

[0245]

[0246] (2) Internal Medicine Spare Medicine Cabinet Entry Form (no interface display, generated in the background)

[0247] Henan Provincial Tenth People's Hospital Internal Medicine Spare Medicine Cabinet Receipt

[0248]

[0249] The ward pharmacy general warehouse has the same entry order as the above table

[0250] (3) List of 0.9% Sodium Chloride Injection in the Large Infusion Bank (1-03_86901133000229100_Drug_list)

[0251] Drug inventory list for large infusion depot

[0252]

[0253] (4) Details of the 0.9% Sodium Chloride Injection in the Ward Pharmacy (2-01_86901133000229100_Drug_list)

[0254] Ward pharmacy drug inventory details

[0255]

[0256] (5) List of 0.9% Sodium Chloride Injection in the Internal Medicine Reserve Medicine Cabinet (3-014_86901133000229100_Drug_list)

[0257] Inventory details of medicines in the internal medicine cabinet

[0258]

[0259] Example 4: Adding a new medicine warehouse and adding a new medicine storage related data table to the medicine warehouse

[0260] The hospital has added a new ward, the ENT ward, and needs a spare medicine cabinet and an emergency medicine cabinet. It needs to first add information to the drug store code data table. The new information is as follows:

[0261]

[0262] Through the program, establish the drug inventory data table of the ENT department's spare medicine cabinet and the drug inventory data table of the ENT department's emergency medicine cabinet. The table names are 3-034_Inventory_data_table and 3-035_Inventory_data_table respectively. The data table structure is exactly the same as that of other drug inventory data tables.

[0263] When the drug warehouse or ward pharmacy issues drugs to the ENT spare medicine cabinet and the ENT emergency medicine cabinet, a drug inventory details table, incoming data table, outgoing data table, procurement plan data table, drug batch number expiration date data table, and drug traceability code data table are simultaneously established for the ENT spare medicine cabinet and the ENT emergency medicine cabinet. The data table structure is exactly the same as that of other drug warehouses, the only difference is that the drug warehouse codes in the prefix are 3-034 and 3-035 respectively.

[0264] Example 4: Application example of three-level management of narcotic drugs

[0265] The three-level management of narcotic drugs is essentially inventory management at different warehouse levels.

[0266] The first-level management of narcotic drugs is the management of narcotic drugs in the first-level warehouse of the hospital, that is, the first-level warehouse of narcotic drugs. According to the affiliation between narcotic drugs and the drug warehouse in the information system, it can be an independent narcotic drug warehouse (the drug warehouse level is 1); it can also be that narcotic drugs belong to the western medicine warehouse, and the information flow is managed in the same way as ordinary drugs (the drug warehouse level is 1); it can also be a sub-library of the western medicine warehouse (the drug warehouse level is 2, and the parent library is the western medicine warehouse). In the case of a sub-library of the western medicine warehouse, all data of each narcotic drug in the western medicine warehouse is exactly the same as all data of each narcotic drug corresponding to the sub-library. In general, the drug warehouse level of narcotic drugs is level 1.

[0267] The second level of management of narcotic drugs is the management distributed in each pharmacy, that is, the secondary warehouse / cabinet of narcotic drugs. According to the affiliation of narcotic drugs and pharmacy warehouses in the information system, it can be an independent secondary warehouse / cabinet of narcotic drugs (on the same level as the general warehouse of each pharmacy, the warehouse level is 2); or narcotic drugs can belong to each pharmacy, and the information flow is managed in the same way as ordinary drugs (the warehouse level is 2, and the upper warehouse is the general warehouse of each pharmacy).

[0268] The third-level management of narcotic drugs refers to the management of the cardinal cabinets of each pharmacy, the cardinal cabinets of each ward or the cardinal cabinet of the anesthesia department. Under normal circumstances, the narcotic drugs in the cardinal cabinet belong to the superior warehouse of the pharmacy in the information system; if the drug warehouse of the second-level management of narcotic drugs is an independent special warehouse (the drug warehouse level is 2), the cardinal cabinets of narcotic drugs in each pharmacy and ward are used as sub-warehouses of the second-level narcotic drug special warehouse / cabinet (the drug warehouse level is 3, the parent warehouse is the second-level special warehouse / cabinet for narcotic drugs, and the superior warehouse is the second-level special warehouse / cabinet general warehouse for narcotic drugs); if the narcotic drugs in the second-level management of narcotic drugs Narcotic drugs are managed in the same way as ordinary drugs (i.e., the drug warehouse level is 2, and the superior warehouse is the general warehouse of each pharmacy), and all cardinal cabinets serve as sub-warehouses of each pharmacy (the drug warehouse level is 3, the superior warehouse is the pharmacy that issues narcotic drugs, and the parent warehouse is the general warehouse of pharmacies that issue narcotic drugs); they can also be included in the management of the standby drug warehouse / cabinet of each ward (the drug warehouse level is 3, the parent warehouse is the pharmacy that issues narcotic drugs, and the superior warehouse is the general warehouse of pharmacies that issue narcotic drugs), but since the management plans of narcotic drugs are significantly different from those of ordinary drugs, they are generally not included in the management of the standby drug warehouse / cabinet of each ward.

[0269] The information processing methods for warehousing and out-of-warehouse, purchasing plan, and medical order out-of-warehouse in the three-level management of narcotic drugs are exactly the same as those for ordinary drugs.

[0270] Example 5: Creation and application of medical advice-related data tables

[0271] The medical order-related data tables in the hospital logistics system include the medical order status data table, the medical order execution data table, the medical order packaging table, the medical order tracing data table, and the medical order status basic table. The medical order execution data table is further divided into the secondary medical order table, the daily medical order table, and the multiple medical order table. The data in the medical order-related data tables in the hospital logistics system are completely derived from the medical order data tables or operation processes of the HIS system.

[0272] 1. Establishment of the doctor's order status data table

[0273] The medical order status data table uses the medical order ID as the primary key, and the fields include all fields related to the medical order and the medical order status, such as patient ID, medical order type, prescription ID, current hospitalization ID, medical order ID, medical order group number, drug ID, drug name, preparation specifications, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, course of treatment, total number of medical orders, notes, execution time, execution department, execution drug warehouse ID, cumulative number of executed medical orders, etc.

[0274] 2. Add, modify and update the data in the doctor's order status data table

[0275] After the doctor successfully issues a medical order, the HIS system assigns a unique medical order number / medical order ID to each medical order and saves all relevant contents of the medical order in the medical order status data table.

[0276] When the medical order status in the HIS changes, the medical order status in the medical order status data table changes synchronously, and other data remain unchanged. If there is no medical order status field in the medical order table of the HIS system, the medical order in the medical order status data table is assigned a value through HIS operation and the operation time is recorded. For example, when the medical order is issued, the medical order status is medical order issued; when the system review of the medical order is completed, the medical order status is system review; when the nurse review of the medical order is completed, the medical order status is transcription; when the pharmacist review is completed, the medical order status is pharmacist review; when the medical order fee recording / prescription payment operation is completed, the medical order status is billing; when the daily rolling medical order is completed, the medical order status is rolling medical order; when the doctor or nurse cancels the medical order, the medical order status is canceled; when the doctor stops the medical order, the medical order status is stopped.

[0277] The execution department and execution drug warehouse ID may be determined when the doctor prescribes / orders, or when the nurse transcribes, or may be determined or changed by the pharmacy, or determined during execution. When the execution department and execution drug warehouse ID are determined or changed at any stage, the execution department and execution department ID in the doctor's order status data table need to be changed in real time.

[0278] The following medical order status data can come from HIS or the in-hospital logistics system. HIS and the in-hospital logistics system can interoperate. When the preparation of medicines is completed, the medical order status is preparation; when the medical order dispensing is completed, the medical order status is dispensing. The medical order status not related to HIS can change the medical order status according to the operations in the in-hospital logistics system (including the operations not recorded by HIS in the above operations), such as labeling, medical order matching, warehousing, preparation, warehousing, sorting, single-dose placement, single-dose placement review, packaging, medical order drug delivery, medical order drug reception, etc. Regarding the return status of the medical order, there are two ways according to the different HIS design mechanisms. One is to return the medicine directly on the original medical order, and the other is to issue a new return medical order / prescription: If it is a newly issued return medical order / prescription, the medical order status data table records the newly added medicine order number, and the medical order status sequence includes: medical order issuance, nurse return, pharmacy return, refund; if the medical order quantity is changed directly on the original medical order (the quantity is changed to 0), the processing method is different according to the different status of the medical order at that time. If the medical order quantity is changed before deployment, the medical order status is changed to change the medical order; if the medical order quantity is changed after deployment, when the quantity in the medical order is reduced, the medical order status is recorded as change the medical order and doctor return the medicine in sequence; after the nurse reviews and confirms the medical order, the medical order status is nurse return; after the pharmacy confirms the return, the medical order status is pharmacy return; after the refund operation is completed, the medical order status is refund, and the further medical order status is stop.

[0279] 3. Create and write the doctor's order data table:

[0280] The fields of the execution medical order data table shall at least include: patient ID, medical order type, prescription ID, current hospitalization ID, ward ID, bed number, nursing unit ID, medical order ID, medical order group number, drug ID, drug name, preparation specifications, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, total number of medical orders, notes, estimated execution time, batch, medication time, and execution location (execution drug warehouse ID).

[0281] The medical order data in the prescription, temporary medical orders for inpatients, and medical orders for taking medicines after discharge are added to the medical order status data table after the doctor issues the medical order. At the same time, the relevant data is added to the execution medical order data table. The data operation process in the execution medical order data table is exactly the same as the actual operation, which is billing, allocation, verification, and dispensing of medicines, etc.

[0282] After the doctor issues a long-term medical order, the medical order data will be added to the medical order status data table. At the same time, the relevant data will be written into the execution medical order data table according to the number of executions on the first day filled in by the doctor. When the rolling medical order of the long-term medical order rolls over at the time set by the hospital, the relevant data of the long-term medical order will be added to the data in the execution medical order data table.

[0283] For the medical orders of intravenous preparation centers and single-dose medicine dispensers, according to the decision-making mechanism, after the medical orders are issued and when the medical orders are rolled over daily, the relevant data in the medical order status data table is split into multiple execution medical order data tables and written into the execution medical order data table.

[0284] 4. Execute the writing of data from the doctor's order data table to the inventory-related data table:

[0285] According to the hospital's configuration file, the order outbound data is written into the inventory-related data table while executing the order-related operations: configuration files such as writing after billing, writing during dispensing, and writing before scanning in the intravenous preparation center. The written content includes reducing the corresponding drug inventory data in the drug inventory data table by the same amount as the executed order (in preparation units), and synchronously changing other data in the same data (such as book quantity, physical quantity, book amount, etc.);

[0286] While writing data to the drug inventory data table, add one piece of data to the drug inventory details table, including: the business type is medical order outbound, the business order number is the medical order ID, and the business quantity is a negative value corresponding to the number of executed medical orders. The related data in the drug inventory details table, such as inventory quantity, amount, etc., are changed synchronously.

[0287] While writing data to the drug inventory data table, the outbound data is synchronously written to the batch number expiration date data table; if the operation of scanning the drug traceability code is involved in the execution of the medical order, the outbound data is synchronously written to the drug traceability data table.

[0288] Example 6: Purchase plan / drug replenishment plan application example

[0289] The average daily usage and the average daily usage frequency are configured as follows:

[0290]

[0291] The calculation formula for purchasing plan days is configured as follows

[0292]

[0293] 1. Calculation of average daily consumption, average daily usage frequency, and usage ranking rate

[0294] Take 86902865000013021 Azithromycin Capsules as an example

[0295]

[0296] Assuming that the total number of drugs with a usage frequency other than 0 in the library is 800, and Azithromycin Capsules is ranked 48th, its ranking rate is 48 / 800*100%=6%.

[0297] 2. Calculation of available inventory days, planned days, and planned quantity

[0298] If the inventory quantity is 4000 pills, the number of days the inventory can be used is 4000 / 2040.998=1.96 days

[0299] According to the table of 6% usage ranking rate of Azithromycin Capsules, the planned number of days for Azithromycin Capsules in the second and third layer warehouses is 7 days. The planned amount of supplementary medicine is 7*2040.998=14287 capsules=1191 boxes.

[0300] If an inventory upper limit (i.e., maximum inventory storage quantity) of azithromycin is set in the drug warehouse, such as 1200 boxes, the current inventory is 4000 tablets / 12=333 boxes, and the planned replenishment quantity is 1191 boxes>1200-333 boxes, then the planned purchase quantity is 1200-333=867 boxes.

[0301] 3. The minimum number of days that the lower-level warehouse can use the inventory and the medicine warehouse ID

[0302] When the available inventory days of azithromycin capsules in all drug depots are available, the available inventory days of each depot are compared to find the minimum available inventory days and the drug depot ID with the minimum available inventory days.

[0303] 4. Calculation of whether to purchase / replenish medicine:

[0304] If the next time to replenish the medicine for this warehouse is 3 days later (this date can be calculated by setting the day of the week or the day of the month for replenishing medicine for a specific medicine warehouse), it is obvious that azithromycin capsules need to be replenished. You can also calculate whether to purchase / replenish medicine by setting a lower limit for inventory. When the inventory quantity is less than the lower limit for inventory, you also need to purchase / replenish medicine.

[0305] 5. Calculate the actual purchase quantity / replenishment quantity according to the set minimum planned whole packaging quantity

[0306] If the number of a medium package of azithromycin is 10 boxes, the minimum planned whole package quantity is set to 10 boxes. According to the above-mentioned replenishment plan quantity of 1191 boxes, the actual planned quantity / replenishment quantity is 1190 boxes (the replenishment plan quantity with an inventory limit is 867 boxes, so the actual purchase quantity / replenishment quantity is 860 boxes).

[0307] Example 7: Application example of generating a QR code for a procurement plan

[0308] According to the hospital procurement plan generation rules, the generated procurement plan is as follows:

[0309] Henan Provincial Tenth People's Hospital Procurement Plan

[0310]

[0311] The QR code text generated according to the procurement plan QR code generation rules is as follows: https: / / www.kangdejian.cn:9889 / ? CGJH=(YY)41604590-741010523A5123(YP)8690188500041602(SL)100(YK)1-02(GYQY)91410100689728113F(YP)8690079600165901(SL)2000(YK)1-02(GYQY )91410100689728113F(YP)8690113300022910(SL)5000(YK)1-03(GYQY)91410 100689728113F(YP)8690113300025000(SL)12000(YK)1-03(GYQY)9141010068 9728113F(YP)8690286500001302(SL)3000(YK)1-02(GYQY)9141010068972811 3F(YP)8690243400073400(SL)1000(YK)1-02(GYQY)91410100689728113F(YP) 8690492000028001(SL)200(YK)1-02(GYQY)91410100689728113F(YP)8690492 000030301(SL)200(YK)1-01(GYQY)91410100796766860E(YP)(SL)(YK)1-01(GY QY)91410100796766860E(YP)8690389100129602(SL)100(YK)1-01(GYQY)9141010079 6766860E(YP)8690293600026301(SL)120(YK)1-01(GYQY)91410100796766860E(END)

[0312] Text description: 41604590-741010523A5123 is the code of the Tenth People's Hospital of Henan Province; 91410100689728113F is the code of China Resources Henan Pharmaceutical Co., Ltd.; 91410100796766860E is the code of Sinopharm Holdings Henan Co., Ltd.

[0313] After scanning with a mobile phone or an external network scanner, you will be redirected to the website https: / / www.kangdejian.cn:9889, where you can obtain the information in the table above through analysis. The name, website, email address, WeChat, and QQ of the drug supplier associated with the drug supplier ID stored on the website. The system automatically sends the procurement plan to the address specified by the relevant supplier through the website, email address, WeChat, or QQ.

[0314] Since the purchase plan is a 16-bit code with the original extension code, the drug supplier directly resolves the drugs in the inventory with the same 16-bit code as the original extension code into a 17-bit code. This can avoid the problem of inconsistent names caused by changes in product names and manufacturer names, resulting in inconsistencies between the purchase plan and the actual inventory and inability to deliver goods correctly. The 10% glucose injection, azithromycin capsules, and Wuji Baifeng pills (water honey pills) in the example have all changed the manufacturer's name. The products in the inventory of the drug supplier in the period before and after the manufacturer's name change may be inconsistent with the hospital's purchase plan, but the hospital can also distribute drugs that meet the requirements of the hospital's purchase plan (the purchase plan generated by the hospital before and after the change of the drug manufacturer's name uses a 16-bit code, and the purchase plan quantity will not be recalculated as a new drug due to the change of the manufacturer's name).

[0315] Example 8: Application example of QR code generation for goods

[0316]

[0317] The QR code text generated according to the invoice QR code generation rules is as follows: http: / / 1.192.218.142:9890 / ? FP=(GYQY)91410100689728113F(YY)41604590-741010523A5123(RQ)210915(YP)86901133000229101(SL)5000(DJ)2.30(PH)210809(XQ)230731(FPH)05289215( YKID)1-03(YP)86901133000250001(SL)12000(DJ)2.15(PH)210605(XQ)230531 (FPH)05289216(YKID)1-03(YP)86901885000416020(SL)100(DJ)3.20(PH)21062 3(XQ)230531(FPH)05289217(YKID)1-02(YP)86900796001659010(SL)2000(DJ) 198.00(PH)210715(XQ)230630(FPH)05289218(YKID)1-02(YP)869028650000130 21(SL)3000(DJ)12.00(PH)210424(XQ)230331(FPH)05289219(YKID)1-02(YP)8 6902434000734000(SL)1000(DJ)1.50(PH)210811(XQ)230731(FPH)05289220(YK ID)1-02(YP)86904311000165000(SL)500(DJ)0.98(PH)210406(XQ)230331(FPH)05289221(YKID)1-0 2(YP)86904920000280010(SL)200(DJ)20.40(PH)210125(XQ)221231(FPH)05289222(YKID)1-02(END)

[0318] After scanning with an intranet scanner, you will be redirected to the website http: / / 1.192.218.142:9890. Compare the number after (YY) with the hospital ID. If the comparison is correct, it means that the invoice is issued to this hospital. The drug supplier name associated with the drug supplier ID stored on the website is used to parse the drug name, specification, manufacturer, etc. according to the local extension code of each drug. Through the analysis, the information in the above table can be obtained (the amount is directly calculated using unit price * quantity, and the other information is the same as the above table after analysis.

[0319] The drug warehouse ID 1-03 belongs to the large infusion warehouse. When the large infusion warehouse enters the warehouse, the data of the Chinese medicine warehouse ID 1-03 after the parsed invoice is obtained and put into the warehouse entry interface. After verification with the actual object, it is directly entered into the warehouse; the drug warehouse ID 1-02 belongs to the western medicine warehouse. When the western medicine warehouse enters the warehouse, the data of the Chinese medicine warehouse ID 1-02 after the parsed invoice is obtained and put into the warehouse entry interface. After verification with the actual object, it is directly entered into the warehouse.

[0320] This specific embodiment is merely an explanation of the present invention and is not a limitation of the present invention. After reading this specification, those skilled in the art may make non-creative modifications to the present embodiment as needed. However, as long as they are within the scope of the claims of the present invention, they are protected by the patent law.

Claims

1. A processing method for an intra-hospital logistics information system based on unified drug coding, characterized by: The following steps are involved: S1. Build a unified drug coding knowledge base and a unified drug supply enterprise code base. The drug coding knowledge base and drug supply enterprise code base are completely consistent within the hospital and the supply enterprise / supply chain, and are updated synchronously; S2. The drug logistics in the hospital are all circulated between entities. The entity is defined as a warehouse or a person. Then, according to the cost of drug use, it is divided into a normal warehouse and a free warehouse. The free warehouse is used for donated drug management and GCP drug management. According to the conventional drug outbound direction, the drug outflow side is regarded as the upper warehouse, and the inflow side is regarded as the lower warehouse. According to the affiliation of the inventory drugs, the upper warehouse with affiliation is regarded as the parent warehouse, and the lower warehouse is regarded as the child warehouse. When there is drug circulation between entities, drug circulation and information circulation are carried out simultaneously. S3. Warehouse management in the in-hospital logistics system database adopts modular design; data tables are designed according to functions and application scenarios. The data tables with the same functions or the same application scenarios have exactly the same structure, and use the same main table name as the prefix or suffix of the table names of different drug warehouses and / or different drug data tables; the same application is used for the same function or the same application scenario, with the same interface operation template, printing template, and the same data storage mechanism; The same data tables involving the same type of drugs in the drug warehouses in the hospital and each drug warehouse should use the same main table name as a prefix or suffix, and add the drug warehouse ID and / or drug ID as a suffix or prefix in the data table name, and operate data tables with different names through system configuration files or parameter settings; the three-level management of narcotic drugs should be designed according to the warehouse management model; S4. When a drug supplier supplies drugs to a hospital, it prints an invoice QR code on the invoice or the package accompanying the goods, and automatically generates a warehouse entry after scanning the QR code on the hospital intranet; the procurement plan formulated by the hospital generates a procurement plan QR code on the hospital intranet, and directly distributes the procurement plan to different drug suppliers after scanning the procurement plan QR code on the external network; S5. The doctor's order management module in the hospital logistics system database is designed in a modular way, and is divided into a doctor's order status data table and an execution doctor's order data table according to the doctor's order usage function; There is only one data table for the medical order status data table, which is written after the doctor issues the medical order; the medical order execution data table is related to the drug warehouse associated with the medical order execution site. All medical order execution data tables have the same table structure, and the data table names contain the same main table name, and the drug warehouse ID associated with the execution site is used as the prefix or suffix of the main table name; S6. Visualized medical order tracing is realized through the medical order tracing data table associated with the medical order ID. In addition to being associated with the medical order status data table, the medical order tracing data table is also associated with the packaged medical order data table; S7. Determine the drug purchase plan or replenishment plan based on the average daily consumption of drugs in the drug warehouse, the frequency of use ranking rate, the number of days the remaining inventory can be used, the planned number of days, and the planned quantity, and generate the purchase plan or replenishment plan in combination with the upper and lower limits of the inventory; S8. The outbound data of the drug circulation in the hospital is based on the purchase plan data automatically generated by the subordinate warehouse, and the inbound data of the subordinate warehouse is derived from the outbound data of the superior warehouse. The inbound and outbound data can be completed by simply modifying the quantity in the aforementioned data. When the upper-level library issues goods across the layers, the parent / child libraries and the main library in the lower-level library will be simultaneously put into the library; when the medicine is issued, the main library will issue goods synchronously at the same time as the parent / child library issues goods; S9. Inventory management includes preparation specifications, packaging specifications, and quantities and unit prices related to preparation specifications or packaging specifications. Only one of the data between preparation specifications and packaging specifications needs to be entered, and the other data is directly calculated based on the conversion coefficient in the local extension code data; S10. Use the data in the hospital logistics system to collect statistics of various data and generate various reports; S11. When the drug coding knowledge base uses the drug standard extension code knowledge base, the drug coding in the information flow related to the physical flow of drugs shall use the standard extension code 17-digit code; the drug coding in the information flow related to the procurement plan and the replenishment plan shall use the standard extension code 16-digit code; The construction of the drug coding knowledge base and the drug supply enterprise code base in step S1 includes the following steps: S101. The drug coding knowledge base is a database composed of a series of data tables and associated programs; the drug coding database data table is used as the most basic data table in the drug coding knowledge base, and the fields of the drug coding database data table at least include drug code, drug name, preparation specification, preparation unit, packaging specification, packaging unit, conversion coefficient, and manufacturer; S102. The drug supply enterprise code library at least includes a drug enterprise code table. The fields of the enterprise code table at least include the enterprise name and enterprise code. The enterprise code table also includes the enterprise website, the purchase plan push website, the email address, the contact person, the contact person's QQ and WeChat. S103. The drug coding knowledge base and drug supplier code base are completely consistent within the hospital and at the supplier / supply chain end, and are updated synchronously; The configuration method of the drug warehouse type, hierarchy, affiliation and inventory transfer described in step S2 is: S201. According to the drug affiliation of the hospital drug warehouse, the drug warehouse affiliated to the hospital is the first level, and the drug warehouse of each pharmacy is the second level. If there is a sub-warehouse under the pharmacy, the pharmacy general warehouse is the second level, which belongs to the virtual warehouse, and the pharmacy physical warehouse is the third level; if the equipment in the pharmacy stores drugs and performs independent inventory management, the equipment warehouse in the pharmacy belongs to the third level; the spare drug warehouse / cabinet / equipment of each ward belongs to the third level warehouse, which is affiliated to the superior pharmacy general warehouse; if the hospital has branches and the branches also have drug warehouses, and the drugs are transferred from the headquarters drug warehouse, the branch drug warehouse belongs to the second level warehouse, the branch pharmacy general warehouse belongs to the third level warehouse, and the branch ward emergency medicine cabinet and spare drug warehouse / cabinet / equipment belong to the fourth level warehouse; and drug warehouses at all levels have unique IDs, and the drug warehouse type, drug warehouse level, and the ID of the superior warehouse with affiliation need to be added to the drug warehouse code data table before adding drug warehouses; S202, Drug in and out: When drugs are transferred between a superior warehouse and a subordinate warehouse that have no subordinate relationship and neither of the superior warehouse nor the subordinate warehouse has a sub-warehouse, the physical goods are transferred from the superior warehouse to the subordinate warehouse. During the information transfer, the superior warehouse performs outbound operations and the subordinate warehouse performs inbound operations. When drugs are transferred between a superior warehouse and a subordinate warehouse with a subordinate relationship, the physical goods are transferred from the parent warehouse to the sub-warehouse. When information is transferred, the parent warehouse is transferred and the sub-warehouse is transferred. There is no operation in the superior warehouse. When drugs are transferred between a superior warehouse and a subordinate warehouse that have no affiliation and the subordinate warehouse has a sub-warehouse, the physical goods are transferred from the superior warehouse to the parent warehouse or sub-warehouse of the subordinate warehouse. During the information transfer, the superior warehouse performs the outbound operation, and the subordinate warehouse enters the warehouse, and at the same time, the parent warehouse or sub-warehouse of the subordinate warehouse enters the warehouse; When drugs are transferred between a superior warehouse and a subordinate warehouse that have no affiliation and both superior and subordinate warehouses have sub-warehouses, the physical goods are transferred from the parent warehouse or sub-warehouse of the superior warehouse to the parent warehouse or sub-warehouse of the subordinate warehouse. During the information transfer, the general warehouse of the superior warehouse is out of stock, the parent warehouse or sub-warehouse is out of stock synchronously, and the general warehouse of the subordinate warehouse is in stock, and the parent warehouse or sub-warehouse of the subordinate warehouse is in stock at the same time; and the data of the information flow is synchronously written to the relevant data table; S203. Dispensing medicines according to doctor's orders: When a drug warehouse without a sub-warehouse dispenses medicines according to doctor's orders, the medicines are shipped out according to the doctor's orders and written into the relevant data tables of the corresponding drug warehouse and / or the medicines; when a drug warehouse with a sub-warehouse dispenses medicines, the parent warehouse or the sub-warehouse and the main warehouse synchronously record the shipment of medicines according to the doctor's orders and write them into the relevant data tables of the parent warehouse / sub-warehouse and the main warehouse of the relevant drug warehouse.

2. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The contents of the relevant data tables of warehouse management in step S3 include: S301, the warehouse management module consists of a series of data tables and application interface templates, and printing templates. The data tables are designed according to functions and application scenarios. The necessary data tables include inventory data tables, drug inventory details tables, outbound data tables, inbound data tables, purchase plan data tables, batch expiration date data tables, and traceability code data tables, and they are used for inventory query, inventory details query, inventory inventory, purchase plan setting, purchase plan formulation, outbound, inbound, batch expiration date query, traceability code query, prescription / doctor's order dispensing, generation of various reports, and doctor's order issuance; Application interface templates and printing templates include inventory query, inventory table, inventory gains, inventory losses, purchase plan, inventory upper and lower limit settings, inventory details query, outbound, inbound, return, borrow and return medicines, loss report, query of near-expiry and expired medicines, query of batch number and expiration date, query of unsalable medicines, prescription dispensing, doctor's order dispensing, traceability code query, and system configuration files; S302. The data table names in the warehouse management module are related to the drug warehouse ID and the drug ID: each type of data table has the same main table name, and the drug warehouse ID and / or drug ID are added as prefixes to generate the data table name of the drug warehouse or the drug. Among them, the inventory data table, the outbound data table, the inbound data table, and the purchase plan data table are only related to the drug warehouse ID, and the data table name combination method adopts "drug warehouse ID+main table name" or "main table name+drug warehouse ID"; the drug inventory details table, the batch number expiration date data table, and the traceability code data table are related to the drug warehouse ID and the drug ID, and the data table name combination method adopts "drug warehouse ID+drug ID+main table name" or "main table name+drug warehouse ID+drug ID", and the drug ID uses the unified drug code; S303, the interface operation template and the printing template display menus according to personnel authority, and open the interface operation template through the menu; the acquisition of interface data obtains the drug warehouse ID and drug ID according to the content in the interface, and then opens, filters and obtains the data in the corresponding data table name; when the data in the interface operation template needs to be saved, the drug warehouse ID and drug ID are obtained according to the content in the interface, and when saving, the saved content is written into a data table with a different name according to the drug warehouse ID and drug ID; S304. When a new drug store is added to the hospital, the drug store name and drug store ID are first added to the drug store code management, and each data table associated with the drug store ID is automatically copied and added according to the template; The method for adding a new drug-related data table in a specific drug warehouse is as follows: when a specific drug warehouse has a storage operation, the drug ID in the drug inventory data table of the corresponding drug warehouse ID is detected, and if not found, after obtaining the new drug ID, the data table related to the drug ID of the drug warehouse is copied and added for the drug warehouse; S305. The three-level management of narcotic drugs is designed according to the warehouse management module, that is, different drug warehouse IDs, drug warehouse levels, upper drug warehouses, and parent-child warehouses are assigned to drugs in the management of narcotic drugs at all levels, and the information flow and information processing method are exactly the same as those of ordinary drugs; S306. The warehouse management module also includes a donated drug warehouse and a GCP drug warehouse according to the needs of the hospital. The data tables and interfaces therein have the same data table structure as other general warehouse management modules, and the table name of the data table needs to be prefixed with a "no charge" code, and the drug ID in the data table needs to be prefixed with a "no charge" code, and the basic attribute information of the drug is the same as the original drug ID; the relevant procedures for donated drugs and GCP drugs do not involve the unit price and amount of the drugs, or the unit price and retail amount are both zero.

3. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The generation of the invoice QR code and the purchase plan QR code and the internal and external network data analysis described in step S4 include the following steps: S401. Elements of the invoice QR code include: hospital resolution website IP address, invoice QR code identifier, supplier enterprise code, hospital code, invoice date, drug code, quantity, unit price, batch number, expiration date, invoice number, drug store code, to-be-continued identifier or end identifier. The above data is used to generate the invoice QR code through QR code generation software, and printed on the invoice or the accompanying bill, or sent to the mobile phone of the relevant personnel, or downloaded and displayed on the website by the relevant personnel; drug code, quantity, unit price, batch number, expiration date, invoice number, drug store code are entered in a circular manner; S402, parsing of the invoice QR code in the hospital intranet: use the QR code scanner in the hospital intranet to scan the invoice QR code, and find the address of the invoice parsing program stored in the intranet through the IP address of the hospital parsing website in the QR code. The invoice QR code identifier is a parsing program. First, the hospital code is parsed to see if it is consistent with the stored hospital code. If not, parsing is not possible. If consistent, all data is parsed into the invoice data table according to the parsing program. Among them, the supplier code is parsed into the supplier name using the supplier table in the system, and the drug code is parsed into the drug name, manufacturer, and packaging specification data fields according to the drug code library data table; the drug name and manufacturer can also be parsed into the hospital drug name and the hospital manufacturer name according to the hospital settings; after the parsing is completed, the data in the invoice data table is parsed into the drug storage data table; S403, Generation of entry order: When the hospital drug warehouse is operating, if the corresponding drug warehouse has unentered data, it will prompt that the operation needs to be performed, and directly fill in all the data of the entry order into the entry interface. After confirmation, the entry operation is completed, and the entry mark in the entry data table is changed to "yes" ; S404, generation of procurement plan QR code: the procurement plan is generated by the program according to the procurement plan or the replenishment plan. The drug warehouse purchaser adjusts the procurement plan in the interface, and generates a procurement plan QR code after the adjustment. The procurement plan QR code includes: QR code parsing IP address, procurement plan identifier, hospital code, drug code, quantity, drug warehouse code, supplier enterprise code, to-be-continued identifier or end identifier. The procurement plan QR code is generated by the QR code generation software; the drug code and quantity can be entered cyclically; S405. Parsing of the procurement plan QR code on the external network: Scan the procurement plan QR code using a mobile phone APP or a QR code scanner on the hospital's external network, and find the address of the procurement plan parsing program stored in the external network through the IP address in the procurement plan QR code. The procurement plan identifier is a parsing program that parses all data into the procurement plan data table in the parsing order, wherein the hospital code is parsed from the hospital name using the hospital information table stored on the website, the drug code is parsed into the data fields of drug name, manufacturer, and packaging specifications based on the drug code library data table, and the supplier code is parsed into the drug supplier name, website, email address, WeChat, QQ using the supplier table stored on the website; the system automatically sends the procurement plan to the address specified by the relevant supplier via the website, email address, WeChat, or QQ.

4. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The doctor's order management module described in step S5 is implemented by the following steps: S501. In addition to the necessary information of the medical order, the medical order status data table also contains the medical order status, that is, the real-time data of the link of the medical order; the medical order status data table uses the medical order ID as the primary key, and its fields include all the fields related to the medical order and the medical order status. The fields related to the medical order include patient ID, medical order type, prescription ID, current hospitalization ID, ward ID, bed number, nursing unit ID, medical order ID, medical order group number, drug ID, drug name, preparation specification, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, total amount of medical order, and remarks; if the medical order status is included in the HIS, it is obtained through the interface or the hospital information platform message transmission method; if the medical order status is not included in the HIS, the medical order status is written into the SPD system through the specific operation of the HIS system; the writing of the drug warehouse outbound data table is determined according to the medical order status set by the system; S502, the medical order status in the medical order status data table is set and adjusted by the hospital according to the hospital management plan and process, and is stored in advance in the medical order status basic table; the fields of the medical order status basic table at least include the primary key, medical order status name, execution location, execution location code, associated drug store, associated drug store code, and whether it is effective; S503, the doctor's order execution data table adopts a modular design, and all doctor's order execution data tables have the same table structure and the same execution program, but different data table names; All the executed medical order data table names contain the same main table name, and the execution location associated drug library code is used as the prefix or suffix of the main table name; the fields of the executed medical order data table include at least: patient ID, medical order type, prescription ID, current hospitalization ID, ward ID, bed number, nursing unit ID, medical order ID, medical order group number, drug ID, drug name, preparation specification, drug origin, single dosage, dosage unit, usage, dosage, number of times per day, total amount of medical orders, remarks, medication time, batch, execution time, execution location, execution location code, and execution result; S504: The execution doctor's order data table is written according to the contents of the doctor's order status data table. The name of the data table to be written needs to be consistent with the drug store code associated with the execution location. The timing and contents of data writing are related to the doctor's order type and / or execution location. Medical orders that are executed only once include outpatient and emergency prescriptions, temporary inpatient orders, and orders to take medicines when discharged. The timing of writing the execution order data table is determined by the hospital configuration file; The medical orders executed daily are long-term medical orders for inpatients. Through the rolling medical order process of HIS, the relevant data is written into the execution medical order data table at a fixed time every day; The medical orders that are executed multiple times every day include those executed by the intravenous preparation center and the single-dose dispensing machine. The relevant medical orders are written into the execution medical order data table according to the decision-making mechanism at a fixed time every day; S505, writing of data from other data tables in the doctor's order data table: when a specific operation is performed on the doctor's order, the doctor's order status in the doctor's order status data table changes synchronously, including: billing, dispensing, checking, dispensing, labeling, matching, warehousing, preparation, warehousing, sorting, packaging, single-dose placement, and single-dose checking; When executing a specific operation on the execution of a doctor's order, the drug inventory data table, drug inventory detail data table, batch number expiration date data table, and traceability code data table corresponding to the drug warehouse ID and / or drug ID of the execution site are synchronously written into the doctor's order outbound data, and the outbound timing is associated with the doctor's order status through the hospital configuration file; Writing the cumulative quantity of executed medical orders in the medical order status data table: while writing the outbound data to the inventory-related data table, add the outbound quantity of this executed medical order to the cumulative quantity of executed medical orders in the medical order status data table and record it in the cumulative quantity of executed medical orders.

5. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The visualized medical order tracing described in step S6 is implemented by the following steps: S601. The key data table used by the medical order tracing module is used as the medical order tracing data table, and its fields include at least patient ID, prescription number, medical order number, medical order status, operation time, and medical order package ID. The medical order status in the medical order tracing data table is synchronized with the real-time medical order status in the medical order status data table. When a medical order ID changes the medical order status in the medical order status data table, a piece of data is added to the tracing medical order table, and the time when the medical order status changes is recorded as the operation time. If the medical order is packaged, the medical order package ID is recorded synchronously; S602. Display the location of each medical order / drug in a table or graphic form according to the location of the medical order ID, or check the location of each patient's drug according to the patient information associated with the medical order ID.

6. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The method for generating the purchase plan or the medicine replenishment plan described in step S7 is: S7 0 1. Generation of purchase plan / drug replenishment plan: The fields in the inventory data table displayed in the interface are: drug code, drug name, simple packaging specification, planned quantity per packaging unit, number of days physical inventory can be used, planned number of days, simple preparation specification, planned quantity per preparation unit, planned quantity, planned quantity unit, whether to purchase, and manufacturer; The planned quantity per packaging unit, the planned quantity per preparation unit, and the planned quantity are automatically adjusted after the planned days are modified. The planned quantity is calculated by converting the planned quantity per packaging unit into multiples of the minimum planned whole packaging quantity and rounding it off. Whether to purchase is adjusted in the interface; The procurement plan seen by the superior library and the generation of the hospital plan QR code are displayed or generated according to the above data requirements.

7. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The automatic generation of the inbound and outbound data described in step S8 includes the following steps: S801. After the subordinate drug warehouse generates a replenishment plan, the superior warehouse automatically obtains the drug name, specification, and quantity information in the replenishment plan of the subordinate warehouse on the outbound interface, fills it in the outbound interface, and directly saves and prints the outbound order. In addition, the interface allows operations such as adding drugs, deleting drugs, and modifying outbound quantities to generate an outbound order, which is saved and printed for physical outbound delivery. The useful contents in the outbound order also include viewing or printing the drug's warehouse location code, the inventory quantity of the current warehouse, the inventory quantity of the subordinate warehouse, and the number of days the inventory of the subordinate warehouse can be used; S802. When the upper warehouse issues the drugs, the lower warehouse can synchronously receive the information of the drugs issued by the upper warehouse and generate the entry order of the lower warehouse to be displayed on the interface; the lower warehouse confirms the acceptance of all the entry orders on the interface, or completes the entry of some drugs by deleting a drug in the entry order or modifying the entry quantity; S803. When some drugs are put into the lower-level warehouse, a return order is generated in the upper-level warehouse at the same time. The return quantity is the difference between the outgoing quantity of this warehouse and the received quantity of the lower-level warehouse. The return is completed after confirmation in the interface. S804: When the upper-level warehouse directly issues goods to the parent warehouse or child warehouse of the lower-level warehouse, an issue order for the upper-level warehouse to issue goods to the lower-level general warehouse and an issue order for the upper-level warehouse to issue goods to the parent warehouse or child warehouse of the lower-level warehouse are generated at the same time; when the lower-level warehouse does not fully receive goods, the upper-level warehouse has a return order, but the lower-level warehouse has no return order.

8. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The steps for implementing the quantity and unit price related to the preparation specifications and packaging specifications described in step S9 are: S901. If the quantity obtained in the inventory management is the quantity and price of the preparation unit, the quantity in the packaging unit = the quantity in the preparation unit / conversion factor, and the unit price of the packaging unit = the unit price of the preparation unit * conversion factor; If the quantity obtained in inventory management is the quantity and price of packaging units, the quantity in preparation units = the quantity in packaging units * conversion coefficient, and the unit price of preparation units = unit price of packaging units / conversion coefficient; among which, the conversion coefficient comes from the drug coding library data table, or is obtained from the hospital drug basic information table generated based on the drug coding library data table.

9. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The steps of performing statistics of various data and generating various reports in step S10 include: S1001. Query and print the detailed list of each drug in each drug warehouse: After inputting the drug warehouse name and drug name, obtain the drug warehouse ID and drug ID respectively, and combine them with the prefix / suffix of the drug inventory detailed list to find the data table name. Through conditional screening, you can view the detailed data of each drug in a specific drug warehouse within a certain period of time; S1002. Query and print the inventory table of each drug warehouse: After inputting the drug warehouse name, obtain the drug warehouse ID, and combine it with the inventory data table prefix / suffix to find the data table name, and directly view or print the real-time inventory data of the corresponding drug warehouse; if the total warehouse inventory table is required, directly open the designated total warehouse inventory data table to view the summary data of the inventory data of each sub-warehouse; S1003. Query and print hospital purchase data: directly filter all drug storage data tables at the drug store level 1 and summarize the data of the specified date into a temporary table to display the purchase data of the entire hospital; if the purchase data of a certain type of drug is specified, the purchase data of this type of drug is displayed by entering the drug attributes; if the purchase data of a certain drug store is specified, the purchase data of the drug store name is displayed by entering the drug store name; S1004. Drug sales data query and printing: open each outbound data table of the drug warehouse level 2, filter all outbound data of the specified time period and the business type of medical order outbound and summarize them into a temporary table, enter the viewing conditions in the interface to filter in the temporary table, and summarize and display the total sales quantity or total amount of each drug under various conditions, or filter the total sales quantity or total amount of a certain type of drugs by the attributes associated with each drug, or the quantity converted by attribute data; S1005. Query of unsaleable drugs: Open the inventory data table of the designated drug warehouse, sort the usage rate from low to high to display the sorting rate of each drug, and find the unsaleable drugs in the designated warehouse through the remaining inventory usable days, the minimum inventory usable days and the minimum inventory usable days drug warehouse ID, or the drug name and inventory usable days of the unsaleable drugs in all subordinate warehouses.

10. The processing method of the hospital logistics information system based on unified drug coding according to claim 1 is characterized by: The steps of using the drug-based extended code as the unified drug code in step S11 include: S1101. Use the 16-digit drug-based extended code as the purchase plan data. When the drug name and / or the manufacturer name and / or the approval number are changed, the quantities before and after the change are combined in the statistical purchase quantity. The uploaded purchase plan or replenishment plan is converted into a delivery note for supply based on the inventory status of the drug supplier / superior warehouse.

Images