BD Clinical Interoperability Services UX

Legacy desktop based interoperability tools created operational friction because software updates, configuration changes, and support workflows could vary across hospital environments and vendor implementations.

Technical teams needed clearer visibility into how clinical data moved between EHR systems, routing channels, endpoints, Pharmacy Automation, Pyxis, and BD connected systems.

Troubleshooting was difficult because users needed to determine whether a message issue came from routing logic, connectivity, transformation rules, endpoint configuration, system status, or downstream delivery.

Data transformation added another layer of complexity because incoming EHR data structures often needed to be mapped, translated, or normalized before BD systems could interpret and process the information accurately.

The opportunity was to create a clearer CIS experience that made clinical data exchange easier to configure, monitor, troubleshoot, update, and support.

Instead of relying on fragmented desktop workflows and vendor dependent setup, CIS gives users a more consistent way to manage routing logic, review message activity, identify failures, trace message behavior, and understand how data moves across connected healthcare systems.

Design Solution:  Designed routing configuration workflows for inbound and outbound clinical data moving between external EHR systems and BD connected healthcare systems.

This experience helps integration teams define endpoints, manage channels, configure route behavior, and control how clinical data moves from source systems into Pharmacy Automation and Pyxis environments.

Design Solution:  Designed monitoring and troubleshooting workflows for tracking EHR data exchange, transaction activity, routing failures, and system connectivity issues.

This experience helps technical teams review message activity, understand what happened during data exchange, isolate failures, and investigate transaction history across the interoperability workflow.

Design Solution:  Designed message tracing workflows that help technical teams understand how clinical data moves, changes, and resolves across EHR systems, routing channels, endpoints, logs, transformations, and BD connected healthcare systems. 

This experience supports investigation of where a data message changed, failed, stalled, or moved successfully across the interoperability process. It helps users follow the full path of a message from source system through routing, transformation, delivery, and system response. 

Current work incorporates AI support to reduce manual investigation, surface likely failure points, and make complex message behavior easier to understand. 

This design makes complex interoperability workflows more understandable, traceable, and manageable. It helps technical users move from fragmented legacy workflows toward a clearer centralized experience for configuring, monitoring, transforming, and tracing clinical data across connected healthcare systems. 

The BD CIS work demonstrates my ability to design complex healthcare infrastructure experiences where usability, accuracy, traceability, auditability, and operational clarity are critical.

The final experience supports technical and clinical operations teams managing healthcare data exchange across EHR systems, BD systems, Pharmacy Automation, Pyxis, routing channels, monitoring workflows, transformation logic, and AI supported message tracing.