Method and system for tracing information of unloaded medicine and electronic equipment
By generating the subsequence code corresponding to each zero-deletion drug and storing it in association with patient information, the problem of traceability of zero-deletion drug information is solved, and the accurate traceability and legal circulation of zero-deletion drugs are realized.
Patent Information
- Application Number
- CN202510550015.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-28
- Publication Date
- 2025-08-22
AI Technical Summary
The existing technology lacks information traceability methods for removing the cut-off drugs, and it is impossible to realize that the source, whereabouts, and responsibilities of the cut-off drugs can be traced.
Based on the drug packaging traceability code of the target drug, a sub-sequence code corresponding to each cut-off drug is generated, and the quantity value of the required sales is determined through the drug sales information, the sub-sequence code is cancelled and stored in association with the patient information, so as to realize the information traceability of the cut-off drug.
Accurate traceability of information of the cut-off drugs is realized, ensuring that each cut-off drug has a sub-sequence code for traceability, supporting drug effect tracking and problematic drug recall, and preventing excessive sales and illegal circulation of drugs.
Smart Images

Figure CN120525547A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of drug management, and in particular relates to an information tracing method, system and electronic equipment for disassembled drugs. Background Art
[0002] Drug traceability refers to the tracing of the source and flow of drugs, enabling the verification of their origin, traceability of their destination, and accountability. Current drug traceability systems are primarily designed for packaged drugs, relying on identifiers such as barcodes or QR codes to establish a "one drug, one code" traceability chain, effectively overseeing the entire process of packaged drugs, from production and distribution to end-use. For smaller-volume drugs sold outside of larger packages, existing research has primarily focused on the development and optimization of automated packaging equipment or pill packaging machines for these smaller-volume drugs, but lacks information traceability methods for these smaller-volume drugs. Summary of the Invention
[0003] The embodiments of the present application provide a method, system, and electronic device for tracing information of retail medicines to solve the problem of the lack of an information tracing method for retail medicines in the prior art.
[0004] A first aspect of an embodiment of the present application provides a method for tracing information of retail medicines, comprising:
[0005] Based on the drug packaging traceability code of the target drug, generating a subsequence code corresponding to each of the split-up drugs according to the first quantity value of the split-up drugs in the target drug;
[0006] Obtain patient information and drug sales information;
[0007] Based on the drug sales information, a second quantity value of the retail drug required for sale is determined, the subsequence code of the second quantity value is written off, and the written-off subsequence code is associated with the patient information and stored.
[0008] A second aspect of the embodiments of the present application provides an information traceability system for retail medicines, including:
[0009] a generating module configured to generate, based on the drug packaging traceability code of the target drug and in accordance with the first quantity value of the split-up drugs in the target drug, a subsequence code corresponding to each of the split-up drugs;
[0010] Acquisition module, used to obtain patient information and drug sales information;
[0011] A verification module is used to determine the second quantity value of the retail medicine required to be sold based on the medicine sales information, verify the second quantity value of the subsequence code, and associate the verified subsequence code with the patient information for storage.
[0012] A third aspect of an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in the first aspect when executing the computer program.
[0013] A fourth aspect of an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the method described in the first aspect.
[0014] A fifth aspect of an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.
[0015] As can be seen from the above, this application generates a subsequence code corresponding to each split-up drug based on the drug packaging traceability code of the target drug and the first quantity value of the split-up drugs in the target drug, ensuring that each split-up drug corresponds to a subsequence code for traceability. Obtain patient information and drug sales information, determine the second quantity value of the split-up drugs to be sold based on the drug sales information, cancel the subsequence code of the second quantity value, and store the cancelled subsequence code in association with the patient information. In this way, based on the generated subsequence code related to the drug packaging traceability code, the association and binding of patient information and split-up drugs can be achieved, which is convenient for tracing, thereby solving the problem of the lack of information tracing methods for split-up drugs in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0017] Figure 1 This is the process of an information tracing method for disassembled medicines provided in the embodiment of the present application. Figure 1 ;
[0018] Figure 2 This is the process of an information tracing method for disassembled medicines provided in the embodiment of the present application. Figure 2 ;
[0019] Figure 3 This is a structural diagram of an information traceability system for retail medicines provided in an embodiment of the present application;
[0020] Figure 4 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0021] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.
[0022] It will be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.
[0023] It should also be understood that the terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit the present application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.
[0024] It should be further understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
[0025] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.
[0026] In specific implementations, the terminals described in the embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).
[0027] In the following discussion, a terminal including a display and a touch-sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.
[0028] The terminal supports various applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk burning application, a spreadsheet application, a game application, a phone application, a video conferencing application, an email application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.
[0029] Various applications that can be executed on the terminal can use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal can be adjusted and / or changed between applications and / or within a corresponding application. In this way, the common physical architecture of the terminal (e.g., the touch-sensitive surface) can support a variety of applications with user interfaces that are intuitive and transparent to the user.
[0030] It should be understood that the size of the serial numbers of each step in this embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of this application.
[0031] In order to illustrate the technical solution described in this application, specific embodiments are provided below.
[0032] See also Figure 1 , Figure 1 This is the process of an information tracing method for disassembled medicines provided in the embodiment of the present application. Figure 1 .like Figure 1 As shown, a method for tracing information of retail medicines includes the following steps:
[0033] Step 101: Based on the drug packaging traceability code of the target drug and in accordance with the first quantity value of the split-up drugs in the target drug, a subsequence code corresponding to each of the split-up drugs is generated.
[0034] Target drugs are drugs that can be sold in their smallest independent units, also known as drugs that can be sold in retail. Target drugs include solid dosage forms, liquid dosage forms, and specialty dosage forms.
[0035] Solid dosage forms can be sold in bulk, including bottled / bagged / boxed tablets and bottled / bagged / boxed capsules. Tablets in bottles, such as enteric-coated aspirin tablets in bottles, are sold as individual tablets. Capsules, such as enteric-coated omeprazole capsules in boxes, are sold as individual capsules.
[0036] Liquid dosage forms include oral liquids and injection ampoules. For example, oral liquids, such as boxed zinc gluconate oral solution, are sold as individual bottles. For injection ampoules, such as boxed vitamin C injection, are sold as individual ampoules.
[0037] Special dosage forms can be sold in small packages, such as granules. Granules can be sold in small packages, such as bagged Isatis Root Granules, which are split into single-dose bags for sale.
[0038] Correspondingly, the smallest independent sales unit refers to the disassembled unit of the drug, such as a pill, a capsule, a tube of oral solution, a tube of injection, etc. The traceability granularity will be refined from "box level" and "bottle level" to "granule level" and "tube level".
[0039] The retail sales of targeted drugs are used in hospital outpatient clinics, hospital inpatients, and pharmacy retail. For example, for inpatients, whole packages of drugs are sold in retail units, divided into single or daily doses; for outpatients undergoing short-term treatment, whole packages of drugs are sold in retail units, divided by treatment course. Dispensing and selling medications based on individualized needs reduces drug waste and ensures accurate medication use, avoiding the risk of leftovers or misuse caused by patients purchasing whole packages, ensuring safe dosage, and reducing waste.
[0040] The drug packaging traceability code refers to a unique structured code printed on the target drug packaging, which contains data segments such as manufacturer code, production batch, drug date and unique serial number, and enables traceability of the entire package of target drugs when the target drugs are sold in the form of whole packages.
[0041] The first quantity value of a retail drug is the maximum quantity that can be sold as the smallest individual sales unit (the retail unit). Specifically, the first quantity value is equal to the total quantity of retail drugs in the package before the retail drug is retailed. For example, if a bottle of medicine contains 30 capsules and can be retailed as 30 capsules, the first quantity value is 30.
[0042] A subsequence code is generated based on the target drug's packaging traceability code. This subsequence code retains the characteristic information of the target drug's packaging traceability code, allowing the retail drug to be associated with the target drug. The quantity value of the generated subsequence code is equal to the first quantity value of the retail drug in the target drug. This ensures that when selling based on the smallest independent sales unit, each retail drug has a corresponding subsequence code for traceability, facilitating traceability management of retail drugs based on subsequence codes.
[0043] In some embodiments, the drug packaging traceability code based on the target drug generates a subsequence code corresponding to each of the split-up drugs according to the first quantity value of the split-up drugs in the target drug, including: generating the first quantity value of the split-up identifier according to the first quantity value of the split-up drugs in the target drug; and combining each of the split-up identifiers corresponding to the same set position of the drug packaging traceability code with the drug packaging traceability code to obtain the first quantity value of the subsequence code.
[0044] Generate equal-quantity split identifiers based on the total number of split-unit drugs in the target drug, ensuring that each split-unit drug has a corresponding split identifier. The split identifiers are then inserted into the designated locations of the target drug's packaging traceability code, maintaining consistent coding rules and ensuring that each split-unit drug has a corresponding subsequence code for traceability.
[0045] A repack identifier is a unique identifier generated for each repack drug. It is used to distinguish different repack drugs of the same target drug, ensuring that each repack drug can be independently traced during circulation and use. Repack identifiers are generated through regularized coding, such as ascending serial number coding.
[0046] In some embodiments, the zero-order identifiers are typically generated using numbers, a combination of numbers and letters, or a combination of numbers, letters, and symbols. For example, if the first quantity value of the zero-order drugs in the target drug is 30, the generated zero-order identifiers are 01, 02, 03, 04, ..., 29, 30. For another example, if the first quantity value of the zero-order drugs in the target drug is 10, the generated zero-order identifiers are C1, C2, ..., C10.
[0047] The subsequence code is a traceability code for a drug that has been broken down into smaller quantities, generated by combining the target drug's packaging traceability code with a smaller quantity identifier according to a rule. Each generated smaller quantity identifier is inserted into the designated position of the target drug's packaging traceability code to produce a first number of corresponding subsequence codes.
[0048] The set position is the position before all data segments or after all data segments of the drug packaging traceability code. Presetting the set position avoids data confusion caused by random identifier positions and ensures a unified subsequence code generation rule for easy parsing and identification.
[0049] In some embodiments, the drug packaging traceability code of the target drug is 1234567-1234567890000, and the setting position is the position after all data segments of the drug packaging traceability code. The first quantity value of the target drug is 30, and the generated fragment identifiers are 01, 02, 03, 04, ..., 29, 30, corresponding to the generation of 30 subsequence codes from 1234567-1234567890000-01 to 1234567-1234567890000-30.
[0050] The subsequence code is linked to the target drug's packaging traceability code, inheriting the drug attribute information from the packaging traceability code. This information includes manufacturer, batch, production date, expiration date, and instructions. Subsequence codes enable the source of retail drugs to be traced.
[0051] In some embodiments, the subsequence code is also associated with information such as the date the drug was split into smaller pieces, information about the staff who performed the splitting operation, etc., to achieve multi-dimensional information traceability.
[0052] In some embodiments, staff members pre-scan the target drug's packaging traceability code using a drug traceability code scanning terminal. Based on the packaging traceability code, the backend identifies the drug as a removable unit. A removable unit reminder interface is displayed via the terminal device, and staff members confirm whether to proceed with the removable unit operation based on the interface. If they confirm, a subsequence code is automatically generated based on the scanned packaging traceability code and coding rules. This manual confirmation prevents accidental removable units, ensures compliance with removable units, and enhances the rigor of removable units.
[0053] In some embodiments, staff members pre-scan the target drug's packaging traceability code using a drug traceability code scanning terminal. Based on this code, the backend automatically generates a subsequence code based on the scanned packaging traceability code and coding rules. This bypasses the manual confirmation step, enabling rapid response and processing of the split-unit operation and improving generation efficiency.
[0054] Step 102: Obtain patient information and drug sales information.
[0055] A patient is an individual who uses medications through distribution channels such as medical institutions or pharmacies. Patient information refers to the identity, medication records, department affiliation, and health data associated with the individual during the drug sales and traceability process.
[0056] Drug sales information includes the name, specifications, manufacturer, sales quantity and other information of the drugs to be sold.
[0057] Obtain patient information and drug sales information to facilitate subsequent drug write-offs and information association.
[0058] Step 103: Based on the drug sales information, determine the second quantity value of the retail drug required for sale, write off the subsequence code of the second quantity value, and associate the written-off subsequence code with the patient information for storage.
[0059] The quantity corresponding to the retail drugs in the drug sales information is the second quantity value required to sell the retail drugs.
[0060] Each sub-sequence code is only allowed to be redeemed once, corresponding to the second quantity value of the sub-sequence code to be redeemed, eliminating the risk of the same split unit being sold multiple times and preventing over-sales.
[0061] The verified subsequence code is stored in association with the patient information, making it easy to accurately trace the information from the split-up drugs to the patient based on the subsequence code, so that the whereabouts of the split-up drugs can be traced, and supporting the tracking of medication effects and the recall of problematic drugs.
[0062] In some embodiments, determining the second quantity value of the retail drugs required for sale based on the drug sales information and writing off the subsequence code for the second quantity value includes: performing a sales compliance check based on the regional verification parameters of the sales terminal that submitted the patient information and the drug sales information; and writing off the subsequence code for the second quantity value if the regional verification parameters are compliant.
[0063] A sales terminal refers to a terminal device, such as a computer or tablet, that submits patient information and drug sales information to apply for the sale of retail drugs.
[0064] Regional verification parameters are used to verify the compliance of retail drug sales. These parameters include the organization identifier of the sales organization to which the sales terminal belongs and the regional location of the sales terminal. The organization identifier refers to a legal code issued by drug regulatory authorities or industrial and commercial administration agencies that uniquely identifies a drug distribution organization (such as a hospital, pharmacy, or community health service center). These codes may include the drug distribution license number, unified social credit code, or medical institution practice license number.
[0065] Sales compliance is verified based on the regional verification parameters of the sales terminal. If the regional verification parameters are in compliance, namely the institution identifier and regional location are in compliance, the corresponding number of subsequence codes are redeemed, indicating the corresponding number of small-lot drugs sold. This not only prevents non-compliant small-lot drug redemption operations, but also clearly identifies the sales institution responsible for selling small-lot drugs, ensuring accountability.
[0066] In some embodiments, the sales compliance check based on the regional verification parameters of the sales terminal that submits the patient information and the drug sales information includes: obtaining the regional verification parameters of the sales terminal that submits the patient information and the drug sales information; checking whether the institution identifier in the regional verification parameters belongs to the pre-authorized institution identifier, and whether the regional location in the regional verification parameters belongs to the pre-authorized regional location; if the institution identifier belongs to the pre-authorized institution identifier and the regional location belongs to the pre-authorized regional location, determining that the regional verification parameters are compliant; if the institution identifier does not belong to the pre-authorized institution identifier and / or the regional location does not belong to the pre-authorized regional location, determining that the regional verification parameters are non-compliant.
[0067] In some embodiments, sales agencies that are allowed to sell target drugs are registered in advance, and the agency identifiers, regional locations, and terminal device identifiers of the corresponding sales terminals of these sales agencies are registered. The registered agency identifier is the pre-authorized agency identifier, and the registered regional location is the pre-authorized regional location. The agency identifier, actual regional location, and terminal device identifier of each sales agency are associated with each other. The terminal device identifier of the sales terminal is device identification information such as the device serial number or the Media Access Control Address (MAC address).
[0068] Obtain the terminal device identifier of the sales terminal that submitted the patient information and drug sales information, determine the sales organization to which the sales terminal belongs based on the terminal device identifier, and then obtain the organization identifier of the sales organization. At the same time, determine the current regional location of the sales terminal based on the positioning device of the sales terminal.
[0069] The obtained sales terminal's organization identifier is compared with the pre-authorized organization identifier to determine whether the organization identifier is a pre-authorized organization identifier. At the same time, the sales terminal's current regional location is compared with the actual regional location of the sales organization to which it belongs. If they match, the sales terminal's current regional location is compared with the pre-authorized regional location to determine whether the regional location is a pre-authorized regional location.
[0070] If the institution identifier is a pre-authorized institution identifier and the regional location is a pre-authorized regional location, the regional verification parameters are confirmed to be compliant, and the resale of the retail drug can be performed on the sales terminal. The institution identifier and regional location must meet the pre-authorized institution identifier and pre-authorized regional location that have been registered with the same sales institution, respectively.
[0071] If the institution identifier does not belong to the pre-authorized institution identifier and / or the regional location does not belong to the pre-authorized regional location, it is determined that the regional verification parameters are not compliant, that is, the verification operation of the retail medicine cannot be performed at the sales terminal.
[0072] Multi-dimensional verification is performed through regional verification parameters to ensure the legality of sales and prevent illegal circulation of drugs.
[0073] In some embodiments, if regional verification parameters are determined to be non-compliant, the write-off operation for the retail drug will be intercepted, and a pop-up window will be displayed to notify the staff of the abnormality in the write-off operation. The abnormality determination information will be provided, such as the institution identifier does not match the pre-authorized institution identifier, or the regional location does not match the pre-authorized regional location, or the institution identifier does not match the pre-authorized institution identifier and the regional location does not match the pre-authorized regional location. At the same time, a write-off abnormality warning will be uploaded to the management staff for investigation and prevention of drug diversion and illegal cross-regional sales.
[0074] In some embodiments, when the regional verification parameters are compliant, the second quantity value subsequence codes are written off according to the second quantity value required to sell the retail drugs, and the drug inventory is updated synchronously and the drug write-off information is stored.
[0075] In some embodiments, information such as the execution time of the write-off operation, the execution terminal, the staff who performed the write-off operation, and the sales agency is recorded to ensure that the responsibility for the entire process of retail sales can be traced.
[0076] In some embodiments, if the regional verification parameters are in compliance, the remaining quantity of the currently opened and split-up drug corresponding to the target drug is queried. If the remaining quantity is greater than or equal to the second quantity, the subsequence code of the second quantity is cancelled. If the remaining quantity is less than the second quantity, the subsequence code of the remaining quantity is cancelled, and the new target drug is split up, corresponding subsequence codes are generated, and the subsequence code of the difference quantity is cancelled to make up the difference between the second quantity and the remaining quantity, thereby meeting the patient's medication needs.
[0077] In some embodiments, the method further includes: determining the second quantity value required to sell the retail drug based on the drug sales information, reimbursing the second quantity value of the subsequence code, and storing the reimbursed subsequence code in association with the patient information, and further includes: determining the dispensing quantity of the target drug for the sales agency; and configuring the drug reimbursement authority of the target drug for the sales agency when the dispensing quantity is not zero, and configuring the drug reimbursement quantity of the drug reimbursement authority to be the quantity value of the dispensing quantity.
[0078] Determine the dispensing quantity for a sales organization's target drug, specifically the current number of available retail drugs. If the dispensing quantity is non-zero, configure drug reimbursement permissions for the target drug for the sales organization, and set the reimbursement quantity within the reimbursement permission to the same value as the dispensing quantity. The reimbursement quantity changes dynamically with reimbursement operations and inventory replenishment.
[0079] In some embodiments, it is allowed to configure drug reimbursement authority and drug reimbursement quantity for sales agencies of registered marketable target drugs.
[0080] Through the dynamic allocation of inventory-driven authorization write-off times, precise control and real-time synchronization of retail drug write-off operations can be achieved, ensuring the legality of drug circulation and data reliability.
[0081] Subsequent write-offs allow for multiple drug write-offs within a single write-off scenario. Without restocking the split-off drug inventory, the cumulative write-off quantity cannot exceed the configured drug write-off quantity to prevent inventory overdrafts or data inconsistencies caused by excessive split-off sales.
[0082] If the number of drug write-offs is zero, the write-off operation cannot be performed.
[0083] In some embodiments, abnormal write-off operations can be intercepted through regional verification parameters to prevent illegal circulation of drugs. At the same time, under the condition of compliance with procedures, sales agencies are allowed to carry out the allocation of target drugs in small quantities, and the corresponding update of the drug reimbursement authority and drug reimbursement quantity of the target drugs is sufficient. Retrieval is only allowed when the procedures are compliant (such as both the transfer-out and transfer-in agencies have passed the regional verification and are qualified) to prevent illegal allocation of drugs from leading to illegal circulation of drugs. Dynamically balance the inventory balance of target drugs of different sales agencies to avoid drug waste or local shortages, and realize the flexible allocation of drugs in small quantities under the condition of legal circulation, taking into account both efficiency and safety.
[0084] Accordingly, relevant information of the dispensing operation is recorded for information traceability of the medicines that have been split into smaller pieces.
[0085] In some embodiments, the remaining time of the target drug's validity period is monitored; based on the validity period interval to which the remaining time of the validity period belongs, the drug expiration warning level of the target drug and the reimbursement authority status of the subsequence code are set; different validity period intervals correspond to different drug expiration warning levels and the reimbursement authority status.
[0086] The remaining validity period of the target drug is the difference between the current date and the target expiration date of the target drug. The difference between the current date and the target expiration date of the target drug is calculated in real time to obtain the remaining validity period.
[0087] In some embodiments, the target expiration date is the expiration date printed on the target drug's factory packaging, i.e., the original packaging expiration date. The difference between the current date and the original packaging expiration date is calculated to obtain the remaining validity period.
[0088] In some embodiments, after the unpacking operation is performed, the target drug corresponds to a unpacking date, an unpacking shelf life, and an unpacking expiration date. The unpacking date is the date on which the unpacking operation is performed, which is a time point. The unpacking shelf life is the theoretical shelf life of the drug determined after unpacking based on the packaging environment, storage conditions, and drug stability, such as 3 months, which is a time period. The unpacking expiration date refers to the effective end date of the drug's use, which is re-evaluated based on the packaging environment, storage conditions, and drug stability after the unpacking operation, which is a time point.
[0089] In some embodiments, the unpacked expiration date is constrained by the expiration date of the original packaging. If the initial unpacked expiration date determined based on the unpacked date and the unpacked shelf life is earlier than the original packaging expiration date, the initial unpacked expiration date determined based on the unpacked date and the unpacked shelf life is determined as the unpacked expiration date, and accordingly, the unpacked expiration date is the target expiration date. If the initial unpacked expiration date determined based on the unpacked date and the unpacked shelf life is equal to or later than the original packaging expiration date, the original packaging expiration date is determined as the unpacked expiration date, and accordingly, the unpacked expiration date, i.e., the original packaging expiration date, is the target expiration date.
[0090] In some embodiments, for a target drug in solid dosage form, the shelf life after unpacking is three months based on the packaging environment, storage conditions, and drug stability. The unpacking date is May 4, 2024, the initial unpacking expiration date is August 3, 2024, and the original packaging expiration date is June 30, 2025. Since the initial unpacking expiration date is earlier than the original packaging expiration date, the actual unpacking expiration date should be August 3, 2024, meaning the target expiration date is August 3, 2024.
[0091] In some embodiments, for a target drug in solid dosage form, the shelf life after unpacking is six months based on the packaging environment, storage conditions, and drug stability. The unpacking date is April 21, 2024, the initial unpacking expiration date is October 20, 2024, and the original packaging expiration date is October 12, 2024. Since the initial unpacking expiration date is later than the original packaging expiration date, the actual unpacking expiration date should be October 12, 2024, meaning the target expiration date is October 12, 2024.
[0092] The application of the expiration date of the retail medicine is to ensure the quality and safety of the retail medicine before it is used by patients.
[0093] In some embodiments, multiple validity period intervals are preset, and different validity period intervals correspond to different drug expiration warning levels and reimbursement authority statuses.
[0094] In some embodiments, there is a first validity period interval, a second validity period interval, and a third validity period interval. The interval value of the first validity period interval is greater than the interval value of the second validity period interval, and the interval value of the second validity period interval is greater than the interval value of the third validity period interval. For example, the first validity period interval is [120, maximum validity period], the second validity period interval is [30, 120), and the third validity period interval is [0, 30), where the maximum validity period is the total time from the drug production date to the target expiration date. The values of each validity period interval are only examples.
[0095] In some embodiments, the first validity period interval corresponds to the first-level warning of drug expiration and the normal status of reimbursement authority, the second validity period interval corresponds to the second-level warning of drug expiration and the restricted status of reimbursement authority, and the third validity period interval corresponds to the third-level warning of drug expiration and the frozen status of reimbursement authority.
[0096] In some embodiments, the first-level warning of drug expiration is to not give a reminder during the write-off, the second-level warning of drug expiration is to prompt the expiration information during the write-off through color identification (such as yellow) and / or a single pop-up reminder, and the third-level warning of drug expiration is to prompt the expiration information during the write-off through color identification (such as red) and multiple pop-up reminders.
[0097] In some embodiments, the normal state of the reimbursement authority is that the reimbursement of the target drug is unlimited, the restricted state of the reimbursement authority is that the single reimbursement quantity of the target drug is reduced, and the frozen state of the reimbursement authority is that the reimbursement of the target drug is not allowed.
[0098] Through the graded warning of validity period and the management of cancellation authority, the life cycle of retail drugs can be finely controlled, the risk of mis-selling can be reduced, expired drugs can be avoided from being sold to patients, and the safety of medication can be guaranteed.
[0099] In some embodiments, the subsequence codes of expired, unsold retail drugs can be marked as "unverified and expired" to prevent the subsequence codes from being written off, ensuring that expired retail drugs cannot flow into the market through write-off operations, eliminating the risk of patient misuse, ensuring the integrity and credibility of drug circulation data, and ensuring drug safety and the effectiveness of the traceability system.
[0100] In some embodiments, if the subsequence code of the target drug is cancelled and marked as "uncancelled and expired", all subsequence codes are invalid, and the drug packaging traceability code of the target drug is correspondingly updated to be invalid.
[0101] In some embodiments, the pharmacy staff scans the drug packaging traceability code of the target drug, automatically obtains the first quantity value corresponding to the target drug, and verifies the subsequence code corresponding to the drug packaging traceability code of the corresponding quantity.
[0102] In some embodiments, a corresponding number of subsequence codes are cancelled in sequence according to the size order of the zero stripping identifiers in the subsequence codes, which facilitates management.
[0103] In some embodiments, the information traceability system for retail drugs in this application is connected to the hospital information system (HIS) and the medical insurance system to achieve full-link traceability of retail drug information and improve processing efficiency.
[0104] In the embodiment of the present application, based on the drug packaging traceability code of the target drug, a subsequence code corresponding to each split-up drug is generated according to the first quantity value of the split-up drugs in the target drug, ensuring that each split-up drug corresponds to a subsequence code for traceability. Patient information and drug sales information are obtained, and based on the drug sales information, the second quantity value of the split-up drugs to be sold is determined, the subsequence code of the second quantity value is cancelled, and the cancelled subsequence code is associated with the patient information and stored. In this way, based on the generated subsequence code related to the drug packaging traceability code, the association and binding of patient information and split-up drugs can be achieved, which facilitates traceability, thereby solving the problem of the lack of information traceability methods for split-up drugs in the prior art.
[0105] See also Figure 2 , Figure 2 This is the process of an information tracing method for disassembled medicines provided in the embodiment of the present application. Figure 2 .like Figure 2 As shown, a method for tracing information of retail medicines includes the following steps:
[0106] Step 201: Based on the drug packaging traceability code of the target drug and in accordance with the first quantity value of the split-up drugs in the target drug, a subsequence code corresponding to each of the split-up drugs is generated.
[0107] The implementation process of this step is the same as the implementation process of step 101 in the aforementioned embodiment, and will not be repeated here.
[0108] Step 202: Obtain patient information and drug sales information.
[0109] The implementation process of this step is the same as the implementation process of step 102 in the aforementioned embodiment, and will not be repeated here.
[0110] Step 203: Based on the drug sales information, determine the second quantity value of the retail drug required for sale, write off the subsequence code of the second quantity value, and associate the written-off subsequence code with the patient information for storage.
[0111] The implementation process of this step is the same as the implementation process of step 103 in the aforementioned embodiment, and will not be repeated here.
[0112] Step 204: Generate a scannable split identification code based on the verified subsequence code.
[0113] In some embodiments, the generated scannable identification code is a scannable identification code such as a barcode or a QR code.
[0114] In some embodiments, there may be unverified small-quantity drugs in the original packaging of the target drug, so the small-quantity drugs corresponding to the verified subsequence codes cannot be placed in the original drug packaging. These small-quantity drugs are packaged by packaging equipment such as a packaging machine, that is, they are provided with new packaging.
[0115] In some embodiments, the sub-packaged drugs corresponding to the cancelled sub-sequence codes are assigned a single sub-package identification code, and the sub-sequence codes of the sub-packaged drugs to be contained in the same package have all been cancelled. That is, a scannable sub-package identification code is generated based on the sub-sequence codes of the sub-packaged drugs to be contained in the same package, allowing users to scan and query information, thereby enabling drug information traceability.
[0116] In some embodiments, the small-package medications to be contained in the same package may be small-package medications of a single category or multiple categories. For example, inpatients in a hospital may take medication with each meal, and multiple categories of small-package medications may be contained in the same package. Outpatient patients may take medication based on a course of treatment, such as two days, and each package may contain a single category of small-package medications.
[0117] Step 205: Print the split-package identification code and the corresponding drug date information, drug image, and patient information on the surface of the drug packaging of the split-package drug.
[0118] Drug date information includes production date, original packaging expiration date, unpacking date, unpacking expiration date, cancellation date and other date information.
[0119] The sub-package identification code is printed on the new packaging of the sub-packaged drug for scanning. Scanning reveals information associated with the sub-package code, including the manufacturer, production batch, production date, original packaging expiration date, sub-package date, sub-package expiration date, write-off date, instructions, sub-package code, drug packaging traceability code, and a drug image. The drug image is a bare image of the sub-packaged drug.
[0120] In some embodiments, you can set the information that can be viewed after scanning the identification code. For example, date information can be viewed directly, while patient-related information requires entering the patient's information for verification. This allows you to set access permissions for information, reducing the risk of patient information being leaked.
[0121] The new packaging also features printed information such as the drug date, drug image, and patient information, making it easier for medical staff and patients to check and verify. The patient information typically includes the patient's name, age, and department.
[0122] In some embodiments, if multiple categories of retail drugs are placed in the same package, the surface of the new package is printed with a retail identification code generated based on the subsequence codes of the multiple categories of retail drugs, patient information, and the drug date information and drug images of the multiple categories of retail drugs.
[0123] In an embodiment of the present application, after the second quantity value subsequence code is verified and the information is associated and stored, a scannable split-up identification code is generated based on the verified subsequence code, and the split-up identification code and the corresponding drug date information, drug image and patient information are printed on the surface of the drug packaging of the split-up drug, so that people can scan the split-up identification code to obtain the split-up drug information, and directly obtain some relevant information of the split-up drug through the tablet packaging, thereby realizing the verification and information traceability of the split-up drug.
[0124] See also Figure 3 , Figure 3 This is a structural diagram of an information traceability system for retail medicines provided in an embodiment of the present application. For ease of explanation, only the parts related to the embodiment of the present application are shown.
[0125] The information tracing system 300 for retail medicines includes: a generating module 301 , an acquiring module 302 , and a writing-off module 303 .
[0126] The generating module 301 is configured to generate a subsequence code corresponding to each of the split-up drugs based on the drug packaging traceability code of the target drug and according to the first quantity value of the split-up drugs in the target drug.
[0127] The acquisition module 302 is used to acquire patient information and drug sales information.
[0128] The verification module 303 is used to determine the second quantity value of the medicine to be sold in small quantities based on the medicine sales information, verify the subsequence code of the second quantity value, and store the verified subsequence code in association with the patient information.
[0129] In some embodiments, the generating module is specifically configured to:
[0130] Generate a split identifier corresponding to the first quantity value according to the first quantity value of the split-retail drug in the target drug;
[0131] Each of the split identifiers corresponding to the same set position of the drug packaging traceability code is combined with the drug packaging traceability code to obtain the first quantity value of the subsequence code.
[0132] In some embodiments, the write-off module is specifically configured to:
[0133] Performing sales compliance inspection based on regional verification parameters of the sales terminal that submitted the patient information and the drug sales information;
[0134] If the regional verification parameters are compliant, the second number of subsequence codes is cancelled.
[0135] In some embodiments, the write-off module is further configured to:
[0136] Obtaining the regional verification parameter of the sales terminal that submitted the patient information and the drug sales information;
[0137] Verifying whether the organization identifier in the area verification parameter is a pre-authorized organization identifier, and whether the area location in the area verification parameter is a pre-authorized area location;
[0138] If the organization identifier belongs to the pre-authorized organization identifier and the area location belongs to the pre-authorized area location, determining that the area verification parameter is compliant;
[0139] If the organization identifier does not belong to the pre-authorized organization identifier and / or the area location does not belong to the pre-authorized area location, it is determined that the area verification parameter is non-compliant.
[0140] In some embodiments, the system further includes a rights management module for:
[0141] determining the dispensing quantity of the target drug for the sales organization;
[0142] In the case that the dispensing quantity is not zero, the sales organization is configured with drug reimbursement authority for the target drug, and the drug reimbursement quantity of the drug reimbursement authority is configured as the quantity value of the dispensing quantity.
[0143] In some embodiments, the system further comprises a drug package processing module for:
[0144] Generating a scannable split identification code based on the verified subsequence code;
[0145] The split-up identification code and the corresponding drug date information, drug image and patient information are printed on the drug packaging surface of the split-up drug.
[0146] In some embodiments, the system further includes a deadline management module for:
[0147] Monitoring the remaining time of the target drug's expiration date;
[0148] According to the validity period interval to which the remaining validity period time belongs, the drug expiration warning level of the target drug and the cancellation authority status of the subsequence code are set; different validity period intervals correspond to different drug expiration warning levels and the cancellation authority status.
[0149] The information tracing system for retail medicines provided in the embodiment of the present application can implement each process of the embodiment of the above-mentioned information tracing method for retail medicines and can achieve the same technical effect. To avoid repetition, it will not be described here.
[0150] Figure 4 1 is a structural diagram of an electronic device provided in an embodiment of the present application. As shown in the figure, the electronic device 4 of this embodiment includes: at least one processor 40 ( Figure 4 Only one is shown), a memory 41 and a computer program 42 stored in the memory 41 and executable on the at least one processor 40, wherein the processor 40 implements the steps of any of the above-mentioned method embodiments when executing the computer program 42.
[0151] The electronic device 4 can be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The electronic device 4 can include, but is not limited to, a processor 40 and a memory 41. It can be understood by those skilled in the art that Figure 4 It is only an example of the electronic device 4 and does not constitute a limitation of the electronic device 4. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.
[0152] The processor 40 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0153] The memory 41 may be an internal storage unit of the electronic device 4, such as a hard disk or memory of the electronic device 4. The memory 41 may also be an external storage device of the electronic device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. Furthermore, the memory 41 may include both an internal storage unit of the electronic device 4 and an external storage device. The memory 41 is used to store the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is about to be output.
[0154] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0155] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0156] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0157] In the embodiments provided in this application, it should be understood that the disclosed systems / electronic devices and methods can be implemented in other ways. For example, the system / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of the system or unit, which can be electrical, mechanical or other forms.
[0158] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0159] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0160] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0161] The present application implements all or part of the processes in the above-mentioned embodiment methods, and may also be implemented through a computer program product. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments when executing the computer program product.
[0162] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.
Claims
1. A method for tracing information of retail medicines, characterized in that: include: Based on the drug packaging traceability code of the target drug, generating a subsequence code corresponding to each of the split-up drugs according to the first quantity value of the split-up drugs in the target drug; Obtain patient information and drug sales information; Based on the drug sales information, a second quantity value of the retail drug required for sale is determined, the subsequence code of the second quantity value is written off, and the written-off subsequence code is associated with the patient information and stored.
2. The method according to claim 1, characterized in that The drug packaging traceability code based on the target drug generates a subsequence code corresponding to each of the split-up drugs according to the first quantity value of the split-up drugs in the target drug, including: Generate a split identifier corresponding to the first quantity value according to the first quantity value of the split-retail drug in the target drug; Each of the split identifiers corresponding to the same set position of the drug packaging traceability code is combined with the drug packaging traceability code to obtain the first quantity value of the subsequence code.
3. The method according to claim 1, characterized in that The step of determining a second quantity value required for selling the retail medicine based on the medicine sales information, and writing off the subsequence codes of the second quantity value, includes: Performing sales compliance inspection based on regional verification parameters of the sales terminal that submitted the patient information and the drug sales information; If the regional verification parameters are compliant, the second number of subsequence codes is cancelled.
4. The method according to claim 3, characterized in that The sales compliance inspection based on the regional verification parameters of the sales terminal that submits the patient information and the drug sales information includes: Obtaining the regional verification parameter of the sales terminal that submitted the patient information and the drug sales information; Verifying whether the organization identifier in the area verification parameter is a pre-authorized organization identifier, and whether the area location in the area verification parameter is a pre-authorized area location; If the organization identifier belongs to the pre-authorized organization identifier and the area location belongs to the pre-authorized area location, determining that the area verification parameter is compliant; If the organization identifier does not belong to the pre-authorized organization identifier and / or the area location does not belong to the pre-authorized area location, it is determined that the area verification parameter is non-compliant.
5. The method according to claim 1, wherein Before determining, based on the drug sales information, a second quantity value required for selling the retail drug, rewriting the subsequence codes corresponding to the second quantity value, and associating and storing the rewritten subsequence codes with the patient information, the method further includes: determining the dispensing quantity of the target drug for the sales organization; In the case that the dispensing quantity is not zero, the sales organization is configured with drug reimbursement authority for the target drug, and the drug reimbursement quantity of the drug reimbursement authority is configured as the quantity value of the dispensing quantity.
6. The method according to claim 1, characterized in that After determining a second quantity value required for selling the retail drug based on the drug sales information, rewriting the subsequence code corresponding to the second quantity value, and associating and storing the rewritten subsequence code with the patient information, the method further includes: Generating a scannable split identification code based on the verified subsequence code; The split-up identification code and the corresponding drug date information, drug image and patient information are printed on the drug packaging surface of the split-up drug.
7. The method according to claim 1, characterized in that The method further comprises: Monitoring the remaining time of the target drug's expiration date; According to the validity period interval to which the remaining validity period time belongs, the drug expiration warning level of the target drug and the cancellation authority status of the subsequence code are set; different validity period intervals correspond to different drug expiration warning levels and the cancellation authority status.
8. An information tracing system for retail medicines, characterized in that: include: a generating module configured to generate, based on the drug packaging traceability code of the target drug and in accordance with the first quantity value of the split-up drugs in the target drug, a subsequence code corresponding to each of the split-up drugs; Acquisition module, used to obtain patient information and drug sales information; A verification module is used to determine the second quantity value of the retail medicine required to be sold based on the medicine sales information, verify the second quantity value of the subsequence code, and associate the verified subsequence code with the patient information for storage.
9. An electronic device, characterized in that: The electronic device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the electronic device implements the method according to any one of claims 1 to 7.
10. A computer program product, characterized in that The invention comprises a computer program which, when executed, causes the method according to any one of claims 1 to 7 to be performed.
Citation Information
Cited By
Drug management method and device based on traceability code and medium
CN120766909A