Close interdepartmental and intersite stock transfers properly
For Stores manager / pharmacy operations lead · Plan implementation
TL;DR — what you’ll learn
- A dispatch confirms movement from the source; receipt and eligibility need their own evidence.
- Reconcile every transfer line across source, transit, destination and unresolved states.
- Preserve damage and quantity differences without silently rewriting the dispatched record.
- Pilot one route with stable identifiers, ordinary permissions and duplicate/recovery tests before enabling broader posting.
Central stores dispatches fifty boxes to a satellite site. The receiving team counts forty-seven intact boxes and three damaged boxes. One screen calls the transfer complete; another shows only forty-seven received, leaving three apparently in transit.
A hospital stock transfer should finish with an explained outcome for every dispatched quantity. Record physical receipt separately from permitted-use status and commercial adjustment. In this example, all fifty may have reached the destination while only forty-seven enter the eligible holding and three remain restricted pending review.
Agree the transfer contract between locations
Start with one source, one destination and one item category. The stores owner should define a stable transfer ID, line ID, item, unit, approved conversion, batch where required, source and destination, dispatch reference, physical-event times and confirmation evidence. Include the source system and revision when more than one application is involved.
Bahmni describes movements between stock locations. For this pilot, obtain evidence of separate dispatch, receipt and restriction records in the deployed version, together with stable identifiers and supported lookup/correction operations. Start with read-only reconciliation if any required write or recovery behaviour remains unproven; the product description does not establish integration readiness.
Before mapping the transfer, ask finance and the appropriate advisers to establish the legal entities and commercial meaning of the movement. Record their approved valuation, tax and documentary requirements as inputs. The fifty-box example demonstrates custody reconciliation only; it cannot determine whether a real transfer is a sale, an internal movement or another financial event.
Reconcile the fifty boxes in two views
The illustrative physical-custody view is 50 dispatched = 50 received + 0 still unresolved in transit. The destination status view is 50 received = 47 eligible + 3 restricted. These are related views of the same stock, not two quantities to add together.
Scroll horizontally to see all columns.
| Transfer evidence | Quantity | Resulting question |
|---|---|---|
| Source dispatch T-15/L-1 | 50 boxes | What left the source? |
| Destination physical count | 50 boxes | What arrived? |
| Intact quantity in approved eligible status | 47 boxes | What meets the locally approved status? |
| Damaged quantity awaiting disposition | 3 boxes | Who decides its next state? |
If only forty-nine boxes physically arrive, retain one unresolved in transit instead of inventing a damage event. This is an identity and quantity distinction. The actual acceptance, restriction and disposition rules must be supplied by the responsible pharmacy, quality or technical owner for the category. The proposed transfer pilot does not decide that damaged or uncertain goods are eligible for use.
Define writes and approvals before building them
The initial integration can propose a destination receipt and discrepancy task from a source dispatch. Require the receiving user to confirm the actual quantity. Any automated posting must stay within the fields, locations and permissions explicitly approved for the pilot.
The system may calculate an unexplained difference; it must not decide that the difference is an authorised loss. Keep the original dispatch immutable within the agreed correction mechanism and link later approved adjustments. A return to source is a further movement with its own references, not deletion of the receipt.
Worked workflow
Original illustrative workflow. Follow the labelled transitions, including the exception paths.
- A · StepAuthorised dispatch with stable line identity
- B · StepDestination records physical count
- C · DecisionDispatched quantity fully explained
- D · StepOwned transit discrepancy
- E · StepApply reviewed destination statuses
- F · StepInvestigate and record authorised resolution
- G · DecisionRestricted quantity remains
- H · StepCategory owner decides disposition
- I · StepReconcile transfer outcome
Scroll horizontally to see all columns.
| From | Condition | Next |
|---|---|---|
| A: Authorised dispatch with stable line identity | Continue | B: Destination records physical count |
| B: Destination records physical count | Continue | C: Dispatched quantity fully explained |
| C: Dispatched quantity fully explained | No | D: Owned transit discrepancy |
| C: Dispatched quantity fully explained | Yes | E: Apply reviewed destination statuses |
| D: Owned transit discrepancy | Continue | F: Investigate and record authorised resolution |
| E: Apply reviewed destination statuses | Continue | G: Restricted quantity remains |
| G: Restricted quantity remains | Yes | H: Category owner decides disposition |
| G: Restricted quantity remains | No | I: Reconcile transfer outcome |
| F: Investigate and record authorised resolution | Continue | I: Reconcile transfer outcome |
| H: Category owner decides disposition | Continue | I: Reconcile transfer outcome |
Prove replay and correction behaviour
Store the relationship between the source event and destination business record. An HTTP success or imported-file count is not enough: the reconciliation must identify what record was created and what outcome remains unknown. If the response is lost, inspect the supported destination evidence before creating another receipt.
Scroll horizontally to see all columns.
| Challenge | Observable acceptance evidence |
|---|---|
| Same fifty-box dispatch delivered twice | One destination business movement, with the repeated event identified |
| Destination receipt succeeds but response is lost | Existing receipt found or outcome held uncertain; no speculative second posting |
| Source revision changes the line after receipt | Reviewed correction path links both versions and affected destination events |
| Operator lacks access to the receiving location | Posting denied and assigned for review without expanding permissions |
| Damage review remains unfinished | Restricted quantity stays visible after the transfer's custody reconciliation |
The vendor must demonstrate the actual duplicate key, lookup and correction support. A generic retry setting is not a substitute for those controls.
Keep the first pilot recoverable
Run the synthetic challenge set before connecting live movements. Begin with a read-only discrepancy report, then an authorised proposal stage, and only then a narrowly scoped writer if the evidence supports it. The stores owner and integration owner should agree who can pause new writes, preserve pending references and reconcile manual receipts before resuming.
Measure unexplained dispatched quantity, unresolved-transfer age and manual recovery effort with an explicit cutoff. Separate physical shortages from restricted quantities; otherwise a damaged-but-received box can be counted as missing twice. Track the same transfer cohort until each outcome is resolved rather than declaring success from a day's message throughput.
A completed transfer is an explained handover. The receiving and source teams should be able to reconstruct custody, status and any adjustment without using the word “complete” to conceal unfinished work.
Next actions
- Agree one route, item category and event contract with both stores owners.
- Demonstrate the fifty-box case and the lost-response challenge in a controlled environment.
- Approve posting scope, pause authority and reconciliation evidence before moving beyond read-only reporting.
Discuss this workflow
Request a workflow assessment focused on this question: When should a hospital stock transfer count as complete?
Describe the operation using business information only. Please leave out patient details.
Applying this guide
The scenarios and numbers are illustrative. Confirm these provider-specific inputs before implementation:
- Pharmacy, quality or technical owner as applicable: Approved receipt and disposition procedure with the permitted decision roles.
- Finance controller and tax/legal adviser: Entity map, accounting and documentary requirements; no tax or valuation rule inferred.
- Stores system owners and integration lead: Version-specific API/export documentation and executed synthetic duplicate, timeout, correction and permission tests.
References
- Bahmni stock management — Advertised inventory concepts only; actual configuration, disposition and access require validation.
Topics: hospital stock transfer · hospital inter store transfer · multi branch stock transfer · hospital transfer discrepancy