Technical Field
The present disclosure generally relates to a prescription management system and a method thereof. More particularly, the present disclosure relates to a prescription management system and method for digitizing prescriptions, monitoring, and verifying the prescriptions of medicines and facilitating dispensation of the prescribed medicines.
Background
Some medicines, specially antibiotics, are known to have a harmful effect if taken without permission from a doctor or if taken in large quantities than prescribed. Specially, in some critical diseases, such as Tuberculosis, appropriate medicines need to be taken and abuse and/or overdosage of such medicines may have significant harmful effects. Therefore, it is necessary to monitor and control dispensing of such medicines to only those who have a legitimate need and prescription from the doctor. However, tracking and monitoring of such huge number of prescriptions, has always been a challenge. One of the reasons for such a challenge is that these prescriptions are mostly hand-written, and it is a cumbersome task to track and record such hand-written prescriptions.
Additionally, microorganisms’ resistance to different classes of antibiotic medicines has turned out to be a major environmental and healthcare problem. Therefore, it is also important to prescribe medicines according such prevailing resistance patterns as per the individual patient or a region to which the patient belongs or both. Accordingly, in addition to tracking and monitoring dispensation of antibiotics to a patient, it is also important to ensure that the medicine prescribed and dispensed are appropriate for the diagnosis of that patient.
Accordingly, there exists a need for a system that prevents irrational usage of medicines, especially, antibiotics and that also monitors accuracy of the medicines dispensed to a patient.
Summary
In an aspect, a method of managing prescriptions is provided. The method includes receiving, by a processing unit, a prescription from an input data source, the prescription being one of a hand-written prescription, an audio prescription and a video prescription. The prescription prescribes one or more medicines to a patient according to a treatment diagnosis. The method also includes extracting, by the processing unit, one or more medicines prescribed in the prescription and verifying the extracted one or more medicines with respect to one or more treatment parameters. The method further includes displaying, by the processing unit, a dispensable list of prescribed medicines based on the verification of the extracted medicines.
In another aspect, a prescription management system is provided. The prescription management system includes an input data source and a control system communicably coupled to the input data source. The input data source is configured to receive a prescription prescribing one or more medicines to a patient according to a treatment diagnosis. The prescription is one of a handwritten prescription, audio prescription and a video prescription. The control system includes a processing unit having a digitization unit and a verification unit. The digitization unit is configured to receive the prescription from the input data source, and extract one or more medicines prescribed in the received prescription and one or more additional information associated with the prescription. The digitization unit is further configured to store the received prescription based on the extracted one or more medicines. The verification unit is configured to verify the one or more extracted medicines with respect to one or more treatment parameters. The verification unit is further configured to display a dispensable list of prescribed medicines based on the verification of the extracted medicines.
Brief Description of the Drawings
FIG. 1 illustrates a block diagram of an exemplary prescription management system, in accordance with the concepts of the present disclosure; and
FIG. 2 illustrates an exemplary method of managing prescriptions, in accordance with the concepts of the present disclosure.
Detailed Description of the Drawings
Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the invention. Furthermore, embodiments of the invention may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the inventions herein described.
The present disclosure relates to a prescription management system and a method thereof. FIG. 1 illustrates a block diagram of an exemplary prescription management system 100 for digitizing prescriptions, monitoring, and verifying the prescription of medicines and facilitating dispensation the prescribed medicines, according to various embodiments of the present disclosure. A prescription may be a hand-written document, and/or an electronic document provided by a doctor to a patient, having one or more health issues. Alternatively, the prescription may be a voice and/or video recorded prescription having appropriate authentication of the doctor issuing the voice prescription. The prescription may include one or more medicines prescribed for the patient according to a diagnosis of the patient. For example, the prescription may include one or more medicines and/or drugs, such as antibiotics, generic medicines, pain killers, steroids, etc.
The prescription management system 100 depicted in FIG. 1 may be implemented in any suitable computing environment, such as one or more of, a desktop or a laptop computer, a computer server, or a mobile computing device, such as a mobile phone, a Personal Digital Assistant (PDA), or a smart phone. In addition, the prescription management system 100 may be combined into fewer systems than shown or divided into more systems than shown. The communications links depicted in FIG. 1 may be through wired or wireless connections and may be a part of a secured network, such as a local area network (LAN) and/or a combination of networks, such as LANs, WANs, MANs and/or the Internet. Further, the prescription management system 100 may be implemented at the doctor’s end, the patient’s end, the pharmacist’s end or a combination thereof.
In an embodiment of the present disclosure, the prescription management system 100 includes an input data source 102, and a control system 104 communicably coupled to the input data source 102. According to an embodiment of the present disclosure, the input data source 102 is configured to receive one or more prescriptions from one or more users, such as a patient, or a doctor or a pharmacist, etc. The input data source 102 may be a mobile phone, a scanner connected to a computer desktop or laptop, an image capturing device, configured to receive an image of a prescription issued by a doctor. In some examples, the input data source 102 may be provided at a pharmacist location, or a patient’s location or the doctor’s location. In an exemplary embodiment, the one or more prescriptions may be hand-written prescriptions given by the doctor. In some other embodiments, the prescription may be a video or audio prescription. It may be contemplated that although there are only a few types of prescriptions provided in the foregoing description, the claimed subject matter is not intended to be limiting to the described types of prescriptions only. For example, when a patient brings the prescription to a pharmacist, the pharmacist may scan or capture the image of the prescription by a mobile camera, or a scanner etc. Alternatively, the patient having the prescription may scan or capture the image of the prescription by his/her mobile camera or scanner etc. In a yet another example, the doctor, issuing the prescription, may scan or capture the prescription using his mobile camera or scanner etc.
The input data source 102 may include an input unit 101 and an output unit 103. The input unit 101 may be a keypad, or a touchpad, or a microphone or a voice recognition system or any other input device. The input unit 101 is configured to receive input from the one or more patient, doctor or the pharmacist. The output unit 103 may be a display device, an audio output device, etc.
The control system 104 is configured to communicate with the input data source 102 and receive the one or more prescription from the input data source 102. In an embodiment of the present disclosure, the control system 104 is configured to digitize the received prescription, process the prescription and finally facilitate dispensing of the medicines prescribed in the prescription based on the processing. The control system 104 may be a centralized system (which may be implemented on a server or a cloud server, etc.) connected to the various other components of the prescription management system 100 via a network (not shown), such as Internet or intranet, etc. The control system 104 includes suitable logic, circuitry, and/or interfaces that are configured to control the various operations of the prescription management system 100.
In an embodiment of the present disclosure, the control system 104 includes an Input / Output unit 106, (hereinafter referred to as I/O unit 106), a processing unit 108, a memory unit 110, and a communication unit 112. The I/O unit 106 is configured to communicate with the input data source 102 via the communication unit 112, to receive the prescription.
The processing unit 108 may include a microprocessor connected to a communication bus (not shown). The memory unit 110 is configured to store a set of instructions that are executable by the processing unit 108 to perform the predetermined operations. The memory unit 110 may include, but is not limited to, a Random-Access Memory (RAM), a Read Only Memory (ROM), a Hard Disk Drive (HDD), and a Secure Digital (SD) card. The processing unit 108 is configured to execute the instructions stored in the memory device 110 to perform predetermined operations. The processing unit 108 may be implemented using one or more controller technologies, such as Application Specific Integrated Circuit (ASIC), Reduced Instruction Set Computing (RISC) technology, Complex Instruction Set Computing (CISC) technology, etc. Further, the communication unit 112 may include a modem, an Ethernet card, or other similar devices, that enable the control system 104 to connect to the various components of the prescription management system 100.
The prescription received from the input data source 102 via the I/O unit 106 is further processed by the processing unit 108. In an embodiment of the present disclosure, the processing unit 108 includes a digitization unit 114 configured to receive the hand-written prescription and/or audio-video prescription and further digitize same. In an embodiment, the digitization unit 114 is configured to digitize the hand-written prescription and/or audio-video prescription in real time. In one example, the digitization unit 114 may extract the patient information from the prescription, by using Optical Character Recognition (OCR) techniques or other text recognition techniques and/or voice recognition techniques. Alternatively, digitization unit 114 is configured to receive data associated with the patient from the I/O unit 106, such as name, age, unique identification, geographic location and diagnosis of the patient. In an embodiment, the patient data may be input by the pharmacist, or by the user (or the patient) through input unit 101 of the input data source 102. Alternatively, a support team member located a central customer care center, may provide the patient data to the digitization unit 114. In an embodiment, the prescription management system 100 includes a patient database 116 configured to store the patient information received by the digitization unit 114, such as the name, unique identification, age, diagnosis, etc., associated with the patient. In an example, the digitization unit 114 and the input data source 102 may communicate with the patient database 116 in order to assist the information provider with suggestions as they feed the patient details into the input unit 101 of the input data source 102.
Further, the digitization unit 114 is configured to receive information associated with the doctor, who has issued the prescription, such as name of the doctor, hospital name, geographic location of the doctor, specialization of the doctor, etc. In one example, the digitization unit 114 may extract the doctor information from the prescription, by using OCR techniques or other text and voice recognition techniques. In another example, doctor information may also be provided by the pharmacist, or the patient, or the doctor himself, or by the support team member. The prescription management system 100 may also include a doctor database 118 configured to store the information associated with the doctor, such as the name and identification of the doctor, specialization of the doctor, contact information of the doctor, the hospital details (if any), the geographic location etc. The digitization unit 114 and the input data source 102 may communicate with the doctor database 118 in order to assist the provider with suggestions as they feed the doctor details into the input unit 101 of the input data source 102.
In an embodiment of the present disclosure, the digitization unit 114 is configured to extract the one or more medicines prescribed in the prescription. For example, the digitization unit 114 may extract the first medicine using the hand writing recognition, OCR technique or voice recognition techniques and communicate the same to the I/O unit 106. Once the digitization unit 114 recognizes the first medicine in the prescription, the pharmacist and/or the support team member is prompted about the same for validation through the I/O unit 106 and further to the output unit 103 of the input data source 102. For example, the pharmacist and/or the support team member may be prompted with the recognized medicine via the output unit 103 provided on the input data source 102. The pharmacist and/or the support team member may validate the recognized medicine via the input unit 101 of the input data source 102. In case, there is an error in the recognized medicine, then the pharmacist and/or the support team member may manually correct the same and communicate it back to the digitization unit 114.
The digitization unit 114 is further configured to predict the other medicines prescribed in the prescription, based on the recognized and validated first medicine. In an exemplary embodiment of the present disclosure, the prescription management system 100 may include a medicine database 115 configured to store information related to the various medicines available in the market. For example, the information may include, but not limited to, the name and composition of the medicine, the diagnosis for which the medicine is generally used, batch number of medicine package, the group of medicine with which a particular medicine is prescribed, contraindicated medicines and drugs, etc. In an embodiment of the present disclosure, the medicine database 115 may also store a maximum permissible dosage limit for every medicine. The digitization unit 114 may predict the remaining medicines in the prescription based on one or more parameters associated with the patient and the doctor. For example, the prediction is based on the diagnosis of the patient, the medicines that are generally prescribed along with the recognized first medicine for the particular diagnosis of the patient (from the medicines database 115), and/or the doctor’s pattern of prescribing the medicines for the particular diagnosis of the patient and/or the doctor’s pattern of prescribing medicines along with the recognized first medicine. The predicted set of remaining medicines are again verified and validated by the pharmacist and/or the support team member as done for the first recognized medicine.
Once, the entire set of medicines prescribed in the prescription are recognized, the entire digitized prescription is obtained and stored in a prescription database 120 along with the scanned copy of the prescription. The prescription database 120 will also store all the additional information associated with the prescription, such as the medicines, the patient name and ID, the doctor name and ID, diagnosis (including doctor’s diagnosis as well as test reports of the patient, etc.), location of the doctor and invoice details associated the prescription, etc.
In an embodiment of the present disclosure, the prescription management system 100 further includes an intelligence database 122 configured to receive and store antibiotic sensitivity and resistance reports pertaining to a geographic location and individual patients. For example, a centralized testing laboratory (not shown) is configured to obtain the prescription details, and/or sensitivity reports and patterns associated with one or more antibiotics and geographic locations. For example, the sensitivity report may indicate which bacteria are resistant to which antibiotic in a particular geographic region, such as a locality, a city, a state or a country. These sensitivity reports may be obtained and collated by the testing laboratories based on hospital bacterial resistance pattern received from hospitals in the geographic region, or antibiotic culture sensitivity reports from various patients in the region etc.
The processing unit 108 further includes a verification unit 124 configured to verify the extracted medicines prescribed in the obtained digitized prescription with respect to a number of treatment parameters, such as the sensitivity and resistance reports and patterns obtained from the intelligence database 122 and the permissible dosages associated with the medicines obtained from the medicine database 115. For example, each and every medicine in the prescription is checked in the sensitivity report received for the particular geographic region in which the patient is located and/or the individual patient. If the medicine is verified with respect to these treatment parameters, then it is included in a disable list of medicines for the received prescription. However, in case, a particular medicine is listed to have a high resistance, then the verification unit 124 may cause to generate an alert on the output unit 103 of the input data source 102 at the pharmacist location or the patient’s location and/or the doctor’s location. For example, the alert may indicate an alternative/substitute medicine according to the diagnosis of the patient and the doctor prescribing the medicine. Alternatively, the alert may reject the prescription and indicate that the patient should consult the doctor to change the prescribed medicine. Furthermore, the verification unit 124 may also send an update to the doctor who has prescribed the prescription, of such resistance issue associated with the medicine, in the form of an email or a message notification.
The verification unit 124 is further configured to check the history of the patient and the prescription in order to facilitate dispensation of the prescribed medicines. For example, when the prescription is received, the prescription is checked in the prescription database 120, whether the prescription has been received before or not. For example, the prescription has a unique identification associated with it, and the verification unit 124 may compare the unique identification of the prescription with the stored prescriptions in the prescription database 120. If the prescription already exists in the prescription database 120, then the dispensation details are checked from the prescription database 120. This means, whether the medicines prescribed in the prescription have all been dispensed entirely or not. If the medicines prescribed in the prescription have been dispensed entirely, then the prescription is rejected by the verification unit 124 and a notification is sent to the output unit 103 associated with the input data source 102. The notification may also include the reason for rejection of the prescription. The dispensation details may be obtained from the invoice associated with pre-stored prescription in the prescription database 120. However, if the prescription is not entirely dispensed earlier, then the allowable remaining quantity of the medicines are determined by the verification unit 124. The remaining allowable quantity of the medicines are also determined from the invoices stored in the prescription database 120. For example, if a medicine is prescribed for 15 days and it is dispensed for 10 days as per the invoices, then the verification unit 124 determines that the medicine is to be dispensed only for the remaining 5 days, and further communicates the same to the output unit 103 associated with the input data source 102.
Further, the verification unit 124 is configured to check maximum permissible dosage limit for every medicine before dispensation is made. In an embodiment, the verification unit 124 is configured to receive the maximum permissible dosage limit of the prescribed medicine and determine if the quantity of medicine prescribed in the prescription is more than the permissible limit for that particular medicine. In case the prescribed dosage is more than the maximum permissible dosage limit, then the prescription is rejected by the verification unit 124 and a notification is sent to the output unit 103 associated with the input data source 102. For example, if a Doctor prescribes medicine of 300 mg, while the medicine database 115 reveals maximum permissible limit to be 250 mg, then the verification unit 124 may generate an alert and accordingly generate advice to contact doctor to change the prescribed dosage and/or the medicine.
Based on the verified medicines and the dosages, the verification unit 124 is configured to cause the output unit 103 of the input data source 102 to display the final dispensable list of medicines, thereby facilitating the pharmacist in dispensing the appropriate medicines and appropriate dosages of the same.
The processing unit 108 further includes an update unit 126 configured to update the dispensation details along with the invoice and batch numbers of the packages associated with the dispensation of the medicines prescribed in the prescription and store these updated details in the prescription database 120. In an embodiment, the update unit 126 may delete the prescription after it is completely dispensed, so that the medicines prescribed in the prescription are not over dispensed or are not repeatedly dispensed. In this example, the prescription may be stored with a unique identification and when all the medicines prescribed in the prescription are dispensed, then the prescription associated with the unique identification is deleted from the database. Accordingly, when a patient again brings the prescription with the unique identification, the verification unit 124 will reject the prescription associated with that unique identification. Furthermore, the prescription management system 100 includes a pharmacist database 128 configured to store details associated with various pharmacists, such as pharmacist license number, location of practice, etc. Therefore, the update unit 126 also updates the pharmacist details along with the dispensation details, and invoices to facilitate tracking of the pharmacist also.
It may be contemplated that the databases described herein may be internal and/or external databases and may include data repositories, or other data sources. Although, there are multiple databases described in the present disclosure, it may be contemplated by a person ordinarily skilled in the art that these databases can be combined also, without deviating from the scope of the present disclosure. In some embodiments, the databases may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, a record-based database, or the like.
A person having ordinary skills in the art will appreciate that the system, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above disclosed system elements, or modules and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.
Those skilled in the art will appreciate that any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules and is not limited to any particular computer hardware, software, middleware, firmware, microcode, or the like.
The claims can encompass embodiments for hardware, software, or a combination thereof.
It will be appreciated that variants of the above disclosed, and other features and functions or alternatives thereof, may be combined into many other different systems or applications. Presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art, which are also intended to be encompassed by the following claims.
Industrial Applicability
Referring to FIG. 2, an exemplary method 200 for managing prescriptions is illustrated. In an embodiment, the method 200 is performed by the prescription management system 100 of the present disclosure.
Initially, at step 202, a prescription is received from the input data source 102, such as via the input unit 101 of the input data source. The received prescription may be a hand-written prescription, textual prescription, audio prescription and/or a video prescription. The prescription is issued by a doctor prescribing one or more medicines to a patient according to a treatment diagnosis.
At step 204, one or more medicines prescribed in the prescription are extracted. For example, the digitization unit 114 of the processing unit 108 is configured to extract the one or more medicines prescribed in the prescription. In one example, the digitization unit 114 may use the Optical Character Recognition (OCR) techniques to extract the one or more medicines prescribed in the prescription, when the prescription is a hand-written prescription. The digitization unit 114 may also extract additional information associated with the received prescription in a similar manner. For example, the digitization unit 114 may extract the patient’s name, patient’s ID, doctor’s name and ID (who has issued the prescription), etc.
In an embodiment of the present disclosure, the digitization unit 114 is configured to extract the first medicine prescribed in the prescription using the text recognition techniques, such as OCR etc. Further the digitization unit 114 is configured to predict the remaining other medicines in the prescription based on the extracted first medicine. For example, the digitization unit 114 may predict the medicines that are generally given along with the first medicine for a particular treatment. The digitization unit 114 may also predict the other medicines based on the issuing doctor’s trend of prescribing medicines along with the extracted first medicine. Once the medicine is extracted and/or predicted by the digitization unit 114, the same is prompted on the input unit 101 of the input data source 102 for validation. In one example, the digitization unit 114 is configured to validate each and every extracted and/or predicted medicine in the prescription based on a user input received through the input unit 101 of the input data source 102. Once all the prescribed medicines are validated, the digitized prescription (including the medicines, the doctor’s name, patient’s name, diagnosis, etc.) are stored in the prescription database 120.
Further, at step 206, the medicines, extracted at step 204, are verified with respect to one or more treatment parameters. The treatment parameters include medicinal sensitivity and resistance, and/or permissible dosage associated with each of the medicines prescribed in the prescription. The sensitivity and resistance associated with the medicines may be received from the sensitivity and resistance reports stored in the Intelligence database 122. For example, the sensitivity and resistance reports may correspond to a particular geographic region(s). Further, the permissible dosages of a medicine may be received from the medicine database 115 and/or the prescription database 120. The permissible dosage may indicate the maximum permissible dosage of a medicine or remaining dosage from the maximum dosage prescribed in the prescription.
When the prescribed medicines are verified with respect to the treatment parameters, then a dispensable list is displayed on the output unit 103 of the input data source 102, based on the verification. For example, when the prescribed medicine, extracted at step 204, is verified as per the permissible dosage and/or does not have sensitivity and is not resistant as per the sensitivity and resistance report, then the medicine is displayed in the dispensable list. However, if the dosage of the medicine is more than the permissible dosage, or if the medicine is listed in the sensitivity and resistance report indicating that the particular region where the patient belongs, the bacteria are resistant to the medicine, then the verification unit 124 may reject the medicine and suggest an alternative to the prescribed medicine. Further, the verification unit 124 may also prompt at the output unit 103 of the input data source 102 to consult the doctor for issuing an alternative medicine to the rejected prescribed medicine.
The prescription management system 100 and the method 200 of the present disclosure provides digitizing of the hand-written prescription and/or audio-video prescription with minimal human intervention. Further, the prescription management system 100 and the method 200 provides tracking of the medicines, especially antibiotics that are dispensed to patients. Therefore, the system prevents irrational usage and abuse of sensitive medicines and antibiotics. For example, for some critical health issues, such as Tuberculosis where abuse and overdosage of medicines may prove to be very harmful, the prescription management system 100 and the method 200 will prevent such abuse and overdosage by tracking and restricting the dispensation of such medicines to the prescribed limit only. The various databases, such as the patient database 116, the pharmacist database 128 and the doctor database 118 being updated regularly, facilitate regular tracking of these entities and help build accountability for them. Any unusual activity may be noted from these databases to ensure no drugs and medicines are being abused. Furthermore, the intelligence database 122 also facilitates regular tracking and monitoring of antibiotic resistance issues prevalent in a region which helps in guiding the doctors, the patients and also the pharmacists in more accurately dispensing and prescribing medicines. Additionally, the system 100 may be configured to update Doctors, patients and the jurisdiction Government with current antibiotic resistance trends. For example, a report may be generated for the Government relating to monitoring of compliance, updating the policies associated with antibiotic based on antibiotic resistance trend achieved by the system 100.
While aspects of the present disclosure have been particularly shown, and described with reference to the embodiments above, it will be understood by those skilled in the art that various additional embodiments may be contemplated by the modification of the disclosed machines, systems, and methods without departing from the spirit and scope of what is disclosed. Such embodiments should be understood to fall within the scope of the present disclosure as determined based upon the claims and any equivalents thereof.

