Versions Compared

Old Version 1

changes.mady.by.user Andrea Price

Saved on

compared with

New Version Current

changes.mady.by.user Andrea Price

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Tentative Agenda

...

Info

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)

 

View file
namePartner Non-Disclosure_Agreement January 2023 (mutual)(76201.1) (2)_HF_signed v01.pdf
View file
namePartner Technical Specification 22.2.docx

From: Nele Jessel <njessel@athenahealth.com>
Sent: Wednesday, January 25, 2023 4:38 PM
To: Ken Allgood <ken.allgood@healthflow.io>; Regina Haynes <rhaynes@athenahealth.com>
Cc: Crystal Nwachuku <CNwachuku@nachc.com>; Pedro Carneiro <PCarneiro@nachc.com>; Andrea Price <APrice@nachc.com>; Nurta Ibrahim <nibrahim@athenahealth.com>; Julia Skapik <JSkapik@nachc.com>
Subject: Re: NACHC HIV CDS Tool + athena Follow-up

 

Hi Ken,

 

I believe (Regina, please correct me if I am wrong here)  that there will not actually be any cost to you for access to our developer portal until you have developed your app and are ready for it to become generally available through our platform - at that time, platform usage fees would apply (presumably covered by the CDC grant as I don’t believe your intent would be to have the health center pay for usage of the HIV guidance.) Whoever would ultimately own the app and be responsible for handling the sensitive data and also paying for platform usage should sign the NDA and provide us with a tech spec. Based on Julia’s earlier email, this would presumably be healthflow and possibly NACHC.

There is no payment due to athena until this goes generally available.