Rawat Inap

rawatInap.update

Tenant-scoped tRPC mutation rawatInap.update. Requires a verified session cookie or an OAuth Bearer token; OAuth callers additionally need the simrs:write scope. Mutations are RBAC-gated server-side (requireRoles) — a broad scope never widens the user's roles.

Authorization

AuthorizationBearer <token>

OAuth 2.0 / OIDC issued by the API itself (better-auth oidcProvider). Dynamic client registration per RFC 7591 at /api/auth/oauth2/register.

In: header

Scope: simrs:write

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

id*string

Length1 <= length

bangsal?string

Length1 <= length

bed?string

Length1 <= length

dpjp?string

Length1 <= length

penjamin?string

Length1 <= length

status?string

Value in

"dirawat"
"rencana-pulang"
"pulang"

Response Body

`application/json`

curl -X POST "https://example.com/trpc/rawatInap.update" \  -H "Content-Type: application/json" \  -d '{    "id": "string"  }'

{  "result": {    "data": null  }}

{  "error": {    "message": "string",    "code": 0,    "data": {      "code": "string",      "httpStatus": 0,      "path": "string"    }  }}

{  "error": {    "message": "string",    "code": 0,    "data": {      "code": "string",      "httpStatus": 0,      "path": "string"    }  }}

{  "error": {    "message": "string",    "code": 0,    "data": {      "code": "string",      "httpStatus": 0,      "path": "string"    }  }}

{  "error": {    "message": "string",    "code": 0,    "data": {      "code": "string",      "httpStatus": 0,      "path": "string"    }  }}

Is this page helpful?

rawatInap.satusehatStatusGET

rawatJalan.listGET

rawatInap.update

Authorization

Request Body

Response Body

200application/json

400application/json

401application/json

403application/json

500application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`