# US 10,310,845 B2 · Medical device low acuity vitals system architecture > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,310,845 B2 - Document ID: US10310845B2 - Status: Granted - Kind: B2 - Application number: 14/535,395 - Filed: 2014-11-07 - Published: 2015-12-31 - Granted: 2019-06-04 - Earliest claimed: 2014-06-27 - Assignees: Welch Allyn, Inc. - Applicants: Welch Allyn, Inc. - Inventors: Cory R. Gondek; Soundharya Nagasubramanian; Paul S. Kovitz; Charles Alfred; Dan E. Goldman, III - Web page: https://patentgrep.com/patent/US10310845B2 ## CPC - G06F 8/70: Software maintenance or management - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/546: {Message passing systems or structures, e.g. queues} - G16H 40/40: for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades - A61B 5/01: Measuring temperature of body parts {; Diagnostic temperature sensing, e.g. for malignant or inflamed tissue} (clinical contact thermometers G01K13/20) - A61B 5/021: Measuring pressure in heart or blood vessels - A61B 5/024: Measuring pulse rate or heart rate - A61B 5/14542: {for measuring blood gases (A61B5/14551 takes precedence)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA - A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D) ## Abstract A medical device including a non-transitory storage device storing a plurality of modular software components programmed to provide medical device functionality is disclosed. The software components can be configured to run independently as a daemon, to be modified without recompiling unchanged software components and to communicate to each other through a software component. A system including a central unit configured to communicate with a medical device is also disclosed. A medical device software architecture stored on a non-transitory, computer readable storage medium including a plurality of modular software components programmed to provide medical device functionality is also disclosed. ## Claims ### Claim 1 A medical device, comprising: a tangible, non-transitory storage device storing a single system architecture including a plurality of modular software components, wherein each of the plurality of modular software components is programmed to provide a separate medical device functionality; wherein each of the plurality of modular software components is configured to run independently as a daemon such that each daemon provides the separate medical device functionality; wherein the plurality of modular software components further comprise a plurality of reusable assets, wherein at least one of the plurality of reusable assets is a proxy for interfacing with a measurement module, wherein the measurement module is configured to obtain patient physiological data; wherein at least one of the plurality of reusable assets specifies a message channel for receiving output from the measurement module; and wherein the message channel is defined between the proxy and the measurement module within the medical device so that the patient physiological data is communicated, using an object-oriented data model with a publish/subscribe bus architecture, from the measurement module to the proxy; wherein each of the plurality of modular software components is configured to be modified and recompiled without recompiling unchanged modular software components; and wherein the plurality of modular software components are configured to communicate to each other through a software component. ### Claim 2 (depends on 1) The medical device of claim 1, wherein at least one of the plurality of reusable assets is configured to enable communication between the medical device and a central unit. ### Claim 3 (depends on 1) The medical device of claim 1, wherein the measurement module is a saturated oxygen module, a non-invasive blood pressure module, or a thermometry module. ### Claim 4 (depends on 3) The medical device of claim 3, wherein one of the plurality of reusable assets is a component manager configured to start up and shut down at least one of the plurality of modular software components; wherein one of the plurality of reusable assets is a capability registry configured to provide a bulletin board system where the plurality of modular software components can post common object-oriented architecture messages and receive messages about changes to any of the common object-oriented architecture messages; wherein one of the plurality of reusable assets is a configuration manager configured to maintain persistent configuration of the medical device and provide a device configuration to client software components; and wherein one of the plurality of reusable assets is a workflow manager configured to add, remove, start, or stop manager scripts in the medical device. ### Claim 5 (depends on 1) The medical device of claim 1, wherein the plurality of modular software components further comprise a plurality of reusable assets; wherein one of the plurality of reusable assets is a virtual operating system configured to interface with an operating system adaptor; and wherein one of the plurality of reusable assets is a virtual hardware configured to interface with a hardware adaptor. ### Claim 6 (depends on 5) The medical device of claim 5, wherein one of the plurality of reusable assets is a message manager configured to provide an inter-process communications bus for sending common object-oriented architecture messages between the plurality of modular software components. ### Claim 7 (depends on 5) The medical device of claim 5, wherein one of the plurality of reusable assets is a component manager configured to start up and shut down at least one of the plurality of modular software components; wherein one of the plurality of reusable assets is a capability registry configured to provide a bulletin board system where the plurality of modular software components can post common object-oriented architecture messages and receive messages about changes to any of the common object-oriented architecture messages; wherein one of the plurality of reusable assets is a configuration manager configured to maintain persistent configuration of the medical device and provide a device configuration to client software components; and wherein one of the plurality of reusable assets is a workflow manager configured to add, remove, start, or stop manager scripts in the medical device.