dualpath
Request a demo
Tasy Integration

Connect your routines to Tasy

dualpath develops solutions integrated with Bionexo Tasy for tasks across patient service, medical care, billing and hospital operations. Each product serves a specific flow — from looking up clinical information to recording the steps of a journey.

Integration has to make sense in the routine

Looking up a prescription is not the same as opening an encounter. That's why you should assess the integration by what each product reads, displays and records, the permissions it needs and the process your team has to carry out.

Bionexo Tasy

What each solution connects

Documented flow of each product in the portfolio.

What to assess with your IT team

To define the scope, consider the Tasy version and modules, the data the flow needs, the read and write points, permissions and external dependencies. The assessment should also clarify staging/approval, failure handling and operational responsibilities.

Frequently asked questions

Frequently asked questions

Does the integration only look up information?

No. It depends on the product. EasyBot Paciente includes self-registration in Tasy; EasyAtend includes opening the encounter; EasyAut plans to record authorization responses as part of its evolving scope. Each flow should be assessed separately.

Do I need to contract all nine products?

The solutions address different routines. Tell us which process you want to cover so we can discuss the right scope.

Does dualpath replace Tasy?

The portfolio presented consists of solutions integrated with Tasy, not a replacement for the hospital system.

Will the integration work at my institution?

Your environment's compatibility and the required scope need to be assessed. Tell us the product you are interested in and, if you know it, your Tasy version — without sending credentials or patient data.

Tasy Integration

Let's start with your process

Explain the routine you want to connect. The conversation can involve user areas and IT from the start.