Robotic Microtool Control in an Intelligent Automated In Vitro Fertilization and Intracytoplasmic Sperm Injection Platform
US-2024426856-A1 · Dec 26, 2024 · US
US12144960B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12144960-B2 |
| Application number | US-202418410780-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 11, 2024 |
| Priority date | Mar 13, 2013 |
| Publication date | Nov 19, 2024 |
| Grant date | Nov 19, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An infusion management and monitoring system comprises an infusion pump and instructions executable by a processor to cause a remote device separate from and in communication with the infusion pump to receive data for a medication to be administered to a patient via the infusion pump within a healthcare environment; receive from the infusion pump data for administration of the medication to the patient; determine a status of the administration of the medication based on at least one of the data for the medication or the data for the administration of the medication; and transmit the status to a mobile communication device within the healthcare environment.
Opening claim text (preview).
What is claimed is: 1. An infusion management and monitoring system comprising: an infusion pump; and a non-transitory computer-readable medium comprising instructions executable by a processor to cause one or more remote devices separate from and in communication with the infusion pump to: receive data for a medication to be administered to a patient via the infusion pump within a healthcare environment, the data for the medication comprising one or more of a medication name, a medication amount to be administered, or date or time data related to when the medication is scheduled to be administered; receive, from the infusion pump, data for administration of the medication to the patient, the data for the administration of the medication comprising one or more of a patient identifier, a medication container identifier, a medication type, a rate of medication administration, an infusion pump identifier, or one or more infusion events and respective event times; determine a status of the administration of the medication based on at least one of the data for the medication or the data for the administration of the medication; associate the infusion pump with a medication order comprising the data for the medication based at least on an association between the patient and the infusion pump; and transmit the status to a mobile device within the healthcare environment, the transmitting enabling the mobile device to at least: provide, on a graphical user interface, information about the administration of the medication; and provide, on the graphical user interface and in response to a user interaction, a parameter characterizing operation of the infusion pump. 2. The infusion management and monitoring system of claim 1 , wherein the instructions executable by the processor further cause the one or more remote devices to: receive the data for the medication from a medication ordering system in communication with the one or more remote devices. 3. The infusion management and monitoring system of claim 1 , wherein the status indicates progress of the administration of the medication. 4. The infusion management and monitoring system of claim 1 , wherein the status indicates whether the infusion pump started administering the medication. 5. The infusion management and monitoring system of claim 1 , wherein the one or more infusion events comprise infusion start, infusion pause, infusion stop. 6. The infusion management and monitoring system of claim 1 , wherein the transmitting enables the mobile device to display administration data organized by time. 7. The infusion management and monitoring system of claim 1 , wherein the transmitting enables the mobile device to display the status of the administration of the medication. 8. A non-transitory computer readable medium comprising instructions executable by a processor to cause one or more remote devices separate from and in communication with an infusion pump to: receive data for a medication to be administered to a patient via the infusion pump within a healthcare environment, the data for the medication comprising one or more of a medication name, a medication amount to be administered, or date or time data related to when the medication is scheduled to be administered; receive, from the infusion pump, data for administration of the medication to the patient, the data for the administration of the medication comprising one or more of a patient identifier, a medication container identifier, a medication type, a rate of medication administration, an infusion pump identifier, or one or more infusion events and respective event times; determine a status of the administration of the medication based on at least one of the data for the medication or the data for the administration of the medication; associate the infusion pump with a medication order comprising the data for the medication based at least on an association between the patient and the infusion pump; and transmit the status to a mobile device within the healthcare environment, the transmitting enabling the mobile device to at least: provide, on a graphical user interface, information about the administration of the medication; and provide, on the graphical user interface and in response to a user interaction, a parameter characterizing operation of the infusion pump. 9. The non-transitory computer readable medium of claim 8 , wherein the instructions executable by the processor further cause the one or more remote devices to: receive the data for the medication from a medication ordering system in communication with the one or more remote devices. 10. The non-transitory computer readable medium of claim 9 , wherein the instructions executable by the processor further cause the one or more remote devices to: associate a medication order comprising the data for the medication with the infusion pump. 11. The non-transitory computer readable medium of claim 8 , wherein the status indicates progress of the administration of the medication. 12. The non-transitory computer readable medium of claim 8 , wherein the status indicates whether the infusion pump started administering the medication. 13. The non-transitory computer readable medium of claim 8 , wherein the one or more infusion events comprise infusion start, infusion pause, infusion stop. 14. The non-transitory computer readable medium of claim 8 , wherein the transmitting enables the mobile device to display the status of the administration of the medication.
for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range · CPC title
based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance · CPC title
Head Mounted Displays [HMD] · CPC title
Touch-screens; Virtual keyboard or keypads; Virtual buttons; Soft keys; Mouse touches · CPC title
User interfaces, e.g. screens or keyboards · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.