Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, a server receives infusion therapy progress data that is generated by an infusion pump and renal failure therapy progress data that is generated by a renal failure therapy machine. The server also receives physiological data that is generated by at least one physiological sensor. The server determines fluid balance data based on a difference between the infusion therapy progress data and the renal failure therapy progress data. The server stores the fluid balance data in conjunction with hemodynamic information from the physiological data to a patient's medical record.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, a processor receives infusion therapy progress data that is generated by an infusion pump and renal failure therapy progress data that is generated by a renal failure therapy machine. The processor also receives physiological data that generated by at least one physiological sensor. The processor determines fluid balance data based on a difference between the infusion therapy progress data and the renal failure therapy progress data. The processor displays the fluid balance data in conjunction with hemodynamic information from the physiological data.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, a processor receives infusion therapy progress data that is generated by an infusion pump and renal failure therapy progress data that is generated by a renal failure therapy machine. The processor also receives physiological data that generated by at least one physiological sensor. The processor determines fluid balance data based on a difference between the infusion therapy progress data and the renal failure therapy progress data. The processor displays the fluid balance data in conjunction with hemodynamic information from the physiological data.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, a processor receives infusion therapy progress data, receives renal failure therapy progress data, and displays derivative data types. Each of the derivative data types includes at least one infusion parameter, at least renal failure therapy parameter, and at least one of the mathematical operation. The example data processor receives a selection of one of the derivative data types, and calculates derivative data by applying the at least one mathematical operation, as specified by the derivative data type, to infusion therapy progress data that relates to the at least one infusion parameter, as specified by the derivative data type, and renal failure therapy progress data that relates to the at least one renal failure therapy parameter, as specified by the derivative data type. The processor also displays the derivative data.

Abstract: Therapy device systems, modules, and methods, include memory, one or more processors, in communication with the memory, a plurality of medical therapy devices, a plurality of patient monitoring devices, and a protocol execution module, configured to execute on the one or more processors. The protocol execution module displays a plurality of protocols. The protocol execution module receives a selected protocol, associated with an individual medical therapy device being one of a plurality of medical therapy devices and associated with an individual patient monitoring device being one of a plurality of patient monitoring devices. The protocol execution module executes the selected protocol with the individual medical therapy device.

Abstract: Therapy device systems, modules, and methods, include memory, one or more processors, in communication with the memory, a plurality of medical therapy devices, a plurality of patient monitoring devices, and a protocol execution module, configured to execute on the one or more processors. The protocol execution module displays a plurality of protocols. The protocol execution module receives a selected protocol, associated with an individual medical therapy device being one of a plurality of medical therapy devices and associated with an individual patient monitoring device being one of a plurality of patient monitoring devices. The protocol execution module executes the selected protocol with the individual medical therapy device.

Abstract: A medical fluid delivery system including analytics for managing patient engagement and treatment compliance is disclosed. In an example, an interface device receives treatment data from a dialysis machine for a patient undergoing dialysis. An analytics processor determines dialysis treatment parameter values by comparing the treatment data to a record of a prescribed therapy or program. The dialysis treatment parameter values may include a lost treatment time parameter value, a lost dwell time parameter value, and/or a completed treatment days parameter value. The analytics processor causes the dialysis treatment parameter values to be displayed within a user interface on a clinician device. The dialysis treatment parameter values provide an indication as to how well the patient is complying with the prescribed therapy or program, and may be used by a clinician to help a patient improve compliance if needed.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, a processor receives infusion therapy progress data, receives renal failure therapy progress data, and displays derivative data types. Each of the derivative data types includes at least one infusion parameter, at least renal failure therapy parameter, and at least one of the mathematical operation. The example data processor receives a selection of one of the derivative data types, and calculates derivative data by applying the at least one mathematical operation, as specified by the derivative data type, to infusion therapy progress data that relates to the at least one infusion parameter, as specified by the derivative data type, and renal failure therapy progress data that relates to the at least one renal failure therapy parameter, as specified by the derivative data type. The processor also displays the derivative data.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, an integration engine receives infusion therapy progress data from an infusion pump and renal failure therapy progress data from a renal failure therapy machine. The integration engine determines a plurality of different types of infusion parameters, determines a plurality of different types of renal failure therapy parameters, and causes a combination user interface to display the plurality of infusion parameters, the plurality of renal failure therapy parameters, and mathematical operations for selection by an operator. The integration engine enables the operator to create derivative data by receiving a selection of an infusion parameter, a renal failure therapy parameter, and a mathematical operation. The integration engine then causes the combination user interface to display the derivative data in conjunction with the infusion therapy progress data and the renal failure therapy progress data.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, an integration engine receives infusion therapy progress data from an infusion pump and renal failure therapy progress data from a renal failure therapy machine. The integration engine determines a plurality of different types of infusion parameters, determines a plurality of different types of renal failure therapy parameters, and causes a combination user interface to display the plurality of infusion parameters, the plurality of renal failure therapy parameters, and mathematical operations for selection by an operator. The integration engine enables the operator to create derivative data by receiving a selection of an infusion parameter, a renal failure therapy parameter, and a mathematical operation. The integration engine then causes the combination user interface to display the derivative data in conjunction with the infusion therapy progress data and the renal failure therapy progress data.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, an integration engine includes a configuration interface configured to receive a patient identifier. The integration engine also includes a subscription processor configured to transmit a first message, including the patient identifier, to a first gateway to receive infusion therapy progress data from at least one infusion pump and transmit a second message, including the patient identifier, to a second gateway to receive renal failure therapy progress data from at least one renal failure therapy machine. The integration engine further includes a data processor configured to receive the infusion therapy progress data from the first gateway, receive the renal failure therapy progress data from the second gateway, and cause a combination user interface to display the infusion therapy progress data and the renal failure therapy progress data.

