HOW IT WORKS

See the whole picture.
Explore every workflow.

Graphical coverage tour for SPD, OR, GI, stock, loan sets, mobile capture, purchasing, maintenance, traceability, and reporting. Choose a topic, click a stage, or run the complete walkthrough.

Visual workflow coverage (full text for search)

Interactive tour on this page covers SPD, decontam, OR, stock, GI, loan sets, mobile capture, purchasing, maintenance, traceability, reporting, and configuration.

Sterile processing

Follow case-linked returns, decontamination, washing, packing, sterilization review and distribution into sterile stock.

  1. Receive & reconcile: Receive returns against the OR case and compare expected contents with what physically comes back. Record: OR return + counts + outstanding items. Scan a case cart, tray or item to resolve the associated OR case.; Confirm received counts and retain outstanding-item exceptions.; The returned assembly’s sterile-processing life ends in Decontam.
  2. Wash & verify: Scan trays/kits directly or use a wash tag/basket to associate contents with a washer load. Record: Washer load + item-level wash result. Record washer, cycle and PASS / FAIL.; Failed items require rewash before packing can continue.; Confirm the wash cycle at Packing where configured.
  3. Identify the kit: Staff find the correct child kit using the identifiers already attached to it. Record: Kit identity. Scan UID, serial, alternate number, temporary tray tag, or kit name.; Open the correct child kit when a parent has multiple children.
  4. Pack & count: The packing workflow brings kit contents and assembly recording together. Record: Assembly UID + packing record. Complete the instrument count; review a tray photo when needed.; Record missing instruments and create the assembly UID.; Use facility label printing or preprinted SER/SPDL scans.; Capture a kit reference image using the mobile phone when required.
  5. Create the load: A new load identifies the machine and cycle for the packed assemblies. Record: Load + linked assemblies. Choose the sterilizer and cycle.; Use the next configured load number.; Scan packed kits onto the load and save the load.
  6. Capture load printout: Use a mobile phone to capture the sterilizer till-roll printout and assign the image to its load. Record: Load + till-roll image. Photograph the physical cycle printout.; Attach it to the corresponding load record/report for reference.
  7. Review the result: Load review separates usable assemblies from failed loads and biological holds. Record: Load result + release / hold state. Review release / Qten on the sterilization workflow.; Failed loads make their kits unusable.; Cycles configured as biological-required enter Quarantine.
  8. Read biologicals: Where required, the Qten workflow captures biological setup and final results. Record: Biological record. Record control, well, expiry, bio label, and incubation details.; Record setup and final pass/fail results with in/out dates and times.; Review completed loads as well as the active queue.
  9. Put away: Sterile-complete assemblies are assigned to a known stock destination. Record: Assembly + stock location. Choose a location or scan its slot.; Put away from the load or use Distribute.; The assembly lifecycle moves to distributed.

Decontam, counts & washing

