Juniper Fitness and Clinic Administration: X12 837 batch rendered as JSON
X12 837 batch rendered as JSON for Juniper Fitness and Clinic Administration. The same 16 claims as a JSON document, so a test can compare a parser output against an expected structure without reimplementing the X12 grammar. Control totals are hoisted to the document: 16 claims, 18 service lines and 1,180.00 USD.
json
application/json
- 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 json: 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
- Claims
- 16
- Service Lines
- 18
- Charge Total
- 1180.00
Testing contract
Expected to pass- Scenario
- Parse the EDI batch, serialise it, and compare it with this document claim by claim.
- Expected result
- Both carry 16 claims and 18 service lines, every claimTotal equals the sum of its own service line charges, and the document control totals equal the aggregate.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Juniper Fitness and Clinic Administration: X12 837 batch rendered as JSON” is a deterministic Novus Examples fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: JSON · 7,453 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.
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 json
with open("claim-837p-batch.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonJuniper Fitness and Clinic Administration: Healthcare reconciliation identitiesHealthcare reconciliation identities for Juniper Fitness and Clinic Administration. 6 named identities covering the booking to claim mapping, both money splits, the 837 and 835 balance rules and the denial that is deliberately not a patient balance. The invalid 837 and its measured 20.00 USD difference are listed separately, with a flag recording that the file is structurally valid.
- jsonJuniper Fitness and Clinic Administration: X12 835 remittance rendered as JSONX12 835 remittance rendered as JSON for Juniper Fitness and Clinic Administration. The same 3 payments and 16 claims as a JSON document with the adjustments as objects carrying their group and reason codes, so the contractual and patient-responsibility split is explicit rather than something a reader has to infer from a CAS segment position.
- jsonJuniper Fitness and Clinic Administration: X12 envelope and delimiter specificationX12 envelope and delimiter specification for Juniper Fitness and Clinic Administration. The delimiters, envelope values and segment counts for every X12 file in this directory, including the invalid one, so a test harness can be configured from the fixture rather than by guessing. It also records that the usage indicator is T for test and that every patient carries the same synthetic date of birth.
- jsonAlder Books Reconciliation: Banking reconciliation identitiesBanking reconciliation identities for Alder Books Reconciliation. 5 named identities covering the amortisation, the unfinanced arrangement fee, the covenant directions, the direct debit control sum and the two different chargeback totals, with the figures behind each. The deliberate defect and its measured 36.15 USD closing balance are listed separately.
- jsonAlder Books Reconciliation: Credit application JSONCredit application JSON for Alder Books Reconciliation. The same application as an object, with each financial summary row keeping the source string that names the file and column it came from. The connected facility is a nested object rather than a string, so a reader can tell that the existing borrowing belongs to a different entity.
- jsonAlder Table Bistro: Cost of goods sold documentCost of goods sold document for Alder Table Bistro. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1736.91, purchases 2834.82, closing 2996.92, cost of goods sold 1574.81 CAD.
Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.