Method and system for verifying a medication to be injected to a subject

Abstract

Provided are embodiments directed to computer-implemented methods and systems for verifying a medication to be administered to a subject, the method including: receiving a video of a drug vial provided with a vial label, the video comprising a plurality of video frames; extracting given drug information from the vial label by analyzing at least one of the video frames using an optical character recognition method, the given drug information comprising at least a drug name, an expiry date and a concentration; and providing for display the detected drug information. Also provided are embodiments directed to a scanning support for holding a labelled cylindrical article and a labelled tubular article for scanning of the labels or marks thereof by an overhead optical sensor, and embodiments directed to a scanning and display station for scanning a labelled cylindrical or tubular article and displaying an information related to the label thereof.

Description

METHOD AND SYSTEM FOR VERIFYING A MEDICATION TO BE INJECTED TO A SUBJECTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority to US Provisional Application 63 / 707,397 filed October 15th, 2024 the entire contents of which are incorporated herein by reference.TECHNICAL FIELD

[0002] The present technology relates to drug delivery in general and more specifically to methods, systems and non-transitory storage mediums for verifying a medication to be injected to a subject.BACKGROUND OF THE ART

[0003] Medication errors refer to errors that can occur when prescribing, dispensing, or administering medications. These errors can have serious consequences on the health of patients and can even lead to adverse effects or even death.

[0004] Therefore, there is a need for a method and system for verifying a medication to be injected to a subject.SUMMARY

[0005] It is an object of the present technology to ameliorate at least some of the inconveniences present in the prior art. One or more implementations of the present technology may provide and / or broaden the scope of approaches to and / or methods of achieving the aims and objects of the present technology.

[0006] According to a first broad aspect, there is provided a method for verifying a medication to be administered to a subject, the method being executed by a processor, the method comprising: receiving a video of a drug vial provided with a vial label, the video comprising a plurality of video frames; extracting given drug information from the vial label by analyzing at least one of the video frames using an optical character recognition method, thegiven drug information comprising at least a drug name, an expiry date and a concentration; and providing for display the detected drug information.

[0007] In some non-limiting implementations the method may further comprise: generating, at the processor, a user interface based on the detected drug information.

[0008] In some non-limiting implementations, the user interface may be one of a dose injection calculator prepopulated based on the detected drug information; a two-part injection calculator prepopulated based on the detected drug information; and a multi-dose injection calculator prepopulated based on the detected drug information.

[0009] In some non-limiting implementations, the step of detecting the given drug information comprises detecting a drug identifier from the vial label.

[0010] In some non-limiting implementations, the drug identifier comprises one of a national drug code and a drug identification number.

[0011] In some non-limiting implementations, the method further comprises: converting the given drug information into an audio signal using a text-to-speech method; and providing the audio signal for play back by a speaker.

[0012] In some non-limiting implementations, the method further comprises: receiving, from a microphone, an audio signal representative of the user reading aloud the displayed drug information; converting the audio signal into text using a speech recognition method; identifying further drug information from the text; comparing the further drug information to the given drug information, thereby obtaining a comparison result; and outputting an alert when the comparing result is indicative of a mismatch.

[0013] In some non-limiting implementations, the method further comprises: receiving a picture of the drug vial and a syringe provided with a syringe label; retrieving further information about the drug; and providing the picture and the further information for display.

[0014] In some non-limiting implementations, the method further comprises extracting further drug information from the syringe label by analyzing the picture using the opticalcharacter recognition method; comparing the further drug information to the given drug information, thereby obtaining a further comparison result; and outputting the further comparison result.

[0015] In some non-limiting implementations, the method further comprises extracting additional drug information from the vial label by analyzing the picture using the optical character recognition method; comparing the additional drug information to the given drug information, thereby obtaining an additional comparison result; and outputting the additional comparison result.

[0016] In some non-limiting implementations, the method further comprises: determining a volume of drug contained in the syringe by analyzing the picture; and outputting the volume of drug.

[0017] In some non-limiting implementations, the method further comprises: provided a medical form to be completed for display; and receiving information associated with the form from a user input device.

[0018] In accordance with another broad aspect, there is provided a system for verifying a medication to be administered to a subject, the system comprising: a processor; a non-transitory storage medium operatively connected to the processor, the non-transitory storage medium comprising computer-readable instructions; the processor, upon executing the instructions, being configured for: receiving a video of a drug vial provided with a vial label, the video comprising a plurality of video frames; extracting given drug information from the vial label by analyzing at least one of the video frames using an optical character recognition method, the given drug information comprising at least a drug name, an expiry date and a concentration; and providing for display the detected drug information.

[0019] In some non-limiting implementations the processor may be configured to: generate a user interface based on the detected drug information.

[0020] In some non-limiting implementations, the user interface may be one of a dose injection calculator prepopulated based on the detected drug information; a two-part injectioncalculator prepopulated based on the detected drug information; and a multi-dose injection calculator prepopulated based on the detected drug information.

[0021] In some non-limiting implementations, the step of detecting the given drug information comprises detecting a drug identifier from the vial label.

[0022] In some non-limiting implementations, the drug identifier comprises one of a national drug code and a drug identification number.

[0023] In some non-limiting implementations, wherein the processor is further configured for converting the given drug information into an audio signal using a text-to-speech method; and providing the audio signal for play back by a speaker.

[0024] In some non-limiting implementations, wherein the processor is further configured for receiving, from a microphone, an audio signal representative of the user reading aloud the displayed drug information; converting the audio signal into text using a speech recognition method; identifying further drug information from the text; comparing the further drug information to the given drug information, thereby obtaining a comparison result; and outputting an alert when the comparing result is indicative of a mismatch.

[0025] In some non-limiting implementations, wherein the processor is further configured for receiving a picture of the drug vial and a syringe provided with a syringe label; retrieving further information about the drug; and providing the picture and the further information for display.

[0026] In some non-limiting implementations, wherein the processor is further configured for extracting further drug information from the syringe label by analyzing the picture using the optical character recognition method; comparing the further drug information to the given drug information, thereby obtaining a further comparison result; and outputting the further comparison result.

[0027] In some non-limiting implementations, wherein the processor is further configured for extracting additional drug information from the vial label by analyzing the picture using the optical character recognition method; comparing the additional drug information to the givendrug information, thereby obtaining an additional comparison result; and outputting the additional comparison result.

[0028] In some non-limiting implementations, wherein the processor is further configured for determining a volume of drug contained in the syringe by analyzing the picture; and outputting the volume of drug.

[0029] In some non-limiting implementations, wherein the processor is further configured for provided a medical form to be completed for display; and receiving information associated with the form from a user input device.

[0030] In accordance with a further broad aspect there is provided a scanning support (500) for holding a labelled cylindrical article and a labelled tubular article for scanning of the labels or marks thereof by an overhead optical sensor, the scanning support comprising: a base (510) configured to stand on a support surface (S); a cross-shaped receptacle (520) extending from the base (510), the cross-shaped receptacle (520) including a saddle portion (524), configured to receive the labelled cylindrical article in abutment, and an access groove portion (526), extending across the saddle portion (524), the access groove portion (526) being leveled with or lower than the saddle portion (524) to access an underside of the labelled cylindrical article being received in the saddle portion (524); and one or more longitudinal receptacle (540) defined in the base (510) adjacently to the cross-shaped receptacle (520), the one or more longitudinal receptacle (540) including a trough portion (542) configured to receive the labelled tubular article in abutment, and an access recess portion (550) connected to a proximal end (544) of the trough portion (542) configured to access an underside of the labelled tubular article being received by the one or more longitudinal receptacle (540).

[0031] In some non-limiting implementations, the scanning support (500) further has a vertical plane symmetry extending from a proximal side (512) to a distal side (514) of the base (510), and the scanning support (500) being arranged such that each side thereof with respect to the vertical plane of symmetry is substantially mirrored.

[0032] In some non-limiting implementations, the vertical plane symmetry also intersects a center (521) of the cross-shaped receptacle (520).

[0033] In some non-limiting implementations, at least one of the saddle portion (524) and the access groove portion (526) is substantially V-shaped and wherein two walls forming the V-shape define an acute angle therebetween.

[0034] In some non-limiting implementations, the scanning support (500) further comprises an autofocus fiducial marker fixed to an upper planar surface (516) of the base (510) and located in the direct or indirect field of view of the overhead optical sensor.

[0035] According to still another broad aspect, there is provided a scanning and display station (600) for scanning a labelled cylindrical or tubular article and displaying an information related to the label thereof, the scanning and display station (600) comprising: a scanning support (500) as described above; a stand (610) extending upwardly from the base (510) of the scanning support (500) and having a lower end (612) connected to the scanning support (500) and an upper end (614); a housing (620) extending from the upper end (614) of the stand (610) at least partially over the scanning support (500); a light source mounted to the housing (620) and configured to illuminate the scanning support (500); an overhead optical sensor (660) mountable to the housing (620) and configured to collect data about the labelled cylindrical or tubular article; a plane mirror (670) mounted to the housing (620) configured oppositely to the optical sensor and inclined downwardly such that a secondary field of view of the optical sensor includes at least the cross-shaped receptacle (520) and the one or more longitudinal receptacle (540) of the scanning support (500); a processor operatively connected to the optical sensor for processing the collected data and generate an information about the labelled cylindrical or tubular article; and a display (680) mounted to the housing (610) and configured to provide the information about the labelled cylindrical or tubular article.

[0036] In some non-limiting implementations, the stand (610) extends from a distal side (514) of the base 510, and wherein the stand (610) has one or more opening (616) in-line with the one or more longitudinal receptacle (540) of the scanning support (500) and configured to fit therethrough the labelled tubular article along an axial direction of the article.

[0037] In another aspect there is provided a computer-implemented method for generating a user interface for verifying a medication at a user device, comprising: displaying, at a displaydevice of the user device, a user interface, the user interface comprising a first input control and a second input control; receiving, from a user input device of the user device, a user input corresponding to the first input control; determining, based on the user input to the first input control, a value for the second input control, the second input control corresponding to a volume of the medication; and updating, at the display device, the user interface based on the received user input corresponding to the first input control, and the determined value for the second input control.

[0038] In one or more embodiments, the user interface further may comprise a third input control populated by analyzing video data of a drug vial collected by a camera device, the third input corresponding to a concentration of the drug vial.

[0039] In one or more embodiments, the third input control may be populated by analyzing video data of a drug vial collected by a camera device by: extracting, at the processor, given drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames using an optical character recognition method, the given drug information comprising the concentration; and transmitting, from the processor to a display device, for display a user interface comprising the detected drug information.

[0040] In one or more embodiments, the first input control may correspond to a dose for the subject; and the determining the value for the second input control may be based on the first input control corresponding to the dose for the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

[0041] In one or more embodiments, the first input control may correspond to a weight of the subject; and the determining the value for the second input control may be based on the first input control corresponding to the weight of the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

[0042] In one or more embodiments, the user interface may comprise a syringe user interface element.

[0043] In one or more embodiments, the updating the user interface may comprise updating the syringe user interface element to display a filled portion proportional to the determined value for the second input control.

[0044] In one or more embodiments, the given drug information may comprise a drug identifier; and the third input control may be populated based on the drug identifier, the drug identifier determined based on a drug database.

[0045] In one or more embodiments, the user interface may further comprise a fourth input control corresponding to a dose threshold, the dose threshold may be determined based on the drug database.

[0046] In one or more embodiments, the updating the user interface may comprise updating the fourth input control to display a highlight portion when the determined value of the second input control exceeds the dose threshold.

[0047] In one or more embodiments, the second input control may comprise a first dose portion corresponding to a medication volume and a second dose portion corresponding to a solvent volume; and the determining the value for the second input control may comprise determining the first portion and the second portion.

[0048] In one or more embodiments, the updating the user interface may comprise updating the syringe user interface element to display a first filled portion proportional to the first dose portion and a second filled portion proportional to the second dose portion.

[0049] In one or more embodiments, the user interface may comprise a fifth input control corresponding to a number of injections.

[0050] In another aspect, there is provided a system comprising a memory, a camera device, and a processor, the processor configured to perform the methods described herein.TERMS AND DEFINITIONS

[0051] Terms and Definitions