Receive against the OR case, reconcile expected and returned counts, control outstanding items, and scan trays, baskets or wash tags to a washer.

  1. Receive against OR case: A case-linked cart, tray or item scan opens the corresponding OR case and its expected return list. Record: OR case + return session. Scan the case cart, tray, kit or item; select the case when required.; Load the items actually allocated to the case/cart.; Keep items belonging to another case linked to their own case history.
  2. Reconcile returned counts: Confirm the physical return against the expected case contents; received and outstanding counts remain visible. Record: Expected / received / outstanding quantities. Compare expected quantities with the trays, kits, Separates and instruments returned.; Receive items in Decontam or allocate them to a wash tag/basket.; Reduce the case’s outstanding count as items are received or resolved.
  3. Flag missing case items: Unresolved differences create a visible outstanding-item exception for investigation rather than disappearing when the rest of the case moves forward. Record: Case-linked missing-item alert. Keep the OR case, item/tray, count difference and last known location attached.; Show outstanding cases by age; identify missing, retained-in-OR, sent-elsewhere or quarantined items.; Record the reason, user and time for resolution; link replacement needs to purchasing.
  4. Assign wash tag / basket: Group received contents into a controlled wash tag or reusable basket session. Record: Wash grouping + item-to-case lineage. Scan or create the wash tag/basket and allocate the returned items.; Show selected, allocated and physical quantities; flag a basket-content mismatch.; When multi-case baskets are enabled, retain each item’s original OR case link.
  5. Scan tray to washer: Scan a tray or kit directly to the washer where enabled, or scan a basket/wash tag and then the washer. Record: Tray / basket / tag + washer load. Associate the scanned contents with the current/open washer load.; If needed, create a new washer load with the next cycle number.; Prevent the same item being added twice to an active load.
  6. Record wash cycle result: The washer load captures the machine, cycle number and explicit PASS / FAIL result for all included items. Record: Washer + cycle + load result. Increment the cycle number once per washer cycle, not per tray or basket.; Distinguish test cycles from production cycles; apply the configured failed-test warning or block.; A passing cycle records a successful wash transaction for each contained item.
  7. Fail → rewash required: A failed wash puts the affected items into REWASH REQUIRED and prevents downstream processing until a successful wash. Record: Failed wash + rewash / pass history. Keep failed cycles visible in the item history.; Block packing, sterilization and release while the failed-wash condition is active.; A later PASS clears the active block without erasing the previous failure.
  8. Confirm wash at Packing: Packing displays the last washer, cycle, date/time and result before the next packing stage. Record: Confirmed wash + audited correction. Confirm the washer cycle where the facility requires it.; Permit washer/cycle corrections only to authorized roles and locations.; Record the old and new value, reason, user and time for corrections.
  9. Pack & clear the basket: Scan the basket once to list eligible Separates and pack one, some or all into new assemblies. Record: New assemblies + closed basket session. Create one new assembly UID per selected Separate.; Leave unresolved items visible until packed, transferred, rewashed, quarantined or otherwise resolved.; Only close and return the reusable basket when active quantity is zero.

OR & preference cards

Connect the procedure requirement, the scheduled case, and the assemblies selected for that case.

  1. Define requirements: Preference cards hold the expected kits and quantities for a surgeon and procedure. Record: Surgeon + procedure requirement. Set card name, procedure, and surgeon.; Choose parent kits and quantities.; Save the reusable requirement card.
  2. Schedule the case: Staff work from the OR calendar, schedules and picking, or a manually created case. Record: Scheduled OR case. Filter by date, surgeon, OR, or status.; Facility settings control which case fields appear.; A local HL7 interface can supply OR bookings.
  3. Pick to cart / OR: The pick connects a planned requirement with identifiable assemblies. Record: Case + selected assembly UIDs. Choose the case and the relevant requirement.; Pick preference-card kits to a case cart or OR.; Scan assembly UIDs onto the case.
  4. Record the case: The actual case list records what was allocated, separately from the preference card. Record: Case allocation record. Print the case with its assigned trays.; Use a scan-only OR workflow where configured.; Optionally save scanned case contents as a future requirement card.
  5. Receive & count returns: The returned case is reconciled against the items actually allocated to it. Record: Case return + received / outstanding counts. Scan the case ID, MRN case UID, cart or case-linked assembly to open the case return.; Record expected and physically received instrument counts.; Keep outstanding items visible instead of treating a partial return as fully resolved.
  6. Alert on missing items: A missing-item exception stays linked to the OR case and the affected instrument or tray. Record: OR case + missing-item alert. Show what is outstanding, the missing quantity and the case context.; Investigate retained-in-OR, sent-elsewhere, missing or quarantined items.; Record resolution, or follow the case-linked replacement need into purchasing.
  7. Review activity: OR case reports and assembly records support subsequent review. Record: OR report + assembly trace. Review case activity by facility and date range.; Trace assemblies linked to the patient case.; Print reports or export the active report as CSV.

Stock & distribution

