Technical reference for system architects evaluating CareIntegrity.AI for government-scale deployment. Covers data source connectivity, identity management, persistence, CI/CD, and multi-cloud infrastructure patterns.
CareIntegrity.AI is designed as a cloud-agnostic platform that integrates with existing government infrastructure. It can deploy on AWS, Azure, GCP, or on-premises -- connecting to any combination of data sources and identity providers.
| Compute | 4+ vCPU, 16GB RAM (min), 8+ vCPU recommended |
| Storage | 100GB SSD for application, scalable object storage for data |
| Network | VPC/VNet with private subnets, NAT gateway |
| Database | PostgreSQL 14+ or any supported RDBMS |
| Python | 3.9+ with scientific computing packages |
| Node.js | 18+ for frontend build |
CareIntegrity.AI connects to any data source that holds NDIS claims, provider registrations, participant records, or workforce data. No data migration required -- connect to existing systems.
Native Snowflake connector with warehouse management.
# snowflake connection SNOWFLAKE_ACCOUNT=org.au-east-1 SNOWFLAKE_WAREHOUSE=COMPUTE_WH SNOWFLAKE_DATABASE=NDIS_PROD SNOWFLAKE_SCHEMA=CLAIMS SNOWFLAKE_AUTH=keypair
Full AWS ecosystem integration.
Native Azure service integration.
Enterprise Oracle database connectivity.
# oracle connection ORACLE_DSN=ndis-claims.oraclecloud.com:1521/CLAIMS_PDB ORACLE_AUTH=wallet ORACLE_WALLET_DIR=/opt/oracle/wallet
Connect to any data source via standard protocols.
CareIntegrity.AI integrates with enterprise identity providers for single sign-on, role mapping, and centralised user lifecycle management. No separate user database required in production.
Primary integration path for Australian government.
# Azure AD SAML configuration SAML_ENTITY_ID=https://careintegrity.ai SAML_SSO_URL=https://login.microsoftonline.com/{tenant}/saml2 SAML_CERT=/etc/ssl/azure-ad-cert.pem ROLE_MAPPING= AzureAD_FraudTeam -> fraud_officer AzureAD_Investigators -> investigator AzureAD_Inspectors -> inspector AzureAD_Analysts -> analyst AzureAD_Admins -> admin
Compatible with any standards-based IdP.
| Capability | Implementation | Standard |
|---|---|---|
| Provisioning | SCIM 2.0 auto-provisioning from Azure AD / Okta | RFC 7643/7644 |
| Deprovisioning | Automatic disable on AD group removal | SCIM 2.0 |
| Role Sync | AD group membership mapped to app roles every 5 min | SAML Assertions |
| MFA | Delegated to IdP (Azure AD, Okta) -- not managed in-app | FIDO2 / TOTP |
| Session Management | JWT tokens with configurable TTL, revocation via IdP | RFC 7519 |
| Audit Trail | All auth events logged with user, IP, action, timestamp | ISO 27001 |
CareIntegrity.AI requires a persistence layer for application state, computed risk scores, audit logs, and investigation records. This is separate from the source data systems it reads from.
| Layer | Technology | Purpose |
|---|---|---|
| Application Cache | Redis / ElastiCache / Azure Cache | Graph computation results, embeddings, baselines |
| Session Store | Redis / DynamoDB / Table Storage | JWT session metadata, CSRF tokens |
| Message Queue | RabbitMQ / SQS / Azure Service Bus | Async claim processing, alert delivery |
| Search Index | Elasticsearch / OpenSearch | Full-text search across entities and claims |
# docker-compose.yml (production) services: api: image: careintegrity/api:latest replicas: 3 resources: 4 vCPU, 8GB RAM worker: image: careintegrity/worker:latest replicas: 2 resources: 8 vCPU, 16GB RAM (GPU optional) redis: image: redis:7-alpine postgres: image: postgres:16 volumes: persistent
| Metric | Target | Measurement |
|---|---|---|
| Availability | 99.9% uptime | Synthetic monitoring + health endpoints |
| Claim Processing | < 500ms per claim | P95 latency from ingestion to risk score |
| Alert Generation | < 5 min from anomaly | Time from data arrival to alert dispatch |
| API Response | < 200ms P95 | All REST endpoints under normal load |
| Recovery Time (RTO) | < 1 hour | Full system recovery from backup |
| Recovery Point (RPO) | < 15 minutes | Maximum data loss on failure |