Description of enterprise contexts
The purpose of athenaEnterprise is to create a method of dividing components of a medical practice for various operational and financial reasons. athenaEnterprise introduces a new layer of complexity in the athenaNet practice that differentiates these components. That layer is called the "provider group." Multiple provider groups can exist for a practice to separate departments such as behavioral health, outpatient clinics and emergency medicine to name a few. It also helps maintain patient privacy or fiscal boundaries for patients.
Enterprise Patient ID versus Patient ID
Patients in each of these departments will have a specific department ID where their patient chart can be accesssed. For this reason, we require the departmentID to be passed into many API calls to access the correct patient information. For a given enterprise context, there may be a set of enterprise ID's given to patients as a single searchable chart for the patient. Enterprise ID's contain all charts for a patient across the entire athenanet practice. When searching for an enterprise ID in athenanet UI, you have the ability to select which of the provider group charts you want to view (so long as you have the correct permissions to do so). The enterprise ID is the default chart for the patient at the practice.
Our APIs support searching for patients by both enterprise ID or department specific ID. We recommend searching using enterprise ID's first, and then subsequent department specific ID's if their information is necessary. We try to return the correct information for patients based on their enterprise IDs. There are a handful of fields (like the current department) that are not routinely synced between sets of departments which requires passing the department ID into the API. Any API calls that return a patientID field return the enterprise ID for that patient.