Skip to content
/// SECTOR / HEALTHCARE

HEALTHCARE WEB DEVELOPMENT. BUILT FOR THE COMPLIANCE REVIEW.

Websites and patient-facing systems for practices, clinics, and health technology companies — where how you handle protected health information is an architectural decision, not a checkbox someone ticks the week before launch.

/// KNOWN FAILURE MODE

THE FORM THAT EMAILS PHI

The most common thing we find on a healthcare site built by a general agency is a contact form that asks about symptoms, insurance, or medications, and then delivers the answers to a staff inbox as plain email through a third-party form service nobody signed an agreement with. It works. It looks fine. It is also a disclosure, and it has usually been running for two years before anybody notices.

The pattern repeats: an appointment request stored in a marketing platform's database, a chat widget that logs conversations to a vendor with no business associate agreement, an analytics tag firing on a page whose URL contains a condition name. None of it is malice. It is what happens when the people building the site have never had to think about where data comes to rest.

We treat that question as the first design input, not the last review gate. What is collected, where it lands, who can reach it, how long it is kept, and what is recorded about who looked at it — decided before the first component is written.

/// CAPABILITY MANIFESTWHAT WE BUILD IN THIS SECTOR

SYSTEMS THAT SURVIVE SCRUTINY

01
PRACTICE & CLINIC SITES
Provider directories, service lines, locations, and insurance information organised the way a patient actually searches — not the way the org chart is drawn. Fast on a phone in a waiting room.
02
PATIENT INTAKE
Forms that collect what the front desk genuinely needs, delivered over encrypted transport into a system covered by an agreement — never a marketing inbox, never a third-party form service chosen for convenience.
03
SCHEDULING INTEGRATION
Appointment requests and booking wired into the practice management or EHR system you already run, so the website stops being a parallel process someone has to rekey by hand.
04
PATIENT PORTALS
Authenticated areas with real access control, session handling, and audit logging — built when a portal is genuinely warranted, and argued against when a well-built public page would serve better.
05
ACCESSIBILITY
WCAG 2.1 AA as a build requirement. Healthcare audiences skew toward exactly the users that inaccessible interfaces exclude, and for many organisations the obligation is legal as well as ethical.
06
LOCAL SEARCH
Location pages, structured data, and the technical work that decides whether you appear when someone searches for your specialty near them. For most practices this is the entire acquisition channel.
/// CONSTRAINT SET

THE RULES THAT SHAPE THE ARCHITECTURE

REG / HIPAA

PHI NEVER TOUCHES A SYSTEM WITHOUT AN AGREEMENT

Anything that could carry protected health information routes only through infrastructure and vendors covered by a business associate agreement. If a tool cannot sign one, it does not go near the data — including analytics, chat, and form services.

SEC / ACCESS

ACCESS CONTROL AND AUDIT LOGGING

Authenticated areas get least-privilege roles, real session management, and logs that record who accessed what and when. Retention is set deliberately rather than left at whatever the platform defaulted to.

SEC / TRANSPORT

ENCRYPTED IN TRANSIT AND AT REST

TLS everywhere, modern ciphers, and storage encryption on anything persisted. Certificates renew automatically, because an expired certificate on a patient portal is both an outage and a trust event.

REG / ADVERTISING

TRACKING THAT DOES NOT LEAK DIAGNOSIS

Analytics and advertising tags are configured so page paths, query strings, and event payloads cannot carry condition or treatment detail to a third party. This is the single most common finding in the audits we run.

OPS / CONTINUITY

BACKUPS THAT HAVE BEEN RESTORED

Automated backups with tested restores and a documented recovery path. A backup nobody has ever restored is a hope, and hope is not a continuity plan when scheduling is down.

DOC / EVIDENCE

WRITTEN DOWN, NOT ASSUMED

Data flow diagrams, vendor inventory, and configuration decisions handed over as documentation. When your compliance officer or an auditor asks how something works, the answer exists on paper.

We build to these requirements and document what we did. We are engineers, not your counsel — your compliance officer signs off, and we give them something legible to sign off on.

/// FIELD REPORTS

CLIENT TRANSMISSIONS

VERIFIED OPERATOR FEEDBACK // CLEARANCE LEVEL: PUBLIC

"Nicklaus was absolutely fantastic to work with. He completely transformed our website for The CPG Co-Op, and the end result is better than I could have imagined. What really sets Nicklaus apart is that he’s not just a great designer—he has a deep understanding of the technical side of websites and the backend functionality that makes everything work. He was able to take a fairly complex project, handle the technical details seamlessly, and still make the entire process incredibly easy for me as someone who is, frankly, a total luddite when it comes to this stuff. He also built the site in a way that makes it incredibly easy for me to manage and make changes myself, which means we aren’t constantly paying someone every time we need to update something. That was a huge win for us. He was responsive, collaborative, incredibly fast, and genuinely cared about getting it right. I would highly recommend Nicklaus to anyone looking for someone who can bring the creative vision and the technical expertise to actually execute it. He made the whole process easy—and delivered a website we absolutely love."

EMILY KEALEY

FOUNDER // THE CPG CO-OP

ON THE CPG CO-OP

Emily Kealey portrait
/// FIELD QUESTIONS

STRAIGHT ANSWERS

CAN YOU BUILD A HIPAA-COMPLIANT WEBSITE?

A website is not certified compliant on its own — compliance is a property of your whole organisation, its agreements, and its policies. What we can do is build the technical side so it holds up: PHI routed only through infrastructure covered by a business associate agreement, encryption in transit and at rest, access control and audit logging, and tracking configured so it cannot leak clinical detail. We document all of it so your compliance officer has something concrete to review.

WILL YOU SIGN A BUSINESS ASSOCIATE AGREEMENT?

Where our work involves systems that handle protected health information, yes. We also tell you plainly when a project does not require one — a purely informational marketing site that collects nothing should be scoped so no PHI is ever in play, which is cheaper and safer than building something that needs the paperwork.

CAN YOU INTEGRATE WITH OUR EHR OR PRACTICE MANAGEMENT SYSTEM?

Usually. It depends on what the vendor exposes — a documented API, an HL7 or FHIR interface, or in the worst case a file drop. We establish what is actually available during scoping rather than promising an integration and discovering the limitation in week six. If the vendor offers nothing workable, we say so before you commit.

OUR CURRENT SITE WAS BUILT BY A MARKETING AGENCY. IS THAT A PROBLEM?

Not automatically, but it is worth checking. The recurring issues we find are forms that deliver patient information as plain email, chat or scheduling widgets from vendors with no agreement in place, and analytics tags capturing URLs that name a condition. We can audit the existing site and hand you the findings whether or not you engage us to fix them.

DO YOU WORK WITH HEALTH TECHNOLOGY COMPANIES AS WELL AS PROVIDERS?

Yes. Digital health products, medical device companies, and health SaaS all sit in the same constraint set with a different shape — the marketing site is usually straightforward, and the interesting work is in the product surfaces, the security posture your enterprise customers will diligence, and the documentation their procurement team will ask for.

HOW LONG DOES A HEALTHCARE BUILD TAKE?

A practice or clinic site is typically measured in weeks; anything with authenticated patient access or a system integration runs longer, because the integration and the review cycle set the pace rather than the design. You get a fixed scope and timeline in writing after the scoping call, not a range that drifts.

/// NEXT STEP

SEND US THE INTAKE FORM.

Point us at whatever on your current site collects information from patients. We will tell you where that data actually goes — within 24 hours, and without a proposal attached.