Opening catalogue record…
Loading its scope, linked MicroERPs and implementation progress.
ERP ATLASAPPNEURALFinanceP2Reference
Insurance Claims
Full nameHospital Insurance and Third-party Claim Coordination Micro ERP
Requests, supporting evidence, approval decisions and settlement need one claim record.
Application configurations3
Extension mappings6
LifecycleReference
About this erp
Purpose and scope
Requests, supporting evidence, approval decisions and settlement need one claim record.
Connected workflows
- Patient bill references
- claim documents
- provider decision tracking
- recorded settlements
- Source
- ERP_Full_Hierarchy_Catalogue.html
- Family
- Returns, claims and adjustments
- Family ID
- claims
- Configuration scope
- Industry operations
- Standalone scope
- Own customers, original orders or policies, claim types, reviewers. Run patient bill references, claim documents, provider decision tracking, recorded settlements. Maintain record history and role permissions.
- Core records
- Customers, original orders or policies, claim types, reviewers
- ERP connections
- Orders, records, inventory, finance
- Primary workflow
- Patient bill references → claim documents → provider decision tracking → recorded settlements
- Readiness
- Source-defined reference configuration; runtime unverified.
AI brief
What it is, when to use it, how to start
Written by Claude from this ERP's record. Check the details before you rely on them.
Connected catalog
Explore the composition
Follow each relationship to its full catalog record.
3 linked records
Application
Insurance Claims: Claim Desk
Full nameHospital Claim Desk App
Register requests, link original records and collect required evidence.
ApplicationInsurance Claims: Claimant
Full nameHospital Claimant App
Submit a claim or return request and view requested actions.
ApplicationInsurance Claims: Claim Approver
Full nameHospital Claim Approver App
Review evidence, authorize an adjustment and confirm settlement.