Keep up with latest product news
wire up real LLM inference engine
We have updated the project's README.md and key pages of the claimauditai-wiki to document production-grade hardening, security fallbacks, and the newly integrated Model Context Protocol (MCP) server.
claimaudit-iris container. It enables the AI chat assistant to call standardized local clinical tools to prevent LLM hallucinations:
lookup_cpt_code(code: str) -> str: Translates 5-digit CPT codes to official procedure descriptions.lookup_icd_code(code: str) -> str: Translates diagnosis codes, supporting prefix matches.validate_diagnosis_procedure(icd_code: str, cpt_code: str) -> str: Runs clinical compatibility audits._v1.pth/npz, _v2.pth/npz, _v3.pth/npz) for instant recovery.torch.manual_seed(42) before model instantiation to eliminate non-deterministic sequential loss fluctuations.flagged=False) when there are fewer than 5 historical claims instead of throwing errors.JWT_SECRET is missing.
^ClaimAuditSecurityError global and falls back to a persistent GUID rather than causing fatal startup exceptions.https://claimauditai.com/fhir/extension/tier-results JSON objects inside ClaimResponse instead of using brittle text substrings.ClaimAudit.Data.Queue) processing engine, which allows immediate 202 Accepted ingestion responses for clients while executing AI pipelines in background worker threads.Recent commits (b0ffe6d, 081bf4f, and feda00f) added 6 new architectural documents to the claimauditai-wiki and updated the README.md to establish complete alignment between the codebase and the documentation:
ChatHistory with reserved keyword escaping, background Queue, Cytoscape-compatible GraphStore, and Debug utilities).ClaimResponse resources.Welcome to the v2.1.0 Release of ClaimAuditAI. This release focuses on production-grade hardening, model drift protection, training determinism, and robust integrations with the Model Context Protocol (MCP) terminology server and structured FHIR extensions.
To prevent model degradation in production, we introduced a robust verification loop during the autoencoder retraining process:
autoencoder_model.pth), the candidate model is evaluated on the validation dataset. If the candidate loss represents a degradation of more than 15% compared to the baseline model's loss, the update is rejected, a warning is logged, and the previous model remains active._v1.pth/npz, _v2.pth/npz, _v3.pth/npz) for instant rollback capability.torch.manual_seed(42)) immediately before candidate model instantiation guarantees deterministic initialization, preventing false drift rejections in automated sequential test runners.GetJWTSecret() to not block application startup or throw a fatal exception if CLAIMAUDIT_ENV=production is set but the JWT_SECRET environment variable is missing.^ClaimAuditSecurityError global and falls back to a persistent GUID. This ensures the application remains functional for contest reviewers while keeping a clear audit trail of security configuration gaps.GetStats() to extract the structured https://claimauditai.com/fhir/extension/tier-results extension directly from the pended ClaimResponse resource.disposition text with deterministic JSON parsing of the flagged status for tier1, tier2, and tier3. This ensures the dashboard stats donut chart accurately counts flags regardless of formatting adjustments.lookup_cpt_code, lookup_icd_code, validate_clinical_edits) to the Chat Agent loop. When a user asks about a CPT/ICD code description in the UI Chat Assistant, the LLM issues a tool call to query the local terminology server, returning official definitions instead of generating hallucinations.$ pytest src/python/tests/
======================== 92 passed in 85.85s =========================
Welcome to the v2.0.0 Release of ClaimAuditAI. This release marks a major shift, transitioning the payment integrity engine from a sequential ReAct tool-calling loop into a type-safe, compiled Agentic Finite State Machine (FSM) powered by Pydantic Graph.
Additionally, this version incorporates advanced InterSystems IRIS for Health integrations, custom Model Context Protocol (MCP) terminology engines, and Explainable AI (XAI) evidence citation linkages.
We refactored the Python-based adjudication pipeline into a type-safe, compiled FSM (agent_graph.py):
AuditState): Explicitly type-checked execution context tracking input metadata, tier-specific findings, citations, and LLM synthesis results.BaseNode[AuditState, None, str] with StepContext validation:
ClaimIngestionNode: Ingests and sanitizes metadata.ClinicalAuditNode: Executes vector database clinical note alignment.AnomalyAuditNode: Calculates autoencoder reconstruction loss.NetworkAuditNode: Evaluates referral loops and address collisions on the provider graph.LLMSynthesisNode: Aggregates scores and builds the markdown report.End to save API tokens and reduce latency.ClaimAudit.AI.AgentWrapper%AI.Agent classes via class dictionary compilation. If present, it maps tools as %AI.Tool bindings under %AI.ToolSet to run natively within AI Hub. Otherwise, it falls back to execution via the Python-compiled Pydantic Graph FSM.@registry.register) that dynamically generates OpenAPI/JSON schemas using function inspection. Exposes 8 medical and diagnostic tools:
lookup_cpt_code / lookup_icd_code (resolves medical codes).validate_clinical_edits (verifies diagnosis-procedure combinations).run_nlp_audit / run_anomaly_audit / run_graph_audit (live tier executions).get_patient_history / get_provider_history (historical database lookups).FastMCP to expose terminology resolution services.Claim and ClaimResponse resources.DocumentReference ID for clinical notes, Practitioner NPIs for address collisions).ClaimId column to the ClaimProjections database table, populated it during ingestion, and stored array citations in the FHIR tier-results extension on ClaimResponse.tier_orchestrator.py with sequential processing to eliminate IRIS Embedded Python database context conflicts.SpecialtyCode to [0,1] prior to evaluation, preventing categorical outliers from skewing continuous Z-score distances.claimResponseId to ledger records, converting Claim IDs in the Override Ledger into navigation links back to resolved read-only detail views.tsc --noEmit exits with 0).Here is the release description for ClaimAuditAI v1.0.2, formatted for immediate use in GitHub Releases, community announcements, or project documentation:
This release introduces three key architectural enhancements: FHIR SQL Builder Integration, a dedicated Medical Terminology MCP Server, and Explainable AI (XAI) Citations to link adjudication findings directly back to their source clinical and administrative evidence.
Allows developers and administrators to bypass manual database projections in favor of platform-native relational maps for advanced analytics.
fhirsql/projections.json: Pre-configured JSON projection configuration for Claim and ClaimResponse resources. This file can be imported directly into the InterSystems FHIR SQL Builder Management Portal.ClaimAudit.FHIR.SQLBuilderHelper: A custom ObjectScript query helper that executes dynamic SQL queries against projected schemas, extracting CPT codes, ICD diagnoses, amounts, and dates with built-in schema fallbacks.A Model Context Protocol (MCP) server built with Python's FastMCP framework, enabling cognitive agents to perform standard clinical translations and diagnosis-procedure justification checks.
lookup_cpt_code(code): Resolves a 5-digit CPT code into its human-readable clinical procedure description.lookup_icd_code(code): Translates an ICD-10 diagnosis code into its standard clinical description.validate_codes(icd_code, cpt_code): Performs programmatic validation to ensure the diagnosis supports the billed procedure.Links threat signals back to specific, traceable FHIR resource identifiers in the adjudication trail, giving auditors exact references to support hold decisions.
DocumentReference/{id} identifier of the progress note matching the billed CPT code.Claim/{id} as evidence of statistical outlier loss.Practitioner/{npi} and Claim/{id} references for geodetic/temporal leaps or address collisions.ClaimId to the ClaimProjections table with a safe ALTER TABLE schema update fallback.tier-results extension array.mcp>=1.27.2 to [requirements.txt](file:///Users/mck/Desktop/claimauditai/requirements.txt).DocumentReferenceId in native vector search.ClaimId from projected edges and return conflicting NPIs and claims for address collisions.claim_id parameters and forward citations downstream.citations type interfaces in [claim.ts](file:///Users/mck/Desktop/claimauditai/ui/src/types/claim.ts).test_mcp_server.py suite).npx tsc --noEmit exited with 0).real_world_e2e_tests.py against the running docker containers to verify database seeding, autoencoder training, single-claim details fetching, and correct REST response mapping.

Release Notes: ClaimAuditAI v1.0.1
This release focuses on production-hardening the containerized deployment lifecycle, resolving startup database initialization errors, and fixing data seeding reliability issues reported during InterSystems Open Exchange verification.
Key Changes & Enhancements:
Build-Time FHIR Provisioning: Moved FHIR server installation (/fhir/r4) and recursive class compilation directly into the docker build phase (iris.script). This ensures all schema tables, vector indices, and custom classes are baked directly into the container image, resolving 404 endpoint errors and startup race conditions.
REST Output Stream Protection: Implemented a quiet mode (pQuiet parameter) in the database Setup() method. This suppresses terminal writes when database initialization is triggered from REST controllers, preventing HTTP response pollution and resolving client-side JSON parsing errors (Expecting value: line 1 column 1) during data seeding.
Programmatic Namespace Safety: Wrapped the sample data loader (LoadSampleData()) in a scoped in-memory namespace switch to INTEROP. This resolves the ServiceIdIdx registry lookup failure if the CLI seeding command is executed from a default namespace (e.g. USER).
Robust Container Start Fallbacks: Updated the runtime initialization script (init_iris.sh) to recursively compile all custom classes (including ClaimAudit.Data and ClaimAudit.FHIR) using LoadDir, ensuring correct compilation ordering when deploying with empty persistent volumes.
ZPM Package Alignment: Correctly registered ClaimAudit.Data.PKG in module.xml to track and compile the GraphStore class within ZPM.
Expanded Diagnostic Wiki: Added new troubleshooting guides to the project wiki detailing resolution steps for ServiceIdIdx failures, missing database tables, and REST output pollution.

Full Changelog: https://github.com/musketeers-br/TriageAide/compare/1.0.1...1.0.2

Full Changelog: https://github.com/musketeers-br/TriageAide/commits/1.0.1
A clinician dashboard with AI triage questions that automate pre-checkup intake, built on InterSystems IRIS for Health.
QuestionnaireResponse%Embedding.OpenAI + VECTOR_COSINE)Encounter, SNOMED-coded ServiceRequest, LOINC/SNOMED Observations, and a Communication alert on escalationdocker compose up β boots IRIS, the agent, and the UI, and self-seeds demo data

