Appearance
Enterprise Tier Capabilities
EDI Paisan Enterprise provides the infrastructure healthcare organizations need to manage EDI processing at scale — with multi-location support, team access controls, comprehensive audit logging, and HIPAA Business Associate Agreement (BAA) coverage.
Who Is Enterprise For?
Enterprise is designed for:
- Healthcare organizations with multiple locations or departments
- Billing companies managing EDI for multiple clients
- Practices requiring HIPAA BAA coverage
- Teams needing centralized configuration and audit trails
Available Today
These Enterprise foundations are implemented and ready to use.
Organization & Location Management
Organize your EDI operations around your business structure.
Organizations
Each Enterprise account belongs to an organization:
Organization
└── Locations (1 or more)
└── Users (assigned to locations)
└── Settings (org-level or location-specific)
└── Control Number Sequences (per location)| Feature | Description |
|---|---|
| Organization Name | Your business name for the account |
| Multiple Locations | Create locations for offices, departments, or clients |
| Default Location | One location per org marked as default |
| Cascading Settings | Org-level settings apply to all locations unless overridden |
Locations
Locations represent physical offices, departments, or logical divisions:
| Capability | How It Works |
|---|---|
| Named Locations | Create and name locations (e.g., "Main Office", "Satellite Clinic") |
| Default Location | One location per organization is marked default |
| Location-Specific Settings | Override org settings at the location level |
| Scoped Control Numbers | Each location maintains independent control number sequences |
Settings Resolution
Settings follow a priority hierarchy:
- Location settings (highest priority)
- Organization settings
- User preferences (local storage)
- Code defaults (lowest priority)
This allows org-wide defaults with location-specific overrides.
User Roles & Access Control
Control what team members can do.
Roles
| Role | Permissions |
|---|---|
| org_admin | Full access to organization and location settings |
| user | Standard access, no organization management |
User-Location Assignment
Users are assigned to specific locations via the user_locations table:
- Users only see locations they're assigned to
- Location assignment controls which control number sequences they can access
- Org admins can manage user assignments
Current State: Role enforcement is implemented in the database. Web layer authorization is in active development.
Comprehensive Audit Logging
Track every action for compliance and troubleshooting.
What Gets Logged
| Action Category | Logged Events |
|---|---|
| File Operations | file:upload, file:upload:csv |
| Transformations | file:split, file:anonymize |
| EDI Exports | export:edi:chunk, export:edi:batch, export:edi:file, export:edi:redacted |
| Data Exports | export:json, export:csv:claims, export:csv:service-lines, export:csv:adjustments |
| Packages | export:audit-package |
| Settings | settings:save |
Log Entry Contents
Each audit log entry includes:
| Field | Description |
|---|---|
| Organization | Which organization performed the action |
| Location | Which location (optional) |
| User | Which user performed the action |
| Action Type | What was done |
| Metadata | Action-specific details (file name, size, hash, counts, etc.) |
| Timestamp | When it happened (immutable) |
Audit Metadata Examples
File Upload:
json
{
"fileName": "claims-batch-2025.edi",
"fileSize": 1048576,
"fileHash": "sha256:abc123...",
"transactionCount": 150,
"interchangeCount": 1,
"groupCount": 1,
"parseErrors": 0
}EDI Export:
json
{
"fileName": "split-chunk-001.edi",
"exportType": "chunk",
"controlNumbers": {
"isa": "000000001",
"gs": "1",
"st": "0001"
}
}Split Operation:
json
{
"splitMode": "claim",
"chunkCount": 47
}Audit Design Principles
- Append-only — Logs cannot be modified or deleted
- Preserved on delete — Even if users/locations are removed, audit history remains
- Organization-scoped — Users see only their organization's logs
- Best-effort — Audit failures never block user workflows
Production Control Numbers
Enterprise organizations get database-backed control number sequences:
| Feature | Description |
|---|---|
| Location-Scoped | Each location maintains independent ISA, GS, and ST sequences |
| Atomic Increment | Guaranteed unique numbers even with concurrent access |
| Persistent | Numbers persist across sessions and never repeat |
| Access Control | Users can only access sequences for their assigned locations |
Control number formats:
- ISA13 — 9-digit interchange control numbers
- GS06 — Functional group control numbers (1-9 digits)
- ST02 — Transaction set control numbers (4-9 digits)
Enterprise Roadmap
These capabilities are planned for Enterprise tier:
HIPAA Business Associate Agreement (BAA)
- Formal BAA for covered entities and business associates
- Required for healthcare organizations processing PHI
- Contact sales for BAA terms
Enhanced Team Management
- Invite team members by email
- Manage location assignments
- View user activity and audit trails
- Role assignment UI
Organization Admin Dashboard
- Overview of all locations
- Cross-location reporting
- Centralized settings management
- User access overview
AI-Powered Features
Enterprise-exclusive AI capabilities (planned):
- Automated claim validation suggestions
- Denial pattern analysis
- Payment prediction insights
Note: AI features are on the roadmap but not yet implemented.
Enterprise vs Pro
| Feature | Pro | Enterprise |
|---|---|---|
| All viewing capabilities | ✅ | ✅ |
| File downloads | ✅ | ✅ |
| Claim splitting | ✅ | ✅ |
| JSON/CSV/PDF exports | ✅ | ✅ |
| 837P generation | ✅ | ✅ |
| PHI anonymization | ✅ | ✅ |
| Production control numbers | ✅ | ✅ |
| Organizations | ❌ | ✅ |
| Multiple locations | ❌ | ✅ |
| Team user accounts | ❌ | ✅ |
| User roles (admin/user) | ❌ | ✅ |
| Audit logging | ❌ | ✅ |
| Location-scoped settings | ❌ | ✅ |
| HIPAA BAA | ❌ | ✅ |
Pricing
Custom pricing based on organization size and needs.
Factors that affect pricing:
- Number of users
- Number of locations
- Support level requirements
- BAA requirements
- AI feature access (when available)
Getting Started
- Contact us — Discuss your organization's needs
- Setup call — We'll help configure your organization structure
- Onboard users — Add team members and assign locations
- Sign BAA — If required for your compliance needs
- Go live — Start processing with full audit coverage
Summary
| ✅ Enterprise Includes |
|---|
| All Pro tier features |
| Organization management |
| Multiple locations |
| Team user accounts |
| User roles (org_admin, user) |
| Comprehensive audit logging |
| Location-scoped control numbers |
| Location-specific settings |
| HIPAA Business Associate Agreement |
| Priority support |
