{"id":20755,"date":"2026-08-31T17:01:11","date_gmt":"2026-08-31T17:01:11","guid":{"rendered":"https:\/\/dianapps.com\/blog\/?p=20755"},"modified":"2026-08-31T17:01:29","modified_gmt":"2026-08-31T17:01:29","slug":"salesforce-development-for-healthcare","status":"publish","type":"post","link":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/","title":{"rendered":"Salesforce Development for Healthcare: What Actually Needs Custom Building"},"content":{"rendered":"<p><b>Key Takeaways<\/b><span style=\"font-weight: 400;\">:\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Health Cloud already provides a FHIR R4-aligned clinical data model, so rebuilding patients, care plans and clinical encounters is usually unnecessary.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Health Cloud is HIPAA-eligible, not automatically HIPAA-compliant. Configuration, access controls, PHI handling and security remain the organization&#8217;s responsibility.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Custom development is most valuable for patient\/provider portals, clinical calculators, consent workflows, intake forms, integration logic and regulator-specific reporting.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EHR integrations commonly involve FHIR R4 and HL7 v2, so teams should not assume every integration is simply a FHIR connector.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Health Cloud is generally the better foundation for genuinely clinical use cases, while core Salesforce can be sufficient for administrative workflows without PHI.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Healthcare Salesforce projects typically require 25\u201340% more investment than comparable unregulated projects because of testing, documentation, validation, and security requirements.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Patient data should be masked before developers work in Full or Partial Copy sandboxes.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The biggest mistake is building custom objects for functionality Health Cloud already provides.<\/span><\/li>\n<\/ul>\n<blockquote><p><b>Quick Answer<\/b><span style=\"font-weight: 400;\">: Salesforce for healthcare works best when organizations extend Health Cloud rather than rebuild its clinical foundation. Health Cloud already provides FHIR-aligned objects for patients, care plans, care teams and clinical encounters, while custom development is better reserved for patient portals, clinical calculations, consent workflows, EHR integrations and organization-specific reporting. Healthcare teams also need to treat HIPAA requirements, PHI security and compliance as part of the development process from the beginning, not as a final checklist.<\/span><\/p><\/blockquote>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">The most expensive mistake in healthcare Salesforce projects isn\u2019t building the wrong thing. It\u2019s rebuilding something the platform already gives you.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Health Cloud\u2019s clinical data model is aligned to FHIR release 4 out of the box. Patient, Care Plan, Care Team, Clinical Encounter, Condition, Medication &#8211; these exist as standard objects, structured to exchange data with EHR systems. Teams that scope custom objects for them spend six figures recreating something that already works, and then discover their integration doesn\u2019t map cleanly.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This guide covers what genuinely needs building, what only needs extending, and the compliance details that shape both.<\/span><\/p>\n<h2><b>Where Standard Salesforce Stops for Healthcare<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Sales Cloud and Service Cloud assume a commercial relationship &#8211; accounts, contacts, opportunities, cases. Healthcare assumes something structurally different: a patient with a longitudinal record, a care team rather than an owner, clinical encounters rather than transactions, and data governed by regulation rather than commercial preference.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Health Cloud closes most of that gap; it adds the clinical data model, care plans, referral management, provider and payer relationships, and an FHIR-aligned structure designed for exchanging data with external clinical systems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What it doesn\u2019t close is anything specific to your organisation\u2019s protocols, your regulator, your patient experience, or the systems you happen to run. That\u2019s where development starts.<\/span><\/p>\n<h2><b>Don\u2019t Build What Health Cloud Already Gives You<\/b><\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-20760\" src=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM.webp\" alt=\"Three-column comparison showing what is already standard in Health Cloud, what should be extended, and what genuinely needs custom building\" width=\"1536\" height=\"1024\" srcset=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM.webp 1536w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM-1024x683.webp 1024w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM-768x512.webp 768w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM-640x427.webp 640w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_46_02-PM-400x267.webp 400w\" sizes=\"auto, (max-width: 1536px) 100vw, 1536px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Three-column comparison showing what is already standard in Health Cloud, what should be extended, and what genuinely needs custom building<\/span><\/i><\/p>\n<p><b>The Rule:<\/b><span style=\"font-weight: 400;\"> Salesforce publishes an HL7 and FHIR mapping reference for Health Cloud. Read it before scoping a single custom object.<\/span><\/p>\n<p><b>Why It Matters Beyond Cost:<\/b><span style=\"font-weight: 400;\"> If you build a custom Patient object rather than using Person Accounts, your EHR integration no longer maps to a standard structure. Every future interoperability requirement becomes bespoke work, and the FHIR integration framework Salesforce provides stops helping you.<\/span><\/p>\n<p><b>The Honest Exception:<\/b><span style=\"font-weight: 400;\"> Occasionally an organisation\u2019s model genuinely doesn\u2019t fit &#8211; unusual entity relationships, a non-clinical use case, or a regulatory structure with no standard equivalent. That\u2019s a real conversation to have with an architect, not an assumption to build on.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When an organisation genuinely falls outside Health Cloud&#8217;s standard model, that decision should involve the right technical expertise. Understanding the difference between a <\/span><a href=\"https:\/\/dianapps.com\/blog\/salesforce-admin-vs-developer-vs-architect\/\"><span style=\"font-weight: 400;\">Salesforce admin, developer, and architect<\/span><\/a><span style=\"font-weight: 400;\"> can help determine whether the requirement needs configuration, custom code, or architectural design.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Related: T<\/span><span style=\"font-weight: 400;\">he Salesforce data model explained<\/span><span style=\"font-weight: 400;\"> \u00b7 C<\/span><span style=\"font-weight: 400;\">onfiguration vs customization<\/span><\/p>\n<h2><b>Health Cloud or Build on Core?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The question most healthcare buyers actually have.<\/span><\/p>\n\n<table id=\"tablepress-287\" class=\"tablepress tablepress-id-287\">\n<thead>\n<tr class=\"row-1\">\n\t<td class=\"column-1\"><\/td><th class=\"column-2\">Health Cloud<\/th><th class=\"column-3\">Service Cloud + custom<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Clinical data model<\/td><td class=\"column-2\">FHIR R4-aligned, out of the box<\/td><td class=\"column-3\">You build and maintain it<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Care plans and care teams<\/td><td class=\"column-2\">Standard<\/td><td class=\"column-3\">Custom objects and automation<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">FHIR integration framework<\/td><td class=\"column-2\">Provided<\/td><td class=\"column-3\">You build the mapping layer<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">BAA coverage<\/td><td class=\"column-2\">Yes, Health Cloud is named<\/td><td class=\"column-3\">Select Enterprise editions only - check<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Licence cost<\/td><td class=\"column-2\">Higher - from around $325\/user\/month list<\/td><td class=\"column-3\">Lower per seat<\/td>\n<\/tr>\n<tr class=\"row-7\">\n\t<td class=\"column-1\">Build cost<\/td><td class=\"column-2\">Lower - configuration over construction<\/td><td class=\"column-3\">Substantially higher<\/td>\n<\/tr>\n<tr class=\"row-8\">\n\t<td class=\"column-1\">Ongoing maintenance<\/td><td class=\"column-2\">Salesforce maintains the model<\/td><td class=\"column-3\">You maintain everything you built<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-287 from cache -->\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Where The Maths Lands:<\/b><span style=\"font-weight: 400;\"> Health Cloud licences cost more per seat and less overall for anything genuinely clinical, because you\u2019re buying a data model rather than building one. Building the same capability on Service Cloud is usually cheaper in year one and more expensive by year three.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Where core Salesforce Is Genuinely Fine:<\/b><span style=\"font-weight: 400;\"> Administrative use cases with no PHI and no clinical model, a healthcare organisation\u2019s HR portal, supplier management, or facilities requests. Don\u2019t pay Health Cloud licence rates for those.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">For administrative healthcare workflows without PHI or a clinical model, <\/span><a href=\"https:\/\/dianapps.com\/blog\/salesforce-low-code-development-guide\/\"><span style=\"font-weight: 400;\">Salesforce low-code development<\/span><\/a><span style=\"font-weight: 400;\"> can keep the implementation configuration-led rather than introducing unnecessary custom code.<\/span><\/p>\n<div style=\"background: #EEF2FE; border: 1px solid #DBE2FB; border-radius: 14px; padding: 28px 32px; margin: 38px 0;\">\n<h4 style=\"color: #1b3fae; font-size: 22px; line-height: 1.3; font-weight: bold; margin: 0 0 10px;\"><span style=\"font-weight: 400;\"><b>Need to Build Salesforce for Healthcare?<\/b><\/span><\/h4>\n<p style=\"color: #4b5563; font-size: 16px; line-height: 1.6; margin: 0 0 22px;\"><span style=\"font-weight: 400;\">Map your Health Cloud boundaries, clinical workflows, integrations, and compliance requirements before deciding what to configure, extend, or custom-build.<\/span><\/p>\n<p><a style=\"display: inline-block; background: #2563EB; color: #ffffff; text-decoration: none; font-size: 15px; font-weight: 600; padding: 13px 26px; border-radius: 8px;\" href=\"https:\/\/dianapps.com\/salesforce-development-services\">Salesforce Development Services<\/a><\/p>\n<\/div>\n<p><span style=\"font-weight: 400;\">Related: <\/span><span style=\"font-weight: 400;\">Salesforce customization cost<\/span><\/p>\n<h2><b>\u201cHIPAA-Eligible\u201d Is Not \u201cHIPAA-Compliant\u201d<\/b><\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-20761\" src=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM.webp\" alt=\"Comparison of what Salesforce provides for HIPAA compliance versus what the customer must configure themselves\" width=\"1536\" height=\"1024\" srcset=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM.webp 1536w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM-1024x683.webp 1024w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM-768x512.webp 768w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM-640x427.webp 640w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_47_27-PM-400x267.webp 400w\" sizes=\"auto, (max-width: 1536px) 100vw, 1536px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Comparison of what Salesforce provides for HIPAA compliance versus what the customer must configure themselves<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400;\">This distinction decides whether a build passes an audit, and it\u2019s stated carelessly almost everywhere.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Salesforce signs a BAA, and Health Cloud along with select Enterprise editions of Sales and Service Cloud fall under it. That makes the platform <\/span><i><span style=\"font-weight: 400;\">eligible<\/span><\/i><span style=\"font-weight: 400;\"> to handle PHI.<\/span><\/p>\n<p><b>Two Things That Catch Teams Out:<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The BAA covers a defined list of services &#8211; not the whole platform. Not every Salesforce capability, add-on or feature is in scope. Building a PHI-handling workflow on a service that isn\u2019t covered creates an exposure nobody notices until an audit.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configuration and access management remain your responsibility, not Salesforce\u2019s. Sharing rules that over-expose PHI internally, an Apex class that skips FLS enforcement, or a sandbox full of unmasked patient data are all your problem regardless of what the BAA says.<\/span><\/li>\n<\/ul>\n<p><b>What this means for development specifically:<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enforce FLS in <\/span><b>every<\/b><span style=\"font-weight: 400;\"> Apex class and Flow touching clinical data &#8211; <\/span><span style=\"font-weight: 400;\">WITH USER_MODE<\/span><span style=\"font-weight: 400;\"> rather than manual checks. See the <\/span><a href=\"https:\/\/dianapps.com\/blog\/apex-programming-guide\/\"><span style=\"font-weight: 400;\">Apex guide<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Mask PHI before anyone develops against a sandbox.<\/b><span style=\"font-weight: 400;\"> Full and Partial copies bring real patient data into a lower-security environment. See <\/span><a href=\"https:\/\/dianapps.com\/blog\/salesforce-sandbox-explained\/\"><span style=\"font-weight: 400;\">Salesforce sandboxes<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Record-triggered Flows and Apex run in <\/span><b>system mode<\/b><span style=\"font-weight: 400;\"> and ignore sharing entirely &#8211; a genuine PHI exposure route. See <\/span><a href=\"https:\/\/dianapps.com\/blog\/the-ultimate-guide-to-salesforce-flow\/\"><span style=\"font-weight: 400;\">Salesforce Flow<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shield Platform Encryption and Event Monitoring are <\/span><b>paid add-ons<\/b><span style=\"font-weight: 400;\">, not included.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Related: <\/span><span style=\"font-weight: 400;\">Salesforce compliance and data security<\/span><\/p>\n<div style=\"background: #EEF2FE; border: 1px solid #DBE2FB; border-radius: 14px; padding: 28px 32px; margin: 38px 0;\">\n<h4 style=\"color: #1b3fae; font-size: 22px; line-height: 1.3; font-weight: bold; margin: 0 0 10px;\"><span style=\"font-weight: 400;\"><b>Building on Salesforce with PHI involved?<\/b><\/span><\/h4>\n<p style=\"color: #4b5563; font-size: 16px; line-height: 1.6; margin: 0 0 22px;\"><span style=\"font-weight: 400;\">The compliance workstream runs alongside the build, not after it. We\u2019ll map what\u2019s in BAA scope and what your configuration has to cover.<\/span><\/p>\n<p><a style=\"display: inline-block; background: #2563EB; color: #ffffff; text-decoration: none; font-size: 15px; font-weight: 600; padding: 13px 26px; border-radius: 8px;\" href=\"https:\/\/dianapps.com\/salesforce-development-services\">Talk to our Salesforce development team \u2192<\/a><\/p>\n<\/div>\n<h2><b>What Healthcare Organisations Actually Build<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The custom work that genuinely earns its cost:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Patient And Provider Portals:<\/b><span style=\"font-weight: 400;\"> Experience Cloud sites for appointment booking, results access, referral submission and document upload. Almost always custom, because the patient experience is the differentiator.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Clinical Scoring And Eligibility Calculators:<\/b><span style=\"font-weight: 400;\"> Risk scores, trial eligibility, care pathway triggers. Business logic no standard object encodes.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Consent And Authorisation Workflows:<\/b><span style=\"font-weight: 400;\"> Consent capture, revocation, and the audit trail proving both. Highly organisation-specific and increasingly scrutinised.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Intake And Assessment Forms:<\/b><span style=\"font-weight: 400;\"> Screen Flows for structured clinical intake, often with conditional logic reflecting a specific protocol.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Integration Middleware Logic:<\/b><span style=\"font-weight: 400;\"> The FHIR framework handles a lot, but mapping to a legacy Meditech instance or a claims platform with a proprietary format is real work.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Regulator-Specific Reporting:<\/b><span style=\"font-weight: 400;\"> Quality measures, submissions, and disclosure reports in whatever format your regulator specifies.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This is where Salesforce Development Services become valuable, extending Health Cloud with the patient experiences, clinical logic, consent workflows, integrations, and reporting requirements that are specific to each organisation.<\/span><\/p>\n<div style=\"background: #EEF2FE; border: 1px solid #DBE2FB; border-radius: 14px; padding: 28px 32px; margin: 38px 0;\">\n<h4 style=\"color: #1b3fae; font-size: 22px; line-height: 1.3; font-weight: bold; margin: 0 0 10px;\"><span style=\"font-weight: 400;\"><b>Need Salesforce Developers for Healthcare?<\/b><\/span><\/h4>\n<p style=\"color: #4b5563; font-size: 16px; line-height: 1.6; margin: 0 0 22px;\"><span style=\"font-weight: 400;\">Add experienced Salesforce developers for patient portals, clinical calculators, consent workflows, FHIR integrations, reporting, and healthcare-specific automation.<\/span><\/p>\n<p><a style=\"display: inline-block; background: #2563EB; color: #ffffff; text-decoration: none; font-size: 15px; font-weight: 600; padding: 13px 26px; border-radius: 8px;\" href=\"https:\/\/dianapps.com\/hire-salesforce-developers\">Hire Salesforce Developers<\/a><\/p>\n<\/div>\n<p>&nbsp;<\/p>\n<h2><b>The Integration Surface<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Healthcare integration is where most of the budget and most of the risk sits.<\/span><\/p>\n\n<table id=\"tablepress-288\" class=\"tablepress tablepress-id-288\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">System type<\/th><th class=\"column-2\">Typical examples<\/th><th class=\"column-3\">Standard<\/th><th class=\"column-4\">Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">EHR<\/td><td class=\"column-2\">Epic, Cerner, Meditech, Allscripts<\/td><td class=\"column-3\">HL7 v2, FHIR R4<\/td><td class=\"column-4\">Salesforce provides a pre-built FHIR framework<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Practice management<\/td><td class=\"column-2\">Varies widely<\/td><td class=\"column-3\">REST, proprietary<\/td><td class=\"column-4\">Often the messiest integration<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Claims and billing<\/td><td class=\"column-2\">Payer clearinghouses<\/td><td class=\"column-3\">X12 EDI<\/td><td class=\"column-4\">Rarely FHIR; usually needs middleware<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Lab and diagnostics<\/td><td class=\"column-2\">LIS platforms<\/td><td class=\"column-3\">HL7 v2<\/td><td class=\"column-4\">Results in, orders out<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Patient engagement<\/td><td class=\"column-2\">SMS, email, telehealth<\/td><td class=\"column-3\">REST<\/td><td class=\"column-4\">Consent state must flow through<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-288 from cache -->\n<p><b>Two Things Worth Knowing:<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Salesforce\u2019s pre-built FHIR integration framework reduces custom development substantially, but it still requires meaningful configuration. Plan six to ten weeks for a first EHR integration rather than assuming it\u2019s a connector you switch on.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HL7 v2 and FHIR are not the same thing, and plenty of EHR estates still run v2 for real-time messaging. If your integration partner talks only about FHIR, ask what they\u2019ll do about v2 interfaces.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Related: <\/span><span style=\"font-weight: 400;\">Salesforce API integration<\/span><span style=\"font-weight: 400;\"> \u00b7 <\/span><span style=\"font-weight: 400;\">Salesforce integration guide<\/span><\/p>\n<h2><b>What It Costs<\/b><\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-20762\" src=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM.webp\" alt=\"Cost bands for healthcare Salesforce builds range from custom fields at 3 to 10 thousand dollars up to custom HL7 integration at 60 to 180 thousand\" width=\"1536\" height=\"1024\" srcset=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM.webp 1536w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM-1024x683.webp 1024w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM-768x512.webp 768w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM-640x427.webp 640w, https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/ChatGPT-Image-Aug-31-2026-04_49_27-PM-400x267.webp 400w\" sizes=\"auto, (max-width: 1536px) 100vw, 1536px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Cost bands for healthcare Salesforce builds range from custom fields at 3 to 10 thousand dollars up to custom HL7 integration at 60 to 180 thousand<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400;\">The healthcare premium is real; comparable builds cost roughly 25\u201340% more than in unregulated industries, and it isn\u2019t the code; it\u2019s the testing, the documentation, the validation evidence, and the security review that regulated environments require.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Licences Sit On Top: <\/b><span style=\"font-weight: 400;\">Health Cloud lists from around $325 per user per month, rising for Unlimited and Einstein 1 editions. Mid-market implementations commonly land between $80,000 and $200,000 before ongoing development.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Discovery is heavier here than elsewhere, and cutting it is a false economy. A proper healthcare discovery produces a data model, an integration architecture document, a care plan template library, a persona matrix, and a HIPAA risk assessment. The gap between what administrators think clinical staff does and what they actually do is consistently larger than anyone expects.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Those costs also make the delivery model important. The <\/span><a href=\"https:\/\/dianapps.com\/blog\/in-house-vs-outsourced-salesforce-development\/\"><span style=\"font-weight: 400;\">in-house vs outsourced Salesforce development<\/span><\/a><span style=\"font-weight: 400;\"> decision should account for healthcare-specific skills, compliance requirements, project duration, and the need for ongoing maintenance.<\/span><\/p>\n<h2><b>The Mistakes That Cost Most<\/b><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Rebuilding The Clinical Data Model:<\/b><span style=\"font-weight: 400;\"> Covered above, and it\u2019s the expensive one.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Treating Compliance As A Phase:<\/b><span style=\"font-weight: 400;\"> It runs alongside the build. Retrofitting FLS enforcement and audit trails across a finished system costs multiples of building them in.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Developing Against Unmasked PHI:<\/b><span style=\"font-weight: 400;\"> Common, and indefensible in an audit.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Assuming The BAA Covers Everything:<\/b><span style=\"font-weight: 400;\"> Check which services are in scope before you architect on one.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Underestimating Clinical Stakeholder Time:<\/b><span style=\"font-weight: 400;\"> Nurses and clinicians are the users, and they\u2019re the hardest people in any organisation to get into a requirements workshop.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Building For The Process Rather Than Fixing It:<\/b><span style=\"font-weight: 400;\"> Automating a broken referral pathway makes it faster and harder to change.<\/span><\/li>\n<\/ul>\n<h2><b>Where to Go Next<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">For the compliance framework in more depth, see <\/span><span style=\"font-weight: 400;\">Salesforce compliance and data security<\/span><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For the integration surface, <\/span><span style=\"font-weight: 400;\">Salesforce integration<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">Salesforce API integration<\/span><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For the build decision, <\/span><span style=\"font-weight: 400;\">configuration vs customization<\/span><span style=\"font-weight: 400;\"> and <\/span><a href=\"https:\/\/dianapps.com\/blog\/custom-salesforce-development-benefits\/\"><span style=\"font-weight: 400;\">custom Salesforce development<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For budgeting, <\/span><span style=\"font-weight: 400;\">Salesforce customization cost<\/span><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For protecting PHI in lower environments, <\/span><a href=\"https:\/\/dianapps.com\/blog\/salesforce-sandbox-explained\/\"><span style=\"font-weight: 400;\">Salesforce sandboxes explained<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><a href=\"https:\/\/dianapps.com\/blog\/salesforce-development-guide\/\"><span style=\"font-weight: 400;\">complete Salesforce development guide<\/span><\/a><span style=\"font-weight: 400;\"> is the hub.<\/span><\/p>\n<h2><b>Before You Scope a Healthcare Build<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The first thing we do on a healthcare Salesforce enquiry is check what\u2019s already standard.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s a slightly awkward opening, because it usually means the scope shrinks &#8211; but rebuilding Health Cloud\u2019s clinical model is the single most expensive mistake in this sector, and it\u2019s easier to prevent than to unwind.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We\u2019re a certified Salesforce Consulting Partner with developers, architects and consultants across the US, UK, Australia, Canada, UAE and India.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">On a scoping call, we\u2019ll tell you which requirements are standard configuration, which genuinely need code, and where the compliance workstream has to run alongside the build rather than after it.<\/span><\/p>\n<div style=\"background: #EEF2FE; border: 1px solid #DBE2FB; border-radius: 14px; padding: 28px 32px; margin: 38px 0;\">\n<h4 style=\"color: #1b3fae; font-size: 22px; line-height: 1.3; font-weight: bold; margin: 0 0 10px;\"><span style=\"font-weight: 400;\"><b>Ready to Scope Your Healthcare Salesforce Build?<\/b><\/span><\/h4>\n<p style=\"color: #4b5563; font-size: 16px; line-height: 1.6; margin: 0 0 22px;\"><span style=\"font-weight: 400;\">Tell us what Health Cloud already covers, where your workflows need extension, and which compliance and integration requirements need custom development.<\/span><\/p>\n<p><a style=\"display: inline-block; background: #2563EB; color: #ffffff; text-decoration: none; font-size: 15px; font-weight: 600; padding: 13px 26px; border-radius: 8px;\" href=\"https:\/\/dianapps.com\/contact\">Talk to Our Team<\/a><\/p>\n<\/div>\n<style>.elementor-20763 .elementor-element.elementor-element-2932a52{text-align:left;}.elementor-20763 .elementor-element.elementor-element-2932a52 > .elementor-widget-container{margin:0px 0px 0px 0px;}.elementor-20763 .elementor-element.elementor-element-0b767d1 .elementor-tab-title{border-width:1px;border-color:#00000014;}.elementor-20763 .elementor-element.elementor-element-0b767d1 .elementor-tab-content{border-width:1px;border-bottom-color:#00000014;}.elementor-20763 .elementor-element.elementor-element-0b767d1 > .elementor-widget-container{margin:0px 0px 0px 0px;}<\/style><div class=\"porto-block elementor elementor-20763\">\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-27707ca elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"27707ca\" data-element_type=\"section\">\r\n\t\t\t\r\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\r\n\t\t\t\t\t\t\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-0163611\" data-id=\"0163611\" data-element_type=\"column\">\r\n\r\n\t\t\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\r\n\t\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-03a2969 elementor-widget elementor-widget-text-editor\" data-id=\"03a2969\" 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.14.0 - 26-06-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\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2932a52 elementor-widget elementor-widget-heading\" data-id=\"2932a52\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.14.0 - 26-06-2023 *\/\n.elementor-heading-title{padding:0;margin:0;line-height:1}.elementor-widget-heading .elementor-heading-title[class*=elementor-size-]>a{color:inherit;font-size:inherit;line-height:inherit}.elementor-widget-heading .elementor-heading-title.elementor-size-small{font-size:15px}.elementor-widget-heading .elementor-heading-title.elementor-size-medium{font-size:19px}.elementor-widget-heading .elementor-heading-title.elementor-size-large{font-size:29px}.elementor-widget-heading .elementor-heading-title.elementor-size-xl{font-size:39px}.elementor-widget-heading .elementor-heading-title.elementor-size-xxl{font-size:59px}<\/style><h2 class=\"elementor-heading-title elementor-size-large\">FAQs <\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-0b767d1 elementor-widget elementor-widget-toggle\" data-id=\"0b767d1\" data-element_type=\"widget\" data-widget_type=\"toggle.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.14.0 - 26-06-2023 *\/\n.elementor-toggle{text-align:left}.elementor-toggle .elementor-tab-title{font-weight:700;line-height:1;margin:0;padding:15px;border-bottom:1px solid #d5d8dc;cursor:pointer;outline:none}.elementor-toggle .elementor-tab-title .elementor-toggle-icon{display:inline-block;width:1em}.elementor-toggle .elementor-tab-title .elementor-toggle-icon svg{-webkit-margin-start:-5px;margin-inline-start:-5px;width:1em;height:1em}.elementor-toggle .elementor-tab-title .elementor-toggle-icon.elementor-toggle-icon-right{float:right;text-align:right}.elementor-toggle .elementor-tab-title .elementor-toggle-icon.elementor-toggle-icon-left{float:left;text-align:left}.elementor-toggle .elementor-tab-title .elementor-toggle-icon .elementor-toggle-icon-closed{display:block}.elementor-toggle .elementor-tab-title .elementor-toggle-icon .elementor-toggle-icon-opened{display:none}.elementor-toggle .elementor-tab-title.elementor-active{border-bottom:none}.elementor-toggle .elementor-tab-title.elementor-active .elementor-toggle-icon-closed{display:none}.elementor-toggle .elementor-tab-title.elementor-active .elementor-toggle-icon-opened{display:block}.elementor-toggle .elementor-tab-content{padding:15px;border-bottom:1px solid #d5d8dc;display:none}@media (max-width:767px){.elementor-toggle .elementor-tab-title{padding:12px}.elementor-toggle .elementor-tab-content{padding:12px 10px}}.e-con-inner>.elementor-widget-toggle,.e-con>.elementor-widget-toggle{width:var(--container-widget-width);--flex-grow:var(--container-widget-flex-grow)}<\/style>\t\t<div class=\"elementor-toggle\">\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1201\" class=\"elementor-tab-title\" data-tab=\"1\" role=\"button\" aria-controls=\"elementor-tab-content-1201\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Is Salesforce HIPAA compliant for healthcare?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1201\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"1\" role=\"region\" aria-labelledby=\"elementor-tab-title-1201\"><p><span style=\"font-weight: 400;\">Salesforce is HIPAA-<\/span><i><span style=\"font-weight: 400;\">eligible<\/span><\/i><span style=\"font-weight: 400;\">: it signs a BAA covering Health Cloud and select Enterprise editions of Sales and Service Cloud. Compliance depends on your configuration &#8211; sharing rules, field-level security, access management, and audit practices remain your responsibility, and the BAA covers a defined list of services rather than the whole platform.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1202\" class=\"elementor-tab-title\" data-tab=\"2\" role=\"button\" aria-controls=\"elementor-tab-content-1202\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Do I need Health Cloud or can I build on Service Cloud?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1202\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"2\" role=\"region\" aria-labelledby=\"elementor-tab-title-1202\"><p><span style=\"font-weight: 400;\">Health Cloud for anything genuinely clinical; its FHIR-aligned data model, care plans, and referral management would otherwise be a large custom build you then maintain forever. Service Cloud is fine for administrative use cases with no PHI and no clinical model.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1203\" class=\"elementor-tab-title\" data-tab=\"3\" role=\"button\" aria-controls=\"elementor-tab-content-1203\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Should I build custom objects for patients and care plans?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1203\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"3\" role=\"region\" aria-labelledby=\"elementor-tab-title-1203\"><p><span style=\"font-weight: 400;\">No. Health Cloud provides Patient (as Person Account), Care Plan, Care Team, Clinical Encounter, Condition, and Medication as standard, aligned to FHIR release 4. Building custom equivalents costs six figures and breaks your ability to use Salesforce\u2019s FHIR integration framework.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1204\" class=\"elementor-tab-title\" data-tab=\"4\" role=\"button\" aria-controls=\"elementor-tab-content-1204\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">How does Salesforce integrate with Epic or Cerner?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1204\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"4\" role=\"region\" aria-labelledby=\"elementor-tab-title-1204\"><p><span style=\"font-weight: 400;\">Through HL7 v2 and FHIR R4, Salesforce provides a pre-built FHIR integration framework that reduces custom development considerably, though it still needs significant configuration &#8211; plan six to ten weeks for a first EHR integration rather than treating it as a switch-on connector.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1205\" class=\"elementor-tab-title\" data-tab=\"5\" role=\"button\" aria-controls=\"elementor-tab-content-1205\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">How much does Salesforce development for healthcare cost?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1205\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"5\" role=\"region\" aria-labelledby=\"elementor-tab-title-1205\"><p><span style=\"font-weight: 400;\">Individual builds range from around $3,000 for configuration work to $180,000 for a complex non-standard HL7 integration. Mid-market Health Cloud implementations commonly run $80,000\u2013$200,000 before ongoing development, with licences from roughly $325 per user per month on top.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1206\" class=\"elementor-tab-title\" data-tab=\"6\" role=\"button\" aria-controls=\"elementor-tab-content-1206\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Why is healthcare Salesforce development more expensive?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1206\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"6\" role=\"region\" aria-labelledby=\"elementor-tab-title-1206\"><p><span style=\"font-weight: 400;\">Roughly 25 &#8211; 40% more than comparable unregulated work &#8211; driven by testing rigour, documentation, validation evidence, and security review rather than by the code itself. Discovery is also heavier, because clinical workflows need mapping rather than assuming.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1207\" class=\"elementor-tab-title\" data-tab=\"7\" role=\"button\" aria-controls=\"elementor-tab-content-1207\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Can developers work with real patient data in a sandbox?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1207\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"7\" role=\"region\" aria-labelledby=\"elementor-tab-title-1207\"><p><span style=\"font-weight: 400;\">They shouldn\u2019t. Full and Partial Copy sandboxes bring real PHI into a lower-security environment. Run Salesforce Data Mask before granting access, and treat that as a non-negotiable step in your environment strategy.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1208\" class=\"elementor-tab-title\" data-tab=\"8\" role=\"button\" aria-controls=\"elementor-tab-content-1208\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">What about the 21st Century Cures Act and interoperability?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1208\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"8\" role=\"region\" aria-labelledby=\"elementor-tab-title-1208\"><p><span style=\"font-weight: 400;\">It drives the requirement for patient access to their own records and for standards-based exchange, which is why FHIR alignment matters beyond convenience. If patient-facing data access is in scope, treat interoperability as a design constraint rather than a later phase.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toggle-item\">\n\t\t\t\t\t<h3 id=\"elementor-tab-title-1209\" class=\"elementor-tab-title\" data-tab=\"9\" role=\"button\" aria-controls=\"elementor-tab-content-1209\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon elementor-toggle-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-closed\"><i class=\"fas fa-caret-right\"><\/i><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-toggle-icon-opened\"><i class=\"elementor-toggle-icon-opened fas fa-caret-up\"><\/i><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-toggle-title\" tabindex=\"0\">Is Agentforce usable in healthcare?<\/a>\n\t\t\t\t\t<\/h3>\n\n\t\t\t\t\t<div id=\"elementor-tab-content-1209\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"9\" role=\"region\" aria-labelledby=\"elementor-tab-title-1209\"><p><span style=\"font-weight: 400;\">It\u2019s being deployed for patient intake, triage support, and administrative deflection. The constraints are the ones you\u2019d expect &#8211; grounding quality, guardrails against clinical advice, audit trail, and confirming the capability sits within your BAA scope.<\/span><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t<script type=\"application\/ld+json\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Is Salesforce HIPAA compliant for healthcare?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Salesforce is HIPAA-<\\\/span><i><span style=\\\"font-weight: 400;\\\">eligible<\\\/span><\\\/i><span style=\\\"font-weight: 400;\\\">: it signs a BAA covering Health Cloud and select Enterprise editions of Sales and Service Cloud. Compliance depends on your configuration &#8211; sharing rules, field-level security, access management, and audit practices remain your responsibility, and the BAA covers a defined list of services rather than the whole platform.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Do I need Health Cloud or can I build on Service Cloud?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Health Cloud for anything genuinely clinical; its FHIR-aligned data model, care plans, and referral management would otherwise be a large custom build you then maintain forever. Service Cloud is fine for administrative use cases with no PHI and no clinical model.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Should I build custom objects for patients and care plans?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">No. Health Cloud provides Patient (as Person Account), Care Plan, Care Team, Clinical Encounter, Condition, and Medication as standard, aligned to FHIR release 4. Building custom equivalents costs six figures and breaks your ability to use Salesforce\\u2019s FHIR integration framework.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"How does Salesforce integrate with Epic or Cerner?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Through HL7 v2 and FHIR R4, Salesforce provides a pre-built FHIR integration framework that reduces custom development considerably, though it still needs significant configuration &#8211; plan six to ten weeks for a first EHR integration rather than treating it as a switch-on connector.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"How much does Salesforce development for healthcare cost?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Individual builds range from around $3,000 for configuration work to $180,000 for a complex non-standard HL7 integration. Mid-market Health Cloud implementations commonly run $80,000\\u2013$200,000 before ongoing development, with licences from roughly $325 per user per month on top.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Why is healthcare Salesforce development more expensive?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">Roughly 25 &#8211; 40% more than comparable unregulated work &#8211; driven by testing rigour, documentation, validation evidence, and security review rather than by the code itself. Discovery is also heavier, because clinical workflows need mapping rather than assuming.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Can developers work with real patient data in a sandbox?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">They shouldn\\u2019t. Full and Partial Copy sandboxes bring real PHI into a lower-security environment. Run Salesforce Data Mask before granting access, and treat that as a non-negotiable step in your environment strategy.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"What about the 21st Century Cures Act and interoperability?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">It drives the requirement for patient access to their own records and for standards-based exchange, which is why FHIR alignment matters beyond convenience. If patient-facing data access is in scope, treat interoperability as a design constraint rather than a later phase.<\\\/span><\\\/p>\"}},{\"@type\":\"Question\",\"name\":\"Is Agentforce usable in healthcare?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"font-weight: 400;\\\">It\\u2019s being deployed for patient intake, triage support, and administrative deflection. The constraints are the ones you\\u2019d expect &#8211; grounding quality, guardrails against clinical advice, audit trail, and confirming the capability sits within your BAA scope.<\\\/span><\\\/p>\"}}]}<\/script>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\r\n\t\t\t\t<\/div>\r\n\t\t\t\t\t\t<\/div>\r\n\t\t\t\t<\/section>\r\n\t\t<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Key Takeaways:\u00a0 Health Cloud already provides a FHIR R4-aligned clinical data model, so rebuilding patients, care plans and clinical encounters is usually unnecessary. Health Cloud is HIPAA-eligible, not automatically HIPAA-compliant. Configuration, access controls, PHI handling and security remain the organization&#8217;s responsibility. Custom development is most valuable for patient\/provider portals, clinical calculators, consent workflows, intake forms, [&hellip;]<\/p>\n","protected":false},"author":15,"featured_media":20769,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_wp_applaud_exclude":false,"footnotes":""},"categories":[85],"tags":[2671],"class_list":["post-20755","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-salesforce","tag-salesforce-for-healthcare"],"featured_image_src":{"landsacpe":["https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039-1140x445.webp",1140,445,true],"list":["https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039-463x348.webp",463,348,true],"medium":["https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039-300x169.webp",300,169,true],"full":["https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp",1536,864,false]},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Salesforce for Healthcare: What to Build, Extend &amp; Avoid<\/title>\n<meta name=\"description\" content=\"Learn what to build, extend, and avoid in Salesforce for healthcare, including Health Cloud, FHIR, HIPAA, EHR integrations, custom portals, and costs.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Salesforce for Healthcare: What to Build, Extend &amp; Avoid\" \/>\n<meta property=\"og:description\" content=\"Learn what to build, extend, and avoid in Salesforce for healthcare, including Health Cloud, FHIR, HIPAA, EHR integrations, custom portals, and costs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/\" \/>\n<meta property=\"og:site_name\" content=\"Learn About Digital Transformation &amp; Development | DianApps Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-31T17:01:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-31T17:01:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"864\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Vaibhav Sharma\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Vaibhav Sharma\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Salesforce for Healthcare: What to Build, Extend & Avoid","description":"Learn what to build, extend, and avoid in Salesforce for healthcare, including Health Cloud, FHIR, HIPAA, EHR integrations, custom portals, and costs.","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:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/","og_locale":"en_US","og_type":"article","og_title":"Salesforce for Healthcare: What to Build, Extend & Avoid","og_description":"Learn what to build, extend, and avoid in Salesforce for healthcare, including Health Cloud, FHIR, HIPAA, EHR integrations, custom portals, and costs.","og_url":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/","og_site_name":"Learn About Digital Transformation &amp; Development | DianApps Blog","article_published_time":"2026-08-31T17:01:11+00:00","article_modified_time":"2026-08-31T17:01:29+00:00","og_image":[{"width":1536,"height":864,"url":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp","type":"image\/webp"}],"author":"Vaibhav Sharma","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Vaibhav Sharma","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#article","isPartOf":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/"},"author":{"name":"Vaibhav Sharma","@id":"https:\/\/dianapps.com\/blog\/#\/schema\/person\/e0ee1e2a6cfb8681a3cc69154f8d8bcf"},"headline":"Salesforce Development for Healthcare: What Actually Needs Custom Building","datePublished":"2026-08-31T17:01:11+00:00","dateModified":"2026-08-31T17:01:29+00:00","mainEntityOfPage":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/"},"wordCount":1876,"commentCount":0,"image":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#primaryimage"},"thumbnailUrl":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp","keywords":["Salesforce for Healthcare"],"articleSection":["Salesforce"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/","url":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/","name":"Salesforce for Healthcare: What to Build, Extend & Avoid","isPartOf":{"@id":"https:\/\/dianapps.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#primaryimage"},"image":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#primaryimage"},"thumbnailUrl":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp","datePublished":"2026-08-31T17:01:11+00:00","dateModified":"2026-08-31T17:01:29+00:00","author":{"@id":"https:\/\/dianapps.com\/blog\/#\/schema\/person\/e0ee1e2a6cfb8681a3cc69154f8d8bcf"},"description":"Learn what to build, extend, and avoid in Salesforce for healthcare, including Health Cloud, FHIR, HIPAA, EHR integrations, custom portals, and costs.","breadcrumb":{"@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#primaryimage","url":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp","contentUrl":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/08\/Untitled-design-2026-08-31T163252.039.webp","width":1536,"height":864,"caption":"Salesforce Development for Healthcare"},{"@type":"BreadcrumbList","@id":"https:\/\/dianapps.com\/blog\/salesforce-development-for-healthcare\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dianapps.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Salesforce Development for Healthcare: What Actually Needs Custom Building"}]},{"@type":"WebSite","@id":"https:\/\/dianapps.com\/blog\/#website","url":"https:\/\/dianapps.com\/blog\/","name":"Learn About Digital Transformation &amp; Development | DianApps Blog","description":"Dianapps","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dianapps.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/dianapps.com\/blog\/#\/schema\/person\/e0ee1e2a6cfb8681a3cc69154f8d8bcf","name":"Vaibhav Sharma","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Vaibhav-Sharma-Salesforce-Specialist-96x96.jpg","url":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Vaibhav-Sharma-Salesforce-Specialist-96x96.jpg","contentUrl":"https:\/\/dianapps.com\/blog\/wp-content\/uploads\/2026\/07\/cropped-Vaibhav-Sharma-Salesforce-Specialist-96x96.jpg","caption":"Vaibhav Sharma"},"description":"A Salesforce specialist with over 15 years in the field, Vaibhav Sharma has built his career at the intersection of CRM strategy and enterprise transformation. As the driving force behind Salesforce innovation at DianApps, he architects solutions across Sales Cloud, Service Cloud, and Experience Cloud that turn fragmented customer data into unified growth engines. His work spans a 360-degree perspective in BFSI, healthcare, and retail, where he's known for engineering platforms that don't just go live, they move revenue and retention numbers. Vaibhav's edge lies in reading where Salesforce is headed next, from AI-powered automation, AgentExchange to Agentforce, and translating that foresight into roadmaps enterprise leaders can act on today.","url":"https:\/\/dianapps.com\/blog\/author\/vaibhav-sharma\/"}]}},"_links":{"self":[{"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/posts\/20755","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/comments?post=20755"}],"version-history":[{"count":1,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/posts\/20755\/revisions"}],"predecessor-version":[{"id":20770,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/posts\/20755\/revisions\/20770"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/media\/20769"}],"wp:attachment":[{"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/media?parent=20755"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/categories?post=20755"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dianapps.com\/blog\/wp-json\/wp\/v2\/tags?post=20755"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}