Healthcare · Managed platform (Stanley / AeroScout)

Asset Tracking

Know where your wheelchairs, pumps and mobile equipment are, with the tracking system run for you

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs the Stanley Healthcare AeroScout real-time location system for hospitals, so staff can find mobile equipment and clinical engineering can manage it. AeroScout tags on wheelchairs, infusion pumps and other mobile devices report their location over your Wi-Fi network, and Moraph configures maps, zones, par levels and alerts around your workflows. Moraph monitors the system, manages tag health and changes, and reviews the service with you every month.

The problem it solves

In most hospitals, nurses and transport staff spend part of every shift looking for equipment that is somewhere in the building. Units hoard pumps and wheelchairs so they are not caught short, clinical engineering cannot find devices that are due for preventive maintenance or affected by a recall, and the hospital rents or buys more equipment than it would need if it could see what it has. Where a location system has been installed, it often drifts out of shape: tags go flat, maps fall behind renovations and nobody owns the alerts.

  • Staff search units and storage rooms for equipment that is needed now
  • Devices due for maintenance or affected by a recall are hard to locate
  • Units keep extra equipment because they cannot see what is available
  • Installed tracking systems decay without someone running them

Who uses it

  • Clinical engineering and biomedical teams at hospitals and health systems
  • Nurse managers and unit leaders who need equipment on hand
  • Central equipment distribution and supply chain teams
  • IT and network teams who support the Wi-Fi infrastructure the tags use
  • Facilities and environment of care leaders who answer for equipment management

Requirements it supports

HIPAA Security Rule (45 CFR Part 164, Subpart C)HIPAA Privacy Rule (45 CFR Part 164, Subpart E)CMS Conditions of Participation for hospitals: physical environment (42 CFR 482.41)The Joint Commission Environment of Care standards for medical equipment managementNFPA 99 Health Care Facilities Code

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Stanley Healthcare provides the AeroScout platform, Moraph implements and runs it for your hospital, and your hospital owns the equipment, the network it runs on and the decisions about how equipment is managed.

