Project Approach Overview

Project Approach Overview

In collaboration with CDC, APHL has technical assistance subject matter experts whose mission is to assist public health partners in implementing data exchange solutions. The Detor team will provide expertise in project management, laboratory workflow, terminology, technical architecture and systems integration.

This team will provide hands-on support and will adhere to a methodology that incorporates best-practices, efficient and effective management, communication, and coordination.

The key benefits of our approach are:

Reduces burden on over-allocated or unavailable resources.

Promotes on-time and on-scope implementations.

Minimizes uncertainty and risk.

Prepares your team for long-term sustainability.

Approach By Phase

image-20240522-144439.png

Pre-Implementation

The pre-implementation phase will be focused on strategizing and preparing for the Detor project, particularly in the areas of legal execution, staff allocation, and completion of a test ordering and test resulting organization profiles.

The primary components of this phase include:

Completion of an organization profile for both the test ordering and test resulting entities
Identification and allocation of required project roles at all organizations (creation of contact list)
Identification of tests in scope (test catalogue)
Completion of legal agreements
Creation of project schedule

Planning & Analysis

The planning and analysis phase will be focused on gathering data on the operational and technical processes of both the test ordering and test resulting organizations. This data will be analyzed to prepare for Detor configuration and support in the design of the new operational and technical processes that will exist with Detor.

The primary components of this phase include:

Project kick-off
Commitment to project schedule
Commitment to project scope
Initial use of project control measures (communication, issue/risk/change management, and status reporting)
Analysis, design and approval of test order and results workflows for selected test types
Analysis of data for selected test types (gap analysis)
Analysis of current technical environment
Integration/connectivity planning
Review of test order message (to be received by APHL via email)
Review of test result message (to be received by APHL via email)
Collection of pre-implementation evaluation metrics

Configuration

The configuration phase will establish the required transport and routing, message transformation and translation, terminology services, and monitoring.

Note that initial configuration work will begin prior to the completion of Planning & Analysis.

The primary components of this phase include:

Mapping/translation of the test ordering entity’s data elements to the Detor data elements
Mapping/translation of the test resulting entity’s data elements to the Detor data elements
Establishing connectivity
Creation of the intermediary test order and results messages
Configuration of monitoring tools

Validation

The validation phase will include the coordinated testing of the Detor operational and technical processes. This phase will be supported by APHL but will require focus and coordination between all partners.

The primary components of this phase include:

Validation of connectivity and data flow
Validation of successful test ordering for all scenarios associated with select test types
Validation of successful test resulting for all scenarios associated with select test types
Validation of expected error handling
Validation of monitoring tools
Validation of operational processes
Updates to Detor configuration, as needed
Training of staff in ongoing Detor support and maintenance responsibilities
Approval for test ordering entity to proceed to production
Approval for test resulting entity to proceed to production

Production

The production phase will include the “go-live” of Detor and 1-2 weeks of post-production implementation team support.

The primary components of this phase include:

Detor productive use
Validation of productive operational and technical processes
Transition to the AIMS Support team
Collection of post-implementation evaluation metrics (this may occur several months following productive use)