Upload Audit
Import the JSON export produced by the local Python runner. Nothing here connects to CentralReach or a database — the browser only reads the summarized file you provide.
1 · Target organization
This is the seeded demo engagement. Create or select a client organization to publish a real audit.
2 · Provide the export
Drop the JSON file, browse, or paste the payload.
Drop audit-export.json here
Result sets or legacy Data Gatekeeper reports are both accepted.
Local runner
How the export you upload here is produced.
- Run the Python audit locally against the client's SQL Server insights database. Credentials stay on your machine as environment variables — never in this app.
- The script writes a summarized JSON export containing the result sets listed below. No PHI-level detail is required.
- Drop that JSON here, review the validation and preview, then import it.
Import contract
Recognized top-level result sets and accepted aliases.
- AuditSummary
- ModuleScores
- TierStats
- FieldStats
- TableStats
- Exceptions
- MissingColumns
- SchemaInventory
- AuditDefinitions
- AuditErrors
Dual-schema aliases are resolved automatically: LogicalTable ↔ SourceObject, and the older DW2-only Table / ActualTable names.
Legacy nested reports are read from result.overallScore, perModule, perTier, perTable, exceptions and missingColumns.
PythonEnvironment is dropped on import and never shown to clients.
3 · Validation
Errors block the import; warnings are informational.
No package validated yet.