Glossary

Refer to the below table to get familiar with the commonly used terminologies throughout the API documentation.

Terms	Description
EHR	An Electronic Health Record (EHR) is an electronic version of a patients medical history.
PMS	A Practice Management Software is software that helps a practice run day to day operations like scheduling and billing. It often includes EHR like 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	Operatory is a term for the vertical columns in scheduling software and represents the physical space where a medical or dental procedure takes place. The term is often interchangeable with 'room', 'chair' or 'column'. NB: Most scheduling softwares require all appointments to be assigned to a provider and operatory. A provider might work exclusively out of one operatory or they may share it with other providers. Office scheduling practices will vary greatly so be sure to consult with your partner office before configuring operatory settings for appointment availability.
Provider	Any staff member that can provide services.
Institution	Institution is a term used by NexHealth to describe the office or group of offices that you are connecting your app with via the NexHealth Synchronizer. An Institution could have one sync or many syncs depending on the health record systems used or locations corresponding to that Institution. All practice based resources are members of an institution.
Sync	A sync can refer 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 id of the record in the third party database. For example, the `foreign_id` of a patient of an Eaglesoft practice is the patient's id from within the Eaglesoft database.