Create Indent

CARE Jharkhand · DVDMS Integration
📋 Tracking
UAT Environment

1 API Connection

Used for every call this page makes (indent save + the master data lookups below).

By default, uses the Cloudflare Pages proxy. Direct calls to the API will likely hit a CORS/403 error from the browser.
Not stored anywhere — used only for requests made from your browser.

2 Master Data

Loads Store, To-Store, Drug and Group lists from DVDMS. The Drug list includes all mapping information (GroupId, SubGroupId, etc.) and auto-fills the indent items table. Field-name mapping is guessed defensively (e.g. storeId vs id) — the raw response is shown below each call so we can verify the mapping.

Not loaded
Uses the "From Store" selected in step 3 + Hospital Code below. Not loaded
Not loaded
Not loaded

3 Indent Details

Header-level information sent as part of the indent save request.

4 Indent Items

Select a Drug from the dropdown (populated from "Load Drugs" button above) to auto-fill ItemId, GroupId, SubGroupId, and other fields from the drug master data. You can also manually enter values if needed.

Drug (search/select) Drug/Item ID ItemBrandId ReqQty Group (search/select) GroupId SubGroupId Rate RateUnitId IndentQtyUnitId InHandQty InhandQtyUnitId AvailableQty IssueQtyUnitId ReorderLevel

5 Save Indent

If using the local proxy, change this to http://localhost:8090/dvdms/save/indent too.

Open Items Tracked (from spec discussion with Shirish)

  • Whether GET /drug/list (item list) is facility-scoped or global — worth confirming since this page loads it once, globally.
  • The seatId concept for store mapping — now wired into "Load From Stores", but its exact meaning/scope is still unclear.
  • Two contradictory Acknowledge Save payload versions exist across the spec docs — response parsing below may need to handle both.
  • No API yet for per-item batch/expiry/manufacture-date detail needed for the inward stock receipt flow.
  • Group/SubGroup mapping is now resolved via drug/list (keyed by hstnum_item_id) — worth confirming with Shirish that this stays the authoritative source if it ever disagrees with the standalone Group List API.