---
mi_id: MILV-fr-MIMR-node_fa547d2
type: market_report
canonical_url: "https://www.pheonixresearch.com/fr/market-report/global-healthcare-security-systems-market/"
md_url: "https://www.pheonixresearch.com/fr/market-report/global-healthcare-security-systems-market.md"

schema:
  "@type": Dataset
  "@id": MILV-fr-MIMR-node_fa547d2
  url: "https://www.pheonixresearch.com/fr/market-report/global-healthcare-security-systems-market/"
  inLanguage: fr
  translationOfWork:
    "@id": MIMR-node_fa547d2
    url: "https://www.pheonixresearch.com/healthcare/healthcare-services/market-report/global-healthcare-security-systems-market/"
  title: "Marché mondial des systèmes de sécurité de santé, par type (système de détection d'intrusion, système de vidéosurveillance, étiquettes RFID, protection périmétrique, systèmes de contrôle d'accès, systèmes de contrôle d'accès électronique, alarme de sécurité, systèmes d'inspection de véhicules, système de sécurité pour nouveau-nés, systèmes de détection, systèmes de notification d'urgence/duress, détecteurs de métaux et détecteurs d'explosifs, systèmes de vidéosurveillance, autres), par application (documents, suivi des dispositifs médicaux, surveillance, suivi du matériel chirurgical, suivi des fichiers de données, suivi des patients, autres), par utilisateur final (pharmacie, centres de diagnostic, hôpital, laboratoires, cliniques, autres), par géographie (Europe, Amérique du Nord, Asie-Pacifique, Moyen-Orient et Afrique, Amérique latine) – Croissance, opportunités et prévisions jusqu'en 2028"
  description: "Analyse complète du marché des systèmes de sécurité pour les soins de santé couvrant la taille, la part, les moteurs de croissance, les acteurs clés et les prévisions jusqu'en 2028."
  datePublished: "2024-01-13T14:10:01+00:00"
  dateModified: "2026-11-20T04:34:16+00:00"
  keywords:
    - Rapport sur le marché des systèmes de sécurité pour les soins de santé 2028
    - "Taille de l'industrie des systèmes de sécurité pour les soins de santé 2028"
    - TCAC des systèmes de sécurité pour les soins de santé 2028-2028
    - Part de marché des systèmes de sécurité pour les soins de santé par acteur
    - Prévision des revenus des systèmes de sécurité pour les soins de santé
    - Tendances du marché des systèmes de sécurité pour les soins de santé
    - Analyse des systèmes de sécurité pour les soins de santé
    - Perspectives des systèmes de sécurité pour les soins de santé 2028
  isPartOf:
    - id: MILV-fr-MISG-node_2419cd8
      type: CollectionPage
      url: "https://www.pheonixresearch.com/fr/healthcare/healthcare-services/"
      name: Services de santé
    - id: MILV-fr-MIIN-node_50b4dbf
      type: CollectionPage
      url: "https://www.pheonixresearch.com/fr/healthcare/"
      name: Industrie de la santé
    - id: MIWS-root
      type: WebSite
      url: "https://www.pheonixresearch.com/"
      name: Pheonix Research
  mentions:
    - id: MIEN-node_4b154fe0
      type: Organization
      url: "https://www.johnsoncontrols.com"
      name: Johnson Controls
      sameAs:
        - "https://www.wikidata.org/wiki/Q667865"
    - id: MIEN-node_c6918569
      type: Organization
      url: "https://www.honeywell.com"
      name: Honeywell International
      sameAs:
        - "https://www.wikidata.org/wiki/Q898208"
    - id: MIEN-node_a100c770
      type: Organization
      url: "https://www.motorolasolutions.com"
      name: Motorola Solutions
      sameAs:
        - "https://www.wikidata.org/wiki/Q634815"
    - id: MIEN-node_2f28a4b8
      type: Organization
      url: "https://www.boschsecurity.com"
      name: Robert Bosch (Bosch Security and Safety Systems)
      sameAs:
        - "https://www.wikidata.org/wiki/Q226327"
    - id: MIEN-node_b050eeaf
      type: Organization
      url: "https://www.siemens.com"
      name: Siemens
      sameAs:
        - "https://www.wikidata.org/wiki/Q81230"
    - id: MIEN-node_df1fdd4a
      type: Organization
      url: "https://www.securitas.com"
      name: Securitas
      sameAs:
        - "https://www.wikidata.org/wiki/Q662174"
    - id: MIEN-node_a4db1801
      type: Organization
      url: "https://www.adt.com"
      name: ADT Inc.
      sameAs:
        - "https://www.wikidata.org/wiki/Q290680"
    - id: MIEN-node_ff300e4c
      type: Organization
      url: "https://www.nedap.com"
      name: Nedap
      sameAs:
        - "https://www.wikidata.org/wiki/Q1479312"
    - id: MIEN-node_3f571dd7
      type: Organization
      url: "https://www.ascom.com"
      name: Ascom
      sameAs:
        - "https://www.wikidata.org/wiki/Q663942"
    - id: MIEN-node_897e7020
      type: Organization
      url: "https://www.zebra.com"
      name: Zebra Technologies
      sameAs:
        - "https://www.wikidata.org/wiki/Q2443609"
    - id: MILV-fr-MIMR-node_67a8248
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/semiconductor-electronics/data-center-infrastructure/market-report/india-video-surveillance-market/"
      name: "??India - Analyse de la part et de la taille du marché de la vidéosurveillance 2025-2033"
    - id: MIMR-node_2521e41
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/market-report/global-smartphone-mobile-credential-market/"
      name: "Analyse de la taille et de la part du marché mondial des lecteurs de pièces d'identité pour smartphones 2025-2033"
    - id: MILV-fr-MIMR-node_5d1d310
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/information-technology/cybersecurity-software/market-report/global-security-orchestration-automation-and-response-soar-market/"
      name: "Rapport sur le marché mondial de l'orchestration, de l'automatisation et de la réponse à la sécurité (SOAR), taille et prévision 2026-2033"
    - id: MILV-fr-MIMR-node_6dbd18e
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/healthcare/medical-devices/market-report/global-electronic-medical-records-market/"
      name: "Rapport sur le marché mondial des dossiers médicaux électroniques (EMR), taille et prévision 2026-2033"
    - id: MILV-fr-MIMR-node_e54cd85
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/healthcare/healthcare-services/market-report/global-healthcare-revenue-cycle-management-market/"
      name: "Rapport sur le marché mondial de la gestion du cycle des revenus de la santé, taille et prévision 2026-2033"
    - id: MIMR-node_e9b95aa
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/market-report/india-homeland-security-market/"
      name: "Marché de la sécurité intérieure en Inde, par type (sécurité des frontières, sécurité aérienne, sécurité maritime, sécurité des infrastructures critiques, cybersécurité, sécurité CBRN (chimique, biologique, radiologique et nucléaire), application de la loi et collecte de renseignements, et autres), par système (système de renseignement et de surveillance, système de détection et de surveillance, système d'armes, système de contrôle d'accès, modélisation et simulation, système de communication, plateforme, système de sauvetage et de récupération, système de commandement et de contrôle, système de contre-mesures et autres), par utilisation finale (secteur public et secteur privé), par région (Nord, Sud, Ouest et Est), par État (Delhi, Mumbai, Telangana, Chennai, Punjab et autres) - Analyse des tendances et prévisions jusqu'en 2027"
    - id: MIMR-node_775965a
      type: Dataset
      url: "https://www.pheonixresearch.com/fr/market-report/biometric-technologies-market/"
      name: "Part de marché des technologies biométriques mondiales, tendances, taille, acteurs, statistiques, faits, opportunités et prévisions (2024-2031)"
    - id: MIMR-node_b9c0a0c
      type: Dataset
  about:
    - "@type": Thing
      name: Market Intelligence
      mi_id: "MILV-fr-MIMR-node_fa547d2#intelligence"
    - "https://www.wikidata.org/wiki/Q1901028"
  base_year: 2025
  forecast_year: 2033
  value_base_year: 20.21
  value_forecast_year: 49.67
  value_cagr: 11.90
  value_currency: USD
  value_unit_scale: Billion

acf:
  base_year: 2025
  forecast_year: 2033
  value_base_year: 20.21
  value_forecast_year: 49.67
  value_cagr: 11.90
  value_currency: USD
  value_unit_scale: Billion
  coverage_type: Global
  coverage_name: "North America, Europe, Asia Pacific, Middle East & Africa, South America"
  competitive_intensity_level: high
  market_structure_type: fragmented
  tier1_player_count: 8
  investment_trend_direction: rising
  capital_intensity_level: low
  recent_mna_activity: yes
  overall_market_risk_level: moderate
  geopolitical_exposure_level: moderate
  substitution_risk_level: moderate
  regulatory_complexity_level: high
  approval_pathway_structure: compliance_driven
  innovation_intensity_level: high
  technology_maturity_stage: growth
  patent_activity_level: moderate
  supply_chain_complexity_level: moderate
  distribution_structure: distributor_led
  primary_operational_model: hybrid
  toc: "<p style=\"text-align: center;\">[wpforms id=\"87321\" title=\"true\" description=\"true\"]</p>"
  competitive_landscape_content: "<h2>3. Competitive landscape: three positions, no leader, and the trap in the middle</h2>

<p>No participant in this market holds a double-digit share of global healthcare security revenue, and Pheonix Research estimates that the ten largest together hold roughly a third of it. That is unusual for a market of this size, and it is a direct consequence of the value chain described in Chapter 1: the buyer purchases an assembled, commissioned, locally warranted system, so scale is local even when the product is global. A hospital in Manchester and a hospital in Manila may run the same video management platform and be served by firms that never compete with each other.</p>

<p>Within that fragmentation, competitors occupy three distinct positions, and the strategic mistake to make is to confuse them.</p>

<h3>Position one: the platform owners</h3>

<p>Johnson Controls, Honeywell, Siemens, Robert Bosch, Motorola Solutions through its video security business, and Schneider Electric. Each owns a piece of the software stack, often the panel or camera hardware, and frequently the service arm as well. Their structural problem is channel conflict: the integrator that specifies the platform is also the entity the platform owner competes with when it bids the service contract directly. In large health systems this conflict is manageable because the buyer wants a single accountable party. In single-site hospitals it is corrosive, because the integrator's rational response is to specify a platform it can control.</p>

<h3>Position two: the services and guarding companies</h3>

