Eyefinity APIs
2 APIs31 Endpoints1 Category
Categories
API Catalog(2 of 2)
Eyefinity EHR FHIR API
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.
4 endpointsEyefinity Optometry EHR FHIR API
Jentic publishes the only available OpenAPI specification for Eyefinity Optometry EHR FHIR API, keeping it validated and agent-ready. The API exposes the Eyefinity Optometry electronic health record over the FHIR R4 standard, covering Patient, Condition, Procedure, Observation, MedicationRequest, AllergyIntolerance, Immunization, CarePlan and additional resources commonly needed for clinical reads. It is targeted at integrators building patient-record viewers, care-coordination tools, and analytics on Eyefinity-powered optometry practices.
27 endpointsConnect Your Agent
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.