Provide Record-Level Field Mapping for New Inputs and Outputs
To support upstream system updates and integration activities, stakeholders have requested additional documentation showing where newly introduced input and output fields will appear within record-level downloads.
In particular, Greg requested visibility into:
- Which new fields have been added
- The position of those fields within each record-level file
- Example values for each new field
- There is a strong preference for newly introduced fields to be appended to the end of record-level
- Environment
- Staging cedars-2
- Select user type
Log in to comment and vote
Comments2
cedars team
Jul 23
Hi @ggreen,
Below are two example 2026 Claims Record-Level download files:
example_claims_records_2026_expected_layout.xlsx
19.8 KB• Spreadsheet
example_claims_records_2026_appended_layout.xlsx
19.7 KB• Spreadsheet
Both files include the new 2026 input/output fields with example values. The expected_layout file demonstrates the current order/position of fields, while the appended_layout file appends all new fields to the end as a group.
Please note that in order to preserve the visual highlighting of the new input/output fields, these files have each been formatted as an XLSX file with two sheets (one sheet each for the record-level claims data and the participant data) rather than the expected ZIP-compressed CSV format.
Roopa Reddy
Jul 23
@cedars team I'm following up on the feedback requested during the July 22 development demos call. PG&E does not have any major concerns regarding the ordering of the newly added input or output fields. However, from a user perspective, the data may be easier to review and utilize if related fields are grouped together in a more logical and intuitive manner. Thank you.