<p>Securitas, which acquired Stanley Healthcare's healthcare security business and now sells infant protection, asset tracking and monitoring inside a guarding relationship; ADT through its commercial and healthcare work; and the large guarding groups that bundle technology into labour contracts. Their economics are labour economics. The technology is a means of winning and retaining a multi-year service agreement, and their pricing power comes from the contract structure rather than from the device. They are the most likely winners of the managed-services layer and the least likely to lead on analytics.</p>

<h3>Position three: the clinical-workflow specialists</h3>

<p>Nedap, Ascom and Zebra, alongside a set of smaller firms in real-time location and infant protection. Their products are small, integrated deep into nursing workflow, and replaced only when a hospital changes its clinical system. This is the smallest position by revenue and the stickiest by account tenure. Their weakness is breadth: they solve one workflow beautifully and cannot be the accountable party for an entire estate.</p>

<table>
<thead>
<tr><th>Company</th><th>Primary position</th><th>Healthcare security relevance</th><th>Wikidata</th></tr>
</thead>
<tbody>
<tr><td>Johnson Controls</td><td>Platform owner</td><td>Access control, video, intrusion; large installed estate across health systems</td><td>Q667865</td></tr>
<tr><td>Honeywell International</td><td>Platform owner</td><td>Access control, video and building integration; strong in acute care retrofits</td><td>Q898208</td></tr>
<tr><td>Motorola Solutions</td><td>Platform owner</td><td>Video security and analytics; body-worn and command software in hospital systems</td><td>Q634815</td></tr>
<tr><td>Robert Bosch (Bosch Security and Safety Systems)</td><td>Platform owner</td><td>Cameras, conference and evacuation systems; strong in European tenders</td><td>Q226327</td></tr>
<tr><td>Siemens</td><td>Platform owner</td><td>Building and access integration inside a wider hospital technology estate</td><td>Q81230</td></tr>
<tr><td>Securitas</td><td>Services and guarding</td><td>Infant protection, asset tracking, monitoring inside guarding contracts</td><td>Q662174</td></tr>
<tr><td>ADT Inc.</td><td>Services and guarding</td><td>Monitoring, intrusion and commercial security with healthcare accounts</td><td>Q290680</td></tr>
<tr><td>Nedap</td><td>Clinical-workflow specialist</td><td>Identification and infant/patient protection; deep European base</td><td>Q1479312</td></tr>
<tr><td>Ascom</td><td>Clinical-workflow specialist</td><td>Alerting, duress and nurse call convergence on one handset</td><td>Q663942</td></tr>
<tr><td>Zebra Technologies</td><td>Clinical-workflow specialist</td><td>Real-time location, patient and asset visibility, handheld identity</td><td>Q2443609</td></tr>
</tbody>
</table>

<p><em>Table 4 — Ten credible players across three positions. Wikidata identifiers verified against the Wikidata query service for this edition. Presence of a company in this table is not an estimate of market share.</em></p>

<h3>The trap in the middle</h3>

<p>Fragmentation is usually described as a benefit to buyers, and in this market it is only half true. The practical consequence at estate level is what our interviews with facilities and security directors describe repeatedly: a mid-sized acute hospital running somewhere between ten and fifteen separate systems — video from one vendor, access from another, the intruder alarm from a local firm, nurse call from a clinical supplier, the infant tag system from a specialist, screening lanes from a third party, and three separate monitoring applications, each with its own login and its own idea of an incident record. The buyer's stated priority in these conversations is rarely more capability. It is fewer logins and one incident record.</p>

<p>That is the demand behind the 15.72 per cent growth we model for integrated software, and it is a demand the platform owners are better placed to meet than any other position — provided they can price it as a subscription carrying an evidence function, rather than as a licence attached to a hardware discount. The services companies can meet it too, but only by integrating competitors' products, which is a business they are structurally capable of running and culturally less inclined to invest in.</p>

<h3>What the competitive map means for a buyer</h3>

<p>The question that separates these positions is not \"who has the best technology\". It is \"who will produce the network map in twelve months, and at what price\". A platform owner will answer with a feature list. A guarding company will answer with a service credit. A clinical-workflow specialist will answer with an integration diagram. The buyer who asks the question in that form will discover in one meeting which of the three has understood the market this report describes — and will usually find that the answer differs between their emergency department, their behavioural health unit and their pharmacy.</p>

<p>Our own reading is that competitive intensity rises rather than falls over the forecast window, because the fastest-growing layers — screening and integrated software — have low barriers to entry on the device side and high barriers on the evidence side. That combination produces a market with many entrants, rapid consolidation among the small ones, and no leader: exactly the structure we have assigned it, and exactly the structure in which the buyer's procurement discipline matters more than the vendor's brand."
  value_chain_content: "<h2>1. Value chain and margin structure: the thinnest margin owns the customer</h2>

<p>In most markets the company closest to the customer earns the best margin. Healthcare security inverts that. The relationship sits with a systems integrator whose net margin is usually in the mid single digits, while the software it installs earns seventy per cent gross and the manufacturer of the camera inside the housing earns a fraction of the project value. That inversion is not an accident of competition. It is a consequence of what the buyer is actually purchasing: a documented, commissioned, auditable system, assembled on site, by people who will still be answering the phone in year four.</p>

<p>Five layers carry the value, and each behaves differently.</p>

<h3>Layer one: device and sensor manufacturers</h3>

<p>Cameras, readers, intrusion panels, RFID tags, duress badges and screening lanes. This is where price deflation is most visible and least important. Image sensors and system-on-chip silicon are consumer-electronics volume; a mid-range camera in 2026 does what a premium camera did in 2019 for materially less, and the same curve has reached access readers and detection lanes. Deflation here does not shrink the market, because the buyer does not want a cheaper camera — it wants more coverage of more space, and the budget freed by falling unit prices is immediately spent on additional endpoints. That is why endpoint count grows 7.71 per cent while hardware value grows 10.18 per cent: more units, more analytics per unit, and a rising services tail attached to each.</p>

<h3>Layer two: platform software</h3>

<p>Video management, access control, visitor management and the physical security information management layer that fuses them. Gross margins here are in the seventy to eighty-five per cent band, but the software is almost never sold on its own in healthcare. It is bundled into a project price, and the licence is often the part the integrator discounts to win the hardware. Software only becomes a genuine margin pool when it is sold as a subscription with an evidence function attached — a compliance dashboard, an incident module, a retention policy that can be shown to an auditor.</p>

<h3>Layer three: clinical integration</h3>

<p>This is the layer outsiders underestimate and the reason a hospital is not a shopping centre with beds. The access control system must talk to the admission-discharge-transfer feed so that a discharged patient's wristband stops opening a ward door. The duress badge must land on the same screen as the nurse call. The infant protection tag must reconcile against the maternity census. The pharmacy cabinet must log to the same identity as the door. Once the credential is the identity and the identity sits in the clinical record, replacement stops being a procurement decision and becomes a re-credentialing and re-validation project — which is why switching costs in this layer are the highest in the entire chain, and why the clinical-workflow specialists hold accounts for a decade or more.</p>

<h3>Layer four: integration and commissioning</h3>

<p>The integrator designs, installs, commissions and warrants the system. Our channel interviews put gross margin at twelve to twenty-two per cent and net margin at three to six per cent on healthcare work, which is thin for the risk carried: a mis-configured door in a behavioural health unit is a ligature and elopement exposure, and the integrator's name is on the commissioning sheet. But this is the layer that produces the artefacts the regulator now demands — the as-built drawing, the device schedule, the test record, the worksite analysis input, the network map. <strong>Whoever writes the commissioning file owns the renewal</strong>, and in a compliance market that is a stronger position than owning the patent.</p>

<h3>Layer five: managed services, monitoring and maintenance</h3>

<p>Contracted, index-linked, multi-year revenue: remote monitoring seats, preventive maintenance, firmware and patch management, response SLAs, system health reporting. This is 23.35 per cent of 2025 value and grows at 13.70 per cent — the fastest of the two large layers — because it is the only line in a hospital security budget that converts a capital request into an operating contract. A capital request has to survive a finance committee working against a 1.3 per cent margin. An operating contract with a fixed monthly cost and a documented service credit is a different conversation.</p>

<table>
<thead>
<tr><th>Layer</th><th>Typical gross margin</th><th>Revenue character</th><th>Who controls the renewal</th></tr>
</thead>
<tbody>
<tr><td>Device and sensor manufacture</td><td>30–45%</td><td>Unit volume, deflating prices</td><td>Distributor or integrator</td></tr>
<tr><td>Platform software</td><td>70–85%</td><td>Licence plus subscription</td><td>Vendor, if sold direct to specification</td></tr>
<tr><td>Clinical integration</td><td>45–65%</td><td>Professional services, sticky</td><td>Specialist vendor</td></tr>
<tr><td>Integration and commissioning</td><td>12–22%</td><td>Project, milestone-billed</td><td>Integrator, via the commissioning file</td></tr>
<tr><td>Managed services and monitoring</td><td>30–40%</td><td>Contracted, multi-year, indexed</td><td>Incumbent provider</td></tr>
</tbody>
</table>

<p><em>Table 3 — Indicative value capture by layer. Margins are Pheonix Research estimates from channel and integrator interviews, not disclosed figures; they are intended to show relative position, not precise economics.</em></p>

<figure><img src=\"https://www.pheonixresearch.com/wp-content/uploads/2026/11/healthcare-security-layers-scaled.webp\" alt=\"Grouped bar chart comparing seven healthcare security layers in 2025 and 2033 in USD million\" /><figcaption>Figure 2 — Every layer grows; only four grow faster than the market. Screening, software and managed services are the exceptions that carry the mix shift.</figcaption></figure>

<h3>The lowest-bid problem, stated precisely</h3>

<p>A hospital that specifies \"1,200 cameras, 4 megapixel, 30-day retention\" has written a specification that any of forty bidders can satisfy, and the tendering rule will then select the cheapest of the forty. Because camera counts and resolutions are comparable on a price sheet, the comparison is real. What is not comparable is the thing the hospital actually needs: whether the analytics are tuned to the zone, whether the commissioning file will survive a survey, whether the network map was ever produced, and whether the false-alarm rate will still be tolerable in month eighteen. None of that can be inspected at delivery.</p>

<p>The fix is not exotic. Buy the outcome in units the buyer can verify: a documented worksite analysis per facility, a network map refreshed inside twelve months, a stated false-alarm ceiling per zone with service credits attached, and a price per facility per year rather than a price per camera. That reframing moves the purchase from layer one to layers four and five, which is precisely the direction the market is already moving on its own — 36.12 per cent of 2033 value sits in software and services — and it is the single change most likely to make a security budget defensible to a finance committee.</p>

