User Tools

Site Tools


capability_8

CA 8: Data Exchange and Interoperability

This capability area focuses on systematically addressing electronic interoperability and data exchange.

Guidance Statement

Purpose: Data exchange and interoperability are two significant capabilities for PHLs. Interoperable public health data systems and standards are a platform for exchange of information across all associated entities and create opportunities for improvement and efficiencies in public health.

What: A key issue for PHLs is the type, quality, and security of data exchange methods and interoperability between systems enabling the safe and secure transmission of data following agreed upon standards. This capability area addresses the types of data exchange, the quality of data including the ability to map to standardized codes, the security of information while its being transported, and the ability to reformat the same data based on partner’s need.

How: As data sharing abilities advance with technology, the ability to utilize standards, the flexibility to accommodate ever-changing transport mechanisms, and the need to validate the content and ensure security of electronic data exchange are becoming critical tools. A laboratory that has the desired Informatics capabilities with regard to data exchange and interoperability can:

  • Exchange data electronically with various entities such as other PHLs and federal, state, and local partners.
  • Exchange bidirectional data, such as receiving electronic orders and test results with health facilities, sending electronic orders, and receiving results (exchange with CDC and other PHLs).
  • Provide data electronically through a web portal for data and information exchange.
  • Create and manage data exchange channels in partnership with state and national efforts such as statewide HIEs1.
  • Meet external reporting requirements of public health agencies and health departments. These requirements include the ability to:
  • - Identify reportable laboratory events.
  • - Adopt required message specifications (e.g., Meaningful Use)2.
  • - Deliver secure automated electronic laboratory reports (ELR)3 to public health authorities.
  • - Generate required HL74 messages for ELR messaging.
  • - Use secure ELR transport mechanisms.
  • Meet external reporting requirements of public health agencies and health departments using required ELR standards.
  • Send automated electronic results to partners based on agreed-upon protocols.
  • Send messages using different secure transports such as Virtual Private Network (VPN)5, PHIN MS6, or HIE Direct7.
  • Map Logical Observation Identifiers Names and Codes (LOINC)8 for tests and Standardized Nomenclature of Medicine (SNOMED)9 codes for test results to national and local notifiable diseases and conditions by integrating with Nationally Notifiable Conditions Tables (i.e., RCMT10 within PHIN VADS11).
  • Interface the LIMS with a message broker that maps local codes to standard codes, validates that all required data elements are present, generates valid message structure and content, and securely transmits the message using the agreed-upon transport mechanism. The message broker/integration engine can be a separate stand-alone capability or integrated with the LIMS.
  • Participate in APHL advocacy initiatives (e.g., PHLIP12, PHLISSA13, ELR TA14, NewSTEPS15).

Capability Statement #8.1

Capability Statement Level Description of Level
Capability Statement #8.1 The laboratory is able to exchange data electronically with various entities, such as with other PHLs and federal, state and local partners, and is able to meet external reporting requirements of public health agencies and health departments. Level 3 The laboratory is able to perform these functions.
Level 2 The laboratory has limited ability to perform these functions.
Level 1 The laboratory is unable to exchange data with partners electronically, mostly reporting to partners manually (e.g., by mail/fax).
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.2

Capability Statement Level Description of Level
Capability Statement #8.2 The laboratory has or intends to develop software as part of its information system that will enable it to identify and message reportable laboratory events to public health. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.3

Capability Statement Level Description of Level
Capability Statement #8.3 The laboratory has or intends to develop the message specification for Meaningful-Use (MU)2 -approved Automated Electronic Laboratory Reporting Implementation Guide (e.g.,ORU R01 HL7 2.5.1). 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 #8.4

Capability Statement Level Description of Level
Capability Statement #8.4 The laboratory delivers or intends to deliver secure automated electronic laboratory reports to a designated public health authority consistent with the MU requirements on an agreed-upon schedule. 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 #8.5

Capability Statement Level Description of Level
Capability Statement #8.5 The laboratory generates HL74 messages directly, without conversion. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.6

Capability Statement Level Description of Level
Capability Statement #8.6 The laboratory uses automated validation tools to assure that ELR messages meet structural and content guidelines. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.7

Capability Statement Level Description of Level
Capability Statement #8.7 The laboratory uses CDC’s PHIN MS6 for secure transport messaging of reportable laboratory tests to public health. Level 3 The laboratory currently has PHIN-MS implemented.
Level 2 The laboratory has plans to implement PHIN-MS.
Level 1 The laboratory does not use PHIN-MS and has no plans to implement it.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.8

