A trigger kicks off a workflow. Example: You want to create a patient record in your EHR when a patient completes a step in your sign up flow. The trigger event in this case is "step completed."
An action is what should happen when the trigger event occurs. In the example from above the action is “create a patient record” in your EHR.
You select triggers, then you select actions, we connect the dots.
.svg)
.png)
Morf takes the complexity out of automations by managing and matching patient identities across your third party tools for you.
When data is sent to Morf via a trigger event, Morf automatically looks up and finds the matching patient profile to perform the action in your destination application.
Any event or data processed for a patient is associated to a single profile. This enables Morf to create a holistic, unified view of your patients’ data and activity.
Example: a patient schedules a visit in Acuity and fills out a form in Formsort. View those appointments and form responses from a single dashboard or access them via an API to build personalized applications.
As you grow and evolve, chances are you’ll want to experiment with new tools that better serve your needs. Morf allows you to easily swap out vendors and migrate your data — no coding required.
Morf also makes your data FHIR compatible and thus future-proofed for interoperability.
If / when a destination application has an outage and your actions are unsuccessful, Morf makes it easy to recover by reprocessing your events and re-triggering your actions.
Or if you’re adding a new destination, Morf can backfill that destination application with your existing data.
