Description
n8n-nodes-trizetto
> [Velocity BPA Licensing Notice]
>
> This n8n node is licensed under the Business Source License 1.1 (BSL 1.1).
>
> Use of this node by for-profit organizations in production environments requires a commercial license from Velocity BPA.
>
> For licensing information, visit https://velobpa.com/licensing or contact licensing@velobpa.com.
A comprehensive n8n community node package for TriZetto healthcare clearinghouse integration. Provides complete EDI transaction support (270/271, 276/277, 837, 835), real-time eligibility verification, claims management, remittance processing, prior authorization workflows, and revenue cycle management capabilities.
!n8n
!TypeScript
!License
!Healthcare
!HIPAA
Features
- Eligibility Verification (270/271) – Real-time and batch eligibility checks with comprehensive benefits parsing
- Claim Submission (837) – Professional, Institutional, and Dental claim submission with validation
- Claim Status (276/277) – Track claim status with detailed event history
- Remittance Processing (835) – Parse ERA files, reconcile payments, extract adjustment codes
- Prior Authorization – Submit, track, and manage prior auth requests
- Provider Management – NPI validation, network status, credentialing
- Payer Directory – Payer rules, EDI requirements, connectivity testing
- Code Validation – ICD-10, CPT, HCPCS, revenue code validation with CCI edits
- Batch Processing – Submit and monitor batch file processing
- EDI Operations – Parse/generate X12 transactions, 997/999 acknowledgments
- Real-Time Transactions – Synchronous eligibility, claim status, cost estimates
- CareAdvance RCM – Work queues, task management, productivity tracking
- Reports & Analytics – A/R reports, denial analytics, clean claim rates
- SFTP Integration – File upload/download for batch processing
- Webhook Support – Event-driven notifications for claims, payments, authorizations
Installation
Community Nodes (Recommended)
1. Open n8n
2. Go to Settings > Community Nodes
3. Click Install a community node
4. Enter n8n-nodes-trizetto
5. Click Install
Manual Installation
Navigate to your n8n installation
cd ~/.n8nInstall the package
npm install n8n-nodes-trizettoRestart n8n
Development Installation
Clone or extract the repository
git clone https://github.com/Velocity-BPA/n8n-nodes-trizetto.git
cd n8n-nodes-trizettoInstall dependencies
npm installBuild the project
npm run buildLink to n8n custom nodes
mkdir -p ~/.n8n/custom
ln -s $(pwd) ~/.n8n/custom/n8n-nodes-trizettoRestart n8n
n8n start
Credentials Setup
TriZetto API Credentials
| Field | Description | Required |
|——-|————-|———-|
| Environment | Production, Test/Staging, or Custom | Yes |
| Username | TriZetto API username | Yes |
| Password | TriZetto API password | Yes |
| Client ID | OAuth client ID | Yes |
| Client Secret | OAuth client secret | Yes |
| Submitter ID | EDI submitter identifier | Yes |
| Site ID | Site identifier (multi-site setups) | No |
| Vendor ID | Vendor identifier | No |
TriZetto Gateway Credentials
| Field | Description | Required |
|——-|————-|———-|
| Gateway URL | TriZetto Gateway endpoint | Yes |
| Certificate | mTLS client certificate (PEM) | Yes |
| Private Key | mTLS private key (PEM) | Yes |
| Partner ID | Trading partner identifier | Yes |
TriZetto SFTP Credentials
| Field | Description | Required |
|——-|————-|———-|
| Host | SFTP server hostname | Yes |
| Port | SFTP port (default: 22) | Yes |
| Username | SFTP username | Yes |
| Authentication | Password or SSH Key | Yes |
| Directory Path | Base directory path | No |
Resources & Operations
1. Eligibility (270/271)
2. Claim Submission (837)
3. Claim Status (276/277)
4. Remittance (835)
5. Prior Authorization
6. Attachment
7. Provider
8. Payer
9. Patient
10. Facility
11. Code Validation
12. Batch
13. EDI
14. Real-Time
15. CareAdvance (RCM)
16. Report
17. Analytics
18. Clearinghouse
19. Enrollment
20. SFTP
21. Webhook
22. Utility
Trigger Node
The TriZetto Trigger node monitors for real-time events:
Eligibility Events
Claim Events
Remittance Events
Prior Auth Events
Batch Events
EDI Events
Task Events
Report Events
Usage Examples
Eligibility Verification
// Real-time eligibility check
{
"resource": "eligibility",
"operation": "checkEligibility",
"payerId": "BCBS001",
"memberId": "ABC123456789",
"firstName": "John",
"lastName": "Smith",
"dateOfBirth": "1980-01-15",
"serviceType": "30" // Health benefit plan coverage
}
Claim Submission
// Submit professional claim (837P)
{
"resource": "claimSubmission",
"operation": "submitProfessional",
"payerId": "AETNA01",
"patientInfo": {
"memberId": "XYZ789012",
"firstName": "Jane",
"lastName": "Doe",
"dateOfBirth": "1975-06-20"
},
"providerNpi": "1234567893",
"diagnosisCodes": ["J06.9", "R05.9"],
"serviceLines": [
{
"cptCode": "99213",
"modifiers": ["25"],
"chargeAmount": 150.00,
"units": 1,
"serviceDate": "2024-01-15",
"placeOfService": "11"
}
]
}
Remittance Processing
// Parse 835 ERA file
{
"resource": "remittance",
"operation": "parse835",
"ediContent": "ISA00...(835 content)...IEA1000000001~"
}// Get payment details
{
"resource": "remittance",
"operation": "getPaymentDetails",
"remittanceId": "ERA20240115001"
}
Prior Authorization
// Submit prior auth request
{
"resource": "priorAuth",
"operation": "submit",
"payerId": "UHC001",
"memberId": "MEM123456",
"providerNpi": "1234567893",
"serviceType": "3", // Consultation
"procedureCode": "27447",
"diagnosis": ["M17.11"],
"requestedUnits": 1,
"clinicalInfo": "Patient requires knee replacement due to severe osteoarthritis"
}
Code Validation
// Validate ICD-10 code
{
"resource": "codeValidation",
"operation": "validateIcd10",
"code": "M17.11"
}// Check CCI edits
{
"resource": "codeValidation",
"operation": "checkCci",
"primaryCode": "99213",
"secondaryCode": "99214"
}
Batch Processing
// Submit batch file
{
"resource": "batch",
"operation": "submit",
"fileType": "837P",
"content": "(batch file content)"
}// Check batch status
{
"resource": "batch",
"operation": "getStatus",
"batchId": "BATCH20240115001"
}
TriZetto Concepts
Gateway
The TriZetto Gateway is the central hub for EDI transactions, routing claims and eligibility requests to appropriate payers.
CareAdvance
Revenue Cycle Management (RCM) platform for work queue management, task assignment, and productivity tracking.
Clearinghouse
EDI intermediary that validates, translates, and routes healthcare transactions between providers and payers.
Trading Partner
A payer connection established through enrollment, defining EDI requirements and routing rules.
X12 Transactions
CARC/RARC Codes
Error Handling
The node provides detailed error information:
{
"error": {
"code": "INVALID_NPI",
"message": "NPI checksum validation failed",
"details": {
"npi": "1234567890",
"expectedcheckdigit": "3",
"actualcheckdigit": "0"
}
}
}
Common Error Codes
| Code | Description |
|——|————-|
| AUTH_FAILED | Authentication failed |
| INVALID_NPI | Invalid NPI format or checksum |
| PAYERNOTFOUND | Payer ID not found |
| CLAIMVALIDATIONERROR | Claim failed validation |
| EDIPARSEERROR | EDI parsing error |
| TIMEOUT | Request timeout |
| RATE_LIMIT | Rate limit exceeded |
Security Best Practices
1. PHI Protection – Never log or expose PHI in clear text
2. Credential Security – Use n8n’s credential store
3. TLS/mTLS – All connections use TLS; Gateway uses mTLS
4. Audit Logging – All transactions are logged for HIPAA compliance
5. Access Control – Implement proper user access controls
6. Data Minimization – Only request necessary patient data
Development
Install dependencies
npm installBuild the project
npm run buildRun tests
npm testRun tests with coverage
npm run test:coverageLint code
npm run lintFix linting issues
npm run lint:fixWatch mode for development
npm run dev
Author
Velocity BPA
Licensing
This n8n community node is licensed under the Business Source License 1.1.
Free Use
Permitted for personal, educational, research, and internal business use.
Commercial Use
Use of this node within any SaaS, PaaS, hosted platform, managed service, or paid automation offering requires a commercial license.
For licensing inquiries: licensing@velobpa.com
See LICENSE, FAQ.md”>LICENSINGFAQ.md for details.
Contributing
1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request