Presentation
Designing User Interfaces with Interoperability in Mind
SessionSystems (MDD4)
DescriptionInteroperability has received a lot of focus in recent years from regulators and organizations such as FDA and AAMI, especially with regard to the technical challenges that the concept presents such as back-end communication between multiple devices and the cybersecurity considerations for those communications. However, no one medical device manufacturer owns every single aspect of the healthcare ecosystem. So, how do you design for Human Factors around the interaction points between devices if: 1) you don’t have any control over them, and 2) they are subject to change based on use environment, region, and many other variables? Where do you draw the line between designing for interoperability and over-constraining your design with too many inputs that are not in your control?
Based on our collective experience, here are some important considerations when designing a medical device with interoperability in mind:
1) Take the time to research all potential users, use environments, markets, and workflow variations (intended and unintended).
2) Consider what data needs to be transferred, how often, and under what circumstances.
3) Consider variations between the devices / departments / functions that create and receive the data.
4) Consider the look/feel/operation of adjacent medical devices.
5) Consider all user groups in the ecosystem (installation, clinical, service, IT).
6) Truly understand the entire user experience, including edge cases where increased security or religious considerations may limit the use of certain technologies.
7) Perform UFMEA for awareness of potential issues and consider what use error recovery looks like at every stage of information transfer.
Our presentation would step through relevant examples about how these considerations could be applied to a design without getting stuck in the quicksand of “analysis paralysis;” i.e., not knowing or having access to every possible variation of an interface point such as HIS/RIS/EMR and not having control over upstream or downstream mitigations.
Based on our collective experience, here are some important considerations when designing a medical device with interoperability in mind:
1) Take the time to research all potential users, use environments, markets, and workflow variations (intended and unintended).
2) Consider what data needs to be transferred, how often, and under what circumstances.
3) Consider variations between the devices / departments / functions that create and receive the data.
4) Consider the look/feel/operation of adjacent medical devices.
5) Consider all user groups in the ecosystem (installation, clinical, service, IT).
6) Truly understand the entire user experience, including edge cases where increased security or religious considerations may limit the use of certain technologies.
7) Perform UFMEA for awareness of potential issues and consider what use error recovery looks like at every stage of information transfer.
Our presentation would step through relevant examples about how these considerations could be applied to a design without getting stuck in the quicksand of “analysis paralysis;” i.e., not knowing or having access to every possible variation of an interface point such as HIS/RIS/EMR and not having control over upstream or downstream mitigations.
Event Type
Oral Presentations
TimeTuesday, March 268:30am - 9:00am CDT
LocationContinental Ballroom, Lobby Level
Medical and Drug Delivery Devices