Juniper Fitness and Clinic Administration: Receivable aging by payer
Receivable aging by payer for Juniper Fitness and Clinic Administration. The 3 payers plus a total row. On every row paid plus patient responsibility plus written off equals charged, and the three aging buckets sum to the outstanding column. Nothing is older than thirty days because every claim was paid 17 days after submission, so the whole 175.20 USD outstanding sits in the first bucket and is owed by patients rather than by payers.
csv
text/csv
- Document Set
- healthcare
- Industry
- fitness-clinic-administration
- Source Kit
- appointment-capacity
- Entity
- Juniper Fitness and Clinic Administration
- Synthetic
- true
- As Of
- 2026-09-08
Binary csv: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Document Set
- healthcare
- Industry
- fitness-clinic-administration
- Source Kit
- appointment-capacity
- Entity
- Juniper Fitness and Clinic Administration
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 4
- Outstanding Total
- 175.20
- Outstanding Owed By
- patients
- Buckets Beyond30 Days
- 0.00
Testing contract
Expected to pass- Scenario
- Check both identities on every row and decide who owes the outstanding balance.
- Expected result
- All 4 rows balance on both identities. The outstanding 175.20 USD is patient coinsurance, not unpaid payer liability: the payers have paid 700.80 and written off 304.00, which with the coinsurance is the whole 1180.00 charged.
What is a .csv file?
CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.
How to use this file
Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.
How to use this file for testing
“Juniper Fitness and Clinic Administration: Receivable aging by payer” is a deterministic Novus Examples fixture for Data import, CSV parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: 4 rows. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import pandas as pd
df = pd.read_csv("aging-by-payer.csv")
print(df.head())
print(df.dtypes)Related files
- csvJuniper Fitness and Clinic Administration: Claim adjustment reason codesClaim adjustment reason codes for Juniper Fitness and Clinic Administration. The 5 adjustment codes the remittance uses, each with its group code and whether it is contractual, patient responsibility or another adjustment. The distinction matters: a CO adjustment can never be billed to the patient and a PR adjustment is exactly what is billed, so a reader that ignores the group code bills the wrong party.
- csvJuniper Fitness and Clinic Administration: Diagnosis code tableDiagnosis code table for Juniper Fitness and Clinic Administration. The 3 diagnosis codes referenced by the claims, all of them administrative rather than clinical: a routine assessment, a follow-up and an equipment familiarisation visit. Every code is a synthetic placeholder and the table says so in its own column.
- csvJuniper Fitness and Clinic Administration: Patient rosterPatient roster for Juniper Fitness and Clinic Administration. The 16 patients, which are the fictional visitor names the appointment model already carries, joined to their booking, encounter, claim and payer. Every row carries the same synthetic date of birth of 1900-01-01 and a column that says so, because the X12 claim needs a demographic segment and this set will not hold a plausible personal record to fill it.
- csvJuniper Fitness and Clinic Administration: Payer fee schedulePayer fee schedule for Juniper Fitness and Clinic Administration. 12 rows, every procedure against every payer. All three payers use the same 80 percent allowed rate and the same 20 percent coinsurance, so the schedule is deliberately uniform and any difference a reader finds between payers in the remittance comes from adjudication rather than from pricing.
- csvJuniper Fitness and Clinic Administration: Payer rosterPayer roster for Juniper Fitness and Clinic Administration. The 3 payers with their claim counts and money. Claims sum to 16, charges to 1,180.00 USD, allowed to 876.00 and paid to 700.80, which are the same control totals the remittance and the reconciliation carry.
- csvJuniper Fitness and Clinic Administration: Procedure code tableProcedure code table for Juniper Fitness and Clinic Administration. The 4 procedure codes this clinic bills, with the charge, the allowed amount at 80 percent of charge and the contractual adjustment that is the difference. The code_system column says on every row that these are synthetic placeholders in the five-character shape, not values from any real code set.
Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.