{"id":14522,"date":"2025-06-23T13:47:26","date_gmt":"2025-06-23T13:47:26","guid":{"rendered":"https:\/\/codeaura.ai\/?p=14522"},"modified":"2025-06-23T13:47:43","modified_gmt":"2025-06-23T13:47:43","slug":"compliance-deadlines-are-coming-is-your-legacy-system-ready-for-fednow-or-hipaa-stage-3","status":"publish","type":"post","link":"https:\/\/codeaura.ai\/fr\/compliance-deadlines-are-coming-is-your-legacy-system-ready-for-fednow-or-hipaa-stage-3\/","title":{"rendered":"Compliance Deadlines Are Coming\u2014Is Your Legacy System Ready for FedNow or HIPAA Stage 3?"},"content":{"rendered":"<div data-elementor-type=\"wp-post\" data-elementor-id=\"14522\" class=\"elementor elementor-14522\">\n\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-22169526 e-flex e-con-boxed e-con e-parent\" data-id=\"22169526\" data-element_type=\"container\" data-settings=\"{&quot;content_width&quot;:&quot;boxed&quot;}\" data-core-v316-plus=\"true\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-468c61de elementor-widget elementor-widget-text-editor\" data-id=\"468c61de\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.17.0 - 08-11-2023 *\/\n.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}<\/style>\t\t\t\t<h4>The Compliance Clock Is Ticking<\/h4><p>Regulatory deadlines used to be distant events\u2014something to plan for \u201cnext fiscal year.\u201d But in 2025, mandates like FedNow adoption and HIPAA Stage 3 compliance are landing fast and hard. And for organizations still running mission-critical operations on legacy systems, the clock isn\u2019t just ticking\u2014it\u2019s sounding the alarm.<\/p><p>These mandates aren\u2019t theoretical. They require:<\/p><ul><li>Real-time payment capabilities (FedNow)<\/li><li>Granular patient data access and exchange (HIPAA Stage 3)<\/li><li>Full audit trails, traceable logic, and system-level transparency<\/li><\/ul><p>Legacy systems, especially those built decades ago in COBOL or PL\/I, were never designed for this. They were built for batch processing, siloed storage, and closed networks\u2014not real-time APIs, interoperability, or dynamic compliance reporting.<\/p><p>As a result, many banks and healthcare providers are now facing a stark choice:<\/p><ul><li>Modernize in time to meet the mandate<\/li><li>Or risk penalties, reputational damage, and systemic outages<\/li><\/ul><p>Regulators are no longer willing to accept \u201clegacy limitations\u201d as an excuse. The expectation is clear: if the law requires it, your tech must deliver it.<\/p><h4>Legacy Infrastructure and the Risk of Noncompliance<\/h4><p>Legacy systems were built for a different era\u2014one where nightly batch jobs, paper trails, and manual oversight were the norm. But modern regulations demand speed, transparency, and traceability that these systems simply weren\u2019t designed to deliver.<\/p><p>The risks of noncompliance in this environment are significant\u2014and growing:<\/p><ol><li>Inability to Meet Real-Time Processing Requirements: FedNow, the U.S. government\u2019s instant payment infrastructure, requires systems that can process, clear, and settle transactions in real time. Legacy COBOL systems that depend on nightly batches or mainframe job schedulers can\u2019t adapt without major architectural changes.<\/li><li>Lack of Interoperability: HIPAA Stage 3 mandates greater data sharing across providers, payers, and patients. Systems that store data in proprietary formats or lack modern integration interfaces can\u2019t support required data exchange\u2014even if the information exists internally.<\/li><li>Audit and Traceability Gaps: Regulators now demand clear, traceable documentation of how systems make decisions\u2014whether it\u2019s how a claim was adjudicated or how a transaction was prioritized. Legacy code often lacks documentation, and changes made over the years are rarely versioned or traceable to source.<\/li><li>Security Exposure: Aging systems often lack encryption, access controls, or update mechanisms needed to meet today\u2019s cybersecurity standards. This exposes institutions to breaches that can trigger regulatory investigations and fines.<\/li><li>Human Bottlenecks: Many compliance processes still rely on a shrinking pool of experts who understand the legacy logic. When those experts retire\u2014or are unavailable during an audit\u2014the organization is effectively blind.<\/li><\/ol><p>Noncompliance isn\u2019t just a technical issue. It becomes a legal, financial, and reputational crisis when regulators come knocking and the system can\u2019t answer.<\/p><h4>FedNow, HIPAA Stage 3, and Beyond: What\u2019s Changing?<\/h4><p>Modern compliance mandates aren\u2019t just incremental upgrades\u2014they represent a fundamental shift in how financial and healthcare systems are expected to operate.<\/p><p>Let\u2019s break down what\u2019s driving urgency in 2025:<\/p><p><strong>FedNow (U.S. Federal Reserve) \u2013 Real-Time Payments Infrastructure<\/strong><\/p><p>Launched to modernize the U.S. banking system, FedNow requires that participating institutions:<\/p><ul><li>Support 24\/7\/365 real-time clearing and settlement<\/li><li>Maintain instant transaction visibility for customers and regulators<\/li><li>Integrate with modern APIs for secure and traceable payment processing<\/li><\/ul><p>Legacy banking systems built around COBOL and batch windows struggle with this model. Without refactoring core transaction systems or building composable front-ends, they risk falling out of compliance or being unable to support critical services.<\/p><p><strong>HIPAA Stage 3 \u2013 Enhanced Interoperability and Patient Access<\/strong><\/p><p>Under the HITECH and 21st Century Cures Act umbrella, HIPAA Stage 3 mandates:<\/p><ul><li>Real-time patient access to medical records<\/li><li>Standards-based data sharing via FHIR APIs<\/li><li>Transparent decision logic for clinical and billing systems<\/li><li>Enhanced security and auditability<\/li><\/ul><p>This pushes legacy EHRs, claims engines, and billing systems beyond their original capabilities. Hard-coded rules and undocumented workflows must now be exposed, traced, and secured\u2014something nearly impossible without extensive reverse engineering or AI support.<\/p><p><strong>Emerging Global Standards (ISO 20022, GDPR+, etc.)<\/strong><\/p><p>Beyond FedNow and HIPAA, global banks and health systems must also contend with:<\/p><ul><li>ISO 20022 for richer, structured payment data<\/li><li>GDPR and state-level privacy laws with real-time access and deletion requirements<\/li><li>SEC and OCC rules mandating complete explainability for AI-assisted decisions<\/li><\/ul><p>The direction is clear: regulators now assume systems are real-time, API-ready, and fully auditable. If your legacy stack can\u2019t meet that bar, it\u2019s not just outdated\u2014it\u2019s out of spec.<\/p><h4>Where Legacy Systems Fall Short<\/h4><p>Legacy systems weren\u2019t built for today\u2019s compliance environment\u2014and their limitations show up across every dimension that modern regulators now care about. Here\u2019s where they most often fall short:<\/p><p><strong>1. No Real-Time Capability<\/strong><\/p><p>Legacy banking and healthcare platforms were designed around batch processing\u2014running jobs overnight or during downtime windows. They simply can\u2019t handle the always-on, milliseconds-matter expectations of FedNow or modern patient portals.<\/p><p><strong>2. Siloed, Non-Interoperable Data<\/strong><\/p><p>Data in legacy systems is often:<\/p><ul><li>Stored in proprietary formats (VSAM, flat files)<\/li><li>Locked in application-specific logic<\/li><li>Tied to mainframe or local storage<\/li><\/ul><p>This makes FHIR compliance in healthcare or ISO 20022 in finance incredibly difficult without costly extraction and transformation.<\/p><p><strong>3. Lack of Explainability<\/strong><\/p><p>In regulated environments, it\u2019s no longer enough to get the right answer\u2014the system must show its work. Legacy COBOL code often has:<\/p><ul><li>No documentation<\/li><li>No visible logic flow<\/li><li>No audit trail connecting code to policy or regulation<\/li><\/ul><p>This breaks traceability requirements in HIPAA Stage 3, SOX, or OCC audits.<\/p><p><strong>4. Security and Access Control Gaps<\/strong><\/p><p>Older systems often lack modern authentication, encryption-at-rest, role-based access, or logging. These are non-negotiable in today\u2019s compliance landscape\u2014and are often flagged during audits.<\/p><p><strong>5. SME Dependency and Fragile Change Cycles<\/strong><\/p><p>When only one or two engineers understand how a core process works, every change becomes a risk. Without automated testing or impact analysis, compliance updates can break unrelated functionality, creating ripple effects that increase exposure.<\/p><p>In short, these systems weren\u2019t built to be agile, transparent, or interoperable. And now, compliance requires all three.<\/p><h4>Modernization Isn\u2019t Optional\u2014It\u2019s a Compliance Requirement<\/h4><p>For years, modernization was positioned as a \u201cnice to have\u201d\u2014a way to boost agility, reduce costs, or attract talent. But today, regulators are making it clear: if your legacy system can\u2019t meet mandated standards, it\u2019s out of compliance. Full stop.<\/p><p>This shift reframes modernization as a regulatory imperative, not just a technical upgrade.<\/p><p><strong>1. Regulators Expect Operational Readiness<\/strong><\/p><p>Whether it\u2019s FedNow in banking or HIPAA Stage 3 in healthcare, compliance now demands:<\/p><ul><li>Real-time capabilities<\/li><li>Interoperable APIs<\/li><li>Complete audit trails<\/li><li>Explainable system behavior<\/li><\/ul><p>If your system can\u2019t deliver, it\u2019s not \u201clegacy\u201d\u2014it\u2019s noncompliant.<\/p><p><strong>2. Technical Debt Is Now Regulatory Risk<\/strong><\/p><p>What used to be internal complexity is now external exposure. That undocumented COBOL routine? If it drives patient billing logic or transaction approvals, regulators want to see it\u2014and understand it.<\/p><p><strong>3. Exceptions and Grace Periods Are Shrinking<\/strong><\/p><p>In the past, some industries received temporary exceptions due to system limitations. That leniency is fading fast. Regulators now expect proactive roadmaps, risk mitigation plans, and documented modernization strategies.<\/p><p><strong>4. Audits Are Getting Smarter<\/strong><\/p><p>Auditors are no longer satisfied with box-checking. They\u2019re asking to see:<\/p><ul><li>Versioned logic<\/li><li>Code provenance<\/li><li>Decision path traceability<\/li><li>Access logs and modification history<\/li><\/ul><p>Legacy systems that lack this visibility are flagged for manual remediation or future phase-out.<\/p><p><strong>5. The Cost of Noncompliance Is Rising<\/strong><\/p><p>Penalties range from monetary fines to lost accreditation, halted transactions, or legal action. And the reputational cost of a public compliance failure\u2014especially one traced back to an aging system\u2014is difficult to recover from.<\/p><h4>Using AI to Accelerate Regulatory Readiness<\/h4><p>Legacy compliance gaps are fundamentally knowledge gaps\u2014about what systems do, how they interact, and where risk hides. AI is closing those gaps, fast.<\/p><p>Platforms like Elliot are transforming how regulated institutions approach legacy modernization\u2014not by rewriting everything, but by making the invisible visible, explainable, and auditable.<\/p><p>Here\u2019s how AI helps teams get\u2014and stay\u2014ready for compliance:<\/p><p><strong>1. Code Comprehension at Scale<\/strong><\/p><p>Elliot can analyze millions of lines of legacy code (COBOL, JCL, PL\/I, etc.) and produce:<\/p><ul><li>Plain-language summaries of business logic<\/li><li>Dependency maps showing system-wide impact<\/li><li>Data lineage for sensitive fields (e.g., patient ID, account balance)<\/li><\/ul><p>This reduces the time to understand systems from months to days.<\/p><p><strong>2. Documentation Where None Exists<\/strong><\/p><p>AI generates traceable, structured documentation from raw code\u2014filling in the gaps left by years (or decades) of unrecorded changes. This is essential for HIPAA audit trails, SOX compliance, and FedNow integration reviews.<\/p><p><strong>3. Real-Time Impact Analysis<\/strong><\/p><p>Need to change a rule to meet a new regulation? AI shows what will break, what depends on that rule, and where in the system the logic flows. This allows teams to make compliance-driven changes safely.<\/p><p><strong>4. SME Bandwidth Expansion<\/strong><\/p><p>With AI answering first-line technical and functional questions, subject matter experts can focus on validating high-risk areas\u2014not re-explaining core logic. This is critical as veteran SMEs retire and talent gaps widen.<\/p><p><strong>5. Proactive Compliance Mapping<\/strong><\/p><p>Elliot can tag code with relevant regulatory domains (e.g., \u201cFedNow SLA logic,\u201d \u201cHIPAA Protected Field,\u201d \u201cSOX-relevant calculation\u201d), making it easy to align modernization tasks with audit requirements.<\/p><h4>The Cost of Delay vs. the ROI of Modernization<\/h4><p>When compliance deadlines loom, delay is rarely neutral\u2014it\u2019s expensive. Whether it\u2019s reactive scrambling, regulatory penalties, or missed business opportunities, waiting to modernize your legacy systems comes with tangible costs.<\/p><p><strong>The Cost of Delay<\/strong><\/p><ul><li>Regulatory Penalties: Noncompliance with HIPAA, FedNow, or GDPR can result in fines ranging from thousands to millions of dollars per incident. And in sectors like healthcare and banking, regulatory reputational damage can lead to customer attrition and market devaluation.<\/li><li>Last-Minute Firefighting: Scrambling to meet compliance deadlines without a clear roadmap increases consultant fees, consumes SME bandwidth, and often requires duplicated work under audit pressure.<\/li><li>Inflexible Systems: Every quarter spent maintaining unmodernized systems limits your ability to adapt. You\u2019re stuck in reactive mode, while more agile competitors roll out new services, integrations, and analytics.<\/li><li>Lost Talent and Institutional Memory: As SMEs retire or leave, undocumented systems become even harder to modernize. Delay increases your reliance on vanishing expertise.<\/li><\/ul><p><strong>The ROI of Modernization<\/strong><\/p><ul><li>Reduced Risk Exposure: Documented, explainable systems reduce audit flags, speed up incident response, and ensure you pass compliance reviews without drama.<\/li><li>Faster Time to Implement Mandates: With AI-assisted understanding and clear architecture, you can update rules, processes, or logic in days\u2014not months.<\/li><li>Improved Developer Productivity: Engineers spend less time reverse-engineering legacy code and more time delivering value\u2014translating to lower maintenance costs and faster feature delivery.<\/li><li>Strategic Agility: Composable architectures and API-wrapped legacy systems enable faster integration with fintech, healthtech, and cloud platforms\u2014turning compliance from a constraint into a competitive advantage.<\/li><\/ul><p>In short: the longer you wait, the more you\u2019ll pay\u2014for less control, more risk, and diminishing talent.<\/p><h4>Compliance as Catalyst, Not Constraint<\/h4><p>Compliance often gets framed as a burden\u2014a box to check, a deadline to dread. But in today\u2019s environment, it can be something far more powerful: a forcing function for change.<\/p><p>The mandates driving urgency\u2014FedNow, HIPAA Stage 3, ISO 20022\u2014aren\u2019t just about rules. They\u2019re about readiness. They push organizations to confront uncomfortable truths about legacy systems that no longer meet the speed, transparency, or interoperability the world now expects.<\/p><p>But that pressure can be productive.<\/p><p>It\u2019s a chance to:<\/p><ul><li>Document institutional logic before it\u2019s lost<\/li><li>Expose and reduce systemic risk embedded in aging code<\/li><li>Equip your teams with tools to understand, change, and govern legacy systems<\/li><li>Accelerate digital transformation with compliance as the business case<\/li><\/ul><p>Modernization, in this light, isn\u2019t a technical project\u2014it\u2019s a compliance readiness program that delivers both risk reduction and operational agility.<\/p><p>\u00a0<\/p><p><strong>Let\u2019s Talk About Your COBOL Documentation and Modernization Needs<\/strong>\u00a0\u2014 <a href=\"https:\/\/calendly.com\/suyash-codeaura\/30min\" target=\"_blank\" rel=\"noopener\">Schedule a session with CodeAura today<\/a>.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>FedNow and HIPAA Stage 3 are here\u2014legacy systems aren\u2019t ready. Learn how to modernize for compliance and reduce risk using AI and strategic planning.<\/p>","protected":false},"author":1,"featured_media":14530,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mo_disable_npp":"","footnotes":""},"categories":[61],"tags":[60],"class_list":["post-14522","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general","tag-general","entry"],"rttpg_featured_image_url":{"full":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"landscape":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"portraits":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"thumbnail":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-150x150.jpg",150,150,true],"medium":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-300x200.jpg",300,200,true],"large":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-1024x683.jpg",1024,683,true],"1536x1536":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"2048x2048":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"trp-custom-language-flag":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-18x12.jpg",18,12,true],"post-thumbnail":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3.jpg",1200,800,false],"martex-360x234-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-360x234.jpg",360,234,true],"martex-390x300-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-390x300.jpg",390,300,true],"martex-400x400-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-400x400.jpg",400,400,true],"martex-450x350-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-450x350.jpg",450,350,true],"martex-750x320-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-750x320.jpg",750,320,true],"martex-700x500-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-700x500.jpg",700,500,true],"martex-1000x600-cropped":["https:\/\/codeaura.ai\/wp-content\/uploads\/2025\/06\/Compliance-Deadlines-Are-Coming\u2014Is-Your-Legacy-System-Ready-for-FedNow-or-HIPAA-Stage-3-1000x600.jpg",1000,600,true]},"rttpg_author":{"display_name":"suyash@codevigor.com","author_link":"https:\/\/codeaura.ai\/fr\/author\/suyashcodevigor-com\/"},"rttpg_comment":0,"rttpg_category":"<a href=\"https:\/\/codeaura.ai\/fr\/category\/general\/\" rel=\"category tag\">General<\/a>","rttpg_excerpt":"FedNow and HIPAA Stage 3 are here\u2014legacy systems aren\u2019t ready. Learn how to modernize for compliance and reduce risk using AI and strategic planning.","_links":{"self":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14522","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/comments?post=14522"}],"version-history":[{"count":7,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14522\/revisions"}],"predecessor-version":[{"id":14529,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/posts\/14522\/revisions\/14529"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/media\/14530"}],"wp:attachment":[{"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/media?parent=14522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/categories?post=14522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeaura.ai\/fr\/wp-json\/wp\/v2\/tags?post=14522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}