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 5
Next »
Attendees
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 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 | athenahealth | |
15 | Discussion James Thoughts on the Integration Approach 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 if we are 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 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 Contact Andrews team about presenting first about their integration during 1/17 call Who should Athena work with on paperwork?
| Julia/Ken | |