{"id":30999,"date":"2026-11-13T15:42:38","date_gmt":"2026-11-13T12:42:38","guid":{"rendered":"https:\/\/www.intellectsoft.net\/blog\/?p=30999"},"modified":"2026-11-13T15:44:02","modified_gmt":"2026-11-13T12:44:02","slug":"patient-portal-software-development","status":"publish","type":"post","link":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/","title":{"rendered":"Patient Portal Software Development: Features, EHR Integration, Cost and Timeline"},"content":{"rendered":"<h3><b>Key takeaways<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In patient portal software development, back-end work first: logins, permissions, and EHR feeds make up most of patient portal software.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Three routes (extend Epic MyChart or Oracle Health, buy a platform, or build custom), often mixed.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">US projects shaped by federal information blocking rules, CMS APIs, and Section 504; English ones by the NHS App.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repeat logins driven by fresh FHIR data and separate proxy accounts for family.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Integration, compliance, and enrollment costing more than the screens.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One weekly-use workflow first, then usage data to pick the next.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Patient portal software development used to sit near the bottom of a hospital IT roadmap. That&#8217;s changed. In 2024, 65% of people in the US logged in to a patient portal or online record, and <\/span><a href=\"https:\/\/www.healthit.gov\/data\/data-briefs\/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2024\"><span style=\"font-weight: 400;\">59% used more than one<\/span><\/a><span style=\"font-weight: 400;\">. In England, the NHS App now connects to every acute trust. In March 2026, <\/span><a href=\"https:\/\/england.nhs.uk\/2026\/04\/hospital-patients-can-now-check-appointments-in-the-nhs-app\/\"><span style=\"font-weight: 400;\">NHS England counted<\/span><\/a><span style=\"font-weight: 400;\"> 8.7 million hospital appointment views, up 93% from a year earlier.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Blame the banks. Once people could move money from a phone, waiting on hold to book a blood test started to feel absurd. Your patient portal doesn&#8217;t get them to itself, though. It sits next to every other healthcare app and front door they already have.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Below: portal types, the rules that rewrote the brief, core and AI features, EHR integration, US and UK compliance, cost, timeline, adoption. If you&#8217;re deciding between the EHR vendor&#8217;s portal, a platform, or your own build (maybe with a partner for <\/span><a href=\"https:\/\/www.intellectsoft.net\/healthcare\"><span style=\"font-weight: 400;\">healthcare IT solutions<\/span><\/a><span style=\"font-weight: 400;\">), start here.<\/span><\/p>\n<h2><b>What Is Patient Portal Software?<\/b><\/h2>\n<blockquote><p><span style=\"font-weight: 400;\">Patient portal software is the secure web and mobile app a healthcare provider, payer, or lab gives patients for everything that happens after a visit. Behind a login, they read a result, answer a nurse\u2019s message, settle a bill, or book the next appointment. Caregivers often do the same for them. The healthcare provider, payer, or lab runs it behind a secure login, on the web and in a mobile app. Behind the screens, the EHR supplies most of the data, and scheduling, billing, pharmacy, and imaging systems fill in the rest.<\/span><\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">Patient portal development is the whole job around it. Design and build, sure, but also integration and the years of running it that rarely make the first budget. It overlaps with general <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/web-portal-development\/\"><span style=\"font-weight: 400;\">web portal development<\/span><\/a><span style=\"font-weight: 400;\">. The stakes don&#8217;t. When a retail portal&#8217;s login breaks, somebody abandons a cart; in healthcare, it can block a patient from a biopsy result. Every rule from <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/healthcare-web-development\/\"><span style=\"font-weight: 400;\">healthcare web development<\/span><\/a><span style=\"font-weight: 400;\"> lands on the portal at once.<\/span><\/p>\n<h3><b>Types of patient portals<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Type<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What it is<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Best when<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Tethered EHR portal (e.g., Epic MyChart, Oracle Health)<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">The EHR vendor\u2019s portal, configured and branded by the provider<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">One EHR, standard workflows, limited product team<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Custom (standalone) portal<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Your own front end and backend, connected to one or more EHRs and other systems through APIs<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Several EHRs, specialty workflows, or the patient experience is the product<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Hybrid: custom front end on EHR APIs<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">A custom patient experience; the EHR stays the source of truth<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">You need a better or branded experience without replacing the EHR<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Specialty portals<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Billing, lab results, pharmacy refills, pediatric or caregiver access, clinical trials<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">One high-volume workflow is the main pain point<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>UK: services integrated with the NHS App<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Hospital or supplier services surfaced inside the NHS App through NHS login and national integrations<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Patient-facing services for NHS patients in England<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>Patient portal vs. patient engagement platform vs. personal health record<\/b><\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31005 size-full\" src=\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram.png\" alt=\"Patient access layer diagram\" width=\"1800\" height=\"1325\" srcset=\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram.png 1800w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-300x221.png 300w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-1024x754.png 1024w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-768x565.png 768w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-1536x1131.png 1536w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-600x442.png 600w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-450x331.png 450w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-access-layer-diagram-1000x736.png 1000w\" sizes=\"auto, (max-width: 1800px) 100vw, 1800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">A portal hangs off one provider&#8217;s records. Add outreach, education, and campaigns, and people start calling it an engagement platform. Personal health records work the other way round. The patient owns one and fills it from every place they&#8217;ve been treated.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Real projects mix these up. Most custom builds we scope end up as a portal with a layer of engagement features bolted to the side.<\/span><\/p>\n<h2><b>Why Patient Portal Requirements Have Changed<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">A patient portal launched five years ago was judged on whether a patient could log in and read a lab value. That bar has moved. Healthcare regulators now care how fast data leaves your systems. Payers publish their own APIs, and in England a national app is absorbing core hospital features.<\/span><\/p>\n<h3><b>US: more portals, more apps and enforced data access<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Nobody uses just one portal anymore. In 2024, 77% of people were offered online access, per ASTP\/ONC Data Brief No. 77. Back in 2022, half of them had more than one portal. Now it&#8217;s 59%. Apps took over, too: 57% reached their records through one, compared with 38% four years earlier.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Caregiving changed as well. In the same ONC survey, 51% said someone else had accessed their records for them, more than double the earlier 24%.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then there&#8217;s enforcement. On September 3, 2025, <\/span><a href=\"https:\/\/www.hhs.gov\/press-room\/hhs-crackdown-health-data-blocking.html\"><span style=\"font-weight: 400;\">HHS directed resources to active information blocking enforcement<\/span><\/a><span style=\"font-weight: 400;\">. Certified health IT developers and health information networks face civil money penalties of up to $1 million per violation. Providers face CMS disincentives instead. By early 2026, ASTP had started issuing notices of investigation to health IT developers, as <\/span><a href=\"https:\/\/hklaw.com\/en\/insights\/publications\/2026\/02\/the-wait-is-over-information-blocking-enforcement-is-officially-here\"><span style=\"font-weight: 400;\">Holland &amp; Knight summarized<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What does that mean for the build? Results and notes go out without unnecessary delay. And the patient portal needs an API that third-party apps can actually call.<\/span><\/p>\n<h3><b>US: APIs, apps and digital identity<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Payers have a hard date. Under <\/span><a href=\"https:\/\/www.cms.gov\/files\/document\/fact-sheet-cms-interoperability-and-prior-authorization-final-rule-cms-0057-f.pdf\"><span style=\"font-weight: 400;\">CMS-0057-F<\/span><\/a><span style=\"font-weight: 400;\">, impacted payers must add prior authorization information to the Patient Access API by January 1, 2027.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The voluntary <\/span><a href=\"https:\/\/www.cms.gov\/initiatives\/health-technology-ecosystem\/overview\/interoperability-framework\"><span style=\"font-weight: 400;\">CMS Interoperability Framework<\/span><\/a><span style=\"font-weight: 400;\"> pushes in the same direction. It defines CMS Aligned Networks and names patient-facing app categories, including &#8220;kill the clipboard&#8221; and conversational AI. Identity gets serious too. With an IAL2-level digital credential, a patient should reach their records without opening yet another portal account. The framework&#8217;s FHIR API, appointment notification, and record locator criteria took effect on July 4, 2026.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then there&#8217;s TEFCA. Through its Individual Access Services, a patient can pull their own records across networks with the app of their choice. About 464 million documents crossed TEFCA by the end of 2025, <\/span><a href=\"https:\/\/healthit.gov\/resources\/data-liquidity-affordability-and-access-the-history-growth-of-tefca\/\"><span style=\"font-weight: 400;\">ASTP reports<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">So design the patient portal to share data and identity with other apps. Not to keep each patient inside one login.<\/span><\/p>\n<h3><b>UK: the NHS App is the front door<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><a href=\"https:\/\/www.gov.uk\/government\/publications\/10-year-health-plan-for-england-fit-for-the-future\"><span style=\"font-weight: 400;\">10 Year Health Plan for England<\/span><\/a><span style=\"font-weight: 400;\">, published in July 2025, makes the NHS App the main digital front door to the health service. You can see the pace already. Every acute NHS trust is connected, and <\/span><a href=\"https:\/\/england.nhs.uk\/2026\/04\/hospital-patients-can-now-check-appointments-in-the-nhs-app\/\"><span style=\"font-weight: 400;\">NHS England says<\/span><\/a><span style=\"font-weight: 400;\"> 64% of hospital appointments now show in the app. Around half of trusts send push reminders through it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Under the <\/span><a href=\"https:\/\/digital.nhs.uk\/services\/nhs-app\/how-to-integrate-with-the-nhs-app\"><span style=\"font-weight: 400;\">NHS App integration guidance<\/span><\/a><span style=\"font-weight: 400;\">, suppliers plug in through NHS login. Referrals and appointments go through the Patient Care Aggregator (Wayfinder), messages through NHS Notify.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The direction shifted again in 2026. NHS England plans to deliver five core appointment features inside the NHS App itself. According to <\/span><a href=\"https:\/\/www.pslhub.org\/news\/%E2%80%98confusing%E2%80%99-nhs-app-functions-to-be-standardised-r9492\/\"><span style=\"font-weight: 400;\">reports of the plan<\/span><\/a><span style=\"font-weight: 400;\">, patient engagement portal suppliers won&#8217;t be needed for them within three years. Through NHS App Direct Integration, trusts will connect their EPRs to the app directly; the first trusts are already in development, <\/span><a href=\"https:\/\/digital.nhs.uk\/services\/referrals-and-appointments\/newsletters\/referrals-and-appointments-newsletter-august-2026\"><span style=\"font-weight: 400;\">NHS England Digital confirms<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The practical rule for England: build hospital and clinic services to plug into the NHS App, not to compete with it.<\/span><\/p>\n<h2><b>Core Features of Patient Portal Software<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Healthcare feature lists all look alike. Whether people use a portal or abandon it comes down to the plumbing. So these notes come from the build side.<\/span><\/p>\n<h3><b>What to launch first and what can wait<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Feature<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">MVP<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Later phases<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Registration, identity proofing, MFA<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">IAL2 digital credentials, passkeys<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Records, results, visit summaries<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Plain-language explanations, record download<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Secure messaging<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Routing rules, AI-drafted replies<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Scheduling and digital intake<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Self-scheduling for all visit types, check-in<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Billing and payments<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes (statements, online payment)<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Payment plans, cost estimates<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Proxy and caregiver access<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Adolescent and shared-care rules<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Prescription refills<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Optional<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Pharmacy integration<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Telehealth and remote monitoring<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Optional<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Device data, care plans<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Notifications<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Yes (email\/SMS)<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Push; NHS Notify in the UK<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Admin console and analytics<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Basic<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Adoption dashboards<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>Registration, identity proofing and login<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Enrollment leaks worst of all, and plenty of patient sign-ups die there. Proofing can happen in person at the front desk or remotely with a document check. Aim for IAL2, because the credential then works elsewhere. Add MFA and passkeys from day one.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Account recovery deserves its own design review. Date of birth plus zip code over the phone? That&#8217;s a gift to social engineers. Teams in England get a shortcut here: NHS login already verifies patient identity, and you inherit it.<\/span><\/p>\n<h3><b>Proxy and caregiver access<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Half the people reading medical records aren&#8217;t the patient. ASTP\/ONC data puts proxy access at 51% in 2024. Edge case? Hardly.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Every proxy gets a separate account, scoped to what they&#8217;re allowed to see, because shared passwords are how proxy access goes wrong. Teen confidentiality is messier. State laws differ, so get the permission model past a lawyer before any developer touches it. In the UK, parents and carers already have proxy links in the NHS App.\u00a0<\/span><\/p>\n<h3><b>Records, results and visit summaries<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">USCDI is the floor for what the medical record view shows: problems, medications, allergies, labs, notes. Thanks to information blocking rules, results and clinical notes go out without unnecessary delay. That includes the awkward ones. (A pathology report nobody has discussed with the patient yet, for instance.) Add visit summaries, record download, and sharing to another app.<\/span><\/p>\n<h3><b>Secure messaging<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Building messaging takes a sprint or two. Running it costs clinician hours every single day. Route messages to a team pool, not one doctor&#8217;s inbox. And tell the patient how long replies take, in plain words. Scan attachments for malware; patients upload some strange files. Notification text should never carry clinical detail; &#8220;You have a new message&#8221; is enough.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Some healthcare organizations bill the longer threads as e-visits. Billing uses CPT 99421\u201399423, and <\/span><a href=\"https:\/\/www.mgma.com\/mgma-stat\/ensuring-accurate-coding-and-billing-for-patient-portal-messages-as-e-visits\"><span style=\"font-weight: 400;\">MGMA&#8217;s guide<\/span><\/a><span style=\"font-weight: 400;\"> covers the details.<\/span><\/p>\n<h3><b>Scheduling, digital intake and check-in<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Self-scheduling pulls open slots from the EHR in real time. Cached slots mean double bookings, and after about a week of those the front desk quietly goes back to the phone. CMS calls this &#8220;kill the clipboard.&#8221; In a clinic, that looks like a waitlist, intake forms done at home, and an insurance card photo uploaded the night before. Reminders tend to come from a <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/healthcare-crm-development\/\"><span style=\"font-weight: 400;\">healthcare CRM<\/span><\/a><span style=\"font-weight: 400;\"> that shares the patient record.<\/span><\/p>\n<h3><b>Billing and payments<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Patient billing portal web development is a common first phase, because finance teams see the return quickly. The first release usually covers statements and online payment through a tokenized PCI DSS processor; payment plans and cost estimates follow. Card data never touches your servers.<\/span><\/p>\n<h3><b>Prescription refills<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A refill request lands in a clinician queue first. Never the pharmacy directly. Pharmacy choice belongs to the patient. Medication lists sync from the EHR. If a doctor discontinued a drug last month, the patient won&#8217;t see a refill button for it.<\/span><\/p>\n<h3><b>Telehealth and remote monitoring<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Video visits launch from the appointment itself. No separate link buried in an email. Glucose meters and blood pressure cuffs at home can upload readings too. The care team picks the alert thresholds, so nurses only see the numbers that need attention. Much of this is ordinary <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/telemedicine-app-development\/\"><span style=\"font-weight: 400;\">telemedicine app development<\/span><\/a><span style=\"font-weight: 400;\">. So, reuse it.<\/span><\/p>\n<h3><b>Notifications<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Keep notification content to the bare minimum. US teams get a BAA from every SMS and email vendor before the first send. UK services use NHS Notify.<\/span><\/p>\n<h3><b>Admin console and analytics<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Staff need role-based admin access, content updates without a release, and audit logs they can actually search. The adoption dashboards are covered in the adoption section below.<\/span><\/p>\n<h2><b>AI Features in Patient Portal Software<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">AI is worth adding to a healthcare portal where it saves staff time. Clinical decisions stay with clinicians. Buyers will ask. The CMS framework lists conversational AI as a patient-facing app category, after all. Here&#8217;s where it tends to pay off, and where <\/span><a href=\"https:\/\/www.intellectsoft.net\/ai\/development\"><span style=\"font-weight: 400;\">AI development services<\/span><\/a><span style=\"font-weight: 400;\"> need the tightest guardrails.<\/span><\/p>\n<h3><b>Drafted replies to patient messages<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The model drafts a reply in the clinician&#8217;s inbox. A clinician edits it and hits send. Nothing clinical goes out automatically.<\/span><\/p>\n<h3><b>Plain-language results and notes<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Picture a lab value with a short plain-language explanation underneath, a link to the original, and a prompt to call the care team. Our bet: fewer patient calls asking what &#8220;mildly elevated ALT&#8221; means.<\/span><\/p>\n<h3><b>Conversational scheduling and navigation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A patient types &#8220;Can I come in Thursday?&#8221; and the bot offers real slots from live availability. Billing and parking questions go through the same chat. Anything past the bot&#8217;s depth goes to a person. Running <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/chatbots-in-healthcare\/\"><span style=\"font-weight: 400;\">chatbots in healthcare<\/span><\/a><span style=\"font-weight: 400;\"> already? That stack can usually stretch.<\/span><\/p>\n<h3><b>Intake and document processing<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Forms arrive half-filled from the last visit. Upload a referral letter or snap an insurance card, and the fields get extracted for staff to check; nothing reaches the chart unchecked.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">None of this works without guardrails. A clinician signs off on anything clinical. We log prompts and outputs as PHI, same as any other record access. Contracts matter too: a BAA with the model provider in the US, a data processing agreement in the UK. Accuracy and bias testing happen before launch, and AI-written text carries a label. Does a feature start hinting at diagnoses? Then read the <\/span><a href=\"https:\/\/www.fda.gov\/regulatory-information\/search-fda-guidance-documents\/clinical-decision-support-software\"><span style=\"font-weight: 400;\">FDA&#8217;s clinical decision support software guidance<\/span><\/a><span style=\"font-weight: 400;\">, last updated in January 2026.<\/span><\/p>\n<h2><b>Patient Portal Software Development in Practice: A Booking and Intake Platform for UK Dental Clinics<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Not every patient portal starts with an EHR. This one started with a dental startup that wanted to take the phone out of booking.<\/span><\/p>\n<h3><b>The challenge<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A UK dental startup needed one platform for clinics, dentists, and patients. The founders wanted patients to book without calling anyone. A patient would pick a dentist and a free slot online. Clinic staff would then see every request and form in one queue, rather than spread across phone calls and emails.<\/span><\/p>\n<h3><b>The solution<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">We built a white-label web platform for both sides of the appointment. Patients get a responsive mobile version, while clinic administrators work in a panel where access depends on their role. Under it sit React.js, .NET Core 3.1, and AWS, with fully automated CI\/CD and a domain-driven design approach.<\/span><\/p>\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">User<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What they can do<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Patients<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Choose a dentist, book appointments, fill out questionnaires, upload photos, submit and cancel requests<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Clinic staff (administrators and dentists)<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Create administrator and dentist profiles, handle appointments and requests, view patient statistics; access depends on role<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><b>The results<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Development took 9 months. Ten clinics now run on the platform. Our team measured about 20% less administrator time per patient, and revenue grew by an average of 8% through better appointment management.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The full story is in our case study on the <\/span><a href=\"https:\/\/www.intellectsoft.net\/cases\/client-management-platform-for-dental-clinics\"><span style=\"font-weight: 400;\">client management platform for dental clinics<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h2><b>Patient Portal Adoption in Practice: A Patient Web Portal for a US Healthcare Company<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Adoption is the number most portal projects get wrong. This one surprised everybody.<\/span><\/p>\n<h3><b>The challenge<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The customer, a US company, provides decision-support solutions to consumers and healthcare professionals. Its audience was getting older. Many of those users already managed care through patient portals and electronic health records, so the company wanted one trusted place for health information.<\/span><\/p>\n<h3><b>The solution<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Episerver CMS sits under the patient portal. That let the customer&#8217;s own team edit articles, swap images, and change static pages without a developer recompiling the app. On the patient side, the portal pulled together medical articles, drug and symptom references, news, illustrations, videos, and health tips. There was also a drug lookup that worked by symptom, pill shape, color, or imprint. The portal linked into the customer&#8217;s main website and marketing campaigns. Our team handled the whole cycle, from design and development to testing, deployment, and maintenance.<\/span><\/p>\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">User<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What the portal gives them<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Patients<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Medical articles, drug and symptom information, news, illustrations, videos, and health tips in one place; drug search by symptom, shape, color, or imprint<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Content and site owners<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Content, image, and page updates through the CMS without code changes or releases<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Marketing team<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">A portal connected to the main website and campaigns, supporting branding and targeted advertising<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><b>The results<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The portal turned out &#8220;extremely popular with patients&#8221; and saw &#8220;surprisingly-high adoption among older patients.&#8221; It took work off hospital staff. The case also notes that patients started taking a more active part in managing their health. What we took from the project is fairly simple. Older patients stuck with the portal because they found things quickly and believed the content, and that counted for more than extra features. Read the full <\/span><a href=\"https:\/\/www.intellectsoft.net\/cases\/patient-web-portal\"><span style=\"font-weight: 400;\">patient web portal<\/span><\/a><span style=\"font-weight: 400;\"> case.<\/span><\/p>\n<h2><b>EHR Integration and Interoperability for Patient Portals<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Ask any healthcare team that&#8217;s shipped a portal where the budget went. Integration, almost always, and mostly because the paperwork started late. Epic and Oracle Health both publish FHIR R4 APIs, and most healthcare networks we talk to run one of them. Through those APIs the portal reads records and books appointments back into the schedule. The lab system is often the odd one out. If it only sends HL7 v2, we route it through an integration engine first. For nurses who open the portal from inside the EHR, SMART on FHIR passes along the patient already on screen.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The slow part is human. App review and API approval at the EHR vendor can drag on longer than several sprints. We put them on the critical path from discovery. In the UK, it&#8217;s NHS login plus whichever NHS App routes apply. NHS App Direct Integration will change that list for trusts. Teams doing deeper <\/span><a href=\"https:\/\/www.intellectsoft.net\/healthcare\/ehr-emr\"><span style=\"font-weight: 400;\">EHR and EMR development<\/span><\/a><span style=\"font-weight: 400;\"> work run these tracks in parallel.<\/span><\/p>\n<h3><b>Standards and services a patient portal works with<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Standard \/ service<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Market<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What it is used for<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">When your portal needs it<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>FHIR R4 (US Core \/ UK Core)<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Both<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">REST APIs for clinical and administrative data<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Reading or writing EHR data: results, records, appointments<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>USCDI<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">US<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">The minimum data classes patients must be able to access<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Deciding what the records view shows<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>SMART on FHIR<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">US (mainly)<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Secure app authorization and launch with patient context<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Third-party app access; launching from the EHR<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>HL7 v2<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Both<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Event messages: admissions, orders, results<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Real-time feeds from systems without FHIR<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>CMS payer FHIR APIs<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">US<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Patient Access API, including prior authorization data by January 1, 2027<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Payer portals and member apps<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>TEFCA Individual Access Services<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">US<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Patient-requested record retrieval across networks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Pulling records from other providers<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>X12 270\/271<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">US<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Insurance eligibility checks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Intake and cost estimates<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>NHS login<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">UK<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Verified patient identity and single sign-on with the NHS App<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Any patient-facing service for NHS patients in England<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Patient Care Aggregator (Wayfinder)<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">UK<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Hospital referrals and appointments in the NHS App<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Secondary care booking and appointment management<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>NHS Notify<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">UK<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Messages and push notifications through the NHS App<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Reminders and letters<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>PDS \/ GP Connect \/ IM1<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">UK<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Demographics and NHS number; GP records and appointments<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Patient matching; primary care data<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>Integrating with more than one EHR<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">We see custom patient portal development pay off fastest in healthcare networks running two or three EHRs, for example after a merger. We&#8217;d put one integration layer with a canonical FHIR data model in the middle, so the portal stops caring which EHR answers. Patient matching across those systems needs its own component: usually an enterprise master patient index, or the NHS number from PDS on UK projects. One identity per patient. Each vendor&#8217;s approval process gets its own plan, since no two behave alike.<\/span><\/p>\n<h2><b>Compliance and Security Requirements in the US and UK<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">On our projects, a person who knows HIPAA or NHS assurance joins the first design workshop. Leaving that review to the end tends to mean redrawing screens a few weeks before launch.<\/span><\/p>\n<h3><b>US vs UK requirements at a glance<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Area<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">United States<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">United Kingdom<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Data protection law<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">HIPAA Privacy and Security Rules, HITECH; state privacy and minor-consent laws<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">UK GDPR and Data Protection Act 2018 (health data is special category data)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Vendor contracts<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">BAA with every vendor that touches PHI (cloud, SMS, video, analytics, AI)<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Data processing agreement with every processor<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Patient data access<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">21st Century Cures Act information blocking rules; patient right of access<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Subject access rights; NHS App integration standards<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Identity<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Identity proofing (IAL2 under the CMS framework), MFA<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">NHS login<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Accessibility<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">HHS Section 504 rule: WCAG 2.1 AA by May 11, 2027 (15+ employees) and May 10, 2028 (smaller)<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">WCAG 2.2 AA for public sector bodies, including the NHS; Equality Act 2010<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Tracking<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">No third-party tracking with PHI on authenticated pages<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">PECR consent for non-essential cookies<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Buyer assurance<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Security questionnaires; SOC 2 \/ HITRUST often requested<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">DTAC, DSPT, DCB0129 \/ DCB0160 clinical safety<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>US: HIPAA and the Security Rule update<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">PHI is broader than most product teams expect. Under HIPAA it covers almost any patient portal screen, right down to an appointment list showing a name. Each vendor that stores or processes it signs a BAA with you. You also keep a written risk analysis and audit logs of who opened each patient record.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The Security Rule itself is mid-rewrite. The <\/span><a href=\"https:\/\/www.hhs.gov\/hipaa\/for-professionals\/security\/hipaa-security-rule-nprm\/factsheet\/index.html\"><span style=\"font-weight: 400;\">proposed rule<\/span><\/a><span style=\"font-weight: 400;\"> HHS published in January 2025 reads like a security team&#8217;s wish list. MFA and encryption would become required rather than recommended. The draft also asks for a current asset inventory, a penetration test every 12 months, and restoring critical systems within 72 hours. It isn&#8217;t final. HHS&#8217;s <\/span><a href=\"https:\/\/www.reginfo.gov\/public\/do\/eAgendaViewRule?pubId=202510&amp;RIN=0945-AA22\"><span style=\"font-weight: 400;\">regulatory agenda<\/span><\/a><span style=\"font-weight: 400;\"> now points to around July 2027. Still, treat MFA and encryption as required in any new build.<\/span><\/p>\n<h3><b>US: information blocking, tracking and accessibility<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Results and notes go out without unnecessary delay, and if you lean on an exception, write down which one. Tracking pixels behind the login are how PHI ends up in ad platforms. Take them off every authenticated page.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Section 504 gives organizations with 15 or more employees until May 11, 2027, a date <\/span><a href=\"https:\/\/www.hhs.gov\/press-room\/hhs-extends-mobile-and-web-accessibility-deadline.html\"><span style=\"font-weight: 400;\">HHS set in May 2026<\/span><\/a><span style=\"font-weight: 400;\">. Anyone smaller gets another year, to May 10, 2028. WCAG 2.1 AA is the bar either way. We&#8217;d build to WCAG 2.2 AA to cover both markets.<\/span><\/p>\n<h3><b>UK: UK GDPR, NHS assurance and NHS App standards<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">UK GDPR basics go first. Before any health data moves, there&#8217;s a DPIA to write, a lawful basis to pick, and an Article 9 condition to name. Then the NHS buyer sends over DTAC. The form is <\/span><a href=\"https:\/\/innovation.nhs.uk\/news\/updated-nhs-england-digital-technology-assessment-criteria-dtac-form-and-guidance\/\"><span style=\"font-weight: 400;\">shorter since March 2026<\/span><\/a><span style=\"font-weight: 400;\">, because NHS England removed the questions that repeated the DSPT. If you touch NHS patient data, the DSPT itself is on you.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Two <\/span><a href=\"https:\/\/digital.nhs.uk\/services\/clinical-safety\/clinical-risk-management-standards\"><span style=\"font-weight: 400;\">clinical risk management standards<\/span><\/a><span style=\"font-weight: 400;\"> apply. On our side, DCB0129 applies while we build the product. DCB0160 then applies to the trust or clinic as it rolls the system out. Going into the NHS App adds two more items: NHS login, and a review against the app&#8217;s accessibility, usability, clinical safety, and data privacy standards.<\/span><\/p>\n<h3><b>Security controls every patient portal needs<\/b><\/h3>\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Control<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What it covers<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Encryption<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">In transit (TLS 1.2+) and at rest, including backups, logs, and exports<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Authentication<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">MFA, passkeys, session timeouts, safe account recovery; NHS login in the UK<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Authorization<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Role- and relationship-based access: patient, proxy, adolescent, staff; minimum necessary data<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Audit logging<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Every view, change, and download of patient data, by user and time; immutable and reviewable<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Vendors and hosting<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">BAAs (US) \/ data processing agreements (UK); data residency as required<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Testing<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">SAST\/DAST, dependency scanning, independent penetration test before launch and annually<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><b>Patient Portal Development Process: Step by Step<\/b><\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31017 size-full\" src=\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process.png\" alt=\"Patient Portal Development Process\" width=\"1800\" height=\"831\" srcset=\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process.png 1800w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-300x139.png 300w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-1024x473.png 1024w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-768x355.png 768w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-1536x709.png 1536w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-600x277.png 600w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-450x208.png 450w, https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Development-Process-1000x462.png 1000w\" sizes=\"auto, (max-width: 1800px) 100vw, 1800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">We&#8217;ve marked the compliance work US and UK healthcare buyers will ask about in each step.<\/span><\/p>\n<h3><b>Step 1: Discovery, workflow mapping and compliance scoping<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Our first workshop is mostly questions. Who will log in: patients, proxies, staff? What goes digital first? Where does patient data travel? US teams begin the HIPAA risk analysis here. UK teams scope the DPIA, DTAC, and DCB0129 work.<\/span><\/p>\n<h3><b>Step 2: Build, buy or extend decision and EHR access<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Confirm the approach against what discovery found. Request EHR sandbox access the same week and file the vendor app review on day one. Waiting until design is done costs months.<\/span><\/p>\n<h3><b>Step 3: UX design with patients, caregivers and staff<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">We put clickable prototypes in front of older patients, adult children managing a parent&#8217;s care, and the people at the front desk. They&#8217;ll find in a minute what the product team missed for weeks. Accessibility and plain language are cheap to add at this point and painful to retrofit. When we run <\/span><a href=\"https:\/\/www.intellectsoft.net\/services\/ui-ux-design-services\"><span style=\"font-weight: 400;\">UI\/UX design services<\/span><\/a><span style=\"font-weight: 400;\"> for healthcare, screen-reader users are part of testing.<\/span><\/p>\n<h3><b>Step 4: Architecture, identity and integration design<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Identity and proxy model come first, since nearly everything else hangs off them. After that come FHIR and HL7 patterns and hosting (under a BAA in the US, in UK regions for NHS work).<\/span><\/p>\n<h3><b>Step 5: MVP development in sprints<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">We&#8217;d rather see one high-value workflow fully working than three half-done. Good first pairings are results plus messaging or booking plus intake. With an <\/span><a href=\"https:\/\/www.intellectsoft.net\/services\/mvp-development\"><span style=\"font-weight: 400;\">MVP development<\/span><\/a><span style=\"font-weight: 400;\"> scope that small, real users arrive within months, and their clicks decide the next release.<\/span><\/p>\n<h3><b>Step 6: Security, accessibility and integration testing<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Before launch, we pay someone to try to break in. Someone else works through it with a screen reader for the WCAG audit. And the whole thing runs against the EHR sandbox. UK teams also need their clinical safety case signed off. We hand these checks to an independent <\/span><a href=\"https:\/\/www.intellectsoft.net\/services\/qa-and-software-testing-services\"><span style=\"font-weight: 400;\">QA and software testing<\/span><\/a><span style=\"font-weight: 400;\"> team. Developers rarely spot gaps in code they wrote last week.<\/span><\/p>\n<h3><b>Step 7: Launch, enrollment and continuous improvement<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Go live in stages. One clinic or service line first. Front-desk staff get a short patient portal enrollment script, and the team watches activation and drop-off in analytics before each release. In our experience, healthcare budgets cut this stage of patient portal development first, and it&#8217;s where many portals stall.<\/span><\/p>\n<h2><b>How Much Does Patient Portal Software Cost?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Patient portal software cost depends far more on healthcare integrations and compliance than on screens. Our <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/web-app-development-costs\/\"><span style=\"font-weight: 400;\">web app development costs<\/span><\/a><span style=\"font-weight: 400;\"> guide puts healthcare web apps at $100,000\u2013$300,000+. Mid-sized portals usually cost $50,000\u2013$150,000. On our projects, compliance adds another 15\u201330%, and maintenance takes 15\u201325% of the build cost every year.<\/span><\/p>\n<h3><b>Indicative patient portal cost by scope<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Scope<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">US<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">UK<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What moves the number<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>MVP: one workflow (e.g., booking and intake, or results and messaging), one EHR<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">$50,000\u2013$100,000<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">\u00a340,000\u2013\u00a380,000<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Number of roles; one or two integrations<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Full patient portal with EHR integration<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">$100,000\u2013$300,000+<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">\u00a380,000\u2013\u00a3240,000+<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">FHIR\/HL7 depth, proxy access, billing, telehealth, mobile apps; NHS login (UK)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Multi-EHR or multi-organization platform, or a commercial product<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">$300,000+<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">\u00a3240,000+<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Several EHRs, payer or national APIs, patient matching, scale<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Extending the EHR vendor portal<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Vendor licensing + configuration<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">n\/a for NHS App services<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Vendor pricing; integrations still cost extra<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Compliance overhead<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">+15\u201330%<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">+15\u201330%<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">HIPAA controls and BAAs (US); DPIA, DTAC, DSPT, DCB0129 (UK); penetration testing<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Maintenance per year<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">15\u201325% of build cost<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">15\u201325% of build cost<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Releases, security patches, EHR upgrades, support<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><span style=\"font-weight: 400;\">The biggest cost drivers are predictable. EHR integrations top the list. Identity proofing, proxy rules, billing, and telehealth follow, roughly in that order for most of the projects we scope. Adding native iOS and Android apps means a second front end to build and maintain. That&#8217;s a common reason <\/span><a href=\"https:\/\/www.intellectsoft.net\/healthcare\/app-development\"><span style=\"font-weight: 400;\">healthcare app development<\/span><\/a><span style=\"font-weight: 400;\"> budgets grow. Accessibility work and data migration from an old portal cost less, but they rarely cost nothing. A custom patient portal development plan should also allow time for EHR vendor approvals, which your team can&#8217;t speed up. UK projects add NHS login and NHS App onboarding.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">After launch, plan for hosting, identity checks, SMS fees, licenses, an annual security test, and someone to answer patients&#8217; questions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">These are estimates from our projects, so your own scope will shift them. UK figures exclude VAT.<\/span><\/p>\n<h2><b>How Long Does Patient Portal Development Take?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Most patient portals take 4\u20138 months to a first production release. MVPs land in 2\u20134 months. Enterprise platforms take 8\u201318. These timeline ranges come from our web portal development guide, plus healthcare-specific delays.<\/span><\/p>\n<h3><b>Patient portal timeline by scope<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Scope<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Typical timeline<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Extra time for UK \/ NHS work<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What sets the pace<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>MVP: one workflow, one EHR<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">2\u20134 months<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">+2\u20136 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">EHR sandbox access; number of roles<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Full patient portal with EHR integration<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">4\u20138 months<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">+1\u20133 months<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Vendor app review, identity proofing, proxy rules; NHS login and NHS App onboarding (UK)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Multi-EHR or multi-organization platform<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">8\u201318 months<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Plan per integration<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Several EHRs, patient matching, phased rollout<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>Where the time goes<\/b><\/h3>\n<div style=\"overflow-x: auto; -webkit-overflow-scrolling: touch;\">\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Phase<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Typical duration<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">Patient-portal-specific note<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Discovery and compliance scoping<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">2\u20134 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Request EHR sandbox and vendor review here<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>UX design<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">3\u20135 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Test with patients, caregivers, and staff; accessibility review<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Architecture and tech stack<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">2\u20133 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Lock identity, proxy, and integration patterns<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Iterative development<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">3\u20136 months<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Integration runs in parallel, not at the end<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>QA, security testing, and UAT<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">3\u20136 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Penetration test, WCAG audit; clinical safety case (UK)<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Launch and hypercare<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">2\u20134 weeks<\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Pilot with one clinic or service line first<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><b>What slows patient portal projects down<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">In our projects, delays usually come from the same few places:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EHR vendor access and app review: file in week one of discovery.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Identity proofing vendor selection: have two finalists before architecture begins.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Legal review of proxy and adolescent rules: book counsel time in the first month.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BAAs (US) or data processing agreements (UK): send templates to every vendor in week one.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Your own security team&#8217;s review: get their questionnaire before anyone signs.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NHS login and NHS App onboarding (UK): apply the moment scope is settled.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Accessibility found late: audit the prototype, not just the release candidate.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">We&#8217;ve written separately about <\/span><a href=\"https:\/\/www.intellectsoft.net\/blog\/how-long-does-it-take-to-make-an-app\/\"><span style=\"font-weight: 400;\">how long it takes to build an app<\/span><\/a><span style=\"font-weight: 400;\"> outside healthcare. Here, plan around the slowest outside dependency.<\/span><\/p>\n<h2><b>How to Drive Patient Portal Adoption<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">One finding matters more than any feature. When providers encouraged them, 87% of people used a portal in 2024, <\/span><a href=\"https:\/\/www.healthit.gov\/data\/data-briefs\/individuals-access-and-use-patient-portals-and-smartphone-health-apps-2024\"><span style=\"font-weight: 400;\">ONC found<\/span><\/a><span style=\"font-weight: 400;\">, against 57% of those who got no nudge.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">So adoption is mostly an operations problem for healthcare teams. Ask at check-in. Most people are holding a phone anyway, so the activation text can go out before they sit down. If a daughter or son came along, set up their proxy access then and there. Offer the portal in the languages your patients speak at home; an English-only version loses those families. Front-desk staff do better with one sentence they repeat at every visit than with a stack of leaflets on the counter. In the UK, NHS login gives people one sign-in across services.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Track these from launch day, against your own baseline rather than someone else&#8217;s benchmark.<\/span><\/p>\n<h3><b>Patient portal KPIs to track<\/b><\/h3>\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #d0d5dd; font-size: 14px; margin-bottom: 24px;\">\n<thead>\n<tr>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">KPI<\/th>\n<th style=\"border: 1px solid #d0d5dd; padding: 8px 10px; text-align: left; vertical-align: top;\">What it shows<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Activation rate (accounts activated \u00f7 patients invited)<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Whether enrollment works<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Monthly active users<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Whether patients come back<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Self-scheduled appointment share<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Load taken off the phone line<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Digital intake completion rate<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Paperwork removed before the visit<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Online payment share and days to payment<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Billing impact<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Message volume and response time<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Care team workload and service level<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>No-show rate<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Effect of reminders and self-rescheduling<\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\"><strong>Proxy accounts<\/strong><\/td>\n<td style=\"border: 1px solid #d0d5dd; padding: 8px 10px; vertical-align: top;\">Caregiver reach<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><b>Common Patient Portal Development Challenges<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Six problems show up across healthcare projects again and again. None is a technical mystery.<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Low adoption.<\/b><span style=\"font-weight: 400;\"> Launch day comes, and the patient portal sits empty. Enrollment at check-in fixes most of it, along with staff who mention the portal at every visit.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>EHR vendor approval delays.<\/b><span style=\"font-weight: 400;\"> We&#8217;ve seen finished builds wait on app review for weeks. File it during discovery.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Proxy and adolescent access rules.<\/b><span style=\"font-weight: 400;\"> Rules shift by state and by family situation. Legal approves the permission model before anyone codes it.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Message overload for clinicians.<\/b><span style=\"font-weight: 400;\"> In an <\/span><a href=\"https:\/\/www.mgma.com\/mgma-stat\/ensuring-accurate-coding-and-billing-for-patient-portal-messages-as-e-visits\"><span style=\"font-weight: 400;\">MGMA poll<\/span><\/a><span style=\"font-weight: 400;\">, 70% of medical groups reported more portal messages in 2024. Routing rules help. So do published response times and AI-drafted replies.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Patient data leaking into analytics.<\/b><span style=\"font-weight: 400;\"> Pixels behind the login quietly ship PHI to ad platforms. First-party analytics does the job without the leak.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Duplicate portals and accounts.<\/b><span style=\"font-weight: 400;\"> Patients already juggle several logins. In the UK, the risk is building what the NHS App already provides or will soon absorb. Check NHS England&#8217;s roadmap before scoping any appointment feature.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Good patient portal development solutions plan for all six up front.<\/span><\/p>\n<h2><b>Patient Portal Software Development with Intellectsoft<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Intellectsoft has been doing <\/span><a href=\"https:\/\/www.intellectsoft.net\/healthcare\/software-development\"><span style=\"font-weight: 400;\">healthcare software development<\/span><\/a><span style=\"font-weight: 400;\"> since 2007: patient-facing portals, EHR and EMR systems, healthcare apps. We open every engagement with an architecture sprint. A portal&#8217;s identity model and integration layer are painful to change later, so they get decided first. A senior architect stays on the project from discovery to launch.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Two appear in this guide: a booking platform used by ten UK dental clinics and a US health portal popular with older patients.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our patient portal software development services cover discovery, UX, FHIR and HL7 integration, healthcare compliance work for HIPAA or the NHS, and support after launch. As a patient portal software development company, we stay mid-size on purpose. That keeps senior people close to each project. If you&#8217;re weighing a patient portal development company against your EHR vendor&#8217;s portal, we&#8217;ll say which fits, even when it&#8217;s the vendor&#8217;s.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our patient portal development services also include audits of existing portals that aren&#8217;t getting used.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Key takeaways In patient portal software development, back-end work first: logins, permissions, and EHR feeds make up most of patient portal software. Three routes (extend&#8230;<\/p>\n","protected":false},"author":92,"featured_media":31045,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[877,6],"tags":[],"class_list":["post-30999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare","category-software-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Patient Portal Software Development: Features &amp; Cost | Intellectsoft<\/title>\n<meta name=\"description\" content=\"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patient Portal Software Development: Features &amp; Cost | Intellectsoft\" \/>\n<meta property=\"og:description\" content=\"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/\" \/>\n<meta property=\"og:site_name\" content=\"Intellectsoft Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T12:42:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-13T12:44:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Vasylyna Kalinina\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Vasylyna Kalinina\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"25 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/\",\"url\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/\",\"name\":\"Patient Portal Software Development: Features & Cost | Intellectsoft\",\"isPartOf\":{\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg\",\"datePublished\":\"2026-11-13T12:42:38+00:00\",\"dateModified\":\"2026-11-13T12:44:02+00:00\",\"author\":{\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/f7ff0943b656fd88a7c27d5ff9bec769\"},\"description\":\"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage\",\"url\":\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg\",\"contentUrl\":\"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg\",\"width\":1672,\"height\":941,\"caption\":\"Patient Portal Software Development\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.intellectsoft.net\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patient Portal Software Development: Features, EHR Integration, Cost and Timeline\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/#website\",\"url\":\"https:\/\/www.intellectsoft.net\/blog\/\",\"name\":\"Intellectsoft Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.intellectsoft.net\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/f7ff0943b656fd88a7c27d5ff9bec769\",\"name\":\"Vasylyna Kalinina\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3220bbd5c31625e9af424209e8402055fd0b3c09b25abe5ca1d932add87d26db?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3220bbd5c31625e9af424209e8402055fd0b3c09b25abe5ca1d932add87d26db?s=96&d=mm&r=g\",\"caption\":\"Vasylyna Kalinina\"},\"sameAs\":[\"https:\/\/www.intellectsoft.net\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Patient Portal Software Development: Features & Cost | Intellectsoft","description":"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/","og_locale":"en_US","og_type":"article","og_title":"Patient Portal Software Development: Features & Cost | Intellectsoft","og_description":"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.","og_url":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/","og_site_name":"Intellectsoft Blog","article_published_time":"2026-11-13T12:42:38+00:00","article_modified_time":"2026-11-13T12:44:02+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg","type":"image\/jpeg"}],"author":"Vasylyna Kalinina","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Vasylyna Kalinina","Est. reading time":"25 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/","url":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/","name":"Patient Portal Software Development: Features & Cost | Intellectsoft","isPartOf":{"@id":"https:\/\/www.intellectsoft.net\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage"},"image":{"@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg","datePublished":"2026-11-13T12:42:38+00:00","dateModified":"2026-11-13T12:44:02+00:00","author":{"@id":"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/f7ff0943b656fd88a7c27d5ff9bec769"},"description":"Patient portal software development explained: build vs buy, core features, EHR and FHIR integration, HIPAA and NHS requirements, cost and timeline.","breadcrumb":{"@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#primaryimage","url":"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg","contentUrl":"https:\/\/www.intellectsoft.net\/blog\/wp-content\/uploads\/Patient-Portal-Software-Development.jpg","width":1672,"height":941,"caption":"Patient Portal Software Development"},{"@type":"BreadcrumbList","@id":"https:\/\/www.intellectsoft.net\/blog\/patient-portal-software-development\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.intellectsoft.net\/blog\/"},{"@type":"ListItem","position":2,"name":"Patient Portal Software Development: Features, EHR Integration, Cost and Timeline"}]},{"@type":"WebSite","@id":"https:\/\/www.intellectsoft.net\/blog\/#website","url":"https:\/\/www.intellectsoft.net\/blog\/","name":"Intellectsoft Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.intellectsoft.net\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/f7ff0943b656fd88a7c27d5ff9bec769","name":"Vasylyna Kalinina","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intellectsoft.net\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3220bbd5c31625e9af424209e8402055fd0b3c09b25abe5ca1d932add87d26db?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3220bbd5c31625e9af424209e8402055fd0b3c09b25abe5ca1d932add87d26db?s=96&d=mm&r=g","caption":"Vasylyna Kalinina"},"sameAs":["https:\/\/www.intellectsoft.net\/"]}]}},"_links":{"self":[{"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/posts\/30999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/users\/92"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/comments?post=30999"}],"version-history":[{"count":1,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/posts\/30999\/revisions"}],"predecessor-version":[{"id":31048,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/posts\/30999\/revisions\/31048"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/media\/31045"}],"wp:attachment":[{"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/media?parent=30999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/categories?post=30999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intellectsoft.net\/blog\/wp-json\/wp\/v2\/tags?post=30999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}