ELEMENT LIST

TITLE: PRESCRIPTION MANAGEMENT SYSTEM AND A METHOD THEREOF

100 Prescription Management System
102 Input Data Sources
101 Input Unit
103 Output Unit
104 Control System
106 Input / Output Unit
108 Processing Unit
110 Memory Unit
112 Communication Unit
114 Digitization Unit
115 Medicines Database
116 Patient Database
118 Doctor Database
120 Prescription Database
122 Intelligence Database
124 Verification Unit
126 Update Unit
128 Pharmacist Database
200 Method
202 Step
204 Step
206 Step
208 Step

CLAIMS:
1. A method for managing prescriptions, the method comprising:
receiving, by a processing unit (108), a prescription from an input data source (102), the prescription being one of a handwritten prescription, audio prescription and video prescription prescribing one or more medicines to a patient according to a treatment diagnosis;
extracting, by the processing unit (108), one or more medicines prescribed in the received prescription;
verifying, by the processing unit (108), the one or more extracted medicines with respect to one or more treatment parameters; and
displaying, by the processing unit (108), on the input data source (102), a dispensable list of prescribed medicines based on the verification of the extracted medicines.

2. The method as claimed in claim 5, wherein the one or more medicines are extracted using Optical Character Recognition (OCR) techniques when the received prescription is a hand-written prescription.