AreaMoraphStanley Healthcare (AeroScout)Your organization
Licensing and hardwareResells AeroScout software, tags and exciters, or works with what you already own, and tracks quantities against your orderSets licence terms and supplies the software, tags and exciters under its warranty termsAgrees to the vendor's terms and decides what to buy and where to deploy it
Platform availabilityMonitors the system and tells you when an issue affects location or alertsProvides software updates, defect fixes and support to Moraph under its support termsProvides the servers or hosting the agreed deployment needs, unless Moraph hosts them, and keeps a fallback process for finding critical equipment
ConfigurationDesigns the baseline and builds and maintains maps, zones, par levels and alertsProvides the configuration options the platform supportsApproves the baseline and every change to it
Wireless networkSpecifies the network requirements and traces location problems to their causePublishes the network requirements for its tagsOwns and maintains the Wi-Fi network and tells Moraph about planned changes
Tags and excitersRegisters, replaces and retires tags, and installs or arranges installation of excitersRepairs or replaces faulty hardware under its warranty termsGives access to areas for installation and decides which equipment is tagged
MonitoringWatches system health, tag batteries and location accuracy, and escalates issues that need a decisionProvides the system health information the platform recordsDecides on escalated issues
Incident responseTriages issues, restores service under the agreed procedure and supports your investigationFixes defects in the platform itselfLeads any incident affecting patient care or patient information and makes notification decisions
ChangesApplies approved changes, tests them where possible and records themDocuments platform features and changesRequests and approves changes through named approvers
Software updatesReviews release notes and plans and applies updates with your approvalReleases software updates on its own scheduleApproves update timing and any configuration change needed
Equipment management decisionsRecommends tagging, par levels and alert settingsNoneDecides how equipment is managed, maintained and recalled

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of Stanley / AeroScout itself, which belongs to its vendor.

  1. Step 1

    The rollout tracker

    During implementation, each area has a row: network readiness, exciters, tagged equipment and where it stands.

    AreaNetwork checkExcitersDevices taggedAccuracy testStatus
    Building A, floor 3 (example)PassedInstalled142PassedLive
    Building A, floor 4 (example)PassedInstalled118PassedLive
    Emergency department (example)PassedInstalled96Retest neededTesting
    Central equipment storage (example)PassedInstalled210Not startedTagging
    Building B, floor 2 (example)Coverage gapPlanned0Not startedPlanned
    During implementation, each area has a row: network readiness, exciters, tagged equipment and where it stands.

  2. Step 2

    The configuration baseline

    Maps, zones, par levels and alerts are written down and approved by your clinical engineering manager.

    Baseline v2 · Example Health System (fictional)

    Status
    Awaiting approval
    Prepared by
    Moraph RTLS engineer
    Approver
    Clinical engineering manager
    Changes from v1
    4
    Device types tracked
    6

    Changes in this version

    • Add par levels for infusion pumps on two medical units
    • Add exit zone alert at the loading dock, routed to security
    • Add 'needs cleaning' status for wheelchairs
    • Retire zone for a closed storage room
    Maps, zones, par levels and alerts are written down and approved by your clinical engineering manager.

  3. Step 3

    A change request

    Your team asks, your approver approves, and Moraph applies and records the change.

    CR-0427 · New zone for relocated pump storage room

    1. Change requested, with new room number and floor planDistribution lead
    2. Impact assessed: map update and par level moveMoraph RTLS engineer
    3. Change approvedClinical engineering manager
    4. Map and zone updated, accuracy tested in the new roomMoraph RTLS engineer
    5. Change recorded and linked to approvalMoraph RTLS engineer
    6. Change confirmed on the floorDistribution lead
    Your team asks, your approver approves, and Moraph applies and records the change.

  4. Step 4

    Issue triage

    Moraph investigates problems with location or alerts and escalates what needs your decision, with the evidence and a recommendation.

    Emergency department · Devices shown in wrong rooms

    Reported by
    Charge nurse
    Area
    Emergency department (example)
    Devices affected
    14 shown in an adjacent room
    Likely cause
    Access point moved during renovation
    Status
    Escalated to network team

    Recommendation

    • Confirm the new access point location with the network team
    • Recalibrate the area and rerun the accuracy test
    • Add an exciter at the treatment room doorway
    Moraph investigates problems with location or alerts and escalates what needs your decision, with the evidence and a recommendation.

  5. Step 5

    Tag health

    Moraph tracks tags with low batteries or no recent reports and replaces them before equipment drops out of view.

    Device typeTagsLow batteryNot reportingReplaced this monthStatus
    Infusion pumps64012318On plan
    Wheelchairs220496Search requested
    Telemetry monitors150203On plan
    Portable suction units85112On plan
    Bladder scanners24000On plan
    Moraph tracks tags with low batteries or no recent reports and replaces them before equipment drops out of view.

  6. Step 6

    The monthly service review

    Moraph and your team go through what changed, what happened and what is still open.

    Service review · Sample month

    Changes applied
    5, all approved
    Issues raised
    8, 7 closed
    Recall devices not located
    2 of 31
    Tags replaced
    29
    Units below pump par most often
    2

    Actions agreed

    • Search for the two recalled pumps not yet located
    • Review pump par levels with the two units most often short
    • Plan exciter installation for Building B, floor 2
    Moraph and your team go through what changed, what happened and what is still open.

Workflows

The principal workflows

  1. Locate

    AeroScout tags report their position over your Wi-Fi network, with exciters at doorways and in rooms where you need finer accuracy. Staff search for equipment by type or asset number and see where the nearest available device is.

    • Equipment is tagged and registered against its asset record
    • Tags report location to the AeroScout software over your Wi-Fi network
    • Staff search by device type, asset number or unit
    • The map shows the nearest devices and their status
    • Searches that fail are logged for Moraph to investigate

  2. Balance

    Par levels are set for each unit and storage area, so the system shows where a unit is short or holding more than it needs, and central distribution can move equipment before anyone has to search.

    • Par levels agreed with each unit and with central distribution
    • AeroScout compares the equipment in each zone against its par level
    • Shortfalls and surpluses are shown to the distribution team
    • Equipment is moved and the change is visible on the map
    • Par levels are reviewed with unit leaders at the service review

  3. Maintain

    Clinical engineering finds devices due for preventive maintenance or named in a recall, and devices tagged as needing cleaning or repair are kept apart from those ready for use.

    • Maintenance due dates and recall lists come from your maintenance system
    • AeroScout shows where each affected device was last located
    • Technicians collect the devices and record the work in your maintenance system
    • Devices returned to service show as available again
    • Devices that cannot be found are listed for follow-up

  4. Operate

    Moraph monitors the system, replaces and re-registers tags, keeps maps and zones in step with your buildings, applies approved changes and reports on the service.

    • Moraph watches system health, tag batteries and location accuracy
    • Issues are triaged and escalated to your team where a decision is needed
    • Changes are requested by your team and approved by your named approver
    • Moraph applies and records each change
    • The monthly service review covers changes, issues and open actions

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Clinical engineering manager

