MD PnP Update
After the break, Julian Goldman provided a brief update on the MD PnP program.
First, Goldman presented ways integrated systems can support safety, using examples from non-healthcare applications. The classic example from Goldman’s stump speech is the automotive brake/automatic transmission interlock, an almost universal interoperable safety feature.
From aviation, the airplane landing gear smart alarm annunciates when a plane is landing if landing gear is not down. This example demonstrates contextual awareness, an important feature needed for health care safety.
Clinical analogs that would improve safety were presented including:
Heart lung machine and ventilator – switching from bypass and back. Ventilators are sometimes not turned on – simple human error that could be eliminated. Citation: Anesthesiology. 87(4):741-748, October 1997
Blood pressure measurement errors can occur if the invasive blood pressure monitor is not manually zero’d when patient’s height and inclination is changed relative to pole mounted patient monitor. Human error occurs when the clinician forgets to recalibrate the pressure transducer after moving the patient.Citation: Acta Anaesthesiol Scand. 2006 May;50(5):600-3
Given the potential patient safety benefits, and the relative simplicity of these initial potential applications, the goals of MD PnP include:
- Lead adoption of open standards
- Define a regulatory pathway
- Elicit clinical requirements
- Use a vendor neutral lab to test and verify solutions
APSF Endorsement of Interoperability
Awareness of these potential patient safety improvements is growing. From the Anesthesia Patient Safety Foundation’s (APSF) endorsement of interoperability, March 2007:
“APSF believes that intercommunication and interoperability of devices could lead to important advances in patient safety, and that the standards and protocols to allow such seamless intercommunication should be developed fully with these advances in mind.
APSF also recognizes that as in all technologies for patient safety, interoperability poses safety and medicolegal challenges as well. Development of standards and production of interoperable equipment protocols should strike the proper balance to achieve
maximum patient safety and outcome benefit.”
The APSF has also noted Dangers of Postoperative Opioids – PCA pump related patient deaths and the need to automatically terminate PCA infusions when monitoring indicates.
“We advocate widespread acceptance of the goal that no patient shall be harmed by opioid-induced respiratory depression in the postoperative period.
“Thus, immediately, we urge health care professionals to consider the potential safety value of continuous monitoring of oxygenation (pulse oximetry) and ventilation in patients receiving PCA or neuraxial opioids in the postoperative period.”
APSF has also publish recommendations regarding PCA pumps:
“A particularly attractive feature may be the ability to automatically terminate or reduce PCA (or PCEA) infusions when monitoring technology suggests the presence of opioid-induced respiratory depression. To facilitate such capabilities, we strongly endorse the efforts to develop international standards for device interoperability and device-device communication.
It is critical that any monitoring system be linked to a reliable process to summon a competent health care professional to the patient’s bedside in a timely manner.”
Kaiser Purchase Contract Language
Providers are also beginning to make demands on vendors regarding connectivity and integration. Kaiser is the first to include purchase contract language that places systems integration responsibilities unambiguously upon the vendor:
“Supplier agrees to participate with Kaiser in the development of a medical device plug and play integration standard (the “Integration Standard”), and … will make reasonable efforts to conform to the Integration Standard when approved and formulated by the parties in writing. Until the Integration Standard is approved, Supplier intends to continue … to provide open interfacing protocols …”
Other providers are evaluating Kaiser’s position and are expected to follow suit.
New Standards Development
Clinical requirements lie at the heart of medical device connectivity. The MD PnP program is currently working to collect use cases and requirements relating to interoperability.
The MD PnP program is also developing a new standard, the “Integrated Clinical Environment” of networked medical devices. Focused on risk management, the project does not specify technology. For risk management, they are specifying data logging, data security, integration with the hospital network, and plug-and-play device discovery.
Another area of focus is the IEC 60601-1-10, the requirements for the development of physiologic closed loop controllers (the PCLC standard). This standard will support distributed patient connected devices that control a patient variable. Example applications include a patient warming system that controls body temperature, and the infusion of a medication to maintain blood pressure in a target range.
The PCLC standard will permit distributed PCLCs that involves more than one item of equipment of a medical electrical system. Distributed PCLCs can also be widely separated in distance. An example here would be the control of blood pressure by networking a bedside blood pressure monitor and an infusion pump, and the titration of inspired oxygen concentration of a lung ventilator with a stand-alone pulse oximeter.