[0052] In the context of the present specification, “computing device” is any computing apparatus or computer hardware that is capable of running software appropriate to the relevant task at hand. Thus, some (non-limiting) examples of computing devices include general purpose personal computers (desktops, laptops, netbooks, etc.), mobile computing devices, smartphones, and tablets, and network equipment such as routers, switches, and gateways. It should be noted that a computing device in the present context is not precluded from acting as a server to other computing devices. The use of the expression “a computing device” does not preclude multiple computing devices being used in receiving / sending, carrying out or causing to be carried out any task or request, or the consequences of any task or request, or steps of any method described herein. In the context of the present specification, a “client device” refers to any of a range of end-user client computing devices, associated with a user, such as personal computers, tablets, smartphones, and the like.

[0053] In the context of the present specification, the expression "computer readable storage medium" (also referred to as "storage medium” and “storage”) is intended to include non-transitory media of any nature and kind whatsoever, including without limitation RAM, ROM, disks (CD-ROMs, DVDs, floppy disks, hard drivers, etc.), USB keys, solid state-drives, tape drives, etc. A plurality of components may be combined to form the computer information storage media, including two or more media components of a same type and / or two or more media components of different types.

[0054] In the context of the present specification, a "database" is any structured collection of data, irrespective of its particular structure, the database management software, or the computer hardware on which the data is stored, implemented or otherwise rendered available for use. A database may reside on the same hardware as the process that stores or makes use of the information stored in the database or it may reside on separate hardware, such as a dedicated server or plurality of servers.

[0055] In the context of the present specification, the expression “information” includes information of any nature or kind whatsoever capable of being stored in a database. Thus, information includes, but is not limited to audiovisual works (images, movies, sound records,presentations etc.), data (location data, numerical data, etc.), text (opinions, comments, questions, messages, etc.), documents, spreadsheets, lists of words, etc.

[0056] In the context of the present specification, unless expressly provided otherwise, an “indication” of an information element may be the information element itself or a pointer, reference, link, or other indirect mechanism enabling the recipient of the indication to locate a network, memory, database, or other computer-readable medium location from which the information element may be retrieved. For example, an indication of a document could include the document itself (i.e. its contents), or it could be a unique document descriptor identifying a file with respect to a particular file system, or some other means of directing the recipient of the indication to a network location, memory address, database table, or other location where the file may be accessed. As one skilled in the art would recognize, the degree of precision required in such an indication depends on the extent of any prior understanding about the interpretation to be given to information being exchanged as between the sender and the recipient of the indication. For example, if it is understood prior to a communication between a sender and a recipient that an indication of an information element will take the form of a database key for an entry in a particular table of a predetermined database containing the information element, then the sending of the database key is all that is required to effectively convey the information element to the recipient, even though the information element itself was not transmitted as between the sender and the recipient of the indication.

[0057] In the context of the present specification, the expression “communication network” is intended to include a telecommunications network such as a computer network, the Internet, a telephone network, a Telex network, a TCP / IP data network (e.g., a WAN network, a LAN network, etc.), and the like. The term “communication network” includes a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared and other wireless media, as well as combinations of any of the above.

[0058] In the context of the present specification, the words “first”, “second”, “third”, etc. have been used as adjectives only for the purpose of allowing for distinction between the nouns that they modify from one another, and not for the purpose of describing any particular relationship between those nouns. Thus, for example, it should be understood that, the use ofthe terms “server” and “third server” is not intended to imply any particular order, type, chronology, hierarchy or ranking (for example) of / between the server, nor is their use (by itself) intended imply that any “second server” must necessarily exist in any given situation. Further, as is discussed herein in other contexts, reference to a “first” element and a “second” element does not preclude the two elements from being the same actual real-world element. Thus, for example, in some instances, a “first” server and a “second” server may be the same software and / or hardware, in other cases they may be different software and / or hardware.

[0059] Implementations of the present technology each have at least one of the above- mentioned object and / or aspects, but do not necessarily have all of them. It should be understood that some aspects of the present technology that have resulted from attempting to attain the above-mentioned object may not satisfy this object and / or may satisfy other objects not specifically recited herein.

[0060] Additional and / or alternative features, aspects and advantages of implementations of the present technology will become apparent from the following description, the accompanying drawings and the appended claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Having thus generally described the nature of the invention, reference will now be made to the accompanying drawings, showing by way of illustration example embodiments thereof and in which:

[0062] For a better understanding of the present technology, as well as other aspects and further features thereof, reference is made to the following description which is to be used in conjunction with the accompanying drawings, where:

[0063] FIG. 1 depicts a schematic diagram of a computing device in accordance with one or more non-limiting implementations of the present technology.

[0064] FIG. 2 depicts a schematic diagram of a communication system in accordance with one or more non-limiting implementations of the present technology.

[0065] FIG. 3A depicts a schematic diagram of a method for verifying a medication to be administered to a subject in accordance with one or more non-limiting implementations of the present technology.

[0066] FIG. 3B illustrates another method diagram for verifying a medication to be administered to a subject in accordance with one or more non-limiting implementations of the present technology.

[0067] FIG. 4 illustrates a first exemplary graphical user interface for displaying information about an identified drug, in accordance with one or more non-limiting implementations of the present technology.

[0068] FIG. 5 illustrates an exemplary graphical user interface to be presented to a user for taking a picture, in accordance with one or more non-limiting implementations of the present technology.

[0069] FIGs. 6A - 6B illustrates a second exemplary graphical user interface for displaying information about an identified drug, in accordance with one or more non-limiting implementations of the present technology.

[0070] FIG. 7 illustrates an exemplary form to input information, in accordance with one or more non-limiting implementations of the present technology.

[0071] FIGs. 8A - 8D illustrates an exemplary graphical user interface for providing access to an history of independent double checks, in accordance with one or more non-limiting implementations of the present technology.

[0072] FIG. 9 illustrates an exemplary graphical user interface for displaying information about an independent double check, in accordance with one or more non-limiting implementations of the present technology.

[0073] FIG. 10A illustrates a first exemplary calculator in the form of a dose injection calculator, in accordance with one or more non-limiting implementations of the present technology.

[0074] FIG. 10B illustrates a vial + syringe user interface, in accordance with one or more non-limiting implementations of the present technology.

[0075] FIG. 10C illustrates the vial and an associated syringe image capture used to populate calculator user interface in accordance with one or more non-limiting implementations of the present technology.

[0076] FIG. 10D illustrates several threshold conditions for atropine, in accordance with one or more embodiments.

[0077] FIG. 11A illustrates a view of a calculator user interface for a closed vial verification, in accordance with one or more non-limiting implementations of the present technology.

[0078] FIG. 1 IB illustrates a clickable title control of FIG. 11 A, in accordance with one or more non-limiting implementations of the present technology.

[0079] FIG. 11C illustrates a dosage recommendation user interface of FIG. 11 A, in accordance with one or more embodiments.

[0080] FIG. 12A illustrates a second exemplary calculator in the form of a two-part injection calculator, in accordance with one or more non-limiting implementations of the present technology.

[0081] FIG. 12B illustrates a first completed view of the second exemplary calculator from FIG. 12A, in accordance with one or more non-limiting implementations of the present technology.

[0082] FIG. 12C illustrates a second completed view of the second exemplary calculator from FIG. 12A, in accordance with one or more non-limiting implementations of the present technology.

[0083] FIG. 13 illustrates a completed view of a third exemplary calculator in the form of a multidose injection calculator, in accordance with one or more non-limiting implementations of the present technology.

[0084] FIG. 14 illustrates a completed view of a fourth exemplary calculator for preparing a single dose of a multi dose injection series, in accordance with one or more non-limiting implementations of the present technology.

[0085] FIG. 15A illustrates a fourth calculator for dilution of a drug, in accordance with one or more non-limiting implementations of the present technology.

[0086] FIG. 15B illustrates a user interface 1550 including an expired medicine warning, in accordance with one or more non-limiting implementations of the present technology.

[0087] FIG. 16 is a front perspective view of a scanning and display station, having a scanning support, in accordance with one or more non-limiting implementations of the present technology.

[0088] FIG. 17 is a left side elevation view of the scanning and display station shown in FIG. 16, in accordance with one or more non-limiting implementations of the present technology.

[0089] FIG. 18 is a right-side elevation view of the scanning and display station shown in FIG. 16.

[0090] FIG. 19 is a front elevation view of the scanning and display station shown in FIG. 16.

[0091] FIG. 20 is an enlarged sectional view taken along cross-section line B-B of FIG. 19, showing the scanning support having a base, a cross-shaped receptacle, and two longitudinal receptacles.

[0092] FIG. 21 is a sectional view taken along cross-section line A-A of FIG. 19, showing a stand, a housing, an overhead optical sensor, an inclined plane mirror and a display.

[0093] FIG. 22 is a schematic of the sectional view of FIG. 21, showing incident rays on the plane mirror and reflected rays towards the optical sensor.

[0094] FIG. 23 is a bottom perspective view of the scanning and display station shown in FIG. 16.

[0095] FIG. 24 is a photograph of the scanning and display station shown in FIG. 16, with the station being mounted atop a cart and connected to a powerline, in accordance with one or more non-limiting implementations of the present technology.

[0096] FIG. 25 is a photograph of the scanning and display station of FIG. 24 provided with an ultrasound probe, in accordance with one or more non-limiting implementations of the present technology.DETAILED DESCRIPTION

[0097] Various embodiments will now be described below to provide an example of the claimed subject matter. No example described below limits any claimed subject matter and any claimed subject matter may cover embodiments such as systems or methods that differ from those described below.

[0098] Furthermore, it will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the examples described herein. However, it will be understood by those of ordinary skill in the art that the examples described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the examples described herein. Also, the description is not to be considered as limiting the scope of the examples described herein.

[0099] It should also be noted that, as used herein, the wording “and / or” is intended to represent an inclusive-or. That is, “X and / or Y” is intended to mean X or Y or both, for example.As a further example, “X, Y, and / or Z” is intended to mean X or Y or Z or any combination thereof.

[0100] It should be noted that terms of degree such as "substantially", "about" and "approximately" as used herein mean a reasonable amount of deviation of the modified term such that the end result is not significantly changed. These terms of degree may also be construed as including a deviation of the modified term if this deviation would not negate the meaning of the term it modifies.

[0101] Furthermore, the recitation of numerical ranges by endpoints herein includes all numbers and fractions subsumed within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.90, 4, and 5). It is also to be understood that all numbers and fractions thereof are presumed to be modified by the term "about" which means a variation of up to a certain amount of the number to which reference is being made if the end result is not significantly changed.

[0102] Some elements herein may be identified by a part number, which is composed of a base number followed by an alphabetical or subscript-numerical suffix (e.g., 112a, or 1121). Multiple elements herein may be identified by part numbers that share a base number in common and that differ by their suffixes (e.g., 1121, 1122, and 1123). All elements with a common base number may be referred to collectively or generically using the base number without a suffix (e.g., 112).

[0103] The example systems and methods described herein may be implemented in hardware or software, or a combination of both. In some cases, the examples described herein may be implemented, at least in part, by using one or more computer programs, executing on one or more programmable devices comprising at least one processing element, a data storage element (including volatile and non-volatile memory and / or storage elements), and at least one communication interface. These devices may also have at least one input device (e.g., a keyboard, a mouse, a touchscreen, and the like), and at least one output device (e.g., a display screen, a printer, a wireless radio, and the like) depending on the nature of the device. For example, and without limitation, the programmable devices (referred to below as computing devices) may be a server, network appliance, embedded device, computer expansion module, apersonal computer, laptop, personal data assistant, cellular telephone, smart-phone device, tablet computer, a wireless device or any other computing device capable of being configured to carry out the methods described herein.

[0104] In some examples, the communication interface may be a network communication interface. In examples in which elements are combined, the communication interface may be a software communication interface, such as those for inter-process communication (IPC). In still other examples, there may be a combination of communication interfaces implemented as hardware, software, and a combination thereof.

[0105] Program code may be applied to input data to perform the functions described herein and to generate output information. The output information is applied to one or more output devices, in known fashion.

[0106] Each program may be implemented in a high-level procedural, declarative, functional or object-oriented programming and / or scripting language, or both, to communicate with a computer system. However, the programs may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language. Each such computer program may be stored on a storage media or a device (e.g., ROM, magnetic disk, optical disc) readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein. Examples of the system may also be considered to be implemented as a non-transitory computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner to perform the functions described herein.

[0107] Furthermore, the example system, processes and methods are capable of being distributed in a computer program product comprising a computer readable medium that bears computer usable instructions for one or more processors. The medium may be provided in various forms, including one or more diskettes, compact disks, tapes, chips, wireline transmissions, satellite transmissions, internet transmission or downloads, magnetic andelectronic storage media, digital and analog signals, and the like. The computer useable instructions may also be in various forms, including compiled and non-compiled code.

