Automate clinical and administrative processes in AndroHealth HIMS — map an event to a workflow so it launches automatically, lands in the right inbox, and feeds the patient's EMR.
AndroHealth lets you automate clinical and administrative processes with workflow triggers. By creating a workflow mapping, you tell the system to launch a predefined dynamic workflow automatically whenever a chosen event occurs — for example, when a patient bill is created or an EMR form is signed. The triggered workflow lands in the right user's Inbox with a notification, and any data captured flows straight into the patient's EMR.
A workflow trigger is a rule — a workflow mapping — that connects three things: a component (such as Billing or Patient Registration), an event on that component (such as Create or Sign), and the workflow to launch when the criteria are met. Once mapped, the system watches for that event and starts the workflow with no manual step.
Go to Admin Console → System Configurations → Workflow Mapping. The list screen shows every mapping you have configured.
When you pick a parameter, the system shows a Parameter Value list scoped to the selected component — so a Billing mapping lists the services shown on the billing screen.
Workflow mapping currently supports these components and events:
When the configured criteria are met, the system triggers the associated workflow, sends a notification to the targeted position, and places the workflow in that user's Inbox. The workflow automatically carries the patient banner data from the component it was triggered from.
The assigned user opens the workflow from the Inbox and clicks Continue to move into the workflow screens, enters the required information, and clicks Next (for multi-form workflows) or Finish.
Once the workflow is finished, the data it captured becomes part of the EMR for the associated visit and appears in the visit summary (including the printed summary from the encounter list).
Click Edit against any mapping to open the Edit Workflow Mapping screen. You can change the mapping or mark it inactive from a chosen date, after which it stops triggering.
Good to know: The system prevents duplicate active mappings — if the same combination already exists, you'll see "Workflow Mapping Already exists."
A mapping of a component and event to a workflow that launches automatically when the criteria are met.
In the targeted user's Inbox, along with a notification.
Yes — clinical workflow data becomes part of the associated visit's EMR.
Was this article helpful?