Abstract: An electronic device includes a hand held base assembly that includes circuitry including memory and firmware executed by a processor or microcontroller of the circuitry; and a cartridge assembly that includes memory that is read by the firmware of the handheld base assembly. The cartridge assembly and the handheld base assembly are configured to removably couple together to define the electronic device for producing an aerosol for inhalation by a person. An enclosed air passageway is defined by the cartridge assembly and by the handheld base assembly, which isolates the airflow from the electronics of the device. The enclosed air passageway extends between the opening of the mouthpiece for taking a breath and a diaphragm of the handheld base assembly, movement of the diaphragm changing the air pressure within an enclosed interior space having a pressure sensor for trigging the pressure sensor when a breath is taken.

Abstract: A real-time transaction processing system and method include the provision of a real-time transactional data store having an importer subsystem embedded therein. The importer subsystem is configured to connect directly to a real-time data source without using an intermediate subsystem. Events are received via the real-time data source at the importer subsystem, which transacts the events into the real-time transactional data store to create one or more records in the real-time transactional data store corresponding to the events.

Abstract: A real-time transaction processing system and method include the provision of a real-time transactional data store having an importer subsystem embedded therein. The importer subsystem is configured to connect directly to a real-time data source without using an intermediate subsystem. Events are received via the real-time data source at the importer subsystem, which transacts the events into the real-time transactional data store to create one or more records in the real-time transactional data store corresponding to the events.

Abstract: A protocol to enable management of opaque entities in a computing environment comprises an events component and a commands component. The events component enables a manager to utilize a received event communicated by a corresponding managed entity to indicate when administration or other management actions have occurred to domain information on the corresponding managed entity. The commands component interacts with the managed entities in response to the events component receiving corresponding events there from. The commands component further comprises commands for backing up the domain information stored by the managed entities as opaque configuration objects, for restoring the domain information to the managed entities as opaque configuration objects and for querying an identified one of the plurality of managed entities to determine whether two domain configurations are semantically different in a way that allows the configuration to remain opaque to the manager.

Abstract: A medication infusion system may include a controller and a reservoir module including a reservoir containing medication to be delivered to an internal wound site via the controller. The controller may have a peristaltic pump driven by a motor to urge medication to flow toward the internal wound site, through a conduit. When the conduit is not tensioned via engagement with the pump, a valve blocks fluid flow to prevent unrestricted flow of medication. The valve may have a tapered plunger separated from an annular valve seat by a portion of the conduit that elongates under tension to enable withdrawal of the plunger from the valve seat. Alternatively, the valve may have features such as a spherical plunger between two annular valve seats, a rigid tubular member biased with respect to the conduit, or an opening in the conduit that moves axially or radially to enable fluid flow.

Abstract: A protocol to enable management of opaque entities in a computing environment comprises an events component and a commands component. The events component enables a manager to utilize a received event communicated by a corresponding managed entity to indicate when administration or other management actions have occurred to domain information on the corresponding managed entity. The commands component interacts with the managed entities in response to the events component receiving corresponding events there from. The commands component further comprises commands for backing up the domain information stored by the managed entities as opaque configuration objects, for restoring the domain information to the managed entities as opaque configuration objects and for querying an identified one of the plurality of managed entities to determine whether two domain configurations are semantically different in a way that allows the configuration to remain opaque to the manager.