Juniper Fitness and Clinic Administration — Workflow and import guide

# Juniper Fitness and Clinic Administration

Synthetic scheduling and resource-administration records for a shared fitness and clinic reception desk, without clinical or health information.

All entities and transactions are fictional. Snapshot: 2026-09-08.

## Start with the linked model

1. Open operations.xlsx and review the Summary sheet. Source tables contain stable primary keys and declared references.
2. Change source values in the workbook to explore the calculated totals and editable chart.
3. Compare output values with expected-results.json. The JSON Schema checks types; primary-key uniqueness and joins also require the listed semantic checks.
4. Use invalid-records.json only in a local validation harness. Its three cases exercise duplicate keys, wrong types and an orphan reference.

## Included tables

| Table | Records | Primary key |
| --- | ---: | --- |
| providers | 3 | provider_id |
| slots | 24 | slot_id |
| bookings | 18 | booking_id |
| resources | 3 | resource_id |
| communications | 18 | message_id |

## Expected totals

- Available slots: 24.00 slots. Sum slots.capacity over the included records.
- Occupied slots: 16.00 slots. Sum bookings.occupied over the included records.
- Booking records: 18.00 records. Count unique booking_id values in bookings.

## Platform mapping

primary-records.csv is a generic example table. It is not a native platform export. Where this kit includes a named profile, use that profile’s separate CSV and schema and review its compatibility level before uploading.

## Scope and assumptions

- No symptoms, diagnoses, patient history, medical identifiers or actual visitors are included. Communications are unsent draft examples.