Question 1

What does Struktive for Healthcare actually do?

Accepted Answer

Struktive takes a messy biomedical equipment register — a CSV or Excel export from your CMMS, spreadsheet, or legacy system — and returns a clean, structured, scored version of that data, ready to import into Nuvolo Connected Workplace, ServiceNow HAM Pro, IBM Maximo, TMS, or any CMMS that accepts a flat CSV. It resolves OEM names (e.g. 'GE', 'GE Healthcare', 'GE Medical Systems' → 'GE HealthCare'), parses free-text location strings into a structured hospital hierarchy (Campus → Building → Floor → Department → Room), assigns GMDN codes and ECRI UMDNS terms to every device, classifies every device into one of 9 GMDN device categories, flags life support devices, cross-references FDA UDI records, and scores each record 0–100 on CMMS import readiness. The output is a seven-tab TJC Compliance Pack XLSX plus platform-native export files for your target CMMS.

Question 2

What file formats does Struktive for Healthcare accept?

Accepted Answer

Struktive accepts CSV and Excel (.xlsx / .xls) files. It handles real-world biomedical equipment register exports — files with metadata preamble rows, inconsistent quoting, mixed delimiters, and empty rows are all handled gracefully. Maximum file size is 50 MB per upload. No reformatting required before upload.

Question 3

Do I need to format my device register before uploading?

Accepted Answer

No. Struktive auto-detects column mappings using a library of 250+ healthcare-specific header aliases (e.g. 'Asset Tag', 'Device ID', 'Equipment No', 'OEM', 'Manufacturer', 'Make', 'Model No', 'Serial', 'S/N', 'Location', 'Department', 'Room', 'Risk Class'). You do not need to rename columns or reformat your file before uploading.

Question 4

How does the 7-stage HTM pipeline work?

Accepted Answer

Stage 1: OEM Name Resolution — resolves 800+ raw OEM name variants to canonical names (e.g. 'Philips', 'Philips Healthcare', 'Philips Medical' → 'Philips'). Stage 2: Hospital Hierarchy Parsing — extracts campus, building, floor, department, and room from free-text location strings. Stage 3: GMDN-coded Device Classification — assigns a GMDN code and ECRI UMDNS term to every device, and classifies it into one of 9 GMDN device categories using clinical engineering keyword rules and LLM fallback. Stage 4: Life Support Flagging — identifies life support devices per AAMI/TJC definitions and flags them in every export. Stage 5: FDA UDI Cross-Reference — matches device descriptions to FDA GUDID records where available. Stage 6: Quality Scoring — scores each record 0–100 on CMMS import readiness. Stage 7: Export Generation — renders platform-native export files for your target CMMS.

Question 5

What is the quality score for biomedical devices?

Accepted Answer

Each device record receives a 0–100 quality score. The healthcare scoring formula weights OEM resolution (+15), serial number validity (+15), hospital hierarchy resolution (+10), and life support flag accuracy (+10) heavily, reflecting CMMS import and TJC audit requirements. Records scoring 70 or above are considered CMMS import-ready. Records below 50 typically have missing device tags, unresolved OEM names, or no location data — these require manual review before CMMS import.

Question 6

Which CMMS platforms does Struktive export to?

Accepted Answer

Struktive currently supports six healthcare export profiles: Nuvolo Connected Workplace (Asset, Location, and Manufacturer records with Nuvolo field names), ServiceNow HAM Pro (alm_asset and cmdb_ci_hardware tables with sys_class_name mapping), IBM Maximo (Equipment, Functional Location, and Classification records), TMS (Tabula Rasa Healthcare TMS format), Dematic (equipment register CSV), and Struktive Native (clean CSV with all normalised fields). The platform selector appears at download time.

Question 7

What is TJC EC.02.04.01 and why does it matter?

Accepted Answer

EC.02.04.01 is the Joint Commission Environment of Care standard that requires hospitals to maintain a written inventory of medical equipment. It has six Elements of Performance (EPs): EP1 requires a written inventory of all medical equipment; EP2 requires documented criteria for including equipment on the inventory; EP3 requires documented inspection, testing, and maintenance (ITM) activities; EP4 requires documented completion of ITM activities; EP5 requires documented actions taken when equipment fails; EP6 requires documented performance data for the equipment management programme. Failure to meet any EP is a finding that can result in a Requirement for Improvement (RFI) — and repeated RFIs can trigger a focused survey or, in extreme cases, CMS decertification proceedings.

