class: theme layout: true --- class: center, middle <div class="image-collage"> <img src="assets/images/failed_synergy_import.png" alt="Failed Synergy Import"> <img src="assets/images/load_sapio_config_error.png" alt="Load Sapio Config Error"> <img src="assets/images/release_46_bundle_error.png" alt="Release 46 Bundle Error" class="large-image"> <img src="assets/images/sapio_no_index_barcode_not_found_Error_1.png" alt="No Index Barcode Error"> <img src="assets/images/seq_complete_exp_error.png" alt="Seq Complete Exp Error"> </div> # Sapio Sciences™ Integration ### Engineering Perspective on Medical Software Integration ### Saurabh @ OUS AMG - 20/08/2025 --- class: middle # Surviving Clinical Software Integration 🏥 **The ground reality:** - Complex proprietary systems with limited integration support and accessible documentation - Integration development taking months instead of weeks - Limited vendor accountability for technical quality? **Our Journey:** - Built custom integration to connect Bioinf pipeline and Sapio Sciences™ LIMS - Write tests for integration components, without concrete data models, testing server - Get triggered by the triggers **Today's Goals:** - Share real-world integration challenges and (possible solutions?) - Learn from others who have done this (successfully?) --- class: middle # The idea was "simple" - **Steps**: New bioinformatics pipeline build with Maestro - **New LIMS**: Sapio Sciences™ - **Integration Layer**: Custom middleware which can be part of Steps - **Data Flow**: Lab → LIMS ↔ Bioinformatics Pipeline ↔ ELLA --- class: middle # Zappy .left-column[  ] .right-column[  ] --- class: middle # The waiting game - The integration draft is ready - We need to run concrete integration tests to ensure things are working as expected - Complete E2E depends on Sapio delivering "Bioinf Triggers" --- class: middle # Let's host the LIMS on Hetzner  --- class: middle # How many clicks again? <video width="100%" controls onloadeddata="this.playbackRate = 16;"> <source src="assets/videos/WGS_SINGLE_TRIO.mp4" type="video/mp4"> Your browser does not support the video tag. </video> --- class: middle # Engineering Lessons from Proprietary Software 🔧 **Sapio LIMS:** - Out of date practices for release and updates - Lack of documentation - Who needs tests anyways? - Production system update, Webhook maintenance? Staging verification **Integration Anti-Patterns:** - Can we haz data model plz? - Direct ways to trigger events - Client or API? **Developer Experience Issues:** - No local development environment - Limited debugging capabilities - Poor documentation and examples - Feedback cycles --- class: middle # Proposed: Standard Integration Framework 🛠️ **Framework Components:** - **Vendor Evaluation Checklist**: Technical requirements for new systems - **Integration Patterns Library**: Reusable components and templates - **Testing Framework**: Standardized test suites for vendor systems - **Monitoring Standards**: Common observability and alerting practices **Qualification Requirements for Vendors:** ``` □ REST API with OpenAPI specification □ Bulk data export/import capabilities □ Comprehensive testing □ Error handling documentation □ Performance SLA guarantees □ and more? ``` **Benefits:** - Faster integration development (weeks vs months) - Consistent quality across departments - Vendor accountability through standardized requirements --- class: middle # Thank You! - opinions? - your own (horror) stories? - questions?