Phreesia API

Overview

Phreesia is a patient intake and engagement platform used by medical practices and health systems across the United States. The platform manages the pre-visit workflow for millions of patient appointments each year, handling digital intake forms, insurance verification, medical history collection, consent signatures, and patient payment collection at the point of care. Phreesia is deployed across a wide range of specialties and practice sizes, from single-provider ambulatory practices to multi-site health systems, and its payment collection and eligibility verification capabilities make it a platform that touches both the clinical and financial sides of the patient visit.

The API access barrier is a formal partner program with no self-serve path. Phreesia's API for intake form data, patient scheduling status, and payment collection information requires partner enrollment. Development teams must apply to the program, satisfy Phreesia's technical and business requirements, and receive partner credentials before a single API call is possible. The partner program review is not self-serve and has no published timeline, and the data it gates is precisely the data that AI patient-access tools, care navigation platforms, and patient financial engagement products need to function. An AI intake assistant that cannot read current intake form responses or write completed forms back to Phreesia is not useful in a Phreesia-deployed practice environment.

Integuru generates a production-ready HTTP API for Phreesia using direct HTTP requests against the same endpoints Phreesia's own web platform uses internally. Intake form retrieval and submission, patient balance and payment collection, appointment intake status, patient demographics, and eligibility verification are all reachable through Integuru's API without a partner enrollment dependency. The Production plan's 24/7 on-call maintenance team handles session management, re-authentication, and endpoint changes before they affect your production calls. Integuru can be deployed in HIPAA-compliant environments; discuss your compliance requirements when you chat with us.

---

Why Teams Need This Integration

Phreesia's deployment in health system and specialty practice settings means that a patient-facing healthtech product operating in those environments will encounter Phreesia as the intake layer. The partner program gates the specific data flows those products need most.

AI patient intake and pre-visit automation. AI tools that help patients complete intake forms before their visit, surface relevant medical history, or flag incomplete information for the front desk need get_patient_intake_form, submit_intake_response, and get_appointment_intake_status as live API calls. A tool that cannot read the current form configuration or write completed responses back to Phreesia has no alternative other than manual data entry or a screenshot-based workaround, neither of which survives production use in a busy practice.

Patient financial engagement and payment collection tools. Patient financial counseling platforms and payment collection tools need get_patient_balance and post_patient_payment to surface outstanding balances and record payments through Phreesia's payment workflow. Phreesia's integration with front-desk payment collection means that a financial engagement product that cannot interact with Phreesia's payment module cannot serve the practices where Phreesia is the collection point of first contact.

Care coordination and patient navigation platforms. Care navigation tools that track whether a patient has completed intake, verified insurance, and provided the demographic information needed for the visit use list_scheduled_patients and get_appointment_intake_status to monitor completion status across the practice's upcoming appointments. For a care navigation platform that serves Phreesia-deployed practices, intake completion data is the signal that triggers outreach when a patient has not finished the pre-visit workflow.

Eligibility verification integrated into the intake workflow. Phreesia performs eligibility verification as part of the intake process, and check_eligibility and get_eligibility_response expose this verification as API calls that external scheduling and access tools can trigger before the patient arrives. For a patient access platform that needs to confirm coverage before completing a booking, Phreesia's integrated eligibility data is the right source in a Phreesia-deployed practice environment.

---

RCM Workflows This Integration Covers

The ten planned actions span the patient intake, payment, and eligibility workflows that Phreesia manages in the pre-visit and point-of-care setting:

• Intake form management: get_patient_intake_form retrieves the form configuration for a scheduled patient. submit_intake_response pushes completed intake data including demographics, insurance information, medical history, and consent signatures. list_intake_forms returns the form templates configured for a practice.
• Appointment and intake status: list_scheduled_patients returns upcoming appointments with intake completion and payment status. get_appointment_intake_status retrieves the completion percentage and outstanding items for a specific appointment.
• Patient demographics: update_patient_demographics updates patient demographic information from an external source or care coordination platform.
• Patient financial data: get_patient_balance retrieves the outstanding balance and copay amount for a scheduled appointment. post_patient_payment records a payment collected through the Phreesia payment workflow.
• Eligibility verification: check_eligibility submits a real-time eligibility inquiry through Phreesia's payer connections. get_eligibility_response returns coverage details, copay amounts, and deductible balances for the patient's active plan.

---

Adjacent Integrations

Integuru already covers several of the EHR platforms that Phreesia is deployed alongside in medical practice and health system environments. The athenahealth integration guide addresses the MDP partner program barrier for one of the most common EHR systems used in conjunction with Phreesia, with eleven planned actions spanning patient records, appointments, clinical notes, and billing data. The AdvancedMD integration guide covers the partner enrollment gap for practices on that platform. The DrChrono integration provides 4 live actions in production including patient creation, patient listing, medication records, and allergy data.