ITF Health · with ITF Digital

Registers and dashboards for facility records

Policy, credential, facility-round and device registers for healthcare organisations, and revenue dashboards built from your own billing data.

Built by
ITF Digital
Built for
Facility records: maintenance, inspections, training, stock
Patient records
Stay in your clinical system
Revenue dashboards
Totalled from your billing exports
Handover
The system, its data model, the test record and the manual

ITF Digital builds the non-clinical systems healthcare organisations keep in spreadsheets: the policy register with acknowledgements, staff credential expiries, facility rounds, the CBAHI evidence index, device traceability, complaint logs and revenue dashboards. They are built for facility records, such as maintenance, inspections, training and stock. Patient records stay in your clinical system.

Left: a device traceability record listed as its fields and types, lot number, device, supplier, goods-in date, delivered to a customer site, delivery date and a kept edit history, feeding a recall list exported by lot. Middle: what the registers are built for, facility records for maintenance, inspections, training and stock, and below it a clinical event referred to by its reference number in your clinical system, which holds the patient record. Right: a billing export from the practice management system, totalled first, feeding a revenue dashboard of claims and payments by payer, denials by reason, receivables by age and the monthly trend.TRACEABILITY RECORDLOT NUMBERTEXTDEVICEFROM A LISTSUPPLIERFROM A LISTGOODS-INDATEDELIVERED TOCUSTOMER SITEDELIVERY DATEDATEEDIT HISTORYKEPTRECALL LISTBY LOT, ONE EXPORTBUILT FOR FACILITY RECORDSMAINTENANCEINSPECTIONSTRAININGSTOCKCLINICAL EVENTBY REFERENCE NUMBERYOUR CLINICAL SYSTEMHOLDS THE PATIENT RECORDBILLING EXPORTFROM YOUR PM SYSTEMTOTALLED FIRSTBY PAYER, REASON, AGE, MONTHREVENUE DASHBOARDCLAIMS AND PAIDBY PAYERDENIALSBY REASONRECEIVABLESBY AGETRENDBY MONTHPATIENT DETAIL STAYS AT THE SOURCEBUILT FOR FACILITY RECORDS; PATIENT RECORDS STAY IN YOUR CLINICAL SYSTEM
A register built for facility recordsPatient records stay in your clinical system; revenue arrives already totalledSwipe to pan
  1. 01 Enquiry
  2. 02 Survey
  3. 03 Scope
  4. 04 Plan
  5. 05 Execute
  6. 06 Evidence
  7. 07 Review
  8. 08 Next cycle

Registers and dashboards for facility records sits at step 6 of the same eight steps, with health's names. You receive the evidence index, or the monthly revenue cycle report.

01

The spreadsheet one person updates

Most healthcare registers live in a spreadsheet that works until the person who keeps it goes on leave.

The credential register is updated by one person, so a licence expiry is found when someone asks for the licence. Policies sit in folders per department with signed sheets in a drawer, and nobody can say who has read the current version. On survey day the evidence is on a shared drive nobody can search.

Device companies have a sharper version of the same problem. A traceability spreadsheet that three people edit has no history of who changed what, and ISO 13485 expects software used in the quality system to be validated for that use. The day it matters is the day a recall list has to be built from it.

02

What gets built, and for whom

Each system replaces something a healthcare organisation already keeps, usually badly.

SystemForWhat it replaces
Policy register with read-and-acknowledgeHospitals and clinicsFolders per department and signed sheets in drawers
Credential and certification expiry registerHospitals and clinicsA spreadsheet one person updates
Facility round appFacilities teamsPaper checklists photographed on phones
CBAHI evidence indexQuality departmentsA shared drive nobody can search on survey day
Traceability registerDevice importers and distributorsDelivery notes without lot numbers
Complaint and vigilance logDevice companiesOne log mixing late deliveries with device failures
Revenue cycle dashboardClinics and practicesA monthly spreadsheet built by hand
03

What is handed over

01

The system itself

Running on the data model agreed with you, with your users set up.

02

The data model

Every field, its type and who can edit it.

03

The test or validation record

Evidence that the system does what it is meant to. For device companies, written as software validation for the quality system.

04

The operations manual

How to add users, run the exports and change a list, written for the person who will own it.

05

The handover pack

Access details and configuration, collected in one pack from ITF Digital.

04

From the data model to go-live

The data model is agreed with you before a screen is drawn.

  1. 01

    Data model first

    Every field is listed and agreed with you, with its type and who can edit it.

    Design
  2. 02

    Clinical records stay in your system

    Where a workflow has to point at a clinical event, it uses the reference number from your clinical system.

    Design
  3. 03

    Aggregate before display

    Exports from your practice management system are totalled by payer, month, denial reason and age of receivables before they reach the dashboard.

    Build
  4. 04

    Test or validate

    The system is tested against its intended use. For a device company under ISO 13485, the record is written as software validation.

    Before go-live
  5. 05

    Handover

    The system, the data model, the test record and the operations manual.

    Go-live
05

A distributor's lot register

A device distributor tracks lots in a spreadsheet that three people edit. Under ISO 13485 the tool it uses to track lots has to be validated for that use, and the spreadsheet has no history of who changed what.

ITF Digital builds a traceability register that records each lot at goods-in and at delivery, keeps an edit history and exports a recall list by lot in one step. The validation record for the register goes into the quality system.

The distributor ends up holding the register, its validation record and a mock recall export.

06

Asked before a build

Q01

Can you connect to our hospital information system?

For non-clinical data such as staff rosters, where your system allows it. Clinical records stay in the system that holds them, and a register refers to them by reference number.

Q02

Does the revenue dashboard replace our billing system?

No. Revenue work runs in your existing practice management system, and the dashboard reads aggregated exports from it. The pattern shows on the dashboard; the patient detail stays at the source.

Q03

Why does ISO 13485 care about a spreadsheet?

Clause 4.1.6 requires software used in the quality management system to be validated for its application before first use and after changes, in proportion to the risk. A shared spreadsheet with no edit history is hard to validate and harder to defend at audit.

Q04

How does the CBAHI evidence index work on survey day?

Each requirement in the index points at the document or record that proves it. The surveyor asks for a standard, and the evidence opens from the requirement instead of being searched for.

Bring the spreadsheet

A systems call starts from the file you use today: which fields matter, who edits it and what it has to produce. That is most of a specification.

Book a systems call