Observation codes are used for tracking various data within individual charts, and can be used across device and system interfaces, as well as within observation flowsheets and questionnaires. With the product's observation codes editor, superusers can configure and customize the data values (which we call observations) that are needed to be used collected within portal flowsheets, encounter section flowsheets, or even for data capture of test results by end users. Observations have to exist first, in order to configure a flowsheet to be utilized by end-users.
Our product does this through a highly configurable, easily manageable observation code editor. Observations are used throughout the product, such as in Vitals data collection or for example in a portal questionnaire. Observations are the specific data points or values that a user can key information into and the system stores each as discrete reportable data. Observations used for specific lab result values or even patient questionnaires as a way to get the data in quickly in a flowsheet type method based on observation data fields. Observations are also used in the observation chart tab, observations are used in encounters, and flowsheets are used to capture discrete data value results, and various other functionality such as the applicant and/or patient portal.

Observation Code configuration requires security permission to access.

The Observation Codes Editor is a useful tool for adding, editing, viewing, merging, and deleting observation codes used within the system. Out of the box, the system is equipped with an extensive list of standard observation codes relevant to varying care settings, and these codes can be managed, updated and defined, as needed. If you are needing information on Flowsheets (which are built upon individual observations in the system), there is a separate course on that, regarding Flowsheets.