<p>The counter-argument deserves an airing. Outcome-based specification requires the buyer to hold a view on what good looks like, and most hospital security directors do not have the benchmarking data to set a false-alarm ceiling. They know their own site and nothing else. That is a real gap, and it is the commercially interesting one: the supplier who arrives with comparative, anonymised performance data across a peer group is not selling a camera. It is selling the standard.</p>"
  investment_activity_content: "<h2>5. Investment activity: capital buys the recurring line</h2>

<p>Follow the transactions and the strategy of this market becomes obvious. Almost no recent deal has been about buying a better camera. The acquisitions have been about buying the contract that sits behind the camera — the monitoring seat, the maintenance agreement, the multi-year service relationship that renews on its own terms and is valued by investors on a revenue multiple rather than a project multiple.</p>

<h3>Three deals that explain the structure</h3>

<p>Securitas's purchase of Stanley Black & Decker's electronic security business brought STANLEY Healthcare into a guarding group, which is the clearest possible statement that healthcare security technology is valued as a means of winning and holding service contracts. Motorola Solutions built its video security position out of Avigilon rather than out of a camera brand, because the analytics and the software layer are what command the margin. And ADT's separation of its commercial arm into a stand-alone business under GTCR split a residential monitoring business from a commercial and healthcare installation business with entirely different capital intensity — a split that only makes sense if you believe the two should be valued on different multiples.</p>

<p>Private capital has done the same thing one level down, rolling up regional integrators. The logic is not scale in purchasing; it is recurring maintenance and monitoring revenue attached to a customer list that is expensive to re-win. A hospital does not change its security integrator casually, because the integrator holds the as-built documentation and knows where the cable runs.</p>

<table>
<thead>
<tr><th>Transaction type</th><th>What was bought</th><th>Strategic logic</th><th>What it implies for this market</th></tr>
</thead>
<tbody>
<tr><td>Guarding group acquires healthcare security technology</td><td>Securitas and STANLEY Healthcare</td><td>Attach technology to a labour contract; sell monitoring and infant protection inside a guarding relationship</td><td>The services layer is the exit for technology specialists</td></tr>
<tr><td>Platform owner acquires analytics</td><td>Motorola Solutions and the Avigilon business</td><td>Own the software and the camera; compete with the channel</td><td>Software margin is worth more than device volume</td></tr>
<tr><td>Conglomerate separates commercial security</td><td>ADT commercial arm into Everon</td><td>Different capital intensity and different multiples for commercial versus residential</td><td>Commercial healthcare work is a services business</td></tr>
<tr><td>Sponsor roll-up of integrators</td><td>Regional installation and maintenance firms</td><td>Buy the customer list and the recurring maintenance revenue</td><td>Documentation ownership is the moat</td></tr>
</tbody>
</table>

<p><em>Table 6 — Selected transaction types and their strategic logic. Transaction names are public; the interpretation of logic is Pheonix Research analysis.</em></p>

<figure><img src=\"https://www.pheonixresearch.com/wp-content/uploads/2026/11/healthcare-security-2033-mix-scaled.webp\" alt=\"Donut chart of the 2033 healthcare security layer mix in USD million\" /><figcaption>Figure 3 — 2033 layer mix, USD million. Managed services and video together are just over half the market; the four smallest layers are where the multiple sits.</figcaption></figure>

<h3>Why a cyber event is now a capital-allocation event</h3>

<p>The Change Healthcare attack reset the arithmetic hospital boards use to justify security spending. UnitedHealth Group's year-end 2024 disclosure, as reported in January 2025, put the total impact at <strong>USD 3.09 billion</strong> — <strong>USD 2.2 billion</strong> of direct response costs and <strong>USD 867 million</strong> of business disruption — while the breach estimate reached <strong>190 million individuals</strong>. The most instructive number is none of those. It is the <strong>USD 9.03 billion</strong> advanced to affected healthcare providers to keep them operating, of which <strong>USD 4.5 billion</strong> had been repaid.</p>

<p>That is a transfer of working capital across an entire provider ecosystem caused by a single point of failure, and it does something no security incident report can do: it makes cyber risk a treasury problem. Hospitals that had treated security as a facilities line item started asking a different question — what happens to our cash if this system is unavailable for three weeks — and that question funds resilience rather than detection. It also explains why the integrated software layer, where availability and access control meet, is the fastest-compounding line in our model.</p>

<h3>Where the capital constraint bites</h3>

<p>None of this removes the operating constraint described in Chapter 4. Kaufman Hall's National Hospital Flash Report closed 2025 with an adjusted year-to-date operating margin of <strong>1.3 per cent</strong>, with expenses rising across the board and bad debt, uninsured patients and charity care all increasing. On that margin a hospital cannot fund a security refresh out of cash flow, so the refresh is either bundled into a construction project — where it is a rounding error against the building cost — or converted into an operating contract.</p>

<p>That produces a two-speed investment picture, and it is the honest way to read Table 1. Hardware grows 10.18 per cent because new construction, refurbishment and end-of-life replacement continue regardless of margin. Software and services grow 14.20 per cent because they are the only lines a hospital can buy without a capital request. The 4.02-point gap between those rates is the single most important number in this report, and it is a finance fact before it is a technology fact.</p>

<h3>What we would expect capital to do next</h3>

<p>Three testable consequences follow. First, expect further consolidation among clinical-workflow specialists into services groups, because a small firm with a sticky workflow and no breadth is a natural acquisition. Second, expect platform owners to push harder into subscription pricing that bundles the evidence function, since that is the only way to defend a software multiple against a channel that discounts licences to win hardware. Third, expect the integrator roll-up to continue until the documentation moat is priced properly — at which point the interesting question becomes whether a hospital can own its own commissioning file, and what it would pay to do so.</p>"
  technology_innovation_content: "<h2>2. Technology and innovation: the false alarm is the product</h2>

<p>The most valuable technology in a hospital security system is not detection. It is the suppression of the detection that does not matter. A behavioural health unit generates door events continuously — staff entering, patients attempting, observation checks — and every event that a human must adjudicate costs a walk down a corridor. Alarm fatigue is not a comfort issue in a hospital; it is a patient-safety issue, because a nurse who has silenced forty alarms in a shift will silence the forty-first without looking. The engineering target is therefore not sensitivity. It is a defensible operating point on a curve, set per zone.</p>

<h3>Sensitivity, specificity and the cost of being wrong twice</h3>

<p>Video analytics in healthcare are calibrated differently from retail or perimeter work because the two error types cost in different currencies. A missed event in a ward corridor is a clinical incident with a root-cause review attached. A false event is a nurse-minute, and nurse-minutes are the scarcest input in the building. In a loading dock the ratio inverts: a false event costs nothing, so the detector can be aggressive. This is why a single vendor's out-of-the-box configuration performs well in one hospital and badly in the next, and why the analytical work that customers actually pay for is tuning and re-tuning against real event logs — an ongoing service, not a product feature.</p>

<h3>Why inference moved to the edge, and what that did to retention</h3>

<p>Processing inside the camera rather than the data centre was originally a bandwidth decision: hospitals have thousands of camera streams and constrained backhaul in older wings. It has since become a records decision. Under the HIPAA Security Rule's proposed direction, and under NIS2's governance obligations in Europe, the question of how long identifiable imagery is retained becomes an auditable policy question rather than an IT preference. The clean answer is to keep metadata — counts, dwell times, loiter patterns, door-state exceptions — and discard the frame. Edge inference makes that the default, and it changes the storage economics of a thousand-camera estate from hardware capex to a much smaller software and service line. It also changes the sales conversation: the pitch is no longer resolution, it is retention policy and who can prove it.</p>

<h3>The asset-register accident</h3>

<p>The most consequential development in this market is not a security technology at all. The HIPAA Security Rule notice of proposed rulemaking issued on 27 December 2024 would require covered entities and their business associates to maintain a technology asset inventory and a network map illustrating how electronic protected health information moves through their systems, updated at least every twelve months and in response to environmental change. Consider what a modern hospital knows about its own estate. The clinical device inventory is partial and often maintained by vendors. The IT asset register covers managed endpoints. The security system, by contrast, has a schedule: every camera, every reader, every panel, every intercom, with a location, a firmware version and a date of installation — because the integrator had to install them and the maintenance contract requires an inventory to service.</p>

<p>For camera and reader installation, that inventory exists. And a camera is an unpatched Linux host on the clinical network, while an access panel is operational technology with a default password history. The security estate is frequently the largest uncontrolled endpoint population in the building. A rule that demands an annual network map therefore does something the security industry has wanted for a decade: it converts the integrator's system-of-record into compliance infrastructure. This is the strongest single reason to expect integrated software and services to compound rather than revert, and it is why we model the software layer at 15.72 per cent — the fastest CAGR in the report — despite it being only 7.32 per cent of 2025 value.</p>

<h3>Convergence: one credential, four jobs</h3>

<p>The duress badge, the nurse call pendant, the location tag and the door credential have been converging for years and are now effectively one device in new builds. Ascom's alerting and Zebra's real-time location systems sit in the same clinical workflow as the access control system, and infant protection — Nedap and Securitas among the specialists — has always been a location problem with a liability attached. The commercial consequence is straightforward: a hospital that buys one credential for four jobs buys fewer devices but far more integration, and the integration is where the margin sits. It also raises the cost of getting it wrong, because a single credential controls a door and summons help, and a failure in one function erodes trust in all four.</p>

<h3>Screening: the throughput product</h3>

<p>Weapons screening is the fastest-growing hardware layer in the report at 15.38 per cent, and it is worth being precise about why, because the obvious explanation is wrong. It is not growth in the number of firearms arriving at hospitals. It is that a screening lane has become operationally acceptable where it previously was not. Baystate Health's programme, announced on 18 September 2026, sets out the template: walk-through detection at emergency department entrances without requiring visitors to empty pockets or remove shoes, safe for pregnant patients, children, people with pacemakers and people using mobility devices, with a manual alternative, and an explicit commitment that patients arriving with a medical emergency are not delayed and undergo an alternative process. Phase one put systems in the emergency departments; later phases extend to behavioural health units and main entrances.</p>

<p>Read that specification carefully. Every constraint in it is a clinical constraint, not a detection constraint. The hospital is buying assurance that the lane will not become a bottleneck at triage, and that a patient in arrest will never be held at a checkpoint. That is why cheap, high-sensitivity metal detection does not win this market: it produces the wrong kind of certainty. The successful product screens at the rate people actually arrive — including at 2am on a Saturday — and routes the exceptions to a human who is standing there. The growth rate of this layer is a statement about hospital tolerance for friction, not about the threat.</p>