Director of clinical engineering, biomedical engineering manager, HTM manager

Owns the tracking service for the hospital and decides which equipment is tracked, how it is managed and which changes are made.

Sees

  • All tracked equipment, its location, status and utilization
  • Maintenance and recall locating results, including devices not found
  • Tag health, change history and service reports
  • Issues Moraph has escalated, with recommendations

Does

  • Approves the configuration baseline and changes to it
  • Decides which device types are tagged and how they are registered
  • Runs maintenance and recall searches and assigns follow-up
  • Approves zone alerts and who receives them
  • Attends the monthly service review and agrees actions
  • Requests evidence for surveys and audits

Cannot

  • Approve a change they requested themselves, where a second approver is named
  • Edit or delete the change history
Approvals
Approves configuration, zone, alert and par level changes; changes they request themselves are approved by a second named approver.
Notified about
Changes waiting for approval, escalated issues, devices on a recall list that cannot be located, and tag health problems that need a decision.

Nurse or unit manager

Nurse manager, charge nurse, unit director, department supervisor

Makes sure the unit has the equipment it needs and that staff can find it.

Sees

  • Equipment on and near their unit, with its status
  • Their unit's par levels and current counts
  • Utilization reports for their unit

Does

  • Searches for equipment and directs staff to it
  • Marks equipment as needing cleaning or repair
  • Requests changes to par levels or zones for the unit
  • Reports equipment that is shown in the wrong place

Cannot

  • Change maps, zones, alerts or par levels directly
  • Register or remove tags
Approvals
Par level and zone changes they request are approved by the clinical engineering manager, with central distribution consulted.
Notified about
Par level shortfalls on their unit, where your configuration enables them, and the outcome of their requests.

Equipment distribution lead

Central equipment distribution supervisor, supply chain coordinator, transport lead

Moves equipment around the hospital so each unit stays at its par level and devices go back for cleaning and maintenance.

Sees

  • Par levels and counts across all units and storage areas
  • Equipment status, including devices waiting for cleaning
  • Utilization by device type and area

Does

  • Works the par level shortfall and surplus lists
  • Collects equipment for cleaning and returns it to service
  • Updates equipment status as devices move through processing
  • Proposes par level changes based on use

Cannot

  • Approve par level changes
  • Change maps, zones or alert routing
Approvals
Par level changes they propose are approved by the clinical engineering manager.
Notified about
Shortfalls and surpluses against par, and equipment marked as needing cleaning.

IT network administrator

Wireless network engineer, network administrator, infrastructure manager

Keeps the Wi-Fi network the tags rely on in good order and coordinates network changes that could affect location.

Sees

  • Location system health and accuracy test results
  • Changes planned to the tracking system that involve the network
  • Issues Moraph has traced to the wireless network

Does

  • Provides network access and settings the AeroScout system needs
  • Notifies Moraph of planned access point and network changes
  • Works network issues Moraph escalates
  • Approves network-related parts of a change

Cannot

  • Change tracking maps, zones, alerts or equipment records
  • Approve changes to how equipment is managed
Approvals
Approves the network parts of changes; the clinical engineering manager approves the rest.
Notified about
Location accuracy problems traced to the network and changes that need network work.

Moraph RTLS engineer

Moraph RTLS engineer, Moraph managed platform engineer

Builds and maintains the AeroScout configuration for the hospital and keeps tags, maps and zones working.

Sees

  • AeroScout configuration, maps, zones, alerts and tag records
  • System health, tag battery and reporting status
  • Approved change requests and the configuration baseline

Does

  • Applies approved changes to maps, zones, par levels and alerts
  • Registers, replaces and retires tags
  • Runs location accuracy tests and records the results
  • Triages system issues and escalates those that need a decision
  • Plans configuration work needed for AeroScout software updates

Cannot

  • Apply a change that has not been approved, except under the agreed emergency procedure
  • Approve their own changes
  • Decide which equipment is tracked or how it is managed
Approvals
Every change they apply is approved in advance by your named approver, or reported straight away when made under the emergency procedure.
Notified about
System health alerts, tags that stop reporting, and approved changes ready to apply.

