Connected systems. Less manual reporting.

Data integrations

I connect existing applications, databases, and file-based processes through APIs and custom data workflows. I map the data between systems, add checks, and automate the transfers your staff handles by hand.

At the start, I agree the hosting and access requirements with your technical team, including how any supporting software fits into your existing infrastructure.

REDCap integrations

I build custom software around existing REDCap projects: API connections, submission-triggered processing, data transformations, and automated reporting. I work with your REDCap administrator on the access and project details the integration needs.

Reporting and calculation automation

I turn data from your existing systems into quality-indicator calculations, activity summaries, enrollment and timeline reports, and statistical outputs. Reports can run on an agreed schedule or as part of a submission workflow.

I translate your program’s criteria into calculations, test the expected results, and document the assumptions. Checks flag missing inputs and inconsistent totals before a report is shared. Your program staff retain responsibility for reviewing the results and making decisions.

Migration from manual process

I take the collection emails, spreadsheet calculations, and committee reports your staff prepares by hand and turn them into a repeatable workflow. I start by understanding the exceptions and institutional knowledge behind the process. Your staff’s time moves from calculating to deciding.

Planned maintenance

I make planned changes to integrations, calculations, and reports as your program evolves. Maintenance is scheduled in advance with a defined scope and delivery date. Your organization retains responsibility for day-to-day operations and time-sensitive incident response.

Continuity

You own what I build. Source, configuration, and documentation are handed over as the work is done, in a form your own staff or another developer can pick up without me. A practice of one should never mean a system only one person can run.