One habit of showing the evidence.

The builder has spent twenty years as an engineer, nearly all of it inside one large health plan. The first ten were hands-on: application and data systems for claims, underwriting, customer service and the actuaries. The last ten have been architecture: data, integration and platform design across the organization, and the calls other teams bring when a choice cannot be undone. Along the way came enrollment, provider data, contracts, pricing and the reporting that explains it all to someone who was not in the room, one domain at a time, usually by asking to see how the next one worked. That is where the products get their sense of where the seams are.

The facility side of the picture comes from across the kitchen table. The person who sits there has spent a working life inside the facilities on the far end of those seams, a trauma center and a behavioral-health facility that serves adults and children: the dashboards a director runs the place by, the governance reporting, the audits nobody looks forward to, and the explaining, in both directions, when a vendor needs the place described or a clinician needs the software described. That person does not write the code.

A plan and a facility are usually two buildings that send each other files. Here they share a kitchen table. The person across it says what a director or an auditor would not accept; the builder decides what the software does about it.

Three products are live, in three different shapes: a read-only view over a clinical record, a four-application system for a health plan's provider data, and a retrieval system over contracts that would rather refuse than guess. A demo and three more things sit in the lab. Read as a list, that is a lot of surface for one person.

Read as a visit, it is one thing. A person is seen in a clinic, and the clinician needs the chart. The facility needs to know the visit happened and was documented. The plan needs to know who delivered it, and the claim needs a contract to be priced against. Somebody, eventually, asks what the contract actually says. Every product is one corner of that loop, and the loop is the reason there is more than one product.

The breadth is also how the habits were found. Cite-or-refuse, one door, synthetic data only: none of these was decided first and built toward. The corners were built separately, for different people, and afterwards the code turned out to have arrived at the same rules in each. What the products share was discovered, not declared, and it is the part Meadowlark trusts most.