Moraph service manager

Moraph service manager, Moraph customer success lead

Runs the service relationship, tracks requests and issues and reports on how the service is performing.

Sees

  • Requests, issues and changes and their status
  • Service reports, tag health and utilization summaries
  • Open actions from earlier service reviews

Does

  • Prepares and chairs the monthly service review
  • Tracks requests and escalations through to closure
  • Coordinates with the vendor on platform defects and service notices
  • Prepares evidence packs your team requests

Cannot

  • Change the AeroScout configuration
  • Approve changes on your behalf
Approvals
None; their reports and minutes are accepted by your clinical engineering manager.
Notified about
Escalations, overdue requests and vendor service notices affecting you.

Auditor or surveyor (read-only)

Internal auditor, compliance officer, accreditation surveyor (under temporary access)

Reviews equipment records, changes and service evidence without being able to change anything.

Sees

  • Equipment records and status within the scope granted
  • Change history and approvals
  • Service reports and evidence packs

Does

  • Reads records and reports within their scope
  • Exports evidence they have been given access to, with each export logged

Cannot

  • Change, approve or delete anything
  • Keep access after it expires
Approvals
Their access is approved by the clinical engineering manager, with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionClin. eng.Unit managerDistributionNetwork adminMoraph eng.Moraph serviceAuditor
Search for and locate equipmentFullOwn work onlyFullNo accessFullNo accessView only
Update equipment statusFullOwn work onlyFullNo accessFullNo accessNo access
Request a configuration changeFullOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo access
Apply a configuration changeApprovesNo accessNo accessNo accessFullNo accessNo access
Change par levelsApprovesNo accessNo accessNo accessFullNo accessNo access
Change zones and alert routingApprovesNo accessNo accessNo accessFullNo accessNo access
Register, replace or retire tagsApprovesNo accessNo accessNo accessFullNo accessNo access
Run maintenance and recall searchesFullNo accessView onlyNo accessFullNo accessView only
Approve network-related changesView onlyNo accessNo accessApprovesView onlyNo accessNo access
Grant access to the tracking systemApprovesNo accessNo accessNo accessFullNo accessNo access
View change history and service reportsView onlyNo accessNo accessView onlyView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph engineers apply changes; your hospital approves them. Nobody approves a change they requested themselves when a second approver is named.
  • Moraph staff use named, individual accounts in AeroScout with only the administrative rights the service needs. There are no shared administrator accounts.
  • Roles are agreed during implementation and can be limited by building, unit or department, so a unit manager sees the equipment that matters to their unit.
  • Every change is recorded with its request and approval in Moraph's change record. Auditors and surveyors get read-only evidence with a defined scope and end date.

Features

What it does

Equipment search

AeroScout shows staff where a device type or a specific asset is, on a floor map, with the nearest available units first.

Room and doorway accuracy

Exciters placed at doorways and in selected rooms give room-level or chokepoint location where Wi-Fi alone is not precise enough, in the areas you choose.

Par level management

Each unit and storage area has agreed par levels, and AeroScout shows where equipment is short or in surplus so it can be moved.

Zone alerts

AeroScout raises alerts when tagged equipment enters or leaves a defined zone, such as a building exit or a loading dock, routed to the people you choose.

Maintenance and recall locating

Devices due for preventive maintenance or named in a recall are matched to their last known location so technicians can collect them.

Equipment status

Devices can be marked as in use, ready, needs cleaning or out for repair, so staff are not sent to equipment that cannot be used.

Utilization reporting

How much each device type is used, where it spends its time and how many sit idle, to inform purchasing and rental decisions.

Tag health management

Moraph watches tag battery levels and tags that have stopped reporting, and replaces or re-registers them as part of the service.

Map and zone upkeep

Floor plans, zones and exciter placements are kept up to date as units move or are renovated, under your change process.

Location accuracy checks

Moraph tests location accuracy in agreed areas after changes to the building or the Wi-Fi network and records the results.

Maintenance system link

Asset records are kept consistent with your computerized maintenance management system, so tags, serial numbers and asset numbers match.

Monthly service review

Changes, issues, tag health, utilization and open actions reviewed with your clinical engineering and nursing leads.

Integrations

How it connects to your systems

