{"id":3651,"date":"2026-11-17T03:45:00","date_gmt":"2026-11-17T03:45:00","guid":{"rendered":"https:\/\/www.bestheartsurgery.com\/blog\/?p=3651"},"modified":"2026-11-20T07:45:00","modified_gmt":"2026-11-20T07:45:00","slug":"heart-failure-data-diagnosis","status":"publish","type":"post","link":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/","title":{"rendered":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams"},"content":{"rendered":"<p>Every hospital administrator knows the sinking feeling of a morning report that looks perfectly fine and is quietly wrong. The overnight job ran, the dashboard loaded, the numbers have the right shape, yet the bed-occupancy figure belongs to the day before yesterday. That gap between &#8220;the system says it worked&#8221; and &#8220;the data is actually right&#8221; is the core problem DataOps sets out to solve, and it is a problem cardiac programmes and their back offices share with every other data-heavy business.<\/p>\n<p>Here the problem gets handled like a recurring complaint at a clinic desk: name the symptoms, narrow the cause, then choose a remedy that fits. It stays on the administrative side, meaning reports, schedules and records, and says nothing about patient care itself.<\/p>\n<h2>The presenting symptom: green lights, wrong numbers<\/h2>\n<p>Picture a reporting pipeline that copies appointment and billing records from several source systems into one summary every night. Each stage logs &#8220;completed&#8221;. Yet on Mondays the summary is thin, and by Wednesday somebody has noticed that an entire clinic is missing. The Google SRE Workbook, as summarised in the Ops Atlas, describes exactly this shape of failure: each stage may log a clean finish even though rows vanish in the hand-off between two of them. A successful job tells you the code ran. It tells you nothing about whether the rows that came out are the rows that should have.<\/p>\n<p>That is why a working definition of DataOps matters here. In the Atlas&#8217;s telling, the discipline means operating pipelines the way good software teams operate services: reviewed, tested edits, an inspection of each load before anyone can see it, and watchfulness once it is live. The final clause is the one most reporting teams skip.<\/p>\n<h2>Differential diagnosis: where do bad numbers come from?<\/h2>\n<p>Before prescribing anything, separate the candidates. In practice they fall into four groups.<\/p>\n<ul>\n<li><strong>A change to the code.<\/strong> Someone edited a transformation and it now drops or duplicates rows. This is the familiar software failure, and version control plus automated tests catch most of it.<\/li>\n<li><strong>A change in the source.<\/strong> A department renames a status value or starts sending dates in a new format. No code of yours changed, yet your output did.<\/li>\n<li><strong>Late or partial arrival.<\/strong> A feed lands hours behind schedule, or only half of it lands. The job still runs on whatever is there.<\/li>\n<li><strong>Drift nobody is measuring.<\/strong> Volumes slide down a little each week and the average quietly follows them.<\/li>\n<\/ul>\n<p>Two loops matter, according to the Atlas. The change loop covers modifications to code, which are protected by review and tests just as in ordinary software delivery. The run loop covers the data itself, which changes every single time the pipeline executes, with no deployment to review. Three of the four causes above live in the run loop, which is precisely why a hospital with excellent code review can still publish a wrong figure.<\/p>\n<h2>Treatment one: check before you publish<\/h2>\n<p>The first remedy is a habit the Atlas calls write-audit-publish. Fresh rows land first in a side area that no report reads. Checks run there: counts against the source, key columns without blanks, totals that reconcile. If the blocking ones pass, the data is promoted to the place where reports look; if one fails, the batch is set aside and yesterday&#8217;s good copy stays on screen.<\/p>\n<p>Think of it as a review before the summary goes out, not after. According to the Atlas the pattern costs extra latency and sometimes duplicate writes, so it is kept for tier-one outputs such as the daily census or the revenue summary.<\/p>\n<h2>Treatment two: make the source accountable<\/h2>\n<p>Checks at the end of the pipeline find problems late. A cheaper remedy is to agree, at the boundary where data enters, what the producer promises. This is the idea of a data contract: the team that owns the source states the columns, their meaning, the quality rules and how fresh the feed will be, and changes that break the promise are caught before they spread. The Atlas names the Open Data Contract Standard, maintained under the Linux Foundation&#8217;s Bitol effort, as one written format.<\/p>\n<p>A related caution from the same source: simple schema compatibility checks only look at structure. If a status called &#8220;returned&#8221; suddenly means something different, the column name and type are unchanged and the structural check passes. Contracts earn their keep by also carrying meaning, quality rules and a named owner. If you want a sibling perspective on growing a data function, <a href=\"https:\/\/www.bestheartsurgery.com\/blog\/dataops-consulting-when-and-how-to-scale-your-data-operations\/\">a post on knowing when to bring in outside help to scale data operations<\/a> covers the organisational side of the question.<\/p>\n<h2>Treatment three: watch for the slow decline<\/h2>\n<p>The fourth cause, silent drift, needs monitoring rather than gating. The Atlas lists five things worth watching on a feed: freshness, volume, schema, value distribution and lineage. Freshness answers &#8220;did it arrive on time&#8221;, volume answers &#8220;did enough of it arrive&#8221;, and lineage answers &#8220;if this table is wrong, which reports sit downstream&#8221;.<\/p>\n<p>Be careful with the alarm thresholds. The usual recipe raises an alarm at three standard deviations from the mean, yet the Atlas warns that the recipe presumes one steady process. Appointment volume in a hospital has a weekly beat: busy weekdays, quiet weekends, so really two processes sharing one chart. In the Atlas lab, a baseline pooled over every day let a half-empty load slip through, one about a fifth under an ordinary weekday, while limits fitted to weekdays only raised the flag. Give each rhythm its own yardstick.<\/p>\n<p>There is also arithmetic to respect on the other side. The other side of the ledger is noise. A point strays outside three-sigma limits by pure chance about 0.27 percent of the time, so a schedule of 600 daily checks will cry wolf close to twice a day.<\/p>\n<h2>Where detection time hides<\/h2>\n<p>One example in the Atlas deserves repeating because it changes where people spend effort. Take four incidents with a combined 43.75 hours of downtime. Of that, 32.75 hours, 75 percent, was the time spent not knowing anything was wrong. Only the remainder was repair. The lesson is that faster fixing helps far less than faster noticing. One metric the Atlas floats: count the incidents that readers discovered before your monitors did, as a fraction of all incidents. Half of them were, in that sample. When that share shrinks over the quarters, monitoring is genuinely improving.<\/p>\n<h2>A short prescription for a reporting office<\/h2>\n<ol>\n<li>List the five or six outputs that leadership and finance actually act on, and call them tier one.<\/li>\n<li>Put the pipeline code under version control so every change has a reviewer and a history.<\/li>\n<li>Add freshness, volume and key-column checks to those outputs first, before anything fancier.<\/li>\n<li>Hold tier-one loads in a staging area and publish only when blocking checks pass.<\/li>\n<li>Keep a plain incident log of who found each problem and how long it took.<\/li>\n<\/ol>\n<p>If your teams also write about operational technology for hospitals, <a href=\"https:\/\/www.bestheartsurgery.com\/blog\/how-telehealth-supports-follow-up-care-after-heart-surgery\/\">the article on how remote follow-up fits around surgical recovery<\/a> is a good example of a service that quietly depends on the kind of reliable data feeds described above, even though it never mentions them.<\/p>\n<h2>Closing the case<\/h2>\n<p>The pattern across all of this is that trust in a number is earned at three moments: when the change is made, when the data lands, and in the days afterwards. Treat the green light on the job as a statement about code only. The entry at <a href=\"https:\/\/www.xopsschool.com\/dataops\/\">the Ops Atlas page on DataOps<\/a> admits the field&#8217;s vocabulary is still unsettled, which is a fair nudge to adopt habits rather than labels. Start with the few outputs that matter, add checks you can explain to a non-technical colleague, and measure how often someone else finds your mistakes before you do.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When every nightly job reports success but the figures are off, the fault usually sits in the run loop. A DataOps diagnosis for hospital reporting teams.<\/p>\n","protected":false},"author":13,"featured_media":3652,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1406],"tags":[],"class_list":["post-3651","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>Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals<\/title>\n<meta name=\"description\" content=\"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.\" \/>\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\/heart-failure-data-diagnosis\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals\" \/>\n<meta property=\"og:description\" content=\"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/\" \/>\n<meta property=\"og:site_name\" content=\"Best Heart Surgery Hospitals\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T03:45:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-20T07:45:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-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=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/\"},\"author\":{\"name\":\"Mukesh Siddiqui\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#\\\/schema\\\/person\\\/564a5ffd6467b9439d68d1ef43d1d89f\"},\"headline\":\"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams\",\"datePublished\":\"2026-11-17T03:45:00+00:00\",\"dateModified\":\"2026-11-20T07:45:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/\"},\"wordCount\":1306,\"image\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3971468-banner.png\",\"articleSection\":[\"Healthcare Technology\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/\",\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/\",\"name\":\"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3971468-banner.png\",\"datePublished\":\"2026-11-17T03:45:00+00:00\",\"dateModified\":\"2026-11-20T07:45:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/#\\\/schema\\\/person\\\/564a5ffd6467b9439d68d1ef43d1d89f\"},\"description\":\"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3971468-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3971468-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/heart-failure-data-diagnosis\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.bestheartsurgery.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams\"}]},{\"@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":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals","description":"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.","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\/heart-failure-data-diagnosis\/","og_locale":"en_US","og_type":"article","og_title":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals","og_description":"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.","og_url":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/","og_site_name":"Best Heart Surgery Hospitals","article_published_time":"2026-11-17T03:45:00+00:00","article_modified_time":"2026-11-20T07:45:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-banner.png","type":"image\/png"}],"author":"Mukesh Siddiqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Mukesh Siddiqui","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#article","isPartOf":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/"},"author":{"name":"Mukesh Siddiqui","@id":"https:\/\/www.bestheartsurgery.com\/blog\/#\/schema\/person\/564a5ffd6467b9439d68d1ef43d1d89f"},"headline":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams","datePublished":"2026-11-17T03:45:00+00:00","dateModified":"2026-11-20T07:45:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/"},"wordCount":1306,"image":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#primaryimage"},"thumbnailUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-banner.png","articleSection":["Healthcare Technology"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/","url":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/","name":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams - Best Heart Surgery Hospitals","isPartOf":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#primaryimage"},"image":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#primaryimage"},"thumbnailUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-banner.png","datePublished":"2026-11-17T03:45:00+00:00","dateModified":"2026-11-20T07:45:00+00:00","author":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/#\/schema\/person\/564a5ffd6467b9439d68d1ef43d1d89f"},"description":"A problem-and-solution walk through DataOps for hospital reporting: why green jobs still publish wrong numbers, and which checks catch them early.","breadcrumb":{"@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#primaryimage","url":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-banner.png","contentUrl":"https:\/\/www.bestheartsurgery.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3971468-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.bestheartsurgery.com\/blog\/heart-failure-data-diagnosis\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.bestheartsurgery.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Right Report, Wrong Numbers: A DataOps Diagnosis for Cardiac Teams"}]},{"@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\/3651","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=3651"}],"version-history":[{"count":1,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts\/3651\/revisions"}],"predecessor-version":[{"id":3770,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/posts\/3651\/revisions\/3770"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/media\/3652"}],"wp:attachment":[{"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/media?parent=3651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/categories?post=3651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bestheartsurgery.com\/blog\/wp-json\/wp\/v2\/tags?post=3651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}