Decima Implant Helper

iAdministration. Manage user accounts and review the activity log of entries and locations across all users.

User accounts

Username

Password

Role

User	Role	Status	Created

Activity log

Time (UTC)	User	Role	Action	Detail	Location	IP

iInventory. Track implant stock across your stores and branches, transfer between them, and record the implants used per case with dates. Counts are shared across all signed-in users; no pricing is shown here.

Stores & branches

Store name

Branch

Location

Store	Branch	Location	Lines	Units

Stock on hand

Check availability

Store

Transfer between stores

From

To

Record a case · implants used

Case ref

Surgery date

Procedure

Draw from store

Recent cases

Date	Case	Procedure	Lines	Units	Store	By

Movement & usage log

Date	Type	Category	Size	Qty	From → To	Case	By

iTechnical view. Enter usage %, stock and case numbers; quantities recalculate live. When the plan is ready, Export handoff (JSON) and send it to procurement. Pricing is added separately by procurement.

iProcurement view. Set one unit price per category in each section header — it applies to every size in that category. Import the technical handoff first if you have one.

iSK1 total knee replacement. Tibial parts scale with total knees; femoral components scale with their side and share one catalogue price. Bone cement is estimated per case.

iDirect procurement analysis. Inventory value = full recommended carry set × category price. Order cost = units still to order (after stock on hand) × category price.

Cost by category — inventory value

Procurement summary

Roles & data separation

Technical staff plan the implant set — case numbers, sizing probabilities and stock on hand — and export a handoff file. That file contains no pricing. Procurement staff import the handoff, add manufacturer prices and run the cost analysis. Prices live only in the procurement view and are never placed in technical exports, so technical staff never receive purchase values.

The procurement PIN is a workflow barrier on a shared device, not encryption. For complete separation, run the two roles on separate devices and exchange the handoff file.

Automatic encrypted handoff

When the relay is configured on your VPS, technical staff press Send to procurement and procurement presses Receive from technical — no files change hands. The handoff is end-to-end encrypted in the browser with AES-256-GCM, using a key derived from a shared transfer passphrase via PBKDF2 (210,000 iterations, SHA-256) with a random salt and IV per submission.

The server (relay.php) only ever stores ciphertext — it never sees the passphrase, the key, or the plaintext, including the institute/camp labels and dates.
Procurement decrypts client-side; a submission encrypted with a different passphrase shows as locked and cannot be read.
Encryption requires HTTPS (a secure context), which your Let's Encrypt certificate already provides.
The relay still carries no pricing — it is the technical handoff. Pricing is added only in the procurement view.

Job details

Each plan records the institute or, for combined orders across several camps, a mixed-procurement label, plus the data-entry date and the expected camp date. These travel with every export, the encrypted handoff, and appear on the procurement summary and printouts.

Stores, transfers & cases

The Inventory tab tracks real implant stock across your stores and branches. Stock is added as receipts, moved between stores as transfers, and consumed by recording a case — which lists the implants used, deducts them from the chosen store and stamps the surgery date. Every movement is kept in a dated ledger, so you can see the number and dates of implants used and the cases they belong to. Unlike the planning records, inventory counts are not end-to-end encrypted: the server has to read them to keep running balances and produce the movement log, so they are protected by sign-in and HTTPS instead. No pricing appears in this tab. Use in planner copies a store's quantities into the planner's stock-on-hand fields so the order calculation reflects what you actually hold.

One price per category

Within a catalogue category every size carries the same manufacturer price, so price is entered once per category and applied to all its sizes. The two femoral components (right and left) are the same component and share a single price.

Quantity to carry

carry = ⌈ (usage% ÷ 100) × cases ⌉

With the safety buffer on, any size that rounds to a single unit across more than one case gets one spare. Knee femoral edge sizes (1, 8, 9) are exempt, preserving the original behaviour.

Quantity to order

order = max( carry − stock on hand, 0 )

Distributions & the reinstated sizes

Cup, liner, head and stem percentages are mutually exclusive per case. The audit (n = 62) never recorded the largest cups, so Acetabular Cup 64 & 66 and Acetabular Liner 64/32 & 66/32 are reinstated at the lowest observed tier (1.61%). Liner 66/32 is added for cup–liner parity and flagged PARITY — remove it if your catalogue caps the 32 mm liner at 64. Adding rare sizes pushes a group above 100%, which is the protective direction for safety stock; Normalize rescales a group to exactly 100%.

Titanium hip screws

Screw usage is a rate, not a distribution. The larger sizes were increased on request, kept within the observed range: 32 → 10.96%, 34 → 8.22%, 36 → 6.85%. All values remain editable.

Decision support only. Final implant selection and quantities remain the responsibility of the operating surgeon and theatre team.