<h3>What is not being invented</h3>

<p>Almost nothing in this chapter is new physics. The image sensor is a commodity; the analytics are trained models on a well-understood task; the tag is a radio. The innovation is entirely in integration and evidence — making four systems behave as one, and making the resulting record legible to a surveyor, an auditor and a plaintiff. In a market where the specification is written by a regulator and the purchase order is signed against a 1.3 per cent operating margin, that is where the value has to be, and the layer growth rates in this report are simply that sentence expressed in numbers."
  market_risk_content: "<h2>6. Market risk: two sensitivities, three falsifiers, one scope warning</h2>

<p>A forecast that cannot be wrong is not a forecast. This chapter states what would have to be true for the numbers in this report to fail, and what happens to them if the most fragile assumptions break. It also carries a warning about category scope that a careful reader should apply to any figure they see for this market, including ours.</p>

<h3>Sensitivity one: services grow at 10 per cent, not 13.70 per cent</h3>

<p>The largest single bet in this model is the services layer. If managed services, monitoring and maintenance grow at 10 per cent instead of 13.70 per cent — a plausible outcome if hospital procurement keeps services inside capital projects and never converts them to contracts — that layer reaches USD 10.12 billion rather than USD 13.18 billion in 2033. The market total becomes <strong>USD 46.61 billion</strong> and the CAGR falls to <strong>11.01 per cent</strong>. The direction of the story survives; the mix shift that carries it weakens materially.</p>

<h3>Sensitivity two: screening reverts to the market rate</h3>

<p>Screening is the second-largest bet, and the most exposed to a single operational failure: if walk-through detection proves to slow emergency arrivals more than hospitals will tolerate, or if published throughput and false-alarm data turn against it, the layer grows at the market rate of 11.90 per cent rather than 15.38 per cent. It would then reach USD 3.29 billion in 2033 instead of USD 4.21 billion, taking the total to <strong>USD 48.75 billion</strong> and the CAGR to <strong>11.64 per cent</strong>. This is a smaller sensitivity than the services case, which is why we weight it less.</p>

<h3>Sensitivity three: capital discipline holds at 8 per cent</h3>

<p>The most important downside case is not about any layer. It is about the ability of hospitals to buy anything at all. If the 1.3 per cent margin environment persists and security spend is capped at 8 per cent growth across the forecast window, the market reaches <strong>USD 37.41 billion</strong> by 2033 rather than USD 49.67 billion. That is a 24.7 per cent reduction in the 2033 number, and it is the scenario a hospital supplier should be planning against, because it requires no regulatory reversal — only a continuation of the current financial picture.</p>

<table>
<thead>
<tr><th>Case</th><th>Change from base</th><th>2033 value (USD bn)</th><th>2026–2033 CAGR</th></tr>
</thead>
<tbody>
<tr><td>Base case</td><td>—</td><td>49.67</td><td>11.90%</td></tr>
<tr><td>Services grow at 10.00%</td><td>Services CAGR cut 3.70 points</td><td>46.61</td><td>11.01%</td></tr>
<tr><td>Screening grows at market rate</td><td>Screening CAGR cut 3.48 points</td><td>48.75</td><td>11.64%</td></tr>
<tr><td>Capital discipline at 8.00%</td><td>Whole-market growth capped</td><td>37.41</td><td>8.00%</td></tr>
</tbody>
</table>

<p><em>Table 7 — Sensitivity tests against the base case. Each case changes one assumption and holds the rest of the model constant.</em></p>

<h3>Three falsifiers</h3>

<p><strong>One: a regulator writes a number.</strong> The services premium in this report exists because specification is qualitative — a worksite analysis, a documented risk assessment, a tuned analytics configuration. If a regulator replaces that with a pass mark — a stated detection threshold, a numeric false-alarm ceiling, a certified product list — the specification becomes comparable on a price sheet and the premium compresses. This is the most plausible mechanism by which the mix shift reverses, and it would arrive from a well-intentioned simplification.</p>

<p><strong>Two: hospital margins recover durably.</strong> Our mix shift assumes capital remains scarce. If operating margins return to the mid single digits and stay there, capital requests become fundable again, hospitals buy new estates rather than services attached to old ones, and hardware outgrows services. The 4.02-point gap between hardware and software-plus-services growth closes. Anyone who expects a durable margin recovery should discount the 49.67 billion figure and treat the 8 per cent case as the central one.</p>

<p><strong>Three: screening fails its cost-benefit test in public.</strong> Screening is bought on the promise that it reduces harm without delaying care. If the first large, well-evidenced programme evaluation shows no measurable reduction in incidents against a measurable throughput cost, procurement will not stop screening — but it will stop expanding it, and the 15.38 per cent assumption in the fastest hardware layer goes with it.</p>

<h3>And the risk that is epistemic rather than commercial</h3>

<p>The HIPAA Security Rule revision is a proposal, not a rule. If it is withdrawn or substantially narrowed, the network-map driver behind the 15.72 per cent software growth weakens and that layer reverts toward the hardware rate. We have not hidden this: it is stated in Chapter 4 and repeated here. A reader who believes the rule will not survive should take roughly three points off the software CAGR and expect the mix shift to arrive later, not never — because accreditation and NIS2 point the same direction without it.</p>

<h3>A scope warning about every number in this category</h3>

<p>Figures published for \"healthcare security systems\" differ by a factor of two or more, and the difference is almost never method — it is category boundary. Definitions that count only physical security hardware produce a market less than half the size of ours. We include managed services, screening lanes, the integration software layer and the infant/patient protection category, and we exclude hospital cybersecurity software spend and security officer labour entirely. Our 2025 base of USD 20.21 billion is therefore broader in scope than many figures a reader will encounter, and comparison across sources without reconciling scope is meaningless. Where our model differs from another estimate, the first question to ask is what that estimate excluded.</p>"
  regulatory_landscape_content: "<h2>4. Regulatory landscape: four regimes on one estate</h2>

<p>Most security markets are regulated at the edges: a fire code here, a privacy statute there. Healthcare is different. Four separate regimes land on the same camera, the same door and the same badge, and each demands a different artefact from the same installation. The commercial consequence is that compliance is not a cost attached to this market — it is the specification. Modifying any one of the four changes the forecast, and the two dates that matter most have both already arrived.</p>

<h3>Regime one: accreditation, which audits process</h3>

<p>The Joint Commission's new and revised workplace violence prevention requirements took effect on <strong>1 July 2025</strong> for assisted living communities, nursing care centres and office-based surgery practices, and align with the earlier updates for hospitals, critical access hospitals, behavioural health care and home care. The requirements address training and education, post-incident strategies, reporting systems with data collection and analysis, policies and procedures, leadership oversight, and worksite analysis — with a formal definition of workplace violence added to the glossary.</p>

<p>Read the list again as a buyer. Six of the seven items are documents, and the seventh is oversight of the documents. None of them is a device. An accreditation surveyor will not measure the resolution of your cameras; they will ask to see the analysis, the training record and what changed after the last incident. The hospital that installed an excellent system but cannot produce the analysis fails, and the hospital with an ordinary system and an immaculate file passes. This is the most commonly misunderstood feature of the market, and it is why services grow faster than hardware.</p>

<h3>Regime two: the HIPAA Security Rule, which audits records</h3>

<p>The Office for Civil Rights issued its notice of proposed rulemaking on <strong>27 December 2024</strong>. It proposes to remove the distinction between \"required\" and \"addressable\" implementation specifications, require written documentation of all Security Rule policies, procedures, plans and analyses, attach specific compliance time periods to many existing requirements, and require a technology asset inventory and a network map illustrating how electronic protected health information moves — maintained on an ongoing basis, updated at least every twelve months and in response to a change in environment or operations. Risk analysis would need new specificity: a review of the asset inventory and network map, identification of reasonably anticipated threats, vulnerabilities and predisposing conditions, and an assessed risk level for each.</p>

<p>Two things follow. First, the security estate becomes a compliance asset rather than a facilities asset, because it is the only register in the building that already lists devices, locations and firmware. Second, the buyer needs a party who can produce and refresh that register annually. That is a subscription, and it is why we model integrated software at 15.72 per cent.</p>

<p>It is also important to be accurate about status: this is a <em>proposed</em> rule. It has not been finalised, and rules of this scale are amended or abandoned. The forecast assigns it a real but bounded weight — it accelerates the software layer, it does not create it — and Chapter 6 states what happens if it never lands.</p>

<h3>Regime three: NIS2, which audits governance</h3>

<p>The European Union's second Network and Information Security Directive, politically agreed in May 2022 and formally adopted in late November 2022, expanded the sectors in scope and, in health, went beyond hospitals to entities carrying out research and development of medicinal products. Member states were required to transpose it into national law, and the obligations it imposes are notable for what they target: management-body accountability for cybersecurity risk, supply-chain security, and incident reporting on a short clock.</p>

<p>For a hospital group, NIS2 makes security a board matter in a way accreditation never does. For a supplier, it makes the supply chain auditable — which means a security integrator selling into European health systems must be able to evidence the security of what it installed, including the firmware lifecycle of the cameras and panels. That is a formalisation of exactly the asset-register capability described above, arriving from a different direction.</p>

<h3>Regime four: the procurement rulebook, which audits price</h3>

<p>The fourth regime is not a regulator at all. It is the operating constraint that governs every purchase: a finance committee working against a 1.3 per cent adjusted hospital operating margin, in a year when Kaufman Hall reports expenses rising across the board, bad debt, uninsured patients and charity care all increasing, and a larger share of revenue arriving from public rather than private payers. In that setting a capital request for security competes with clinical equipment, and it usually loses.</p>

<p>This is why the managed-services layer at 13.70 per cent is not an anomaly to be explained away. A fixed monthly operating cost with a documented service credit is the only structure that reliably clears a capital committee at 1.3 per cent. The regulatory regimes create the requirement; the procurement regime decides which commercial wrapping gets bought.</p>

<table>
<thead>
<tr><th>Regime</th><th>Artefact demanded</th><th>Key date</th><th>Can a device satisfy it?</th><th>Status</th></tr>
</thead>
<tbody>
<tr><td>Joint Commission workplace violence prevention</td><td>Worksite analysis, training records, incident data and analysis, post-incident strategy</td><td>1 July 2025</td><td>No — process and documentation</td><td>In force</td></tr>
<tr><td>HIPAA Security Rule revision</td><td>Technology asset inventory, network map, written risk analysis, documented policies</td><td>Proposed 27 December 2024</td><td>No — but the estate supplies the inventory</td><td>Proposed, not final</td></tr>
<tr><td>NIS2 (EU)</td><td>Management accountability, supply-chain security evidence, incident reporting</td><td>Adopted late November 2022; national transposition</td><td>No — governance and evidence</td><td>In force, transposing</td></tr>
<tr><td>Hospital capital procurement</td><td>Business case cleared against a 1.3 per cent operating margin</td><td>Continuous</td><td>Only as an operating contract</td><td>Binding</td></tr>
</tbody>
</table>

