# Practice Fusion MCP connector

Connect Practice Fusion to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up encounters, conditions, allergies, care plans, immunizations and coverages, with each person signed in as themselves and every lookup logged.

Source: https://elaichi.ai/connectors/practicefusion/

## Facts

| | |
| --- | --- |
| Application | Practice Fusion |
| Category | CRM |
| AI tools | 48 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Practice Fusion is connected

- Summarize this week's encounters for Dr. Patel's panel
- List patients with open care plans and no encounter since March
- Which immunizations are recorded for patient Maria Lopez?

## Connect Practice Fusion in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Practice Fusion.
2. Optionally set Share with, then press Connect.
3. Supply your own Practice Fusion app, then approve. Practice Fusion needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Practice Fusion tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Practice Fusion MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Practice Fusion MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Practice Fusion MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Practice Fusion MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Practice Fusion MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Practice Fusion to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Practice Fusion tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Practice Fusion through Elaichi

### Catch up on a patient before the visit

Clinical. Pull a patient's conditions, allergy intolerances, immunizations and the last few encounters from Practice Fusion into one short summary before walking into the room.

### See who is on a patient's care team

Care coordination. Ask which care team members and goals are attached to a patient and which care plans are still open, without clicking through each tab in Practice Fusion.

### Check coverage before a claim goes out

Billing. Look up a patient's coverage details in Practice Fusion and match them against the encounter being billed so the claim is right the first time.

### Confirm where and when a patient was seen

Front desk. Find a patient's recent encounters and the location each one happened at when they call to ask about a visit.

### Review diagnostic reports across a panel

Quality. Ask for the diagnostic reports from a date range and list the results that still have no follow-up encounter in Practice Fusion.

### Produce a continuity of care document

Medical records. When a patient transfers, generate a CCD from their Practice Fusion document references and hand it to the receiving practice without rebuilding it by hand.

## Elaichi vs Zapier MCP vs Composio for Practice Fusion

All three can connect Practice Fusion to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Practice Fusion tools | Allow or restrict single Practice Fusion tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Practice Fusion call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Practice Fusion to Claude?

Connect Practice Fusion in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Practice Fusion requires an OAuth application registered inside Practice Fusion itself, so one person brings its client ID and secret into Elaichi once and signs in through the Practice Fusion sign-in screen. After that nobody else on the team has to generate a client ID or secret, they just sign in as themselves.

### Does Practice Fusion work with ChatGPT and Cursor as well as Claude?

Yes. Once Practice Fusion is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Practice Fusion once and every client picks it up.

### What can an AI agent actually do with my Practice Fusion data?

An agent connected to Practice Fusion can look up a patient's conditions, allergy intolerances, immunizations, care plans, care teams, goals, coverages, devices, encounters, diagnostic reports and locations, and it can generate a continuity of care document from a patient's document references. In practice that means asking for a pre-visit summary, a coverage check or a list of reports from last week and getting an answer from the live chart. Short, concrete asks such as a patient name and a date range work better than long sentences.

### Does connecting Practice Fusion give the AI access to every patient?

No. Every call into Practice Fusion runs under the account of the person who signed in, so an agent can only see the patients, encounters and reports that person can already see in Practice Fusion. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Practice Fusion already allows.

### Can my team share one Practice Fusion connection?

Yes. One person connects Practice Fusion in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret or any other credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Practice Fusion lookup.

### Can I stop an agent from deleting or changing things in Practice Fusion?

This Practice Fusion connector reads records and generates care documents, it does not edit or delete charts. Even so, you can restrict any individual action, such as generating a CCD or listing coverages, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it against Practice Fusion no matter what the prompt says.

### What happens to a Practice Fusion connection when someone leaves?

Offboarding a person in Elaichi ends their access to Practice Fusion through every client at once. If they were using a shared Practice Fusion connection, it keeps working for everyone else on the team. If you want Practice Fusion gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the Practice Fusion MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Practice Fusion is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Practice Fusion?

Yes. Both let Claude, ChatGPT or Cursor use Practice Fusion. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Practice Fusion call.

### How is Elaichi different from Composio for Practice Fusion?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Practice Fusion: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 48 Practice Fusion tools

