Spaces:
Running
Running
Commit History
-
inside each and ALL modals, all email, name, company, etc. entry boxes must be fixed, icons, etc. must be fixed - growth pricing 1,999/mo
Verified signature2611ab6 -
when you click on each button and modal opens, whatever is inside modal must be enhanced, in terms of design/css/etc. to be aligned with entire landing page
Verified signature7defb5a -
1-enhance and fix all modals 2-esc key must work to exit modals
Verified signature3bf73b2 -
1-create modals for all buttons 2- faq must be collapsing 3- enhance copywriting 10x
Verified signature226d3a5 -
create a modern landing page for following- restriction: no image is permitted - Agreed. For the public landing, you should position the outcomes (safe, structured, auditable clinical processing) and keep the implementation details (OpenMed, Parsr, ClickHouse, Meilisearch, etc.) for the Docs / Developer Portal / Security page. That reduces vendor-dependence perception and avoids anchoring buyers on “components” rather than “guarantees.”
Verified signatureBelow is a re-written landing page with no mention of OpenMed or any underlying stack, plus updated visual mockups that communicate the value without naming internals. ⸻ ClinicalAPI.com — Landing Page Copy (Stack-Agnostic) Header • Product • Solutions • Deployment (SaaS / BYOC) • Security • Developers • Pricing • Company • Sign in • Get API Key ⸻ Hero H1 Clinical documents in. Safe, structured outputs out. Subhead ClinicalAPI preprocesses, de-identifies, extracts, and normalizes clinical text into audit-ready outputs—via a single API. Run fully managed or deploy runtimes into your AWS account to keep PHI inside your boundary. Primary CTAs • Get API Key • Book a Demo Secondary links • View Docs • BYOC Overview • Security Overview One-line proof Policy-gated PHI processing, evidence packs, versioned pipelines, and usage-based billing—built for regulated workflows. ⸻ Visual mockup #1: “One request → governed pipeline” A single horizontal pipeline with labeled …8627915