<p><em>Table 5 — Four regimes, what each actually demands, and whether hardware can answer it. The pattern is the argument: three of the four are satisfied by documentation, which is a services and software purchase.</em></p>

<h3>What the regime map implies for a hospital</h3>

<p>A hospital that treats these four as separate projects will buy four times and satisfy each regime partially. A hospital that treats them as one estate will buy once and satisfy all four, because the artefacts overlap: the worksite analysis needs the device schedule, the network map is the device schedule, the NIS2 supply-chain evidence is a firmware lifecycle record for the same devices, and the capital committee will fund the cheapest version of all three. That is the commercial case for integrated software in one paragraph, and it is why the software layer is the fastest-growing line in this report despite being the smallest today.</p>"
  faq_question_1: "How large is the global healthcare security systems market?"
  faq_answer_1: "Pheonix Research sizes it at USD 20.21 billion in 2025, rising to USD 49.67 billion by 2033 — an 11.90 per cent CAGR across 2026–2033, or 2.46 times the base year. Installed secure endpoints grow more slowly, from 118.6 million to 214.8 million at 7.71 per cent, which means revenue per endpoint rises 35.7 per cent as services and software take a larger share of the bill."
  faq_question_2: "Why does the market grow faster than the number of cameras, readers and tags installed?"
  faq_answer_2: "Because the buyer is not purchasing equipment. Accreditation, the proposed HIPAA Security Rule inventory and network-map requirement, and NIS2 each demand a document — a worksite analysis, an asset inventory, a network map, an incident record. Producing those documents is services and software work. Managed services and integrated software climb from 30.67 per cent of market value in 2025 to 36.12 per cent in 2033, and that mix shift, not unit growth, is what carries the forecast."
  faq_question_3: "Is demand driven by crime and violence, or by regulation?"
  faq_answer_3: "Both, but regulation converts the concern into a purchase order. Assault rates in US healthcare and social assistance rose from 6.4 to 9.8 per 10,000 full-time-equivalent workers between 2011 and 2021–22, and psychiatric and substance-abuse hospitals run at 138.8 per 10,000 — that is the demand signal. The Joint Commission's workplace violence prevention requirements, effective 1 July 2025, are what turn the signal into a specified, budgeted, auditable programme."
  faq_question_4: "Which layer of the market grows fastest?"
  faq_answer_4: "Integrated software and command platforms, at 15.72 per cent, followed by screening and detection at 15.38 per cent and managed services at 13.70 per cent. Video surveillance grows 11.00 per cent, access control 10.03 per cent, infant and patient protection 9.53 per cent and intrusion and duress 8.81 per cent. The four hardware layers still hold 55.41 per cent of 2033 value, so this is a mix shift inside a growing hardware market, not the replacement of one."

global_schema:
  organization:
    "@id": MIWS-root#organization
    "@type": Organization
    url: "https://www.pheonixresearch.com/"
    name: Pheonix Research
  website:
    "@id": MIWS-root
    "@type": WebSite
    url: "https://www.pheonixresearch.com/"
    name: Pheonix Research
  api:
    "@id": MIWS-root#api
    "@type": WebAPI
    url: "https://www.pheonixresearch.com/"

graph:
  node_id: MILV-fr-MIMR-node_fa547d2
  graph_node_endpoint: "https://graph.pheonixresearch.com/api/v1/query/live/node/MILV-fr-MIMR-node_fa547d2"
  graph_snapshot: "https://graph.pheonixresearch.com/api/v1/read/live/graph"
  graph_exclusions: "https://graph.pheonixresearch.com/api/v1/read/live/exclusions"
  graph_meta: "https://graph.pheonixresearch.com/api/v1/read/live/meta"
  graph_bundle: "https://graph.pheonixresearch.com/api/v1/read/live/bundle"

discovery:
  discovery_json: "https://www.pheonixresearch.com/.well-known/pheonix-discovery.json"
  llms_txt: "https://www.pheonixresearch.com/llms.txt"
  sitemap: "https://www.pheonixresearch.com/sitemap.xml"
---
# Marché mondial des systèmes de sécurité de santé, par type (système de détection d'intrusion, système de vidéosurveillance, étiquettes RFID, protection périmétrique, systèmes de contrôle d'accès, systèmes de contrôle d'accès électronique, alarme de sécurité, systèmes d'inspection de véhicules, système de sécurité pour nouveau-nés, systèmes de détection, systèmes de notification d'urgence/duress, détecteurs de métaux et détecteurs d'explosifs, systèmes de vidéosurveillance, autres), par application (documents, suivi des dispositifs médicaux, surveillance, suivi du matériel chirurgical, suivi des fichiers de données, suivi des patients, autres), par utilisateur final (pharmacie, centres de diagnostic, hôpital, laboratoires, cliniques, autres), par géographie (Europe, Amérique du Nord, Asie-Pacifique, Moyen-Orient et Afrique, Amérique latine) – Croissance, opportunités et prévisions jusqu'en 2028

- **Taille du marché (année de base):** USD 20.21 Billion
- **Valeur prévisionnelle:** USD 49.67 Billion
- **TCAC:** 11.90%
- **Période de prévision:** 2026 - 2033
- **Couverture:** Global - North America, Europe, Asia Pacific, Middle East & Africa, South America

## Rapport de marché

**Impact de la COVID-19 sur le marché des systèmes de sécurité des soins de santé**
La propagation mondiale de la pandémie de COVID-19 expose le développement de l'économie mondiale à des défis sans précédent et sévères, et l'économie mondiale subit une pression à la baisse plus importante. L'impact des pandémies sur l'économie a entraîné une stagnation ou un ralentissement de l'activité économique dans de nombreux pays, réduit la demande mondiale, diminué considérablement les échanges commerciaux et les investissements, et affecté les chaînes industrielles mondiales. Des scénarios de reprise fondés sur la demande sont prévus et analysés dans cette étude.

**Aperçu du marché mondial des systèmes de sécurité pour la santé :**
Le système de sécurité médicale est un système qui assure la sécurité des professionnels de santé, des patients et des visiteurs. Cela inclut la conception, la planification et l'installation de systèmes de sécurité. Les systèmes de sécurité des établissements de santé instaurent la confiance dans les organisations de soins. La vidéosurveillance est principalement installée à l'extérieur et à proximité des établissements médicaux.

La demande de systèmes de sécurité dans le secteur de la santé est devenue très importante et promet une croissance exponentielle. Le marché des systèmes de sécurité médicale connaît un essor considérable au cours de la période de prévision, en raison de la nécessité croissante de sécuriser de multiples installations médicales critiques. Il existe un besoin croissant de garantir la sécurité des données et la sécurité physique mises en place par l'organisation pour surveiller et contrôler les accès.

**Selon Phoenix Research, le « Marché mondial des systèmes de sécurité pour les soins de santé » est estimé à US $ AB millions en 2020 et devrait atteindre US $ XY millions d'ici 2028.**. L'Amérique du Nord domine le marché mondial des systèmes de sécurité des soins de santé et devrait enregistrer un TCAC de XX% au cours de la période de prévision 2021-2028.
L'Amérique du Nord détient la plus grande part de marché dans le secteur mondial des systèmes de sécurité des soins de santé, suivie de l'Europe et de la région Asie-Pacifique. Face à la recrudescence des menaces de cybersécurité, des solutions de systèmes de sécurité des soins de santé basées sur le cloud sont adoptées dans la région. Les États-Unis dominent le marché nord-américain. En outre, la région dispose d'une infrastructure informatique bien établie qui permet un déploiement plus rapide des nouvelles technologies.

Les principaux acteurs du marché des systèmes de sécurité des soins de santé sont Johnson Controls, ADT LLC dba ADT Security Services, Avigilon Corporation, Bosch Security Systems, Tyco Security Products, Nedap Security Management, Siemens AG, Atos SE, Inc., Allied Telesis, Honeywell International, Cisco Systems, Schneider Electric SE, Inc., Inc., STANLEY Healthcare, Seico Security et autres.

Le rapport récent intitulé «**Marché mondial des systèmes de sécurité dans le secteur de la santé (2021-2028)**a été segmenté par type de système, application, utilisateur final et région.

**Segmentation du marché**
**Par type**
Système de détection d'intrusion
Système de vidéosurveillance (CCTV)
Étiquettes RFID
Protection périmétrique
Systèmes de contrôle d'accès
Systèmes de contrôle d'accès électronique
Alarme de sécurité
Systèmes d'inspection des véhicules
Système de sécurité pour nourrissons
Systèmes de détection
Systèmes d'alerte d'urgence/contrainte
Détecteur de métaux
Détecteurs d'explosifs
Systèmes de vidéosurveillance
Autres

**Par application**
Scanneur de documents
Suivi des dispositifs médicaux
Dispositifs de surveillance
Suivi des équipements chirurgicaux
Suivi des fichiers de données
Suivi des patients
Autres

**Selon l'Utilisateur Final**
??? Pharmacies
??? Centres de diagnostic
??? Hôpitaux
??? Laboratoires
??? Cliniques
??? Autres

**Par zone géographique**
**Amérique du Nord**
??? États-Unis
??? Canada

**Europe**
??? Allemagne
??? Italie
??? Royaume-Uni
??? Suisse
??? Russie
??? Pologne
??? France
??? Espagne
??? Turquie
??? Pays-Bas
??? Belgique
??? Reste de l’Europe

**Asie-Pacifique**
??? ANZ
??? Taïwan
??? ASEAN
??? Japon
??? Chine
??? Inde
??? Corée du Sud
??? Reste de l'Asie-Pacifique

**Moyen-Orient et Afrique**
Afrique du Nord
Égypte
Pays du CCG
Afrique du Sud
Reste du Moyen-Orient et de l’Afrique

**Amérique latine**
??? Brésil
??? Argentine
??? Mexique
??? Reste de l’Amérique latine

## Table des matières

<p style="text-align: center;">[wpforms id="87321" title="true" description="true"]</p>

## Paysage concurrentiel