Follow sterile assemblies into defined locations and keep their lifecycle visible as they move.

  1. Define locations: Locations provide a consistent destination structure across the facility. Record: Location structure. Create stock areas, case carts, specialty carts, ORs, and workstations.; Define area, row, shelf, and bin.; Each location also receives its own UID.
  2. Choose destination: Distribution starts with the place the assemblies are going. Record: Distribution target. Scan the stock slot or select the target location.; Optionally restrict work to a sterilizer load.
  3. Scan & distribute: Assembly scans connect individual sterile-complete items to that target. Record: Assembly location. Scan one or multiple assembly UIDs.; Add them to the queue and process.; Move assemblies already in stock using the same path.
  4. Reconcile the slot: The Set action supports stock-taking at the selected slot. Record: Slot reconciliation. Scan the assemblies physically present.; Unscanned assemblies previously at that slot move to area-only.
  5. Search inventory: Stock Management provides one row per assembly UID. Record: Searchable assembly inventory. Filter by lifecycle.; Search UID, kit, patient, location, or load.; See patient assignment when an assembly is on a case.
  6. Review & export: Staff can review stock and open the assembly detail for authorized changes. Record: Stock extract + assembly detail. Export the current list as CSV.; Use Audit detail to update patient or stock location.

GI Lab & endoscopy

Track scope identity, visit context, processing checks, competency and storage life in a separate GI Lab path.

  1. Configure & register: Facility setup defines visit fields, scope identifiers, checklists and cabinets. Record: Scope register + GI configuration. Register serial, alternate asset tag, name, and checklist assignment.; Build cabinets with hook counts and storage life.; Configure the visible TagIT visit fields.
  2. Load & link visit: TagIT identifies the scope and records its visit context. Record: Scope + visit identity. Scan the hang tag, serial, alternate number, or asset tag.; Enter the enabled patient / visit fields or find a prior visit.; Generate Unique Visit ID from MRN + date + time when enabled.
  3. Complete checks: Core processing checks and simple checklists sit within the TagIT workflow. Record: Processing checks + step times. Record HLD, leak and channel responses.; Complete the assigned TagIT-only checklist.; Auto-clock checklist steps where configured.
  4. Verify competency: Optional full competency templates support a more detailed SOP walkthrough. Record: Full competency result. Walk through groups and steps.; Record cycle start/end, pass/fail, and an optional docket.; Return to TagIT for the hang-tag and cabinet workflow.
  5. Save & tag: A saved visit creates a cycle record, with hang-tag availability tied to configured checks. Record: Cycle record + hang tag. Save the visit to the cycle log.; Print the DYMO hang tag when required steps are complete.; Identify reprocessing without recorded patient use.
  6. Store & monitor: Cabinet hooks make storage position and storage life visible. Record: Hook location + storage-life state. Hang, move, or remove a scope by scan.; Green / orange / red show in-life, expiring, and expired.; Expired scopes require reprocessing before they can be hung again.
  7. Reprocess & reuse: Loading a stored scope back into TagIT returns it to the processing workflow. Record: Next scope cycle. Load the scope from its cabinet detail or by scan.; An occupied cabinet hook can be released during loading.; Repeat the visit and processing checks.
  8. Report & trace: GI reporting supports cycle history and facility-level review. Record: GI report + cycle history. Open a per-scope cycle log.; Review GI Lab / scopes by surgeon, user, scope, or use type.; Filter processed or reprocessed-without-use cycles and export CSV.

Loan sets & implants