Abstract: Therapy device systems, modules, and methods, include memory, one or more processors, in communication with the memory, a plurality of medical therapy devices, a plurality of patient monitoring devices, and a protocol execution module, configured to execute on the one or more processors. The protocol execution module displays a plurality of protocols. The protocol execution module receives a selected protocol, associated with an individual medical therapy device being one of a plurality of medical therapy devices and associated with an individual patient monitoring device being one of a plurality of patient monitoring devices. The protocol execution module executes the selected protocol with the individual medical therapy device.

Abstract: Methods, systems, and apparatuses for integrating medical device data are disclosed. In an example embodiment, an integration engine includes a configuration interface configured to receive a patient identifier. The integration engine also includes a subscription processor configured to transmit a first message, including the patient identifier, to a first gateway to receive infusion therapy progress data from at least one infusion pump and transmit a second message, including the patient identifier, to a second gateway to receive renal failure therapy progress data from at least one renal failure therapy machine. The integration engine further includes a data processor configured to receive the infusion therapy progress data from the first gateway, receive the renal failure therapy progress data from the second gateway, and cause a combination user interface to display the infusion therapy progress data and the renal failure therapy progress data.

Abstract: Methods, systems, and apparatuses integrating medical device data are disclosed. In an example embodiment, a vital sign monitor apparatus includes a renal failure therapy interface configured to receive a renal failure therapy parameter from a renal failure therapy machine performing a renal therapy treatment on a patient and an infusion pump interface configured to receive an infusion parameter from an infusion pump performing an infusion treatment for the same patient. The apparatus also includes a vital sign monitor engine configured to display, within a combination user interface of a vital sign monitor, the renal failure therapy parameter within a renal failure therapy timeline, and the infusion parameter within an infusion timeline that is aligned with the renal failure therapy timeline.

Abstract: Methods, systems, and apparatuses integrating medical device data are disclosed. In an example embodiment, a vital sign monitor apparatus includes a renal failure therapy interface configured to receive a renal failure therapy parameter from a renal failure therapy machine performing a renal therapy treatment on a patient and an infusion pump interface configured to receive an infusion parameter from an infusion pump performing an infusion treatment for the same patient. The apparatus also includes a vital sign monitor engine configured to display, within a combination user interface of a vital sign monitor, the renal failure therapy parameter within a renal failure therapy timeline, and the infusion parameter within an infusion timeline that is aligned with the renal failure therapy timeline.

Abstract: Described is a technology by which medical patient facial images are acquired and maintained for associating with a patient's records and/or other items. A video camera may provide video frames, such as captured when a patient is being admitted to a hospital. Face detection may be employed to clip the facial part from the frame. Multiple images of a patient's face may be displayed on a user interface to allow selection of a representative image. Also described is obtaining the patient images by processing electronic documents (e.g., patient records) to look for a face pictured therein.

Abstract: A data consumer is provided with a system that enables automatic generation of a virtual database schema in order to support a customized pattern of data consumption across one or more source databases. In one embodiment, a metadata manager component is configured to facilitate creation of a first data tag and a second data tag. A schema definition manager component is configured to facilitate creation of a data entity that groups the first data tag with the second data tag. A virtual schema generation service component generates the virtual database schema by analyzing the data entity and, based on the grouping of the first data tag with the second data tag, automatically generating and storing a database query statement that, when executed, causes a retrieval of data consistent with data location indicators included in the first and second data tags.

Abstract: Described is associating metadata with different sources of data (e.g., database tables) that allows a single view of data from the sources to be created. An administrator creates baseviews corresponding to database tables and associates metadata with the baseviews, including primary key metadata for the baseviews and meta-tags for one or more of the columns of each baseview. A user selects fields (corresponding to table columns) from a starting baseview, along with fields from any other baseview that has metadata that matches the starting baseview's metadata. A join mechanism automatically creates the view if a metadata match is detected.

Abstract: The synchronous semantic processing technique described herein provides the level of completeness of a document in real-time as a user is creating or editing the document and provides recommendations to the user to increase the level of completeness. In one embodiment, the level of completeness of a medical document, and the state of the components of the document that are used to determine level, are used to make recommendations to a user (e.g., a physician) to provide additional information for the components that determine the level, thereby increasing the level. The level of medical documentation can be represented by an Evaluation and Management (E&M) coding level, which is a U.S. standard defined to evaluate how comprehensive a medical document is. The E&M level is used to determine the completeness of the medical document and to make recommendations to the user to improve the quality and the completeness of the document.

Abstract: A data consumer is provided with a system that enables automatic generation of a virtual database schema in order to support a customized pattern of data consumption across one or more source databases. In one embodiment, a metadata manager component is configured to facilitate creation of a first data tag and a second data tag. A schema definition manager component is configured to facilitate creation of a data entity that groups the first data tag with the second data tag. A virtual schema generation service component generates the virtual database schema by analyzing the data entity and, based on the grouping of the first data tag with the second data tag, automatically generating and storing a database query statement that, when executed, causes a retrieval of data consistent with data location indicators included in the first and second data tags.