---
title: "EHR vendors"
description: "What EHR vendors are, which EHR systems Leyr supports, and the services available for each integration."
canonical_url: "http://localhost/product/fundamentals/ehr-vendors"
---
# EHR vendors

> What EHR vendors are, which EHR systems Leyr supports, and the services available for each integration.

## What is an EHR?

EHR (Electronic Health Record) is electronically stored digital representation of patients data.

In Leyr's context we think of EHRs (and especially, EHR **vendors**) as companies, providing infrastructure to healthcare organization (e.g. systems where practitioners work or databases where they store the patients' data).

Different healthcare organisations often use different EHRs. To give you a couple of examples:

- Karolinska University Hospital in Sweden uses TakeCare EHR, owned by CGM
- Mayo Clinic in the USA uses Epic EHR

This means, traditionally, you would have to build two separate integrations: One towards the TakeCare API, and one towards Epic's API. The APIs will differ in what they call things, and how requests are made, so count on some duplicate work if you do it the old-school way.

However, with Leyr, you can pretty much enjoy a single integration with both of them 😉

## Which EHRs are supported by Leyr?

EHR vendors, currently supported by Leyr.

<u-alert color="primary" variant="subtle">
<template v-slot:description="">

`Leyr Code` from the table below is used as a parameter to make calls to EHRs via our APIs - see examples at endpoints documentation, listed at [API reference](http://localhost/api) space.

</template>
</u-alert>

<ehr-vendors>



</ehr-vendors>

## Supported Services

<supported-services>



</supported-services>

<callout color="success" icon="i-lucide-check">

Functionality is fully supported.

</callout>

<callout color="primary" icon="i-lucide-help-circle">

Not yet available - reach out to us [over email](mailto:contact@leyr.ai) or through your Slack channel to discuss adding this functionality for your use case!

</callout>


## Sitemap

See the full [sitemap](http://localhost/sitemap.md) for all pages.