Receive loan sets, photograph each tray and layer, follow processing and use, then document shipping contents for comparison and billing review.

  1. Plan the arrival: The loan-set calendar organizes receiving around the procedure date. Record: Loan calendar. View sets by date.; Filter by surgeon when needed.
  2. Receive the set: Facility configuration determines which clinical and scheduling fields appear. Record: Loan receiving record. Record the enabled surgeon, procedure, date, time, MRN, and OR fields.; Start the receiving record for the selected day.
  3. Photograph received layers: Capture receiving photos for every tray and layer in the loan set. Record: Receiving images by tray / layer. Link images to the loan set, tray and layer.; Retain the incoming arrangement and contents for the later shipping comparison.
  4. Identify & pack: Default receiving uses a reusable LOANSET tag before assembly creation in Packing. Record: Loan tag + assembly UID. Scan the semi-permanent LOANSET tag.; Rescan in Packing to create the assembly and label.; Where configured, receiving creates assemblies immediately instead.
  5. Process & use: Loan sets use the regular packing, sterilization and case workflows. Record: Processing + case history. Keep packing on the Packing screen.; Apply configured biological requirements.; Connect use and return to the clinical workflow.
  6. Record return: The loan lifecycle includes the post-use processing path before return. Record: Return-processing history. Use the relevant Decontam and sterilization workflows.; Keep processing records attached to identified assemblies.
  7. Photograph shipping layers: Capture the corresponding tray and layer images before the loan set is shipped back. Record: Shipping images by tray / layer. Document outgoing contents per tray and layer.; Keep receiving and shipping evidence linked to the same loan set.
  8. Compare contents & consumption: Compare the receiving and shipping images to evaluate consumed, missing or changed items. Record: Loan-set comparison + billing reference. Review corresponding layers and trays.; Retain the comparison as reference for consumption evaluation and billing review.
  9. Sign out: Loan-set sign-out completes the vendor return workflow. Record: Loan sign-out. Confirm HLD when required at shipping.; Sign out the loan set.; Release the reusable LOANSET tag.

Mobile photos & evidence

Use a mobile phone to capture kit images, sterilizer till-roll printouts, and loan-set photographs by tray and layer at receiving and shipping.

  1. Capture a kit image: Photograph a surgical kit using a mobile phone. Record: Mobile kit photograph. Capture the kit and its instrument layout clearly.; Use the image as a visual reference for that kit.
  2. Assign the kit photo: Keep the captured photograph associated with the corresponding kit. Record: Kit + reference image. Identify the correct kit before assigning the image.; Make the kit image available as a reference within its workflow.
  3. Capture the till roll: Photograph the sterilizer’s physical till-roll printout using the mobile phone. Record: Sterilizer till-roll image. Capture the cycle printout clearly, including its relevant sections.; Check the image is readable before assigning it.
  4. Attach to the load: Assign the captured till-roll image to the corresponding sterilizer load record/report. Record: Load + captured cycle printout. Select the correct load.; Keep the image with that load’s supporting printout documentation.
  5. Receive: tray & layer photos: At loan-set receiving, document the contents of each tray and its individual layers. Record: Receiving photo set by tray / layer. Identify the loan set, tray and layer for each photograph.; Capture each layer before it is moved into the processing workflow.
  6. Ship: tray & layer photos: Before return shipping, photograph the corresponding trays and layers again. Record: Shipping photo set by tray / layer. Record the outgoing condition and contents.; Keep the shipping photographs linked to the same loan set, tray and layer.
  7. Compare & evaluate: Review receiving and shipping images to evaluate what was consumed, missing or changed. Record: Receiving-versus-shipping review. Compare the corresponding tray and layer views.; Evaluate discrepancies and items consumed using the recorded evidence.; Keep the photographic comparison available for reference.
  8. Reference & billing review: Retain the receiving and shipping evidence with the loan-set record for later reference and billing evaluation. Record: Loan-set photo evidence + billing reference. Refer back to the relevant tray and layer photographs.; Use the documented comparison when reviewing consumption and billing.

Missing items & purchasing

Connect missing items discovered at case return, Decontam, Packing or maintenance with investigation, replacement purchasing and resolution.

  1. Capture the missing-item alert: A count mismatch or missing item can be discovered against an OR case, during Decontam, at Packing or in maintenance. Record: Case / item / tray + missing-item record. Retain case, tray/item, expected and received quantities where relevant.; Record the last known location/event, user, time and reason.; Indicate whether a replacement is required.
  2. Investigate & resolve: The missing-item workflow follows the exception until it is located, replaced or otherwise closed. Record: Missing-item status + resolution. Track Investigating, Located, Replaced, Written Off, On Order and Closed.; Review the linked OR case and processing history.; Link replacement requirements to purchasing instead of creating an unrelated order.
  3. Build the request: Purchasing organizes RFP and order documents by instrument and status. Record: RFP / order document. Open or build the relevant request.; Work with the vendor and manufacturer records.
  4. Track progress: Document and line statuses show where purchasing activity stands. Record: Document + line status. Follow draft, sent, partial, ordered, closed, or cancelled documents.; Track line states such as ordered, PO attached, or not available.
  5. Keep the evidence: Order and pricing records keep supporting details with the transaction. Record: PO / invoice + price history. Attach PO or invoice PDFs.; Review instrument pricing history.; Print or open the purchasing document.
  6. Link replacement & closure: Keep the replacement transaction connected to the original missing-item event. Record: Missing event → order → replacement → closure. Retain the RFP/PO, expected arrival and received replacement.; Record the final disposition and resolution of the missing-item case.

