WRITING
Notes from building regulated software
Problems we have had to solve properly rather than approximately, written up while they are still fresh. Mostly about the unglamorous parts — clocks, money, evidence — because that is where operational software is actually won or lost.
Exporting a claim file is easy. Reconciling one is the job.
Most software treats claiming as an export and stops. Pricing at time of service, validating before submission, and matching remittance back line by line are where claims are actually won — and the test is whether a provider can close the month without opening a spreadsheet.
Read →Five business days is a harder problem than it looks
Weekends, state-by-state public holidays, when the clock starts, and an incident recorded at 4:58pm on the Thursday before Easter. Why the deadline should be derived from stored facts rather than saved as a field — and why a stored due date goes quietly wrong.
Read →What we write about
Everything here comes out of work we have actually done, so the subjects are narrow on purpose: computed compliance, government claiming integrations, audit evidence that survives staff turnover, tenant isolation and data residency, and award interpretation. If a topic is not something we have had to get right in production, it will not appear here.
If one of these problems is on your desk and you would like to compare notes, write to us — we are happy to talk about how we approached it, whether or not there is a project in it.