The Challenge
Outpatient surgical centres carry a business workload alongside the clinical one — pre-arrival workflow, prior authorisation, insurance verification, medical necessity checking, financial assistance screening, appeals and release of information. Each depends on configuration that was not centrally managed across facility types.
Standalone, member and enterprise sites configured separately.
Plan and medical codes maintained outside one system.
User access defined per application, not centrally.
No structured phases for routing administrative work.
Approach & Solution
smartData built the portal on .NET and Angular as a multi-tenant SaaS administration layer. Administrators define facilities as standalone, member or enterprise, then attach the medical offices, payor offices, physicians and contacts belonging to each, with database access provisioned per facility according to what that site needs to manage.
Insurance code sets — plan codes, medical codes and activity codes — are maintained centrally rather than per site. User groups such as administrators, audit managers and collection callers carry their own permissions, and LDAP mode provisions accounts against network identity through active directory.
Key Features
Standalone, member and enterprise types in one model.
Plan, medical and activity codes maintained once.
Access assigned by role across applications and modules.
Accounts created against active directory network identity.
Product Showcase
Final Outcome
Facility structure, office relationships, insurance code sets, user permissions and work queues are defined once and applied across the network, so adding a site becomes a configuration task rather than a rebuild.
