Skip to content
Testaroo
md5.8 KB

Juniper Fitness and Clinic Administration: healthcare document set README

Document set README for Juniper Fitness and Clinic Administration. 27 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

Preview, first 50 linesmd
# Juniper Fitness and Clinic Administration: superbill, X12 837 claim, X12 835 remittance and explanation-of-benefits documents

The claim administration a small clinic produces around its appointments: a superbill, the X12 837 professional claim that carries it, the X12 835 remittance that answers it, the explanation of benefits and patient statement that follow, and the registers, code tables and aging that hold the whole cycle together. The 837 and 835 pair is the part that is genuinely hard to find as a fixture, so it ships three ways: as EDI, as JSON, and with an envelope specification that documents its own delimiters.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Records are derived from the shared operating model `appointment-capacity`, so identifiers join across this set, across the other commercial document sets, and across every fixture built on the same model.

## Reconciliation identities this set asserts

- Each of the 16 confirmed bookings produces one encounter and one claim; the 2 cancelled bookings produce none.
- Charge equals allowed plus contractual on every claim: 1,180.00 splits into 876.00 and 304.00 USD.
- Allowed equals payer payment plus patient coinsurance: 876.00 splits into 700.80 and 175.20 USD.
- Every CLM02 in the 837 equals the SV102 amounts beneath it, and the SE segment count matches the segments actually present.
- Every BPR02 in the 835 equals the CLP04 amounts in its transaction set, and the 3 sets sum to 700.80 USD.
- Every provider identifier carries a valid modulo-10 check digit over the 80840 prefix.
- The denied claim is adjusted CO 97, a contractual group, so it becomes a write-off and not a patient balance.

## Parameters this set introduces

These are properties of the document class, not of the operating model. They are declared once and every file in the set agrees with them.

- Procedure codes, diagnosis codes, payers, the allowed rate and the coinsurance rate. The appointment model carries providers, rooms, slots and bookings and nothing clinical.
- The 80 percent allowed rate and the 20 percent coinsurance, applied uniformly across all three payers so that any difference between payers comes from adjudication rather than pricing.
- The X12 envelope values: sender, receiver, delimiters, control numbers and the T usage indicator, all recorded in x12-envelope-spec.json.
- A single synthetic date of birth of 1900-01-01 on every patient, and the clinic and provider identifiers.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `procedure-code-table.csv` | csv | valid | Procedure code table |
| `diagnosis-code-table.csv` | csv | valid | Diagnosis code table |
| `provider-roster.csv` | csv | valid | Provider roster |
| `payer-roster.csv` | csv | valid | Payer roster |
| `adjustment-reason-codes.csv` | csv | valid | Claim adjustment reason codes |
| `fee-schedule.csv` | csv | valid | Payer fee schedule |
| `encounter-register.csv` | csv | valid | Encounter register |
| `superbill-lines.csv` | csv | valid | Service line detail |
| `superbill-ENC-0006.pdf` | pdf | valid | Superbill (PDF) |
| `superbill-ENC-0006.docx` | docx | valid | Superbill (DOCX) |
| `claim-837p-batch.edi` | edi | valid | X12 837 professional claim batch |
| `claim-837p-CLM-0006.edi` | edi | valid | X12 837 professional claim, single claim |
| `claim-837p-CLM-0006-service-line-total-mismatch.edi` | edi | invalid | X12 837 claim whose service lines do not add up to the claim total |
| `claim-837p-batch.json` | json | valid | X12 837 batch rendered as JSON |
| `x12-envelope-spec.json` | json | reference | X12 envelope and delimiter specification |
| `remittance-835.edi` | edi | valid | X12 835 remittance advice |
| `remittance-835.json` | json | valid | X12 835 remittance rendered as JSON |
| `explanation-of-benefits-CLM-0006.pdf` | pdf | valid | Explanation of benefits (PDF) |
| `explanation-of-benefits-CLM-0006.docx` | docx | valid | Explanation of benefits (DOCX) |
| `eob-lines.csv` | csv | valid | Remittance adjustment lines |
| `claim-status-register.csv` | csv | valid | Claim status register |
… 71 lines total: download for the full file.

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
Documented Files
27
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 27 entries including this README, and the deliberate-defect section names 1 file(s) with the measured size of each discrepancy.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Juniper Fitness and Clinic Administration: healthcare document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 5,980 bytes. 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.