Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Agenda

  1. Introductions - All

  2. Description of the tool, status, and desired outcomes for this meeting – Julia

  3. Technical issues – data mapping and integration components to achieve the goal – athenahealth team

  4. Discussion – All

  5. Next Steps - Julia

Materials

Attendees

NACHC Informatics Team

athenahealth

HealthFlow

Julia Skapik (Deactivated)

John Gresh

Pedro Carneiro (Deactivated)

Andrea Price (Deactivated) - on leave

Crystal Nwachuku (Deactivated)

Nele Jessel- CMO

Chad Dodd

BJ Bloom

Morgan Diaz - Sales

Yolanda Montano

Vanessa Vining

Ken Allgood

Thai Lam

James Haines-Temons

Notes

Duration

Item

Who

Action Items

5

Welcome and Introductions

Julia/All

7

Description of the tool, status, and desired outcomes for this meeting

  • Need to find Athena health center customers that are interested in using this

    • Does Athena have list of health center partners?

  • NACHC Athena User Meeting soon - Andrea already touched base with Phillip. HealthFlow should join.

  • Timeline - 6 months of use at the health center level, ending July 31, 2023.

Julia

  • Invite HealthFlow to NACHC Athena User Group Meeting

7

Technical issues – data mapping and integration components to achieve the goal – athenahealth team

  • Should logic live in Athena or outside?

  • Couple ways to integrate the app into the user experience.

    • Was not clear to Crystal what those approaches were.

athenahealth

15

Discussion

  • James Thoughts on the Integration Approach

    • Problem is ontology/classification of items with Athena and where to find things, not availability of the data.

  • How does Athena typically integrate these type of tools?

    • Need to identify mutual customer for validation before moving into production

    • Contracting and identifying mutual clients usually takes the most time

    • Athena usually launches in 30 days or less when using APIs,

    • Athena does not offer customization, they offer configurations.

  • Use case for a clinical visit?

  • Intention to monetize? No, CDC paid for development.

  • If enough information is there to indicate medium/high risk, provider would be notified. Connect to order set that does pre PrEP assessment requirements, etc.

All

  • Julia/Pedro - Need to identify clear use case for a clinical visit.

5

Next Steps

  • Invite HealthFlow to NACHC Athena User Group Meeting

  • Identify mutual client. Get buy in from the organization.

  • Athena will send over some documentation

    • Identify technical team and resources - Morgan and Chad

  • Contact Andrews team about presenting first about their integration during 1/17 call

  • Who should Athena work with on paperwork?

Julia/Ken

  • Andrea sent a note to Phillip Stringfield asking if HealthFlow could demo on an upcoming meeting.

1/24/2023 - Ken

General list of tasks to address to enable support of the HIV CDS app on AthenaOne

  • Identify target health center (must be a current AthenaOne subscriber) - NACHC

  • Come up with funding approach, establish and issue contract - NACHC

  • Sign partner contract with Athena - HealthFlow

  • Perform LOE assessment - Athena & HealthFlow

  • Submit final cost for integration, to include Athena partner tax - HealthFlow

  • Initiate app build and integration design work - HealthFlow & Athena (with engagement from target health center and NACHC)

  • Finalize build and implement within AthenaOne instance for testing - HealthFlow & Athena

  • Validate Smart On FHIR app functionality and usability within AthenaOne - Target users & NACHC

  • Officially release app for target health center users and advertise availability for other health centers for phase 2 release  (need to identify funding source for follow on implementations)

 

  • No labels