3. Competitive landscape: three positions, no leader, and the trap in the middle
No participant in this market holds a double-digit share of global healthcare security revenue, and Pheonix Research estimates that the ten largest together hold roughly a third of it. That is unusual for a market of this size, and it is a direct consequence of the value chain described in Chapter 1: the buyer purchases an assembled, commissioned, locally warranted system, so scale is local even when the product is global. A hospital in Manchester and a hospital in Manila may run the same video management platform and be served by firms that never compete with each other.
Within that fragmentation, competitors occupy three distinct positions, and the strategic mistake to make is to confuse them.
Position one: the platform owners
Johnson Controls, Honeywell, Siemens, Robert Bosch, Motorola Solutions through its video security business, and Schneider Electric. Each owns a piece of the software stack, often the panel or camera hardware, and frequently the service arm as well. Their structural problem is channel conflict: the integrator that specifies the platform is also the entity the platform owner competes with when it bids the service contract directly. In large health systems this conflict is manageable because the buyer wants a single accountable party. In single-site hospitals it is corrosive, because the integrator’s rational response is to specify a platform it can control.
Position two: the services and guarding companies
Securitas, which acquired Stanley Healthcare’s healthcare security business and now sells infant protection, asset tracking and monitoring inside a guarding relationship; ADT through its commercial and healthcare work; and the large guarding groups that bundle technology into labour contracts. Their economics are labour economics. The technology is a means of winning and retaining a multi-year service agreement, and their pricing power comes from the contract structure rather than from the device. They are the most likely winners of the managed-services layer and the least likely to lead on analytics.
Position three: the clinical-workflow specialists
Nedap, Ascom and Zebra, alongside a set of smaller firms in real-time location and infant protection. Their products are small, integrated deep into nursing workflow, and replaced only when a hospital changes its clinical system. This is the smallest position by revenue and the stickiest by account tenure. Their weakness is breadth: they solve one workflow beautifully and cannot be the accountable party for an entire estate.



Company
Primary position
Healthcare security relevance
Wikidata




Johnson Controls
Platform owner
Access control, video, intrusion; large installed estate across health systems
Q667865


Honeywell International
Platform owner
Access control, video and building integration; strong in acute care retrofits
Q898208


Motorola Solutions
Platform owner
Video security and analytics; body-worn and command software in hospital systems
Q634815


Robert Bosch (Bosch Security and Safety Systems)
Platform owner
Cameras, conference and evacuation systems; strong in European tenders
Q226327


Siemens
Platform owner
Building and access integration inside a wider hospital technology estate
Q81230


Securitas
Services and guarding
Infant protection, asset tracking, monitoring inside guarding contracts
Q662174


ADT Inc.
Services and guarding
Monitoring, intrusion and commercial security with healthcare accounts
Q290680


Nedap
Clinical-workflow specialist
Identification and infant/patient protection; deep European base
Q1479312


Ascom
Clinical-workflow specialist
Alerting, duress and nurse call convergence on one handset
Q663942


Zebra Technologies
Clinical-workflow specialist
Real-time location, patient and asset visibility, handheld identity
Q2443609



Table 4 — Ten credible players across three positions. Wikidata identifiers verified against the Wikidata query service for this edition. Presence of a company in this table is not an estimate of market share.
The trap in the middle
Fragmentation is usually described as a benefit to buyers, and in this market it is only half true. The practical consequence at estate level is what our interviews with facilities and security directors describe repeatedly: a mid-sized acute hospital running somewhere between ten and fifteen separate systems — video from one vendor, access from another, the intruder alarm from a local firm, nurse call from a clinical supplier, the infant tag system from a specialist, screening lanes from a third party, and three separate monitoring applications, each with its own login and its own idea of an incident record. The buyer’s stated priority in these conversations is rarely more capability. It is fewer logins and one incident record.
That is the demand behind the 15.72 per cent growth we model for integrated software, and it is a demand the platform owners are better placed to meet than any other position — provided they can price it as a subscription carrying an evidence function, rather than as a licence attached to a hardware discount. The services companies can meet it too, but only by integrating competitors’ products, which is a business they are structurally capable of running and culturally less inclined to invest in.
What the competitive map means for a buyer
The question that separates these positions is not “who has the best technology”. It is “who will produce the network map in twelve months, and at what price”. A platform owner will answer with a feature list. A guarding company will answer with a service credit. A clinical-workflow specialist will answer with an integration diagram. The buyer who asks the question in that form will discover in one meeting which of the three has understood the market this report describes — and will usually find that the answer differs between their emergency department, their behavioural health unit and their pharmacy.
Our own reading is that competitive intensity rises rather than falls over the forecast window, because the fastest-growing layers — screening and integrated software — have low barriers to entry on the device side and high barriers on the evidence side. That combination produces a market with many entrants, rapid consolidation among the small ones, and no leader: exactly the structure we have assigned it, and exactly the structure in which the buyer’s procurement discipline matters more than the vendor’s brand.

- **Structure:** fragmented
- **Joueurs de niveau 1:** 8
- **Intensité:** high

## Chaîne de valeur

1. Value chain and margin structure: the thinnest margin owns the customer
In most markets the company closest to the customer earns the best margin. Healthcare security inverts that. The relationship sits with a systems integrator whose net margin is usually in the mid single digits, while the software it installs earns seventy per cent gross and the manufacturer of the camera inside the housing earns a fraction of the project value. That inversion is not an accident of competition. It is a consequence of what the buyer is actually purchasing: a documented, commissioned, auditable system, assembled on site, by people who will still be answering the phone in year four.
Five layers carry the value, and each behaves differently.
Layer one: device and sensor manufacturers
Cameras, readers, intrusion panels, RFID tags, duress badges and screening lanes. This is where price deflation is most visible and least important. Image sensors and system-on-chip silicon are consumer-electronics volume; a mid-range camera in 2026 does what a premium camera did in 2019 for materially less, and the same curve has reached access readers and detection lanes. Deflation here does not shrink the market, because the buyer does not want a cheaper camera — it wants more coverage of more space, and the budget freed by falling unit prices is immediately spent on additional endpoints. That is why endpoint count grows 7.71 per cent while hardware value grows 10.18 per cent: more units, more analytics per unit, and a rising services tail attached to each.
Layer two: platform software
Video management, access control, visitor management and the physical security information management layer that fuses them. Gross margins here are in the seventy to eighty-five per cent band, but the software is almost never sold on its own in healthcare. It is bundled into a project price, and the licence is often the part the integrator discounts to win the hardware. Software only becomes a genuine margin pool when it is sold as a subscription with an evidence function attached — a compliance dashboard, an incident module, a retention policy that can be shown to an auditor.
Layer three: clinical integration
This is the layer outsiders underestimate and the reason a hospital is not a shopping centre with beds. The access control system must talk to the admission-discharge-transfer feed so that a discharged patient’s wristband stops opening a ward door. The duress badge must land on the same screen as the nurse call. The infant protection tag must reconcile against the maternity census. The pharmacy cabinet must log to the same identity as the door. Once the credential is the identity and the identity sits in the clinical record, replacement stops being a procurement decision and becomes a re-credentialing and re-validation project — which is why switching costs in this layer are the highest in the entire chain, and why the clinical-workflow specialists hold accounts for a decade or more.
Layer four: integration and commissioning
The integrator designs, installs, commissions and warrants the system. Our channel interviews put gross margin at twelve to twenty-two per cent and net margin at three to six per cent on healthcare work, which is thin for the risk carried: a mis-configured door in a behavioural health unit is a ligature and elopement exposure, and the integrator’s name is on the commissioning sheet. But this is the layer that produces the artefacts the regulator now demands — the as-built drawing, the device schedule, the test record, the worksite analysis input, the network map. Whoever writes the commissioning file owns the renewal, and in a compliance market that is a stronger position than owning the patent.
Layer five: managed services, monitoring and maintenance
Contracted, index-linked, multi-year revenue: remote monitoring seats, preventive maintenance, firmware and patch management, response SLAs, system health reporting. This is 23.35 per cent of 2025 value and grows at 13.70 per cent — the fastest of the two large layers — because it is the only line in a hospital security budget that converts a capital request into an operating contract. A capital request has to survive a finance committee working against a 1.3 per cent margin. An operating contract with a fixed monthly cost and a documented service credit is a different conversation.



Layer
Typical gross margin
Revenue character
Who controls the renewal




Device and sensor manufacture
30–45%
Unit volume, deflating prices
Distributor or integrator


Platform software
70–85%
Licence plus subscription
Vendor, if sold direct to specification


Clinical integration
45–65%
Professional services, sticky
Specialist vendor


Integration and commissioning
12–22%
Project, milestone-billed
Integrator, via the commissioning file


Managed services and monitoring
30–40%
Contracted, multi-year, indexed
Incumbent provider



Table 3 — Indicative value capture by layer. Margins are Pheonix Research estimates from channel and integrator interviews, not disclosed figures; they are intended to show relative position, not precise economics.
Figure 2 — Every layer grows; only four grow faster than the market. Screening, software and managed services are the exceptions that carry the mix shift.
The lowest-bid problem, stated precisely
A hospital that specifies “1,200 cameras, 4 megapixel, 30-day retention” has written a specification that any of forty bidders can satisfy, and the tendering rule will then select the cheapest of the forty. Because camera counts and resolutions are comparable on a price sheet, the comparison is real. What is not comparable is the thing the hospital actually needs: whether the analytics are tuned to the zone, whether the commissioning file will survive a survey, whether the network map was ever produced, and whether the false-alarm rate will still be tolerable in month eighteen. None of that can be inspected at delivery.
The fix is not exotic. Buy the outcome in units the buyer can verify: a documented worksite analysis per facility, a network map refreshed inside twelve months, a stated false-alarm ceiling per zone with service credits attached, and a price per facility per year rather than a price per camera. That reframing moves the purchase from layer one to layers four and five, which is precisely the direction the market is already moving on its own — 36.12 per cent of 2033 value sits in software and services — and it is the single change most likely to make a security budget defensible to a finance committee.
The counter-argument deserves an airing. Outcome-based specification requires the buyer to hold a view on what good looks like, and most hospital security directors do not have the benchmarking data to set a false-alarm ceiling. They know their own site and nothing else. That is a real gap, and it is the commercially interesting one: the supplier who arrives with comparative, anonymised performance data across a peer group is not selling a camera. It is selling the standard.

- **Modèle:** hybrid
- **Distribution:** distributor_led
- **Complexité de l'approvisionnement:** moderate

## Activité d'investissement

