Get Engaged

Become a Member of the MD PnP Community

General Membership in the MD PnP Community is free, and ensures that you will receive notification of upcoming events, subscription to our occasional eNewsletter, and access to documentation, software, and educational materials. Community-building is an important part of moving forward with device interoperability.

Members of the MD PnP community will automatically qualify for the new RTI Infrastructure Community program for implementation of the Data Distribution Service (DDS), which includes access to their library of source code and OMG DDS software. RTI's program is intended to make it easy to build, test, integrate, and deploy high-performance, mission critical distributed systems.Click here to sign up for General Membership

Collaborate with our Research Team
 
The MD PnP research team is interested in collaborating with researchers working on architecture, communication, network security, and health IT infrastructure related to medical devices, and facilitating collaboration within the community. Contact us if you would like to propose collaboration on a specific project.

Take Advantage of Resources offered by MD PnP

Our Interoperability Lab in Cambridge is a collaborative space providing an environment of computing and medical device resources to support projects, testing, and prototyping work. MD PnP researchers share their expertise in presentations and publications.
Contact us if you would like to request content from our researchers or access to our lab.

Help Facilitate the Adoption of Interoperability

  • Clinicians can contribute clinical scenarios (or “use cases”) to ensure that new interoperability standards and technologies will enable meaningful clinical solutions. Diversity of use cases increases the likelihood of effective and generalizable solutions.
  • Engineers can analyze clinical use cases to generate functional specifications, assess current standards to perform “gap analyses”, and evaluate proposed technologies. Diverse engineering expertise is essential.
  • Healthcare delivery organizations can specify performance requirements, and require adherence to medical device interoperability language in vendor contracts, adopting the MD FIRE sample language now available and continuing to refine it. Widespread adoption of interoperability will happen only when there is recognized consumer demand.
  • Regulatory agencies can facilitate regulatory clearance of interoperable medical devices, creating new regulatory paradigms where needed.
  • Medical device manufacturers can participate in the development and adoption of interoperability standards, work with the FDA on the regulatory pathway, and partner with the MD PnP Program to develop a shared interoperability testing and use case demonstration environment.
  • Interoperability-promoting organizations can support revision of existing standards to meet clinical requirements, collaborate on clinical use case implementations in the MD PnP Lab, and ensure that through collaboration we shepherd the adoption of medical device interoperability to empower innovation in the safety and efficiency of health care.