Skip to main content

Athena Template Mapping: Map Attend Sections to Athena

Choose where each Attend template section should appear in Athena and avoid common mapping problems.

Written by Attend Health Team

Athena Template Mapping: Map Attend Sections to Athena

Template mapping determines where each section of an Attend note appears in Athena.

When a template is created or edited for an Athena workspace, every text section must be assigned an Athena destination or explicitly marked Do not send to Athena.

Supported Athena destinations

Attend can write to four Athena documentation sections.

History of Present Illness

Use for content such as:

  • Presenting concern

  • Symptom history and course

  • Interval history

  • Relevant subjective history

Review of Systems

Use for an explicit system-by-system review of symptoms.

Physical Exam

Use for clinician-observed or measured examination findings.

Assessment and Plan

Use for content such as:

  • Diagnoses

  • Clinical impression

  • Assessment

  • Treatment and follow-up plan

Do not send to Athena

Use this option when a section has no safe destination in the supported Athena fields. Common examples include:

  • Patient-facing instructions

  • Administrative content

  • Internal workflow notes

  • Content that should remain in Attend only

The section remains part of the Attend note but is omitted during Athena writeback.

Map a template

If you have permission to create or edit the template:

  1. Open the template editor in Attend.

  2. Review each section.

  3. Use the Athena destination menu to choose the appropriate destination.

  4. Choose Do not send to Athena for sections that should be omitted.

  5. Confirm that at least one section is sent to Athena.

  6. Save the template.

Mapping rules

  • Every text section needs a destination or an explicit Do not send choice.

  • At least one section must be sent to Athena.

  • Athena does not currently support separate Attend destinations for Plan, Medications, Orders, or Patient Instructions.

  • Multiple Attend sections may map to the same Athena destination.

  • When multiple sections share a destination, Attend combines them before sending.

  • Mapping is configured per template. Two templates can route similar content differently.

Example mapping

For a SOAP-style template, a common mapping is:

  • Subjective → History of Present Illness

  • Objective → Physical Exam

  • Assessment and Plan → Assessment and Plan

If your Objective section contains material that does not belong in Physical Exam, consider creating more specific Attend sections or choosing Do not send to Athena for content without an appropriate destination.

What happens when a template changes?

Review the Athena mapping whenever you:

  • Add a section

  • Delete a section

  • Rename or substantially change the purpose of a section

  • Duplicate a template

  • Change the type of content a section should contain

New sections need a destination or Do not send selection. Deleted sections should no longer be referenced by the mapping.

Mapping changes apply to future sends. They do not move or alter content already written to Athena.

Common setup messages

Athena Setup Required

The Send to EHR button may display Athena Setup Required when the template does not have a complete, valid mapping.

Open the template editor and confirm that every section has a destination or Do not send to Athena.

Choose an Athena destination or “Do not send” for every section

At least one section has not been configured. Assign a destination to each section.

At least one section must be sent to Athena

Every section is currently configured as Do not send to Athena. Route at least one section to a supported Athena destination.

This note template needs Athena destinations before it can be sent

The saved template mapping is missing or no longer matches the template. Review the template mapping or contact your workspace administrator.

If the template cannot be edited or the message continues after saving, contact [email protected].

Did this answer your question?