Question 8

What does the TJC Compliance Pack contain?

Accepted Answer

The TJC Compliance Pack is a seven-tab XLSX file generated for every healthcare normalisation job. Tab 1 (Cover): chain-of-custody metadata — source file SHA-256 hash, processing timestamp, normaliser version, record count, and sign-off blocks. Tab 2 (Equipment Register): the full normalised device inventory with HTM classification, life support flags, and quality scores. Tab 3 (Maintenance Schedule): ITM schedule derived from device category and criticality rating. Tab 4 (Life Support Devices): a dedicated register of all life support devices with AAMI/TJC classification basis. Tab 5 (Imaging & Radiology): all imaging and radiology devices with modality codes. Tab 6 (Surgical & Procedural): all surgical and procedural devices with risk class. Tab 7 (Summary Statistics): record count, quality score distribution, OEM breakdown, and HTM category breakdown.

Question 9

How does Struktive address each TJC EC.02.04.01 Element of Performance?

Accepted Answer

EP1 (Written inventory): The Equipment Register tab provides the complete written inventory. EP2 (Inclusion criteria): The Cover tab documents the classification rules and inclusion criteria used. EP3 (ITM activities): The Maintenance Schedule tab documents the required ITM activities by device category. EP4 (ITM completion): The Equipment Register includes fields for last maintenance date and next due date — populated from your source data where available. EP5 (Equipment failure): The Exceptions Log documents devices flagged for quality issues or missing data. EP6 (Performance data): The Summary Statistics tab provides the programme-level performance data required for EP6.

Question 10

How quickly can I prepare for a TJC survey with Struktive?

Accepted Answer

For a typical hospital biomedical register of 1,000–5,000 devices, the normalisation pipeline completes in under 5 minutes. The TJC Compliance Pack is generated automatically as part of every job — there is no additional step. A hospital that uploads a clean register in the morning can have a survey-ready TJC Compliance Pack by the same morning. The manual equivalent — reviewing and cleaning a 3,000-row register, building the maintenance schedule, and preparing the life support register — typically takes an HTM team 4–6 weeks.

Question 11

Does Struktive flag life support devices automatically?

Accepted Answer

Yes. The life support flagging stage identifies devices that meet AAMI/TJC life support criteria based on device category, description keywords, and risk class. Life support devices receive a dedicated flag in the normalised output and appear in a separate Life Support Devices tab in the TJC Compliance Pack. The flagging logic is documented in the Cover tab so the HTM team can review and override any flags before the pack is submitted as audit evidence.

Question 12

Why do CMMS migrations fail and how does Struktive help?

Accepted Answer

The single most common reason a Nuvolo, ServiceNow HAM, or Maximo go-live is delayed or fails is that the source biomedical equipment register is too dirty to load cleanly. Typical issues: OEM names have 40–80 variants for the same manufacturer, location strings are free text with no consistent hierarchy, device categories are missing or inconsistent, and duplicate records inflate the count. Struktive resolves all of these issues in a single pipeline run — before the data reaches your CMMS implementation partner. The result is a clean, classified, scored register that imports on the first attempt.

Question 13

How does the Nuvolo Connected Workplace export work?

Accepted Answer

The Nuvolo export generates three linked CSV files: Asset (with Nuvolo field names: asset_tag, display_name, manufacturer, model_number, serial_number, install_status, asset_category, location, department, life_support_flag, criticality_rating, fda_udi), Location (location_name, parent_location, location_type, building, floor, room), and Manufacturer (manufacturer_name, country_of_origin). The pre-flight summary panel shows any location codes that need to be created in Nuvolo before the asset import.

Question 14

How does the ServiceNow HAM Pro export work?

Accepted Answer

The ServiceNow HAM Pro export generates records mapped to two ServiceNow tables: alm_asset (asset_tag, display_name, model_category, install_status, assigned_to, location, department, serial_number, manufacturer) and cmdb_ci_hardware (name, serial_number, manufacturer, model_id, sys_class_name, location, department, life_support, criticality). The sys_class_name is mapped from the HTM device category — for example, Imaging devices map to cmdb_ci_medical_imaging_device.

Question 15

