MCHS NWAU Calculator MCP server

NWAU Calculator

Contributing | Security | Code of Conduct | Citation

This project provides Python translations of the IHACPA SAS funding calculators. Modules cover acute, emergency department, mental health, subacute and outpatient activity along with HAC and AHR adjustment logic. The implementation is being brought into explicit parity with the official SAS calculators, but validation is tracked per calculator and year rather than claimed as complete across the whole repository. The current implementation still uses pandas-based paths, while the longer-term data stack is moving toward Arrow-backed interchange and Polars where parity work allows it. A lightweight command line interface is available via the funding-calculator script.

The public documentation site is published from the Starlight scaffold in docs-site/ and serves as the canonical docs front door. The GitHub Pages deployment path is wired through .github/workflows/docs-site.yml. Open the docs at .

Releases

Releases are tag-driven and start from v0.2.0-style tags. The repo uses release drafts for notes and a release workflow to build distributions and publish GitHub Releases from tagged commits. Tagged releases also trigger Python package publishing to PyPI through trusted publishing. The Rust GA workflow also publishes Rust artifacts to GitHub Releases, but crates.io submission is not wired in this repository yet. The conda-forge recipe draft is maintained under conda/recipe/; new conda packages are currently recipe-only until a staged-recipes PR is accepted and the package appears on the public channel; users should treat conda-forge as unpublished until that registry record exists. All release claims still depend on the CI and validation gates passing for the tagged source.

Maven Central readiness

The JVM binding has repo-side Maven publishing metadata and a manual GitHub Actions workflow. Maven Central publication is still not claimed because the external Central Portal account gates remain open:

CENTRALPORTALPASSWORD provisioned in the release secret store;

• a registered Central Portal namespace for the publishable JVM coordinates;
• CENTRALPORTALDEPLOYURL, CENTRALPORTAL_USERNAME, and

secret store.

• MAVENSIGNINGKEY and MAVENSIGNINGPASSWORD provisioned in the release

secrets are supplied; dry-runs are intentionally credential-free.

• Local JVM readiness checks use exact Gradle commands:
• gradle -p bindings/jvm tasks --all
• gradle -p bindings/jvm publishAllPublicationsToCentralPortalRepository --dry-run --console=plain
• Real publish attempts fail closed unless deploy URL, credentials, and signing

Package registry status

As of 2026-05-26:

Shortened. The full README is on GitHub.