filer_inventory
What one hospital filer carries, so a call that prices something is a call that answers. One filer in, one answer out, and no figure anywhere in it. The loop this replaces is guessing a code, being refused, and reading the edition note in the refusal. That loop works and it costs a call per guess, and it teaches nothing about the codes nobody thought to guess. Back from this tool come the groupers that filer files, the codes this build can answer under each, the counterparty strings exactly as the hospital wrote them, how the filer says its figures were arrived at, and the facilities inside it. Read the groupers before the codes. A grouper the filer files that this build answers nothing under is listed apart, with the rows behind it and the reason, because this filer files no such admission, this world does not read that grouper, and this world reads it and nothing in this filing came through the parse are different answers to one question. A list is not a census. The codes are the codes this extract can answer, the counterparty strings are that filer's own free text and resolve to nobody, and every count counts cells in a document rather than admissions, patients or payments. An absence from any list here is a fact about this document and never about what the filer performs or prices. No money, at any depth. A listing that also priced things would be a second, thinner pricing surface without the methodology, the two row counts, the reporting floor and the refusals that decide what a figure means, so an argument reaching for a median, a minimum, a maximum or a total is refused and told which tool serves it. Nothing here is ordered either: there is no figure on this payload to order by, and an ordering of filers is a ranking this world refuses at its own boundary.
Use this form for new arguments. Follow concrete links for known values. Fetch-only readers may be unable to submit new URLs.
Exact input contract
{
"additionalProperties": false,
"properties": {
"filer": {
"description": "One health system, named as this corpus names it. Required: this tool answers for one filer at a time and computes nothing across them, because one filer is a large share of the corpus and a figure across them would be a figure about that one filer wearing a wider name.",
"enum": [
"cleveland-clinic",
"hca-medical-city",
"hss",
"mount-sinai",
"northwell",
"nyu-langone",
"vanderbilthealth-com"
],
"type": "string"
}
},
"required": [
"filer"
],
"type": "object"
}