[0108] Various examples of systems, methods and computer programs products are described herein. Modifications and variations may be made to these examples without departing from the scope of the invention, which is limited only by the appended claims. Also, in the various user interfaces illustrated in the figures, it will be understood that the illustrated user interface text and controls are provided as examples only and are not meant to be limiting. Other suitable user interface elements may be used with alternative implementations of the systems and methods described herein.

[0109] Moreover, all statements herein reciting principles, aspects, and implementations of the present technology, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof, whether they are currently known or developed in the future. Thus, for example, it will be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the present technology. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo-code, and the like represent various processes which may be substantially represented in computer-readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0110] The functions of the various elements shown in the figures, including any functional block labeled as a "processor" or a “graphics processing unit”, may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. In one or more non-limiting implementations of the present technology, the processor may be a general-purpose processor, such as a central processing unit (CPU) or a processor dedicated to a specific purpose, such as a graphics processing unit (GPU). Moreover, explicit use of the term "processor" or "controller" should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specificintegrated circuit (ASIC), field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, conventional and / or custom, may also be included.

[0111] Software modules, or simply modules which are implied to be software, may be represented herein as any combination of flowchart elements or other elements indicating performance of process steps and / or textual description. Such modules may be executed by hardware that is expressly or implicitly shown.

[0112] With these fundamentals in place, we will now consider some non-limiting examples to illustrate various implementations of aspects of the present technology.

[0113] Computing device

[0114] Referring first to FIG. 1, there is shown a computing device 100 suitable for use with some implementations of the present technology, the computing device 100 comprising various hardware components including one or more single or multi-core processors collectively represented by processor 110, a graphics processing unit (GPU) 111, a solid-state drive 120, a random-access memory 130, a display interface 140, and an input / output interface 150. The computing device may further comprise a microphone, an electroacoustic transducer such as a speaker, a user input device such as a keyboard, a mouse, a touchscreen, and / or the like, etc.

[0115] Communication between the various components of the computing device 100 may be enabled by one or more internal and / or external buses 160 (e.g., a PCI bus, universal serial bus, IEEE 1394 “Firewire” bus, SCSI bus, Serial-ATA bus, etc.), to which the various hardware components are electronically coupled.

[0116] The processor 110 controls the operation of the computing device 100. The processor 110 can be any suitable processor, controller or digital signal processor that can provide sufficient processing power depending on the configuration, purposes and requirements of the computing device 100 as is known by those skilled in the art. For example, the processor unit 110 may be a general-purpose processor, e.g. a raspberry Pi device. In alternativeembodiments, the processor 110 can include more than one processor with each processor being configured to perform different dedicated tasks. The processor 110 may include a standard processor, such as an Intel® processor or an AMD® processor.

[0117] The GPU 111 may comprise one or more Graphic Processing Units (GPUs), such as but not limited to a Intel® or AMD® based GPU.

[0118] The random access memory 130 comprises software code for implementing an operating system, programs, databases, user interfaces such as those found in FIGs. 3 - 15 loaded from another storage device, for example solid-state drive 120.

[0119] The input / output interface 150 may be connected to multiple input or output devices. The input / output interface 150 may be coupled to a touchscreen 190 and / or to the one or more internal and / or external buses 160. The touchscreen 190 may be part of the display. In one or more implementations, the touchscreen 190 is the display. The touchscreen 190 may equally be referred to as a screen 190. In the implementations illustrated in FIG. 1, the touchscreen 190 comprises touch hardware 194 (e.g., pressure-sensitive cells embedded in a layer of a display allowing detection of a physical interaction between a user and the display) and a touch input / output controller 192 allowing communication with the display interface 140 and / or the one or more internal and / or external buses 160.

[0120] The display interface 190 may include an LED or LCD based display, and may be a touch sensitive user input device that supports gestures, as provided by touch input / output controller 192.

[0121] In one or more embodiments, the input / output interface 150 may be connected to a keyboard (not shown), a mouse (not shown) or a trackpad (not shown) allowing the user to interact with the computing device 100 in addition or in replacement of the touchscreen 190.

[0122] In one or more embodiments, the input / output interface 150 includes a camera device. This may include a camera device such as a video camera device or an image capture device. For example, the camera device may be a Sony® IMX sensor. The camera device mayinclude one or more lenses. The camera device may be capable of capturing both image data and video data. The camera device may capture video data including a plurality of video frames.

[0123] In one embodiment, the input / output interface 150 may include wired or wireless connection capabilities. The wired or wireless connection capabilities can include a radio that communicates using standards such as IEEE 802. I la, 802.11b, 802.11g, or 802.1 In. The wired or wireless connection capabilities may communicate with a network (e.g. network 230 in FIG. 2).

[0124] According to implementations of the present technology, the solid-state drive 120 stores program instructions suitable for being loaded into the random-access memory 130 and executed by the processor 110 and / or the GPU 111 for providing the methods and user interfaces described herein. For example, the program instructions may be part of a library or an application.

[0125] The computing device 100 may be implemented as a server, a desktop computer, a laptop computer, a tablet, a smartphone, a personal digital assistant or any device that may be configured to implement the present technology, as it may be understood by a person skilled in the art.

[0126] For example, the computing device 100 may be any two-way communication device with capabilities to communicate with other devices. A computing device 100 may be a desktop computer, mobile device, or laptop computer. A computing device 100 may be a mobile device such as mobile devices running the Google® Android® operating system or Apple® iOS® operating system. A computing device 100 may be the personal device of a user, or may be a device provided by an employer.

[0127] System

[0128] Referring to FIG. 2, there is shown a schematic diagram of a system 200, the system 200 being suitable for implementing one or more non-limiting implementations of the present technology. It is to be expressly understood that the system 200 as shown is merely an illustrative implementation of the present technology. Thus, the description thereof that followsis intended to be only a description of illustrative examples of the present technology. This description is not intended to define the scope or set forth the bounds of the present technology. In some cases, what are believed to be helpful examples of modifications to the system 200 may also be set forth below. This is done merely as an aid to understanding, and, again, not to define the scope or set forth the bounds of the present technology. These modifications are not an exhaustive list, and, as a person skilled in the art would understand, other modifications are likely possible. Further, where this has not been done (i.e., where no examples of modifications have been set forth), it should not be interpreted that no modifications are possible and / or that what is described is the sole manner of implementing that element of the present technology. As a person skilled in the art would understand, this is likely not the case. In addition, it is to be understood that the system 200 may provide in certain instances simple implementations of the present technology, and that where such is the case they have been presented in this manner as an aid to understanding. As persons skilled in the art would understand, various implementations of the present technology may be of a greater complexity.

[0129] The system 200 comprises inter alia a client device 210 associated with a user 205, and a remote service 220 communicatively coupled over a communications network 230.

[0130] Client Device

[0131] The system 200 comprises a client device 210 (e.g. computing device 100 in FIG. 1). The client device 210 is associated with the user 205. As such, the client device 210 can sometimes be referred to as a “computing device”, “end user device” or “client computing device”. It should be noted that the fact that the client device 210 is associated with the user 205 does not need to suggest or imply any mode of operation — such as a need to log in, a need to be registered, or the like.

[0132] The client device 210 comprises one or more components of the computing device 100 such as one or more single or multi-core processors collectively represented by processor 110, the graphics processing unit (GPU) 111, the solid-state drive 120, the random-access memory 130, the display interface 140, the input / output interface 150 and / or the like.

[0133] It will be appreciated that the client device 210 may be implemented as a server, a desktop computer, a laptop, a smartphone, a tablet, and / or the like.

[0134] In one or more implementations, the client device 210 is configured to execute a browser application. The purpose of the given browser application is to enable the user to access one or more web resources. How the given browser application is implemented is not particularly limited. Non-limiting examples of the given browser application that is executable by the client device 210 include Google™ Chrome™, Mozilla™ Firefox™, Microsoft™ Edge™, and Apple™ Safari™.

[0135] In one or more implementations, the user 205 may be a medical practitioner who is responsible for preparing a dose of a drug to be administered to a subject and / or for providing the drug to the subject.

[0136] Remote Service

[0137] A remote service 220 may include a database and one or more servers. The one or more servers may provide a web server that is accessed by the browser at device 210. The one or more servers may include an application server providing a application for providing the user interfaces described herein. The application server may send and receive information to the device 210 in conjunction with the web server. The application server may further provide an Application Programming Interface (API) to an application running on the device 210. The application servers may connect to the database of the remote service, and the database may respond to queries from the application servers with the requested information.

[0138] A remote service 220 is communicatively coupled the client device 210 via the communications network 230 but, in one or more alternative implementations, the remote service 220 may be directly coupled to the client device 210 without departing from the teachings of the present technology. Although the remote service 220 is illustrated schematically herein as a single entity, it will be appreciated that the database 220 may be configured in a distributed manner, for example, the database, web servers and application servers may have different components, each component being configured for a particular kind of retrieval therefrom or storage therein.

[0139] The database of remote service 220 may be a structured collection of data, irrespective of its particular structure or the computer hardware on which data is stored, implemented or otherwise rendered available for use. The database of remote service 220 may reside on the same hardware as a process (for example, the application server) that stores or makes use of the information stored in the database of the remote service 220 or it may reside on separate hardware. The database of remote service 220 may receive data from the client device 210 for storage thereof and may provide stored data to the client device 210 for use thereof.

[0140] In one or more implementations of the present technology, the database of remote service 220 is configured to store inter alia information about a plurality of drugs.

[0141] The remote service 220 may be a physical server, a virtual machine, or a container. The remote service 220 may be provided via Amazon Web Services (AWS®).

[0142] Communication Network

[0143] In one or more implementations of the present technology, the communications network 230 is the Internet. In one or more alternative non-limiting implementations, the communication network 230 may be implemented as any suitable local area network (LAN), wide area network (WAN), a private communication network or the like. It will be appreciated that implementations for the communication network 230 are for illustration purposes only. How a communication link 243 (not separately numbered) between the client device 210, the remote service 220, and / or another computing device (not shown) and the communications network 230 is implemented will depend inter aha on how each computing device is implemented.

[0144] The communication network 240 may be used in order to transmit data packets amongst the client device 210 and the remote service 220. For example, the communication network 240 may be used to transmit requests from the client device 210 to the remote service 220. In another example, the communication network 240 may be used to transmit requested information from the remote service 220 to the client device 210.

[0145] Method Description

[0146] FIG. 3 A depicts a flowchart of a computer- implemented method 300 for verifying a medication to be administered to a subject, in accordance with one or more non-limiting implementations of the present technology. In particular, the method 300 may provide for the generation of one or more user interfaces that assist a user with verifying a medication based on information stored in a database at a remote service.

[0147] The method 300 is to be executed when a prescribed dose of a drug is to be injected to a subject to ensure that the correct prescribed drug and the correct prescribed dose are injected to the subject. The medical practitioner who is in charge of preparing the prescribed dose accesses the medical file of the subject to know the given drug that was prescribed to the subject and the given dose. Before starting the preparing the prescribed drug dose, the medical practitioner executes the method 300. The method 300 may further include generating user interfaces such as those found in FIGs. 4-15. These user interfaces may be generated at a computing device for a user (i.e. using an application at the computing device), or alternatively may be generated at a remote service and transmitted to a computing device (i.e. in a browser).

[0148] In one or more implementations, the client device 210 comprises a processing device or unit such as the processor 110 and / or the GPU 111 operatively connected to a non- transitory computer readable storage medium such as the solid-state drive 120 and / or the random-access memory 130 storing computer-readable instructions. The processing device upon executing the computer-readable instructions, is configured to or operable to execute the method 300.

[0149] According to processing step 302, the processing device receives video data of a drug vial provided with a vial label. The medical practitioner takes a vial of drug that he / she believes correspond to the prescribed drug and positions the vial in front of a camera device in communication with the processing device so that the label of the vial substantially faces the camera. The label of the vial contains information such as the name of the drug, an identification (ID) of the drug, a concentration, an expiry date, and / or the like. The camera device records images of the vial, i.e., of the label of the vial, to generate the video data which is transmittedto the client device 210. The video data comprising a plurality of video frames which are sequentially or timely ordered, as known in the art.

[0150] According to processing step 304, the processing device extracting drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames of the video data using an optical character recognition method. The extracted drug information comprises at least a drug name, an expiry date and a concentration.

