Letter Document

Source Object: Letter Document

Overview and Usage: The "Letter Document" source object in the athena EHR system is designed to manage and store various types of letter documents, including correspondence, medical reports, and other written communications. Developers can access and utilize this object for applications involving letter generation, storage, and retrieval. Key data fields include:

• Action Note: Records actions or comments associated with the letter document.
• Appointment ID: Links the letter document to a specific appointment.
• Assigned To: Identifies the recipient or responsible party for the letter.
• Created Date and Time: Indicates when the letter document was initially created.
• Created User: Represents the user responsible for creating the letter.
• Deleted Date and Time: If applicable, marks when the letter document was deleted or removed.
• Department ID: Specifies the department or entity associated with the letter.
• Description: Provides a brief description or summary of the content of the letter.
• Document Source and Subclass: Categorizes the source and type of the document for classification.
• Encounter ID: Associates the letter document with a specific patient encounter.
• Entity Type: Identifies the type or category of the entity that the letter pertains to.
• Internal Note: Allows for internal notes or comments related to the letter document.
• Last Modified Date: Records the last date of modification for the letter document.
• Last Modified User: Specifies the user responsible for the most recent modifications.
• Pages (Content Type, Href, Page ID, Page Ordering): Facilitates page management and layout for multi-page letters.
• Patient ID: Links the letter document to the relevant patient.
• Priority: Indicates the level of urgency or importance assigned to the letter.
• Provider ID: Identifies the healthcare provider or clinician associated with the letter document.
• Provider Username: Specifies the username of the provider responsible for the letter.
• Status: Describes the status of the letter document (e.g., draft, pending, approved).
• Subject: Provides the subject or topic of the letter.
• Clinical Provider ID: Identifies the healthcare provider associated with the clinical aspects of the letter.
• Declined Reason Text: If declined, captures the reason or explanation for the letter's decline.
• Document Class and Type: Categorizes the letter by class and type for organization and searchability.
• External Accession ID: Links the letter document to an external accession identifier.
• External Note: Records external notes or comments related to the letter document.
• Internal Accession ID: Associates the letter with an internal accession identifier.
• Recipient Name: Specifies the name of the recipient or addressee of the letter.
• Approved Date and User: Records the approval date and the user responsible for approval.
• Attachments Link: Stores links or references to any attached documents or files.
• Callback Number: Provides a callback contact number for the letter recipient.
• Create From Order ID: If generated from an order, links to the original order.
• HTML: Contains the letter content in HTML format.
• Letter ID: Serves as a unique identifier for the letter document.
• Letter Text: Stores the textual content of the letter.
• Paper Form Name: If applicable, specifies the name of the associated paper form.
• XML: Contains the letter content in XML format.
• XML Title: Stores the title associated with the XML content.
• XML Type: Indicates the type of XML content within the letter document.

Developers can leverage the "Letter Document" source object to create applications that facilitate the creation, management, and distribution of various letter documents, streamlining communication within healthcare settings or other industries.

Mapping Table