Every tool below is callable through https://api.elaichi.ai/mcp once Practice Fusion is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Practice Fusion allergy intolerance by ID** (Get). Read one AllergyIntolerance by id (GET /AllergyIntolerance/{id}). AllergyIntolerance (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion allergy intolerances** (List). Search AllergyIntolerance (GET /AllergyIntolerance): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). AllergyIntolerance (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion care plan by ID** (Get). Read one CarePlan by id (GET /CarePlan/{id}). CarePlan (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion care plans** (List). Search CarePlan (GET /CarePlan): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). CarePlan (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion care team by ID** (Get). Read one CareTeam by id (GET /CareTeam/{id}). CareTeam (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion care teams** (List). Search CareTeam (GET /CareTeam): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). CareTeam (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion condition by ID** (Get). Read one Condition by id (GET /Condition/{id}). Condition (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion conditions** (List). Search Condition (GET /Condition): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Condition (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion coverage by ID** (Get). Read one Coverage by id (GET /Coverage/{id}). Coverage (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion coverages** (List). Search Coverage (GET /Coverage): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Coverage (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion device by ID** (Get). Read one Device by id (GET /Device/{id}). Device (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion devices** (List). Search Device (GET /Device): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Device (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion diagnostic report by ID** (Get). Read one DiagnosticReport by id (GET /DiagnosticReport/{id}). DiagnosticReport (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion diagnostic reports** (List). Search DiagnosticReport (GET /DiagnosticReport): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). DiagnosticReport (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion document reference by ID** (Get). Read one DocumentReference by id (GET /DocumentReference/{id}). DocumentReference (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion document references** (List). Search DocumentReference (GET /DocumentReference): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). DocumentReference (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Practice Fusion document references generate ccd** (Generate). Generate Continuity of Care Documents on demand (GET /DocumentReference/$docref): returns a Bundle of DocumentReference resources whose content.attachment.url links the CCD XML. They aren't stored and can't be read later. Existing CCDs (made when an encounter is signed): document_references.list with type=34133-9. Required: patient.
- **Get single Practice Fusion encounter by ID** (Get). Read one Encounter by id (GET /Encounter/{id}). Encounter (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion encounters** (List). Search Encounter (GET /Encounter): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Encounter (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion goal by ID** (Get). Read one Goal by id (GET /Goal/{id}). Goal (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion goals** (List). Search Goal (GET /Goal): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Goal (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion immunization by ID** (Get). Read one Immunization by id (GET /Immunization/{id}). Immunization (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion immunizations** (List). Search Immunization (GET /Immunization): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Immunization (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion location by ID** (Get). Read one Location by id (GET /Location/{id}). Location (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion locations** (List). Search Location (GET /Location): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Location (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion medication dispense by ID** (Get). Read one MedicationDispense by id (GET /MedicationDispense/{id}). MedicationDispense (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion medication dispenses** (List). Search MedicationDispense (GET /MedicationDispense): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). MedicationDispense (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion medication request by ID** (Get). Read one MedicationRequest by id (GET /MedicationRequest/{id}). MedicationRequest (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion medication requests** (List). Search MedicationRequest (GET /MedicationRequest): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). MedicationRequest (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion observation by ID** (Get). Read one Observation by id (GET /Observation/{id}). Observation (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion observations** (List). Search Observation (GET /Observation): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Observation (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion organization by ID** (Get). Read one Organization by id (GET /Organization/{id}). Organization (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion organizations** (List). Search Organization (GET /Organization): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Organization (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion patient by ID** (Get). Read one Patient by id (GET /Patient/{id}). Patient (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion patients** (List). Search Patient (GET /Patient): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Patient (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion practitioner by ID** (Get). Read one Practitioner by id (GET /Practitioner/{id}). Practitioner (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion practitioners** (List). Search Practitioner (GET /Practitioner): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Practitioner (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion procedure by ID** (Get). Read one Procedure by id (GET /Procedure/{id}). Procedure (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion procedures** (List). Search Procedure (GET /Procedure): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Procedure (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion provenance by ID** (Get). Read one Provenance by id (GET /Provenance/{id}). Provenance (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **Get single Practice Fusion related person by ID** (Get). Read one RelatedPerson by id (GET /RelatedPerson/{id}). RelatedPerson (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion related persons** (List). Search RelatedPerson (GET /RelatedPerson): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). RelatedPerson (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Practice Fusion server metadata** (Action). The FHIR server's CapabilityStatement (GET /metadata): supported resources, interactions, search parameters and the SMART OAuth URIs. Public.
- **Practice Fusion server smart configuration** (Action). The well-known SMART configuration (GET /.well-known/smart-configuration): authorize, token and introspection endpoints, capabilities and grant types. Public.
- **Get single Practice Fusion service request by ID** (Get). Read one ServiceRequest by id (GET /ServiceRequest/{id}). ServiceRequest (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion service requests** (List). Search ServiceRequest (GET /ServiceRequest): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). ServiceRequest (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
- **Get single Practice Fusion specimen by ID** (Get). Read one Specimen by id (GET /Specimen/{id}). Specimen (FHIR R4, US Core). Returns the FHIR resource. Practice Fusion: 404 when the id doesn't exist or isn't visible to the token. Required: id.
- **List all Practice Fusion specimens** (List). Search Specimen (GET /Specimen): returns the searchset Bundle's resources (entry[].resource; with _include / _revinclude the related resources are records too, tell them apart by resourceType). Specimen (FHIR R4, US Core). Filters are FHIR search parameters (repeat a key for AND, comma-separate values for OR). The connector follows the Bundle's next link (limit = page size, _count). With a provider (user) token most searches need patient; with a patient token, patient is the patient in the token.