[0151] In some non-limiting implementations, the processing device is configured for detecting a drug identifier, an expiry date and a concentration from the vial label using the video data. The drug identifier may be a number or an alphanumerical code which is uniquely associated with a respective drug. For example, the drug identifier may be a national drug code, a drug identification number, or the like. In this case, the database of the remote service 220 comprises a plurality of drug identifiers stored thereon and for each drug identifier, a respective unique drug name. In this case, after extracting the drug identifier from the label, the processing device accesses the database of remote service 220 to retrieve the drug name associated with the extracted drug identifier from the video data. In an alternate embodiment, the processing device access an API of an application server of the remote service 220.

[0152] In some non-limiting implementations, the processing unit first analyses a first video frame to detect text therein. If no text is detected in the first video frame, a further video frame is analyzed. If text is detected within the first video frame, the processing unit extracts the text from the video frame. For example, ML KitTM may be used for detecting and extracting text from video frames. Once text has been detected and extracted, the processing unit analyses, using optical character recognition (OCR), the extracted text to determine whether the extracted text contains drug information such as a drug name or identifier, a concentration and an expiry date.

[0153] In some non-limiting implementations in which a drug is to be identified via a drug identifier having a predefined format (e.g., a series of a predefined number of alphanumerical characters and / or symbols), the processing unit searches from the extracted text a sequence of alphanumerical characters and / or symbols (e.g., letters and / or numbers) that match thepredefined format of a drug identifier. Alternatively, the processing unit may search for an acronym associated with the drug identifier, such as DIN representing Drug Identifier Number, and once the acronym DIN has been detected from the extracted text, the characters that follow the acronym DIN are considered to correspond to the drug identifier. For example, when a DIN comprises 8 characters such as 8 numbers and when the processing unit detects the acronym DIN in the extracted text, the 8 characters following the acronym DIN are considered as corresponding to the drug identifier. In some implementations in which the first character that follows the acronym DIN is this character is ignored, and the next 8 following characters are chosen as corresponding to the drug identifier.

[0154] The sample principles are applied for detecting and identifying the concentration and the expiry date form the extracted text. For example, a predefined character (such as “ / ”), a predefined character sequence (e.g., a predefined term, a predefined expression, a predefined acronym such as EXP, ml, etc.) or a predefined character and / or symbol format (such as 8 consecutive digits, two letters followed by 6 digits, two digits followed by “ / ” followed by 2 digits followed by “ / ” followed by 2 or 4 digits, etc.) may be searched by the processing unit for identifying an expiry date and the concentration.

[0155] It will be understood that any adequate method for identifying a drug name or identifier, an expiry date and a concentration from the extracted text may be used.

[0156] In some non-limiting implementations, the processing unit stops analyzing video frames as soon as drug information was successfully extracted from a given video frame.

[0157] In other non-limiting implementations, the processing unit analyzes a plurality of the video frames contained in the received video data to decease the risk of identifying a wrong drug, expiry date and / or concentration. If more than one drug name or identifier, expiry date and / or concentration is identified from the analysis of the video frames, the processing unit executes a voting method to select the given drug name or identifier, expiry date and / or concentration to be presented to the user. Taking the example in which the processing unit identifies two distinct drug identifies from the analysis of the video frames, the processing unit counts the number of times the first drug identifier has been detected from the video frames andthe number of times the second drug identifier has been identified from the video frames. The given drug identifier that has been identified the greatest number of times is chosen as being the correct drug identifier. The same voting method may be used when more than one expiry date and more than one concentration is identified from the video frames.

[0158] In some non-limiting implementations, the number of times an element (i.e., drug name or identifier, expiry date and concentration) is detected from the video frames is compared to a threshold. Once the number of times for a given element reaches the threshold, the processing unit stops analyzing the video frames for that element. For example, the threshold may be set to 5. In this case, once it has detected the same drug identifier, for example, in 5 different frames, the processing unit stops analyzing the video frames to identify the drug identifier and considers that the dug identifier identified 5 times is the correct one.

[0159] Referring back to FIG. 3A and according to processing step 306, the processing unit provides the determined drug information, i.e., the determined drug name, the expiry date and the concentration, for display. The processing unit may generate a user interface in which the determined drug information is inserted, and the interface is displayed on a display unit. The medical practitioner may then have a visual confirmation of the name of the drug and the concentration of the drug contained in the vial to ensure that the correct drug will be injected to the subject. The medical practitioner has also a visual confirmation of the expiry date of the vial to ensure that the drug is not expired.

[0160] In some non-limiting embodiments, the processing unit is further configured to generate a user interface based on the determined drug information.

[0161] For example, the generated user interface may provide to the user at the computing device a streamlined calculator such as the first calculator in FIGs. 10-11 that is pre-populated based on the determined drug information. The pre-population may include pre-populating the concentration of the drug vial identified in the determined drug information. The practitioner may then add an identifier associated with the practitioner themselves, a mass of the patient, other patient characteristics, etc.

[0162] In another example, the generated user interface may provide to the user at the computing device a two-part dose regimen calculator such as the second calculator in FIGs. 12A - 12C. The single dose regimen calculator may be pre-populated based on the determined drug information.

[0163] In another example, the generated user interface may provide to the user at the computing device a multiple dose regimen calculator such as the third calculator in FIGs. 13- 14.

[0164] In another example, the generated user interface may provide to the user at the computing device a drug dilution calculator such as the fourth calculator in FIG. 15.

[0165] In some non-limiting embodiments, the processing unit is further configured for comparing the identified expiry date to the actual date on which the drug is to be injected to determine if the drug is expired. In the event the drug would be expired, i.e., if the expiry date is anterior to the actual date, the processing may generate and output an alert to inform the medical practitioner that the drug is expired.

[0166] In some non-limiting embodiments, the method 300 further comprises a step of vocally providing the determined drug information to the medical practitioner. In this case, the processing unit is further configured to convert the determined drug information into an audio signal using a text-to-speech method and provide the audio signal to a speaker that will play back the audio signal to prove the medical practitioner with an audio mention of the determined drug information.

[0167] In some non-limiting implementations, the user, i.e., the medical practitioner, is requested to read aloud the displayed drug information to further reduce the risk of errors. In this case, the processing unit is further configured for receiving an audio signal from a microphone. The audio signal corresponds to the audio signal recorded by the microphone while the user is reading aloud the displayed drug information. The processing unit is then configured for converting the audio signal into text using a speech recognition method and identifying further drug information, i.e., a further drug name, a further expiry date and a further concentration, from the converted text. The processing unit then compares the further druginformation extracted from the audio signal to the drug information identified at step 304 to obtain a comparison result. If at least one element of the drug information does not match, i.e., if the drug name, the expiry date and / or the concentration determined at step 304 does not match the drug name, the expiry date and / or the concentration extracted from the audio signal, respectively, the processing unit generates and outputs an alert indicative of a mismatch, there by informing the user of a potential risk in the preparation of the drug dose. The processing unit may also provide for display the comparison result.

[0168] Once the correct drug, expiry date and concentration have been identified, the medical practitioner may collect a volume of drug (corresponding to a prescribed dose) from the vial using an injection syringe. It should be understood that a dilution of the drug may be required to obtain the desired dose. Once the syringe has been prepared, a label having the drug information printed thereon is usually stick on the syringe.

[0169] Since it regularly happens that the medication that will be used during the surgery is prepared in advance by a person other than the one who will administer the medications, the method 300 may further comprise additional steps to ensure that the correct drug will be administered to the subject. In this case, the medical practitioner places both the vial and the syringe in front the camera so that the vial label and the syringe label face the camera and a picture or a video of the vial and the syringe is captured. The processing unit then receives the captured video or picture from the camera. The processing unit then provides for display the received picture or a video frame of the received video. The processing may further access the database of remote service 220 and retrieves further information about the identified drug and provide the further information for display along with the picture. In an alternate embodiment, the processing may access an API of the application server of the remote service 220 to retrieves further information about the identified drug and provide the further information for display along with the picture.

[0170] In some non-limiting implementations, the method further comprises a step of comparing the drug information contained on the label of the syringe to the drug information extracted at step 304. In this case, the processing device is further configured to extract drug information from the syringe label appearing in the received picture using the above-describedmethod. The drug information extracted from the syringe label, i.e. the drug name, expiry date and concentration appearing on the syringe label, is compared to the drug information extracted at step 304 to determine if there is a match between the drug information extracted from the vial label and the drug information extracted from the syringe label. If there is a mismatch, e.g., if the name of the drug does not match, the processing device generates and outputs an alert. In some non-limiting implementations, the method further comprises a step of comparing the drug information of the vial label contained in the received picture to the drug information extracted at step 304, i.e., the first drug information extracted from the vial label at step 304, to ensure that the same vial was in the picture. In this case, the processing device is further configured to extract second drug information from vial label appearing in the received picture using the above-described method. The second drug information, i.e. the drug name, expiry date and concentration, is compared to the first drug information extracted at step 304 to determine if there is a match between the first and second drug information. If there is a mismatch, e.g., if the name of the drug does not match, the processing device generates and outputs an alert.

[0171] In some non-limiting implementations, the method further comprises a step of determining and providing for display the volume of drug contained in the syringe from the received picture. It should be understood that any adequate method to determine the volume of drug contained in the syringe from the received picture may be used. Some exemplary methods are described in the following.

[0172] For example, the processing unit may be configured to analyze the received picture in order to detect the graduated marks present on the syringe and the respective written volume (e.g., 1 ml, 2 ml, etc.) associated with the graduated marks. The processing unit then identifies the position of the distal end of the lunger of the syringe in the received picture and determines the volume of drug contained in the syringe by determining the relative position of the distal end of the lunger relative to the graduated marks.

[0173] In another example such as when the graduated marks are not present, the graduated marks are not visible in the received picture or no volume is associated with each graduated mark, the user may be requested to input the brand of the syringe. In that case, before taking the picture, the user is requested to position the syringe on a support provided with a diameter sensorconfigured to measure the diameter of the syringe. It should be understood that any adequate sensor adapted to measure the diameter of a syringe such as a mechanical sensor or an optical sensor may be used. The processor then receives the measured diameter of the syringe in addition to the picture. The processor accesses the database of remote service 220 which contains for each syringe brand and each syringe diameter of that brand, a respective total volume of the syringe and / or a volume associated with a graduated mark and retrieves the total syringe volume, or the graduated mark volume associated with the syringe brand and diameter. The processing device then determines the volume of drug contained in the syringe based on the received he total syringe volume or the graduated mark volume. In an alternate embodiment, the processor access an API of an application server of the remote service 220 to receive for each syringe brand and each syringe diameter of that brand, a respective total volume of the syringe and / or a volume associated with a graduated mark and retrieves the total syringe volume, or the graduated mark volume associated with the syringe brand and diameter.

[0174] When the processing device receives the total volume of the syringe, the processing device is configured to determine the volume of drug contained in the syringe using the length of the barrel of the syringe and the distance between the distal end of the plunger and the distal end of the barrel.

[0175] When the processing device receives the volume associated with a graduated mark of the syringe, the processing device is configured to determine the volume of drug contained in the syringe using the volume associated with a graduated mark of the syringe and the position of the distal end of the plunger relative tot eh graduated marks.

[0176] In a further example, a reference element having a predefined and known dimension such as a predefined and known length is placed next to the syringe before taking the picture of the syringe. In this case, the processing device is configured for measuring, based on the known dimension of the reference element, the distance between the distal end of the plunger and the distal end of the barrel and the diameter of the syringe to determine the volume of drug contained in the syringe.

[0177] In some non-limiting implementations, the method 300 further comprises a step of generating a form or retrieving the form from the remote service 220 and providing the form for display. The medical practitioner is then requested to complete the form. The information inputted by the medical practitioner is received by the processing device and stored in memory such as in the database of the remote service 220. An exemplary form is provided below.

[0178] In the following there is provided an exemplary implementation of method 300.

[0179] In some non-limiting implementations, the execution of the method 300 comprises three modes of operation to realize an independent double check (IDC). Each mode aims to integrate into the work process of medical practitioners so as not to disrupt their work habits. Sight, hearing and verbal communication are all components found in the normal procedure which are also integrated into the present method. Additional features may be offered to the user such as an IDC history stored in the database of the remote service 220 and a calculator for dose and dilution calculations.

[0180] Referring next to FIG. 3B and FIGs. 10 - 14 together, another computer method for generating a user interface for verifying a medication at a user device is provided.

[0181] At 352, displaying, at a display device of the user device, a user interface, the user interface comprising a first input control and a second input control.

[0182] At 354, receiving, from a user input device of the user device, a user input corresponding to the first input control.

