Indent Tracking

1 API Connection

Same proxy setup as the Create Indent page — no changes needed to dvdms-proxy.sh, these endpoints share the same base path.

API Base URL By default, uses the Cloudflare Pages proxy. Direct calls to the API will likely hit a CORS/403 error from the browser.

Authorization Header (Basic <key>) Not stored anywhere — used only for requests made from your browser.

Calls GET /getDrug/datails. Response is a list of pipe/caret-encoded item strings — parsed fields below are best-effort based on comparing against known values; click a row to see the full breakdown including raw, unlabeled segments.

Hospital Code

From Store Id

Issuing Store Id

Indent No

Not loaded

Item Name	ItemId	ItemBrandId	Req / Approved	Unit
No data loaded yet — click "Fetch Indent Details" above.

Raw response

Store Id	Issue No	Req Type	Party / Store Name	Date
No data loaded yet — click "Fetch Pending List" above.

Indent No	Indent Date	From Store	To Store	Status	Remarks
No data loaded yet — click "Fetch Issue Pending List" above.

Open Items to Confirm with Shirish

Exact meaning of the unlabeled trailing segments in getDrug/datails (the repeated 0/0 pairs and the -1 flag) — currently shown as raw, unlabeled fields in the drawer rather than guessed.
Exact meaning of the leading flag and trailing flag in each acknowledge-pandding/list entry (shown as index 0 and last raw segment) — not yet mapped to a named field.
Whether pkKey in the Acknowledge Details item list follows the same composite-key convention as strPk elsewhere in the spec — worth confirming before using it for anything beyond display.

1 API Connection

Open Items to Confirm with Shirish

Details