3. The method as claimed in claim 1, wherein extracting the one or more medicines includes:
extracting, by the processing unit (108), a first medicine prescribed in the prescription;
predicting, by the processing unit (108), other one or more medicines prescribed in the prescription based on the extracted first medicine;
validating, by the processing unit (108), the extracted and predicted first medicine and the one or more other medicines; and
storing, by the processing unit (108), the validated one or more medicines prescribed in the prescription.

4. The method as claimed in claim 1, wherein the one or more treatment parameters includes:
medicinal sensitivity and resistance associated with the extracted one or more medicines; and
permissible dosage associated with the extracted one or more medicines.

5. The method as claimed in claim 1, wherein displaying the dispensable list of prescribed medicines further includes:
rejecting, by the processing unit (108), the extracted one or more medicines when not verified with respect to the one or more treatment parameters; and
displaying, by the processing unit (108), on the input data source (102), one or more alternative medicines for the rejected one or more medicines.

6. A prescription management system (100) comprising:
an input data source (102) configured to receive a prescription prescribing one or more medicines to a patient according to a diagnosis of treatment, the prescription being one of a handwritten prescription, audio prescription and video prescription; and
a control system (104) communicably coupled to the input data source (102), the control system (104) including:
a processing unit (108) including:
a digitization unit (114) to:
receive the prescription from the input data source (102);
extract one or more medicines prescribed in the received prescription and one or more additional information associated with the prescription;
store, in a prescription database (120), the received prescription based on the extracted one or more medicines; and
a verification unit (124) to:
verify the one or more extracted medicines with respect to one or more treatment parameters; and
display, on the input data source (102), a dispensable list of prescribed medicines based on the verification of the extracted medicines.

7. The prescription management system (100) as claimed in claim 6, wherein the digitization unit (114) is configured extract the one or more medicines using Optical Character Recognition (OCR) techniques when the received prescription is a hand-written prescription.

8. The prescription management system (100) as claimed in claim 6, wherein the digitization unit (114) is to:
extract a first medicine prescribed in the prescription;
predict one or more other medicines prescribed in the prescription based on the extracted first medicine;
validate the extracted and predicted first medicine and the one or more other medicines; and
store the validated one or more medicines prescribed in the prescription in the prescription database (120).

9. The prescription management system (100) as claimed in claim 6, wherein the one or more treatment parameters includes:
medicinal sensitivity and resistance associated with the extracted one or more medicines; and
permissible dosage associated with the extracted one or more medicines.

10. The prescription management system (100) as claimed in claim 6, wherein the verification unit (124) is to:
reject the extracted one or more medicines when not verified with respect to the one or more treatment parameters; and
display, on the input data source (102), one or more alternative medicines for the rejected one or more medicines.