The domain expert knew the pain. The product still had to be discovered.
SmartDocs worked closely with EMS organizations through training and inspections. The owner understood the operational and compliance problems in detail and asked whether those workflows could become software.
My role was to translate that expertise into a system: what data belongs to a run, what should be scored, what users need to see, and what reports make the information useful.
A Drupal platform shaped around real EMS workflows.
I built the platform on Drupal using Webforms, custom modules, dynamic scoring, and report generation. Drupal provided a durable content and permissions foundation while custom logic handled the domain-specific behavior that made the system more than a generic form repository.
- Structured ambulance-run reporting
- Dynamic scoring and evaluation logic
- Custom operational workflows
- Generated reports for review and follow-up
The important result was behavior in the field.
Organizations using the platform reported significantly fewer deficiencies and fines. I do not have a defensible percentage and do not present one; the useful evidence is the consistent qualitative result reported back by users and the continuing use of the system.
The company and platform kept going.
SmartDocs remains in business and continues to grow. The platform is now beginning another evolution toward AI-enabled capabilities.
That longevity matters to me because this was not a disposable prototype. It became part of an operating company and accumulated real workflow data over time.
Good product architecture starts with translating domain expertise.
- Work closely with a non-software domain expert.
- Model operational rules rather than merely digitizing forms.
- Build on a platform that can evolve with the business.
- Measure success through sustained use and operational outcomes.