Encounter

Source Object: Encounter

Overview and Usage: The "Encounter" source object in athena EHR is a pivotal component for recording detailed information related to patient encounters. It encapsulates various aspects of encounters, including encounter details, diagnosis information, provider information, and status updates. Here's an overview of key fields and their usage:

• Appointment ID: "appointmentid" indicates the ID of the associated appointment, if applicable, connecting the encounter to the scheduled appointment.
• Department ID: "departmentid" specifies the department or clinic where the encounter took place, providing context for the encounter's location.
• Encounter Date: "encounterdate" records the date when the encounter occurred, offering a chronological reference.
• Encounter ID: "encounterid" is a unique identifier for the encounter, ensuring individual encounter records can be distinguished.
• Encounter Type: "encountertype" describes the type of encounter, which can vary based on the purpose or nature of the visit (e.g., routine checkup, urgent care, specialist consultation).
• Encounter Visit Name: "encountervisitname" may provide a descriptive name or title for the encounter, enhancing recognition and categorization.
• Patient Location ID: "patientlocationid" designates the location within the healthcare facility where the patient was seen during the encounter, aiding in tracking patient movement.
• Patient Status ID: "patientstatusid" represents the patient's status during the encounter (e.g., inpatient, outpatient, emergency), enabling the differentiation of encounter types.
• Provider ID: "providerid" identifies the healthcare provider or clinician responsible for the encounter, connecting the encounter to the provider's profile.
• Stage: "stage" and "status" fields can be used to record the stage and status of the encounter, providing insights into the progress and completion of the encounter.
• Closed Date: "closeddate" records the date when the encounter was closed or marked as completed.
• Closed User: "closeduser" specifies the user or entity responsible for closing the encounter, allowing tracking of closure actions.
• Last Reopened: "lastreopened" documents the date when the encounter was last reopened or modified after closure.
• Last Updated: "lastupdated" records the date and time of the last update to the encounter record.
• Provider First Name: "providerfirstname," "providerlastname," and "providerphone" contain information about the provider's first name, last name, and contact phone number.
• Diagnoses: The "diagnoses" section includes multiple sub-fields for recording diagnosis-related information, such as description, diagnosis ID, ICD codes, SNOMED code, and additional notes.
• Reviewed and Signed By: "reviewedandsignedby" indicates the user or entity who reviewed and signed the encounter record.
• Reviewed and Signed Date: "reviewedandsigneddate" records the date when the encounter record was reviewed and signed off.

The "Encounter" source object serves as a comprehensive repository for encounter-related information, facilitating accurate patient tracking, documentation of healthcare services, and communication among healthcare providers. Developers can leverage this source object to enhance encounter management within athena EHR, streamline workflows, and support clinical decision-making.

Mapping Table