PrognoCIS API

Does PrognoCIS have a public API?

PrognoCIS offers custom API integrations arranged practice by practice, plus interfaces for labs, radiology, clearinghouses and health information exchange, but no self-serve developer API and no public documentation. Integuru generates a production-ready HTTP API from your PrognoCIS login, with 6 verified actions that read the day sheet and the chart and write the encounter.

A per-practice integration project is a reasonable path for a health system with a year to spend. An AI scribe vendor that signed a pain management group last week has a different timeline. Integuru covers that case with direct HTTP requests to the endpoints the PrognoCIS 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 PrognoCIS API

In an occupational medicine clinic the injured workers arrive in a steady line, and each visit needs a chief complaint, an HPI, a review of systems, an exam, an assessment with ICD-10 codes and an E/M level, and the encounter has to be open in PrognoCIS while all of it lands. The six actions follow that visit in order.

Start from the day sheet and the chart

• list_appointments returns every appointment for the authenticated provider on a date (YYYY-MM-DD).
• patient_face_sheet and patient_last_visit_note take a chart_number (as shown in PrognoCIS patient search) or an internal patient_id, which skips the chart-number lookup. Together they give a scribe the context it needs before the encounter starts.

Write the note into the open encounter

• write_encounter_notes takes a chart_number and overwrites hpi_note, ros_note and physical_exam_note on the current open encounter. If no complaint exists, chief_complaint is matched to the master list or created; when omitted, the first line of hpi_note is used.
• save_assessment applies assessment_text and plan_text to the primary diagnosis and adds the ICD-10 diagnoses array without removing anything already coded.
• set_em_code writes an em_code from the Office Visit matrix (99211 through 99215) and returns the valid codes if yours is not available for that encounter.

Who uses this

Ambient documentation vendors serving pain management, occupational medicine and urgent care groups map a finished transcript onto write_encounter_notes and save_assessment so the provider signs rather than types. Coding assistants read the completed note, propose the E/M level and call set_em_code, using the returned list of valid codes as their guardrail. Front-office tools pull list_appointments per provider each morning to drive check-in and reminders. Groups that run another ambulatory EHR at some sites pair this page with the eClinicalWorks and NextGen integrations; the EHR Central page covers a similar independent-practice workflow. The healthcare industry page puts EHR writes in the context of the whole clinical stack.

Setup notes

Integuru authenticates against your practice's subdomain of prognocis.com (the verified account uses the advancedspecialtycare prefix) with a PrognoCIS provider or staff user. list_appointments is scoped to the authenticated provider, so a group needs one connection per provider or a login with visibility across the schedule. Every write is keyed on chart_number and lands in the patient's current open encounter; the three note fields overwrite existing text, while diagnoses on save_assessment are additive. Dates are YYYY-MM-DD.

Get started

Install the CLI and connect your PrognoCIS login:

npm install -g integuru

Or sign in at app.integuru.com, add PrognoCIS, and call list_appointments for today. Orders, prescriptions, charge capture beyond the E/M code and patient demographics are built on request through the Managed Service.