EHR Central API

Does EHR Central have a public API?

EHR Central publishes no developer API, no FHIR endpoint and no integration documentation for its cloud EHR and practice management system; its site describes exchanging patient data with other systems only in general terms. Integuru generates a production-ready HTTP API from your EHR Central login, with 14 verified actions that cover the schedule, the chart, encounter documentation and coding.

The lack of a documented surface is the whole problem for a vendor selling into independent practices, because each practice is small and none of them will fund an interface. Integuru covers the platform with direct HTTP requests to the endpoints the EHR Central web app already uses, authenticated, using the practice's own credentials, with login and any second factor handled for you.

What you can do with the EHR Central API

A family practice provider finishes a visit and an AI scribe has the transcript. The visit needs an encounter, the history and exam sections, the codes and the plan, in that order. The actions map onto the order.

Find the patient and the visit

• search_patients takes a keyword (full name, partial name or fragments such as jam or Smith) and returns internal ids. get_patient_demographics reads one patient_id.
• get_appointments returns a date's schedule (YYYY-MM-DD); list_patient_encounters and get_encounter_summary read a patient's history and a single encounter.

Open the encounter

• create_encounter requires patient_id, provider_location_id, date, time (24-hour HH:MM) and mode (the visit mode or location type). Everything below takes the resulting encounter_id.

Write the history and exam

• save_encounter_notes fills the free-text fields: chief_complaint, hpi, past_medical_history, family_history, social_history, allergy_notes, vaccination and hospitalization_surgery_notes, plus hospitalizations and surgeries arrays that each create a record.
• save_review_of_systems applies a template_name such as General Female and a sections object keyed by snake_case system names; only included sections are saved.
• save_physical_examination applies one or more exam templates in a single save.

Code and plan

• search_icd_codes (by search_term) and search_cpt_codes (by keyword, including the encounter's favorites) both need 3 or more characters and an encounter_id. search_lab_procedures finds orders by lab type and keyword for a patient_id.
• add_encounter_codes attaches diagnosis_codes and internal CPT procedure_codes, with onset_date and performed_date defaulting to today.
• create_plan_of_care records short_term_goals and long_term_goals (omitted goals default to In-Progress) and a procedures array with code id, name and notes.

Who uses this

Ambient scribe vendors targeting independent practices push a structured note through save_encounter_notes, save_review_of_systems and save_physical_examination so the provider reviews and signs in EHR Central rather than pasting. Coding automation reads the encounter summary, resolves codes with the two search actions and commits them with add_encounter_codes. Practice operations tools pull get_appointments each morning to drive reminders and check-in. Vendors that support several independent-practice EHRs pair this page with the PrognoCIS, DrChrono and Practice Fusion integrations, and the healthcare industry page covers EHR writes across the stack.

Setup notes

Integuru authenticates against ehrcentral.com with your EHR Central user. Patient identifiers are internal system ids from search_patients, not the display MR number, and encounter identifiers come from create_encounter or list_patient_encounters. Both code searches are scoped to an encounter, so create or look up the encounter before coding. Dates are YYYY-MM-DD and encounter times are 24-hour HH:MM.

Get started

Install the CLI and connect your EHR Central login:

npm install -g integuru

Or sign in at app.integuru.com, add EHR Central, and call get_appointments for today. Prescriptions, lab order submission, billing and patient portal messages are built on request through the Managed Service.