1.6 Release (11/2023)

Athena V1 Integration

  • V1 Nsight-Athena EMR integration now available on the Athena Marketplace
  • WATCH FIRST: A Loom video short demonstration high level overview of the included features can be viewed for internal use only here

V1 Integration Features Summary

  • As an Athena EMR-Nsight integrated provider, all relevant appointments, appointment types, patient data, and provider data gets automatically uploaded ("seeded") into the Nsight tenancy on display
    • Reduction of administrative burden
  • At conclusion of Nsight workflow, push SOAP Note or Full Encounter Summary note .PDFs automatically into EMR & relevant patient encounter clinical chart
    • Additionally, we take relevant text fields of SOAP note and Full Encounter Summary note and upload to relevant fields within that particular patient's encounter clinical chart

How Is Athena V1 Integration Different from a non-EMR integrated Tenancy?

  • The EMR is the source of truth for all appointments & patient creation, rescheduling & edits - none done in Nsight
    • Integration affects the front/back end of the workflows, starting/ending at the EMR
  • In Nsight, certain settings removal - EMR is source of truth
    • More details surrounding these changes can be summarized in this video here
      • Some scheduling settings removed
      • Data upload removed
  • Additional information requirements needed up front via Sales; or from existing customers via CS in order to integrate (see right below screenshots for these requirements)

What Hasn't Changed?

  • Generally, outside of appointment scheduling, patient/provider creation done in app - most items remain the same
    • No changes to workflow features, including Telehealth
    • No changes to transcription, diarizing, summarization, or documentation
  • More information available in FAQs below

Send SOAP Note to EMR

Screenshots Illustrating "Send to EMR" Feature for Nsight generated SOAP Note from Nsight into integrated Athena (all fake data below)
Athena EMR UI when information comes from Nsight in the Encounter summary page

 


Send Encounter Summary Note to EMR

Screenshots Illustrating "Send to EMR" Feature for Nsight generated Full Encounter Summary Note from Nsight into integrated Athena (all fake data below)

Additional Information Needed from the Customer

What Additional Information do we need from a prospective Customer in order to integrate?
  1. We need a list of all Athena instances that may exist for the Provider, their unique EHR ID, and departments (locations?)
  2. We need a list of all the physical providers who have access to the Athena instance of choice for Nsight, their location, and respective unique email addresses
  3. We need to understand where their Athena license comes from - is it held at the ambulatory provider level? Or is it held with the hospital? If held at a hospital or network level, we do not yet know the implications of an integration - this demands a deeper discovery via Product/Project to understand the unique circumstances of the customer's Athena database tenancy BEFORE ANY AGREEMENT CAN BE MADE.

V1 Integration FAQ's

  1. Are Nsights still functional? Yes - insights are still functional and still lean on the selected workflows just like the "core" non-EMR Nsight product
  2. What about the other fields in the clinical chart in Athena? What about ROS? Vitals? Templates? Macros? Currently, these other fields are not yet supported. Additionally, macro intake & templates are not supported either. Templates, if existing in a provider's workflow in Athena, will NOT have their data overwritten when Nsight sends data to the EMR - it is "amended" to the clinical chart and viewable alongside pre-existing data.
  3. Does Nsight do anything else when pushing data to Athena? Anything else in this integration? No - V1 release was intentionally simplified in it's features to ensure stability with the short timeline available for development. Future versions will increase size and scope of value-adding features.
  4. So, what data comes from Athena vs. what comes from us (Nsight)? Athena provides all appointment, patient, and provider/location data. Nsight provides SOAP note/Full Encounter Summary note .PDFs, and SOAP/Full Encounter Summary note text fields into their clinically aligned fields back into the Athena database/clinical chart relevant to that particular patient appointment card/encounter
  5. How do I know Nsight successfully pushed the information to the EMR? You will notice a banner message popup in the lower right hand corner of Nsight:
  1. What happens if the information does not post to the EMR? What if it fails? You will receive a similar banner, but will be notified of a failure directly. At this point, you can try again, or wait and then try again.
  2. Why am I getting a "Document has been sent to EMR!" message, but I am not seeing the information posted as expected? Check to make sure that the provider has CHECKED IN the patient in the scheduled encounter. The appointment MUST BE CHECKED IN on Athena UI side before an Nsight appointment/encounter can push the information back into the EMR attached to their scheduled encounter & related clinical chart
  3. What happens if I click "Send to EMR" more than once? If the appointment has not been closed on the Athena side by the provider, then a duplicate posting of the same exact (edited/unedited) information is posted. This is purposeful, for this release, as we do not want to overwrite any information that may have existed previously in the patient's encounter clinical chart
  4. What happens to a provider's templates that may exist in their workflows in Athena? We do not yet fully know, but we designed the logic to not overwrite any existing information in the Athena clinical chart. It will "amend", meaning, "add to" the chart's overall collection of information without deleting/overwriting existing information. We cannot guarantee any specific formatting, placement, or user experience of how the data is viewed other than the fields described above - each provider customization could impact the data inputs
  5. Is Athena integration available for hospitals? No, currently only designed for ambulatory clients - hospital is future state
  6. So what's next? Is there any future iterations with Athena for ambulatory? Yes, in near future, a deeper integration with Athena will be taking place. Details are unknown at this time outside of Product roadmap.
  7. The Athena Marketplace listing seems to have issues, or I have a problem with some of the content, how do we get this resolved? Defer to Sales & Marketing who own the content for review - Product owns the review with Athena directly, after Sales & Marketing internal review and corrections.

 

---END---

Bug Fixes & Improvements

  • N/A

Known Bugs