This specification is a draft (v6) and is subject to change. Contact your Customer Success Partner (CSP) for the current version before building or changing a delivery.
RevSpring Connect for Payers, Cost supports three delivery scenarios for price transparency data. Which one applies depends on who produces your in-network machine-readable files (MRFs) and whether RevSpring hosts them. Your CSP can confirm your scenario.
Scenario 1: RevSpring generates your in-network MRFs.
You send your Transparency in Coverage (TiC) data. RevSpring generates the in-network MRFs, and an adapter may create the standardized files from your source extracts.
Scenario 2: Your payer or vendor supplies the in-network files.
RevSpring hosts your table of contents and may use those files for Cost. You do not need to rebuild vendor provider groups or rates.
Scenario 3: Cost data only.
RevSpring does not host MRFs for you. You send the files that map your products to the MRF sources Cost will use.
Files by scenario
| File | Scenario 1 | Scenario 2 | Scenario 3 |
|---|---|---|---|
| CONTROL_FILE | Required | Required | Required |
| PLAN_DETAILS | Required | Required | Required |
| NTWK_MAPPING | Required | Required | Not used |
| NTWK_PROVIDERGRPCNTRCT | Required | Not used | Not used |
| PROVIDER_IDENTIFIERS | Required | Not used | Not used |
| INNETWORK_NEGOTIATED_RATE | Required | Not used | Not used |
| ATTESTATION | Required | Required | Not used |
| EXTERNAL_MRF_MAPPING | Conditional | Required | Conditional |
| BILLING_CODES | Required | Conditional | Conditional |
| POS_MAPPING | Required | Conditional | Conditional |
| COVERED_BUNDLED_BILLING_CODES | Conditional | Not used | Not used |
| OUTOFNETWORK_ALLOWED_AMOUNT | Conditional | Conditional | Conditional |
Delivery basics
- Send the CONTROL_FILE last, after the rest of the data set. It lists each file, its record count, and the spec version.
- Files can be pipe-delimited text or CMS-compliant JSON.
- File names follow the pattern CLIENTCODE_FILENAME_YYYYMMDD_HH24mmss.txt.
What’s changing in draft v6
- MRF_Key replaces Plan_Collection_Key in PLAN_DETAILS.
- The legacy NCK is removed from PROVIDER_IDENTIFIERS.
- The layout aligns to the draft CMS 3.0 schema.
Field-level details, including some lengths and valid values, are still being finalized. Your CSP will share the full specification when it is ready.