The Platform

History Key

  • New content
  • Removed content

Recent Versions

Choose two versions to compare, or click the link to view it.

  1. 4. almost 2 years by markcopenhaver
  2. 3. almost 2 years by markcopenhaver
  3. 2. almost 2 years by markcopenhaver
  4. 1. almost 2 years by markcopenhaver
 

You heard EncounterPRO-OS was an EHR?  Well yes it certainly is, but it's more than that.  EncounterPRO-OS was the first (and IMHO still the only) EHR built from the ground up as a platform for components rather than an application.

Let's start with some basic EncounterPRO-OS concepts...

Workflow Engine  The state machine at the heart of an EncounterPRO-OS installation which governs the behavior of EncounterPROEncounterPRO-OS.

Shell  An application which authenticates users and consults the workflow engine to present users with information about outstanding tasks.  The shell also offers users a way to perform the outstanding tasks (usually by clicking on one) and the shell will instantiate and call the component appropriate to that task.

Component Manager  A specific object in the EncounterPRO-OS shell which alone has the logic to instantiate a component.  All work is through a component, and all components are instantiated by the component manager.

Component   A callable applet that performs or allows a user to perform some function.

Config  The settings, rules and instructions that the Workflow Engine, Shell and Components use to govern the behavior of EncounterPRO-OS.  It is fair to say that EncounterPRO-OS by itself does nothing.  The Config informs EncounterPRO-OS how to react and respond to every event.