Understanding the CPM data flow

CPM uses a subset of Peak quality and utilization measures within the module. Staging Tables, Data Import and Export assets, and scheduled jobs are used to maintain the CPM data.

The DSS admin calls for CPM data to be updated by starting a scheduled job. This scheduled job uses imports to populate the four CPM staging tables in the table library. Next, the system uses the four exports to create files, and the system sends the Peak Client Success Team an email notification that the job is complete and the files are ready for pickup.

The Peak Client Success Team processes the client data through DME, and creates updated clinical measure files. The files are then imported into Axiom Enterprise Decision Support using a scheduled job. The system sends an email notification to the DSS Admin after the job is successful, and the Clinical Measure tables are ready.

CPM infrastructure and assets

CPM is a feature within the Axiom Enterprise Decision Support and can be accessed through the following areas in the system:

CPM is maintained by users with the DSS Admin role.

  • DSS Folder > CPM Folder

    CPM Staging Tables

    • CPMencounterstaging
    • CPMchargesstaging
    • CPMprocedurestaging
    • CPMdiagnoisstaging

    CPM Clinical Measure Tables

    • ClinicalMeasure
    • ClinicalBenchmark
    • ClinicalPeerGroup
    • ClinicalMeasureData

    • Job Scheduler

    • Job 1
    • Job 2

    Imports = Imports Library > DSS > CPM

    • CPM Staging (four imports)
    • CPM Measures (four4 imports)

    Exports = Exports Library > DSS > CPM

    • CPM Staging (four exports)
    • CPM Date

    • Quality and Safety Indicator Analysis Dashboard