Install Jentic One Beta

Connect the Netsmart CareConnect FHIR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Netsmart CareConnect FHIR API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetsmartcloud.com%2Fnetsmart" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetsmartcloud.com%2Fnetsmart" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Netsmart CareConnect FHIR API.

Pull a patient's conditions, observations, and medication requests for care coordination

Look up encounters, procedures, and care plans on a specific patient id

Retrieve allergy intolerances before generating a clinical note

Search the payer-provider directory for practitioners and organisations

GET STARTED

Start building with Netsmart CareConnect FHIR API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Netsmart CareConnect FHIR API for, with concrete tasks.

★ Care Coordination Patient Pull

When a care manager opens a patient case, pull conditions, medications, observations, and recent encounters from Netsmart CareConnect to build a longitudinal view. The FHIR R4 endpoints return structured resources so the coordination platform can render the data without screen-scraping the EHR.

For tenant T-1 and patient PAT-123, fetch /Condition, /MedicationRequest, /Observation, and /Encounter and return a combined chronological summary.

Prior Authorisation Evidence Gathering

Before submitting a prior authorisation, gather the supporting clinical evidence - diagnoses, prior treatments, observations - directly from CareConnect's FHIR endpoints. Reduces the back-and-forth between payer and provider by attaching structured FHIR bundles to the auth request.

Fetch /Condition and /Observation for patient PAT-555 in the last 12 months and bundle them into a single FHIR document for a prior auth submission.

Payer Provider Directory Refresh

Payers can pull the practitioner and organisation directory from CareConnect's payer-provider-directory endpoints to keep their network rosters in sync. Supports the federal Payer-to-Payer Directory rule without manual file exchanges.

List all Practitioner and Organization resources in tenant T-1, return any that changed since the last sync timestamp.

AI Agent Clinical Q&A

Let an AI agent answer 'show me this patient's recent labs and diagnoses' through Jentic by querying CareConnect under SMART-on-FHIR scopes. The agent fetches only the resources the requesting clinician's scope allows, keeping PHI handling within the FHIR consent model.

Given clinician question 'what are this patient's active conditions and recent A1c?', call /Condition and /Observation filtered by code 4548-4 and return both.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for netsmart careconnect fhir api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/provider/patient-access/v2/{tenantId}/Patient/{id}

Read a Patient by id

GET

/provider/patient-access/v2/{tenantId}/Condition

Search Conditions

GET

/provider/patient-access/v2/{tenantId}/Observation

Search Observations

GET

/provider/patient-access/v2/{tenantId}/MedicationRequest

Search MedicationRequests

GET

/provider/patient-access/v2/{tenantId}/Encounter

Search Encounters

GET

/provider/system-access/v2/{tenantId}/Patient/$export

Bulk export Patient resources

GET

/payer/provider-directory/v2/{tenantId}/Practitioner

Search Practitioners in the provider directory

GET

/provider/patient-access/v2/{tenantId}/Patient/{id}

Read a Patient by id

GET

/provider/patient-access/v2/{tenantId}/Condition

Search Conditions

GET

/provider/patient-access/v2/{tenantId}/Observation

Search Observations

GET

/provider/patient-access/v2/{tenantId}/MedicationRequest

Search MedicationRequests

GET

/provider/patient-access/v2/{tenantId}/Encounter

Search Encounters

GET

/provider/system-access/v2/{tenantId}/Patient/$export

Bulk export Patient resources

GET

/payer/provider-directory/v2/{tenantId}/Practitioner

Search Practitioners in the provider directory

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Netsmart CareConnect FHIR API by hand means running its OAuth2 client-credentials or authorization-code flow, choosing between the fhir.netsmartcloud.com production host and the fhirtest sandbox, and threading the tenant id through every FHIR R4 read yourself. Through Jentic you install once, import CareConnect from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

CareConnect puts the tenant id and resource id in the URL path (/provider/patient-access/v2/{tenantId}/Patient/{id}), so a rule can pin your agent to one tenant and specific resources. You choose the operations it may call, so the system-access bulk $export is not included unless you add it.

Credential isolation

Your CareConnect OAuth client credentials are stored once, encrypted, by your own Jentic One instance and short-lived tokens scoped to the requested tenant are injected at execution time. The raw client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get patient conditions from Netsmart' or 'read a provider directory', and Jentic returns the matching FHIR operation with its parameter schema so the agent calls the right resource without browsing the reference docs.

FAQs

Specific to using Netsmart CareConnect FHIR API through Jentic.

Why is there no official OpenAPI spec for the Netsmart CareConnect FHIR API?

Netsmart documents CareConnect through a developer portal but does not publish a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the FHIR API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Netsmart CareConnect FHIR API use?

CareConnect uses OAuth 2.0 in two flavours: SMART-on-FHIR authorisation_code for user-context patient access, and OAuth 2.0 client_credentials for system-to-system bulk export. Through Jentic the client credentials are stored encrypted and exchanged for short-lived access tokens at execution time.

Can I pull a patient's conditions and medications through the Netsmart FHIR API?

Yes. GET /provider/patient-access/v2/{tenantId}/Condition and /MedicationRequest accept patient-id search parameters and return FHIR R4 bundles. Combine with Observation and Encounter for a full longitudinal view.

What are the rate limits for the Netsmart CareConnect FHIR API?

Netsmart enforces tenant-specific limits negotiated as part of your CareConnect contract. Bulk-export endpoints are designed for off-hours panel pulls; live patient-access endpoints are tuned for interactive clinician traffic.

How do I run a FHIR bulk export through Jentic?

Run jentic.search('netsmart fhir bulk export'), load the matching operation, and execute GET /provider/system-access/v2/{tenantId}/Patient/$export with your group or panel identifier. Jentic returns the operation handle the agent can poll for completion.

Does the Netsmart FHIR API support write operations?

This OpenAPI surface focuses on read access - Patient, Condition, Observation, and the provider-directory resources. Write-back into CareConnect goes through Netsmart's certified EHR write APIs which require additional onboarding.

Can I limit what my agent is allowed to do with the Netsmart CareConnect FHIR API?

Yes. Jentic One runs self-hosted, so your own rules decide which CareConnect operations and credentials the agent may use. Because the tenant id and resource id sit in the URL path, such as /provider/patient-access/v2/{tenantId}/Patient/{id}, you can pin the agent to a single tenant and to specific FHIR resources like Condition, Observation, or MedicationRequest. You also choose the operations it may call, so the system-access bulk $export stays out of reach unless you explicitly add it.

Netsmartcloud Netsmart CareConnect FHIR API

Name: Netsmart CareConnect FHIR API
Brand: Netsmart CareConnect FHIR API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticHealthcareEhr Emroauth216 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read FHIR R4 patient records, provider directory entries, and bulk-export jobs from Netsmart CareConnect EHRs.

Use for: Get all conditions for patient PAT-123, Retrieve a patient's active medication requests, Search the provider directory for psychiatrists in tenant T-1, List recent encounters for a patient

Not supported: Does not handle clinical write-back, e-prescribing, or claim submission - use for FHIR R4 read access to patient records and the provider directory only.

Jentic publishes the only available OpenAPI specification for Netsmart CareConnect FHIR API, keeping it validated and agent-ready. CareConnect is Netsmart's HL7 FHIR R4 surface for community and behavioural health EHRs, exposing patient access, provider directory, and bulk system-access endpoints required for US Cures Act and Payer-Provider Directory rules. Use it to pull longitudinal patient records - conditions, medications, observations, encounters - into care coordination, prior authorisation, and analytics workflows.

Jentic One on Github View OpenAPI Document