Modules
The modules are the smallest element of the orchestration flow. These are the key pieces of functionality that organizes a key business capability. For example, benefit determination and third-party liability editing. The SCE provides a series of modules for specific out-of-the-box functionality that can be implemented. The modules provided by the SCE are all prefixed with an “S” identifier. Proprietary modules can also be created in the application for use in the SCE. The list of supplied modules is defined below. Each of these can be added as necessary to sequences to support orchestrations:
| Module | Identifier | Description |
| Claim adjustments | SAD | Claim adjustment processing and validation |
| Authorization processing | SAP | Authorization matching and adjudication |
| Claim business audits | SBA | Multiple claim or multi-line editing against historical claims or the current claim |
| Benefit determination | SBD | Matches the claim to an appropriate benefit |
| Claim business edits | SBE | Single claim or line business edits and core action codes |
| Benefit limit accumulator processing | SBL | Benefit limit calculations and accumulator processing |
| Coverages, accumulators and payments | SCA | Liability calculations based on benefit coverage and accumulator use. |
| COB reductions | SCB | Payment reductions based on claim submitted COB |
| ClaimsXten | SCX | SCE adaptor for ClaimsXten integration and processing |
| Episode processing | SEP | Episode of care identification and linking |
| Event code review | SER | Reviews event codes assigned on the claim for disposition, routing, and next steps |
| Finalization claim | SFC | Finalizes the claim and performs any remaining calculations |
| Finalization pricing | SFP | Finalizes the pricing on the claim and applies any COB adjustments |
| Incentives and surcharges | SIS | Applies any provider incentives or regulatory surcharges |
| Member eligibility | SME | Legacy member match and eligibility module. Performs member lookup, checks eligibility, and validates member related data |
| Member match | SMM | Matches the subscriber and/or patient on the claim to a member in the system |
| Policy selection and eligibility | SMP | Selects the appropriate policy for adjudication and validates member eligibility |
| Member validations | SMV | Validates patient and/or subscriber information on the claim against the matched member record |
| Process authorizations | SPA | Identifies if an authorization is required, matches, and processes the claim against an authorization |
| Provider eligibility | SPE | Matches the provider on the claim to the provider records and validates the provider details |
| Price calculation | SPC | Prices the lines on the claim based on the submitted codes |
| Process updates | SPU | Updates the claim and any supporting accumulators based on the final status |
| Random audits | SRA | Applies random audit event codes to the claim based on the audit configuration |
| Ratesheet selection | SRS | Selects the appropriate ratesheet ID based on the provider’s contract |
| Split claim | SSC | Applies the generic system configured automatic split claims logic. |
| Subscriber lock | SSL | Locks the claims from subscribers from processing in parallel to ensure accumulators are in sync |
| NetworX pricer | SSP | SCE adaptor to integrate to NetworX pricer |
| TPL edits | STP | Applies COB / TPL edits to the claim |
| Process validation edits | SVE | Performs key field validations to the claim |
| Winning price | SWP | Performs the winning price logic to select the appropriate price for adjudication |
New modules can be easily added to the list by selecting Add module. This then presents the Add module screen displaying the fields needed for the module. On selecting Submit, the new module is added to the list for subsequent addition to sequences. The fields are:
| Field | Description |
| Module * | Brief name or description of the module. This description is used by the application whenever there is a reference required for the module being processed, for example, Claim Audit. |
| Identifier * | Key assigned to this module. This identifier is stored for references to the module and is used as a lookup value for the module. It lets you modify the description without worrying about the reference to the module. Once you assign and use it, you should not modify it. This identifier is also used in assigning event codes |
| Process * | Collection rule associated with the module. Select the process from a drop-down list of available collections. This is the rule that the module executes. |
| Process type * | The type of module (Stub, Pega, and External) as it relates to the application |
| Measurement | Indicator that defines whether a measurement should be captured for this module. This allows specific module measurement if the global measurement is off in the system settings. |
| Audit | Indicator that defines whether any audit information should be reported for this module. This allows specific module audits to be logged if the global audit is off in the system settings. |
| Bypass | Indicator that defines whether to always bypass processing of this module. This is a useful feature during the testing of new modules |
| Module bypass table | Bypass table used for configuring information that can cause the module to be bypassed for specific claims |
| Module initialization | A collection rule that can be used to initialize any values pre-run or perform any pre-run logic. |
| Module finalization | A collection rule that can be used to finalize any values post-run or add any extensions to the module for client driven processing. |
| Module next step | A collection rule that is executed on completion of the module. |
Note: fields with an * Asterix are required.
Modifying & deleting modulesExisting modules can be modified by selecting the gear icon next to the module in the list. This will then open the Edit module screen enabling easy modification of the configuration.
Modules can be deleted by selecting the trash can icon next to the module in the list. Modules can only be deleted if they are not referenced in an existing sequence. A warning message is displayed when this occurs.
Previous topic Module, sequences, and orchestration Next topic Sequences