Maintenance & repair

Keep an open repair record connected to the kit and prevent it from returning to packing too early.

  1. Identify the kit: Maintenance starts with an identified child kit. Record: Kit + service record. Search or scan the kit.; Confirm that it is out of service.
  2. Control availability: An open maintenance record removes that kit from Packing. Record: Out-of-service state. Record the repair details.; Keep the kit unavailable for packing while maintenance is open.
  3. Manage vendor loop: Repair records follow the kit through shipping and receiving. Record: Vendor repair history. Use Records to review maintenance history.; Record Ship out and Receiving.
  4. Set counters: Kit maintenance setup supports configurable counters and warning points. Record: Maintenance counter setup. Set counter start and warning threshold.; Review current remaining and optional default serial.
  5. Return to service: Closing maintenance returns the kit to service. Record: Closed repair + service availability. Close the record when the kit is back.; The kit becomes available for packing and the counter resets.
  6. Review costs: Maintenance reports support date-range cost review. Record: Maintenance cost report. Choose facility and report dates.; Review maintenance costs and export reporting data.

Audit & recall search

Review assembly details and locate related records by kit, load, patient, or stock location.

  1. Start with a reference: Recall search accepts several identifiers rather than a single starting point. Record: Search reference. Search by assembly UID, kit, code, lot, load, sterilizer, patient, or location.
  2. Narrow the results: Lifecycle filters help focus the assemblies under review. Record: Matching assemblies. Filter packed, loaded, sterilized, quarantine, distributed, recalled, or in-use records.
  3. Open the assembly: Assembly detail brings the identified record into focus. Record: Assembly detail. Open from Audit, Packing, the packed queue, Recall, or Quarantine.; Review the assembly details.
  4. Follow the context: Patient and location references explain allocation and movement. Record: Patient / load / location context. Patient identifies allocation to an OR case.; Location can identify a pack station, sterilizer load, or stock slot.
  5. Review & extract: Search results and audit tables can be exported for follow-up. Record: Trace results + audit extract. Export recall-search results as CSV.; Export the Audit table.; Use authorized assembly detail for patient or location corrections.

Reporting & visibility

Explore reporting across processing, staff activity, GI, OR, exceptions, turnaround and maintenance.

  1. Set the scope: Reports begin with the facility and date range. Record: Facility + reporting period. Select facility, From and To.; Refresh the report data.
  2. Choose the view: The report workspace groups related operational views. Record: Selected reporting view. Overview, packed trays, staff / packing, GI Lab / scopes, and OR cases.; Exceptions, turnaround, maintenance, detailed packing, and processed trays.; Productivity by category and packed queue purge.
  3. Review operations: Each report presents a different part of the recorded workflow. Record: Operational report. Review activity, exceptions, or turnaround for the selected period.; Use the relevant report rather than treating every record as the same lifecycle.; Review outstanding case returns, count mismatches, missing-item states and washer pass/fail history in the configured reporting scope.
  4. Explore analytics: Reporting Analytics opens the full-screen reporting workspace. Record: Analytics workspace. Access the report tabs in a larger workspace.; Review the available data catalog.
  5. Print or export: Report outputs support review outside the on-screen workspace. Record: Printed report / CSV. Print the active report with the browser print dialog.; Export the active report tab as CSV.

