Capabilities
Everything a critical application needs, from one team.
i-tecsol takes an application from design through build, integration, hosting, daily operation and protection, so there is one accountable team across its whole life.
What i-tecsol does
Web applications
Platforms, portals and internal tools built around the work users must complete.
Desktop and mobile
Windows desktop applications in .NET and apps for iOS and Android, planned as parts of the same operation as the web software.
Healthcare workflows
Patient, prescription, compounding, clinical, insurance, billing, document, staff-queue and delivery processes, built under HIPAA discipline.
Integration and data
APIs, enterprise application integration, reporting and data pipelines that move information between existing systems.
Telephony and call centers
Call handling, SMS, activity records, escalations, dashboards, agent administration and quality review, connected to operational records.
Infrastructure and cloud
Servers, storage, networks, virtualization and containers, on-premises or in the cloud, across several sites where needed.
Operations and support
Monitoring, releases, fixes and user questions, handled by the people who built and run the system.
Security and compliance
Hardening, continuous checks, access control, logging and written reviews, including HIPAA, as a business associate. How we protect what we run.
Technology
The stacks we work in
Broad on purpose: the right stack is chosen per system and kept current.
- Web and services
- ASP.NET and C# · PHP · Node.js · Python
- Desktop
- Windows applications in .NET
- Mobile
- iOS · Android
- Data
- SQL Server · MySQL · PostgreSQL
- Infrastructure
- Windows and Linux servers · virtualization and containers · on-premises and cloud · networks across sites
- Communications
- Telephony · SMS · call-center platforms · chat
- Integration
- APIs · enterprise application integration · data pipelines between existing systems
How a project starts
- Describe the operation.
Explain what staff do, which systems they use and where work stops or repeats.
- Define the data involved.
Identify patient information, documents, calls, transactions and system boundaries.
- Choose the smallest useful scope.
Start with the workflow or integration that can produce a clear operational result.
- Plan how it will run.
Include deployment, monitoring, support and protection instead of treating release as the end of the work.
Bring the current workflow, not a polished brief.
i-tecsol can begin with a direct account of the problem and the systems already in place.