Machine-readable file
A machine-readable file is a digital file structured so that a computer can import and process it without a person reading each entry. Federal price-transparency rules use the format as their vehicle for bulk price disclosure: the Transparency in Coverage rule requires health plans and issuers to post files of their negotiated rates and out-of-network allowed amounts, and the Hospital Price Transparency rule requires hospitals to post a file of their standard charges. The files are meant for software and analysis, not for a quick human lookup.
Updated
A machine-readable file is a digital file whose contents are structured so a computer system can import and process them automatically, without human intervention. Under the federal Transparency in Coverage rule, the codified definition is "a digital representation of data or information in a file that can be imported or read by a computer system for further processing without human intervention, while ensuring no semantic meaning is lost" (45 CFR 147.210(a)).
The regulation defines what the file must accomplish but does not itself name a file format. The specific technical format — an open, non-proprietary format such as JSON — is set by the Departments' implementation guidance rather than by the regulatory text, which is why the files are readable by software yet impractical to open and scan by hand.
In practice
Machine-readable files are the vehicle two federal price-transparency rules use for bulk disclosure. Under Transparency in Coverage, a group health plan or issuer must post files of its in-network negotiated rates, its out-of-network allowed amounts and billed charges, and covered prescription drugs, updated monthly and accessible free of charge without a login or any submission of personal information (45 CFR 147.212(b)). Under the separate Hospital Price Transparency rule, a hospital posts a machine-readable file of its standard charges.
For a billing operation the files are a cross-reference, not a source of truth. They are built at the payer or hospital level and are very large — a plan's file spans an entire network — so they are made for bulk analysis, not to look up one rate. A practice's executed contract and loaded fee schedule remain the authoritative record of what it is owed; the file can help corroborate a rate but does not replace the contract.
Commonly confused with
- Consumer-friendly display / self-service tool: A machine-readable file is the software-facing artifact. Its human-facing counterparts are different deliverables under the same rules: the Transparency in Coverage member self-service tool returns a personalized cost estimate, and the Hospital Price Transparency consumer-friendly display shows shoppable-service charges. Those are built for a person to read; the machine-readable file is built for a computer.
- Electronic remittance advice (835): An 835 electronic remittance advice is a machine-processable transaction too, but it reports how a specific claim was adjudicated and paid. A price-transparency machine-readable file is a public, standing disclosure of rates and charges, not a claim-level payment record for one encounter.