Case Study

Walter – The “OS” for Swisscoding

In the Swiss medical landscape, diagnoses and treatments are coded to assign Diagnostic Related Groups (DRGs) to patients. This, along with the total hospitalization duration, forms the basis for comprehensive case billing. Recognizing the critical nature of this coding process, Swisscoding saarl aimed to centralize medical coding resources and skills across hospitals and clinics in Switzerland, covering all specialties and scales—delivering to each client, the benefits of such a pool of experience & expertise.

I was approached to build & drive the core system that would get this undertaking on the road.

The CEO’s Challenge.

Despite being a first-mover, Swisscoding faced a bevy of early challenges—including the absence of SOPs for collaboration, non-existent data pipelines, and skepticism about an external vendor. The priority was to be highly tech enabled, yet to start small and operate with a lean tech-stack from day one.

The user-base ranged in age and tech-savviness, and consisted of global collaborators. Familiarity with medical coding and the density of such data was not an issue for most users, but usability, simplicity and efficiency of the system was. Data had to reside within Switzerland due to privacy concerns and bureaucratic red-tape between doctors and administrators posed additional hurdles.

TheDemanding

TheVisionaryUser

CEO

Swisscoding Group

Stefan Stefaniak

"I want a proprietary, robust,SCALEABLE system"

"I want to STAY LEAN but move fast"

"I want to synergize expertise across hospitals, while adapting to the constraints ofLEGACY HOSPITAL SYSTEMS "

"I want to establish trust, ensure quality andREDEFINE THE PARADIGM for Swiss Medical Coding."

The Solution.

The solution followed an iterative and evolutionary path—with a focus on internal case management and data ingestion workflows, on building trust and evangelization of clients, and progressive expansion of scope. There was a balance between the old (data-dense interfaces) & the new (simplified and lucid interfaces).

As the sole partner for a UX, design & technology solution—I designed and developed a multi-lingual, multi-modal system named Walter, initially conceived as a ‘butler’ managing case data, automating and streamlining internal workflows. A web-app deployed on Microsoft’s Azure in Switzerland, Walter redefined data ingestion and presentation, training users across roles through simplified yet data-dense interfaces.

Across 5 years of continuous improvement, besides designing and developing the system, I managed the data and maintained it, delivering a solution that not only solved for the users’ challenges but also ensured an extraordinary 99.99% uptime (merely 5 hours of downtime in 5 years).

This engine emerged as the vital core of Swisscoding operations, and also became the preferred workflow for its clients — essentially becoming the OS for Swisscoding ++.”

The CASC Ecosystem.

Walter Workflow & Case Anatomy

An efficient, information rich process-map in Walter's workflow helped with daily coding tasks. Each information and coordination subsystem was implemented as a microservice within the tool, and accessible via REST APIs.

Powerful Business Intelligence

Business Intelligence was one of the initial goals of Walter, and is amply provided for through its powerful views on company data. This was a major enabler for the C-suite of the company.

CRM & Invoicing

The introduction of complex contract structures and the scale of operations required Walter to up its financial management game as well.1

Ensuring Quality

Walter not only helped perform comprehensive coding reviews, but also had features to help identify cases that needed such attention.

Client Data & Processes

Despite the initial friction and skepticism, Walter evangelized clients by making it easy to prepare and track case progress. It became an integral part of the Client Liaison's workflow.

The Evolution of Walter. Two major releases – Walter 1.0 and Walter 2.0.

2018
L
2018

Basic ERP System (Walter 0.1)

UX/UI/Features: The original system was a basic ERP with integration of basic hospital data feeds (OFS input), user and case management, time tracking, secure patient data handling, internal messaging and fora, and an IT ticket system.

Technology: Walter 0.1 was bootstrapped as a single-page (BackboneJS, UnderscoreJS) MVC app  built on top of a bespoke WordPress plugin (PHP, MySQL). WordPress was used simply for its built-in user and role management.

2019
L
2019

Scaling Up (Walter 1.0)

UX/UI/Features: As client trust grew, so did the demand for additional user roles in the system. Many stakeholders such as client liaisons and external coders expressed interest in utilizing Walter’s robust, user-friendly interface to manage their workflows.

Technology: The REST API and message-based architecture played a crucial role during this phase. The system was also transitioned to Microsoft Azure infrastructure, and the system and codebase was refactored to use MS-SQL (T-SQL) to take advantage of this change. Walter 1.0 was here.

2020
L
2020

Deeper Integrations, CRM, Accounting (Walter 1.x)

UX/UI/Features: Much deeper integrations with hospital systems & data were achieved, automatic decision making enabled. A proprietary, integrated planning, invoicing, and accounting subsystem was also designed for Swisscoding’s complex contract structures.

Technology: The first foray into ML based methods implemented, automation and rule-based decision engines were developed, a message-based architecture strengthened, and Azure infrastructure leveraged further.

2021-2022
L
2021-2022

The Advent of CASC (Walter 2.0)

UX/UI/Features+: With increased data volume and expertise, we laid the foundation for CASC (Computer Aided Swiss Coding). Collaborating with EPFL engineers, we conceptualized tools like Queen (Quality & Optimization) and Lexicode (Manuals & Standardized Documents), and I also developed a design system to build on Walter’s success.

Technology: ISO Certification hurdles were overcome, and there was an increased focus on DevOps. The frontend was also rewritten in VueJS, and integrated it with CASC. Walter 2.0 was born.

The Workflow.  Anatomy of the case workflow established by Walter and how it fed into the system.

Walter in action. A simple but powerful, actionable “List Mode”

Designed for Business Intelligence.

Walter was designed with powerful filtration methods and dashboard construction capabilities in mind.

The ability to create multiple actionable dashboards — easily mapped to client & process KPIs was an important objective. The ability to automate varied rules/directives and also to create customized views and worklists for delegation to users enabled Swisscoding to eliminate complex BI integrations. The ability to track case progress with high granularity within such views was an added bonus, and was greatly appreciated by the users.

User Stories (how Walter simplified workflows for various stakeholders)

Multiple Use Cases. Singular focus on Simplicity.

Walter was eventually expanded in scope to many more user roles than initially planned for. The journey was harder for some use-cases, but  transformative for and genuinely useful for each such user.  Explore use cases and some of the challenges overcome above.

There have been a lot of great contributions to Swisscoding’s success story. But for Walter though, Swisscoding simply would not exist.

Stefan Stefaniak

CEO, Swisscoding Group