Connects toHowWhat flows
Wi-Fi networkAeroScout tags report location through your existing wireless network, set up to the vendor's requirements during implementation.In: tag location and status messages over your network.
Computerized maintenance management systemAsset numbers, device types, maintenance due dates and recall flags are kept consistent with your maintenance system, by file or interface where the system supports it.In: asset records, maintenance due dates and recall lists. Out: last known location.
Floor plansBuilding floor plans are loaded as maps and updated when units move or are renovated.In: floor plan drawings from your facilities team.
Alert deliveryZone and par level alerts are sent by email or to the messaging or paging tools your configuration supports.Out: alerts to the people and groups you choose.
Single sign-onStaff sign in to the AeroScout software through your identity provider where the deployment supports it.In: user identity and group membership.
Reporting and data warehouseUtilization and location history can be exported to your reporting tools for capital planning.Out: utilization and location history extracts.
Moraph service recordsRequests, changes, issues and service reviews are tracked in Moraph's service records and available to your team.Out: change, ticket and service review records.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Named Moraph administrators

Moraph staff work in AeroScout with individual accounts and only the administrative rights the service needs; there are no shared accounts.

Role-based access

What each person at your hospital and at Moraph can see and do follows their role; requesting a change is separate from approving it.

Patient information

The service tracks equipment, not people. Where location data could be linked to a patient, it is handled as protected health information under a business associate agreement.

Complete audit trail

Moraph's change record links every configuration change to its request and approval, alongside the activity AeroScout records.

Encryption and keys

Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Audited company-wide

Moraph is audited to SOC 2 Type II and ISO/IEC 27001 across the company, including the teams that run this service. The vendor's own commitments cover the platform.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Equipment

Utilization by device type

For clinical engineering, supply chain, finance

How much each tracked device type is in use, idle or out of service, and where it spends its time.

Break down by
Device type, Unit, Period, Status
Delivered as
AeroScout reports; monthly PDF from Moraph
Used for
Deciding whether to buy, rent or redistribute equipment.

Par level performance

For nurse managers, distribution lead, clinical engineering

How often each unit and storage area was below or above its par level for each device type.

Break down by
Unit, Device type, Period, Shortfall or surplus
Delivered as
AeroScout reports; monthly PDF from Moraph
Used for
Adjusting par levels and distribution rounds.

Maintenance and recall locating

For clinical engineering

Devices due for maintenance or named in a recall, where they were last located, and which have been found.

Break down by
Work type, Device type, Location found, Not located
Delivered as
On request; CSV export
Used for
Completing maintenance and recall work and following up devices that cannot be found.

Service operations

Tag health

For clinical engineering, Moraph service manager

Tags with low batteries, tags that have stopped reporting and tags replaced in the period.

Break down by
Device type, Unit, Battery status, Last report
Delivered as
Monthly PDF; CSV export
Used for
Keeping tagged equipment visible and planning tag replacement.

Change log

For clinical engineering, auditors

Every change to maps, zones, par levels, alerts and tags, with who requested, approved and applied it.

Break down by
Change type, Requester, Approver, Date
Delivered as
Live view in Moraph's service records; CSV and PDF export
Used for
Showing that changes were requested, approved and recorded.

Requests and issues

For clinical engineering, Moraph service manager

Requests and issues raised, their status, and how each was resolved or escalated.

Break down by
Type, Unit, Status, Period
Delivered as
Live view in Moraph's service records; monthly PDF
Used for
Tracking open work and spotting recurring problems.

Location accuracy tests

For clinical engineering, IT network team

Results of accuracy tests in agreed areas, when they were run and what was changed in response.

Break down by
Area, Test date, Result, Cause
Delivered as
PDF after each test
Used for
Confirming that location is reliable after building or network changes.

Alerts

Zone alert activity

For clinical engineering, security, unit leaders

Zone alerts raised, who received them and how they were handled.

Break down by
Zone, Device type, Recipient, Period
Delivered as
AeroScout reports; CSV export
Used for
Checking that alerts reach the right people and tuning those that are not useful.

Escalated issues

For clinical engineering manager

Issues Moraph escalated for a decision, the recommendation given and the decision made.

Break down by
Issue type, Date, Decision, Status
Delivered as
Live view; monthly PDF
Used for
Making sure escalated issues are decided and closed.

Survey and audit

Equipment evidence pack

For compliance, accreditation and audit teams

Selected equipment records, maintenance locating results, change history and service reviews for a defined period.

Break down by
Period, Device type, Record type
Delivered as
On request; PDF and CSV
Used for
Answering survey and audit requests for equipment management evidence.

