Eyefinity EHR FHIR API
Browse all Eyefinity APIs★ Only Publicly Available OpenAPI DocumentHealthcareEhr Emroauth24 EndpointsREST
For Agents
Read patient demographics and clinical conditions from Encompass EHR through a FHIR R4 interface, with OAuth 2.0 authorisation against the Eyefinity authority server.
Use for: I need to look up a patient by demographics in Encompass EHR, Retrieve a single patient record by FHIR id, Search for a patient's documented conditions, Get the FHIR capability statement to confirm supported resources
Not supported: Does not handle billing, scheduling, or clinical writes — use for FHIR R4 reads of Patient and Condition resources from Encompass EHR only.
Jentic publishes the only available OpenAPI specification for Eyefinity EHR FHIR API, keeping it validated and agent-ready. The API exposes a slice of the Encompass EHR through the FHIR R4 standard, focusing on patient demographics, clinical conditions, and the FHIR capability statement endpoint. It is intended for integrators building patient-record reads against Encompass-powered optometry practices and complies with the ONC information-blocking interoperability requirements.
Install Jentic One Beta
Connect the Eyefinity EHR FHIR API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eyefinity EHR FHIR API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Eyefinity EHR FHIR API.
Search Patient resources by demographic parameters via GET /Patient
Retrieve a single Patient record by FHIR resource id via GET /Patient/{id}
Query Condition resources to access a patient's diagnoses and clinical conditions
Read the server's FHIR capability statement from /metadata to discover supported interactions
Authorise reads with OAuth 2.0 authorization-code flow against fhirauthority.eyefinity.com
Use Cases
Patterns agents use Eyefinity EHR FHIR API for, with concrete tasks.
★ Patient Demographic Lookup
Query Encompass-based optometry practices for patient demographic data through a standard FHIR R4 interface. Use GET /Patient with search parameters or GET /Patient/{id} when the FHIR id is already known. The OAuth 2.0 authorization-code flow at fhirauthority.eyefinity.com gates access and limits returned data to the scopes granted by the practice.
Call GET /Patient with family=Smith and birthdate=1985-04-12 to retrieve matching patient resources from the Encompass EHR.
Condition History Read
Retrieve the documented clinical conditions for an optometry patient by querying the FHIR Condition resource. Useful for downstream applications that need a patient's diagnoses to drive eligibility, referral, or care-coordination logic. The Condition endpoint returns FHIR R4 Condition resources scoped to the practice that authorised the access token.
Call GET /Condition?patient={patient_id} to fetch the Condition resources for the patient and summarise the active diagnoses.
Capability Discovery
Read the FHIR /metadata endpoint to discover which FHIR interactions and resources the Eyefinity EHR server supports before issuing real reads. The capability statement is the canonical way to confirm that Patient and Condition reads are exposed for a given deployment and to detect changes between releases.
Call GET /metadata and parse the rest.resource list to confirm Patient and Condition are exposed before issuing further reads.
Agent EHR Read via Jentic
An AI agent that helps optometry staff triage requests can use Jentic to discover and call Eyefinity EHR FHIR operations without hand-coding the FHIR client. Through Jentic the agent searches for the intent, loads the operation schema, and executes the call with an OAuth 2.0 token kept inside the Jentic vault rather than in the agent's context.
Through Jentic, search 'look up an Eyefinity EHR patient', load GET /Patient, and execute it with the family-name parameter for an inbound staff request.
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for eyefinity ehr fhir api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/Patient
Search Patient resources
GET
/Patient/{id}
Read a Patient by id
GET
/Condition
Search Condition resources
GET
/metadata
Read the FHIR capability statement
GET
/Patient
Search Patient resources
GET
/Patient/{id}
Read a Patient by id
GET
/Condition
Search Condition resources
GET
/metadata
Read the FHIR capability statement
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth 2.0 access tokens for fhirauthority.eyefinity.com are stored encrypted in the Jentic vault; the agent receives a scoped token at execution time and never sees the underlying client secret or refresh token.
Intent-based discovery
Agents express intents like 'look up an Eyefinity EHR patient' and Jentic returns matching /Patient or /Condition operations with their FHIR R4 input schemas, so the agent does not have to learn FHIR search semantics from the docs.
Time to first call
Direct integration: 1-3 days to wire OAuth 2.0, parse the capability statement, and handle FHIR bundle pagination. Through Jentic: under an hour to search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Eyefinity EHR FHIR API through Jentic.
Why is there no official OpenAPI spec for Eyefinity EHR FHIR API?
Eyefinity does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Eyefinity EHR FHIR API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Eyefinity EHR FHIR API use?
The spec declares OAuth 2.0 with the authorization-code flow against https://fhirauthority.eyefinity.com/core/connect/authorize and the token endpoint at https://fhirauthority.eyefinity.com/core/connect/token. Through Jentic, the access token lives in the vault and never enters the agent's prompt context.
Can I retrieve a patient's conditions with the Eyefinity EHR FHIR API?
Yes. Issue GET /Condition with a patient parameter to return FHIR R4 Condition resources scoped to that patient, provided the access token has been granted the necessary scope by the practice.
What FHIR resources does this API support?
The OpenAPI spec covers Patient (search and read by id) and Condition (search), plus the standard /metadata capability endpoint. Other FHIR resources commonly available in EHRs are not exposed in this spec — use the sister Eyefinity Optometry EHR FHIR API for a wider resource set.
How do I look up a patient through Jentic?
Run pip install jentic, search 'look up an Eyefinity EHR patient', load the GET /Patient operation, then execute with family-name and birth-date parameters. Jentic injects the OAuth 2.0 token from the vault when the call runs.
What are the rate limits for the Eyefinity EHR FHIR API?
The spec does not declare explicit rate limits; treat this as a clinical system and pace reads conservatively, honour any 429 responses with backoff, and avoid running unbounded patient searches during business hours.
GET STARTED