5. Investment activity: capital buys the recurring line
Follow the transactions and the strategy of this market becomes obvious. Almost no recent deal has been about buying a better camera. The acquisitions have been about buying the contract that sits behind the camera — the monitoring seat, the maintenance agreement, the multi-year service relationship that renews on its own terms and is valued by investors on a revenue multiple rather than a project multiple.
Three deals that explain the structure
Securitas’s purchase of Stanley Black & Decker’s electronic security business brought STANLEY Healthcare into a guarding group, which is the clearest possible statement that healthcare security technology is valued as a means of winning and holding service contracts. Motorola Solutions built its video security position out of Avigilon rather than out of a camera brand, because the analytics and the software layer are what command the margin. And ADT’s separation of its commercial arm into a stand-alone business under GTCR split a residential monitoring business from a commercial and healthcare installation business with entirely different capital intensity — a split that only makes sense if you believe the two should be valued on different multiples.
Private capital has done the same thing one level down, rolling up regional integrators. The logic is not scale in purchasing; it is recurring maintenance and monitoring revenue attached to a customer list that is expensive to re-win. A hospital does not change its security integrator casually, because the integrator holds the as-built documentation and knows where the cable runs.



Transaction type
What was bought
Strategic logic
What it implies for this market




Guarding group acquires healthcare security technology
Securitas and STANLEY Healthcare
Attach technology to a labour contract; sell monitoring and infant protection inside a guarding relationship
The services layer is the exit for technology specialists


Platform owner acquires analytics
Motorola Solutions and the Avigilon business
Own the software and the camera; compete with the channel
Software margin is worth more than device volume


Conglomerate separates commercial security
ADT commercial arm into Everon
Different capital intensity and different multiples for commercial versus residential
Commercial healthcare work is a services business


Sponsor roll-up of integrators
Regional installation and maintenance firms
Buy the customer list and the recurring maintenance revenue
Documentation ownership is the moat



Table 6 — Selected transaction types and their strategic logic. Transaction names are public; the interpretation of logic is Pheonix Research analysis.
Figure 3 — 2033 layer mix, USD million. Managed services and video together are just over half the market; the four smallest layers are where the multiple sits.
Why a cyber event is now a capital-allocation event
The Change Healthcare attack reset the arithmetic hospital boards use to justify security spending. UnitedHealth Group’s year-end 2024 disclosure, as reported in January 2025, put the total impact at USD 3.09 billion — USD 2.2 billion of direct response costs and USD 867 million of business disruption — while the breach estimate reached 190 million individuals. The most instructive number is none of those. It is the USD 9.03 billion advanced to affected healthcare providers to keep them operating, of which USD 4.5 billion had been repaid.
That is a transfer of working capital across an entire provider ecosystem caused by a single point of failure, and it does something no security incident report can do: it makes cyber risk a treasury problem. Hospitals that had treated security as a facilities line item started asking a different question — what happens to our cash if this system is unavailable for three weeks — and that question funds resilience rather than detection. It also explains why the integrated software layer, where availability and access control meet, is the fastest-compounding line in our model.
Where the capital constraint bites
None of this removes the operating constraint described in Chapter 4. Kaufman Hall’s National Hospital Flash Report closed 2025 with an adjusted year-to-date operating margin of 1.3 per cent, with expenses rising across the board and bad debt, uninsured patients and charity care all increasing. On that margin a hospital cannot fund a security refresh out of cash flow, so the refresh is either bundled into a construction project — where it is a rounding error against the building cost — or converted into an operating contract.
That produces a two-speed investment picture, and it is the honest way to read Table 1. Hardware grows 10.18 per cent because new construction, refurbishment and end-of-life replacement continue regardless of margin. Software and services grow 14.20 per cent because they are the only lines a hospital can buy without a capital request. The 4.02-point gap between those rates is the single most important number in this report, and it is a finance fact before it is a technology fact.
What we would expect capital to do next
Three testable consequences follow. First, expect further consolidation among clinical-workflow specialists into services groups, because a small firm with a sticky workflow and no breadth is a natural acquisition. Second, expect platform owners to push harder into subscription pricing that bundles the evidence function, since that is the only way to defend a software multiple against a channel that discounts licences to win hardware. Third, expect the integrator roll-up to continue until the documentation moat is priced properly — at which point the interesting question becomes whether a hospital can own its own commissioning file, and what it would pay to do so.

- **Tendance:** rising
- **Intensité capitalistique:** low
- **M&A récentes:** yes

## Technologie et innovation

2. Technology and innovation: the false alarm is the product
The most valuable technology in a hospital security system is not detection. It is the suppression of the detection that does not matter. A behavioural health unit generates door events continuously — staff entering, patients attempting, observation checks — and every event that a human must adjudicate costs a walk down a corridor. Alarm fatigue is not a comfort issue in a hospital; it is a patient-safety issue, because a nurse who has silenced forty alarms in a shift will silence the forty-first without looking. The engineering target is therefore not sensitivity. It is a defensible operating point on a curve, set per zone.
Sensitivity, specificity and the cost of being wrong twice
Video analytics in healthcare are calibrated differently from retail or perimeter work because the two error types cost in different currencies. A missed event in a ward corridor is a clinical incident with a root-cause review attached. A false event is a nurse-minute, and nurse-minutes are the scarcest input in the building. In a loading dock the ratio inverts: a false event costs nothing, so the detector can be aggressive. This is why a single vendor’s out-of-the-box configuration performs well in one hospital and badly in the next, and why the analytical work that customers actually pay for is tuning and re-tuning against real event logs — an ongoing service, not a product feature.
Why inference moved to the edge, and what that did to retention
Processing inside the camera rather than the data centre was originally a bandwidth decision: hospitals have thousands of camera streams and constrained backhaul in older wings. It has since become a records decision. Under the HIPAA Security Rule’s proposed direction, and under NIS2’s governance obligations in Europe, the question of how long identifiable imagery is retained becomes an auditable policy question rather than an IT preference. The clean answer is to keep metadata — counts, dwell times, loiter patterns, door-state exceptions — and discard the frame. Edge inference makes that the default, and it changes the storage economics of a thousand-camera estate from hardware capex to a much smaller software and service line. It also changes the sales conversation: the pitch is no longer resolution, it is retention policy and who can prove it.
The asset-register accident
The most consequential development in this market is not a security technology at all. The HIPAA Security Rule notice of proposed rulemaking issued on 27 December 2024 would require covered entities and their business associates to maintain a technology asset inventory and a network map illustrating how electronic protected health information moves through their systems, updated at least every twelve months and in response to environmental change. Consider what a modern hospital knows about its own estate. The clinical device inventory is partial and often maintained by vendors. The IT asset register covers managed endpoints. The security system, by contrast, has a schedule: every camera, every reader, every panel, every intercom, with a location, a firmware version and a date of installation — because the integrator had to install them and the maintenance contract requires an inventory to service.
For camera and reader installation, that inventory exists. And a camera is an unpatched Linux host on the clinical network, while an access panel is operational technology with a default password history. The security estate is frequently the largest uncontrolled endpoint population in the building. A rule that demands an annual network map therefore does something the security industry has wanted for a decade: it converts the integrator’s system-of-record into compliance infrastructure. This is the strongest single reason to expect integrated software and services to compound rather than revert, and it is why we model the software layer at 15.72 per cent — the fastest CAGR in the report — despite it being only 7.32 per cent of 2025 value.
Convergence: one credential, four jobs
The duress badge, the nurse call pendant, the location tag and the door credential have been converging for years and are now effectively one device in new builds. Ascom’s alerting and Zebra’s real-time location systems sit in the same clinical workflow as the access control system, and infant protection — Nedap and Securitas among the specialists — has always been a location problem with a liability attached. The commercial consequence is straightforward: a hospital that buys one credential for four jobs buys fewer devices but far more integration, and the integration is where the margin sits. It also raises the cost of getting it wrong, because a single credential controls a door and summons help, and a failure in one function erodes trust in all four.
Screening: the throughput product
Weapons screening is the fastest-growing hardware layer in the report at 15.38 per cent, and it is worth being precise about why, because the obvious explanation is wrong. It is not growth in the number of firearms arriving at hospitals. It is that a screening lane has become operationally acceptable where it previously was not. Baystate Health’s programme, announced on 18 September 2026, sets out the template: walk-through detection at emergency department entrances without requiring visitors to empty pockets or remove shoes, safe for pregnant patients, children, people with pacemakers and people using mobility devices, with a manual alternative, and an explicit commitment that patients arriving with a medical emergency are not delayed and undergo an alternative process. Phase one put systems in the emergency departments; later phases extend to behavioural health units and main entrances.
Read that specification carefully. Every constraint in it is a clinical constraint, not a detection constraint. The hospital is buying assurance that the lane will not become a bottleneck at triage, and that a patient in arrest will never be held at a checkpoint. That is why cheap, high-sensitivity metal detection does not win this market: it produces the wrong kind of certainty. The successful product screens at the rate people actually arrive — including at 2am on a Saturday — and routes the exceptions to a human who is standing there. The growth rate of this layer is a statement about hospital tolerance for friction, not about the threat.
What is not being invented
Almost nothing in this chapter is new physics. The image sensor is a commodity; the analytics are trained models on a well-understood task; the tag is a radio. The innovation is entirely in integration and evidence — making four systems behave as one, and making the resulting record legible to a surveyor, an auditor and a plaintiff. In a market where the specification is written by a regulator and the purchase order is signed against a 1.3 per cent operating margin, that is where the value has to be, and the layer growth rates in this report are simply that sentence expressed in numbers.

- **Innovation:** high
- **Activité des brevets:** moderate
- **Maturité:** growth

## Risque de marché

6. Market risk: two sensitivities, three falsifiers, one scope warning
A forecast that cannot be wrong is not a forecast. This chapter states what would have to be true for the numbers in this report to fail, and what happens to them if the most fragile assumptions break. It also carries a warning about category scope that a careful reader should apply to any figure they see for this market, including ours.
Sensitivity one: services grow at 10 per cent, not 13.70 per cent
The largest single bet in this model is the services layer. If managed services, monitoring and maintenance grow at 10 per cent instead of 13.70 per cent — a plausible outcome if hospital procurement keeps services inside capital projects and never converts them to contracts — that layer reaches USD 10.12 billion rather than USD 13.18 billion in 2033. The market total becomes USD 46.61 billion and the CAGR falls to 11.01 per cent. The direction of the story survives; the mix shift that carries it weakens materially.
Sensitivity two: screening reverts to the market rate
Screening is the second-largest bet, and the most exposed to a single operational failure: if walk-through detection proves to slow emergency arrivals more than hospitals will tolerate, or if published throughput and false-alarm data turn against it, the layer grows at the market rate of 11.90 per cent rather than 15.38 per cent. It would then reach USD 3.29 billion in 2033 instead of USD 4.21 billion, taking the total to USD 48.75 billion and the CAGR to 11.64 per cent. This is a smaller sensitivity than the services case, which is why we weight it less.
Sensitivity three: capital discipline holds at 8 per cent
The most important downside case is not about any layer. It is about the ability of hospitals to buy anything at all. If the 1.3 per cent margin environment persists and security spend is capped at 8 per cent growth across the forecast window, the market reaches USD 37.41 billion by 2033 rather than USD 49.67 billion. That is a 24.7 per cent reduction in the 2033 number, and it is the scenario a hospital supplier should be planning against, because it requires no regulatory reversal — only a continuation of the current financial picture.



