The technical implementation guide for the tri-departmental price transparency rule.
The technical implementation guide for the tri-departmental price transparency rule.
Since the schema has the HIOS ID/EIN (plan_id) associated with the 'plan_name', wouldn't the plan_name need to associate with the file name? Otherwise, how does the schema support multiple plan_id information in one file, as the reporting information, plan_name and plan_id seems to identify/associate to the file name. I was confused by the file naming standard examples provided too.
provider_group_id malicious compliance and making things not machine readable
CMS validator for 2.0
"business name" and reporting clarification needed for providers with SSN only.
Does allowed amounts file (out of network) need to contain setting field? Validator throws error either way
In Network Rates sample file contains version 1.0.0 but is updated to the 2.0.0 spec
Negotiated Rate based on CMS Inpatient Psychiatric Facility PPS : Per-Diem + DRG + Comorbidities + Age + Length of Stay Adjustment
CSTM-ALL descriptions are inconsistent
EAPG Rates on Price Transparency Machine Readable File Requirment
Difference between negotiated, derived and fee schedule negotiated type - related question