canonical: https://jentic.com/apis/csso.cl/csso

# Csso Cl SIC API

The SIC API reports hospital events into the Salud Ness SIC system, keeping patient and facility records in sync with an external source. It records patient admissions and updates, a patient's diet regimen, and a patient's bed or location change, each tied to an episode. It also logs operational events: staff dining-room entry, cleaning requests triggered by an admission or bed move, parking access for a vehicle plate, and staff entry and exit. Every call uses HTTP Basic authentication against the SIC integration host.

## For AI agents

Report hospital events into the Salud Ness SIC system: patient admissions and updates, diet regimens, bed moves, cleaning requests, parking access, and staff entry and exit.

## Scope

Does not handle clinical charting, lab results, or billing. Use for reporting patient and facility events into the Salud Ness SIC system only.

## Capabilities

- Report a patient admission or update by episode
- Record a patient's diet regimen
- Report a patient's bed or location change
- Request a cleaning service for an admission or bed move
- Register parking entry and exit for a vehicle plate
- Log staff entry and exit

## Use cases

### Agent-driven patient event sync

An AI agent connected through Jentic forwards patient events from a source system into SIC, reporting an admission, then the patient's diet regimen, then any bed move. Each event is tied to the patient's episode, so SIC keeps a consistent patient record without a human re-keying it.

Example prompt: Report a patient admission, then record the patient's diet regimen for the same episode

### Facility services triggers

When a patient is admitted or moved, a workflow requests a cleaning service for the affected location so housekeeping is notified automatically. The SIC API exposes a dedicated cleaning-request operation triggered by admission or bed-move context.

Example prompt: Submit a cleaning request for a patient location after reporting a bed move

### Access and staffing logs

An integration logs parking access for vehicle plates and staff entry and exit into SIC, giving the hospital a single record of who and what entered. The parking and staffing operations accept entry and exit events so access data flows into the same system as patient events.

Example prompt: Register a parking entry for a vehicle plate and log a staff member's entry

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/alimentacionPacientes/pacient` | Report a patient admission or update |
| PUT | `/alimentacionPacientes/pacient/{numepisodio}` | Update a patient by episode |
| POST | `/alimentacionPacientes/pacientDiet` | Record a patient's diet regimen |
| POST | `/alimentacionPacientes/pacientLocation` | Report a patient bed or location change |
| POST | `/aseo/request` | Request a cleaning service |
| POST | `/estacionamiento/entry` | Register parking entry for a vehicle plate |

## Key resources

- **Patients** — Report patient admissions and updates, diet regimens, and bed or location changes
- **Cleaning** — Request a cleaning service for an admission or bed move
- **Parking** — Register parking entry and exit for a vehicle plate
- **Staffing** — Log staff dining-room entry and staff entry and exit

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 40 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/csso.cl/csso/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the SIC API by hand means handling HTTP Basic credentials against the SIC integration host and mapping your source events to its patient, cleaning, parking, and staffing operations. Through Jentic you install once, import SIC from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** SIC groups its operations by event type, and rules bound which operations your agent may call. You choose the operations it may call, so it can report patient admissions and diets without being able to log parking or staff events unless you add those.
- **Credential handling:** Your SIC 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 'report a patient admission' or 'request a cleaning service', and Jentic returns the matching SIC operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **DrChrono** — DrChrono is a full EHR and practice-management API, where SIC reports events into one hospital system.
- **athenahealth** — athenahealth exposes clinical and administrative records for care organizations.
- **1up Health** — 1up Health aggregates patient health data across providers via FHIR.

## FAQ

### What authentication does the SIC API use?

The SIC API uses HTTP Basic authentication against the SIC integration host, per its OpenAPI spec. Through Jentic the credentials are stored once by your own self-hosted instance and injected when a call runs, so they never appear in the agent's prompt or logs.

### Can I report a patient admission with the SIC API?

Yes. Use the patient operation to report an admission or update, and the diet and location operations to record a diet regimen or a bed move. Updates to an existing patient are made by episode through the patient update operation.

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

Yes. Write a rule that allows only the event operations the agent needs, such as patient admission and diet, so it cannot report parking or staff events, and every call it makes is logged. Add other operations only when the integration requires them.

### What are the rate limits for the SIC API?

The OpenAPI spec does not specify rate limits. Check the Salud Ness SIC integration documentation for current limits before sending high volumes of patient or facility events.

### Is there a SIC MCP server?

You don't need an MCP server to give your agent the SIC API. Jentic connects it directly from the API Directory: import it, store the credentials once, and your agent calls the patient and facility operations on demand without loading another server's tool definitions into its context.

### How do I report a patient event with the SIC API through Jentic?

Search Jentic by intent such as 'report a patient admission', and Jentic returns the patient operation with its input schema so your agent fills in the patient and episode details. To run it on your own infrastructure, install Jentic One from its GitHub repo.