Skip to end of metadata
Go to start of metadata
Agenda |
|---|
Presenter/Facilitator | Topic |
Datapult | Centralized ELR Updates |
APHL ETOR Team | APHL ETOR Presentation |
Vanessa Holley, APHL | Questions/Updates |
Notes: |
|---|
Presenter/Facilitator | Topic | Discussion: | Action Items |
Datapult | Centralized ELR Updates | No updates for 10/5. | |
Rachel Shepherd and Dari Shirazi, APHL | ETOR Presentation | Achieving ETOR across Public Health: Full presentation slides available  Current landscape for ETOR: Landscape analysis conducted in 2021 found that very few public health labs (PHLs) were prepared to implement ETOR in a large scale and substantial way. Technical capabilities varied across labs: 86% indicated lack of resources 13% indicated limited access to training 65% indicated challenges with partner engagement.
When labs are successful in achieving ETOR, often via ‘one-off’ solutions or single connections for each partner, with minimal economies of scale. For DMI, ETOR is now a required activity for public health labs. There are however different approaches to ETOR with varying degrees of sustainability: Web portal System integrated (Direct) AKA 1:1 connections with each partner System integrated (Indirect) AKA using a centralized middle solution or intermediary to connect with multiple partners. This is currently what the AIMS ETOR team is developing.
AIMS is one of the intermediary approaches being developed for ETOR. Leverages shared tools, resources, and technical expertise - all reducing the burden on pubic health to achieve ETOR and reducing redundancy. Initial year for the project: APHL currently convening core project team and PHL-specific technical assistance teams. Developing technical solution, working with a couple pilot implementation PHLs and the HCO partners using Newborn Screening as a first use case. However, what is currently being designed will be able to apply to any use case moving forward (e.g., foodborne, environmental, clinical, etc.)
Aiming to go live by the end of this year for the pilot states, looking to expand to others in following year. Benefits of ETOR on ELR: Improve data completeness, flexibility, and quality. Less dependence on manual data entry Long-term potential for decision support.
Discussion and Q&A: For those already working on the more direct ETOR connection, this would be an additive solution correct? Meaning that work would not need to be started over. Labs and hospital can absolutely choose to keep any existing solution, especially if you have the resources to maintain. You may however switch those connections over to AIMS, if you choose. Some jurisdictions do not have the resources and capabilities to maintain many direct connections, which is where the AIMS can help.
Will the AIMS ETOR solution be free? Oregon: One of the pieces we are most excited about is the vocabulary server, including mapping and translation services. This will be very helpful in dealing with local codes. When will this be available for PHLs beyond the initial pilot?
| |
Other Discussion/Updates |
Open forum questions | | Question: When would a sender’s CLIA switch from 0ZID to a traditional CLIA, but still send through AIMS? Did this happen recently with eMed? | |