{"id":3176,"date":"2026-11-16T04:05:00","date_gmt":"2026-11-16T04:05:00","guid":{"rendered":"https:\/\/www.kneehospitals.com\/blog\/?p=3176"},"modified":"2026-11-18T09:05:00","modified_gmt":"2026-11-18T09:05:00","slug":"cloudops-recovery-postures-compared","status":"publish","type":"post","link":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/","title":{"rendered":"Three Recovery Postures Compared: A CloudOps Evidence Review"},"content":{"rendered":"<p>Software teams that support hospital operations sooner or later face the same architectural question: when the cloud provider has a bad day, which recovery posture actually holds up? Three answers circulate in meetings. Trust the contract, copy everything to a second Region, or build a second environment on a second cloud. This comparison tests those options against the public record, taking the Ops Atlas as its reference text. It concerns non-clinical systems only, such as scheduling, portals and back-office tools, and it makes no medical claims.<\/p>\n<h2>The yardstick: what a recovery plan must do<\/h2>\n<p>Before comparing anything, fix the criteria. A recovery posture should be judged on four questions. How long until the service is usable again? How many steps in the plan depend on asking the provider to create or change something? How much extra complexity does the posture add for everyday operation? And what does it cost in attention, since small teams have little to spare?<\/p>\n<p>The second question carries most of the weight. In <a href=\"https:\/\/www.xopsschool.com\/cloudops\/\">the Atlas&#8217;s CloudOps write-up<\/a>, a tighter recovery-time goal should mean fewer control-plane operations in the plan, and for the most critical tier the plan should need none, relying on data-plane activity only. The reasoning comes from observed incidents: when a provider&#8217;s management layer misbehaves, systems already running often continue, while anything that must launch or reconfigure resources stalls.<\/p>\n<h2>Option A: rely on the service-level agreement<\/h2>\n<p>The simplest posture is to deploy in one Region, accept the provider&#8217;s published availability promise and move on. It has real merits. It is cheap, easy to operate and easy to explain. For internal tools whose downtime is an inconvenience rather than a crisis, it may be entirely adequate.<\/p>\n<p>The weakness is what the promise actually pays. The Atlas notes that the 99.99 percent availability promise for compute in a Region is honoured by crediting the customer, and credits are a discount on a future bill and not a restoration of lost availability. Credits do not bring back an appointment-booking morning. The evidence from October 2025 underlines this: in one provider&#8217;s us-east-1 Region, attempts to start new instances failed across a window of about eight hours, and a database service produced errors for around 172 minutes overall. A team that had relied on the promise alone would have been left waiting.<\/p>\n<ul>\n<li><strong>Recovery time:<\/strong> depends entirely on the provider.<\/li>\n<li><strong>Control-plane steps:<\/strong> not applicable, because there is no plan beyond waiting.<\/li>\n<li><strong>Everyday complexity:<\/strong> lowest of the three.<\/li>\n<li><strong>Attention cost:<\/strong> minimal.<\/li>\n<\/ul>\n<h2>Option B: a second Region in the same cloud<\/h2>\n<p>The next posture keeps the same provider but maintains a copy elsewhere, either warm or cold. It is the usual first upgrade, and it brings genuine protection against a failure confined to one Region. Data replication, health checks and a failover runbook are the main ingredients.<\/p>\n<p>Its subtlety lies in how failover is performed. If the runbook says &#8220;launch the new servers, update the routing, restore the database&#8221;, every verb is a control-plane operation, and those operations can be impaired at exactly the moment they are needed. During that October 2025 incident, as the Atlas recounts it, console logins in other Regions broke for roughly an hour and a half, while trouble with the identity service and a warehouse product spread to all Regions. A second Region protected the data; it did not guarantee that the steps to switch over would work.<\/p>\n<p>There is a better version of this option, which the Atlas calls static stability. The standby is already running at full size, traffic shifting happens through data-plane mechanisms, and nobody needs to create anything during the crisis. It costs more to hold idle capacity, and quotas must be large enough in the standby Region to carry the load, but the plan no longer depends on the fragile part.<\/p>\n<ul>\n<li><strong>Recovery time:<\/strong> as short as the design allows, if the standby is pre-built.<\/li>\n<li><strong>Control-plane steps:<\/strong> several in the cold version, zero in the pre-built version.<\/li>\n<li><strong>Everyday complexity:<\/strong> moderate: replication, drift checks, extra quotas.<\/li>\n<li><strong>Attention cost:<\/strong> moderate, and it grows with each service added.<\/li>\n<\/ul>\n<h2>Option C: a second cloud<\/h2>\n<p>The third posture is the most dramatic: a parallel environment on a different provider. The intuition is attractive, since one company&#8217;s outage cannot reach another&#8217;s. Yet the Atlas lists reflexive multi-cloud among its anti-patterns, and its reasoning is worth reading closely. Choosing a second cloud means taking on another management layer, another way of signing in and another rulebook of guardrails, all to be designed, tested and kept in step. Even a provider&#8217;s own guidance, as the Atlas reports it, concedes that the added complexity may outweigh the initial benefits.<\/p>\n<p>There are good reasons to choose it nonetheless. Regulation is one. The EU&#8217;s digital operational resilience rules have applied since 17 January 2025 and ask regulated financial entities to maintain exit strategies, and the EU Data Act removes charges for switching providers from 12 January 2027. A hospital group is not a bank, so these texts may not bind it directly, but they show the direction of travel: documenting how you would leave is becoming ordinary due diligence. Having rehearsed a move is different from running in two places at all times, though.<\/p>\n<ul>\n<li><strong>Recovery time:<\/strong> potentially good, but only if the second environment is exercised regularly.<\/li>\n<li><strong>Control-plane steps:<\/strong> a second set to manage, with a different console and different failure modes.<\/li>\n<li><strong>Everyday complexity:<\/strong> highest.<\/li>\n<li><strong>Attention cost:<\/strong> high; the team must be fluent in two ecosystems.<\/li>\n<\/ul>\n<h2>Side-by-side reading<\/h2>\n<p>Setting the three against each other produces a clearer picture than any one in isolation.<\/p>\n<ol>\n<li>Option A is honest about being a bet on the provider. It suits low-stakes tools.<\/li>\n<li>Option B in its pre-built form gives the strongest ratio of protection to effort for important services, because it removes dependence on the provider&#8217;s management layer without doubling the toolset.<\/li>\n<li>Option C buys independence from a single company at a steep price in complexity, and its benefits show up only if the team practises using it.<\/li>\n<\/ol>\n<p>None of this is a universal ranking. The Atlas itself frames its views as editorial, noting that the field is emerging and has no neutral standard. A fair reading is that the posture should follow the importance of the service: tier-one systems deserve the zero-control-plane design, while lesser systems can sit comfortably in Option A.<\/p>\n<h2>How to test your own claim<\/h2>\n<p>Whichever option a team picks, the Atlas suggests proving it with a rehearsal. A game day that simulates an unreachable control plane will show whether the plan truly avoids it. Measure how many control-plane steps the failover contains, and aim for zero on the tier that matters. Also check the monitoring: a June 2025 outage at another provider left some customers without dashboards because their monitoring ran on the same platform.<\/p>\n<p>For readers who want context beyond this single comparison, a discussion of <a href=\"https:\/\/www.kneehospitals.com\/blog\/rethinking-it-operations-the-unified-architecture-of-xops\/\">how a unified XOps architecture reshapes IT operations<\/a> places this topic in a larger frame, and a practical article about <a href=\"https:\/\/www.kneehospitals.com\/blog\/streamlining-software-and-cloud-operations-with-expert-engineering-services\/\">smoothing out software and cloud work with outside engineering help<\/a> covers the delivery side.<\/p>\n<h2>What the comparison leaves out<\/h2>\n<p>Several factors sit beyond this review. Data-residency obligations may limit which Regions are even eligible. Licence terms can make a standby expensive. And people matter: a posture that only one engineer understands is weaker than its diagram suggests. A fair assessment records these constraints next to the technical scores, so that decision-makers see the whole trade-off instead of a tidy table that hides the awkward parts.<\/p>\n<h2>Verdict<\/h2>\n<p>If a hospital software team can afford only one improvement, the evidence favours pre-building a standby in a second Region and designing failover to use only data-plane actions. If it cannot afford even that, it should at least write down which services are in Option A by choice rather than by accident. And if a second cloud is on the table, treat it as a project with its own budget and rehearsals, not as a switch to flip. The reasoning is mostly about arithmetic and attention, and it holds whatever the sector.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Contract promise, second Region or second cloud: a comparison of three recovery postures against public outage evidence and the Ops Atlas.<\/p>\n","protected":false},"author":11,"featured_media":3177,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1656],"tags":[],"class_list":["post-3176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-software"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals<\/title>\n<meta name=\"description\" content=\"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.\" \/>\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.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals\" \/>\n<meta property=\"og:description\" content=\"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/\" \/>\n<meta property=\"og:site_name\" content=\"Knee Hospitals\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-16T04:05:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-18T09:05:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-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=\"Anil Nair\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Anil Nair\" \/>\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.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/\"},\"author\":{\"name\":\"Anil Nair\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/4d12821d4d9c17d9079ff50d30d6a676\"},\"headline\":\"Three Recovery Postures Compared: A CloudOps Evidence Review\",\"datePublished\":\"2026-11-16T04:05:00+00:00\",\"dateModified\":\"2026-11-18T09:05:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/\"},\"wordCount\":1340,\"image\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3612860-banner.png\",\"articleSection\":[\"Healthcare Software\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/\",\"url\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/\",\"name\":\"Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3612860-banner.png\",\"datePublished\":\"2026-11-16T04:05:00+00:00\",\"dateModified\":\"2026-11-18T09:05:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/4d12821d4d9c17d9079ff50d30d6a676\"},\"description\":\"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3612860-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3612860-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/cloudops-recovery-postures-compared\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Three Recovery Postures Compared: A CloudOps Evidence Review\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/\",\"name\":\"My blog\",\"description\":\"Expert Care for Your Knees, Restoring Mobility and Quality of Life\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/4d12821d4d9c17d9079ff50d30d6a676\",\"name\":\"Anil Nair\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g\",\"caption\":\"Anil Nair\"},\"url\":\"https:\\\/\\\/www.kneehospitals.com\\\/blog\\\/author\\\/anil-nair\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals","description":"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.","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.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/","og_locale":"en_US","og_type":"article","og_title":"Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals","og_description":"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.","og_url":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/","og_site_name":"Knee Hospitals","article_published_time":"2026-11-16T04:05:00+00:00","article_modified_time":"2026-11-18T09:05:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-banner.png","type":"image\/png"}],"author":"Anil Nair","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Anil Nair","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#article","isPartOf":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/"},"author":{"name":"Anil Nair","@id":"https:\/\/www.kneehospitals.com\/blog\/#\/schema\/person\/4d12821d4d9c17d9079ff50d30d6a676"},"headline":"Three Recovery Postures Compared: A CloudOps Evidence Review","datePublished":"2026-11-16T04:05:00+00:00","dateModified":"2026-11-18T09:05:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/"},"wordCount":1340,"image":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#primaryimage"},"thumbnailUrl":"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-banner.png","articleSection":["Healthcare Software"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/","url":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/","name":"Three Recovery Postures Compared: A CloudOps Evidence Review - Knee Hospitals","isPartOf":{"@id":"https:\/\/www.kneehospitals.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#primaryimage"},"image":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#primaryimage"},"thumbnailUrl":"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-banner.png","datePublished":"2026-11-16T04:05:00+00:00","dateModified":"2026-11-18T09:05:00+00:00","author":{"@id":"https:\/\/www.kneehospitals.com\/blog\/#\/schema\/person\/4d12821d4d9c17d9079ff50d30d6a676"},"description":"Comparing three cloud recovery postures for hospital software teams: SLA reliance, a second Region and a second cloud, judged by CloudOps evidence.","breadcrumb":{"@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#primaryimage","url":"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-banner.png","contentUrl":"https:\/\/www.kneehospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3612860-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.kneehospitals.com\/blog\/cloudops-recovery-postures-compared\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.kneehospitals.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Three Recovery Postures Compared: A CloudOps Evidence Review"}]},{"@type":"WebSite","@id":"https:\/\/www.kneehospitals.com\/blog\/#website","url":"https:\/\/www.kneehospitals.com\/blog\/","name":"My blog","description":"Expert Care for Your Knees, Restoring Mobility and Quality of Life","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.kneehospitals.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.kneehospitals.com\/blog\/#\/schema\/person\/4d12821d4d9c17d9079ff50d30d6a676","name":"Anil Nair","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5b6688c0d55dcc8367e53658ff9350997e6aa6c261e805a03d367fcfdf3dab3c?s=96&d=mm&r=g","caption":"Anil Nair"},"url":"https:\/\/www.kneehospitals.com\/blog\/author\/anil-nair\/"}]}},"_links":{"self":[{"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/comments?post=3176"}],"version-history":[{"count":1,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3176\/revisions"}],"predecessor-version":[{"id":3289,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3176\/revisions\/3289"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/media\/3177"}],"wp:attachment":[{"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/media?parent=3176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/categories?post=3176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kneehospitals.com\/blog\/wp-json\/wp\/v2\/tags?post=3176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}