canonical: https://jentic.com/apis/swaggerhub.om-labs/bifrost-for-emr

# Om Labs Bifrost for EMR

This describes all the API methods to sync data between any EMR and Bifrost. The API exposes 4 endpoints.

## For AI agents

Programmatically access Bifrost for EMR resources. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Access Bifrost for EMR resources via REST API
- Manage developer tools data programmatically
- Integrate Bifrost for EMR into automated workflows
- Query and filter Bifrost for EMR records by parameters
- Monitor Bifrost for EMR operational status and events

## Use cases

### Developer Tools Operations

The API provides 4 endpoints for developer tools operations.

Example prompt: Execute a primary operation against the Bifrost for EMR

### Data Retrieval and Monitoring

Query Bifrost for EMR resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Bifrost for EMR endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Bifrost for EMR endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'bifrost for emr', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **results** — Methods to sync reports from Bifrost-powered diagnostic systems
- **patients** — Methods to sync patient information between Bifrost and EMR

## Why Jentic

- **Setup:** Wiring Bifrost for EMR by hand means pointing at its Azure host and calling the organization, patient, and results endpoints yourself. Through Jentic you install once, import Bifrost for EMR from the API Directory, store any connection detail once, and your agent calls it.
- **Permission scoping:** Bifrost for EMR carries its targets in the request body rather than the URL path, so scope your agent by the operations it needs, such as listing organizations or exporting results. You choose which operations it may call, so writes like adding a patient are not included unless you add them.
- **Credential handling:** Any Bifrost for EMR connection detail is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list EMR organizations' or 'export patient results', and Jentic returns the matching Bifrost for EMR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Bifrost for EMR use?

The Bifrost for EMR uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### What are the rate limits for the Bifrost for EMR?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I use bifrost for emr through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use bifrost for emr'. Jentic returns the matching Bifrost for EMR operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bifrost for EMR have?

The Bifrost for EMR exposes 4 endpoints covering results, patients operations.

### Does the Bifrost for EMR support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Bifrost for EMR API?

Yes. Because you run Jentic One yourself, you decide which Bifrost for EMR operations your agent may call and which connection details it may use. Since this API carries its targets in the request body rather than the URL path, you scope the agent to just the operations it needs, such as listing organizations or exporting patient results. Write operations like adding a patient are not available to the agent unless you explicitly include them.