BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20250327T203344Z
LOCATION:Frontenac Foyer
DTSTART;TZID=America/New_York:20250331T164500
DTEND;TZID=America/New_York:20250331T181500
UID:HFESHCS_2025 International Symposium on Human Factors and Ergonomics i
 n Health Care_sess147_POST290@linklings.com
SUMMARY:MDD23 - Off to the Races: Keeping Pace with Product Development
DESCRIPTION:Poster Presentation\n\nSuruchi Batra and Layne Hartman (Emergo
  by UL)\n\nManufacturers are constantly challenged with the prospect of ke
 eping up with the accelerated rate of technological advancement. The days 
 of slowly and steadily releasing a product to the market have long since p
 assed. Now, manufacturers need to begin product “version 2” development, i
 ncluding usability testing, before version 1 has even received de novo aut
 horization. \n\nImagine having just received the good news of de novo laun
 ch! The entire company is thrilled but they have already been working on s
 ystem updates and are pursuing an aggressive submission timeline for the n
 ext version. R&D teams are often already prepared to continue designing an
 d readying updated product versions and software releases. But what happen
 s when those advancements affect the critical tasks of the product? Is it 
 true that manufacturers must prepare to re-validate the entire system? And
 , if so, should these validation tests include all user groups?\nThis pres
 entation will define the different strategies manufacturers and consultant
 s can take to balance the desire for conservative product development appr
 oaches with potentially expansive usability testing cycles, regulatory rev
 iew timelines, and associated time and monetary “costs.” It will also expl
 ore these differences as they apply to varying submission types (e.g., 510
 (k), Special 510(k), letter to file).\n\nIn this presentation, we plan to:
 \n- Define and provide examples of what types of product updates might req
 uire supplemental HF validation testing. These would include: \n -- impact
 s to existing critical tasks\n -- creation of new critical tasks – or of n
 ew essential tasks related to new or existing critical tasks\n -- indicati
 on expansions\n -- user group modifications\n -- UI design changes, whethe
 r or not they are related to essential or critical tasks\n\n- Explain how 
 to leverage HF documentation to determine the scope for supplemental testi
 ng. This would include:\n -- Leveraging a KPA or post-market surveillance 
 data analysis to identify or draw comparisons between indications of use a
 nd/or users of similar product types\n -- Conducting a literature review t
 o identify or draw comparisons between indications of use and/or users of 
 similar product types\n -- Comparing the “original” risk analysis to the u
 pdated risk analysis to specifically determine which essential and/or crit
 ical tasks have been impacted\n -- Analyzing any task analysis and/or inte
 nded workflow changes resulting from product updates and identifying where
  user interactions might differ with the new system \n -- Identifying pote
 ntial impacts to critical tasks and the resulting potential harm(s)\n -- A
 nalyzing data collected during previous usability tests – and most importa
 ntly validation test(s) – to determine if any findings observed during suc
 h tests are related to critical tasks and/or user groups impacted by the n
 ew system and/or its modified indication for use\n\n- Provide strategies f
 or navigating these different updates and, relatedly, how to determine the
  proper testing scope. These strategies might include:\n -- Affected criti
 cal tasks, including new or modified essential tasks: consider only re-eva
 luating essential and critical tasks affected by design updates, and justi
 fying that remaining critical tasks are not affected and, notably, have al
 ready been validated. Furthermore, consider evaluating these impacted task
 s with a limited number of participants per user group (e.g., 8 rather tha
 n 15).\n -- Indication expansions: consider justifying that the added indi
 cation does not affect the user population and/or workflow. For example, i
 f the product is a surgical robotic system that is intended for general su
 rgical procedures, consider justifying that the same user population would
  use the system in the same way even with another surgical procedure. \n  
    --- If the added indication does affect the user population or intended
  use specifications, prepare a list of sub-tasks that might be affected by
  the additional indication and develop a justification to solely evaluate 
 those tasks.\n -- User group modifications: Consider developing a justific
 ation that the altered and/or additional user group(s) are not different w
 ith regard to Human Factors. For example, the expanded indication of use m
 ight have distinct clinical applications, but those applications do not ex
 tend to usability (i.e., the user interactions with the system). \n -- If 
 there are distinct user interactions with the expanded indications of use,
  prepare a usability study that focuses only on tasks that would be comple
 ted by the altered and/or added user group(s).\n -- UI design changes: con
 sider justifying that these design changes either do not affect critical t
 asks, or that they can only serve to reduce harm/design out use errors for
  critical tasks. This is similar to the justifications of design changes t
 hat sometimes happen after HF Validation but before full submission. For e
 xample, something like changing the background from a pure while to a pale
  cream color on a GUI might not have a significant affect, but changing th
 e color of a button or adding an indication light might. \n\n - Discuss re
 cent FDA feedback about testing devices undergoing updates\n -- For indica
 tion expansions, manufacturers should focus on proving that individual pro
 cedures are still safe and effective, such as by demonstrating clinical ba
 ckgrounds and applications do not impact user interactions with the system
 \n -- Consider which user groups are “procedure-agnostic” and could be con
 sidered “proxy” participants for other user groups. For example, if there 
 are some tasks that both sterile and circulating nurses are responsible fo
 r, consider whether including only one type of nurse is sufficiently repre
 sentative for both user groups\n\nTrack: Digital Health (DH), Simulation a
 nd Education (SE), Hospital Environments (HE), Medical and Drug Delivery D
 evices (MDD), Patient Safety and Research Initiatives (PS)
END:VEVENT
END:VCALENDAR
