API development, web services and Windows services
REST and SOAP APIs, WCF services and background Windows services that other systems call every day.
API development is half of system integration. The other half is the background work behind the API: Windows services that pull from queues, retry failed calls and record what happened. We build both in .NET, for systems that other teams and partners depend on.
Services and APIs we build
-
REST API development
ASP.NET Core endpoints versioned by schema, each consumer with a typed client.
-
SOAP and WCF services
Upkeep and new endpoints for partners that still call SOAP.
-
Windows services
Queue workers, schedulers and intake services that run unattended.
-
System integration services
Partner, regulator and clearing systems connected through adapters.
-
Retries and incidents
Retry queues that separate transient from permanent failures, and alerts that carry context.
Services other systems call
-
HEDIS measurement pipelineTransient and permanent failures go to separate retry queues in the HEDIS engine we built, and on-call staff get a Slack message with the order attached.
-
Clinical data aggregation hubRequest budgets in our clinical aggregation hub stop one consumer from starving the others.
-
FHIR · TEFCA · USCDI integrationPayer-to-payer Member Match on our FHIR server issues a short-lived signed JWT for each Patient/$match call.
-
HIPAA audited file proxyEvery read, download and expiry in our clinical file proxy goes into an audit dataset that compliance can query directly.
-
Energy billing systemBilling software we built for energy distributors exchanges data with national clearing pipelines.
Language and runtime: .NET development. Desktop software on the same machines: Windows desktop applications.
How service work starts
-
Callers and load
Tell us who calls the service, what it processes, where it runs and what fails.
-
Contract first
We write the API contract or WSDL and agree it with the teams that call it.
-
Parallel run
The new service answers part of the real traffic before the old one is switched off.
And much more. Ask about your project
Common questions
Can you keep our SOAP services running?
Which systems call your services?
Describe the service, its callers and the servers it runs on.