canonical: https://jentic.com/apis/swaggerhub.advancedcomputersoft/docman-sci-gateway-api

# Advancedcomputersoft Docman SCI Gateway API

Integration between SCI Gateway and DM10. The API exposes 8 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get patients, get patient. Covers 8 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get Patients
- Add a Document Reference
- Update notes for a Document Reference
- Query and filter Docman SCI Gateway API records by parameters
- Monitor Docman SCI Gateway API operational status and events

## Use cases

### Developer Tools Operations

Use the Docman SCI Gateway API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including get patients, get patient, add a document reference.

Example prompt: Call GET /{tenantId}/Patient to get patients

### Automated DocumentReference Management

Automate documentreference operations by combining multiple Docman SCI Gateway API endpoints. Agents can get patient and then add a document reference in a single workflow.

Example prompt: Call GET /{tenantId}/Patient/{patientId} to get patient, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Docman SCI Gateway API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get patients', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /{tenantId}/Patient | Get Patients |
| GET | /{tenantId}/Patient/{patientId} | Get Patient |
| POST | /{tenantId}/DocumentReference | Add a Document Reference |
| GET | /{tenantId}/DocumentReference | Get Document References |
| GET | /{tenantId}/DocumentReference/{documentId} | Get Document Reference |
| PATCH | /{tenantId}/DocumentReference/{documentId} | Update notes for a Document Reference |
| POST | /{tenantId} | Get Many Responses for SCI Gateway |
| GET | /{tenantId}/ValueSet/national-folder-structure | Get Folder Structure |

## Key resources

- **DocumentReference** — Document Reference
- **Folder** — Folder Structure
- **Patient** — Patient

## Why Jentic

- **Setup:** Wiring the Docman SCI Gateway API by hand means setting up its OAuth2 flow, choosing among its SwaggerHub host variants, and threading the tenant id through each patient and document call yourself. Through Jentic you install once, import the Docman SCI Gateway API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** The SCI Gateway API puts the tenant id in the URL path (/{tenantId}/...), so a rule can pin your agent to one tenant for its patient and document-reference operations. You choose the operations it may call, so writes like patching a document reference are not included unless you add them.
- **Credential handling:** Your Docman SCI Gateway OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find patients for a tenant' or 'create a document reference', and Jentic returns the matching Docman SCI Gateway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Docman SCI Gateway API use?

The Docman SCI Gateway API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get patients with the Docman SCI Gateway API?

Yes. Use the GET /{tenantId}/Patient endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Docman SCI Gateway API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get patients through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get patients'. Jentic returns the matching Docman SCI Gateway API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Docman SCI Gateway API have?

The Docman SCI Gateway API exposes 8 endpoints covering documentreference, folder, patient operations.

### Can I limit what my agent is allowed to do with the Docman SCI Gateway API?

Yes. Jentic One is self-hosted, so your own rules decide which Docman SCI Gateway operations and credentials the agent may use. Because the tenant id lives in the URL path (/{tenantId}/...), you can pin the agent to a single tenant for its patient and document-reference calls, and you choose exactly which operations it may run. That means read-only work like GET /{tenantId}/Patient can be allowed while writes such as POST /{tenantId}/DocumentReference or PATCH /{tenantId}/DocumentReference/{documentId} stay off unless you add them.