Encounter Document

Source Object: Encounter Document

Overview and Usage: The "Encounter Document" source object in athena EHR is a pivotal component for documenting and managing documents and notes related to patient encounters. It enables healthcare providers to capture a wide range of information, including clinical notes, documents, and encounter-specific details. Here's an overview of key fields and their usage:

• Action Note: "actionnote" allows for the inclusion of specific notes or comments related to actions taken or required for the encounter document. It provides additional context for the document's purpose or status.
• Appointment ID: "appointmentid" specifies the unique identifier for any appointment associated with the encounter document, allowing for tracking and linkage to specific appointments.
• Assigned To: "assignedto" identifies the user or entity to whom the encounter document is assigned, facilitating task management and responsibility allocation.
• Created Date and Time: "createddatetime" records the date and time when the encounter document was created, aiding in chronological tracking and reference.
• Created User: "createduser" indicates the user who created the encounter document, providing information about the document's origin.
• Deleted Date and Time: "deleteddatetime" captures the date and time when the encounter document was deleted or marked for removal.
• Department ID: "departmentid" serves as an identifier for the department or unit associated with the encounter document, aiding in organization and categorization.
• Description: "description" provides a textual description of the encounter document, offering information about the document's content or purpose.
• Document Data: "documentdata" may include the actual data or content of the encounter document, such as clinical notes, reports, or other document types.
• Document Source: "documentsource" identifies the source or origin of the encounter document, helping with document attribution and provenance.
• Document Subclass: "documentsubclass" categorizes the encounter document into a specific subclass, facilitating document classification and management.
• Encounter Date: "encounterdate" specifies the date of the patient encounter associated with the document, aiding in chronological organization.
• Encounter Document ID: "encounterdocumentid" serves as a unique identifier for the specific encounter document, enabling efficient tracking and reference.
• Encounter ID: "encounterid" links the encounter document to a specific encounter, ensuring proper association with patient care events.
• Entity Type: "entitytype" may indicate the type of entity or user associated with the encounter document, allowing for differentiation between various document creators or contributors.
• Internal Note: "internalnote" allows for internal comments or notes related to the encounter document, which can be useful for administrative or clinical context.
• Last Modified Date and Time: "lastmodifieddate" and "lastmodifieduser" record the date and time of the last modification and the user responsible for it, aiding in tracking changes to the document.
• Pages Content Type: "pages.contenttype," "pages.href," "pages.pageid," and "pages.pageordering" pertain to the content and structure of document pages, enabling detailed document organization and formatting.
• Patient ID: "patientid" links the encounter document to the patient to whom it pertains, ensuring proper patient data management.
• Priority: "priority" may indicate the priority level or urgency associated with the encounter document, aiding in document triage and handling.
• Provider ID and Username: "providerid" and "providerusername" specify the healthcare provider responsible for the encounter document, allowing for proper attribution.
• Status: "status" indicates the current status or state of the encounter document, helping track its progress or completion.
• Subject: "subject" provides a title or subject for the encounter document, summarizing its content.
• Clinical Provider ID: "clinicalproviderid" specifies the clinical provider associated with the encounter document, enabling proper clinical context and reference.
• Declined Reason Code, Description, and Code Set: Fields related to declined reasons ("declinedreason.code," "declinedreason.description," "declinedreason.codeset") allow for documenting reasons for document declines, aiding in tracking and resolution.
• Contraindication Reason Code, Description, and Code Set: Fields related to contraindication reasons ("contraindicationreason.code," "contraindicationreason.description," "contraindicationreason.codeset") document contraindication reasons associated with the encounter document, ensuring patient safety and appropriate documentation.

The "Encounter Document" source object is essential for documenting and managing a wide array of documents, notes, and information associated with patient encounters within athena EHR. It plays a crucial role in maintaining comprehensive patient records and facilitating efficient care coordination. Developers can leverage this source object to build features and applications that enhance the documentation, organization, and management of encounter-related information.

Mapping Table