Frontend module · STATIC DECLARATIONS

Utils client API reference · mansoq-hmis-web

3 client route/call declarations with path parameters, named payload/response types and source references. Exact server acceptance and permissions require the matched backend contract.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Client contract scope

These 3 declarations come from repositories/teleicu/mansoq-hmis-web/src/pages/Encounters/utils/utils.tsx. Client types and noAuth flags describe the caller; they do not authorize a server action. Dynamic paths and missing backend matches are retained as review work, not repaired into invented endpoints.

Operation map

Client method	HTTP method	Path pattern	Resolution
endEncounter	UNRESOLVED	`unresolved dynamic path`	computed expression; route resolution review pending
endEncounter	UNRESOLVED	`unresolved dynamic path`	computed expression; route resolution review pending
endEncounter	UNRESOLVED	`unresolved dynamic path`	computed expression; route resolution review pending

endEncounter

UNRESOLVED unresolved dynamic path. HTTP option object; client/server ownership review pending; computed expression; route resolution review pending. no exact statically resolved backend match in scanned contracts.

Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.

endEncounter

Pinned source evidence

Links require access to the private source repository.