Choose requested health record categories and inspect returned consent metadata with ConsentLoom. Understand session access, sharing scope and revocation.
Site: https://consentloom.com/ Repository: https://github.com/consentloom/app
The previous synthetic demo integration has been removed. This client requests real patient-authorized records using FinchNode production through the shared connection service. It never calls the public demo API or falls back to fixture data.
Production activation is pending operator legal/privacy details and a server-side live key plus webhook signing secret. Until that is complete, connecting fails closed with an explicit setup message. Deployment of this code alone is not evidence of a completed real EHR connection.
The public home route presents a complete, individually designed website with navigation, a product explanation, and a primary import button. Import and private records live at /#/import; opening the homepage never starts a record request. The import button opens category selection before any external connection. Back to home clears records from the rendered page. Returning from Hosted Connect opens the import route. Existing sessions can be resumed via the homepage button.
Choose record categories, click Connect my EHR, and complete FinchNode Hosted Connect and your own provider sign-in. Consent identifies FinchApps Personal Health Tools, the shared application behind these eleven sites. Return here to view the authorized record. Each visitor session is isolated to this site's origin and expires after 30 minutes; free service restarts can end it earlier. Reconnect if necessary.
Consent scope simulator. Source names, dates, units, missing categories and partial sync warnings come from the production response. No patient identity, provider, measurement or connection is invented. FHIR Trail shows FinchNode's normalized records derived from FHIR, not an untouched FHIR bundle. ConsentLoom displays actual consent metadata. SourceWeave lists only the sources returned with the authorized record.
End this session removes local access. Revoke sharing or request deletion through FinchNode data controls. Sharing consent is for the common application, so revocation can affect all eleven tools. Exported or printed copies remain on the user's device.
Node 22.13+:
npm ci
npm run dev
npm test
npm run buildThe build outputs dist/. This is a React/Vite static frontend with responsive layouts, keyboard controls, visible focus styles and reduced-motion support. Development runs do not bypass production origin restrictions. To exercise authentication locally, run the backend's injected mock tests; do not relax its production allowlist or embed keys in the client.
Create a free Static Site from this repository, build with npm ci && npm run build, and publish dist. The supplied render.yaml documents the service and security headers. Public-repository deployments require a manual deploy after pushing a commit. The separate Node connection service runs on Render's free plan and may sleep.
CSP connect-src must allow only https://finchapps-connect.onrender.com. Deploy the backend and configure its secret environment before enabling live connections. Never add API keys to Vite variables, source, browser storage, logs, README examples or Git. No frontend environment secret is required.
Read the data-handling notice. No clinical record is saved in browser storage; visible data is held in memory, cleared on hiding the page, and periodically revalidated. No browser agent tools expose medical data. Unit tests validate production envelopes and preserve source values. Backend tests cover origin/session isolation, scope checks, invalid environments, expiration and signed revocation without using real medical data.
A real patient must perform their own EHR authentication and consent; these tests do not claim successful patient connectivity. Availability varies by healthcare organization.
consentloom.com is registered through Squarespace and assigned to this Render site. DNS uses an apex A record pointing to 216.24.57.1 and a www CNAME pointing to consentloom.onrender.com. Render redirects www to the apex domain and manages HTTPS certificates.
From category selection to a consent receipt — What each step of the sharing flow means, and why ending a browser session is different from revoking access.
Search ConsentLoom guides · About the site · Sitemap
ConsentLoom is a standalone product with its own interface, documentation and repository, prepared for independent business operation and continued development. Its FinchNode integration is documented in the code. Live production activation remains pending.
Edit content/seo.json for reviewed article text and site metadata. npm run build generates public HTML pages, a sitemap, social metadata and structured data, then prerenders the actual React homepage. npm run test:seo checks the built crawl surface after a build. Public guide search filters only public text in the browser; no patient data or search analytics enter the index.
Keep canonical URLs on the custom domain configured in content/seo.json. Add only public, canonical pages to the sitemap. Validate links, mobile layout and the built HTML after editorial changes. Search engine indexing and rich results are not guaranteed.
Business handoff covers product identity, the receiving business’s production setup, domain migration, search verification and ongoing editorial maintenance.
Understand category selection, returned consent receipts, session closure and sharing revocation through the controls implemented in ConsentLoom.
-
Ending a session vs revoking health-data sharing — Learn which ConsentLoom controls end local access, manage the authorized connection, or start a new request with different categories.
-
How to read a consent receipt in ConsentLoom — Inspect authorized categories, returned record counts, source receipts and expiry metadata without confusing a request with a completed authorization.
-
How to test consent behavior before launching a health app — ConsentLoom explains how to test category requests, granted access, expiry and revocation as observable product behavior before an independent deployment.