[0183] At 356, determining, based on the user input to the first input control, a value for the second input control, the second input control corresponding to a volume of the medication,

[0184] At 358, updating, at the display device, the user interface based on the received user input corresponding to the first input control, and the determined value for the second input control.

[0185] In one or more embodiments, the user interface further may comprise a third input control populated by analyzing video data of a drug vial collected by a camera device, the third input corresponding to a concentration of the drug vial.

[0186] In one or more embodiments, the third input control may be populated by analyzing video data of a drug vial collected by a camera device by: extracting, at the processor, given drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames using an optical character recognition method, the given drug information comprising the concentration; and transmitting, from the processor to a display device, for display a user interface comprising the detected drug information.

[0187] In one or more embodiments, the first input control may correspond to a dose for the subject; and the determining the value for the second input control may be based on the first input control corresponding to the dose for the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

[0188] In one or more embodiments, the first input control may correspond to a weight of the subject; and the determining the value for the second input control may be based on the first input control corresponding to the weight of the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

[0189] In one or more embodiments, the user interface may comprise a syringe user interface element.

[0190] In one or more embodiments, the updating the user interface may comprise updating the syringe user interface element to display a filled portion proportional to the determined value for the second input control.

[0191] In one or more embodiments, the given drug information may comprise a drug identifier; and the third input control may be populated based on the drug identifier, the drug identifier determined based on a drug database.

[0192] In one or more embodiments, the user interface may further comprise a fourth input control corresponding to a dose threshold, the dose threshold may be determined based on the drug database.

[0193] In one or more embodiments, the updating the user interface may comprise updating the fourth input control to display a highlight portion when the determined value of the second input control exceeds the dose threshold.

[0194] In one or more embodiments, the second input control may comprise a first dose portion corresponding to a medication volume and a second dose portion corresponding to a solvent volume; and the determining the value for the second input control may comprise determining the first portion and the second portion.

[0195] In one or more embodiments, the updating the user interface may comprise updating the syringe user interface element to display a first filled portion proportional to the first dose portion and a second filled portion proportional to the second dose portion.

[0196] In one or more embodiments, the user interface may comprise a fifth input control corresponding to a number of injections.

[0197] In another aspect, there is provided a system comprising a memory, a camera device, and a processor, the processor configured to perform the methods described herein.

[0198] FIG. 4 illustrates an exemplary graphical user interface (GUI) that may be provided for display by the processing device.

[0199] The menu 5 allows for the medical practitioner to select one of the three modes of operation, i.e., IDC-stat, IDC-prep and IDC timeout.

[0200] The IDC-stat mode allows for the medical practitioner to read the vial label and validate the drug name, expiry date and concentration quickly by recording a video of the vial as described above. The drug information extracted from the video is displayed in the window 10 of the GUI.

[0201] The IDC-prep mode adds an additional verification step to the IDC-stat, i.e. a picture of both the syringe and the drug vial is acquired in order to check if the syringe is correctly identified and if the drug is the same as the one previously presented.

[0202] In the operating room or any healthcare area, it regularly happens that the medications that will be used during the operation are prepared in advance by a person other than the one who will administer the medications. Compared to the IDC-stat mode, the medical practitioner who prepares the medication is not in an emergency. The medical practitioner can therefore prepare several syringes one after the other. To prepare the syringes, this requires dilution of the medicine according to procedures predefined by the hospitals. Before the operation, the medical practitioner who will administer the medications can validate the contents of the syringes by checking the history.

[0203] The IDC-timeout is the third mode available for IDC. The IDC-timeout mode represents all the checks that must be carried out before to have a complete and successful IDC.

[0204] In the window 1 of the GUI illustrated in FIG. 4, the reference number assigned to an IDC is provided. This reference number is used to identify the current IDC. This number, combined with the date, represents a unique playback identifier and helps identify the IDC playback in history.

[0205] The button 2 corresponds to a voice playback button. This button 2 allows the medical practitioner to enable or disable voice playback in the application. Certain events may trigger voice playback. When detecting the drug, the application may dictate the name of the detected drug and its concentration and / or expiry date. When detecting the expiration date, the application will dictate this date and specify if it has passed, therefore expired. When the volume of the drug contained in the syringe is determined, the application may also dictate the calculated volume. By default, this button may be enabled.

[0206] The button 3 corresponds to an alarm button: This button turns the reading alarm on or off. When the drug name, expiry date and concentration have been determined, the application will make a sound. Two types of sounds may be available: one to indicate asuccessful reading (for example, the expiry date has not passed) and another to indicate a failed reading (for example, when the medicine is expired). By default, this button may be enabled.

[0207] The button 4 corresponds to an instruction playback button. This button allows the medical practitioner to activate or deactivate the voice reading of instructions in the application. During steps where the user needs to show the vial for IDC and / or the vial and syringe to the camera, the instructions displayed on the screen will be read aloud to the medical practitioner. By default, this button may be enabled.

[0208] Reference element 6 identifies a volume calculator: For some medications whose concentration is displayed in units per volume, it is possible to use the calculator to help calculate the needed volume to be extracted from the vial. The medical practitioner is requested to input the desired dose, and the processing device automatically calculates the volume of drug needed.

[0209] The text box 7 is used for optionally inputting the practitioner ID number.

[0210] In some non-limiting information, once the drug has been identified, the processing device may retrieve further information about the drug from the database of remote service 220 (either directly from the database or through an API call to the application server) and display this further information in the window 8 and 9. For example, the window 8 may be used for displaying the drug family to which the identified drug belongs. A color dot may also be displayed, the color representing the drug family. Additional information about the identified drug may be accessible in the window 9. In some implementations, the window 9 may be replaced with a menu.

[0211] The window 10 is used to display a label that comprises the name of the identified drug, its expiry date and its concentration. The color of the label corresponds to the color of the drug family.

[0212] When a problem occurs during an IDC, an error message is displayed in the window 10 indicating what appears to have been the cause of the error. When an error occurs, several icons may change in the interface. For example, the IDC stage icon may have an additional redX icon. The B tablet corresponding to the analysis carried out may turn red and have an X inside.A red error message may appear.

[0213] Possible errors comprise:

[0214] a. Expired drug

[0215] b. Drug not listed in the database

[0216] c. Drug associated with the syringe different from the vial drug

[0217] d. Wrong label on the syringe

[0218] e. Overdosed medication using the calculator

[0219] The button 12 corresponds to a cancel button. At any time, it is possible to cancel the IDC currently performed. This button will cause the Reference No. to be cleared and the current IDC to be completely cleared from the history.

[0220] Button 13 corresponds to a next step button. As its name indicates, this button allows a user to move on to the next step.

[0221] A picture 14 of the drug vial is also included in the GUI.

[0222] Icons 15 are displayed on the right of the GUI to indicate the progression of the IDC. When an icon 15 is gray with a question mark and pulses blue, this means that the system is waiting for information. When an icon 15 is green with a check mark, this means that the corresponding step was successfully performed, and that the information appears to be correct. If an icon 15 is red with an X, this means that there was a problem during its corresponding step (e.g., expired drug).

[0223] In some non-limiting implementations, the processing device may be configured to control alight present in the surgery room. The processing device may turn on the light to indicate to persons present in the room that a task is in progress to avoid any interruption of the task.

[0224] In some non-limiting implementations, when opening the application, the camera performs an autofocus in order to always have a clear image when placing the vials in front of the camera.

[0225] By choosing the IDC-prep mode, a new step is proposed to the medical practitioner, which consists in leaving a trace in the history of the drug that will be injected and the syringe that will be used (with its appropriate label).

[0226] In this mode, the medical practitioner is requested to place the vial used to fill the syringe in front of the camera, ensuring that the vial label is clearly visible to the camera, as illustrated in the exemplary graphical user interface illustrated in FIG. 5. Then, medical practitioner is requested to place the syringe also in front of the camera, with the label also visible to the camera. Once this is done, the medical practitioner is requested to input his practice ID number. If the number is not filled in, the procedure may be prevented from being performed. Finally, the medical practitioner clicks a button to take a photo, which will save the photo to the database or file system of the remote service 220 and allow the medical practitioner to continue.

[0227] Subsequently, the medical practitioner is taken to a page that shows the information about the identified drug and provides a calculator, as illustrated in FIGs. 6A-6B and 10A-15B. In addition, it is at this step that the medical practitioner will be able to see the photo they have just taken.

[0228] In the IDC-timeout mode, the medical practitioner is presented with a from to be completed, such as the form illustrated in FIG. 7. This form 700 represents all the checks that must be carried out before to have a complete and successful IDC. The medical practitioner may be requested to input the following information: the prescription 702, whether allergies have been checked 704, Telemetry 706, validation of the prescription 708, the dose 710, the method of administration 712, the administration time 714, the prescriber 716, the subject ID number 718, the subject date of birth 720 and / or the subject weight 722.

[0229] In some non-limiting implementations, a history of IDCs is generated and stored in the database of the remote service 220. The history comprises, for each performed IDC, the pictures, the identified drug information and the inputted information obtained during an IDC.The history may be used to confirm that any medications that have been prepared in advance have been checked before a medical procedure. By having this history, it is possible to ensure that each step of the IDC has been scrupulously followed, thus reducing the risk of medical errors. In addition, this history makes it possible to trace actions in the event of doubt or incident, providing a clear and detailed trace of the use of medications. This not only contributes to patient safety, but also transparency and accountability in medical processes, allowing clinicians to quickly and efficiently verify compliance with current protocols.

[0230] FIGs. 8 - 8D illustrates an exemplary GUI that may be provided to a user to access the history of IDCs. The user may have access to the list of all IDC readings previously performed. Each row in this list represents a different IDC. The information of each IDC is divided as follows in this line:

[0231] Ref Number 802 represents the reference number of the specific DVT

[0232] Drug Name 804 represents the name of the drug that has been associated with the specific DVT

[0233] DVI Type 806 indicates the type of IDC to which the specific IDC belongs, i.e., IDC-stat, IDC-prep or IDC-timeout.

[0234] Success 808 indicates whether the specific IDC was a success (green) or a failure (red).

[0235] Date & Time 810 represents the date and time at which this specific IDC was performed.

[0236] By clicking on a given IDC, all information about the IDC may be accessed such as all pictures, identified drug information and inputted information related to the IDC, as illustrated in FIG. 9.

[0237] Referring next to FIGs. 10A - 15B together, the dilution and dose calculators may allow users to quickly confirm whether the previously calculated dose and dilution match the response on the computing device. This may help reduce medication errors by assistinghealthcare professionals in minimizing dose errors. The user interfaces of FIGs. 1 OA - 15B may be provided in an application at the computing device, or alternatively may be provided using a web interface that a browser on the computing device accesses.

[0238] The user interface of the calculators may include easy to read information and visualizations for the users that is based on automatically determined medication data collected using a camera device, including of a medication vial.

[0239] There may be 3 different tabs for different operations: a quick calculator (e.g. FIG. 10A and 11 A), a single dose calculator (e.g. FIG. 12A - 12C), and a multi-dose calculator (e.g. FIG. 13 - 14). At the beginning of each camera scan, the professional’s identifier and the patient's weight may be entered. It may be possible to click on the lock icon to keep these values the same for the next scans.

[0240] Referring next to FIG. 10A, there is shown a first exemplary calculator user interface 1000 in the form of a dose injection calculator, in accordance with one or more nonlimiting implementations of the present technology.

[0241] As described above, the user at the computing device may be provided with a calculator user interface 1000. FIG. 10A illustrates a first exemplary calculator including a dose injection calculator 1004. User interface 1000 may be for a closed vial verification interface identified in tab 1016. In an alternate embodiment shown in FIG. 10B, a vial + syringe tab 1018.

[0242] The calculator user interface 1000 includes an image captured of the vial 1006, a calculator 1004, a volume control 1002, a dose control 1008, a concentration control 1010, a weight based dose 1012, a syringe user interface control 1014,

[0243] With this calculator, the user is able to calculate the correct volume to take from the vial of the medication. The user is asked to write the concentration of the medication in the concentration control 1010 and the desired dose in the dose control 1008. The processing device then calculates the corresponding volume and populates that volume control 1002 which is displayed to the user and advantageously provides a clear indication whether the corresponding weight based dose populated in weigh based dose control 1012 is within a threshold.

[0244] As shown, the “Concentration” refers to the concentration determined when the vial is detected by the camera device. The identified concentration may be automatically populated in the concentration control 1010. This may be done based on an image recognition of the image capture of the vial 1006 as described herein.