Service review summary

For clinical engineering and nursing leadership

The month's changes, issues, tag health, utilization highlights and agreed actions.

Break down by
Month, Topic, Action owner
Delivered as
PDF after each service review
Used for
Keeping leadership informed and holding both sides to agreed actions.

Exports, access and evidence

  • Service reports are prepared by Moraph from AeroScout reports and from Moraph's own change and ticket records.
  • AeroScout's own reports remain available in the software to the staff you authorize.
  • Reports respect each viewer's role: unit managers see their own units, and auditors see only the evidence within their scope.
  • Utilization and location history can be exported to your data warehouse for capital planning alongside other equipment data.
  • Requesting and exporting an evidence pack is itself recorded, so you can show what was given to whom.

Deployment

Where and how it runs

Licences and hardware through Moraph

Moraph resells AeroScout software, tags and exciters and runs the system as one service, subject to the vendor's terms.

Your existing AeroScout system

If you already own AeroScout, Moraph reviews the current configuration and tag estate against a new baseline and takes over its operation.

Co-managed

Your clinical engineering team keeps some tasks, such as tagging new equipment, and Moraph runs the rest; the split is written into the responsibilities for the service.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We review your floor plans, Wi-Fi coverage, equipment inventory and maintenance system with clinical engineering, nursing and IT, and agree which device types and areas come first.

Network and site assessment

We check your wireless network against the vendor's requirements and identify the areas that need exciters for room or doorway accuracy.

Baseline design

Maps, zones, par levels, equipment statuses and alerts are designed with your teams and approved by your clinical engineering manager.

Installation and tagging

Exciters are installed and equipment is tagged and registered against its asset record, area by area, with your staff giving access.

Accuracy testing and training

Location accuracy is tested in each area before it goes live, and unit staff, distribution and clinical engineering are trained on their own tasks.

Handover to operations

Change process, approvers, escalation contacts, fallback procedures and reporting are agreed, and the service moves into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Stanley Healthcare. The vendor provides the AeroScout platform, and its own service commitments, roadmap, maintenance and outages apply.
  • AeroScout software, tags and exciters are subject to the vendor's licence and warranty terms.
  • Location accuracy depends on your Wi-Fi network and on where exciters are installed. Areas without exciters show a less precise location.
  • Moraph does not own or run your wireless network; network problems are fixed by your network team or its provider.
  • Only tagged equipment can be located. Tags can be removed or damaged, and devices whose tags have stopped reporting show their last known location.
  • The service tracks equipment. Patient and staff tracking, infant protection and hand hygiene monitoring are not included unless agreed separately.
  • Moraph does not perform maintenance on medical devices or decide how they are managed, maintained or recalled; your clinical engineering team does.
  • The tracking system is not a replacement for your maintenance management system, which stays the record of maintenance work.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Pick two device types your staff search for most and ask how they would be tagged, located and kept at par
  2. Review your Wi-Fi coverage with Moraph and identify areas that would need exciters
  3. Walk through a recall search from list to located devices to follow-up on those not found
  4. Review a sample configuration baseline and change request
  5. Ask how tag batteries and non-reporting tags are tracked and replaced
  6. Confirm the split of responsibilities between Moraph, the vendor, your network team and clinical engineering

Questions

Frequently asked questions

Do we buy AeroScout from Moraph or from the vendor?

Either. Moraph can resell the software, tags and exciters, or run a system you already own. In both cases the vendor's terms apply.

Does it track patients or staff?

This service tracks equipment. Patient or staff tracking raises different privacy and workflow questions and would be scoped separately.

Who changes our maps, zones and par levels?

Named Moraph engineers, under change requests your approver has approved. Emergency actions follow a procedure agreed with you and are reported straight away.

What happens if the location system is down?

Moraph tells you and works to restore service, and the vendor's own support commitments apply to platform defects. Your fallback process for finding critical equipment, agreed during implementation, applies in the meantime.

How is it priced?

Software, tags and exciters are priced under the vendor's terms, and the managed service and implementation are quoted separately. See Working with Moraph for what drives a quotation.

Can we take the service back in-house?

Yes. The system and its configuration are yours; at the end of the agreement Moraph hands over the baseline, documentation and change history and removes its administrator accounts.

Next steps

Evaluate Asset Tracking

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Asset Tracking guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Asset Tracking support guide.

Related products