Skip to main content
All tracking and reporting of communications relating to order submissions in CPOE is accomplished through the Tracking/Reporting tab in the administration interface. The Commure Pro tracking and reporting tools provide information about all data that is communicated within the CPOE application. You can also use these tools to obtain information about order data that is transmitted over an HL-7 interface between CPOE and your back-end system. Data that is exchanged between CPOE and the back-end system includes session data to report on the status of order submissions and back-end processing operations related to orders. The following statistics enable you to track data in the CPOE application. This includes data traveling within the CPOE application as well as data exchanged over the HL-7 interface between the CPOE application and the back-end server:
  • The total number of route submissions
  • The total number of invalid order submissions
  • The total number of order submission failures
  • The total number of route submissions, prior to and after back-end processing
  • The total number of CPOE order submissions, or the total number of admission “meds rec” submissions
  • The total number of route submissions queued for back-end processing
  • The total number of route submissions that are held until a specific condition is met
  • The total number of back-end processing failures and successes
  • The average back-end and server processing times
  • The maximum back-end and server processing times

​
Tracking Activity Specific to the CPOE Application

Tracking of much of the CPOE activity is accomplished from the Submission Status tab. To access this tab, click the Admin tab, followed by the Tracking/Reporting tab. By configuring the filters on the Search Criteria screen, you can filter the available data so that only activity relating to CPOE is included in the statistics reports. These filters enable you to conduct efficient searches by defining your search criteria as narrowly as necessary. To monitor activity that is specific to the CPOE application:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. From the Application drop-down menu, select CPOE.
  4. From the Submission Record Type drop-down menu, select Route Submissions. The Order Session Type field displays, enabling filtering of session type from the following choices:
    • All: Displays submission records from all order types (CPOE orders and Meds rec admission orders)
    • Order Entry: Displays submission records from CPOE orders only
    • Meds Rec - Admission: Displays submission records from med rec admission orders only
    • Meds Rec - Transfer: Displays submission records from med rec transfer orders only
    • Meds Rec - Discharge: Displays submission records from med rec discharge orders only
  5. Select the Order Entry option to display submission records from CPOE orders only.
  6. (optional) You can restrict your search to the following specific CPOE data:
    • Route Type: You can monitor all activity relating to a particular printer, file server, or interface.
    • Destination Group: You can monitor all activity destined for a particular grouping of Destinations of the same type.
    • Destination: You can monitor all activity destined for a specific Destination within your facility or institution.
  7. (Optional) You can use any of the following additional search filters to further refine your search:
    • Select Patient
    • Timeframe
    • Start Date and End Date
    • Submission ID
    • Session ID
    • Status
    • Department (available to level 2 and 3 users based on user permissions)
    • Server Processing Time (ms)
    • User (who entered the order) (available to level 2 and 3 users based on user permissions)
    • Location (the location of the patient at the time an order is submitted)
    • Back-end Processing Time (ms)
    • Maximum # of Results
    • Include Ignored Records For more information about any of these search filters, see the Commure Pro Administration Tools Guide.
  8. Click the Show Detailed Results button to view the status of all orders that have been assigned to a corresponding route submission. The Search Results screen uses a table to display the following information about each submission:
    • Submitted: The date and time when the order was submitted. This data displays as a link that you can click to view more information about a particular entry.
    • Device: If the submission was initiated from a handheld device, this column provides information about the type of device used. Clicking the associated link for a specific submission yields the Submission Record Details window, which provides additional details, including the Commure Pro application version, order session ID, specific build number, submission status, routing location (the location used to determine the Destination), and patient location (both the location at the time of order entry as well as the patient’s current location (determined at the time the screen is loaded).
    • Type: The type of submission. Submissions pertaining to the CPOE application use the Route Submissions type.
    • Status: The status of the order or route submission. This status can include any of the following submission statuses:
      • Sent: (Reserved for future use (by interface Destinations only)).
      • Submitted: The submission has been successfully created and parsed and is ready for processing.
      • Sending for Processing: The submission has been picked up from the queue and is undergoing preparations prior to being sent for processing.
      • In Processing: The submission is currently undergoing processing with no detection of errors.
      • Waiting n minutes before being reprocessed again: The submission is delayed for a configurable amount of time after problems were encountered with the initial processing attempt. When this time limit is reached, the submission will be sent for one or more processing attempts. You can configure both the re-processing interval and the maximum number of retries. For more information, consult with your Commure Pro representative.
      • Queued for Reprocessing: The initial processing attempt failed and the submission is awaiting subsequent processing attempt(s). This submission status applies to submissions routed to printers, email or file servers, but does not apply to submissions routed to interface Destinations (such as HL7 or scripter). Instead of fluctuating between queued and re-processing states, interface submissions remain in a queued state until they are picked up by the interface Destination.
      • Processing Failure: Indicates a processing (or re-processing) failure that cannot be sent for additional processing attempts. Process failures can result from configuration problems (such as a mis-configured Destination) or an internal system failure. Processing failures can also result when the maximum number of re-tries is reached without success.
      • Submission Parsing Failure: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Destination Unreachable Failure: Problems occurred when sending a specific submission to the specified Destination. When a single submission enters this status, all submissions routed to the same Destination are put on hold, and are assigned the submission status ‘Waiting Behind Destination Unreachable Failure’.
      • Waiting Behind Destination Unreachable Failure: Submissions are entered into this state when they are stuck behind a single submission that remains stuck in a state of ‘Destination Unreachable Failure’.
      • Submission Record Parsing Failure: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Sync Version Mismatches from concurrent account and patient modifications: Indicates that discrepancies were found between the data in the Commure Pro application and the back-end application, likely resulting from data synchronization issues.
      • Permissions have changed on the server since last sync: The specified user is not authorized to submit this order due to restrictions placed on the user, such as enforcement of co-signature rules or a change in authorization level.
      • Superseded by another Submission: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Completed with Warnings: Processing has been completed for this submission but non-critical errors were encountered during processing of the order.
      • Queued to Destination: The submission is queued at its configured Destination and is awaiting processing. Submissions routed to interface Destinations (such as HL7 or scripter) remain in this state until they are picked up by their designated interface Destination. In the case of other types of Destinations (printers, email, file servers), submissions remain in a queued state until they are processed or sent for re-processing.
      • Submission Locking Failure: Too much time elapsed between the original processing attempt and subsequent attempts to re-process the order submission.
      • ROUTING Delayed for processing due to dxml condition: The order submission is in a pending state, awaiting a specific condition to be met before it is sent to its configured Destination. You can create rules so that order submissions are withheld until one or more conditions (defined using DXML) are satisfied. For more information, contact your Commure Pro representative.
      • Submission too Old to route: Indicates that the submission has aged beyond the configured time limit and will be excluded from the submission records sent over the outbound interface. You can configure this threshold independently for order sessions with one or more STAT orders vs. those sessions that have no STAT orders. For more information, see Identifying Older Submissions to Exclude from the Outbound Interface. - o Verified: (Reserved for future use (by interface Destinations only)).
      • Ignorable Failure: Indicates the presence of errors that are not considered urgent and which are reported for informational purposes only. You can define specific conditions that warrant this error level, such as errors that are triggered by a test Destination, or errors that do not prevent order submissions from successfully being processed and sent to their Destination.
    • Patient: The name of the patient associated with the submission.
    • User Name: The name of the user who entered the order from which this submission was generated.
    • Submission ID: The unique code that identifies the submission. Submission IDs are used to identify submissions beyond the scope of the CPOE application. For example, submission IDs can be used to identify note submissions.
    • Order Session ID: The unique code that identifies the CPOE order submission. All order submissions are assigned an order session ID.
    • Additional Info: Identifies the Destination Group used by the route submission.
    • Failure Reason: Provides specific information about some types of processing failures.
    • Mobilizer: Indicates the specific mobilizer associated with the route activity.
    • Hostname: Indicates the specific host name associated with the route activity. For more information about any of these result categories, see the Commure Pro Administration Tools Guide.
  9. Click the Back to Criteria button to return to the Submission Status screen. For more information about elements on the Submission Status tab, see the Commure Pro Administration Tools Guide.

​
Tracking Activity Specific to the ePrescribing Application

Tracking ePrescribing activity is quite similar to monitoring in the CPOE application, mostly differing only in the selection of submission record types. Also, some additional information is included among the submission record details from ePrescribing activity, such as the Surescripts Provider Identifier (SPI) number(s) associated with the provider (or providers, if ePrescribing submission requires co-signature). To monitor activity that is specific to the ePrescribing application:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. From the Application drop-down menu, select CPOE.
  4. From the Submission Record Type drop-down menu, select either:
    • ERXRoutingSubmission — To view all ePrescribing routing submissions, including all order submissions sent to the pharmacy electronically and all order submissions sent to a printer Destination. Routing submissions events on the Submission Status tab are distinguished by whether they pertain to new prescriptions (NEWRX) or canceled prescriptions (CANCELRX).
    • PharmacyUpdateSubmission — To see submissions that are associated with updating pharmacy information. This type of submission is created whenever physicians update a patient’s default or preferred pharmacy in Commure Pro ePrescribing. These submissions identify each pharmacy (referenced by its NCPDP ID) and describe the type of update (adding, editing, or deleting the pharmacy).
  5. (Optional) You can use any of the following additional search filters to further refine your search:
    • Select Patient
    • Timeframe
    • Start Date and End Date
    • Submission ID
    • Session ID
    • Status
    • Department (available to level 2 and 3 users based on user permissions)
    • Server Processing Time (ms)
    • User (who entered the order) (available to level 2 and 3 users based on user permissions)
    • Location (the location of the patient at the time an order is submitted)
    • Back-end Processing Time (ms)
    • Maximum # of Results
    • Include Ignored Records For more information about any of these search filters, see the Commure Pro Administration Tools Guide.
  6. Click the Show Detailed Results button to view the status of all orders that have been assigned to a corresponding route submission. The Search Results screen uses a table to display the following information about each submission:
    • Submitted: The date and time when the order was submitted. This data displays as a link that you can click to view more specific details about the submission record, including the status history of the submission as it gets sent to and processed at its Destination. In the case of ePrescribing submissions, the Submission Record Details window displayed upon clicking this link also displays the Surescripts Provider Identifier (SPI) number(s) of any providers associated with the submission (including co-signers). You can also access the XML representation of the ePrescribing submission from this window, by clicking a link (‘Show ERX Message’) that displays in the Message column (under the Submission Record Changes section).
  • Device: (currently not used by the ePrescribing application).
    • Type: The type of submission. Submissions pertaining to ePrescribing use either a submission type of ERXRoutingSubmission or PharmacyUpdateSubmission.
    • Status: The status of the order or route submission. This status can include any of the following submission statuses:
      • Sent: (Reserved for future use (by interface Destinations only)).
      • Submitted: The submission has been successfully created and parsed and is ready for processing.
      • Sending for Processing: The submission has been picked up from the queue and is undergoing preparations prior to being sent for processing.
      • In Processing: The submission is currently undergoing processing with no detection of errors.
      • Waiting n minutes before being reprocessed again: The submission is delayed for a configurable amount of time after problems were encountered with the initial processing attempt. When this time limit is reached, the submission will be sent for one or more processing attempts. You can configure both the re-processing interval and the maximum number of retries. For more information, consult with your Commure Pro representative.
      • Queued for Reprocessing: The initial processing attempt failed and the submission is awaiting subsequent processing attempt(s). This submission status applies to submissions routed to printers, email or file servers, but does not apply to submissions routed to interface Destinations (such as HL7 or scripter). Instead of fluctuating between queued and re-processing states, interface submissions remain in a queued state until they are picked up by the interface Destination.
      • Processing Failure: Indicates a processing (or re-processing) failure that cannot be sent for additional processing attempts. Process failures can result from configuration problems (such as a mis-configured Destination) or an internal system failure. Processing failures can also result when the maximum number of re-tries is reached without success.
      • Submission Parsing Failure: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Destination Unreachable Failure: Problems occurred when sending a specific submission to the specified Destination. When a single submission enters this status, all submissions routed to the same Destination are put on hold, and are assigned the submission status ‘Waiting Behind Destination Unreachable Failure’.
      • Waiting Behind Destination Unreachable Failure: Submissions are entered into this state when they are stuck behind a single submission that remains stuck in a state of ‘Destination Unreachable Failure’.
      • Submission Record Parsing Failure: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Sync Version Mismatches from concurrent account and patient modifications: Indicates that discrepancies were found between the data in the Commure Pro application and the back-end application, likely resulting from data synchronization issues.
      • Permissions have changed on the server since last sync: The specified user is not authorized to submit this order due to restrictions placed on the user, such as enforcement of co-signature rules or a change in authorization level.
      • Superseded by another Submission: This status is used to report on submissions from mobile devices only. See the Commure Pro Administration Tools User’s Guide for more information.
      • Completed with Warnings: Processing has been completed for this submission but non-critical errors were encountered during processing of the order.
      • Queued to Destination: The submission is queued at its configured Destination and is awaiting processing. Submissions routed to interface Destinations (such as HL7 or scripter) remain in this state until they are picked up by their designated interface Destination. In the case of other types of Destinations (printers, email, file servers), submissions remain in a queued state until they are processed or sent for re-processing.
      • Submission Locking Failure: Too much time elapsed between the original processing attempt and subsequent attempts to re-process the order submission.
      • ROUTING Delayed for processing due to dxml condition: The order submission is in a pending state, awaiting a specific condition to be met before it is sent to its configured Destination. You can create rules so that order submissions are withheld until one or more conditions (defined using DXML) are satisfied. For more information, contact your Commure Pro representative.
      • Submission too Old to route: Indicates that the submission has aged beyond the configured time limit and will be excluded from the submission records sent over the outbound interface. You can configure this threshold independently for order sessions with one or more STAT orders vs. those sessions that have no STAT orders. For more information, see Identifying Older Submissions to Exclude from the Outbound Interface. - o Verified: (Reserved for future use (by interface Destinations only)).
      • Ignorable Failure: Indicates the presence of errors that are not considered urgent and which are reported for informational purposes only. You can define specific conditions that warrant this error level, such as errors that are triggered by a test Destination, or errors that do not prevent order submissions from successfully being processed and sent to their Destination.
    • Patient: The name of the patient associated with the submission.
    • User Name: The name of the user who entered the order from which this submission was generated.
    • Submission ID: The unique code that identifies the submission. Submission IDs are used to identify submissions beyond the scope of the CPOE application. For example, submission IDs can be used to identify note submissions.
    • Order Session ID: The unique code that identifies the CPOE order submission. All order submissions are assigned an order session ID.
    • Additional Info: Identifies the Destination Group used by the route submission.
    • Failure Reason: Provides specific information about some types of processing failures. In the case of route submissions sent over an outbound interface, if the interface component (such as the BSS scripter or RXM outbound bridge) includes a description of the failure reason in the web response, this data is reported here. In the case of ePrescribing submissions that are sent back from Surescripts withoug a failure reason, the default value “Failure Reason Unknown” is assigned to prevent the outbound bridge from exceeding the maximum retry threshold and failing. For more information about any of these result categories, see the Commure Pro Administration Tools Guide.
  1. Click the Back to Criteria button to return to the Submission Status screen. For more information about elements on the Submission Status tab, see the Commure Pro Administration Tools Guide.

​
Identifying Processing Failures Among Submissions

One of the more frequent tasks that you are likely to perform as part of your tracking and reporting strategy is to identify failures among your order submissions. This task is easily accomplished from the Submission Status tab, where you can use a few of the filters available from the Search Criteria screen to obtain a report of all such processing failures. To identify all processing failures among your order submissions:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. From the Application drop-down menu, select CPOE.
  4. From the Status drop-down menu, select Processing Failure.
  5. From the Submission Record Type drop-down menu, select Route Submissions.
  6. (optional) You can further restrict the list of processing failures returned by selecting any of the following additional filters:
    • Route Type: You can select processing failures relating to a particular printer, file server, or interface.
    • Destination Group: You can select processing failures relating to a particular grouping or cluster of related Destinations.
    • Destination: You can select processing failures relating to a specific Destination within your facility or institution.
  7. (Optional) If you want to control the number of processing failures that display on a page, use the Maximum # of Results setting. The default number of failures displayed is 50.
  8. Click the Show Detailed Results button. The Search Results screen displays the list of processing failures.

​
Sending Submissions to the Queue for Re-processing

When you monitor the CPOE application to identify processing failures among your institution or facility’s order submissions, you can re-submit each failed submission so that it is queued to be re-processed during the next processing run. An administrator’s ability to re-submit submissions is determined by the Submission Record Management user preference which, when set to Yes, displays the Queue for Reprocessing button on the Search Results pane, and also on the Submission Record Details window that displays when you select a specific result from the Search Results pane. Note that some successful submissions can also be flagged for re-processing. Authorized administrators can select one or more submissions that were already successfully sent to a (printer) Destination and send these submissions back to the queue to be processed a second time. This functionality enables administrators to re-send submissions when they need to obtain a second copy of the order session, such as when orders are routed to a printer that is low on toner. To send submissions back to the queue to be re-processed:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. From the Application drop-down menu, select CPOE.
  4. From the Status drop-down menu, select Processing Failure.
  5. Click the Show Detailed Results button.
  6. From the Search Results screen, select the row associated with the failure that you want to send for re-processing.
  7. Click the Queue for Reprocessing button. A confirmation box indicates that the selected record was sent to be re-processed.
  8. Click OK.

​
Re-Processing of Submissions with Controlled Medications

There are certain limitations pertaining specifically to ePrescribing submissions that must be enforced to ensure compliance with DEA requirements. Once providers sign and submit prescriptions to a pharmacy electronically, all successful submissions are considered “final” and administrators are prevented from queuing any such submissions for re-processing (the Queue for re-processing button is disabled). In cases where controlled medication prescriptions that initially fail electronically are then routed to a printer Destination instead, the following note is included on the printed prescription to indicate that the initial attempt failed: “Prescription was sent electronically to [pharmacy name] on [date / time] but submission failed” In the case of controlled medication prescriptions routed to a printer Destination, such submissions can be queued for re-processing after initially succeeding, but the following note is included on the printed prescription of any subsequent instances of re-processing: “This prescription is a copy to be used for informational purposes only.” However, any modifications made to such orders after they are initially printed prevent any changes to the Destination, which must remain configured to printer Destination type. This is to prevent duplicate prescriptions that might result from providers (re-)submitting controlled medication orders electronically that they had already sent to a printer.

​
Excluding Selected Submissions from Detailed Results

When you monitor the activity of your CPOE application to identify processing failures, the report that is generated (by clicking the Show Detailed Results button) may produce a significant amount of entries related to multiple areas. If you are tracking your system to identify failures relating to a particular area or set of functionality, you can exclude one or more entries from your report on an individual basis. An “Ignore” column displays on the right-hand side of the Submission Status report. By selecting check boxes associated with specific submissions belonging to any submission status, you can selectively exclude specific records from your failure report. To exclude one or more submissions from your failure report:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. From the Application drop-down menu, select CPOE.
  4. From the Status drop-down menu, select the submission status to use to further filter your search results.
  5. Click the Show Detailed Results button.
  6. For each processing failure that you want to exclude from your report, enable the associated check box in the Ignored column. Note that when you mark failures of meaningful submissions as ignored, the status of these submissions changes from “submitted” to “ordered”.
  7. Click the Back to Criteria button. Each time that you generate a report to display processing failures, all of the entries that you selected will be excluded from the report.
If at any time you want these entries to display among the others, you can enable the Include Ignored Records check box that displays on the Submission Status tab on the Search Criteria screen, to the right of the Reset Criteria button.

​
Exempting Records from System Cleanup

There may be records that you want to remain on your system for the purposes of tracking and reporting certain data that you identify as high-priority data. For example, you may want to retain one or more individual route submissions whenever automated or manual cleanup operations are performed on your system. In such cases, you can configure your system so that any specified records are excluded from all cleanup operations that are run on your system.
The option to exempt records from system cleanup is selectively granted to administrators using the Submission Record Management setting. Administrators configure this setting as part of configuration of user permissions. For more information, see the Commure Pro Administration Tools User’s Guide.
To exempt a specific record from system cleanup:
  1. Click the Admin tab, followed by the Tracking/Reporting tab.
  2. Click the Submission Status tab.
  3. Use the criteria to define the record(s) that you want to exempt from cleanup.
  4. Click the Show Detailed Results button.
  5. From the list of entries that displays, click the link that is associated with the record to exclude. Each link displays in the left-most (Submitted) column belonging to the table that displays the record details.
  6. From the Submission Record Details screen, check the Exclude From Purge check box. A confirmation dialog box displays.
  7. Click the OK button, followed by the Close button. This record will now remain on your system, exempt from all cleanup operations that are run on your system. This includes all device sessions, submission records, and server logs.
For more information about purge activity, including instructions for excluding all records of a particular type, see the Commure Pro Administration Tools User’s Guide.

​
Identifying Older Submissions to Exclude from the Outbound Interface

You can configure submissions that age beyond a configurable timeframe to be excluded from the submission records that are sent over the outbound interface. These records can be assigned the submission status “Exceeded interface timeframe” after a configurable number of minutes. Note that two configuration options let you configure this threshold differently when order sessions include one or more STAT orders vs. those sessions that have no STAT orders. For more information, contact your Commure Pro representative.

​
Generating a Report of Back-end Orders With No Corresponding CPOE Order

In some cases, there might not be any Order Definition in Commure Pro to correspond to a back-end order. You can create a report that lists all such orders that exist over a specified duration. Each back-end order meeting this criteria is listed in this (.csv) report, along with its associated NDC code. To generate a report of back-end orders with no corresponding CPOE orders:
  1. Click the Admin tab and then the Facility Group or CPOE tab.
In deployments where Facility Groups are not enabled, the Facility Group tab is replaced by the CPOE tab.
The CPOE Preferences page displays by default.
  1. If your institution uses multiple Facility Groups, select the Facility Group you want to configure from the Facility Group drop-down list.
  2. Click the Reports link.
  3. The Reports pane displays the list of available reports. Select the Missing NDC code report, and click Run.
  4. In the dialog box, enter the number of week’s worth of data you want the report to generate.
  5. Click Run the Report, and then confirm download of the report.
  6. When prompted, you can either view the report or save it to your local machine. The report displays all back-end orders that are found to have no corresponding orders in Commure Pro CPOE.

​
Generating a Report to Identify Inactive NDC Codes

You can generate a list of Formulary NDC codes to see which codes have undergone a status change, such as those made inactive in the drug database. This list identifies the inactive NDC codes, along with their associated CPOE Order Definition name. To generate a report identifying all formulary NDCs that are marked as inactive in the drug database:
  1. Click the Admin tab and then the Facility Group or CPOE tab.
In deployments where Facility Groups are not enabled, the Facility Group tab is replaced by the CPOE tab.
The CPOE Preferences page displays by default.
  1. If your institution uses multiple Facility Groups, select the Facility Group you want to configure from the Facility Group drop-down list.
  2. Click the Reports link. The Reports pane displays the list of available reports.
  3. Select the Inactive Formulary NDC Report option, and click Run.
  4. When prompted, begin the download process and select whether to open or save the (.csv) file. The report displays all formulary NDC codes that are currently marked as inactive in the drug database.

​
Generating Reports for Managing Formulary Medications

You can generate several reports to assist you in the process of managing your formulary medications so that you can reconcile the medications that are on your institution’s formulary with the medications from your drug database. These reports help you to manually validate that every formulary medication is associated with the appropriate back-end mnemonic.
  • Duplicate Mnemonics — This report provides a list of Order Definitions where the same mnemonic is associated with more than one Order Definition, or the same back-end mnemonic is associated with more than one NDC code within the same Order Definition.
  • Missing Mnemonics — This report provides a list of all Order Definitions that are on formulary, but which do not have any back-end mnemonic. Note that Order Definitions are omitted from this report when they have one or more NDCs on formulary with an assigned mnemonic value.
  • Manual Order Strings Not On Formulary — This report provides a list of all Order Definitions that are not on formulary, but which have at least one manually-created order string. Once you complete this clean-up process, your Commure Pro representative can run a SQL statement to remove the formulary “Yes” flag for all NDC codes that do not have a mnemonic.
To generate a report identifying all formulary NDCs that are marked as inactive in the drug database:
  1. Click the Admin tab and then the Facility Group or CPOE tab.
    In deployments where Facility Groups are not enabled, the Facility Group tab is replaced by the CPOE tab.
  2. Click the Reports link.
  3. Select one of the following reports (described above):
    • Duplicate mnemonics
    • Missing Mnemonics
    • Manual Order Strings Not On Formulary
  4. Click Run. A message informs you that download of the report is in progress.
  5. Click OK.
  6. When prompted, you can open your report or save it to a specified location.

​
Determining a Facility Group’s Drug Database Version in Use

You can obtain the current version of the drug database that is in use on a per-Facility Group basis. This support is added in the form of updates that have been made to the CPOE database schema. For more information, contact your Commure Pro representative.

​
Monitoring SOLR Search Activity

Authorized administrators can do basic monitoring of the SOLR search engine from the SOLR Search Engine section of the Self Test screen (Admin > System Management > Self Test). This section displays details about the SOLR Search and SOLR Master Indexer services, including the URL and availability of each service. Additional details are also provided (under the Info column) indicating whether the SOLR indexer was run and, if so, the date and time of the most recent activity. Errors and warnings also display under this column to indicate activity requiring action (red font) or is informational only (yellow font).

​
Monitoring the Process of Loading of Formulary Medications

Support is provided for monitoring the process of loading medications from your facility’s formulary list. Any medications that are rejected during the loading process are written to a file, which includes the following information for each medication that was rejected during the loading process:
  • Date that the formulary medication was rejected
  • Facility to which the formulary medication belongs
  • Facility name Any errors are written to a file once daily, which is stored at a configurable location. Each rejected NDC is written to a file at the specified location with the message “Cannot update orderDefinition to formulary because ndc sent - [NDC #] - could not be found for facility group: [DefaultFacilityGroup]”.
For more information, contact your Commure Pro representative.

​
Statistics for Tracking and Reporting

The following statistics are used to report on several aspects of CPOE application behavior. These statistics, which display on the lower-half of the Submission Status tab, are available to level 1 administrators only. Each statistic is displayed as a link that administrators can click to access additional detail about the associated activity.
  • Total Submission Records: The total number of records that have been submitted in the Commure Pro CPOE application. This total includes submission failures as well as successful submissions.
  • Submission Parsing Failures: Indicates the number of failures that occurred during parsing of both order and routing submissions.
  • Submission Record Parsing Failures: Indicates the number of failures that occurred during parsing of routing submission records.
  • Validated - No Further Processing Required: Indicates how many submission records have been successfully processed by Commure Pro CPOE.
  • Validated for Back-end Processing: Indicates how many submission records have been successfully processed by Commure Pro CPOE in preparation for additional processing by the back-end system.
  • Queued for Processing: Indicates how many submission records currently exist in the queue awaiting processing.
  • Queued for Reprocessing: Indicates how many submission records currently exist in the queue awaiting reprocessing. These are records that have a status of Processing Failure.
  • Processing Failures: Indicates how many failures occurred during processing of submission records.
  • Successfully Processed: Indicates the total number of submission records that have been processed by both Commure Pro CPOE and the back-end system.
  • Average Back-end Processing Time: The average amount of time that it took for an order submission to travel round trip from the CPOE application to the back-end system and back to the CPOE application.
  • Max Back-end Processing Time: The maximum amount of time that the back-end system took to process session requests before returning a response to the CPOE application.
  • Average Server Processing Time: The average amount of time that the CPOE application took to process session requests.
  • Max Server Processing Time: The maximum amount of time that the CPOE application took to process session requests.

​
Additional Monitoring of Printer Destinations

Additional monitoring is available that provides more detailed reporting for identifying and monitoring printers that have been configured as Destinations. This support is provided in the form of a JSP file that provides the following information about each printer that you configure as a specific Route Destination:
  • Printer address
  • Information indicating whether the printer is available
  • Name of the printer
  • Facility Group to which the printer belongs
  • The number of submissions that have been sent to the printer
  • The earliest submission ID that was sent to the printer For more information, contact your Commure Pro support representative.

​
Reporting on Promoting Interoperability Compliance

Access to Promoting Interoperability reporting is provided from the PI Report sub-tab under the Admin > Tracking/Reporting tab. From this PI Report sub-tab, you can select a facility and then generate compliance reports (both stage 2 and stage 3 measures) for a specified reporting period. You can create reports to display Promoting Interoperability compliance data for the CPOE, Medication Reconciliation, and ePrescribing applications. For more information about creating these and other Promoting Interoperability reports, see the Commure Pro Administration Tools User’s Guide.