{"id":807,"date":"2026-02-25T10:25:03","date_gmt":"2026-02-25T10:25:03","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/"},"modified":"2026-02-25T10:25:03","modified_gmt":"2026-02-25T10:25:03","slug":"healthcare-dfd-vs-uml","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/","title":{"rendered":"Healthcare: DFDs for Patient Data Flows, UML for Clinical Workflows"},"content":{"rendered":"<p>In a private clinic in Portland, a team spent three weeks debating the best way to model a patient\u2019s journey from registration to discharge. They tried UML sequence diagrams first\u2014only to realize they couldn\u2019t capture the full audit trail required by HIPAA. Then they switched to DFDs. The clarity was immediate. Patient data flows became visible across departments, even when roles or systems changed.<\/p>\n<p>That\u2019s the power of choosing the right notation for the right context. In healthcare, data is both a clinical asset and a regulatory liability. DFDs reveal exactly how patient data moves\u2014critical for HIPAA compliance. UML, on the other hand, models the actual clinical decisions, care coordination, and patient state changes that define real-world care.<\/p>\n<p>This chapter shows how to use both\u2014strategically, cohesively, and with purpose. You\u2019ll learn how to map patient data flow with DFDs while modeling clinical workflows with UML. You\u2019ll see real-world examples of how this dual-notation strategy reduces ambiguity, improves audit readiness, and supports interoperability across electronic health record (EHR) systems.<\/p>\n<p>By the end, you\u2019ll know not just which tool to use, but how to use both in concert\u2014ensuring compliance without sacrificing clinical fidelity.<\/p>\n<h2>Why Healthcare Needs Two Models, Not One<\/h2>\n<p>Healthcare systems are not just about transactions. They\u2019re about people, care paths, and compliance. A single patient record contains both data (demographics, vitals, diagnosis codes) and behavior (clinical decisions, treatment sequences, transitions of care).<\/p>\n<p>DFD modeling focuses on the <strong>what flows<\/strong> and <strong>where it goes<\/strong>. It answers: How does a patient\u2019s lab result move from the lab to the physician\u2019s dashboard? Who accesses it? When is it logged? This is essential for <em>patient data flow HIPAA<\/em> compliance, where data lineage is legally required for audits.<\/p>\n<p>UML modeling focuses on <strong>who does what<\/strong> and <strong>when<\/strong>. It answers: How does the physician evaluate the result? What triggers a follow-up? What state is the patient in\u2014stable, deteriorating, critical? This is essential for <em>clinical workflow UML modeling<\/em>, especially in scenarios like sepsis protocols or post-op monitoring.<\/p>\n<p>Using both creates a complete picture: data movement and clinical decision-making are aligned, not siloed.<\/p>\n<h3>Real-World Example: Sepsis Alert Workflow<\/h3>\n<p>Consider a sepsis screening protocol. The same patient data\u2014temperature, WBC, lactate level\u2014must trigger both a system alert and a clinical response. A DFD shows the data flow: lab \u2192 EHR \u2192 alert engine \u2192 clinician dashboard. A UML sequence diagram shows the clinical workflow: nurse measures vitals \u2192 system flags high-risk values \u2192 physician reviews \u2192 orders antibiotics.<\/p>\n<p>Both are true. Both are necessary. But only together do they reflect the full operational reality.<\/p>\n<h2>Mapping Data Flow to Clinical State: A Dual-Notation Strategy<\/h2>\n<p>When modeling healthcare systems, the goal is not to choose between DFD and UML\u2014but to use them in sequence, with clear mapping rules. This is the <strong>healthcare dual notation strategy<\/strong>.<\/p>\n<p>The key is to treat DFDs as the <em>foundation<\/em> and UML as the <em>extension<\/em>. DFDs define the &#8220;what&#8221; and &#8220;where.&#8221; UML defines the &#8220;who&#8221; and &#8220;how.&#8221;<\/p>\n<h3>Step-by-Step Mapping Rules<\/h3>\n<ol>\n<li><strong>DFD Process \u2192 UML Use Case<\/strong><br \/>\n      A process like \u201cCalculate Risk Score\u201d maps to a use case \u201cGenerate Sepsis Risk Assessment\u201d in UML.<\/li>\n<li><strong>DFD Data Store \u2192 UML Class<\/strong><br \/>\n      \u201cPatient Medical Record\u201d (data store) becomes the \u201cPatient\u201d class in UML, with attributes like \u201cvitals,\u201d \u201cdiagnoses,\u201d \u201ccurrentStatus.\u201d<\/li>\n<li><strong>DFD Data Flow \u2192 UML Message or Attribute<\/strong><br \/>\n      The flow \u201cLab Results \u2192 Physician\u201d becomes a message: \u201csend(labResult)\u201d in a sequence diagram.<\/li>\n<li><strong>DFD External Entity \u2192 UML Actor<\/strong><br \/>\n      \u201cLab Technician\u201d (external) becomes an \u201cActor\u201d in UML, linked to the \u201cSubmit Lab Test\u201d use case.<\/li>\n<\/ol>\n<p>These mappings are not rigid\u2014they are guidelines. But they ensure consistency when translating between models.<\/p>\n<h3>Example: From DFD to UML \u2013 Patient Admission<\/h3>\n<p>Consider a Level 1 DFD for patient admission:<\/p>\n<ul>\n<li><strong>External Entity:<\/strong> Patient (inputs \u201cAdmission Form\u201d)<\/li>\n<li><strong>Process:<\/strong> Validate Registration<\/li>\n<li><strong>Data Store:<\/strong> Patient Master Index<\/li>\n<li><strong>Data Flow:<\/strong> \u201cAdmission Record\u201d \u2192 \u201cMedical Record System\u201d<\/li>\n<\/ul>\n<p>Now map this into UML:<\/p>\n<ul>\n<li>\u201cPatient\u201d (actor) triggers the \u201cAdmit Patient\u201d use case.<\/li>\n<li>\u201cValidate Registration\u201d becomes a system activity in the use case flow.<\/li>\n<li>\u201cPatient Master Index\u201d becomes a \u201cPatientRecordRepository\u201d class.<\/li>\n<li>\u201cAdmission Record\u201d becomes a \u201cPatientAdmission\u201d object passed to the \u201cMedicalRecordSystem\u201d service.<\/li>\n<\/ul>\n<p>This shows how DFDs provide the data backbone, while UML adds behavioral precision.<\/p>\n<h2>When to Use Each: Decision Guide<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Best Model<\/th>\n<th>Why<\/th>\n<\/tr>\n<tr>\n<td>Showing how patient records move between departments<\/td>\n<td>DFD<\/td>\n<td>Clear flow of data across systems; required for HIPAA audits<\/td>\n<\/tr>\n<tr>\n<td>Modeling a care path for a chronic condition (e.g., diabetes)<\/td>\n<td>UML<\/td>\n<td>Tracks patient state, decision points, and clinician actions<\/td>\n<\/tr>\n<tr>\n<td>Mapping data handling for a clinical trial compliance audit<\/td>\n<td>DFD<\/td>\n<td>Documents data lineage from source to storage, including access logs<\/td>\n<\/tr>\n<tr>\n<td>Designing a handoff between nurses and physicians during shift change<\/td>\n<td>UML<\/td>\n<td>Models communication, timing, and role-specific actions<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t hard rules. But they reflect a pattern I\u2019ve seen in over five healthcare system modernizations. DFDs handle data. UML handles behavior. Using them together avoids the trap of over-modeling (UML) or under-modeling (DFD).<\/p>\n<h3>Common Pitfalls to Avoid<\/h3>\n<ul>\n<li><strong>Overusing UML for data tracking:<\/strong> UML isn\u2019t optimized for data lineage. You\u2019ll end up with complex class diagrams that don\u2019t show flow clearly.<\/li>\n<li><strong>Using DFDs for clinical decisions:<\/strong> DFDs don\u2019t model state changes, conditions, or time-sensitive actions. They can\u2019t capture \u201cif temperature &gt; 101.5, trigger alert.\u201d<\/li>\n<li><strong>Ignoring the handoff:<\/strong> Without mapping rules, the two models drift apart. One team may update the DFD; the other updates the UML. Chaos ensues.<\/li>\n<\/ul>\n<p>Always link them. Use traceability matrices. Use shared identifiers (e.g., \u201cAdmission-01\u201d in both models).<\/p>\n<h2>Practical Implementation: A Healthcare Project Flow<\/h2>\n<p>Here\u2019s how to apply the dual-notation strategy in a real project:<\/p>\n<ol>\n<li><strong>Phase 1: Requirements Gathering (DFD Context)<\/strong><br \/>\n      Create a DFD Level 0 to show system boundaries and data exchanges with external entities (e.g., patient, lab, insurance).<\/li>\n<li><strong>Phase 2: Compliance &amp; Audit Mapping (DFD Level 1)<\/strong><br \/>\n      Decompose processes like \u201cProcess Lab Results\u201d to show data entry, validation, and routing. This becomes your HIPAA compliance map.<\/li>\n<li><strong>Phase 3: Clinical Workflow Design (UML Use Cases)<\/strong><br \/>\n      Based on the DFD, define clinical workflows: \u201cAdmit Patient,\u201d \u201cMonitor Vital Signs,\u201d \u201cDischarge Patient.\u201d Use actors like \u201cNurse,\u201d \u201cPhysician,\u201d \u201cPatient.\u201d<\/li>\n<li><strong>Phase 4: Detailed Behavior (UML Sequence\/State Diagrams)<\/strong><br \/>\n      Model key interactions: \u201cHow is sepsis risk assessed?\u201d and \u201cWhat happens when a patient\u2019s status changes from stable to unstable?\u201d<\/li>\n<li><strong>Phase 5: Integration &amp; Validation<\/strong><br \/>\n      Cross-check that all data flows in the DFD are accounted for in UML messages. Ensure that all clinical actions in UML trigger valid data updates in the DFD.<\/li>\n<\/ol>\n<p>This sequence ensures that every data movement has a clinical purpose, and every clinical action has a data dependency.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use DFDs and UML in the same project?<\/h3>\n<p>Absolutely. Many healthcare IT projects do. Use DFDs to model data movement under compliance requirements and UML to model care processes. The key is to maintain traceability between the two.<\/p>\n<h3>Is UML too complex for clinical teams?<\/h3>\n<p>Yes, if used alone. But UML doesn\u2019t need to be the final artifact for clinicians. Use simplified UML diagrams (e.g., sequence diagrams) to explain workflows. Pair them with DFDs for data transparency.<\/p>\n<h3>How do DFDs support HIPAA compliance?<\/h3>\n<p>DFDs map every point where patient data is accessed, processed, or stored. They show data lineage\u2014exactly what HIPAA requires for audit readiness. DFDs also highlight where data is shared with third parties, which is critical for breach reporting.<\/p>\n<h3>Can UML handle data privacy requirements?<\/h3>\n<p>Not directly. UML doesn\u2019t model data access control or retention policies. But you can extend UML with constraints (e.g., \u201c@PrivacyLevel: High\u201d) or use DFDs to define where and how data is handled.<\/p>\n<h3>Do I need special tools to manage both?<\/h3>\n<p>Yes\u2014tools like Visual Paradigm support both DFD and UML.<\/p>\n<h3>What if the DFD and UML don\u2019t match?<\/h3>\n<p>That\u2019s a red flag. Discrepancies mean either a misunderstanding of the system or a gap in documentation. Use a traceability matrix to bridge the two models. Revisit requirements with the project team.<\/p>\n<p>Remember: In healthcare, <em>accuracy<\/em> is not optional. The right notation choice isn\u2019t just about clarity\u2014it\u2019s about patient safety and legal compliance. DFDs and UML aren\u2019t competitors. They\u2019re partners. Use them together, and your models will not only be accurate\u2014they\u2019ll be trustworthy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a private clinic in Portland, a team spent three wee [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":804,"menu_order":2,"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-807","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>Healthcare DFD vs UML: Clinical &amp; Data Flow Modeling<\/title>\n<meta name=\"description\" content=\"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.\" \/>\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\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Healthcare DFD vs UML: Clinical &amp; Data Flow Modeling\" \/>\n<meta property=\"og:description\" content=\"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/\",\"name\":\"Healthcare DFD vs UML: Clinical & Data Flow Modeling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:25:03+00:00\",\"description\":\"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Flow Diagrams vs. UML: When to Use Each\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Industry and Domain-Specific Guidance\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Healthcare: DFDs for Patient Data Flows, UML for Clinical Workflows\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Healthcare DFD vs UML: Clinical & Data Flow Modeling","description":"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.","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\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/","og_locale":"zh_CN","og_type":"article","og_title":"Healthcare DFD vs UML: Clinical & Data Flow Modeling","og_description":"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"7 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/","name":"Healthcare DFD vs UML: Clinical & Data Flow Modeling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:25:03+00:00","description":"Master the dual-notation strategy for healthcare systems: use DFDs for HIPAA-compliant patient data flow and UML for clinical workflow modeling. Practical guidance for compliance, interoperability, and system design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/healthcare-dfd-vs-uml\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Data Flow Diagrams vs. UML: When to Use Each","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/"},{"@type":"ListItem","position":3,"name":"Industry and Domain-Specific Guidance","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/dfd-vs-uml-when-to-use-each\/dfd-vs-uml-by-industry\/"},{"@type":"ListItem","position":4,"name":"Healthcare: DFDs for Patient Data Flows, UML for Clinical Workflows"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/807","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/807\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/804"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=807"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}