About Integrations

You may choose to integrate Ovation with other systems to more fully streamline your lab operations. For example, common integrations can

  • automate order creation
  • incorporate external results analysis
  • initiate billing
  • deliver test results to an EHR or patient portal
  • implement “send out” workflows.

Most integration objectives can be satisfied by writing custom code that calls our REST API or that is itself called by our webhooks. See the articles here and here for more information on this approach to system integration.

Depending on your objectives, you may also be able to use one of Ovation’s supported integrations. Most of these integrations directly integrate Ovation with a particular system, such as AdvancedMD for billing or Arkstone for reporting, to meet a specific need. We call these “native” integrations.

Ovation also offers a general, flexible capability to exchange files, often HL7® messages, through an SFTP host to achieve a variety of ends. When an API/webhook integration is impractical and a native integration doesn’t meet your needs, a file exchange integration is often the answer.

Integrations Home Page

Functionality to create, modify and monitor integrations is available at More > Lab > Integrations. This Integrations home page lists all integrations that have been created in your instance. If you do not yet have any integrations, you will instead see the Gallery of available integrations, from which you can choose your first one.

Once you have at least one integration, you can always add another one by returning to the Gallery (and then choosing Add Integration) and selecting the integration you want to add.

The table on the Integrations home page includes some summary information about each integration you have. You can click on the name of the integration to review or modify its configuration and monitor its operation.

Table Column Usage
Name The name you’ve given this integration; click here to view and modify it
Type The type of integration: Native or Generic.
Status The integration’s status: Enabled or Disabled. See here for more information about enabling and disabling integrations.
Health* The integration’s health: Healthy, Unhealthy or Unknown. An integration is considered unhealthy if any of the last ten events failed. Unknown status indicates an integration type that does not support this feature.
Last Event* When the last event for this integration was attempted, whether inbound or outbound
Event Log* Choose this icon to review events for that integration in its Event Log.
[...] Select the ellipsis and then select Delete to remove this integration

* Some native integrations do not support these fields.

Configuring Native Integrations

If you want to implement one of Ovation’s native integrations, please submit a change request here.


HL7® is a registered trademark of Health Level Seven International and our use of these trademarks does not constitute an endorsement by HL7.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.