HIPAA-compliant intake forms, tracking-technology discipline, BAA-routed analytics.
Patient-facing intake forms collect Protected Health Information by default. Name plus appointment-type plus chief complaint is PHI as soon as the form lands in the practice's pipeline. Generic SaaS form vendors (Typeform, Google Forms, Jotform's default tier) cannot lawfully process the data without a Business Associate Agreement, encryption-in-transit and at-rest matching the HIPAA Security Rule technical safeguards, and a data-flow record. The architecture routes the intake through a HIPAA-aware vendor (Jotform HIPAA, Formstack Healthcare, or self-hosted with the encryption stack), captures consent for any marketing uses inline, and posts to a back-end that does not pass through generic logging.
Tracking technologies face a stricter rule. The HHS Office for Civil Rights bulletin (initial 2022-12-01, updated 2024-03) states that tracking technologies on a covered entity's webpages can constitute disclosures of PHI to the tracking vendor when the data includes patient identity or interaction signals 1 . Google Analytics, Meta Pixel, and similar trackers on a medical practice's site trigger the disclosure when they fire on authenticated patient surfaces or capture identifying queries on unauthenticated pages. Several covered entities have entered OCR resolution agreements over tracking-technology configurations since the bulletin issued. The architectural fix is server-side analytics where the vendor will sign a Business Associate Agreement and the events strip identifiers before they cross the boundary.
De-identification under 45 CFR 164.514 Safe Harbor exempts 18 specific identifiers (names, geographic subdivisions smaller than state, dates more granular than year, contact endpoints, account numbers, biometric identifiers, full-face photographs, and more) 3 . The intake architecture handles de-identification as a workflow input: data that travels into analytics, into the marketing surface, or into the editorial-content pipeline gets de-identified at the boundary or carries explicit authorization under 45 CFR 164.508.
MedicalBusiness + Physician + sameAs to NPI, ABMS, state medical board.
The schema architecture marks the practice location as MedicalBusiness (or a more specific subtype: MedicalClinic, Hospital, Dentist, etc.). Each attending physician marks up as Physician, which inherits from Person and MedicalOrganization 4 . The connection between facility and practitioner runs via employee or member on the MedicalBusiness, and worksFor or location on the Physician. The Physician node uses the sameAs property to chain to the NPI registry profile at NPPES 8 , the state medical board license profile, and the ABMS verification page 7 .
The sameAs chain is the load-bearing mechanism that transfers off-site EEAT to the on-site author byline. Without the chain, Google's entity resolver does not consolidate the physician across the public directory ecosystem and the practice's editorial content competes for ranking without the underlying entity signal. Praxis builds the chain into the JSON-LD on every author byline and into the practice's primary MedicalBusiness node site-wide.
The discipline that goes with the schema is what does NOT mark up. MedicalCondition, MedicalProcedure, MedicalTherapy, and Drug belong on encyclopedic editorial content. Applying them to a commercial service page that markets a procedure reads to Google's medical-content classifiers as an attempt to manipulate medical rich results 2 . The manual-action pattern for spammy structured data is well-documented. Commercial pages stay on MedicalBusiness + availableService. The clinical types ship only on the editorial template where a credentialed physician fronts the byline.
Editorial template separated from commercial. ABMS bylines. ADA Title III at WCAG 2.1 AA.
Articles authored or reviewed by the practice's physicians sit on a distinct template from the commercial service pages. The editorial template surfaces a named-author byline at the top of the article: name, ABMS board certification with member-board name, active state license number and jurisdiction, ACGME-accredited residency, and the link chain to NPI + state board + ABMS verification. Body copy reads peer-reviewed-journal adjacent. Numbered citation marks in the body link to a bibliography section at the article's end. The article-template structure tells Google's Reviews System framework where to read for the practicing-physician reviewer signal.
Accessibility runs on top of the architecture. ADA Title III applies to places of public accommodation and healthcare provider websites are treated as extensions of the physical practice 5 . The working compliance target is WCAG 2.1 Level AA conformance 6 . Common gaps surface in form-field labeling on appointment-booking surfaces, color contrast on procedure-page calls-to-action, keyboard navigation in patient-portal modals, and missing alt text on procedure illustrations. The accessibility audit runs alongside the schema and HIPAA audits in the diagnostic phase. Remediations route through the design system, not through one-off page patches, so the compliance state holds as the site grows.
The architecture sits inside the broader medical SEO work at Praxis. The website-design surface is one input. The schema layer, the editorial-content layer, the directory layer, the GBP layer all run against the same architectural discipline.