IVAN FERLAND / EXPERTISE
Software, systems, and the work between them.
Build a tool, connect an existing application, restore a workflow: here is how I approach the work, and where to explore it.
← HomeApplication development
Turn a business process into software people can use: clear interfaces, explicit rules and records that stay consistent as the work changes. Model the workflow, build the interface and test the complete journey.
Integration and automation
Connect the steps between systems. Define what moves, what triggers an action and what happens when an input or dependency fails. Use validated exchanges and replay checks to prevent accidental duplicate work.
COBOL and legacy modernization
Give established business logic a modern interface while preserving the rules that make it useful. Make record formats, decimal arithmetic, compatibility and safe failure part of the integration contract.
Data and application dependencies
Understand how an application uses its records, where relationships can break and how to validate a change without losing the business workflow. Investigate dependencies and design consistent state transitions.
Infrastructure and service dependencies
Follow the chain from the user’s workstation to the application, service and data it needs. Make permissions, runtime requirements and recovery steps explicit before changing a system.
Clinical technology
Work across practice-management applications, clinical imaging, claims connectivity and their server/database dependencies. Delivered a major share of a national ITRANS ICD 2.0 migration across hundreds of dental practices, including remote implementation, troubleshooting and workflow validation.
Incident investigation and recovery
Turn a recurring problem into a clear investigation: establish impact, test explanations, restore the workflow and leave a useful record. Separate recovery from root-cause confirmation and make the next action clear.
Web delivery and release
Take a web application from source to a verifiable release. Keep configuration, automated checks, runtime packaging and operating notes together, and make deployment and rollback decisions reviewable.
Technical delivery in two languages
Connect technical decisions with the people responsible for the outcome. Clarify scope, coordinate implementation, validate the workflow and explain the next step in English or French.