Configuration & connections

Set up kit identities, locations, printers, machines, roles and the local interface context.

  1. Structure the catalogue: Facility setup defines kits, instruments, separates and parent / child relationships. Record: Facility kit catalogue. Maintain bills of materials and kit identifiers.; Deactivate or reinstate child kits while retaining history.; Map catalogue items to facility kits and preference cards.
  2. Define the environment: Location and equipment setup provides the choices used in daily workflows. Record: Locations + equipment configuration. Create stock slots, carts, ORs, and workstations.; Configure sterilizer types, cycles, machines and biological requirements.; Register printers and semi-permanent labels.; Configure washers, production/test cycles and washer numbering.
  3. Configure workflows: Facility Case data settings control visible fields and selected permissions. Record: Facility workflow settings. Show or hide OR, GI visit, and loan-set fields.; Configure staff permissions for cycle and load-number changes.; Choose applicable facility workflow options.; Enable direct tray-to-washer, wash tags/baskets, multi-case baskets and washer correction permissions as required.
  4. Set access: User roles determine the menus and actions available to each person. Record: Role-based access. Assign facility and permitted roles.; Use built-in roles or admin-managed custom roles.; Menus follow the signed-in user’s permissions.
  5. Review HL7 intake: The local HL7 interface supplies patient updates and OR bookings. Record: Interface intake log. Review PID patient messages and SUI booking messages.; Cases created from bookings appear on the OR calendar.
  6. Maintain the setup: Saved equipment and configuration support ongoing operation. Record: Configuration + release context. Deactivate machines or cycles for new loads while retaining saved names.; Use Version updates to review releases by area.
START WITH YOUR WORKFLOW

Make readiness
everyone’s business.

Walk through your process and what a connected workflow could look like.

Explore SurgiDat with us ↗

Crawler-visible interactive content

This section expands JavaScript-driven demos and filters so crawlers can index the full workflow text.

mobile-nav-toggle

Opens and closes the main navigation on small screens.

visual-workflow-tour

Graphical multi-topic walkthrough: processing, decontam/wash, OR, stock, GI, loan sets, mobile evidence, purchasing, maintenance, audit search, reporting, admin.

Sterile processing

  1. Receive & reconcile: Receive returns against the OR case and compare expected contents with what physically comes back. Record: OR return + counts + outstanding items
  2. Wash & verify: Scan trays/kits directly or use a wash tag/basket to associate contents with a washer load. Record: Washer load + item-level wash result
  3. Identify the kit: Staff find the correct child kit using the identifiers already attached to it. Record: Kit identity
  4. Pack & count: The packing workflow brings kit contents and assembly recording together. Record: Assembly UID + packing record
  5. Create the load: A new load identifies the machine and cycle for the packed assemblies. Record: Load + linked assemblies
  6. Capture load printout: Use a mobile phone to capture the sterilizer till-roll printout and assign the image to its load. Record: Load + till-roll image
  7. Review the result: Load review separates usable assemblies from failed loads and biological holds. Record: Load result + release / hold state
  8. Read biologicals: Where required, the Qten workflow captures biological setup and final results. Record: Biological record
  9. Put away: Sterile-complete assemblies are assigned to a known stock destination. Record: Assembly + stock location

Decontam, counts & washing

  1. Receive against OR case: A case-linked cart, tray or item scan opens the corresponding OR case and its expected return list. Record: OR case + return session
  2. Reconcile returned counts: Confirm the physical return against the expected case contents; received and outstanding counts remain visible. Record: Expected / received / outstanding quantities
  3. Flag missing case items: Unresolved differences create a visible outstanding-item exception for investigation rather than disappearing when the rest of the case moves forward. Record: Case-linked missing-item alert
  4. Assign wash tag / basket: Group received contents into a controlled wash tag or reusable basket session. Record: Wash grouping + item-to-case lineage
  5. Scan tray to washer: Scan a tray or kit directly to the washer where enabled, or scan a basket/wash tag and then the washer. Record: Tray / basket / tag + washer load
  6. Record wash cycle result: The washer load captures the machine, cycle number and explicit PASS / FAIL result for all included items. Record: Washer + cycle + load result
  7. Fail → rewash required: A failed wash puts the affected items into REWASH REQUIRED and prevents downstream processing until a successful wash. Record: Failed wash + rewash / pass history
  8. Confirm wash at Packing: Packing displays the last washer, cycle, date/time and result before the next packing stage. Record: Confirmed wash + audited correction
  9. Pack & clear the basket: Scan the basket once to list eligible Separates and pack one, some or all into new assemblies. Record: New assemblies + closed basket session

