23
Analysis. Answers. Action. www.aphl.org APHL Electronic Test Order and Result Initiatives

APHL Electronic Test Order and Result Initiatives

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

Page 1: APHL Electronic Test Order and Result Initiatives

Analysis. Answers. Action. www.aphl.org

Analysis. Answers. Action. www.aphl.org

APHL Electronic Test Order and ResultInitiatives

Page 2: APHL Electronic Test Order and Result Initiatives

ETOR- Electronic Test Order and Results

Web Portal

Page 3: APHL Electronic Test Order and Result Initiatives

PHL ETOR Drivers

• PHLs need to remain competitive and relevant• Informatics solutions need to be streamlined to meet increased

data demands.• Result data need to get into the right hands quickly• Data are needed by multiple stakeholders

– from the clinician to PH partners

Page 4: APHL Electronic Test Order and Result Initiatives

Web Portal RFP distributed – Supported thru CDC’s Division of TB elimination– National DST reference center– iConnect/Lab Web Portal (LWP) Selected

Programmatic Efforts to assist ETOR– White paper / policy statement– Standards Development (LOI/LRI)– #1 priority of info subcommittee

LWP deployed on AIMS VPC – 5 Antibiotic Resistance Lab Network (ARLN) regional labs– National TB DST reference center project

HHS ONC ETOR process improvement– Expand use of LWP to support emerging infectious disease use case.– Expand to look at provider, lab and epi communication channels-

Gaining momentum

Page 5: APHL Electronic Test Order and Result Initiatives

ETOR in the Clinical Domaincare & treatment / passive surveillance

DETECT REPORT RESPONDREPORT

Page 6: APHL Electronic Test Order and Result Initiatives

ETOR in Public Healthactive surveillance needed

DETECT REPORT RESPOND

critical

Page 7: APHL Electronic Test Order and Result Initiatives

CRE Colonization Use Case:Interrupt transmission asap

DETECT REPORT

Page 8: APHL Electronic Test Order and Result Initiatives

Public Health needs always evolve

Page 9: APHL Electronic Test Order and Result Initiatives

National Tuberculosis Drug Susceptibility Testing Reference Lab

Provide ETOR tools that support TB-DST shared services

Page 10: APHL Electronic Test Order and Result Initiatives

Antibiotic Resistance Lab Network

Electronically report CRE colonization results to a network of cross-jurisdictional clinical and public health partners within 48 hours of specimen

receipt

Page 11: APHL Electronic Test Order and Result Initiatives

ONC Idea Lab Project

Build on current ETOR efforts to enhance tools to support both private and public needs in the face of Zika and other emerging diseases

Presenter
Presentation Notes
Clinical submitters need: a way to ordering tests, retrieving status and receiving results for suspect Zika cases. Current tools to capture epidemiological significant questions when a specimen is submitted for Zika testing (known as Ask at Order Entry questions), are too cumbersome and “after the fact” to help with testing prioritization. Epidemiologists do not have an efficient way to assist in the testing process to authorize, sort and prioritize testing based on submitter provided information and national case definitions.
Page 12: APHL Electronic Test Order and Result Initiatives

Approach

Centrally hostedSelected competitively LIMS agnostic

Page 13: APHL Electronic Test Order and Result Initiatives

Lab Web Portal on AIMS

Presenter
Presentation Notes
Minimize impact to the Laboratory Workflow Support cross jurisdictional partners Increase communication across a network of clinical and public health partners
Page 14: APHL Electronic Test Order and Result Initiatives

HL7 standards (HL7 2.5.1 LOI/LRI) have had slow adoption ratesSpecialized knowledge neededEach time you add a test, its like running around the house 7 times…(Dari)Most commercial labs (e.g. Quest) already have web portals

Couldn’t wait any longerPHLs are launching LIMS specific portal extensionsSame model as LIMS- now all the web portals will be disparate…Wanted to find something LIMS agnostic, flexible, and “Cloud-ready” to support mutual assistance and surge needs.

Why a web portal vs. Traditional ETOR (HL7)

Page 15: APHL Electronic Test Order and Result Initiatives

Collective Goals• Document Existing and potential data flows

• Identify technology and process Impact to stakeholders

• Identify & validate Functional requirements

• Perform Gap Analysis between LWP and Requirements

• Develop Standards-based implementation guides

• Define user scenarios and prioritize enhancements to captureepidemiological relevant information

• Look for solutions to reduce the burden of PHL standards based data exchange.

Page 16: APHL Electronic Test Order and Result Initiatives

160

Presenter
Presentation Notes
AIMS currently supports 15 distinct use cases. ELSM for Flu PHLs sending 2.5.1 and 2.31 to CDC Navy Lab PHLIS2 via SFTP to AIMS Air Force sending 2.3.1 via SFTP to AIMS NMI-PHA sending case notification data in HL7 2.5.1. to CDC VPD—PHLs sending HL7 2.5.1 to CDC Rabies—PHL HL7 2.5.1 to CDC ELR-Quest/PAML clinical lab HL7 2.5.1 to PHA’s LRN-PHLs sending HL7 2.5.1 to CDC (19 labs) AMD: Whole genome sequence data (flu to CDC, strep to CDC, Urdo to CDC Use case for STEVE 2.0 data flows from states to registry Death records (possibly) can showcase as a success—STEVE 2.0 has made simpler ElCR—providers sending initial case reports from hospital to PHA as tests are ordered, automatic PHIZ? Immunization registries at states sending to other immunization registries SURGE….FL and TX State to state exchange Syndromic surveillance AR – 55 PHLs sending CRE/CRPA to CDC via CSV through AIMS (for now, Live by June) AR – 7 regional PHLs sending candida strep pneumo, GC and CRE colonization to CDC via HL7 (summer) ETOR – TB DST and AR CRE colonization – (AR is 5 PHLs) TB is CA PHL (MDL lab)
Page 17: APHL Electronic Test Order and Result Initiatives

APHL Committee Structure- where does this fit?

Strategy– organizational

Strategic Alignment– Programmatic- Big picture– Member Focused

Innovation and Delivery– Time bound– Single initiative/focus

Targeted Needs– Initiative Driven– Concrete actions

Page 18: APHL Electronic Test Order and Result Initiatives

Focused on specific technical challenges, advancements and trends in PHL informatics

– First project focused on the challenges of centralized IT infrastructure

– July 2017: ETOR selected as primary focus

Subcommittee Overview

Page 19: APHL Electronic Test Order and Result Initiatives

ETOR: Divide and Conquer

• Complex initiative- needed to expand membership

• Technical, business and operational components

• Meeting the needs of the project sponsors and PH stakeholders

• APHL technical efforts come into play– AIMS/member services– Cloud Computing options

Page 20: APHL Electronic Test Order and Result Initiatives

Short Term: Refine and validate new functionality and deployment of the LWP solution on AIMS

– ONC/APHL Lab/Epi support for EID/others

Long Term: Provide technical guidance on ETOR technology solutions and deployment options

Technical Development Taskforce Charge:

Page 21: APHL Electronic Test Order and Result Initiatives

Identify operational/institutional topics for BC taskforce to consider

Page 22: APHL Electronic Test Order and Result Initiatives

So….as summer approaches and the mosquitos start to buzzzz…How can we better leverage our community to:

Define and evolve common solutions to support both clinical and public health ETOR

Identify the ETOR business case/operational drivers

Page 23: APHL Electronic Test Order and Result Initiatives

Thank You!