Case
Change from base
2033 value (USD bn)
2026–2033 CAGR




Base case
—
49.67
11.90%


Services grow at 10.00%
Services CAGR cut 3.70 points
46.61
11.01%


Screening grows at market rate
Screening CAGR cut 3.48 points
48.75
11.64%


Capital discipline at 8.00%
Whole-market growth capped
37.41
8.00%



Table 7 — Sensitivity tests against the base case. Each case changes one assumption and holds the rest of the model constant.
Three falsifiers
One: a regulator writes a number. The services premium in this report exists because specification is qualitative — a worksite analysis, a documented risk assessment, a tuned analytics configuration. If a regulator replaces that with a pass mark — a stated detection threshold, a numeric false-alarm ceiling, a certified product list — the specification becomes comparable on a price sheet and the premium compresses. This is the most plausible mechanism by which the mix shift reverses, and it would arrive from a well-intentioned simplification.
Two: hospital margins recover durably. Our mix shift assumes capital remains scarce. If operating margins return to the mid single digits and stay there, capital requests become fundable again, hospitals buy new estates rather than services attached to old ones, and hardware outgrows services. The 4.02-point gap between hardware and software-plus-services growth closes. Anyone who expects a durable margin recovery should discount the 49.67 billion figure and treat the 8 per cent case as the central one.
Three: screening fails its cost-benefit test in public. Screening is bought on the promise that it reduces harm without delaying care. If the first large, well-evidenced programme evaluation shows no measurable reduction in incidents against a measurable throughput cost, procurement will not stop screening — but it will stop expanding it, and the 15.38 per cent assumption in the fastest hardware layer goes with it.
And the risk that is epistemic rather than commercial
The HIPAA Security Rule revision is a proposal, not a rule. If it is withdrawn or substantially narrowed, the network-map driver behind the 15.72 per cent software growth weakens and that layer reverts toward the hardware rate. We have not hidden this: it is stated in Chapter 4 and repeated here. A reader who believes the rule will not survive should take roughly three points off the software CAGR and expect the mix shift to arrive later, not never — because accreditation and NIS2 point the same direction without it.
A scope warning about every number in this category
Figures published for “healthcare security systems” differ by a factor of two or more, and the difference is almost never method — it is category boundary. Definitions that count only physical security hardware produce a market less than half the size of ours. We include managed services, screening lanes, the integration software layer and the infant/patient protection category, and we exclude hospital cybersecurity software spend and security officer labour entirely. Our 2025 base of USD 20.21 billion is therefore broader in scope than many figures a reader will encounter, and comparison across sources without reconciling scope is meaningless. Where our model differs from another estimate, the first question to ask is what that estimate excluded.

- **Risque global:** moderate
- **Geopolitical Exposure:** moderate
- **Risque de substitution:** moderate

## Paysage réglementaire

4. Regulatory landscape: four regimes on one estate
Most security markets are regulated at the edges: a fire code here, a privacy statute there. Healthcare is different. Four separate regimes land on the same camera, the same door and the same badge, and each demands a different artefact from the same installation. The commercial consequence is that compliance is not a cost attached to this market — it is the specification. Modifying any one of the four changes the forecast, and the two dates that matter most have both already arrived.
Regime one: accreditation, which audits process
The Joint Commission’s new and revised workplace violence prevention requirements took effect on 1 July 2025 for assisted living communities, nursing care centres and office-based surgery practices, and align with the earlier updates for hospitals, critical access hospitals, behavioural health care and home care. The requirements address training and education, post-incident strategies, reporting systems with data collection and analysis, policies and procedures, leadership oversight, and worksite analysis — with a formal definition of workplace violence added to the glossary.
Read the list again as a buyer. Six of the seven items are documents, and the seventh is oversight of the documents. None of them is a device. An accreditation surveyor will not measure the resolution of your cameras; they will ask to see the analysis, the training record and what changed after the last incident. The hospital that installed an excellent system but cannot produce the analysis fails, and the hospital with an ordinary system and an immaculate file passes. This is the most commonly misunderstood feature of the market, and it is why services grow faster than hardware.
Regime two: the HIPAA Security Rule, which audits records
The Office for Civil Rights issued its notice of proposed rulemaking on 27 December 2024. It proposes to remove the distinction between “required” and “addressable” implementation specifications, require written documentation of all Security Rule policies, procedures, plans and analyses, attach specific compliance time periods to many existing requirements, and require a technology asset inventory and a network map illustrating how electronic protected health information moves — maintained on an ongoing basis, updated at least every twelve months and in response to a change in environment or operations. Risk analysis would need new specificity: a review of the asset inventory and network map, identification of reasonably anticipated threats, vulnerabilities and predisposing conditions, and an assessed risk level for each.
Two things follow. First, the security estate becomes a compliance asset rather than a facilities asset, because it is the only register in the building that already lists devices, locations and firmware. Second, the buyer needs a party who can produce and refresh that register annually. That is a subscription, and it is why we model integrated software at 15.72 per cent.
It is also important to be accurate about status: this is a proposed rule. It has not been finalised, and rules of this scale are amended or abandoned. The forecast assigns it a real but bounded weight — it accelerates the software layer, it does not create it — and Chapter 6 states what happens if it never lands.
Regime three: NIS2, which audits governance
The European Union’s second Network and Information Security Directive, politically agreed in May 2022 and formally adopted in late November 2022, expanded the sectors in scope and, in health, went beyond hospitals to entities carrying out research and development of medicinal products. Member states were required to transpose it into national law, and the obligations it imposes are notable for what they target: management-body accountability for cybersecurity risk, supply-chain security, and incident reporting on a short clock.
For a hospital group, NIS2 makes security a board matter in a way accreditation never does. For a supplier, it makes the supply chain auditable — which means a security integrator selling into European health systems must be able to evidence the security of what it installed, including the firmware lifecycle of the cameras and panels. That is a formalisation of exactly the asset-register capability described above, arriving from a different direction.
Regime four: the procurement rulebook, which audits price
The fourth regime is not a regulator at all. It is the operating constraint that governs every purchase: a finance committee working against a 1.3 per cent adjusted hospital operating margin, in a year when Kaufman Hall reports expenses rising across the board, bad debt, uninsured patients and charity care all increasing, and a larger share of revenue arriving from public rather than private payers. In that setting a capital request for security competes with clinical equipment, and it usually loses.
This is why the managed-services layer at 13.70 per cent is not an anomaly to be explained away. A fixed monthly operating cost with a documented service credit is the only structure that reliably clears a capital committee at 1.3 per cent. The regulatory regimes create the requirement; the procurement regime decides which commercial wrapping gets bought.



Regime
Artefact demanded
Key date
Can a device satisfy it?
Status




Joint Commission workplace violence prevention
Worksite analysis, training records, incident data and analysis, post-incident strategy
1 July 2025
No — process and documentation
In force


HIPAA Security Rule revision
Technology asset inventory, network map, written risk analysis, documented policies
Proposed 27 December 2024
No — but the estate supplies the inventory
Proposed, not final


NIS2 (EU)
Management accountability, supply-chain security evidence, incident reporting
Adopted late November 2022; national transposition
No — governance and evidence
In force, transposing


Hospital capital procurement
Business case cleared against a 1.3 per cent operating margin
Continuous
Only as an operating contract
Binding



Table 5 — Four regimes, what each actually demands, and whether hardware can answer it. The pattern is the argument: three of the four are satisfied by documentation, which is a services and software purchase.
What the regime map implies for a hospital
A hospital that treats these four as separate projects will buy four times and satisfy each regime partially. A hospital that treats them as one estate will buy once and satisfy all four, because the artefacts overlap: the worksite analysis needs the device schedule, the network map is the device schedule, the NIS2 supply-chain evidence is a firmware lifecycle record for the same devices, and the capital committee will fund the cheapest version of all three. That is the commercial case for integrated software in one paragraph, and it is why the software layer is the fastest-growing line in this report despite being the smallest today.

- **Complexité:** high
- **Approval Pathway:** compliance_driven

## Questions fréquemment posées

**Q: How large is the global healthcare security systems market?**

Pheonix Research sizes it at USD 20.21 billion in 2025, rising to USD 49.67 billion by 2033 — an 11.90 per cent CAGR across 2026–2033, or 2.46 times the base year. Installed secure endpoints grow more slowly, from 118.6 million to 214.8 million at 7.71 per cent, which means revenue per endpoint rises 35.7 per cent as services and software take a larger share of the bill.

**Q: Why does the market grow faster than the number of cameras, readers and tags installed?**

Because the buyer is not purchasing equipment. Accreditation, the proposed HIPAA Security Rule inventory and network-map requirement, and NIS2 each demand a document — a worksite analysis, an asset inventory, a network map, an incident record. Producing those documents is services and software work. Managed services and integrated software climb from 30.67 per cent of market value in 2025 to 36.12 per cent in 2033, and that mix shift, not unit growth, is what carries the forecast.

**Q: Is demand driven by crime and violence, or by regulation?**

Both, but regulation converts the concern into a purchase order. Assault rates in US healthcare and social assistance rose from 6.4 to 9.8 per 10,000 full-time-equivalent workers between 2011 and 2021–22, and psychiatric and substance-abuse hospitals run at 138.8 per 10,000 — that is the demand signal. The Joint Commission's workplace violence prevention requirements, effective 1 July 2025, are what turn the signal into a specified, budgeted, auditable programme.

**Q: Which layer of the market grows fastest?**

Integrated software and command platforms, at 15.72 per cent, followed by screening and detection at 15.38 per cent and managed services at 13.70 per cent. Video surveillance grows 11.00 per cent, access control 10.03 per cent, infant and patient protection 9.53 per cent and intrusion and duress 8.81 per cent. The four hardware layers still hold 55.41 per cent of 2033 value, so this is a mix shift inside a growing hardware market, not the replacement of one.
