Performance Monitoring Workflow

The PMW profile page is being edited below. Some of the text is from a template. This note will be removed when the page is complete.

The Performance Monitoring Workflow (PMW) profile provides guidance on sharing proficiency testing results and other laboratory performance monitoring data with external performance evaluation organizations.

Summary

Most of the assay results produced by clinical laboratories are for the purpose of patient care. However, there are results that are produced for assessment of laboratory performance rather than clinical care, for example test validation or performance monitoring in comparison with other laboratories. These results may be derived from analysis of repurposed patient samples, or they may use locally-concocted or purchased samples. Existing IHE Pathology and Laboratory Medicine profiles are designed to communicate patient results for clinical care. Results produced for performance assessment are often handled manually outside of the clinical workflow. This difference in workflow is resource-intensive and error prone, and it decreases the utility of performance monitoring in assessing all elements of the clinical workflow.

The PMW Profile defines workflow and content for messages that communicate orders and results for tests that are carried out to evaluate the technical performance of laboratories. The initial use case is proficiency testing (testing and reporting results on external specimens, with results compared for consistency between laboratories). The PMW profile automates ordering and result reporting of performance monitoring testing in a manner resembling clinical testing and reporting so that the workflow and analyses are streamlined and less error-prone than manual methods, and more closely reflect clinical specimen testing. The scope of the PMW includes communication of orders for testing of performance monitoring specimens and return of results for those specimens. Other activities related to performance monitoring, such as registration into performance monitoring programs and selection of a menu of tests for monitoring, are out of scope for the profile and are supported by the business systems of performance monitoring providers.

Performance monitoring overview. Laboratories subscribe to a performance monitoring program and receive specimens for testing (top, gray). After testing the results are analyzed and a performance report is provided (bottom, gray). The PMW profile defines messages used to order testing and report individual test results (middle, black and in dotted box).

Benefits

Many laboratories carry out performance monitoring using manual methods or non-standard online portals. These activities include local entry of orders for performance monitoring tests and reporting of the test results for aggregation, analysis, and comparison with other laboratories. This manual workflow is time-consuming, error-prone, and does not match the workflow for handling patient specimens. The PMW profile defines standard orders and results messages for performance monitoring specimens, which can be used in a laboratory workflow similar to outreach patient specimens. This saves time and reduces irrelevant error, and it creates the possibility of extending proficiency testing to include a meaningful evaluation of data returned by the laboratory to the proficiency testing provider, including the accuracy of test and result coding, and the accuracy of transfer of data elements from orders to results messages.

Details

The PMW profile supports test orders and results that have the primary purpose of monitoring the quality of laboratory operations rather than clinical care, using a standard reference laboratory interface as defined by the Interlaboratory Workflow (ILW) profile. The specimens used for performance monitoring may be repurposed patient material, but they also may be artificially produced and include human components, animal components, and/or chemical reagents. Performance monitoring specimens may be purchased from a vendor that offers a performance monitoring program including analysis of results and reports that include comparison to accepted performance metrics or other laboratories. For some rare tests and laboratory-developed tests, groups of laboratories may share specimens and analyze comparative results themselves.

The scope of the PMW profile includes only order communication and individual specimen result reporting for performance monitoring specimens. Other communications between the provider of a performance monitoring program and a participating laboratory, such as registration into a performance monitoring program, mapping a laboratory’s local test codes to the provider’s catalog of supported tests, and providing aggregated performance results are outside the scope of the profile and would normally be handled by the program provider’s business process systems such as an online portal or paper forms.

The PMW profile extends existing PaLM TF profile messages for performance monitoring. Communications between the performance monitoring program provider and participating laboratories use a reference laboratory interface and Interlaboratory Workflow (ILW) profile messages with the provider acting as a “local” laboratory (issuing orders and receiving results) and the participating laboratories acting as “subcontracting” laboratories (receiving orders and returning results). The internal communication of orders and results in participating laboratories use messages from the LTW and LAW profiles. The corresponding actor names in the PMW profile reflect those in the ILW, LTW, and LAW profiles.

Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

• PACS systems may store, manage, and/or display Evidence Documents.
• Display systems may query, retrieve and display Evidence Documents.
• Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• DICOM
• HL7
• ...

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>

Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>

• Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
• Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
• Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
• Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
• Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.

Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >

This page is based on the Profile Overview Template <Delete this Category Templates line since your Profile page is no longer a template.>