bhsim 1.0.0rc2__tar.gz

bhsim-1.0.0rc2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Rahul Byrapuneni
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

bhsim-1.0.0rc2/PKG-INFO

@@ -0,0 +1,267 @@
+Metadata-Version: 2.4
+Name: bhsim
+Version: 1.0.0rc2
+Summary: Privacy-first synthetic behavioral health operations simulator
+Author: Rahul Byrapuneni
+Maintainer: Rahul Byrapuneni
+License: MIT
+Keywords: synthetic-data,behavioral-health,sqlite,power-bi
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Provides-Extra: ui
+Requires-Dist: streamlit>=1.35; extra == "ui"
+Requires-Dist: pandas>=2.0; extra == "ui"
+Dynamic: license-file
+
+# BHSim
+
+### Synthetic behavioral health data, ready for SQL and analytics
+
+BHSim is an open-source Python library that creates **fictional, connected behavioral health records** for SQL practice, BI dashboards, software testing, and analytics prototypes.
+
+Instead of hand-building spreadsheets or borrowing sensitive patient data, you can generate a small SQLite database with clients, programs, staff, appointments, enrollments, and screening assessments—and start querying it right away.
+
+**Created and maintained by Rahul Byrapuneni.**
+
+> **Important:** BHSim generates synthetic test data, not real patient records. Its scheduling, attendance, assessment trajectories, and productivity assumptions are examples for development and learning—not clinical predictions, diagnostic advice, official reporting definitions, or billing guidance.
+
+## What can BHSim generate?
+
+- **Individuals:** Fictional names, dates of birth, demographic fields, and unique numeric identifiers.
+- **Programs:** Mental health (MH), substance use (SA), and intellectual/developmental disabilities (IDD) services.
+- **Enrollments:** Admissions, discharges, multiple concurrent programs, and re-enrollment histories.
+- **Employees:** Staff records, program assignments, and supervisor relationships.
+- **Visits:** Completed, no-show, canceled, rescheduled, and upcoming appointments, with scheduled and actual service times.
+- **Productivity:** Example service-unit calculations linked to visits and program rules.
+- **Assessments:** PHQ-9 and GAD-7 with readable question text, answer choices, responses, and total scores for complete assessments.
+
+The records are linked through primary and foreign keys, so you can practice realistic joins without needing access to an EHR.
+
+## Quick start
+
+**Requirements:** Python 3.10 or newer. No database server, paid API, or patient data is needed.
+
+BHSim is currently available from its GitHub repository. To install it directly:
+
+```bash
+python -m pip install git+https://github.com/rahulbyrapuneni/bhsim.git
+```
+
+> PyPI publication is planned, but **`pip install bhsim` is not yet the documented installation method**.
+
+Create a file named `example.py`:
+
+```python
+from bhsim import BHSimulator
+
+# ---SET UP A SYNTHETIC ORGANIZATION---
+sim = BHSimulator(
+    clients=1000,
+    employees=80,
+    history_months=12,
+    future_days=30,
+    seed=42,
+)
+
+# ---GENERATE, CHECK, AND EXPORT---
+sim.generate("behavioral_health.db")
+print(sim.validate())
+sim.to_csv("output")
+```
+
+Run:
+
+```bash
+python example.py
+```
+
+You'll get `behavioral_health.db` plus a folder of CSV files, one for each table. A successful validation returns a result with `"valid": true` and an empty `issues` list.
+
+**Already have an output database?** BHSim deliberately refuses to overwrite it. Choose a new filename or move the old one before generating another dataset.
+
+### Prefer the command line?
+
+```bash
+python -m bhsim generate demo.db --clients 100 --seed 42
+python -m bhsim validate demo.db
+python -m bhsim export-csv demo.db output
+```
+
+The installed `bhsim` command can be used instead of `python -m bhsim` when it is available on your PATH.
+
+## Explore the data with SQL
+
+You can open the generated `.db` file with a SQLite-compatible editor, including [SQLime](https://sqlime.org/), or use Python's built-in `sqlite3` library.
+
+### Appointments by program
+
+```sql
+SELECT
+    p.program_code,
+    p.description AS program_name,
+    COUNT(*) AS appointments,
+    SUM(CASE WHEN v.visit_status = 'COMPLETED' THEN 1 ELSE 0 END) AS completed,
+    SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END) AS no_shows
+FROM visits AS v
+JOIN programs AS p ON p.program_id = v.program_id
+GROUP BY p.program_code, p.description
+ORDER BY appointments DESC;
+```
+
+### No-show rate by program
+
+```sql
+SELECT
+    p.program_code,
+    COUNT(*) AS eligible_appointments,
+    SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END) AS no_shows,
+    ROUND(
+        100.0 * SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END)
+        / COUNT(*), 2
+    ) AS no_show_pct
+FROM visits AS v
+JOIN programs AS p ON p.program_id = v.program_id
+WHERE v.visit_status IN ('COMPLETED', 'NO_SHOW')
+GROUP BY p.program_code
+ORDER BY no_show_pct DESC;
+```
+
+This example uses **completed + no-show** visits as its denominator. Organizations may define reportable no-show measures differently.
+
+### Individual visit history
+
+```sql
+SELECT
+    i.individual_id,
+    i.full_name,
+    p.program_code,
+    v.visit_status,
+    v.scheduled_start,
+    e.full_name AS employee_name
+FROM visits AS v
+JOIN individuals AS i ON i.individual_id = v.individual_id
+JOIN programs AS p ON p.program_id = v.program_id
+JOIN employees AS e ON e.employee_id = v.employee_id
+ORDER BY v.scheduled_start DESC
+LIMIT 20;
+```
+
+### Read actual assessment questions and selected answers
+
+BHSim keeps question text and answer choices in lookup tables instead of repeating them in every response. The built-in view joins those tables for you:
+
+```sql
+SELECT
+    instrument_code,
+    question_text,
+    selected_answer,
+    score_value
+FROM assessment_responses_readable
+LIMIT 20;
+```
+
+PHQ-9 contains nine scored symptom items (complete total: **0–27**); GAD-7 contains seven (complete total: **0–21**). Incomplete assessments do not receive a complete total. Scores in BHSim are simulated screening data, **not diagnoses**.
+
+## How the tables fit together
+
+| Area | Tables | What they represent |
+|---|---|---|
+| People and programs | `individuals`, `programs`, `individual_programs` | Individuals and their enrollment episodes |
+| Workforce | `employees`, `employee_programs`, `employee_supervision` | Staff assignments and reporting relationships |
+| Services | `visits`, `visit_types`, `locations` | Scheduled appointments and documented services |
+| Productivity | `productivity_rules`, `visit_productivity` | Example rules and calculated units |
+| Assessments | `assessment_instruments`, `assessment_questions`, `answer_options`, `assessments`, `assessment_responses`, `assessment_scores` | Forms, questions, selected answers, and scored submissions |
+| Supporting data | `simulation_metadata` | Configuration and generation metadata |
+
+There is also an `assessment_responses_readable` **SQL view** for simpler queries.
+
+Identifiers are numeric-looking **TEXT** values, with fixed lengths defined by entity type. They are deliberately nonsequential and are joined by ID, not by name. Names may repeat, just as they can in real records.
+
+## Customize a run
+
+These are the main settings available through the Python API:
+
+| Parameter | Example | Meaning |
+|---|---|---|
+| `clients` | `1000` | Number of fictional individuals |
+| `employees` | `80` | Number of fictional staff records |
+| `history_months` | `12` | Historical period to simulate |
+| `future_days` | `30` | Days of upcoming appointments |
+| `reference_date` | `"2026-10-10"` | Simulation's reference date, in `YYYY-MM-DD` format |
+| `seed` | `42` | Controls the pseudorandom sequence for reproducibility |
+
+**What is a seed?** With the same BHSim code, settings, and seed, generation is reproducible. Change the seed to get a different fictional dataset. The number `42` has no special meaning.
+
+Some program-specific probabilities, operating hours, and productivity assumptions are currently defined internally rather than exposed as configurable API options.
+
+## Data checks
+
+BHSim includes a validator for core integrity rules:
+
+```bash
+python -m bhsim validate demo.db
+```
+
+You can also run these independent SQLite checks:
+
+```sql
+-- Broken foreign keys: expect no rows
+PRAGMA foreign_key_check;
+
+-- Completed visits without valid service timestamps: expect zero
+SELECT COUNT(*) AS invalid_completed_visits
+FROM visits
+WHERE visit_status = 'COMPLETED'
+  AND (actual_start IS NULL OR actual_end IS NULL
+       OR actual_end <= actual_start);
+
+-- Visits without a matching program enrollment: expect zero
+SELECT COUNT(*) AS visits_outside_enrollment
+FROM visits AS v
+WHERE NOT EXISTS (
+    SELECT 1
+    FROM individual_programs AS ip
+    WHERE ip.individual_id = v.individual_id
+      AND ip.program_id = v.program_id
+      AND DATE(v.scheduled_start) >= DATE(ip.start_date)
+      AND (ip.end_date IS NULL OR DATE(v.scheduled_start) <= DATE(ip.end_date))
+);
+```
+
+Validation checks **consistency**, not whether the generated statistics match real healthcare populations.
+
+## Contributing and developing locally
+
+```bash
+git clone https://github.com/rahulbyrapuneni/bhsim.git
+cd bhsim
+python -m pip install -e ".[dev]"
+python -m pytest -q
+```
+
+The library's main code lives under `src/bhsim/`. `app.py` is an **optional Streamlit demonstration**; it is not needed for library installation or use. To run the demo, install the optional UI dependencies with `python -m pip install -e ".[ui]"`, then use `python -m streamlit run app.py`.
+
+Contributions that improve documentation, validation, reproducibility, or realistic *synthetic* workflows are welcome. Please don't submit real patient records or other protected health information in issues, examples, or tests.
+
+## Limitations and responsible use
+
+- All records are fictional. BHSim does **not** access EHRs or require patient data.
+- Generated distributions are illustrative; the library has not been validated as a model of real-world clinical outcomes, demographics, or utilization.
+- PHQ-9 and GAD-7 are screening instruments. Simulated scores are not diagnoses, treatment recommendations, or a substitute for clinical judgment.
+- Visit eligibility currently assumes a matching enrollment episode; un-enrolled crisis-service exceptions are not generated in this release.
+- Scheduling checks cover completed-service conflicts, not every possible appointment-booking workflow.
+- Productivity units use demonstration rules and should not be treated as reimbursement or billing guidance.
+- Existing databases are not automatically migrated when the schema changes. Newer releases use `full_name` in place of the older `synthetic_name` column.
+- Questionnaire wording and names belong to their respective instrument originators. Preserve attribution and confirm the relevant usage terms before redistributing or using the instruments clinically.
+
+## License and author
+
+BHSim is released under the [MIT License](LICENSE). See the repository's `LICENSE` file for its full terms. Instrument attribution and third-party rights are separate from the project's software license.
+
+**Creator & maintainer:** [Rahul Byrapuneni](https://github.com/rahulbyrapuneni)  
+**Repository:** [github.com/rahulbyrapuneni/bhsim](https://github.com/rahulbyrapuneni/bhsim)
+
+Developed using AI-assisted software engineering, with behavioral health domain direction and product design led by the creator.

bhsim-1.0.0rc2/README.md

@@ -0,0 +1,249 @@
+# BHSim
+
+### Synthetic behavioral health data, ready for SQL and analytics
+
+BHSim is an open-source Python library that creates **fictional, connected behavioral health records** for SQL practice, BI dashboards, software testing, and analytics prototypes.
+
+Instead of hand-building spreadsheets or borrowing sensitive patient data, you can generate a small SQLite database with clients, programs, staff, appointments, enrollments, and screening assessments—and start querying it right away.
+
+**Created and maintained by Rahul Byrapuneni.**
+
+> **Important:** BHSim generates synthetic test data, not real patient records. Its scheduling, attendance, assessment trajectories, and productivity assumptions are examples for development and learning—not clinical predictions, diagnostic advice, official reporting definitions, or billing guidance.
+
+## What can BHSim generate?
+
+- **Individuals:** Fictional names, dates of birth, demographic fields, and unique numeric identifiers.
+- **Programs:** Mental health (MH), substance use (SA), and intellectual/developmental disabilities (IDD) services.
+- **Enrollments:** Admissions, discharges, multiple concurrent programs, and re-enrollment histories.
+- **Employees:** Staff records, program assignments, and supervisor relationships.
+- **Visits:** Completed, no-show, canceled, rescheduled, and upcoming appointments, with scheduled and actual service times.
+- **Productivity:** Example service-unit calculations linked to visits and program rules.
+- **Assessments:** PHQ-9 and GAD-7 with readable question text, answer choices, responses, and total scores for complete assessments.
+
+The records are linked through primary and foreign keys, so you can practice realistic joins without needing access to an EHR.
+
+## Quick start
+
+**Requirements:** Python 3.10 or newer. No database server, paid API, or patient data is needed.
+
+BHSim is currently available from its GitHub repository. To install it directly:
+
+```bash
+python -m pip install git+https://github.com/rahulbyrapuneni/bhsim.git
+```
+
+> PyPI publication is planned, but **`pip install bhsim` is not yet the documented installation method**.
+
+Create a file named `example.py`:
+
+```python
+from bhsim import BHSimulator
+
+# ---SET UP A SYNTHETIC ORGANIZATION---
+sim = BHSimulator(
+    clients=1000,
+    employees=80,
+    history_months=12,
+    future_days=30,
+    seed=42,
+)
+
+# ---GENERATE, CHECK, AND EXPORT---
+sim.generate("behavioral_health.db")
+print(sim.validate())
+sim.to_csv("output")
+```
+
+Run:
+
+```bash
+python example.py
+```
+
+You'll get `behavioral_health.db` plus a folder of CSV files, one for each table. A successful validation returns a result with `"valid": true` and an empty `issues` list.
+
+**Already have an output database?** BHSim deliberately refuses to overwrite it. Choose a new filename or move the old one before generating another dataset.
+
+### Prefer the command line?
+
+```bash
+python -m bhsim generate demo.db --clients 100 --seed 42
+python -m bhsim validate demo.db
+python -m bhsim export-csv demo.db output
+```
+
+The installed `bhsim` command can be used instead of `python -m bhsim` when it is available on your PATH.
+
+## Explore the data with SQL
+
+You can open the generated `.db` file with a SQLite-compatible editor, including [SQLime](https://sqlime.org/), or use Python's built-in `sqlite3` library.
+
+### Appointments by program
+
+```sql
+SELECT
+    p.program_code,
+    p.description AS program_name,
+    COUNT(*) AS appointments,
+    SUM(CASE WHEN v.visit_status = 'COMPLETED' THEN 1 ELSE 0 END) AS completed,
+    SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END) AS no_shows
+FROM visits AS v
+JOIN programs AS p ON p.program_id = v.program_id
+GROUP BY p.program_code, p.description
+ORDER BY appointments DESC;
+```
+
+### No-show rate by program
+
+```sql
+SELECT
+    p.program_code,
+    COUNT(*) AS eligible_appointments,
+    SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END) AS no_shows,
+    ROUND(
+        100.0 * SUM(CASE WHEN v.visit_status = 'NO_SHOW' THEN 1 ELSE 0 END)
+        / COUNT(*), 2
+    ) AS no_show_pct
+FROM visits AS v
+JOIN programs AS p ON p.program_id = v.program_id
+WHERE v.visit_status IN ('COMPLETED', 'NO_SHOW')
+GROUP BY p.program_code
+ORDER BY no_show_pct DESC;
+```
+
+This example uses **completed + no-show** visits as its denominator. Organizations may define reportable no-show measures differently.
+
+### Individual visit history
+
+```sql
+SELECT
+    i.individual_id,
+    i.full_name,
+    p.program_code,
+    v.visit_status,
+    v.scheduled_start,
+    e.full_name AS employee_name
+FROM visits AS v
+JOIN individuals AS i ON i.individual_id = v.individual_id
+JOIN programs AS p ON p.program_id = v.program_id
+JOIN employees AS e ON e.employee_id = v.employee_id
+ORDER BY v.scheduled_start DESC
+LIMIT 20;
+```
+
+### Read actual assessment questions and selected answers
+
+BHSim keeps question text and answer choices in lookup tables instead of repeating them in every response. The built-in view joins those tables for you:
+
+```sql
+SELECT
+    instrument_code,
+    question_text,
+    selected_answer,
+    score_value
+FROM assessment_responses_readable
+LIMIT 20;
+```
+
+PHQ-9 contains nine scored symptom items (complete total: **0–27**); GAD-7 contains seven (complete total: **0–21**). Incomplete assessments do not receive a complete total. Scores in BHSim are simulated screening data, **not diagnoses**.
+
+## How the tables fit together
+
+| Area | Tables | What they represent |
+|---|---|---|
+| People and programs | `individuals`, `programs`, `individual_programs` | Individuals and their enrollment episodes |
+| Workforce | `employees`, `employee_programs`, `employee_supervision` | Staff assignments and reporting relationships |
+| Services | `visits`, `visit_types`, `locations` | Scheduled appointments and documented services |
+| Productivity | `productivity_rules`, `visit_productivity` | Example rules and calculated units |
+| Assessments | `assessment_instruments`, `assessment_questions`, `answer_options`, `assessments`, `assessment_responses`, `assessment_scores` | Forms, questions, selected answers, and scored submissions |
+| Supporting data | `simulation_metadata` | Configuration and generation metadata |
+
+There is also an `assessment_responses_readable` **SQL view** for simpler queries.
+
+Identifiers are numeric-looking **TEXT** values, with fixed lengths defined by entity type. They are deliberately nonsequential and are joined by ID, not by name. Names may repeat, just as they can in real records.
+
+## Customize a run
+
+These are the main settings available through the Python API:
+
+| Parameter | Example | Meaning |
+|---|---|---|
+| `clients` | `1000` | Number of fictional individuals |
+| `employees` | `80` | Number of fictional staff records |
+| `history_months` | `12` | Historical period to simulate |
+| `future_days` | `30` | Days of upcoming appointments |
+| `reference_date` | `"2026-10-10"` | Simulation's reference date, in `YYYY-MM-DD` format |
+| `seed` | `42` | Controls the pseudorandom sequence for reproducibility |
+
+**What is a seed?** With the same BHSim code, settings, and seed, generation is reproducible. Change the seed to get a different fictional dataset. The number `42` has no special meaning.
+
+Some program-specific probabilities, operating hours, and productivity assumptions are currently defined internally rather than exposed as configurable API options.
+
+## Data checks
+
+BHSim includes a validator for core integrity rules:
+
+```bash
+python -m bhsim validate demo.db
+```
+
+You can also run these independent SQLite checks:
+
+```sql
+-- Broken foreign keys: expect no rows
+PRAGMA foreign_key_check;
+
+-- Completed visits without valid service timestamps: expect zero
+SELECT COUNT(*) AS invalid_completed_visits
+FROM visits
+WHERE visit_status = 'COMPLETED'
+  AND (actual_start IS NULL OR actual_end IS NULL
+       OR actual_end <= actual_start);
+
+-- Visits without a matching program enrollment: expect zero
+SELECT COUNT(*) AS visits_outside_enrollment
+FROM visits AS v
+WHERE NOT EXISTS (
+    SELECT 1
+    FROM individual_programs AS ip
+    WHERE ip.individual_id = v.individual_id
+      AND ip.program_id = v.program_id
+      AND DATE(v.scheduled_start) >= DATE(ip.start_date)
+      AND (ip.end_date IS NULL OR DATE(v.scheduled_start) <= DATE(ip.end_date))
+);
+```
+
+Validation checks **consistency**, not whether the generated statistics match real healthcare populations.
+
+## Contributing and developing locally
+
+```bash
+git clone https://github.com/rahulbyrapuneni/bhsim.git
+cd bhsim
+python -m pip install -e ".[dev]"
+python -m pytest -q
+```
+
+The library's main code lives under `src/bhsim/`. `app.py` is an **optional Streamlit demonstration**; it is not needed for library installation or use. To run the demo, install the optional UI dependencies with `python -m pip install -e ".[ui]"`, then use `python -m streamlit run app.py`.
+
+Contributions that improve documentation, validation, reproducibility, or realistic *synthetic* workflows are welcome. Please don't submit real patient records or other protected health information in issues, examples, or tests.
+
+## Limitations and responsible use
+
+- All records are fictional. BHSim does **not** access EHRs or require patient data.
+- Generated distributions are illustrative; the library has not been validated as a model of real-world clinical outcomes, demographics, or utilization.
+- PHQ-9 and GAD-7 are screening instruments. Simulated scores are not diagnoses, treatment recommendations, or a substitute for clinical judgment.
+- Visit eligibility currently assumes a matching enrollment episode; un-enrolled crisis-service exceptions are not generated in this release.
+- Scheduling checks cover completed-service conflicts, not every possible appointment-booking workflow.
+- Productivity units use demonstration rules and should not be treated as reimbursement or billing guidance.
+- Existing databases are not automatically migrated when the schema changes. Newer releases use `full_name` in place of the older `synthetic_name` column.
+- Questionnaire wording and names belong to their respective instrument originators. Preserve attribution and confirm the relevant usage terms before redistributing or using the instruments clinically.
+
+## License and author
+
+BHSim is released under the [MIT License](LICENSE). See the repository's `LICENSE` file for its full terms. Instrument attribution and third-party rights are separate from the project's software license.
+
+**Creator & maintainer:** [Rahul Byrapuneni](https://github.com/rahulbyrapuneni)  
+**Repository:** [github.com/rahulbyrapuneni/bhsim](https://github.com/rahulbyrapuneni/bhsim)
+
+Developed using AI-assisted software engineering, with behavioral health domain direction and product design led by the creator.

bhsim-1.0.0rc2/pyproject.toml

@@ -0,0 +1,27 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "bhsim"
+version = "1.0.0rc2"
+description = "Privacy-first synthetic behavioral health operations simulator"
+readme = "README.md"
+requires-python = ">=3.10"
+license = {text = "MIT"}
+authors = [{name = "Rahul Byrapuneni"}]
+maintainers = [{name = "Rahul Byrapuneni"}]
+keywords = ["synthetic-data", "behavioral-health", "sqlite", "power-bi"]
+
+[project.optional-dependencies]
+dev = ["pytest>=8"]
+ui = ["streamlit>=1.35", "pandas>=2.0"]
+
+[project.scripts]
+bhsim = "bhsim.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

bhsim-1.0.0rc2/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

bhsim-1.0.0rc2/src/bhsim/__init__.py

@@ -0,0 +1,5 @@
+"""BHSim synthetic behavioral health dataset library."""
+from .engine import Config, generate, validate, export_csv
+from .simulator import BHSimulator
+__version__ = "1.0.0rc2"
+__all__ = ["BHSimulator", "Config", "generate", "validate", "export_csv"]

bhsim-1.0.0rc2/src/bhsim/__main__.py

@@ -0,0 +1,4 @@
+from .cli import main
+
+if __name__ == "__main__":
+    main()

bhsim-1.0.0rc2/src/bhsim/cli.py

@@ -0,0 +1,26 @@
+import argparse
+import json
+from .engine import Config, generate, validate, export_csv
+
+def main():
+    parser=argparse.ArgumentParser(description='BHSim synthetic behavioral health data generator')
+    sub=parser.add_subparsers(dest='command',required=True)
+    gen=sub.add_parser('generate')
+    gen.add_argument('path')
+    gen.add_argument('--clients',type=int,default=1000)
+    gen.add_argument('--employees',type=int,default=80)
+    gen.add_argument('--months',type=int,default=12)
+    gen.add_argument('--future-days',type=int,default=30)
+    gen.add_argument('--reference-date',default='2026-10-10')
+    gen.add_argument('--seed',type=int,default=42)
+    valid=sub.add_parser('validate');valid.add_argument('path')
+    exp=sub.add_parser('export-csv');exp.add_argument('path');exp.add_argument('directory')
+    a=parser.parse_args()
+    if a.command=='generate':
+        result=generate(a.path,Config(a.clients,a.employees,a.months,a.future_days,a.reference_date,a.seed))
+    elif a.command=='validate':result=validate(a.path)
+    else:result=export_csv(a.path,a.directory)
+    print(json.dumps(result,indent=2))
+    if a.command=='validate' and not result['valid']:raise SystemExit(1)
+
+if __name__=='__main__': main()