User Tools

Site Tools


capability_1

CA 1: Laboratory Test Request and Sample Receiving

This capability area addresses informatics capabilities related to the business processes associated with initial test sample request and receiving.

Guidance Statement

Purpose: Laboratories need efficient processes to receive a sample and its associated test requests. These processes play a critical role in a laboratory’s ability to report results proficiently. Laboratories can best perform these processes by exchanging data electronically, including test ordering and reporting (ETOR), and by leveraging systems such as laboratory information management systems (LIMS).

What: LIMS allow laboratories to take advantage of informatics capabilities and established data standards. Many LIMS accept multiple message types, create a flexible vocabulary model to utilize different standards, input and edit necessary data, and accommodate various transport mechanisms for receiving data. Other informatics efficiency measures for sample receiving and accessioning include the utilization of barcode scanning, radio frequency identification1, robotics2, and enterprise accessioning across multiple laboratory disciplines.

How: Informatics has allowed the modern laboratory to move from paperbased requisitions to electronic test orders. As data sharing abilities advance with technology, the ability to use standards, the flexibility to accommodate everchanging transport mechanisms, and the need to validate the content and ensure the security of electronic data exchange, are becoming critical to PHL success.

A laboratory that has the desired informatics capabilities to receive the sample and the associated request can:

  • Receive an electronic test request package message from a submitter and process the message. To process the workflow completely, PHLs would follow an agreed upon standard/format, verify the submitter, verify an established relationship with the submitter, separate acceptable requests from problematic ones, match acceptable requests to prescheduled submissions, edit the data record for completeness, and send an acknowledgment to the submitter about the message and physical sample when received.
  • Receive and send data using one or more standard message types as stipulated in state and federal regulations (e.g., Meaningful Use)3. Data include sample metadata, test orders, and test results.
  • Meet multiple transport protocols (e.g., Direct4 [HIE5 Service/Protocol], CONNECT6, PHIN MS7, and SOAP8).
  • Use multiple standardized vocabulary formats and function as an integration broker; integrate local and new codes and vocabulary standards; and flexibly utilize vocabulary standards across parties, e.g., using different codes to report the same test to different entities (from submitter to state to CDC).
  • Apply informatics efficiency measures during sample receiving and accessioning.
  • Electronically define and capture required identifiers/core data elements (submitter information, package, sample, tests, etc.) in the LIMS to initiate handling of any samples received or prepared, and add new data elements (e.g., metadata and demographics).

Capability Statement #1.1

Capability Statement Level Description of Level
Capability Statement #1.1 The laboratory is able to receive an electronic test request message from a submitter for all tests. Level 3 The laboratory is able to receive an electronic test request message from a submitter for all tests.
Level 2 The laboratory is able to receive an electronic test request message for some tests and paper-based requisitions for other tests.
Level 1 The laboratory is able to receive only paper-based requisitions for tests.
N/A Not applicable to this laboratory.

Level 3 : If the lab has a Drupal system set up, then using the basic form capabilities of Drupal, CA #1.1 should meet Level 3.

Required Drupal 8 Modules

[Core] Basic forms for editing entities


Capability Statement #1.2

Capability Statement Level Description of Level
Capability Statement #1.2 The laboratory is able to receive an individual electronic test request or package request message from a submitter and process the workflow Level 3 The laboratory is able to receive an individual electronic test request or package request message from a submitter and process the workflow completely.
Level 2 The laboratory is able to receive an individual electronic test request or package request message from a submitter and process the workflow partially.
Level 1 The laboratory is able to receive a paper, e-mail, or fax, but not an electronic test order request message.
N/A Not applicable to this laboratory.

Level 2 : Because there is currently no generic workflow module for Drupal 8, any workflow would only be implemented partially.

Required Drupal 8 Modules

[Core] Basic forms for editing entities


Capability Statement #1.3

Capability Statement Level Description of Level
Capability Statement #1.3 The laboratory is able to receive data using one or more standard message types9 (e.g., HL710 orders). Data include sample metadata, auxiliary data, test orders, test results, etc. Level 3 The laboratory is able to receive data on samples using one or more standard message types, and data include sample metadata, auxiliary data, test orders, etc.
Level 2 The laboratory is able to receive data using nonstandard formats but cannot receive data on samples using standard message types.
Level 1 The laboratory is able to receive data on samples only via paper, e-mail or spreadsheets.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #1.4

Capability Statement Level Description of Level
Capability Statement #1.4 The laboratory is able to send data using one or more standard message types (e.g., PHLIP11, SDWIS12, EDWR13, ERLN14 and LIMSi15). Data include sample metadata, auxiliary data, test orders, test results, etc. Level 3 The laboratory is able to send data on samples using one or more standard message types, and data include sample metadata, auxiliary data, test results, etc.
Level 2 The laboratory is able to send data on samples using nonstandard formats but cannot send data on samples using standard message types.
Level 1 The laboratory is able to send data on samples only via paper, e-mail or spreadsheets.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #1.5

Capability Statement Level Description of Level
Capability Statement #1.5 The laboratory is able to use multiple secure transport protocols, e.g., Direct4 (HIE5 Service/ Protocol), CONNECT6, PHIN MS7, SOAP8, etc. Level 3 The laboratory is able to use multiple secure transport protocols
Level 2 The laboratory is able to use at least one secure transport protocol.
Level 1 The laboratory is unable to use any transport protocols.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #1.6

Capability Statement Level Description of Level
Capability Statement #1.6 The laboratory is able to generate messages using multiple standardized vocabulary formats; integrate local and new codes and vocabulary standards16; and flexibly use vocabulary standards across parties, e.g., use different codes to report the same test to different entities (from submitter to state to CDC). Level 3 The laboratory is able to integrate vocabulary standards and local and new codes, including mapping local codes to national standards.
Level 2 The laboratory is able to use multiple vocabulary standards but cannot integrate new codes and vocabulary standards.
Level 1 The laboratory uses only local coding standards but not multiple vocabulary formats.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #1.7

The laboratory evaluates and applies informatics efficiency measures during specimen receiving and accessioning. Examples are provided below.

Capability Statement Level Description of Level
Capability Statement #1.7a Barcode scanners Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7b Flatbed scanners to read hard copy forms and transfer to electronic format to be stored as image/PDF files Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7c Radio-frequency identification (RFID) Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7d Robotics Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7e Central accessioning Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7f Consistent accessioning practices across the laboratory Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7g Web-based test order entry by submitter Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
Capability Statement Level Description of Level
Capability Statement #1.7h Distributing barcoded sample collection container/card Level 3 Yes
Level 2 The laboratory has evaluated this measure and opted not to implement.
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #1.8

Capability Statement Level Description of Level
Capability Statement #1.8 The laboratory is able to electronically define and capture required identifiers/core data elements (submitter information, package, sample, tests) in the LIMS to initiate handling of any samples received or prepared and can also add new data elements (e.g., metadata and pass through auxiliary data). Level 3 The laboratory is able to electronically define and capture required identifiers/core data elements in the LIMS to initiate handling of any samples received or prepared and can also add new data elements.
Level 2 The laboratory is able to electronically define and capture required identifiers and core data elements in the LIMS, to initiate handling of any samples received or prepared, but does not have the ability to add new data elements on an ad hoc basis.
Level 1 The laboratory is able to capture required identifiers and core data elements on paper only.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules
capability_1.txt · Last modified: 2016/12/30 20:09 by awake