{"id":3244,"date":"2026-11-16T18:05:00","date_gmt":"2026-11-16T18:05:00","guid":{"rendered":"https:\/\/www.hiphospitals.com\/blog\/?p=3244"},"modified":"2026-11-19T12:05:00","modified_gmt":"2026-11-19T12:05:00","slug":"sysops-clocks-explained-evidence","status":"publish","type":"post","link":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/","title":{"rendered":"Why Server Clocks Matter: A Plain-Language SysOps Explainer"},"content":{"rendered":"<p>Ask a room of technicians which part of server care is the most glamorous and nobody will say &#8220;the clock&#8221;. Yet a surprising share of confusing outages trace back to time: certificates that look expired, logs that cannot be lined up, scheduled jobs that fire twice or not at all. This explainer uses plain language and evidence to show why timekeeping sits at the heart of SysOps, the everyday practice of keeping individual servers in good order. It is a technology piece with no medical content, written for people who run websites and internal systems for hospitals and other organisations.<\/p>\n<h2>What a computer means by &#8220;now&#8221;<\/h2>\n<p>A server has a hardware clock that drifts a little every day, like a cheap wristwatch. A background service compares it with outside reference sources and adjusts it. Two styles of adjustment exist. Stepping jumps the clock straight to the correct value. Slewing speeds the clock up or slows it down by a tiny amount until it catches up, so time never leaps and never runs backwards.<\/p>\n<p>Programs usually assume that time moves forward in a smooth line. Stepping breaks that assumption, which is exactly where trouble begins.<\/p>\n<h2>The case that made engineers rethink the problem<\/h2>\n<p>The most quoted example in the field is the leap second added at the end of 2016, taking effect at midnight UTC on 1 January 2017. According to <a href=\"https:\/\/www.xopsschool.com\/sysops\/\">the Ops Atlas page on SysOps<\/a>, software at a large content delivery company computed a negative duration when the clock repeated a second, and the code panicked. Roughly one in 500 name lookups misbehaved, per the Atlas figure of 0.2 percent, while under 1 percent of HTTP traffic felt any effect. The Atlas quotes the root cause as a belief that time cannot go backwards.<\/p>\n<p>Look at the shape of that story. A tiny, rare event hit an assumption nobody had written down, and the visible damage was small in percentage terms but large in absolute terms because the service was enormous. The remedy the Atlas describes is a configuration choice in the time service: set its leap-second mode to slew, which spreads a roughly twelve second correction smoothly instead of replaying a second.<\/p>\n<h2>Reading the evidence: what the numbers do and do not say<\/h2>\n<p>An evidence-led reader should notice what is missing as well as what is present. The percentages above tell us the blast radius, not the number of customers. They show the failure was partial, which means many teams would have seen only a handful of odd errors and might have blamed something else. And they show the fix was a single setting, not a rewrite.<\/p>\n<p>That is a pattern worth remembering whenever someone proposes an expensive response to an outage. Ask first whether a small, explicit configuration choice would have prevented it, and whether you can demonstrate that choice is in place on every machine.<\/p>\n<h2>The settings the Atlas mentions, in everyday terms<\/h2>\n<p>The page uses chrony 4.9 as its example time service. Two lines capture the idea. One sets the leap-second mode to slew, as above. The other, written as makestep 1.0 3, allows the clock to jump only when it is off by more than one second, and only during the first three updates after the service starts. After that, adjustments are gentle.<\/p>\n<p>Think of it as a sensible rule for a ship&#8217;s navigator: at the start of a voyage you may correct the chart in one move if it is badly out, but once you are under way you only nudge the heading.<\/p>\n<ul>\n<li><strong>Start-up:<\/strong> allow a one-time jump if the clock is far off, since nothing important is running yet.<\/li>\n<li><strong>Normal running:<\/strong> prefer small, continuous corrections that programs cannot notice.<\/li>\n<li><strong>Leap seconds:<\/strong> spread them out instead of repeating a second.<\/li>\n<\/ul>\n<h2>Why time errors hide so well<\/h2>\n<p>Time faults rarely announce themselves. A job scheduled for two in the morning may run an hour early after a clock change, and the only symptom is a report that looks stale. Two servers a few seconds apart can produce log lines that tell contradictory stories about the same event, which makes incident reviews painful. Even encrypted connections can fail when one side believes a certificate is not yet valid.<\/p>\n<p>A neighbouring trap sits in scheduled work. Classic cron hands commands to a bare-bones shell, where a stray percent character is read as the end of a line, and the Atlas flags it. Timers managed by systemd can be set to run missed jobs after downtime and to add a small random delay, so you spend less time debugging schedules that silently misbehaved.<\/p>\n<p>One more habit is worth adopting: keep servers on a single zone, ideally coordinated universal time, and translate to local time only when humans read the output. Daylight saving changes create an hour that happens twice and an hour that never happens, and scheduled jobs that ignore this either double up or vanish. A plain rule such as &#8220;servers speak UTC, people see local time&#8221; removes an entire family of puzzles before they start.<\/p>\n<h2>Why audit trails depend on agreeing clocks<\/h2>\n<p>Organisations that handle sensitive records usually keep a trail of who did what and when. That trail is only as persuasive as its timestamps. If two systems disagree by a minute, reconstructing a sequence of events becomes guesswork, and an honest reviewer has to say so. Keeping every machine pointed at the same trusted references is therefore less a technical nicety than a basis for credible records.<\/p>\n<p>The same reasoning applies to monitoring. Alerts based on rates, such as errors per minute, assume that the sample windows are aligned. When clocks wander, graphs from different servers cannot be stacked on one screen without misleading anyone. A modest investment in time hygiene pays back every time someone has to explain an incident to a manager, an auditor or a customer.<\/p>\n<h2>A five-point time check for this week<\/h2>\n<ol>\n<li>List every server and note which time service it uses and where it gets its reference.<\/li>\n<li>Check the current offset on each machine and record it, so you know what &#8220;normal&#8221; looks like.<\/li>\n<li>Confirm that the leap-second handling is explicit rather than left to defaults.<\/li>\n<li>Compare timestamps across two servers for one shared event and see whether they agree.<\/li>\n<li>Write down who owns the time configuration and where it is stored.<\/li>\n<\/ol>\n<p>None of this takes long, and it builds the sort of evidence that makes future incident reviews factual rather than speculative.<\/p>\n<h2>Related reading on this site<\/h2>\n<p>Careful measurement matters in every field, and readers who like that mindset may enjoy the overview of <a href=\"https:\/\/www.hiphospitals.com\/blog\/common-causes-of-hip-pain-patients-should-understand\/\">what people commonly learn about the origins of hip discomfort<\/a>. For a lighter take on keeping complicated automated systems under control, there is also the essay titled <a href=\"https:\/\/www.hiphospitals.com\/blog\/running-smart-machines-without-losing-your-mind\/\">running intelligent machines without losing your composure<\/a>. Both are general information and not advice for any individual.<\/p>\n<h2>What SysOps teams should take away<\/h2>\n<p>Time is a shared dependency, and shared dependencies deserve explicit settings, recorded values and a periodic look. The 2017 leap-second episode did not happen because engineers were careless; it happened because a quiet assumption met a rare event. SysOps is largely the habit of finding such assumptions before they find you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Server time looks dull until it breaks. This explainer walks through stepping, slewing and one famous leap-second failure, with a short audit you can run.<\/p>\n","protected":false},"author":12,"featured_media":3245,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1794],"tags":[],"class_list":["post-3244","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hospital-it"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care<\/title>\n<meta name=\"description\" content=\"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.\" \/>\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.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care\" \/>\n<meta property=\"og:description\" content=\"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/\" \/>\n<meta property=\"og:site_name\" content=\"HipHospitals \u2013 Your Gateway to Hip Surgery Care\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-16T18:05:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-19T12:05:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-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=\"Ritika Kapoor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ritika Kapoor\" \/>\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.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/\"},\"author\":{\"name\":\"Ritika Kapoor\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/062e9f54e9e574b4829e930690423097\"},\"headline\":\"Why Server Clocks Matter: A Plain-Language SysOps Explainer\",\"datePublished\":\"2026-11-16T18:05:00+00:00\",\"dateModified\":\"2026-11-19T12:05:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/\"},\"wordCount\":1197,\"image\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-739037-banner.png\",\"articleSection\":[\"Hospital IT\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/\",\"url\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/\",\"name\":\"Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-739037-banner.png\",\"datePublished\":\"2026-11-16T18:05:00+00:00\",\"dateModified\":\"2026-11-19T12:05:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/062e9f54e9e574b4829e930690423097\"},\"description\":\"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-739037-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-739037-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/sysops-clocks-explained-evidence\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why Server Clocks Matter: A Plain-Language SysOps Explainer\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/\",\"name\":\"My blog\",\"description\":\"Discover the Best Hospitals, Surgeons &amp; Innovations in Hip Replacement &amp; Joint Care Worldwide\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/#\\\/schema\\\/person\\\/062e9f54e9e574b4829e930690423097\",\"name\":\"Ritika Kapoor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g\",\"caption\":\"Ritika Kapoor\"},\"url\":\"https:\\\/\\\/www.hiphospitals.com\\\/blog\\\/author\\\/ritika-kapoor\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care","description":"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.","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.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/","og_locale":"en_US","og_type":"article","og_title":"Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care","og_description":"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.","og_url":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/","og_site_name":"HipHospitals \u2013 Your Gateway to Hip Surgery Care","article_published_time":"2026-11-16T18:05:00+00:00","article_modified_time":"2026-11-19T12:05:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-banner.png","type":"image\/png"}],"author":"Ritika Kapoor","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ritika Kapoor","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#article","isPartOf":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/"},"author":{"name":"Ritika Kapoor","@id":"https:\/\/www.hiphospitals.com\/blog\/#\/schema\/person\/062e9f54e9e574b4829e930690423097"},"headline":"Why Server Clocks Matter: A Plain-Language SysOps Explainer","datePublished":"2026-11-16T18:05:00+00:00","dateModified":"2026-11-19T12:05:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/"},"wordCount":1197,"image":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#primaryimage"},"thumbnailUrl":"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-banner.png","articleSection":["Hospital IT"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/","url":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/","name":"Why Server Clocks Matter: A Plain-Language SysOps Explainer - HipHospitals \u2013 Your Gateway to Hip Surgery Care","isPartOf":{"@id":"https:\/\/www.hiphospitals.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#primaryimage"},"image":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#primaryimage"},"thumbnailUrl":"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-banner.png","datePublished":"2026-11-16T18:05:00+00:00","dateModified":"2026-11-19T12:05:00+00:00","author":{"@id":"https:\/\/www.hiphospitals.com\/blog\/#\/schema\/person\/062e9f54e9e574b4829e930690423097"},"description":"Understand why server clocks matter in SysOps: stepping versus slewing, a leap-second failure, safe time settings and a five-point audit.","breadcrumb":{"@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#primaryimage","url":"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-banner.png","contentUrl":"https:\/\/www.hiphospitals.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-739037-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.hiphospitals.com\/blog\/sysops-clocks-explained-evidence\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.hiphospitals.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Why Server Clocks Matter: A Plain-Language SysOps Explainer"}]},{"@type":"WebSite","@id":"https:\/\/www.hiphospitals.com\/blog\/#website","url":"https:\/\/www.hiphospitals.com\/blog\/","name":"My blog","description":"Discover the Best Hospitals, Surgeons &amp; Innovations in Hip Replacement &amp; Joint Care Worldwide","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.hiphospitals.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.hiphospitals.com\/blog\/#\/schema\/person\/062e9f54e9e574b4829e930690423097","name":"Ritika Kapoor","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f129cf3def755c5f324eb8e54b40daf092d4ecd9ab134a581ccbaa897dcc06c8?s=96&d=mm&r=g","caption":"Ritika Kapoor"},"url":"https:\/\/www.hiphospitals.com\/blog\/author\/ritika-kapoor\/"}]}},"_links":{"self":[{"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3244","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/comments?post=3244"}],"version-history":[{"count":1,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3244\/revisions"}],"predecessor-version":[{"id":3364,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/posts\/3244\/revisions\/3364"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/media\/3245"}],"wp:attachment":[{"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/media?parent=3244"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/categories?post=3244"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hiphospitals.com\/blog\/wp-json\/wp\/v2\/tags?post=3244"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}