{"id":3603,"date":"2026-11-15T12:45:00","date_gmt":"2026-11-15T12:45:00","guid":{"rendered":"https:\/\/www.bestheartsurgery.com\/blog\/?p=3603"},"modified":"2026-11-16T21:45:00","modified_gmt":"2026-11-16T21:45:00","slug":"vulnerabilityops-state-of-flow","status":"publish","type":"post","link":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/","title":{"rendered":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today"},"content":{"rendered":"<p>Hospital technology teams spend much of their year answering one plain question: of everything that is currently open in our systems, what gets fixed first, who owns it, and how do we know it is really closed? That question now has a name in security circles. VulnerabilityOps describes the habit of treating vulnerability handling as steady throughput, not an occasional sweep, and the last twelve months have given us enough numbers to say where the practice stands.<\/p>\n<p>What follows is a status report aimed at administrators and IT coordinators in healthcare settings. It stays on the operations side: queues, clocks, ownership and evidence. Nothing here is clinical guidance, and nothing here concerns any particular institution.<\/p>\n<h2>Why VulnerabilityOps is showing up now<\/h2>\n<p>The vocabulary is fresh. Readers can see how <a href=\"https:\/\/www.xopsschool.com\/vulnerabilityops\/\">the Ops Atlas entry on VulnerabilityOps<\/a> frames it: no standards body owns the label, and the Atlas treats it as a young name for vulnerability handling arranged as a flow, with triage, a dated owner, proof of closure and measurement. It also notes that the underlying work is old. NIST published its enterprise patch and vulnerability guidance (SP 800-40 Revision 4) in 2022, and the CIS Controls have carried a vulnerability-management item for years. What is new is the emphasis on throughput rather than on the size of the pile.<\/p>\n<p>Two pressures explain the timing. The first is volume. Annual CVE publication has roughly 2.6 times its 2020 level by 2025, while January to June 2026 had already contributed nearly 36 thousand more. The second is speed on the attacker side. The Atlas also quotes Mandiant: bugs that attackers used in 2023 were being exploited about five days after disclosure on average (extreme cases excluded), where the 2018-2019 average ran past two months.<\/p>\n<h2>The capacity gap, in numbers<\/h2>\n<p>A hospital network runs a long tail of equipment: administrative servers, imaging workstations, building systems, vendor-managed appliances. Every one of those produces findings. Capacity is the other half. The Atlas leans on a 2019 survey covering about 300 companies, where the typical firm retired roughly a tenth of its open findings each month and the top group managed about 2.5 times that pace.<\/p>\n<p>Lay the two figures next to each other and the problem takes shape. Inflow has multiplied, while the usual closure rate has not visibly moved. A queue that receives more than it clears simply gets longer, and a long queue is where the dangerous items hide.<\/p>\n<ul>\n<li><strong>Exploitation is the front door.<\/strong> In the 2026 Verizon breach report, as the Atlas summarises it, abuse of a software flaw was behind 31 percent of first entries, which made it the top route.<\/li>\n<li><strong>Follow-through is weak.<\/strong> The same summary adds that only 26 percent of known-exploited catalogue entries were fully fixed in 2025 (a year before, the figure stood at 38 percent), with 43 days as the midpoint for getting there.<\/li>\n<li><strong>Old advice is not enough.<\/strong> Fixing whatever carries the highest severity score first does not keep pace with either trend.<\/li>\n<\/ul>\n<h2>From severity bands to clocks<\/h2>\n<p>The clearest sign of change is policy. In June 2026 a US federal directive, BOD 26-04, stopped using severity bands to set deadlines. Four yes\/no style questions now drive the clock: is the system reachable from the public internet, does the known-exploited catalogue list the flaw, could an attacker script the abuse end to end, and how severe would the technical damage be? Only US federal civilian agencies are bound by it, so a hospital group has no duty to copy the scheme. Still, the Atlas treats it as a useful template because the logic transfers.<\/p>\n<p>The examples are instructive. An exposed, listed, automatable flaw with total impact gets three days plus a forensic look at whether it was already used. An exposed flaw that is not on the list and has only partial impact gets somewhere between fourteen and sixty days. A flaw on an internal machine that is unlisted and cannot be automated can simply ride along with the next upgrade. When a fact is unknown, the defaults lean cautious: unknown automation is treated as &#8220;no&#8221;, while unknown impact is treated as &#8220;total&#8221;. The clock starts at listing or detection, whichever comes first, and the directive issues no waivers.<\/p>\n<p>For a hospital IT desk the translation is easy to picture. A patient-portal web server facing the internet and an offline records archive should not share a deadline simply because the same scanner flagged both as high.<\/p>\n<h2>Signals, in order of trust<\/h2>\n<p>The Atlas ranks the inputs. Evidence of real exploitation outranks a probability estimate, and a probability estimate outranks a severity score. The probability model, EPSS, starts from a modest baseline: in any given month, between 1.5 and 3 percent of the flaws on the public list turn up in real attacks. A low score can justify waiting but never justifies forgetting. In the Atlas wording, a 5 percent score still means roughly a one-in-twenty chance of activity within a month.<\/p>\n<p>One habit the Atlas flags as an error is multiplying the probability score by the severity score to produce a single number. The standards body that maintains the model has a name for this, &#8220;score laundering&#8221;, because the product looks precise while meaning nothing. Keep the signals separate and read them in order.<\/p>\n<h2>Data quality is slipping underneath us<\/h2>\n<p>A trend that rarely makes the headlines is the state of the public enrichment data that scanners lean on. Since mid-April 2026 the national database has fully enriched only the entries it prioritises. As of mid-October 2026 the Atlas records tens of thousands of entries marked as deferred and several thousand waiting for enrichment. Teams that assumed every record would arrive with clean product and weakness metadata now need to tolerate gaps, and to prefer feeds that carry exploitation evidence.<\/p>\n<p>Regulators elsewhere are moving as well. The Atlas notes that the European vulnerability database is operating under the NIS2 regime, that FedRAMP programmes are due to align with the federal clocks by 7 December 2026, and that manufacturer reporting duties under the EU Cyber Resilience Act, including a 24-hour early warning, have applied since 11 September 2026. Hospitals that buy devices from several regions will feel these changes through their suppliers before they feel them directly.<\/p>\n<h2>What a mature flow looks like<\/h2>\n<p>The Atlas sketches a ladder of five rungs that climbs from reacting to scan output, through owned queues and a risk-informed policy, up to flow management and finally adaptive behaviour. Most organisations sit at the first or second rung. The step that matters most is the second, because a finding without a named, dated owner has no way to leave the queue.<\/p>\n<p>Closure is where discipline shows. The Atlas insists that a fix counts only when evidence says so: one of four things: a rescan that logs in with credentials, a direct test of the configuration, a rebuilt container image with a changed digest, or a challenge that reviewers upheld. A ticket marked resolved is not evidence. Its Citrix Bleed lesson adds that the definition of &#8220;fixed&#8221; sometimes has to include more than a patch; for that 2023 case, active sessions needed to be ended too, or an attacker could keep a hijacked session alive after the update.<\/p>\n<p>Measurement follows the same logic. The flow view asks whether arrivals are being cleared faster than they land, tier by tier. A ratio above one means the backlog is growing. The Atlas also warns about a trap: the median age of old items can improve while the backlog swells, because a stream of new arrivals dilutes the old ones. Age without that ratio is a flattering half-picture.<\/p>\n<h2>Where this leaves a hospital IT team<\/h2>\n<p>Three observations seem safe. First, the practice is moving from &#8220;how severe is it&#8221; toward &#8220;how exposed, how likely, and who is on the hook&#8221;. Second, evidence-based closure is becoming the dividing line between a dashboard that looks healthy and a system that is. Third, public data is getting thinner, so local tagging of what each asset does and where it sits matters more each year.<\/p>\n<p>Readers who want practical neighbouring reading on this site can start with <a href=\"https:\/\/www.bestheartsurgery.com\/blog\/how-telehealth-supports-follow-up-care-after-heart-surgery\/\">a piece on how remote follow-up services extend care after surgery<\/a>, which shows how much hospital workflow now leans on connected software, and a short note on <a href=\"https:\/\/www.bestheartsurgery.com\/blog\/how-sre-training-helps-build-reliable-skills-for-modern-systems\/\">why reliability training builds dependable habits for modern systems<\/a>. Both help explain why a hospital IT desk needs a dependable queue for the weaknesses its systems collect.<\/p>\n<p>A sensible next step for a coordinator is small: list the systems that face outward, list who owns each, and ask for the last verified closure date on the open items. If nobody can answer that third question, the flow has not started yet, and that gap is the most honest starting point available.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A state-of-the-field look at VulnerabilityOps for hospital IT desks: rising volumes, new remediation clocks, and why verified closure matters.<\/p>\n","protected":false},"author":13,"featured_media":3604,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1406],"tags":[],"class_list":["post-3603","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-technology"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals<\/title>\n<meta name=\"description\" content=\"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals\" \/>\n<meta property=\"og:description\" content=\"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/\" \/>\n<meta property=\"og:site_name\" content=\"Best Heart Surgery Hospitals\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-15T12:45:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-16T21:45:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Mukesh Siddiqui\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mukesh Siddiqui\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/\"},\"author\":{\"name\":\"Mukesh Siddiqui\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#\\\/schema\\\/person\\\/564a5ffd6467b9439d68d1ef43d1d89f\"},\"headline\":\"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today\",\"datePublished\":\"2026-11-15T12:45:00+00:00\",\"dateModified\":\"2026-11-16T21:45:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/\"},\"wordCount\":1446,\"image\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-2897691-banner.png\",\"articleSection\":[\"Healthcare Technology\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/\",\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/\",\"name\":\"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-2897691-banner.png\",\"datePublished\":\"2026-11-15T12:45:00+00:00\",\"dateModified\":\"2026-11-16T21:45:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#\\\/schema\\\/person\\\/564a5ffd6467b9439d68d1ef43d1d89f\"},\"description\":\"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-2897691-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-2897691-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/vulnerabilityops-state-of-flow\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/\",\"name\":\"My blog\",\"description\":\"Explore the World\u2019s Leading Heart Surgery Centers\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#\\\/schema\\\/person\\\/564a5ffd6467b9439d68d1ef43d1d89f\",\"name\":\"Mukesh Siddiqui\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g\",\"caption\":\"Mukesh Siddiqui\"},\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/author\\\/mukesh-siddiqui\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals","description":"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/","og_locale":"en_US","og_type":"article","og_title":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals","og_description":"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.","og_url":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/","og_site_name":"Best Heart Surgery Hospitals","article_published_time":"2026-11-15T12:45:00+00:00","article_modified_time":"2026-11-16T21:45:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png","type":"image\/png"}],"author":"Mukesh Siddiqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Mukesh Siddiqui","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#article","isPartOf":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/"},"author":{"name":"Mukesh Siddiqui","@id":"https:\/\/www.bestheartsurgery.com\/blog\/#\/schema\/person\/564a5ffd6467b9439d68d1ef43d1d89f"},"headline":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today","datePublished":"2026-11-15T12:45:00+00:00","dateModified":"2026-11-16T21:45:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/"},"wordCount":1446,"image":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#primaryimage"},"thumbnailUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png","articleSection":["Healthcare Technology"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/","url":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/","name":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today - Best Heart Surgery Hospitals","isPartOf":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#primaryimage"},"image":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#primaryimage"},"thumbnailUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png","datePublished":"2026-11-15T12:45:00+00:00","dateModified":"2026-11-16T21:45:00+00:00","author":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/#\/schema\/person\/564a5ffd6467b9439d68d1ef43d1d89f"},"description":"Hospital IT teams face rising vulnerability volumes. See where VulnerabilityOps stands in 2026: clocks, signals, data gaps and what to do next.","breadcrumb":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#primaryimage","url":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png","contentUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-2897691-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.bestheartsurgery.com\/blog\/vulnerabilityops-state-of-flow\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.bestheartsurgery.com\/blog\/"},{"@type":"ListItem","position":2,"name":"VulnerabilityOps in 2026: Where Hospital IT Queues Stand Today"}]},{"@type":"WebSite","@id":"https:\/\/www.bestheartsurgery.com\/blog\/#website","url":"https:\/\/www.bestheartsurgery.com\/blog\/","name":"My blog","description":"Explore the World\u2019s Leading Heart Surgery Centers","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.bestheartsurgery.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.bestheartsurgery.com\/blog\/#\/schema\/person\/564a5ffd6467b9439d68d1ef43d1d89f","name":"Mukesh Siddiqui","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9822c153c1be6a46b13dfccdc8d59faca69859f6baa6d5c9143a16bb2494fe39?s=96&d=mm&r=g","caption":"Mukesh Siddiqui"},"url":"https:\/\/www.bestheartsurgery.com\/blog\/author\/mukesh-siddiqui\/"}]}},"_links":{"self":[{"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts\/3603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/comments?post=3603"}],"version-history":[{"count":1,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts\/3603\/revisions"}],"predecessor-version":[{"id":3703,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts\/3603\/revisions\/3703"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/media\/3604"}],"wp:attachment":[{"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/media?parent=3603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/categories?post=3603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/tags?post=3603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}