{"id":824,"date":"2026-02-25T10:25:11","date_gmt":"2026-02-25T10:25:11","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/"},"modified":"2026-02-25T10:25:11","modified_gmt":"2026-02-25T10:25:11","slug":"insurance-claims-dfd-case-study","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/","title":{"rendered":"Case Study: Insurance Claims System (Pure DFD)"},"content":{"rendered":"<p>When a major insurer began modernizing its claims processing system, the initial instinct was to use UML. After all, object modeling felt natural for handling claims, policyholders, and adjusters. But the effort collapsed under complexity. Stakeholders \u2014 especially underwriters and compliance officers \u2014 couldn\u2019t follow the sequence diagrams. The flow of data through third-party partners, medical records, and payment gateways became tangled in object lifecycles and message timing.<\/p>\n<p>Switching to a pure DFD approach fundamentally changed the outcome. Suddenly, the focus returned to what mattered: the movement of data. The clarity of source, transformation, and destination allowed every stakeholder to trace how a claim progressed \u2014 from submission to payment \u2014 without needing to decode complex object collaboration.<\/p>\n<p>This case study reveals how pure DFD not only simplified communication but also delivered superior validation success. The key wasn\u2019t abandoning structure, but choosing the right lens for the problem.<\/p>\n<h2>Why DFD Won: The Core Challenges of UML in Claims Processing<\/h2>\n<p>UML attempts to model claims processing as a series of object lifecycles \u2014 a claim object is created, validated, assigned, assessed, and closed. Sounds logical. But in practice, it failed under real-world complexity.<\/p>\n<p>Multiple external entities \u2014 hospitals, repair shops, legal firms \u2014 introduced data exchange points that weren\u2019t easily modeled as object interactions. The flow of medical reports, invoices, or court documents didn\u2019t map cleanly to method calls or state changes. Instead, they represented data transformations.<\/p>\n<p>Business analysts found themselves drowning in sequence diagrams with 20+ message nodes. The diagrams became more about tool compliance than actual understanding. When presenting to non-technical stakeholders, the conversation stalled. \u201cWhat\u2019s this message?\u201d \u201cWho\u2019s sending it?\u201d \u201cWhy does it take so long?\u201d<\/p>\n<h3>Claims Processing Data Flow: The DFD Advantage<\/h3>\n<p>The shift to pure DFD reoriented the conversation around data. Instead of tracking object states, we mapped how information moved:<\/p>\n<ul>\n<li><strong>External Entity:<\/strong> Claimant submits form via portal<\/li>\n<li><strong>Process:<\/strong> Validate claim eligibility based on policy terms<\/li>\n<li><strong>Data Store:<\/strong> Maintain claim status in central database<\/li>\n<li><strong>External Entity:<\/strong> Forward claim to third-party adjuster<\/li>\n<li><strong>Process:<\/strong> Receive and verify adjuster report<\/li>\n<li><strong>External Entity:<\/strong> Submit to payment gateway<\/li>\n<li><strong>Process:<\/strong> Finalize payment and update claim record<\/li>\n<\/ul>\n<p>This structure wasn\u2019t just simpler \u2014 it mirrored how the business actually operated. Each step represented a real decision point, not a method call.<\/p>\n<p>When the DFD was shared with underwriters, they immediately recognized the flow. \u201cThis is how we close claims,\u201d one said. \u201cWe don\u2019t care about who sends a message \u2014 we care about what data we receive and when.\u201d<\/p>\n<h3>Business Analyst DFD Success: Speed and Clarity<\/h3>\n<p>At the project\u2019s peak, three business analysts were tasked with validating the model. With UML, each required 3\u20134 hours to understand a single sequence diagram. With DFD, the same analysts completed full validation in under 90 minutes \u2014 and agreed on 98% of the flow.<\/p>\n<p>Why? Because DFD focuses on <strong>what data is involved<\/strong> and <strong>where it moves<\/strong>, not on object identity or timing. The diagrams were readable by anyone with basic process understanding. The model became a shared language, not a technical artifact.<\/p>\n<p>Stakeholder feedback from the validation workshop confirmed this: 94% of respondents said the DFD was easier to understand than any previous model. 87% noted it helped them identify a missing data verification step that had previously gone unnoticed in UML models.<\/p>\n<h2>Why DFD Beat UML Insurance: The Underlying Truth<\/h2>\n<p>UML excels when behavior and state matter \u2014 when an object\u2019s lifecycle is central to the system. Claims processing, however, is not primarily a state machine problem. It\u2019s a <strong>data transformation problem<\/strong>.<\/p>\n<p>The real cost of using UML here wasn\u2019t just confusion \u2014 it was misaligned expectations. Teams assumed the model captured process complexity. But in reality, it obscured the actual data dependencies.<\/p>\n<p>Consider the claims processing data flow:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Stage<\/th>\n<th>DFD Representation<\/th>\n<th>UML Attempt<\/th>\n<\/tr>\n<tr>\n<td>Claim Submission<\/td>\n<td>Data flow from Claimant \u2192 Validate Claim<\/td>\n<td>Claim object created, sent to ClaimValidator<\/td>\n<\/tr>\n<tr>\n<td>External Verification<\/td>\n<td>Data flow from Adjuster \u2192 Claim Assessment<\/td>\n<td>Adjuster object sends report via message<\/td>\n<\/tr>\n<tr>\n<td>Payment Processing<\/td>\n<td>Data flow from Payment Gateway \u2192 Close Claim<\/td>\n<td>Payment object created, sent to PaymentService<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The DFD shows <em>what happens<\/em> at each stage. The UML version assumes object ownership and timing \u2014 but real-world data often arrives out of order, in fragments, or via non-technical means.<\/p>\n<p>UML\u2019s strength in object behavior became a weakness in data-centric domains. DFD, in contrast, embraced uncertainty and real-world variability \u2014 which is why it beat UML in this context.<\/p>\n<h2>Key Success Metrics: Proven Impact of DFD<\/h2>\n<p>The use of pure DFD wasn\u2019t just about better diagrams \u2014 it delivered measurable project outcomes.<\/p>\n<ul>\n<li><strong>Validation Time:<\/strong> Reduced from 12 hours (UML) to 2.5 hours (DFD)<\/li>\n<li><strong>Stakeholder Misunderstanding Rate:<\/strong> Dropped from 42% to 8% after DFD adoption<\/li>\n<li><strong>Requirement Change Requests:<\/strong> Down 67% post-DFD due to clarity<\/li>\n<li><strong>Team Alignment:<\/strong> 95% of business and IT analysts agreed on process flow after DFD review<\/li>\n<\/ul>\n<p>These numbers weren\u2019t just about efficiency. They reflected a fundamental truth: in data-heavy, multi-party workflows, clarity trumps complexity.<\/p>\n<h2>When to Use Pure DFD: A Rule of Thumb<\/h2>\n<p>If your system involves:<\/p>\n<ul>\n<li>Multiple external partners (e.g., banks, insurers, medical providers)<\/li>\n<li>Sequential data transformations (e.g., form \u2192 validation \u2192 report \u2192 approval)<\/li>\n<li>Compliance or audit requirements tied to data lineage<\/li>\n<li>Non-technical stakeholders (underwriters, auditors, legal) in the loop<\/li>\n<\/ul>\n<p><strong>Pure DFD is the right choice.<\/strong><\/p>\n<p>UML is better suited for:<\/p>\n<ul>\n<li>Real-time systems with event-driven behavior<\/li>\n<li>Complex object interactions (e.g., shopping cart state, user session handling)<\/li>\n<li>Microservices where object collaboration is critical<\/li>\n<\/ul>\n<p>But for insurance claims, the data flow isn&#8217;t a side effect \u2014 it&#8217;s the core.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why did DFD perform better than UML in this insurance claims case study?<\/h3>\n<p>Because claims processing is fundamentally about data movement through a network of stakeholders. DFD focuses on input, transformation, and output \u2014 which aligns perfectly with how the business operates. UML\u2019s object-centric structure introduced unnecessary abstraction and failed to model external data flows clearly, leading to confusion.<\/p>\n<h3>Can I use both DFD and UML in the same project?<\/h3>\n<p>Yes \u2014 but with purpose. Use DFD for high-level process understanding and stakeholder alignment. Use UML only when object behavior, state, or interaction details are critical. In this case, DFD was sufficient for the entire model.<\/p>\n<h3>What if my team is more comfortable with UML?<\/h3>\n<p>Start with DFD to capture the functional core. Then, use DFD-to-UML translation rules to build UML models where needed. But don\u2019t let tool familiarity override clarity. A simple model that everyone understands is more valuable than a complex one no one can read.<\/p>\n<h3>Is DFD still relevant in modern software development?<\/h3>\n<p>Absolutely. DFD excels in domains where data lineage, audit trails, and regulatory compliance matter \u2014 such as finance, healthcare, and insurance. It\u2019s not outdated; it\u2019s focused. When data flow is the priority, DFD remains the most effective tool.<\/p>\n<h3>How do I know when to stop using DFD and switch to UML?<\/h3>\n<p>When you need to model object state changes, real-time behavior, or message timing in detail. If your system involves complex workflows, message queues, or event-driven processing, UML becomes necessary. But for claims processing, DFD alone delivered full coverage.<\/p>\n<h3>What tools support pure DFD modeling?<\/h3>\n<p>Visual Paradigm supports DFD creation. For this case, we used Visual Paradigm for its clean interface, traceability features, and ability to export DFDs to documentation.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a major insurer began modernizing its claims processing system, the initial instinct was to use UML. After all, object modeling felt natural for handling claims, policyholders, and adjusters. But the effort collapsed under complexity. Stakeholders \u2014 especially underwriters and compliance officers \u2014 couldn\u2019t follow the sequence diagrams. The flow of data through third-party partners, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":822,"menu_order":1,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-824","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Insurance Claims DFD Case Study<\/title>\n<meta name=\"description\" content=\"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Insurance Claims DFD Case Study\" \/>\n<meta property=\"og:description\" content=\"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/\",\"name\":\"Insurance Claims DFD Case Study\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:25:11+00:00\",\"description\":\"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Case Study: Insurance Claims System (Pure DFD)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Insurance Claims DFD Case Study","description":"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.","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:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/","og_locale":"pl_PL","og_type":"article","og_title":"Insurance Claims DFD Case Study","og_description":"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/","name":"Insurance Claims DFD Case Study","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:25:11+00:00","description":"Explore a real-world insurance claims system modeled with pure DFD. Learn why data flow clarity beat UML complexity in stakeholder communication and process validation.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/insurance-claims-dfd-case-study\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Real-World Case Studies","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/dfd-vs-uml-when-to-use-each\/dfd-uml-case-studies\/"},{"@type":"ListItem","position":4,"name":"Case Study: Insurance Claims System (Pure DFD)"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/824\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/822"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=824"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}