A clinical workflow platform physicians configure themselves

Smart Data managed the full redevelopment of the iDocData platform, then continued as the engineering partner through 15+ years of ongoing feature work.

Architecture decisions that shaped the rebuild

• Configurable clinical workflows. Clinical administrators (not engineers) build surveys, scoring algorithms and document templates through the platform UI. Reference-name conventions handle variable uniqueness across complex multi-question-set scoring. That way, physician-specific documentation flows survive engineering turnover.
• Automated patient outreach. SMS and email reminders for survey completion with handlebars-style templating. Cadence is configurable per study: notify after X days, remind every Y days, send up to Z reminders. Patient outreach is not a separate vendor; it runs inside the platform.
• Multi-tenant deployment. A single codebase serves multiple clinical sites with isolated data, branding and configuration. New sites onboard through configuration, not code.
• Global Pages pattern. Screen-level components are reusable across clinical acts and study contexts. Physician-specific UI customization happens through HTML and CSS overrides at the page and control level, without forking the platform.
• JSON-configured reporting. Administrators define custom reports queryable by date, study and survey path through configuration, not code.
• Epic HL7 integration. Patient demographics and clinical context flow through HL7 to the production deployments running Epic.
• Containerized cloud architecture. Today the platform runs as Node.js services in Docker containers on AWS, with PostgreSQL backing the configurable layer, and CI/CD pipelines support iterative feature delivery without site-by-site coordination.

Migration approach: Rebuilt the original Java and XML desktop application as one multi-tenant web platform while preserving every existing physician workflow. The custom UI engine that allowed physicians to maintain personalized documentation flows was rebuilt, not replaced. Migration completed with zero data loss and minimal downtime.

The rebuild shipped with no data loss and minimal downtime, and the platform has been in production at multiple clinical sites for 15+ years without significant maintenance overhead.

Since the rebuild, the platform has stayed in production and moved onto current cloud infrastructure without major maintenance events, while the systems around it have changed several times.