System and method for providing a genericized medical device architecture
Systems, methods, and computer readable storage medium for providing a genericized medical device architecture common to a plurality of medical devices are disclosed. The architecture may comprise at least one diagnostics module associated with at least one of the plurality of medical devices, wherein the at least one diagnostics module is configured to monitor an operational status of the at least one medical device. At least one hardware abstraction layer may be associated with at least one of the plurality of medical devices, and may be configured to provide abstracted access to hardware of the at least one medical device.
1. A non-transitory computer readable storage medium at least partially on a mobile device and having encoded thereon computer executable instructions which, when executed, cause a computer processor to implement an application comprised of at least software architecture common to a plurality of remote medical devices, the software architecture comprising:
a plurality of modules, each module of the plurality of modules configured to control and monitor aspects of each hardware and software related to each of the plurality of medical devices; and
a graphical user interface (GUI) that provides uniform remote interaction across the plurality of medical devices, wherein native applications of each of the plurality of medical devices are normalized to provide the uniform remote interaction,
wherein each of the plurality of medical devices has multiple operating modes, and each of the multiple operating modes is accessible via the GUI, and
wherein a plurality of slide-out menus provide access to a plurality of submode s to each operating mode of the multiple operating modes, and
wherein a button on the GUI, when pressed, displays a slide-out menu of the plurality of slide-out menus depending on a current operating mode of the multiple operating modes.
2. The medium of claim 1 , wherein one of the plurality of modules is configured to provide at least one application programming interface (API) that comprises a plurality of options for the GUI with respect to each of the plurality of modules.
3. The medium of claim 1 , wherein one of the plurality of modules comprises a diagnostics module commonly associated with the software of the plurality of medical devices, wherein the diagnostics module is configured to monitor an operational status of the hardware of each of the plurality of medical devices.
4. The medium of claim 3 , wherein the diagnostics module provides at least one application programming interface (API) to allow for the monitoring of the operational status of the hardware and software of the medical device.
5. The medium of claim 1 , wherein one of the plurality of modules comprises: a hardware abstraction layer associated with at least one remote medical device of the plurality of remote medical devices, wherein the hardware abstraction layer is configured to allow hardware independent access to functionality of the at least one medical device.
6. The medium of claim 5 , wherein the hardware abstraction layer provides at least one application programming interface (API) to allow for the use of underlying hardware of the medical device.
7. The medium of claim 1 , wherein one of the plurality of modules comprises a datastore associated with each of the plurality of medical devices, wherein the datastore is configured to provide dedicated persistent and non-persistent data storage for each of the plurality of medical devices.
8. The medium of claim 1 , wherein the GUI is further configured to provide at least one application programming interface (API) to manage and transition between graphical views of the GUI.
9. The medium of claim 8 , wherein the plurality of slide-out menus that provide access to a plurality of submodes to each operating mode of the multiple operating modes are secondary slide-out menus and the transition comprises a primary slide-out menu.
10. The medium of claim 1 , wherein one of the plurality of modules comprises a low level services library configured to allow implementation of low level services associated with the hardware which provide support to manage single core functionality.
11. The medium of claim 10 , wherein the low level services library provides at least one application programming interface (API) to allow for the use of the underlying functionality of the medical device.
12. The medium of claim 1 , wherein one of the plurality of modules comprises a workflow module configured to allow implementation of a workflow across components of the software architecture.
13. The medium of claim 12 , wherein the workflow module provides an application programming interface to manage a state machine.
14. The medium of claim 1 , wherein an aspect of the GUI is dedicated to each of the plurality of modules.
15. The medium of claim 1 , wherein the GUI comprises distinct applications for each of the plurality of medical devices.
16. The medium of claim 1 , wherein ones of the plurality of medical devices comprise phacoemulsification systems.