PatientView

Name: PatientView API
Brand: PatientView
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareEhr EmrapiKey15 EndpointsREST

For Agents

Manage patient portal sessions, record clinical observations, retrieve patient demographics, and administer patient group registrations for healthcare organizations.

Connect the PatientView to your agent

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

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 PatientView API.

Authenticate users and manage secure session tokens for API access

Query clinical observations by standardized code for individual patients

Record patient-entered health measurements such as vitals and lab values

Retrieve patient demographic data and group membership information

GET STARTED

Start building with PatientView API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for PatientView, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for PatientView, keeping it validated and agent-ready. PatientView exposes REST API endpoints for patient portal integration, enabling authentication, patient record access, clinical observation management, and patient administration. The API provides 15 endpoints for managing user sessions, recording health observations like blood pressure and weight, retrieving patient demographics, and administering patient group memberships across healthcare organizations.

Use Cases

Patterns agents use PatientView API for, with concrete tasks.

★ Patient Health Self-Reporting

Enable patients to submit their own health measurements through the PatientView API. The patient-entered observation endpoints accept values for configured clinical codes such as blood pressure, weight, and blood glucose. These self-reported values integrate into the patient's clinical timeline alongside clinician-recorded data.

Record a weight observation of 72.5 kg for user ID 12345 via POST /user/{userId}/observations/{code}/patiententered with code 'weight'

Clinical Data Integration

Retrieve patient observation data from PatientView to integrate with external clinical systems or dashboards. The observation endpoints return time-series health data by clinical code, enabling trending, alerting, and cross-system data synchronization for healthcare IT platforms.

Retrieve all blood pressure observations for user 12345 via GET /user/{userId}/observations/bloodpressure and return the latest 5 readings with dates

Multi-Site Patient Registration

Administer patient identifiers and group associations for healthcare organizations operating across multiple sites. The patient management endpoints validate identifier data and create associations between patients and organizational groups, supporting complex multi-facility patient identity management.

Validate patient data for user 12345 in group 'HOSP01' via GET /patientmanagement/validate, then register the identifier via POST /patientmanagement/{userId}/group/{groupId}/identifier/{identifierId}

AI Agent Patient Portal Access

AI agents access PatientView endpoints through Jentic to automate patient data retrieval and observation recording without managing session token lifecycle. Agents search for healthcare operations and receive structured schemas with authentication handled by the Jentic credential vault.

Search Jentic for 'record a patient observation', load the schema for POST /user/{userId}/observations/{code}/patiententered, and execute with user ID, code, and value

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for patientview, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/login

Authenticate and get session token

GET

/patient/{userId}/basic

Retrieve patient demographics

GET

/user/{userId}/observations/{code}

Query observations by code

POST

/user/{userId}/observations/{code}/patiententered

Submit patient-entered observation

GET

/user/{userId}/availableobservationheadings

List observation types for user

GET

/user/{userId}/patiententeredobservationheadings

List patient-enterable observation types

POST

/auth/login

Authenticate and get session token

GET

/patient/{userId}/basic

Retrieve patient demographics

GET

/user/{userId}/observations/{code}

Query observations by code

POST

/user/{userId}/observations/{code}/patiententered

Submit patient-entered observation

GET

/user/{userId}/availableobservationheadings

List observation types for user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PatientView session tokens are stored encrypted in the Jentic vault. Agents authenticate through Jentic and receive automatic token injection without handling login credentials directly.

Intent-based discovery

Agents search by intent (e.g., 'submit a patient health observation') and Jentic returns the matching PatientView operation with parameter schemas and auth requirements.

Time to first call

Direct PatientView integration: 1-2 days for session management, code discovery, and observation recording flows. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PatientView

Primary slug for the same PatientView API surface

Both slugs cover identical PatientView endpoints. Use main as the primary reference.

Complementary

drchrono API

Full EHR with clinical workflows, prescriptions, and scheduling

Use drchrono for comprehensive clinical operations. Use PatientView for patient-facing portal access and self-reported observations.

Alternative

athenahealth API

Enterprise healthcare platform with records and billing

Use athenahealth for a broader healthcare platform including billing. Use PatientView for focused patient portal and observation management.

FAQs

Specific to using PatientView API through Jentic.

Why is there no official OpenAPI spec for PatientView?

PatientView does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PatientView via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does PatientView use?

PatientView uses token-based session authentication. Clients authenticate via POST /auth/login with credentials and receive a token used in subsequent requests. Sessions are terminated via POST /auth/logout/{token}. Jentic manages the token lifecycle in its credential vault so agents do not handle raw login credentials.

Can patients submit their own health observations?

Yes. The POST /user/{userId}/observations/{code}/patiententered endpoint accepts patient-entered values for any observation code configured for that user. Available codes can be discovered via GET /user/{userId}/patiententeredobservationheadings which returns the list of headings patients are allowed to self-report.

What observation types are supported?

Available observation types are configured per user and retrieved via GET /user/{userId}/availableobservationheadings. Common types include blood pressure, weight, and blood glucose. The specific headings available depend on the patient's clinical group and condition.

How do I retrieve patient observations through Jentic?

Search Jentic for 'get patient clinical observations by code', load the operation schema for GET /user/{userId}/observations/{code}, and execute with the user ID and observation code. Jentic injects the session token automatically. Install with pip install jentic.

Does PatientView support multi-group patient management?

Yes. The /patientmanagement endpoints manage patient identifiers within specific healthcare groups. Patients can be associated with multiple groups, and the /patientmanagement/validate endpoint checks data validity before creating associations. Surgery records can also be managed per group context.