Glossary
Use this table to get familiar with commonly used terminology.
Terms | Description |
---|---|
EHR | An Electronic Health Record (EHR) is an electronic version of a patients health history. |
PMS | A Practice Management System (PMS) is software that helps a practice run day to day operations like scheduling and billing. It often includes EHR capabilities as well. |
Health Record System | A general term for an EHR or PMS that NexHealth can connect to. |
Integrated resource | An API resource that reads/writes data to/from the integrated system. |
Non-integrated resource | An API resource that does not read/write back to the integrated system. |
Operatory | An Operatory is a vertical column in scheduling software that represents the physical space where medical or dental procedures take place. It is often used interchangeably with "room," "chair," or "column." Note: Most dental scheduling software requires appointments to be assigned to both a provider and an operatory. A provider may work exclusively in one operatory or share it with others. Since scheduling practices vary by office, consult with your partner office before configuring operatory settings. |
Provider | Any staff member that provides dental or medical services. |
Institution | In NexHealth, an Institution refers to the office or group of offices your app connects to via the NexHealth Synchronizer. An Institution may have one or multiple syncs, depending on the health record systems used or the locations associated with it. All practice-based resources belong to an Institution. |
Sync | A sync refers to a location or a server computer where the Synchronizer API is actively reading the health record system. |
Multi-location | Multi-location practices are generally grouped under one Institution with multiple syncs corresponding to the multiple locations. |
Product key | A unique token created during installation that links the Synchronizer to the intended health record system. There is one product key per sync. |
Foreign id | The foreign_id is the record's ID in the third-party database. For example, in an Eaglesoft practice, a patient's foreign_id is their ID from the Eaglesoft database. |
Updated 10 days ago