Integration boundary · STATIC DECLARATIONS

NPHIES and Fatoora in the current core integration boundary

Source boundary for NPHIES and Fatoora in the current core: 39 Python backend mappings, 8 client declarations and 0 service routes. Installation, mounts and production qualification require verification.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Declared component boundary

embedded core integration surfaces. Static implementation evidence is separate from NPHIES certification, authorized package pin, taxpayer/unit onboarding and production credential qualification.

Routes and installation

These are embedded core integration surfaces. Environment, authorized package, certification, certificate, taxpayer/unit and connector evidence must be qualified separately.

Documentation evidence

The pinned integration sources identify the package and operational boundary. The operation/schema inventory retains the concrete route evidence.

Review status

This article establishes repository/contract boundaries and does not prove installed capability, production credentials, regulator acceptance, security completeness or a validated click-by-click workflow.

Pinned source evidence

Links require access to the private source repository.