OR & preference cards

  1. Define requirements: Preference cards hold the expected kits and quantities for a surgeon and procedure. Record: Surgeon + procedure requirement
  2. Schedule the case: Staff work from the OR calendar, schedules and picking, or a manually created case. Record: Scheduled OR case
  3. Pick to cart / OR: The pick connects a planned requirement with identifiable assemblies. Record: Case + selected assembly UIDs
  4. Record the case: The actual case list records what was allocated, separately from the preference card. Record: Case allocation record
  5. Receive & count returns: The returned case is reconciled against the items actually allocated to it. Record: Case return + received / outstanding counts
  6. Alert on missing items: A missing-item exception stays linked to the OR case and the affected instrument or tray. Record: OR case + missing-item alert
  7. Review activity: OR case reports and assembly records support subsequent review. Record: OR report + assembly trace

Stock & distribution

  1. Define locations: Locations provide a consistent destination structure across the facility. Record: Location structure
  2. Choose destination: Distribution starts with the place the assemblies are going. Record: Distribution target
  3. Scan & distribute: Assembly scans connect individual sterile-complete items to that target. Record: Assembly location
  4. Reconcile the slot: The Set action supports stock-taking at the selected slot. Record: Slot reconciliation
  5. Search inventory: Stock Management provides one row per assembly UID. Record: Searchable assembly inventory
  6. Review & export: Staff can review stock and open the assembly detail for authorized changes. Record: Stock extract + assembly detail

GI Lab & endoscopy

  1. Configure & register: Facility setup defines visit fields, scope identifiers, checklists and cabinets. Record: Scope register + GI configuration
  2. Load & link visit: TagIT identifies the scope and records its visit context. Record: Scope + visit identity
  3. Complete checks: Core processing checks and simple checklists sit within the TagIT workflow. Record: Processing checks + step times
  4. Verify competency: Optional full competency templates support a more detailed SOP walkthrough. Record: Full competency result
  5. Save & tag: A saved visit creates a cycle record, with hang-tag availability tied to configured checks. Record: Cycle record + hang tag
  6. Store & monitor: Cabinet hooks make storage position and storage life visible. Record: Hook location + storage-life state
  7. Reprocess & reuse: Loading a stored scope back into TagIT returns it to the processing workflow. Record: Next scope cycle
  8. Report & trace: GI reporting supports cycle history and facility-level review. Record: GI report + cycle history

Loan sets & implants

  1. Plan the arrival: The loan-set calendar organizes receiving around the procedure date. Record: Loan calendar
  2. Receive the set: Facility configuration determines which clinical and scheduling fields appear. Record: Loan receiving record
  3. Photograph received layers: Capture receiving photos for every tray and layer in the loan set. Record: Receiving images by tray / layer
  4. Identify & pack: Default receiving uses a reusable LOANSET tag before assembly creation in Packing. Record: Loan tag + assembly UID
  5. Process & use: Loan sets use the regular packing, sterilization and case workflows. Record: Processing + case history
  6. Record return: The loan lifecycle includes the post-use processing path before return. Record: Return-processing history
  7. Photograph shipping layers: Capture the corresponding tray and layer images before the loan set is shipped back. Record: Shipping images by tray / layer
  8. Compare contents & consumption: Compare the receiving and shipping images to evaluate consumed, missing or changed items. Record: Loan-set comparison + billing reference
  9. Sign out: Loan-set sign-out completes the vendor return workflow. Record: Loan sign-out

