
Medical Device Interoperability Research Summary
AAMI Conference Presentation:
Press Response: Articles Featuring the Paper - Importance of the Topics Covered
My Story- Scot Copeland
My name is Scot Copeland. Some of you have never heard of me, while others have heard of me but don’t know me.
A few of you know me. Let me give you a bit of background so you can understand why I started this project and what the Medical Device Interoperability Incubator (sponsored by AwareComm®) is all about.
I was trained as a Radio Repairman in the United States Marine Corps back in 1980. As I was released into the reserves, I began working for an independent medical device repair company as a Biomed in San Diego, CA. Through the next 15 years and several acquisitions, I repaired all types of medical devices in hospitals, clinics, doctors’ offices, you name it.
I even worked for a time for a Radiology equipment company.
When I came to Scripps Health in 1995, I began to specialize in medical device networks, and computerized medical devices. Soon everything was going onto networks and the challenges began.
- How do we get these devices to communicate on the network safely?
- How do we get data safely from one system to another when they are designed differently?
- How do we get the clinical staff to accept the rapid changes in technology?
I began to understand that medical device computer networks and the associated challenges were going to demand an enhanced skill set, so I prepared to get a college degree in I.T. Security. I applied for and obtained a scholarship through Scripps that helped me through each of the four years. On the receipt of one of the scholarships, I was asked to speak and present my concept of MDNOS. The president and CEO of Scripps Health, Chris Van Gorder, acknowledged my vision and encouraged me to follow my dreams.
Through my years of college courses and concentration in the area of medical device network integrations and security, I began to see that there was no single solution to the information security problems with medical devices. Whereas in the I.T. community, there can be one security policy that can be administered across the entire enterprise. There exists nothing like that for the growing population of medical device networks and medical devices. Further, there were new mandates coming down every year governing patient information on the network that we were not able to comply with.
I knew we needed a solution to bring all of the medical devices together on a single management platform, so we could manage all of the necessary security elements.
I wanted to become part of something bigger.
I discovered Awareness Communication Technology, LLC (AwareComm®), a Research and Development Firm with Microsoft Gold Competency, and began to explore the concept of a Medical Device Network Operating System (MDNOS). This is where the real journey began. I returned to Chris Van Gorder with my findings. He further supported my vision by opening doors to the top executives of Scripps, so that I could develop the most effective application of my opportunities -- for both Scripps and the HealthCare Industry.
In doing research and exploring opportunities in the field of information security for medical devices, I became part of AwareComm’s Wisdom Incubator 365. The Wisdom Incubator is a place where inter-disciplinary minds are brought together to share ideas, generate innovation and develop an interdependent culture that promotes progress in a focused direction.
The Wisdom Incubator environment helped me understand that I had been focused on the symptoms and not the problems; not focused on that which supports the human application of technology. I began to see that first and foremost, our problem was the lack of interoperability of medical devices. Indeed, I had never understood what true interoperability meant.
In short, I discovered that “true interoperability” is not only that one medical device can talk to another, but that on a purely device level all of its information input and output can be available to other devices and systems. On the organizational level, it means that our medical device systems are integrated into the clinical workflow safely, such that the intended benefits are realized from the patient all the way through the EHR and back. Furthermore, on a human wellness level, there is complete communication and understanding between the HealthCare provider and the patient.
Thus, the patient is empowered to take full responsibility and accountability for their care. In other words, the HealthCare provider is properly and safely integrated into the community.
Right now there are shortcomings on every level:
- Lack of interoperability on a device and system level contributes to extremely high costs in medical errors;
- Lack of “interoperability” with the patient community contributes high costs of repeat care due to non-compliance… just to name the easy ones.
During this exploration process, and in foreseeing the merit of my project as well as my passion, AwareComm® spun up a Medical Device Interoperability Incubator that I believe can be applied to address these issues by bringing together members and contributors from all HealthCare fields to develop a HealthCare culture for change; learning to embrace and accept “The New”:
- A culture of interoperability in the Medical Device Industry can help bring interoperable devices to the
HealthCare market. Together we can design a Medical Device Network Operating System that will serve as a security management platform, and manage the device interoperability by users and groups. - A culture that embraces “The New” can help integrate the new technologies into the HealthCare organizational workflow so that
the full benefits of the technology can be realized, reducing medical errors and increasing efficiency. - A patient culture that is empowered to embrace the new realities in HealthCare and wellness; to learn how patient accountability and responsibility will help reduce the load on the HealthCare system and support patients living healthier, happier lives.
I truly believe all of this and more is possible and worth doing.
The Medical Device Interoperability Incubator is designed to be self-funding, self-perpetuating and self-regulating, but its success depends upon people like you, Industry professionals like yourselves, from all disciplines, are needed to address the full range of issues in the present and future. I am seeking to assemble a core team to join with me to attract, engage and enroll: Founding Core Advisory Group
The founding core team will help me assemble people of power (Members, Sponsors and Partners) to participate and contribute to the Medical Device Interoperability Incubator, which is:
- Self-Funding from Member Services and Member Organizations’ Private Branded
App-based Network Configuration, ePackaging and Distribution; - Self-Perpetuating through “Word of Mouth” Member Successes; and
- Self-Regulating so we can remain in control of our own destiny.
As a founding core team, we will join together in the support of the common culture of unified Industry strength.
Don’t miss the Catch the Wave video for more details.
Member Organizations
Members make it all happen. Members join for the purpose of having a voice in drafting standards for MDNOS and developing their own Private Branded eMod™ Apps that create Private Branded App-based Networks. These Networks prepare staff and patients for the common mission of accepting the “New” Technology/Service and Methodology, to more effectively deliver “tomorrows HealthCare… today.”
Incubator and App Sponsors
Private Branded eMod™ Apps become a new and exciting media for sponsor awareness. Sponsors provide the financial backing to insure a consistent and cohesive flow of resources, as well as enhance communication to the community.
Incubator Partners and Advisory Board Representation
Partner services are integrated into the Medical Device Interoperability Incubator, which results in their services becoming part of the eMod™ Apps and App-based Networks. In this way, partners share generously in revenues earned in the Medical Device Interoperability Incubator, while strengthening their position as a pillar of direction for their industry.
The job is much bigger than me. I know that I can only see these issues from my viewpoint.
With your input, it will be fascinating to see what solutions we can achieve.
While working in AwareComm’s® Wisdom Incubator, I came across a story that touched me deeply. It talked to me in a way that I wanted to know more and be more than I was. Perhaps this story will invite you to jump out of the box and join me for even a bigger purpose.
Take a moment and watch the button below “The Stone.”
I am ready to get started, all I need is you!