Iodine Software Interact Mobile Case Study

Iodine Interact: 2-Minute Mobile Query Resolution Loops

How we re-engineered clunky, desktop-locked EMR widgets into an intuitive Material-designed mobile satellite app that maximizes clinician query response rates.

NDA & Simulation Notice

This project was executed under a strict Non-Disclosure Agreement (NDA). The interactive panels and dashboard mockups shown below represent sanitized, functional wireframes designed to simulate the core system logic and information architecture without disclosing proprietary client data. High-fidelity UI designs and case files are available upon request.

Request Hi-Fi Access

Physician-Facing Mobile satellite systems

Iodine Software provides sophisticated NLP and AI/ML tooling to help Clinical Documentation Improvement (CDI) specialists ensure electronic medical records (EMR) are accurate. A core component of this workflow is requesting clarification from physicians.

Previously, physicians could only respond to these queries using desktop EMR widgets (Epic/Cerner Compasses) at their workstations. Because hospitalists and private clinicians are constantly on the move, queries remained pending for days, impacting reimbursement rates.

Under Proto UX’s phased approach, we re-architected this process into the **Iodine Interact Mobile App**. Rather than rushing a product out, we designed the mobile workflow over a 14-week cycle, iteratively validating requirements with practicing physicians.

Proto UX Iterative Phasing Model

2 Weeks

Phase 1: UX Prep & UI

Stakeholder interviews (3-5), physician discoveries, HIPAA mobile guidelines, user profile mapping.

2 Weeks

Phase 2: Sprint 0 Onboarding

Infrastructure setup, test-driven development (TDD) pipelines, and low-fidelity interactive wireframes.

10 Weeks

Phase 3: Agile Delivery

Backend storage coding, Material-based Vuetify frontend, weekly physician feedback logs, and sprint deployments (Sprints 1-5).

The Target User Profiles

We mapped physician needs based on user discoverings, settling on two primary customer segments.

PRIMARY USER PROFILE

Brent, 31

Austin, TX • Internal Medicine Hospitalist

"I'm comfortable using my phone for work. I already use messaging, database lookup, and EMR apps provided by the hospital."

Setup: iPad Pro, iPhone X, work laptop

Tech Comfort: High ( Netflix, Reddit, Snapchat)

Behaviors & Motivations

Brent is swipe-badge authenticated on work desktops. Documenting charts and writing notes consumes most of his day. Because seconds add up when switching EMR tabs, he values system velocity.

Needs & Goals

Needs to resolve queries within 24 hours without administrative drag. Prefers a single batched notification per day rather than constant, real-time alerts.

Delight Parameters

Biometric Face ID authentication, fast response time, and ensuring he doesn't receive queries regarding previous doctor handoffs for the patient.

Key Design Takeaways

Through physician and stakeholder discoveries, we isolated several key design axioms that guided the Iodine Interact Mobile architecture:

The Chart Lookup Paradox: Physicians resist answering queries on mobile if they have to navigate EMR charts. By pulling and embedding geocoded **EMR clinical snippets** directly within the query body, 90% of queries can be answered with a simple single touch.
Batched Notification Flow: Rather than buzzes for every query, the system batches alerts once a day (in the afternoon before patient rounds), respecting doctor focus.
Off-Week Engagement: Securing the hospitalist's off-week meant making query resolution as frictionless as replying to a text message, directly linking performance to billing bonus allocations.