Can Struktive push data directly into Nuvolo or ServiceNow?

Accepted Answer

Not yet. The current workflow is: normalise in Struktive → download the platform-specific export file → import into your CMMS using the platform's native import tool or your implementation partner's migration scripts. Direct API push to Nuvolo and ServiceNow HAM Pro is on the roadmap.

Question 16

What is the typical timeline for a CMMS migration with Struktive?

Accepted Answer

Without Struktive, the data preparation phase of a CMMS migration typically takes 8–12 weeks: 2–3 weeks to audit the source register, 3–4 weeks of manual cleaning and mapping, 1–2 weeks of test imports, and 2–3 weeks of remediation. With Struktive, the data preparation phase compresses to under 1 hour for the normalisation run, plus 1–2 days for the HTM team to review the quality score report and resolve any records below the import-ready threshold. This typically saves 6–10 weeks of implementation time.

Question 17

Where is my biomedical device data stored?

Accepted Answer

Uploaded files and generated exports are stored in an S3-compatible object store with non-enumerable keys. Metadata is stored in a MySQL-compatible database. No data is shared with third parties. Device register data is not used to train any models.

Question 18

Does Struktive use my device data to train models?

Accepted Answer

No. Your biomedical device register data is never used to train machine learning models. The LLM classification stage receives only the device description and category options — it does not receive your device tags, serial numbers, patient data, or location data.

Question 19

Is Struktive HIPAA-aware?

Accepted Answer

Struktive processes equipment register data — device tags, serial numbers, OEM names, and location data. It does not process Protected Health Information (PHI) as defined under HIPAA. Equipment register data does not typically constitute PHI. If your equipment register contains any patient-linked data fields, you should remove those columns before uploading. Struktive's data handling commitments (TLS 1.2+, AES-256 at rest, no third-party sharing, no model training) are consistent with HIPAA technical safeguard requirements for non-PHI data.

Question 20

Is my data encrypted in transit and at rest?

Accepted Answer

Yes. All data is encrypted in transit via TLS 1.2+. Data at rest is encrypted using AES-256 at the storage layer.

Question 21

How does pricing work for biomedical equipment registers?

Accepted Answer

Struktive uses a credit-based model. Credits are purchased in packs and consumed per record processed. One record = one device row in your register CSV. There is a free tier that allows you to normalise up to 350 records without purchasing credits — no login required. See the Pricing page for current pack sizes and rates.

Question 22

What counts as a record for healthcare?

Accepted Answer

One record is one device row in your uploaded CSV file, after the pre-processor strips empty rows and metadata preamble rows. A hospital with 3,200 devices in its register would consume 3,200 credits for a full normalisation run.

Question 23

Is the TJC Compliance Pack included in the standard credit cost?

Accepted Answer

Yes. The seven-tab TJC Compliance Pack XLSX is generated automatically as part of every healthcare normalisation job. There is no additional charge for the compliance pack — it is included in the standard per-record credit cost.

Question 24

Do credits expire?

Accepted Answer

Credits do not expire. Once purchased, they remain in your account until used.

Question 25

Is there a volume plan for large health systems?

Accepted Answer

Yes. Volume plans are available for health systems with multiple sites or large device registers. Contact us via the pricing page to discuss volume pricing for your programme.

Question 26

What happens to my uploaded file after processing?

Accepted Answer

Your original uploaded file is automatically deleted from our storage servers when your job completes. This happens without any action from you. We keep the normalised results — not your raw file.

Question 27

How long is my data retained?

Accepted Answer

Free-tier jobs (no account) are retained for 90 days. Paid jobs are retained for 12 months. TJC Compliance Audit Packs are retained for 12 months regardless of tier. Data is purged automatically by a nightly cleanup job.

Question 28

Can other users see my device register data?

Accepted Answer

No. Every job is isolated to your account or session. Authenticated jobs are accessible only to the account that created them. Anonymous jobs are accessible only via the unique job ID.

Question 29

How are TJC Compliance Packs protected against tampering?

Accepted Answer

Every TJC Compliance Pack receives a SHA-256 hash at generation time stored in a tamper-evident registry with WORM semantics. You can verify the integrity of any pack at any time via struktive.io/verify. The hash appears on the Cover tab of every pack.

Everything you need to know about Struktive for Healthcare

HTM & CMMS

Ready to clean your device register?