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.

Can I limit what my agent is allowed to do with the PatientView API?

Yes. Because you run Jentic One yourself, your own rules decide which PatientView operations and credentials the agent may use. Since PatientView puts the user id in the URL path, such as GET /user/{userId}/observations/{code}, you can pin the agent to a single user and grant only read operations like querying observations and listing available observation headings. Write operations such as POST /user/{userId}/observations/{code}/patiententered stay off limits unless you explicitly add them.