Capability Statement Level Description of Level
Capability Statement #8.8 The laboratory uses secure ELR transport mechanisms. Level 3 The laboratory currently participates in NHIN or connects through some HIE.
Level 2 The laboratory uses secure electronic transport mechanisms and proprietary point-point connections.
Level 1 The laboratory cannot use secure electronic transport mechanisms.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.9

Capability Statement Level Description of Level
Capability Statement #8.9 The laboratory’s ELR software solution employs business rules to automatically select/filter identified reportable data. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.10

Capability Statement Level Description of Level
Capability Statement #8.10 The laboratory is able to exchange transactional data18 between systems (e.g., ETORs19). Level 3 The laboratory is able to receive transactional data and process it.
Level 2 The laboratory is able to receive a transaction but the transaction is not integrated with the process.
Level 1 The laboratory is not able to receive these transactions.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.11

Capability Statement Level Description of Level
Capability Statement #8.11 The laboratory is able to provide data electronically through a web portal for data and information exchange (e.g., turn-around information, result reporting, samples in-house, ad hoc queries, etc.). Level 3 The laboratory is able to provide data electronically through a web portal for data and information exchange.
Level 2 The laboratory has some capability to provide data electronically through a web portal for data and information exchange.
Level 1 The laboratory is not able to provide data electronically through a web portal for data and information exchange.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.12

Capability Statement Level Description of Level
Capability Statement #8.12 The laboratory is involved with state and national efforts, such as statewide HIEs and relevant standards development organizations (SDOs), to create and manage data exchange channels. Level 3 The laboratory is able and is involved with state and national efforts to create and manage data exchange channels.
Level 2 The laboratory is aware of the standards bodies and activities around these efforts but is not an active participant.
Level 1 The laboratory is not involved in these efforts.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.13

Capability Statement Level Description of Level
Capability Statement #8.13 The laboratory supports other “environmental” and non-clinical data exchange/data submittal networks. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.14

Capability Statement Level Description of Level
Capability Statement #8.14 The laboratory performs data exchange electronically with the PH Newborn Screening program. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.15

Capability Statement Level Description of Level
Capability Statement #8.15 The laboratory performs data exchange electronically through HIE1 or direct connections. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.16

Capability Statement Level Description of Level
Capability Statement #8.16 The laboratory exchanges blood lead data for CLPPPs. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.17

Capability Statement Level Description of Level
Capability Statement #8.17 The laboratory’s software solution integrates Nationally Notifiable Conditions Tables and Local Tables (e.g., RCMT10) within PHIN VADS11, with mappings of LOINC8 test codes to national and local notifiable diseases/conditions. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.18

Capability Statement Level Description of Level
Capability Statement #8.18 The laboratory actively participates with public health jurisdictions to create and develop listings of unique conditions that are reportable, and is able to proactively upgrade its capabilities to accommodate these changes. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.19

Capability Statement Level Description of Level
Capability Statement #8.19 The laboratory supports the electronic reporting of the SACHDNC24 screening panel of 31 core conditions and 26 secondary conditions. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.20

Capability Statement Level Description of Level
Capability Statement #8.20 The laboratory uses an enterprise integration engine that validates, filters, and maps the data, converting local codes to standard codes, checks that all required data elements are present, and generates valid message structure and content before securely transmitting the message to the public health authorities using the agreed-upon transport mechanisms. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.21

Capability Statement Level Description of Level
Capability Statement #8.21 The laboratory is able to electronically support the ICLN26 networks where possible, and for each one, data exchange occurs automatically. (Please respond in regards to your laboratory’s ability to participate directly or indirectly through your partners.) Level 3 The laboratory is able to electronically support ICLN networks where possible.
Level 2 The laboratory is able to participate manually
Level 1 The laboratory is unable to support this operation.
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

Capability Statement #8.22

Capability Statement Level Description of Level
Capability Statement #8.22 The laboratory actively participates in APHL advocacy initiatives, such as PHLIP, HLISSA, ELR TA, and NewSTEPS. Level 3 Yes
Level 1 No
N/A Not applicable to this laboratory.
Required Drupal 8 Modules

capability_8.txt · Last modified: 2017/01/01 01:11 by awake