One data layer for your hospital and the business around it
ICE is how Insource products share data. Patients, employees, items and visits are created once and used everywhere, so your finance, HR and operations reports agree with each other.
You do not have to buy everything at once. ICE is the reason adding the next product is a configuration task rather than an integration project.
What problem ICE solves
A typical 200-bed hospital runs a hospital system, a separate payroll tool, a spreadsheet for biomedical assets, a stock system in the pharmacy, and an accounting package. Each is fine on its own. The trouble starts at month end, when the nursing headcount in HR does not match the roster in the hospital system, and the pharmacy's stock value does not match the ledger.
ICE removes those reconciliation jobs. The products are built on shared platform primitives: one master patient index, one employee master, one item master, common authentication, audit and workflow. When TechPro needs a nurse's shift, it reads it from Talent Plus. When the pharmacy dispenses, Inventory Plus and the patient bill move together.
What connects to what
Integration points available today between Insource products.
| From | To | What flows |
|---|---|---|
| TechPro HMIS | Talent Plus HRMS | Staff master, duty rosters, shift handover owners, payroll inputs |
| TechPro HMIS | Inventory Plus | Pharmacy and ward consumption, indents, purchase requests, item master |
| TechPro HMIS | RadioMind PACS | Radiology orders, worklists, images and reports on the patient record |
| Fieldera FSM | Inventory Plus | Field inventory used on visits, distributor orders |
| Fieldera FSM | Talent Plus HRMS | Field attendance and geo-verified check-ins feeding payroll |
| All products | Financial accounting | GL, AP and AR postings, with a Tally connector where you keep Tally |
Depth of each link depends on the modules licensed. Confirmed during scoping.
Separate tools versus ICE: a month-end comparison
What changes for the people who close the month.
| Task | With separate systems | With Insource products on ICE |
|---|---|---|
| Nursing headcount for payroll | HR exports the roster; wards correct it by email | Rosters live in Talent Plus and TechPro reads them |
| Pharmacy stock value | Store count, then a ledger adjustment | Inventory Plus values stock daily from every issue and receipt |
| Consumables billed to patients | Ward slips matched to bills by hand | Issue to patient posts to the bill and the stock ledger together |
| Field staff attendance | Spreadsheets from regional managers | Geo-verified check-ins from Fieldera |
| Department P&L | Built in spreadsheets from four exports | Generated from shared cost centres |
What you need to decide before connecting products
Connecting products is mostly a data-ownership exercise. Someone must own the item master, someone the employee master, someone the department list. We run a short master-data workshop at the start of every multi-product rollout, because agreeing these owners early prevents months of reconciliation later.
The second decision is sequence. A hospital that is short of nurses usually connects Talent Plus first; one with pharmacy leakage starts with Inventory Plus. There is no single right order, only the order that removes your biggest manual job first.
What leadership sees
Role-based views pull from every connected product.
CEO and COO
Occupancy, throughput, bottlenecks, patient experience and network performance in one view.
CFO
Revenue leakage, billing errors, claims, refunds, deposits, inventory value and collections.
CIO
Integrations, mobile access, PACS links, security, audit, uptime and rollout status.
Medical and nursing leads
Quality, safety, documentation completeness, critical results and nursing workload.
HR head
Headcount, attendance, attrition risk and payroll status by facility.
Unit heads
Turnaround times, backlog, workload and escalations by department, shift and site.
How customers usually adopt ICE
- 01
Start with the urgent system
Most hospitals begin with TechPro; distributors often start with Inventory Plus or Fieldera.
- 02
Agree the masters
Patients, employees, items, departments and cost centres are set up once in the shared master data layer.
- 03
Add the second product
Talent Plus or Inventory Plus picks up the existing masters, so there is no second data migration.
- 04
Turn on the command layer
Cross-product dashboards and MIS go live once two or more products share data.
ICE is a platform, not a separate licence fee
ICE describes how Insource products connect. Pricing is based on the products and modules you license. See plans and packaging.
A record entered once, seen everywhere
A medicine dispensed to a ward patient leaves stock and lands on their bill in the same step.
Lab and imaging reports appear in the patient’s chart the moment they are signed.
The duty roster decides which doctors appear for appointments.
The central store replenishes every pharmacy counter before it runs out.
Single sign-on
One login across products, with role-based access down to the screen.
Audit trails
Who changed what, and when, on every record that matters.
Cloud, web & mobile
Browser access for every role, plus patient, doctor and employee apps.
Open standards
HL7, FHIR R4 and open APIs for the systems you already run.
Frequently asked questions
Is ICE a separate product?
Can ICE connect to software from other vendors?
Does every module share one database?
How long does it take to add a second product?
Can different branches run different products?
Related pages
TechPro HMIS
TechPro is a hospital management system with EMR, nursing, pharmacy, lab, billing, insurance and AI across 81 modules. Live in 60+ hospitals. Book a demo.
Open Main product pageTalent Plus HRMS
Talent Plus runs attendance, rosters, leave, payroll with PF, ESI and TDS, recruitment and appraisals, with a mobile app for every employee.
Open Main product pageInventory Plus
Real-time stock across stores and warehouses, purchase orders from reorder levels, barcode tracking, transfers and a built-in Tally connector.
OpenMap your current systems to ICE
Share the systems you run today. We will show which ones ICE replaces, which it connects to, and the order that causes the least disruption.
- Current-state system map
- Recommended sequence and timeline
- Integration effort estimate