[0245] “Dose” may refer to a user-submitted number corresponding to the desired dose (populated within dose control 1008) and separately the dose / kg (populated within weight- based dose control 1012 may be provided to the user to review based on the recipient of the injection.

[0246] “Volume to be drawn” may refer to the determined volume to be injected to reach the user-submitted dose and populated within volume control 1002. The determined volume may be calculated using the following formula:Dose— - ■_ — = VolumeConcentration

[0247] The “Dose / kg” may refer to a determined weight-based dose (i.e. in mg per kg of the patient’s mass or weight) determined based on the patient's weight in the “Patient's weight (kg)” box. The “dose / kg” may be populated in the weight-based dose control 1012. The user may themselves directly modify the dose / kg value in the weight- based dose control 1012, which adjusts the dose in the dose control 1008 and thus the volume in the volume control 1002 to be drawn. A dose limit based on weight may have a corresponding threshold derived from the literature. In this case, if the determined weight-based dose 1012, i.e. “Dose / kg”, is exceeded (or conversely, deviates from the threshold), the user interface may automatically change the weight-base control 1012 (e.g. see FIG. 11) to highlight it so that it, for example, appears red if this threshold is exceeded (or conversely, simply deviated from significantly). Other types of user interface highlighting may be used. This highlighting of the weight-based dose may clearly identify to the user that the numerical dose 1012 it a risk to the recipient based on the recipient’s weight. In an alternate embodiment, the highlighting of the weight-based does field may also include an alert to the user as described herein. In either case, the highlighting or alert threshold may be triggered according to one or more safety criteria of the medication. This may further include safety criteria based on the patient's weight, age and local practices. For example, referring to FIG. 10D there is shown safety thresholds 1080 for an example medication atropine,a drug used in emergency situations. The safety thresholds 1080 may include an overdose threshold 1082, a cumulative overdose threshold 1084, an age adjustment threshold 1086, and an under dosage threshold 1088.

[0248] The overdose threshold 1082 may generate an overdose alert in the user interface. The overdose threshold 1082 may be triggered when a user enters a single dose of medication (in mg / kg), and a visual indicator may be active if the dose exceeds the safe limit. For example, for atropine, a dose greater than 0.5 mg per injection may results in a highlighting in the user interface by way of change in the color of the mg / kg input control to red, indicating a unit overdose.

[0249] The cumulative overdose threshold 1084 may generate a cumulative overdose alert in the user interface. The threshold 1084 may be triggered where multiple doses are administered at short intervals. This may be based on records received for the patient from a database, based on the patient identifier. For example: a correct single dose may be given, but may be repeated every 5 minutes and thus may exceed the maximum cumulative dose (0.5 mg in this case) for a given time period. A bandage alert highlight (similar to that for expired medications) may be displayed under the syringe control on the calculator in such a situation, informing that the cumulative doses are potentially toxic.

[0250] The age adjustment threshold 1086 may trigger an age adjustment alert in the user interface. The adjustment alert may indicate that the overdose threshold 1082 or cumulative overdose threshold 1084 is adjusted based on the patient's age (adult, adolescent, child). For example, in one situation for adolescents, the adult dose may apply. The same overdose threshold 1082 or underdose thresholds 1088 may be recalculated according to the appropriate scaled value associated with the age adjustment threshold 1086, with a visual indication on the relevant user interface controls where the thresholds have changed based on the patients age.

[0251] The under dosage threshold 1088 may generate an under dosage alert in the user interface. This may include when the dose entered is below the minimum threshold of efficacy. The user interface may display a visual indication including for example a highlight of the mg / kg field so that it turns a particular color, e.g. pale blue, indicating that the dose may beineffective or cause a paradoxical effect (e.g., atropine in too low a dose that can slow down the heart instead of speeding it up).

[0252] Referring next to FIG. 10B, there is shown an embodiment of a vial + syringe user interface 1030. The vial + syringe interface 1030 may include an image collected of a vial and a syringe 1032. In one embodiment, as shown in interface 1000, the vial alone may be captured in an image and used with calculators in FIGs. 10A, 11A - 15B. In another embodiment, the vial and an associated syringe may be captured in an image and used with calculator 1060 in FIG. 10C.

[0253] Referring next to FIG. 11 A, there is shown a view of a calculator user interface 1100 for a closed vial verification, in accordance with one or more non-limiting implementations of the present technology. The user interface 1100 may include a quick calculator 1104 and may include an image collected of the vial 1102. Additionally, the user interface 1100 may include a title control 1106 including data determined as described herein from the image of the vial 1102. The title control 1106 may be clickable to provide more information (e.g. FIG. 1 IB) based on a request to a database including a drug identifier determined from the image of the vial 1102.

[0254] The syringe control 1108, or another user interface control may be selectable or clickable to display a dosage recommendation for the identified vial 1102 (e.g. FIG. 11C). Prior to a user entering a dose within the calculator, the user may consult the dosage recommendations according to the standards associated with the medication in a database. By selecting the syringe control 1108 or another user interface control, a suggested dose 1182c, a suggested volume 1182b, and a suggested weight-based dose 1182a may appear for the concentrations detected on the ampoule of the drug concerned. This suggestion mode 1180 may allow for quick checking, which may be particularly useful if the fields are left blank or if the entered doses are outside the usual ranges.

[0255] Referring next to FIGs. 12A to 12C together, there is shown a second user interface in the form of a two-part injection calculator 1204, in accordance with one or more non-limitingimplementations of the present technology. As shown in FIG. 12A a calculator may be provided that determines the necessary volumes of medication, solvent, and a total volume.

[0256] “Diluted Concentration” may refer to the determined diluted concentration identified when the camera device scans the medication vial. The diluted concentration may pre-populated based on the determined diluted concentration control 1202 from the medical vial scan. This user interface control 1202 may be manually modified by the user, and may provide visual feedback (e.g. it may be highlighted as shown in FIG. 12C). When this user interface control 1202 is modified, the corresponding volume of medication 1206, solvent 1208, and the total volume 1210 may be adjusted.

[0257] “Dose”, this user interface control 1212 may be user-submitted according to the desired dose, and may be used to determine the volume of medication 1206, solvent 1208, total volume 1210, and weigh-based dose 1214.

[0258] “Medication” 1206, “Solvent” 1208, “Total” 1210 may be determined as described herein. The user interface 1200 may provide the determined volumes for medication 1206, solvent 1208, and the total volume 1210 in the user interface controls as shown and provide them to a user. The values for medication, solvent, and total volumes of the two-part dose that are populated in the user interface controls may be determined as follows:VolU n.eoivent Volwnefg^^ V olwne Medication

[0259] “Dose / kg” 1214: This user interface control may be determined automatically when the user submits the patient's weight in the “Patient's weight (kg)” user interface control 1216. The user may manually modify the weight-based dose value in the user interface control 1214, which automatically adjusts the dose control 1212 and thus the controls for volume of medication 1206, solvent 1208, and total volume 1210. A dose threshold based on weight maybe derived from the literature, and the “Dose / kg” weight-based user interface control may be highlighted (e.g. FIG. 12C) if the threshold is exceeded (or if it deviates substantially from the threshold). For example, the user interface control 1214 may be highlighted red if the threshold is exceeded (or if it deviates substantially from the threshold).

[0260] The syringe user interface control 1218 may be displayed with a portion corresponding to the medication 1206 and a portion corresponding to the solvent 1208. The display of the syringe user interface control 1218 may be displayed proportionally to the amounts of the portion corresponding to the medication 1206 and the portion corresponding to the solvent 1208, i.e. as the ratio changes, the display proportion changes. The display proportion of the syringe control 1218 may have two colours or patterns, or other visual representations.

[0261] In another example, the calculator may take into account dilution. In this case, the user may be requested to indicate if the dilution is for a single dose syringe (or single dose to inject) or for a multi dose syringe when a syringe with diluted medication that can be administered several times over a chosen period of time. For the single-dose syringe, the calculator may indicate to the user how to make the dilution and inject the patient. The user is requested to input the dose 1212 and the concentration 1202 with the desired dose to inject and the desired concentration after dilution. Once inputted, the calculator calculates the volume of undiluted medication 1206 to add to the syringe, the volume of diluting liquid 1208 to add to the syringe as well, and the final total volume 1210 the syringe should hold for injection.

[0262] Referring next to FIG. 13 and 14 together, a multi-step calculator user interface 1300 may be provided. The first step tab 1312 may show the calculator 1302 for determining the dose to inject (FIG. 13), and a second step tab 1314 may show the calculator 1402 for determining the number of injections (FIG. 14). For preparing a multidose syringe, the user is requested to input the Sample Volume user interface control (which corresponds to the total, undivided dose that he wishes to give), the Desired Concentration and the dose to be injected for each injection. So, when the user has the Sampled Volume and the Desired Concentration filled, the calculator automatically calculates the necessary volume of dilution liquid to add tothe syringe. Finally, when the user is requested to input the Dose to Inject, the calculator will automatically calculate the volume that he must inject during each injection.

[0263] Referring next to FIG. 13, there is shown a completed view of a third user interface 1300 including a calculator 1302 in the form of a multidose injection calculator, in accordance with one or more non-limiting implementations of the present technology.

[0264] “Diluted Concentration” 1304: When the user scans the medication vial using the camera device and medication information is determined, the identified concentration may be automatically pre-populated in this user interface control. The user interface control 1304 may be manually modified by the user. In this case, the user modification results in a highlighting of the user interface control 1304. For example, the user highlighting may include changing the color of the control 1304 to yellow. When a user modification is made, the controls for volume of medication 1306, and the weight-based dose 1310 may be automatically adjusted. The concentration 1304 may not be changed to a value higher than the original concentration on the vial. The diluted concentration is permitted to be reduced only the results below the reading on the vial.

[0265] “Dose to inject” 1308 may be a user interface control for user submission according to the desired dose for each injection. When a user modification is made, the controls for volume of medication 1306, and the weight-based dose 1310 may be automatically adjusted.

[0266] “Dose / kg” 1316: This user interface control may be automatically determined when the patient's weight or mass in the “Patient's weight (kg)” box is filled. The user may manually modify the dose / kg value 1310, which adjusts the dose 1308 and thus the volume 1306 to be drawn. A dose threshold based on weight may be derived from the literature, and the “Dose / kg” control 1310 may be highlighted if the threshold is exceeded (or alternatively if there is substantial deviation from the threshold). For example, the highlighting may include changing the color of this user interface control to red if this limit is exceeded (or substantially deviated from).

[0267] Referring next to FIG. 14, there is shown a second completed view 1400 of a calculator 1402 for preparing a single dose of a multi dose injection series, in accordance withone or more non-limiting implementations of the present technology. In this second stage, a volume to inject the recipient is determined.

[0268] The “Number of injections” 1404 user interface control may be determined based on the number of injections in the syringe. This information may be determined based on the scan of the medication vial by the camera device, e.g. the collected image 1406.

[0269] “Medication” 1408, “Solvent” 1410, “Total” 1412 user interface controls may be determined as described herein to identify the volumes necessary to reach the user- submitted dose 1414. This may be done as follows:DoseVolumeTotalinjectionsCocentrationdnutedDoseVolumeMedication Concentrationorig .naiinjectionsVolU n.eoivent Volwnefg^^ V olwne Medication

[0270] “Diluted Concentration” 1416 user interface control: When the user scans the medication vial using the camera device and medication information is determined, the identified concentration may be automatically pre-populated in this user interface control. The user interface control 1416 may be manually modified by the user. In this case, the user modification results in a highlighting of the user interface control 1416. For example, the user highlighting may include changing the color of the control to yellow. When a user modification is made, the volume of medication 1408, solvent 1410, and the total volume 1412 may be automatically adjusted.

[0271] “Dose to inject” 1414 user interface control may be a user-submitted number corresponding to the dose per injection.

[0272] “Volume to inject” 1412 user interface control for each injection of a multidose injection may be determined automatically as follows:Dose= VolumeConcentration

[0273] Referring next to FIG. 15 A, there is shown a user interface 1500 including a calculator 1502 for dilution of a drug, in accordance with one or more non-limiting implementations of the present technology.

[0274] Referring next to FIG. 15B, there is shown a user interface 1550 including an expired medicine warning 1552. The collected drug vial image 1554 may have drug identifier information determined as described herein. The drug identifier from the vial image 1554 may be used to look up drug expiry information in a database.

[0275] In an alternate embodiment, a drug expiry date may be determined as described herein based on the collected vial image 1554.

[0276] In either case, a warning 1552 may be presented in the user interface 1550 to warn the user that the medication may have expired.

[0277] In another embodiment, a warning may be shown based on a lookup associated with the patient receiving the medication. This may be performed by looking up a medication history (e.g. FIGs. 8A-8D) for a patient and generating a warning if the patient has previously received the same medication within, for example, a predetermined threshold, or the medication regimen prescribed by the physician. These warnings may be determined further based on the weightbased dosing information generated by the calculator, and other relevant information provided in the patient record or the medication record.

[0278] In the following, there is described a scanning and display station that may be used to implement the above-described method and system.

[0279] The present disclosure describes a scanning and display station for scanning labelled cylindrical or tubular articles, for instance for scanning medical vials and syringes in the context of a double independent verification anesthesia protocol (hereinafter, "DIV"). This said, any cylindrical or tubular article displaying a label or a mark with relevant information is envisioned herein as the subject of the scanning and display station. Indeed, although the terms "label" and"labelled" are presently used, the present disclosure is not limited to labels but encompasses any markings of interest on the article. The scanning and display station also aims to process data collected from the article and display information about the scanned article, for example to a healthcare professional. Reference is repeatedly made to the healthcare and anesthesiology field with respect to the station and its support for illustrative purposes.

[0280] With reference to the drawings, FIGS. 16 to 25 show an exemplary and non- limitative embodiment of the scanning and display station 600 (hereinafter, the "station"). The station 600 shown includes a scanning support 500, a housing 620 to shelter a light source, an optical sensor, a plane mirror 660, a processor, and a stand 610 to vertically space apart from the housing 620 from the scanning support 500. In brief, the scanning support 500 is adapted to hold a labelled cylindrical article (e.g., a vial) and / or a labelled tubular article (e.g., a syringe) during a scanning sequence involving by the optical sensor.

[0281] The Scanning Support 500

[0282] Drawing attention to the embodiment of the scanning support 500 shown in FIGS. 16 to 25, to ensure that outputs of the scanning sequence are consistent and reliable, the scanning support 500 advantageously allows to hold corresponding labelled articles in the field of view of the optical sensor according to a preset position, orientation and distance relative to the optical sensor. It's understood that controlling the spatial parameters of the desired article to be scanned relative to the optical sensor can improve the scanning sequence and the overall DIV procedure since the user can introduce the articles in an intuitive manner guided by the configuration of the scanning support 500. Also, the optical sensor can capture and collect label data more quickly by bypassing or shortening, at least partially, the autofocus time of the article. The image recognition processing time executed by the processor can also be shortened.

[0283] The scanning support 500 can include a base 510, a cross-shaped receptacle 520 and a longitudinal receptacle 540. Base 510 is configured to stand on a support surface S, such as a planar supporting surface of a medical cart as illustrated in FIG. 24. According to an alternative embodiment (not shown), the base 510, and particularly a lower surface thereof, can be adapted to mount a correspondingly shaped support surface.

[0284] Referring more particularly to the top plan view of the scanning support 500 shown in FIG. 20, the cross-shaped receptacle 520 and the longitudinal receptacle 540 are respectively configured to receive in abutment thereon a cylindrical article (e.g., a vial) and a longitudinal receptacle (e.g., a syringe) for a scanning sequence. Both the cross-shaped receptacle 520 and the longitudinal receptacle 540 are connected to the base 510, as explained in more details below.

[0285] In the embodiment shown, the cross-shaped receptacle 520 and the longitudinal receptacle 540 are interconnected to form a continuous cross-shaped recess. In the embodiment of FIGS. 16 to 25, the cross-shaped receptacle 520 protrudes upwardly from the base 510 and is located about a middle section of said base 510.

[0286] More specifically, the cross-shaped receptacle 520 includes a saddle portion 524 and an access groove portion 526. The saddle portion 524 provides a recess that extends along a direction from a proximal side 512 to a distal side 514 of the base 510. The access groove portion 526 extends across and orthogonally to the saddle portion 524, hence the "cross-shape" of the cross-shaped receptacle 520. According to an alternative embodiment, the location and orientation of the saddle portion 524 and the access groove portion 526 can be interchanged such that the access groove portion 526 extends along the proximal-distal direction of the base 510 and the saddle portion 524 extends across thereof.

[0287] The terms "proximal" and "distal" use as a reference point a normal position of a user with respect to station 600. For instance, referring to FIG. 20, the bottom side of the drawing corresponds to the proximal side 512 and the top side of the drawing corresponds to the distal side 514. It is apparent to one skilled in the art that the station embodiment of FIGS. 16 to 25 is arranged to mostly accommodate a user operating the station 600 from a proximal side 512.

[0288] Saddle portion 524 can be configured to receive the cylindrical article in abutment therein and the access groove portion 526 can be configured to allow or facilitate access to an underside of the labelled cylindrical article being received in the saddle portion 524. For instance, according to one mode of use, the cylindrical article is placed in the saddle portion524 by the user. Assuming that the label does not face upwardly towards the optical sensor or that the label extends along the circumference of the article such that a portion thereof is hidden from the field of view of the optical sensor, the user can rotate the article along its longitudinal axis (advantageously while maintaining the article in the saddle portion) by handling the curved surface of the article until the label is appropriately exposed to the optical sensor overhead.

[0289] It should be understood that the shape and size of the saddle portion 524 and the access groove portion 526 can be substantially identical, as provided by the embodiment of the scanning support 500 of FIGS. 16 to 25. In such embodiment, the function of the saddle portion 524 and the access groove 520 can be interchangeable in that the access groove portion 526 can be used to receive the cylindrical article in abutment while the saddle portion 524 as shown can be used to handle the cylindrical article received by the saddle portion 524. It's understood that depending on the orientation of the cylindrical article, the optical sensor is configured correspondingly to read the label as such.

[0290] Referring to the cross-section shape as better shown in FIGS. 19 and 21, the saddle portion 524 and the access groove portion 526 are substantially V-shaped, such that the walls forming the V-shapes define an acute angle therebetween. In the embodiment shown, the acute angle in question is about 80 degrees. Advantageously, the V-shape provides a narrow channel on the underside of the cylindrical article being received in abutment to allow a user to grab said underside when removing said article, for example.

[0291] According to an alternative embodiment (not shown) of the cross-shaped receptacle 520 - instead of protruding from the base 510 as shown in FIGS. 16 to 25 - the cross-shaped receptacle 520 can be defined fully as a recess in the base 510, located below a level of a upper planar surface 516 of the base 510, similarly to the arrangement of the longitudinal receptacle 540 as explained below.

[0292] The scanning support 500 can include one or more longitudinal receptacle 540 defined in the base 510 and located adjacently to the cross-shaped receptacle 520. The longitudinal receptacle 540 is configured to receive the labelled tubular article in abutment. Alternatively, the longitudinal receptacle 540 can protrude from the base 510, similarly to thecross-shaped receptacle 520 embodiment shown in FIGS. 16 to 25. Referring again to FIGS. 16 to 25, and as better shown in FIG. 20, the scanning support 500 includes two longitudinal receptacles 540 disposed on both sides of the cross-shaped receptacle 520. The longitudinal receptacles 540 shown extend in the proximal-distal direction of the base 510.

[0293] Moreover, the longitudinal receptacle 540 includes a trough portion 542 configured to receive the labelled tubular article in abutment, and an access recess portion 550 connected to a proximal end of the trough portion 542 to allow or facilitate access to an underside of the labelled tubular article being received therein. According to one mode of use, the tubular article is placed in abutment in the trough portion 542. Evidently, a length of the trough portion 542 is slightly shorter than a length of the tubular article such that an end segment of the tubular objects extends over the access recess portion 550. Therefrom, a user can more easily grab or handle the tubular article from an underside of the end segment. According to some alterative embodiments (not shown), a varying number of longitudinal receptacles with differing dimensions and orientations are envisioned herein. For example, a single longitudinal receptacle can be provided on the right-hand side of the base 510 while the longitudinal receptacle on the left-hand side can be dispensed with.

[0294] Advantageously, the embodiment of the scanning support 500 shown in FIGS. 16 to 25 has a vertical plane symmetry that makes the scanning support 50 ambidextrous for a user. The scanning support 500 can be arranged with a vertical plane symmetry extending from a proximal side to a distal side of the base 510. As such, the scanning support 500 is arranged such that each side thereof with respect to the vertical plane of symmetry is substantially mirrored. In other words, the vertical plane symmetry defines two substantially mirrored sides of the reading support 500. As implemented in FIG. 20, the vertical plane symmetry also specifically intersects a center of the cross-shaped receptacle 520 (which coincides with the cross-section line AA, as shown in FIG. 19). It should be noted that in this embodiment, the vertical plane symmetry only applies to the scanning support 500 since the housing 620 is offset from the middle of the scanning support 500 to accommodate the asymmetrical display-sensor device (i.e., the optical sensor is coupled to an extremity of the display).

[0295] According to an embodiment that is not illustrated herein, the scanning support 500 includes an autofocus fiducial marker fixed to the upper planar surface 516 of the base. More specifically, the autofocus fiducial marker is positioned on the base 510 in the field of view of the overhead optical sensor 660.

[0296] The Scanning and Display Station

[0297] As previously mentioned, the station 600 can incorporate the scanning support 500 according to one of the previously mentioned embodiments.

[0298] Referring to the embodiment and use shown in FIG. 24, it is appreciated that the scanning and display station can be adapted to mount to atop a medical cart, or the like, to raise the station 600 to a suitable height for a user. The medical cart, if used, can also be used to temporarily hold the articles before or after the DIV procedure. Also, the base 510 of the scanning support 500 can be made integral with a cart (arrangement not shown).

[0299] Referring to the embodiment shown in FIGS. 16 to 25, the station 600 further includes the stand 610 extending upwardly from the base 510 of the scanning support 500. As such, the stand 610 has a lower end connected to the scanning support 500 and an upper end. In the embodiment, the stand 610 extends specifically from a distal side of the base 510. In addition, the stand 610 defines two openings 616, each one aligned or in-lined with a respective one of the two longitudinal receptacles 540 of the scanning support 500. Each opening 616 is configured (i.e., sized and shaped) to fit the labelled tubular article along a longitudinal direction thereof. According to a mode of use, the tubular article can be introduced or removed to the longitudinal receptacle 540 via said opening 616. Also, the opening 616 can simply be used to accommodate therein a tubular article that is so long as to otherwise interfere with the stand 610.

[0300] Advantageously, the stand 610 adds a preset distance between the scanning support 500 and the optical sensor 660 to provide the optical sensor 660 with a full field of view of the article(s) and with enough room for a user to handle the articles in said vertical space therebetween. The preset distance can be accounted for to calibrate the optical sensor 660 and facilitate focus.

[0301] The station 600 can include the light source (not illustrated) mounted in the housing 620 and configured to illuminate the scanning support 500. The light source can be arranged to directly project light on the scanning support 500 or indirectly via the plane mirror 670.

[0302] The station 600 can include the overhead optical sensor 660 mounted in the housing 620 and configured to collect data about the labelled cylindrical or tubular article. As shown in the embodiment of FIGS. 16 to 25, and as better seen in FIGS. 21 and 22, the field of view of the optical sensor 660 is substantially directed towards the distal side of the station and further downwardly towards the scanning support 500. This orientation of the field of view of the optical sensor is a result of the optical sensor orientation as integrated to a tablet. It's generally understood that an interface / display of a tablet is more ergonomic when it is inclined upwardly for the user.

[0303] The station 600 can include the plane mirror 670 mounted in the housing 620. The plane mirror is opposed to the optical sensor and inclined downwardly according to a mirror angle configured for a secondary field of view of the optical sensor (indirect, reflected, secondary, mirror-reflected field of view, etc.) to encompass at least the cross-shaped receptacle 520 and the longitudinal receptacle 540 of the scanning support 500. In the embodiment shown in FIGS. 16 to 25, the tablet encased in the housing 620 is inclined at a 110 degrees angle with respect to a vertical axis. Additionally, a bottom window is provided about a bottom portion of the housing 620 to allow a clear incident field of view between the plane mirror 670 and the scanning support 500.

[0304] Advantageously, a polarizing filter can be provided in front of the light source and in front of the optical sensor, preferably perpendicularly to a line of sight thereof. If the scanning and display station 600 is used with vials and syringes, it is known that such cylindrical and tubular articles can produce parasitic light reflections that could negatively impact data collection by the optical sensor 660.

[0305] Optionally, the station 600 can include a support for tubular articles, such as syringes, distinct from the longitudinal receptacle 540, to vertically hold syringes on a lateral side of the station.

[0306] The station 600 can have a power source operably connected to the optical sensor 660, light source, etc. The power source can be a battery or connecting means to an electrical outlet external to the station 600.

[0307] In some non-limiting implementations, the present technology is an innovative medical device designed for use in emergency or critical situations, where speed and precision are essential for administering life-saving treatments. The device combines two key functionalities that secure and expedite the drug administration process.

[0308] In some non-limiting implementations, the present technology assists clinicians in establishing vascular access by using real-time ultrasound imaging. This feature enables efficient and precise navigation of needles toward veins or arteries, even under conditions where vessels are difficult to locate. Ultrasound guidance reduces the risks of damaging vessels and nerves and improves the success rate of vascular access on the first attempt.

[0309] In some non-limiting implementations, once vascular access is established, the present technology verifies medications through a computer vision system equipped with dual polarization. This system automatically identifies ampoules and syringes, validating the correct medication and exact dose to be administered. It provides a double-check system to minimize medication errors, especially in critical moments where every second counts.

[0310] In some non-limiting implementations, the present technology provides a complete solution for managing urgent interventions, from securing vascular access to safely and accurately preparing and administering medications.

[0311] It should be expressly understood that not all technical effects mentioned herein need to be enjoyed in each and every implementation of the present technology. For example, implementations of the present technology may be implemented without the user enjoying some of these technical effects, while other non-limiting implementations may be implemented with the user enjoying other technical effects or none at all.

[0312] Some of these steps and signal sending-receiving are well known in the art and, as such, have been omitted in certain portions of this description for the sake of simplicity. Thesignals can be sent-received using optical means (such as a fiber-optic connection), electronic means (such as using wired or wireless connection), and mechanical means (such as pressurebased, temperature-based, or any other suitable physical parameter based).

[0313] Modifications and improvements to the above-described implementations of the present technology may become apparent to those skilled in the art. The foregoing description is intended to be exemplary rather than limiting.

[0314] The embodiments described above are intended to be exemplary only. The scope of the invention is therefore intended to be limited solely by the appended claims.

Claims

CLAIMSWhat is claimed is:

1. A computer- implemented method for verifying a medication to be administered to a subject, the method being executed by a processor, the method comprising: receiving, from a camera device in communication with the processor, video data of a drug vial provided with a vial label, the video data comprising a plurality of video frames; extracting, at the processor, given drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames using an optical character recognition method, the given drug information comprising at least a drug name, an expiry date and a concentration; and transmitting, from the processor to a display device, a user interface comprising the detected drug information.

2. The method of claim 1, further comprising: generating, at the processor, a user interface based on the detected drug information.

3. The method of claim 2, wherein the user interface is one of: a dose injection calculator prepopulated based on the detected drug information; a two-part injection calculator prepopulated based on the detected drug information; and a multi-dose injection calculator prepopulated based on the detected drug information.

4. The method of claim 1, wherein said detecting the given drug information comprises detecting a drug identifier from the vial label.

5. The method of claim 4, wherein the drug identifier comprises one of a national drug code and a drug identification number.

6. The method of any one of claims 1 to 5, further comprising: converting the given drug information into an audio signal using a text-to-speech method; and providing the audio signal for play back by a speaker.

7. The method of any one of claims 1 to 5, further comprising: receiving, from a microphone, an audio signal representative of the user reading aloud the displayed drug information; converting the audio signal into text using a speech recognition method; identifying further drug information from the text; comparing the further drug information to the given drug information, thereby obtaining a comparison result; and outputting an alert when the comparing result is indicative of a mismatch.

8. The method of any one of claims 1 to 7, further comprising: receiving a picture of the drug vial and a syringe provided with a syringe label; retrieving further information about the drug; and providing the picture and the further information for display.

9. The method of claim 8, further comprising extracting further drug information from the syringe label by analyzing the picture using the optical character recognition method; comparing the further drug information to the given drug information, thereby obtaining a further comparison result; and outputting the further comparison result.

10. The method of claim 9, further comprising extracting additional drug information from the vial label by analyzing the picture using the optical character recognition method;comparing the additional drug information to the given drug information, thereby obtaining an additional comparison result; and outputting the additional comparison result.

11. The method of any one of claims 8 to 10, further comprising: determining a volume of drug contained in the syringe by analyzing the picture; and outputting the volume of drug.

12. The method of any one of claims 1 to 11, further comprising: provided a medical form to be completed for display; and receiving information associated with the form from a user input device.

13. A system for verifying a medication to be administered to a subject, the system comprising: a processor; a non-transitory storage medium operatively connected to the processor, the non- transitory storage medium comprising computer-readable instructions; the processor, upon executing the instructions, being configured for: receiving video data of a drug vial provided with a vial label, the video data comprising a plurality of video frames; extracting given drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames using an optical character recognition method, the given drug information comprising at least a drug name, an expiry date and a concentration; and providing for display the detected drug information.

14. The system of claim 13, wherein the processor is further configured to: generate a user interface based on the detected drug information.

15. The system of claim 14, wherein the user interface is one of: a dose injection calculator prepopulated based on the detected drug information; a two-part injection calculator prepopulated based on the detected drug information; and a multi-dose injection calculator prepopulated based on the detected drug information.

16. The system of claim 13, wherein said detecting the given drug information comprises detecting a drug identifier from the vial label.

17. The system of claim 16, wherein the drug identifier comprises one of a national drug code and a drug identification number.

18. The system of any one of claims 13 to 17, further comprising: converting the given drug information into an audio signal using a text-to-speech method; and providing the audio signal for play back by a speaker.

19. The system of any one of claims 13 to 18, further comprising: receiving, from a microphone, an audio signal representative of the user reading aloud the displayed drug information; converting the audio signal into text using a speech recognition method; identifying further drug information from the text; comparing the further drug information to the given drug information, thereby obtaining a comparison result; and outputting an alert when the comparing result is indicative of a mismatch.

20. The system of any one of claims 13 to 19, further comprising: receiving a picture of the drug vial and a syringe provided with a syringe label; retrieving further information about the drug; and providing the picture and the further information for display.

21. The system of claim 20, further comprising extracting further drug information from the syringe label by analyzing the picture using the optical character recognition method; comparing the further drug information to the given drug information, thereby obtaining a further comparison result; and outputting the further comparison result.

22. The system of claim 21, further comprising extracting additional drug information from the vial label by analyzing the picture using the optical character recognition method; comparing the additional drug information to the given drug information, thereby obtaining an additional comparison result; and outputting the additional comparison result.

23. The system of any one of claims 20 to 22, further comprising: determining a volume of drug contained in the syringe by analyzing the picture; and outputting the volume of drug.

24. The system of any one of claims 13 to 23, further comprising: provided a medical form to be completed for display; and receiving information associated with the form from a user input device.

25. A scanning support (500) for holding a labelled cylindrical article and a labelled tubular article for scanning of the labels or marks thereof by an overhead optical sensor, the scanning support comprising: a base (510) configured to stand on a support surface (S); a cross-shaped receptacle (520) extending from the base (510), the cross-shaped receptacle (520) including a saddle portion (524), configured to receive the labelled cylindrical article in abutment, and an access groove portion (526), extending across the saddle portion (524), the access groove portion (526) being leveled with or lower thanthe saddle portion (524) to access an underside of the labelled cylindrical article being received in the saddle portion (524); and one or more longitudinal receptacle (540) defined in the base (510) adjacently to the cross-shaped receptacle (520), the one or more longitudinal receptacle (540) including a trough portion (542) configured to receive the labelled tubular article in abutment, and an access recess portion (550) connected to a proximal end (544) of the trough portion (542) configured to access an underside of the labelled tubular article being received by the one or more longitudinal receptacle (540).

26. The scanning support (500) of claim 25, further having a vertical plane symmetry extending from a proximal side (512) to a distal side (514) of the base (510), and the scanning support (500) being arranged such that each side thereof with respect to the vertical plane of symmetry is substantially mirrored.

27. The scanning support (500) of claim 26, wherein the vertical plane symmetry also intersects a center (521) of the cross-shaped receptacle (520).

28. The scanning support (500) of any one of claims 25 to 28, wherein at least one of the saddle portion (524) and the access groove portion (526) is substantially V-shaped and wherein two walls forming the V-shape define an acute angle therebetween.

29. The scanning support (500) of any one of claims 25 to 28, further comprising an autofocus fiducial marker fixed to an upper planar surface (516) of the base (510) and located in the direct or indirect field of view of the overhead optical sensor.

30. A scanning and display station (600) for scanning a labelled cylindrical or tubular article and displaying an information related to the label thereof, the scanning and display station (600) comprising: a scanning support (500) according to any one of claims 25 to 29; a stand (610) extending upwardly from the base (510) of the scanning support (500) and having a lower end (612) connected to the scanning support (500) and an upper end (614);a housing (620) extending from the upper end (614) of the stand (610) at least partially over the scanning support (500); a light source mounted to the housing (620) and configured to illuminate the scanning support (500); an overhead optical sensor (660) mountable to the housing (620) and configured to collect data about the labelled cylindrical or tubular article; a plane mirror (670) mounted to the housing (620) configured oppositely to the optical sensor and inclined downwardly such that a secondary field of view of the optical sensor includes at least the cross-shaped receptacle (520) and the one or more longitudinal receptacle (540) of the scanning support (500); a processor operatively connected to the optical sensor for processing the collected data and generate an information about the labelled cylindrical or tubular article; and a display (680) mounted to the housing (610) and configured to provide the information about the labelled cylindrical or tubular article.

31. The scanning and display station (600) of claim 30, wherein the stand (610) extends from a distal side (514) of the base 510, and wherein the stand (610) has one or more opening (616) in-line with the one or more longitudinal receptacle (540) of the scanning support (500) and configured to fit therethrough the labelled tubular article along an axial direction of the article.

32. A computer-implemented method for generating a user interface for verifying a medication at a user device, comprising: displaying, at a display device of the user device, a user interface, the user interface comprising a first input control and a second input control; receiving, from a user input device of the user device, a user input corresponding to the first input control; determining, based on the user input to the first input control, a value for the second input control, the second input control corresponding to a volume of the medication; andupdating, at the display device, the user interface based on the received user input corresponding to the first input control, and the determined value for the second input control.

33. The method of claim 32, wherein the user interface further comprises a third input control populated by analyzing video data of a drug vial collected by a camera device, the third input corresponding to a concentration of the drug vial.

34. The method of claim 33, wherein the third input control is populated by analyzing video data of a drug vial collected by a camera device by: extracting, at the processor, given drug information from the vial label by analyzing at least one of the video frames of the plurality of video frames using an optical character recognition method, the given drug information comprising the concentration; and- transmitting, from the processor to a display device, for display a user interface comprising the detected drug information.

35. The method of any one of claims 32 to 34, wherein the first input control corresponds to a dose for the subject; and- the determining the value for the second input control is based on the first input control corresponding to the dose for the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

36. The method of any one of claims 32 to 34, wherein the first input control corresponds to a weight of the subject; and- the determining the value for the second input control is based on the first input control corresponding to the weight of the subject and the third input control corresponding to the third input control corresponding to the concentration of the vial.

37. The method of any one of claims 32 to 36, wherein the user interface comprises a syringe user interface element.

38. The method of claim 37 wherein the updating the user interface comprises updating the syringe user interface element to display a filled portion proportional to the determined value for the second input control.

39. The method of claim any one of claims 34 to 38 wherein the given drug information comprises a drug identifier; and the third input control is populated based on the drug identifier, the drug identifier determined based on a drug database.

40. The method of claim 38 wherein the user interface further comprises a fourth input control corresponding to a dose threshold, the dose threshold determined based on the drug database.

41. The method of claim 40 wherein the updating the user interface comprises updating the fourth input control to display a highlight portion when the determined value of the second input control exceeds the dose threshold.

42. The method of any one of claims 37 to 41 wherein the second input control comprises a first dose portion corresponding to a medication volume and a second dose portion corresponding to a solvent volume; and the determining the value for the second input control comprises determining the first portion and the second portion.

43. The method of claim 42 wherein the updating the user interface comprises updating the syringe user interface element to display a first filled portion proportional to the first dose portion and a second filled portion proportional to the second dose portion.

44. The method of any one of claims 39 to 43 wherein the user interface comprises a fifth input control corresponding to a number of injections.

45. A system comprising a memory, a camera device, and a processor, the processor configured to perform the method of any one of claim 32 to 43.

Images