Mobile photos & evidence

  1. Capture a kit image: Photograph a surgical kit using a mobile phone. Record: Mobile kit photograph
  2. Assign the kit photo: Keep the captured photograph associated with the corresponding kit. Record: Kit + reference image
  3. Capture the till roll: Photograph the sterilizer’s physical till-roll printout using the mobile phone. Record: Sterilizer till-roll image
  4. Attach to the load: Assign the captured till-roll image to the corresponding sterilizer load record/report. Record: Load + captured cycle printout
  5. Receive: tray & layer photos: At loan-set receiving, document the contents of each tray and its individual layers. Record: Receiving photo set by tray / layer
  6. Ship: tray & layer photos: Before return shipping, photograph the corresponding trays and layers again. Record: Shipping photo set by tray / layer
  7. Compare & evaluate: Review receiving and shipping images to evaluate what was consumed, missing or changed. Record: Receiving-versus-shipping review
  8. Reference & billing review: Retain the receiving and shipping evidence with the loan-set record for later reference and billing evaluation. Record: Loan-set photo evidence + billing reference

Missing items & purchasing

  1. Capture the missing-item alert: A count mismatch or missing item can be discovered against an OR case, during Decontam, at Packing or in maintenance. Record: Case / item / tray + missing-item record
  2. Investigate & resolve: The missing-item workflow follows the exception until it is located, replaced or otherwise closed. Record: Missing-item status + resolution
  3. Build the request: Purchasing organizes RFP and order documents by instrument and status. Record: RFP / order document
  4. Track progress: Document and line statuses show where purchasing activity stands. Record: Document + line status
  5. Keep the evidence: Order and pricing records keep supporting details with the transaction. Record: PO / invoice + price history
  6. Link replacement & closure: Keep the replacement transaction connected to the original missing-item event. Record: Missing event → order → replacement → closure

Maintenance & repair

  1. Identify the kit: Maintenance starts with an identified child kit. Record: Kit + service record
  2. Control availability: An open maintenance record removes that kit from Packing. Record: Out-of-service state
  3. Manage vendor loop: Repair records follow the kit through shipping and receiving. Record: Vendor repair history
  4. Set counters: Kit maintenance setup supports configurable counters and warning points. Record: Maintenance counter setup
  5. Return to service: Closing maintenance returns the kit to service. Record: Closed repair + service availability
  6. Review costs: Maintenance reports support date-range cost review. Record: Maintenance cost report

Audit & recall search

  1. Start with a reference: Recall search accepts several identifiers rather than a single starting point. Record: Search reference
  2. Narrow the results: Lifecycle filters help focus the assemblies under review. Record: Matching assemblies
  3. Open the assembly: Assembly detail brings the identified record into focus. Record: Assembly detail
  4. Follow the context: Patient and location references explain allocation and movement. Record: Patient / load / location context
  5. Review & extract: Search results and audit tables can be exported for follow-up. Record: Trace results + audit extract

Reporting & visibility

  1. Set the scope: Reports begin with the facility and date range. Record: Facility + reporting period
  2. Choose the view: The report workspace groups related operational views. Record: Selected reporting view
  3. Review operations: Each report presents a different part of the recorded workflow. Record: Operational report
  4. Explore analytics: Reporting Analytics opens the full-screen reporting workspace. Record: Analytics workspace
  5. Print or export: Report outputs support review outside the on-screen workspace. Record: Printed report / CSV

Configuration & connections

  1. Structure the catalogue: Facility setup defines kits, instruments, separates and parent / child relationships. Record: Facility kit catalogue
  2. Define the environment: Location and equipment setup provides the choices used in daily workflows. Record: Locations + equipment configuration
  3. Configure workflows: Facility Case data settings control visible fields and selected permissions. Record: Facility workflow settings
  4. Set access: User roles determine the menus and actions available to each person. Record: Role-based access
  5. Review HL7 intake: The local HL7 interface supplies patient updates and OR bookings. Record: Interface intake log
  6. Maintain the setup: Saved equipment and configuration support ongoing operation. Record: Configuration + release context